HP BL860c, SmartSetup Scripting Toolkit Administrator's Manual

Microsoft Windows Server 2008 SP2 and
Windows Server 2008 R2 on HP Integrity
Servers
SmartSetup Scripting Toolkit Administrator's
Guide

Abstract

This document describes how to use the SmartSetup Scripting Toolkit (SSTK). This document is for system administrators who
write scripts to automate hardware configuration and software installation operations for HP Integrity® server deployments.
You must have some expertise in unattended installations of Windows Server 2008 and in configuring Integrity server hardware.

HP Part Number: T2369-96019
Published: April 2011

© Copyright 2011 Hewlett-Packard Development Company, L.P

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial
Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under
vendor's standard commercial license.

The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express
warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall
not be liable for technical or editorial errors or omissions contained herein

SmartSetup Scripting Toolkit uses Linux and related open source software under the terms of the GPL and includes the source of that software in the
SmartSetup Scripting Toolkit package.

Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. Intel and Itanium are registered trademarks of Intel Corporation
or its subsidiaries in the United States and other countries.

Contents

1 Overview..................................................................................................6

Minimum requirements..............................................................................................................6

SSTK environment.....................................................................................................................6

SSTK boot image.................................................................................................................7

SSTK repository...................................................................................................................7

The deployment process............................................................................................................7

Extracting the SSTK package......................................................................................................8

2 Creating an SSTK boot image....................................................................12

Editing the SSTKStart.cmd file...................................................................................................12

Installing OEM drivers in the boot image...................................................................................13

Creating the boot image.........................................................................................................13

Setting up the boot mechanism.................................................................................................14

Creating a bootable CD/DVD or virtual media......................................................................14

Creating a Bootable USB flash device..................................................................................16

Setting up a network boot environment.................................................................................16

Windows Deployment Services.......................................................................................17

3 Configuring an SSTK action.......................................................................19

commandprompt action...........................................................................................................19

readhwconf action..................................................................................................................19

Configuring conrep............................................................................................................20

applyhwconf action................................................................................................................20

sethbabootdevice action..........................................................................................................20

applysasconf action................................................................................................................21

Choosing the installation disk...................................................................................................21

deploy action.........................................................................................................................22

Uploading the Windows installation files..............................................................................22

Uploading the Integrity Support Pack 7.1..........................................................................23

Uploading the Smart Update Pack...................................................................................23

Preparing for Windows Server 2008 SP2 or R2 deployment....................................................23

Uploading OEM device drivers.......................................................................................24

Modifying the answer file...............................................................................................24

Editing the SSTKConfig.cmd file.......................................................................................25

Editing the default_layout_2008.txt file............................................................................26

Replicating a server configuration.............................................................................................26

4 Booting the server....................................................................................27

Boot instructions.....................................................................................................................27

Booting from the CD/DVD..................................................................................................27

Boot from the USB flash device............................................................................................27

Booting from the network....................................................................................................27

SSTK log file..........................................................................................................................28

Log file format...................................................................................................................28

Monitoring the Deployment......................................................................................................28

5 Advanced topics......................................................................................30

Customizing the SSTK boot image.............................................................................................30

Contents 3

Enabling a boot device on a SAN............................................................................................30

Increasing security in SSTK.......................................................................................................31

Encrypting the repository password......................................................................................31

Setting permissions for repository access...............................................................................32

Checking the CLM mode.........................................................................................................32

Enabling Max Payload Size.....................................................................................................33

6 Utilities reference......................................................................................34

conrep..................................................................................................................................34

Synopsis...........................................................................................................................34

Description........................................................................................................................34

Options............................................................................................................................34

Examples..........................................................................................................................35

Return codes.....................................................................................................................35

hpacuscripting........................................................................................................................36

Synopsis...........................................................................................................................36

Description........................................................................................................................36

Options............................................................................................................................37

Sample Script File..............................................................................................................37

Error reporting...................................................................................................................38

hpchkclm...............................................................................................................................42

Synopsis...........................................................................................................................42

Description........................................................................................................................42

Options............................................................................................................................43

Example...........................................................................................................................43

hpshowdisk............................................................................................................................43

Synopsis...........................................................................................................................43

Description........................................................................................................................43

Options............................................................................................................................43

Examples..........................................................................................................................44

Return Codes.....................................................................................................................44

hwdiscovery...........................................................................................................................45

Synopsis...........................................................................................................................45

Description........................................................................................................................45

Options............................................................................................................................45

Example...........................................................................................................................46

Error Codes......................................................................................................................46

hwquery................................................................................................................................47

Synopsis...........................................................................................................................47

Description........................................................................................................................47

Options............................................................................................................................47

Examples..........................................................................................................................47

ifhw......................................................................................................................................47

Synopsis...........................................................................................................................47

Description........................................................................................................................47

Options............................................................................................................................47

Examples..........................................................................................................................48

Return Codes.....................................................................................................................49

sethbaini...............................................................................................................................49

Synopsis...........................................................................................................................49

Description........................................................................................................................49

Options............................................................................................................................49

Example...........................................................................................................................49

Return Codes.....................................................................................................................50

4 Contents

sstkencrypt.............................................................................................................................50

Synopsis...........................................................................................................................50

Description........................................................................................................................50

Example...........................................................................................................................50

sstkmount..............................................................................................................................50

Synopsis...........................................................................................................................50

Description........................................................................................................................50

Parameters........................................................................................................................50

Example...........................................................................................................................51

7 Support and other resources......................................................................52

Contacting HP........................................................................................................................52

Documentation feedback.........................................................................................................52

Typographic conventions.........................................................................................................52

A Support Matrix........................................................................................53

Contents 5

1 Overview

The SmartSetup Scripting Toolkit (SSTK) provides utilities and scripts that simplify the tasks of
deploying Windows on HP Integrity® servers by automating hardware configuration and software
installation. Using the SSTK, you can deploy a large number of servers efficiently by replicating a
server configuration and performing a Windows unattended installation. This reduces the time,
effort, and errors involved in these high-volume server deployments.

The SSTK sample scripts and utilities run in a pre-boot environment based on Windows PE for
IA-64.

CAUTION: Improper use of the SSTK utilities can result in data loss. Therefore, use the SSTK

utilities only if you have experience installing and configuring hardware and software.

This chapter describes the minimum requirements for running the SSTK, the SSTK environment, an
overview of the deployment process, and the SSTK package contents.

Minimum requirements

To use the SSTK, you must have the following:

• A workstation with Windows Server 2003 SP2

• Installation media for Microsoft Windows Server 2008 with SP2 for Itanium-based systems

and for Microsoft Windows Server 2008 R2 for Itanium-based systems

NOTE: You only need the installation media one time to populate the Windows install files

on the SSTK repository server.

• Windows Automated Installation Kit (AIK) 2.0 for IA64, containing WinPE image files

• Integrity Support Pack 7.1 for Windows Server 2008 SP2 and Windows Server 2008 R2

• Installation CDs for Windows Server 2008 IA64 SP2 and Windows Server 2008 IA64 R2

• Windows Deployment Services (WDS) server

SSTK environment

The SSTK enables you to configure and deploy Windows on Integrity servers with minimum user
interaction. You can use the SSTK scripts and utilities to configure a server or replicate the
configuration of a model server to a large number of servers. The configuration includes setting
EFI variables, RAID configuration, disk partitioning, and Host Bus Adapter (HBA) configuration.
The software deployment includes Windows Server 2008 with SP2 for Itanium-based systems,
Windows Server 2008 R2 for Itanium-based systems, and Integrity Support Pack (ISP) 7.1
installation.

Figure 1 shows a typical SSTK deployment scenario.

6 Overview

Figure 1 Simple SSTK Deployment Scenario

SSTK repository

(Workstation)

SSTK boot image

(Target Server)

CommandPrompt

ReadHWConf

ApplyHWConf,
ApplySASConf and Deploy

You use a workstation to unpack the toolkit, edit the configuration files, and set up the boot
mechanism. The workstation typically hosts the SSTK repository, which holds the configuration files,
scripts, utilities, and Windows installation files.

Each time the target server loads the SSTK boot image, the repository is shared and the SSTK
performs a preconfigured action. Sample actions include saving the server configuration
(ReadHWConf), replicating a saved configuration (ApplyHWConf), applying RAID1 configuration
to a LSI SAS 1068 Controller ApplySASConf, and installing Windows (Deploy), or showing a
command prompt in order to run the SSTK utilities manually (CommandPrompt).

SSTK boot image

The SSTK boot image is based on the Windows Pre-installation Environment (Windows PE). Windows
PE is a subset of the Windows 2008 Kernel and provides operating system features for the toolkit.
For more information, see the Windows PE User’s Guide in the Windows Automated Installation
Kit (AIK).

The SSTK provides a script to create a customized boot image using AIK tools. This is described
in Chapter 2 (page 12).

SSTK repository

Every server that boots to the SSTK environment must have access to the repository of configuration
files, scripts, utilities, OS files, driver files, and application files. If you host the repository on the
workstation, it must be accessible to the Integrity servers being deployed.

IMPORTANT: A repository solution is not limited to the previous example. You can host the

repository on a boot device (a local disk on the Integrity server or a USB device). The repository
must have write permission in order to save SSTK log and data files.

The deployment process

The deployment process consists of the following steps:

1. Extract the SSTK software package.

2. Create an SSTK boot image.

3. Configure an SSTK action.

4. Boot the target server and monitor the deployment using the SSTK log system or Integrated
Lights-Out (iLO) interface.

The deployment process 7

Typically, you perform steps 1 and 2 only once. Steps 3 and 4 are performed multiple times,
depending on the number of target servers you need to deploy. The following section describes
how to extract the SSTK package. The remaining chapters describe the other steps.

Extracting the SSTK package

The SSTK software package is a self-extracting package component. You can extract files by
double-clicking the SSTK package component cp012164.exe. Figure 2 shows the Package Setup
screen.

Figure 2 HP Package Setup screen

If you use the workstation to hold the SSTK repository, extract the contents of the package to a
destination folder (SSTK root folder). In Figure 3, the root folder is SSTK-WindowsIntegrity.
You must share the SSTK root folder and set Read-Write permissions to all subfolders. For information
on how to restrict write permission in the SSTK repository, see “Increasing security in SSTK”

(page 31).

Figure 3 SSTK repository folder

boot Contains boot files for the SSTK boot image and the following script. The

OEMDrivers subfolder stores the device drivers to be installed on the boot

image. For more information, see Chapter 2 (page 12).
SSTKStart The startup script included on the SSTK WinPE image that mounts

the repository share, initializes the log file, and runs the
SSTKMain script. This script holds the repository configuration.
You must edit this script only once before creating the SSTK WinPE
boot image. See “Editing the SSTKStart.cmd file” (page 12).

data_files Contains the following configuration files for the SSTK utilities and SSTK log files.

array_settings\
hpacucapt.ini

The configuration file captured by the
hpacuscripting tool that contains the
MSA RAID and controller configuration.
This folder also contains sample standard
array configuration files that can be

8 Overview

applied to Smart Array controllers with the
hpacuscripting tool.

This file is created when the

readhwconfig option is executed.

conrep.dat A file into which the conrep tool saves

the values of the EFI variables contained
in the conrep.xml configuration file.

This file is created when the readhwconf
action is executed.

hwdisc.dat The hwdiscovery output file that

contains a system inventory to be used by
the ifhw and hwquery utilities.

This file is created when the readhwconf
action is executed.

hba-qlogic.ini The QLogic HBA configuration file, used

to enable or disable boot devices on
QLogic host bus adapters (HBAs).

This file is created when the readhwconf
action is executed.

hba-emulex.ini The Emulex HBA configuration file, used

to enable or disable the boot devices on
Emulex HBAs.

This file is created when the readhwconf
action is executed.

logs This folder stores log files that are created

during SSTK execution. Use the log files
to monitor the deployment process and to
troubleshoot any problems.

oem Contains the OEM drivers used by the OS setup process.
os Contains Windows Server 2008 SP2 and Windows Server 2008 R2 installation

files and their respective answer files for unattended installations. See “Uploading

the Windows installation files” (page 22).

scripts Contains the following SSTK Windows configuration and installation scripts that

control SSTK execution, run the utilities, and deploy Windows:
SSTKConfig The main SSTK configuration file in which

you set the action for SSTK to take each
time a system boots to SSTK WinPE. You
must edit this script before initiating an OS
deployment. See “Editing the

SSTKConfig.cmd file” (page 25).

SSTKMain Controls the SSTK execution depending

on the configured action.

ReadHWConf Called if the configured action is

readhwconf. It calls hwdiscovery,
conrep, the Emulex and QLogic

configuration tools, and
hpacuscripting. See “readhwconf

action” (page 19).

Extracting the SSTK package 9

ApplyHWConf Called if the configured action is

applyhwconf. It calls conrep, the

Emulex and QLogic configuration tools,
and hpacuscripting. See

“applyhwconf action” (page 20).

SetHBABootDevice.cmd Capture the Fibre Channel Controller HBA

INI file (hba_emulex.ini or
hba_qlogic.ini), updates it with
information about WWID and LUN, and
applies the new configuration in the card.
For Emulex, it also sets the

HostAdapterBiosEnable and
SelectBootEnable parameters. For

QLogic, it also sets the SelectiveLogin
parameter.

DeployWS2008.cmd Performs Windows Server 2008 SP2 or

Windows Server R2 installation. See

“deploy action” (page 22).

CheckESP.cmd Tests if there is more than one ESP partition

on the system.

SetWS2008SP2.cmd,
SetWS2008R2.cmd

Optional scripts for configuring a deploy
action manually from the command
prompt. If you use these scripts, you do
not need to reconfigure the
SSTKConfig.cmd file. These scripts set
the os_deploy variable to

2008-server-sp2 and
2008-server-r2, respectively. The

scripts also set the paths to the answer files
(unattend_files variable) and to the
OS installation files (windows_files
variable). To run these scripts, follow these
steps:

1. At the command prompt, run
SSTKStart.cmd.

2. Run SetWS2008SP2.cmd or
SetWS2008R2.cmd (Windows
Server 2008 SP2 or Windows Server
2008 R2, respectively).

3. Run DeployWS2008.cmd to begin
the deployment process.

CaptureArrayConfiguration Runs the hpacuscripting utility to

capture the Smart Array RAID
configuration.

ApplySaSConf Applies RAID 1 configuration to an LSI

1068 controller on BL860c systems and
RAID1 + RAID1 configuration to an LSI
1068 controller on and BL870c systems.
See “applysasconf action” (page 21).

SSTKLogInit, SSTKLogger Manages the SSTK log system. See “SSTK

log file” (page 28).

10 Overview

CopyISP, CopySmartUpdate,
PostInstall2008SP2,
PostInstall2008R2

After Windows installation, the post-Install
script calls the Integrity Support Pack (ISP)
installer if ISP installation files are
available on the repository.

For information on configuring the SSTK
repository, see “Uploading the Windows

installation files” (page 22).

diskpart\default_layout_2008.txt A diskpart script that specifies the

installation disk partition layout for
Windows Server 2008 SP2 and Windows
Server R2.

software Contains ISP installation files, SmartUpdate installation packages, and additional

software to be installed after the operating system is initially installed. See

“Uploading the Integrity Support Pack 7.1” (page 23). and “Uploading the Smart
Update Pack” (page 23).

utilities Contains the toolkit utilities. For complete information on each SSTK utility, see

Chapter 6 (page 34).

Extracting the SSTK package 11

2 Creating an SSTK boot image

After you set up the workstation, you create an SSTK boot image. The boot image starts the target
server in order to execute an SSTK action.

NOTE: The network location of the SSTK repository share is configured in the boot image. If you

want to change or access a different repository share, you must edit the SSTKStart.cmd file and
create the boot image again.

Creating a boot image consists of the following tasks:

1. Editing the SSTKStart.cmd file.

2. Installing OEM drivers in the boot image.

3. Creating the boot image

4. Setting up the boot mechanism

This chapter describes these tasks.

Editing the SSTKStart.cmd file

The SSTKStart.cmd file is the SSTK bootstrap file that contains information for accessing the
repository share and for initializing the deployment process.

NOTE: You must edit the boot\SSTKStart.cmd file before creating an SSTK boot image.

The file contains the following variables.
repository_name Specifies the hostname or IP address (IPv4 or IPv6) of the

system that hosts the repository.

share_name Specifies the name of the directory marked as shared on

the repository system.

repository_user Specifies the user name to access the repository share. The

format is username or domain\username.

repository_password Specifies the password (in plain text) for the user on the

repository system.

repository_encrypted_pass Specifies the encrypted password generated by

sstkencrypt utility (see “Encrypting the repository

password” (page 31)).

NOTE: The repository password can be a plain text

password or an encrypted password. If you decide to use
a plain password, you must comment the encrypted
password variable and set the plain password properly. For
information on encrypting the repository password, see

“Encrypting the repository password” (page 31).

repository_letter Specifies the letter to which to map the repository share.

The default is y:.

A sample SSTKStart.cmd script is as follows:

repository_name=192.168.0.220

1

share_name=sstk_repository
repository_user=Administrator
rem repository_password=

2

repository_encrypted_pass=a89ea897a9aa9ea298

repository_letter=y:

12 Creating an SSTK boot image

1

SSTK only supports DHCPv6 and Router Advertisement IPv6 addresses. If you need to use the
IPv6 address directly, you must convert the IPv6 address to the Microsoft ipv6-literal
namespace format. Convert the colon symbol (:) to the hyphen symbol (-) and append

ipv6-literal.net . For example, convert the Router Advertisement IPv6 Address
2001:db8:100:f101:21a:4bff:fecd:8697 to
2001-db8-100-f101-21a-4bff-fecd-8697.ipv6-literal.net. For example,

convert the DHCPv6 IPv6 Address: 2002::2 to 2002--2.ipv6-literal.net.

2

The repository password can consist of up to 127 alphanumeric characters, including the
following symbols: `, ~, !, @, #, $, %, ^, &, *, (, ), _, +, -, =, {, }, |, [, ], \, :, ", ; , ',
<, >, ?, ,, and .. In addition, blank spaces are also valid. If you use any of the previous
non-alphanumeric characters or blank spaces, you must enclose the password in quotation
marks. If you use ", you must escape it with \. For example, if you enter

"myStrong385$%\"paSsWorD" in sstkencrypt, the command outputs
549eae85aba6a89e9c676a6659579356a99188a789a0a77659. Use the sstkencrypt

output to set the repository_encrypted_pass variable.

Installing OEM drivers in the boot image

Installing OEM drivers in the SSTK boot image does the following:

• Guarantees that the SSTK utilities run on WinPE.

• Provides hardware support during Windows Server 2008 SP2 and Windows Server R2 setup.

Appendix A (page 53) shows the hardware that require you to install an OEM driver in the SSTK

boot image.
Any device driver placed under boot\OEMDrivers folder is automatically installed on the SSTK

boot image when it is created. For example, to add the Emulex 4Gb device driver for A8002A
and A8003A controllers, follow these steps:

1. Extract the Integrity Support Pack 7.1 package that contains the driver files.

2. Under the SSTK boot\OEMDrivers folder create a new folder with a generic name. For
example, \boot\OEMDrivers\emulex. The folder name must not contain any white spaces.

3. Copy all files extracted from the ISP component to that folder. Be sure to copy the SYS, CAT,
and INF files.

Use this procedure to add other device drivers.

Creating the boot image

To create an SSTK boot image, follow these steps:

1. Navigate to the \boot folder as follows:

cd \SSTK-WindowsIntegrity-4.1\boot\

2. Run the mkbootimg.cmd script as follows:

mkbootimg

This script creates a customized image (boot.wim) in the winpe\iso\sources\ folder. For a
description of the mkbootimg.cmd script, see “Customizing the SSTK boot image” (page 30).

This script has the following characteristics:

• Assumes that a default AIK installation is located at the following location:

%ProgramFiles%\Windows AIK\
If you want to change the location of the Windows AIK, change the SOURCE variable in the

mkbootimg.cmd script.

Installing OEM drivers in the boot image 13

NOTE: The repository must be on the same letter drive on which the AIK was installed.

• Creates the default path for EFI booting in the winpe\iso folder as follows:

efi\boot\bootia64.efi

Where: bootia64.efi is the SSTK boot loader utility.

After creating a boot image, you must set up a boot mechanism (CD/DVD, USB or PXE). See

“Setting up the boot mechanism” (page 14).

Setting up the boot mechanism

The SSTK supports three boot mechanisms: CD/DVD, USB device, or network boot. The boot
mechanism holds the files that boot the server to the toolkit environment and run the main script.
The main script gets configuration files, OS files, and application files from the repository, configures
the hardware, and installs the software.

NOTE: For mid-range and high-end systems, you must manually set the ACPI mode in the EFI

Shell prior to booting for the first time to WinPE.

This section describes how to perform the following tasks:

• Creating a bootable CD or DVD

• Creating a bootable USB device

• Setting up a network boot environment

Creating a bootable CD/DVD or virtual media

To create a bootable CD or DVD to launch the SSTK, follow these steps

1. Navigate to the SSTK \boot folder as follows:

cd Your SSTK root folder\boot\

2. Run the mkbootiso script as follows:

mkbootiso

The mkbootiso script automatically detects and uses the version of the AIK installed on the
machine

This scripts creates a bootable CD/DVD image named bootimg.iso. You can burn this image
file to a CD/DVD using any CD or DVD-burning application. Alternatively, you can mount the ISO
image using virtual media in the Integrated Lights-Out (iLO) interface, if available.

To configuring virtual media, follow these steps:

1. Connect to the target server iLO interface by typing the MP IP address in your favorite browser.

2. Select Virtual Media.

3. Click Launch.

4. Select Local Image File.

5. Click Browse and select the SSTK boot image (bootimg.iso).

6. Click Connect.

Figure 4 shows this process for the iLO 2 interface.

14 Creating an SSTK boot image

Figure 4 Configuring virtual media using the iLO interface

Figure 5 shows this process for the iLO 3 interface.

Setting up the boot mechanism 15

Figure 5 Configuring virtual media using the iLO 3 interface

When the EFI Shell starts at the target server, a virtual file system is available with the SSTK boot
files. You can add a new boot entry using the EFI Boot Manager.

Creating a Bootable USB flash device

To create a bootable USB flash device, use the xcopy command to copy the appropriate files
from your workstation to the USB flash device. For example:

xcopy winpe\iso\*.* /s /e /f f:\

Where:

winpe\iso The folder created by the mkbootimg.cmd script.
f: The letter of your USB flash device.

Setting up a network boot environment

The following sections show how to set up a network boot environment for SSTK using the Windows
Deployment Sever (WDS) for Windows Server 2003 SP2.

NOTE: For mid-range and high-end systems, you must manually set the ACPI mode in the EFI

Shell prior to booting for the first time to WinPE.

Figure 6 shows an environment where SSTK is configured in an isolated network with the following

machines:

• A gateway configured as VPN server

• A Proliant DL380 or any compatible x86 system configured as Primary Domain Controller,

DHCP server, and host of the SSTK repository

• A target server connected to the SSTK network

16 Creating an SSTK boot image

Figure 6 Sample SSTK Network Environment

Gateway/VPN

Isolated network -

10.51.201.0/24

Target / dynamic IP

Active Directory / DHCP / SSTK Repository

CORPNET

Windows Deployment Services

Windows Deployment Services (WDS) is included in Windows Server 2003 SP2. You can integrate
the SSTK with the WDS Server Components, which include a Pre-Boot Execution Environment (PXE)
server.

An advantage of using WDS for network boot is that a boot menu is automatically configured
when more than one SSTK boot image is added.

To configure WDS, see the Microsoft TechNet Windows Deployment Services Update Step-by-Step
Guide for Windows Server 2003 at:

http://technet2.microsoft.com/WindowsVista/en/library/
9e197135-6711-4c20-bfad-fc80fc2151301033.mspx

After WDS is configured, add an SSTK boot image by following these steps:

1. Start Windows Deployment Services.

2. Click to expand the Servers list, then click the server to which you want to add the image.

3. Right-click the Boot Image node, then click Add Boot Image.

4. On the Image File page, browse to the location of the image created by the mkbootimg.cmd
script. Click Open to continue.

Setting up the boot mechanism 17

5. Enter the name and description of the boot image or accept the defaults.

6. When the image copy has completed successfully, click Finish to exit the wizard.
To add another image, repeat the preceding steps. WDS now displays a boot menu.

NOTE: You must use the default IA64 boot loader, which is already set to bootmgfw.efi in

WDS.

18 Creating an SSTK boot image

3 Configuring an SSTK action

After you create the boot image, you must configure an SSTK action. When the target server boots
up, the SSTK boot image initiates the SSTK action (ReadHWConf, ApplyHWConf, ApplySASConf,
CommandPrompt, SetHBABootDevice, or Deploy) specified in the repository. The process
runs without user intervention.

You set the SSTK action in the SSTKConfig.cmd file located under the scripts folder. The

default_action variable specifies one of the following actions to be performed by SSTK:
commandprompt Boots the SSTK and waits for user interaction. This is the default action.

readhwconfig Reads the hardware configuration variables and saves the configuration

files to the data_files folder.

applyhwconfig Writes the hardware configuration files previously saved in the

data_files folder.

sethbabootdevice Sets the boot device to the selected disk in the Fibre Channel controller

(Emulex or QLogic). The script captures the INI file (hba_emulex.ini
or hba_qlogic.ini, respectively), updates it with the WWID, LUN,
and other needed parameters and applies the new configuration to the
controller.

applysasconf Configures RAID 1 on LSI1068 or LSI1078 controllers.
deploy Deploys the operating system configured in the os_deploy variable.

This chapter describes how to configure and use the different actions to configure the server,
replicate a server configuration, and prepare for Windows Server 2008 SP2 and Windows Server
2008 R2 deployment.

commandprompt action

The commandprompt action is useful if you must interact with the target server. When you boot
the target server to WinPE with the commandprompt action enabled, you can run the SSTK utilities
manually and retrieve some system information, or examine the hardware profile.

When the default_action variable is set to commandprompt in the SSTKConfig.cmd file,
a Special Administration Console (SAC) is available when target system boots up. You can open
a Windows PE command prompt by entering the following:

SAC>cmd

Then press ESC and TAB to switch among channels.
At the command prompt you are able to access the SSTK repository, mounted at volume y: by

default. Run the SSTK utilities from y:\utilities folder.

NOTE: You can invoke the SSTK bootstrap script at any time from the command prompt to execute

a new action configured in the STKConfig.cmd file by entering the following:

c:\Windows\System32\SSTKStart.cmd

readhwconf action

The readhwconf action reads the hardware configuration and saves the configuration files to
the data_files folder in the repository. You can use these configuration files afterwards for
server replication (EFI variables, Array Configuration Utility (ACU), and HBA configuration). See

“applyhwconf action” (page 20).

commandprompt action 19

Configuring conrep

By default, the conrep utility reads the following EFI variables as configured in the conrep.xml
file and saves the variable data saved to conrep.dat file:

• Lang

• Default

• UIOption

• CPUTreadControl

• Timeout

• AutobootRetry or AutobootRetries

To read (replicate) another EFI variable, edit the conrep.xml file and add it. Use the EFI Shell
dmpstore command to list the variables and their values on the target server.

See Chapter 6 (page 34) for additional information on utilities called by the readhwconf action.

NOTE: By default, ACU reads the RAID configuration with the –internal switch showing

information about Direct Attached Disks (DAS) only. If you want to capture information on Storage
Area Network (SAN) disks, remove the –internal switch in the
CaptureArrayConfiguration.cmd script.

applyhwconf action

The applyhwconf action replicates the configuration files saved in the data_files folder as
described in “readhwconf action” (page 19).

If you want to skip some configuration variables (EFI , ACU, or HBA), delete (or rename) the
corresponding configuration file. For example, if you rename the ACU configuration file, the current
array configuration on the server is preserved when applyhwconf runs.

NOTE: If an EFI variable saved in the conrep.dat configuration file does not exist on the target

server, SSTK does not create it by default. Use conrep with the –F switch if you want to create
new EFI variables when applying the conrep configuration file.

When applying the RAID configuration with ACU, the disk IDs can change. If you want to install
to a disk other than the first disk (disk ID 0), HP recommends you use the hpshowdisk tool to
ensure you are choosing the correct installation disk. See “Choosing the installation disk” (page 21).

IMPORTANT: Always use the –internal switch when applying the RAID configuration with

ACU. This prevents overwriting the Emulex or Qlogic HBA configuration in the Storage Area
Network (SAN) environment.

sethbabootdevice action

The sethbabootdevice action sets the boot device. This configuration is needed in order to
deploy the Windows operating system in disks present in storage controlled by Emulex or QLogic
in SAN environments. This action performs the following:

1. Calls the hpshowdisk utility using the number set in the hbabootdevicediskid variable

(in SSTKConfig.cmd script) to retrieve the WWID and LUN information of the disk.

2. Calls the sethbaini utility to write the information in the corresponding INI file.

3. Applies the new configuration in the controller using the Emulex configuration tool or the

Qlogic configuration tool.

To set the hbabootdevicediskid variable, follow these steps:

1. Set the default_action variable to commandprompt in the SSTKConfig.cmd script.

20 Configuring an SSTK action

2. Boot to WinPE.

3. Open a command prompt window.

4. Run the hpshowdisk utility as follows:

run y:\utilities\hpshowdisk -n

5. Find the disk you want in the list of disks and get the disk ID.

6. Set the hbabootdevicediskid variable to the disk ID in the SSTKConfig.cmd script.

7. Set the default_action variable to sethbabootdevice in the SSTKConfig.cmd script.

8. Reboot to WinPE.

IMPORTANT: Be sure there is at least one presentation configured to some Fibre Channel controller.

Otherwise, the sethbabootdevice action will have no affect.
If the hbaapi.dll is not present in the utilities directory under the SSTK repository tree, this action

will not function correctly. In order to obtain that DLL, see the following issue in section 7 of the

readme file:

"HPshowdisk utility and SetHBABootDevice action do not work properly
if hbaapi.dll is not present"

applysasconf action

When the default_action variable is set to applysasconf, the ApplySASConf.cmd script
executes. If the target system is a BL860c, it applies RAID1 array configuration. If it is a BL870c,
it applies RAID1 + RAID1 array configuration.

Choosing the installation disk

By default, the toolkit installs Windows at the first disk (disk ID 0). If you want to install Windows
on another disk, the hpshowdisk tool can help you identify the target disk by showing disk details,
such as disk size and type.

To run hpshowdisk, follow these steps:

1. Boot the target server using the commandprompt action.

2. Open a Windows PE command prompt and enter hpshowdisk.

3. Change to the y:\utilities directory.

4. Run hpshowdisk -n.

Y:\utilities>hpshowdisk -n
HP Smart Array
HP Smart Array P400 Controller - 05132-B21
Disk ID 0: LUN 0 - 101.65 GB
HP PCIe Smart Array P411 SAS Controller - AM311A
Disk ID 1: LUN 0 - 169.43 GB
Disk ID 2: LUN 0 - 698.56 GB

If you want to install Windows on the disk connecting HP Smart Array P411, for example, choose
disk 1.

After you identify the installation disk, edit the following SSTK diskpart script to set the disk ID
of the installation disk:

diskpart\
default_layout_2008.txt

For installing Windows Server 2008 SP2 and Windows
Server 2008 R2

You must also edit the os\unattended_files\2008-server-version\unattended.xml
file (or unattended-JP.xml for Japanese Windows deployment) and set the disk ID of the
installation disk. For example:

<InstallTo>
<DiskID>1</DiskID>
</InstallTo>

applysasconf action 21

Edit the file with a text editor or by using SIM as explained in “Modifying the answer file” (page 24).

NOTE: For Storage Area Network (SAN) disks, make sure the installation disk is a boot device

(available on EFI for booting). For information on how to set a boot device, see “Enabling a boot

device on a SAN” (page 30).

deploy action

The deploy action performs the following tasks:

• Checks the CLM mode (hpchkclm)

• Creates and formats disk partitions (diskpart)

• Copies the ISP and SmartUpdate files

• Copies the PostInstall script

• Executes Windows Setup

• Reboots the system

NOTE: If you populated the ISP or SmartUpdate folders on the SSTK repository, the Postinstall

scripts automatically run and install the ISP package and QFEs just after the first boot to the newly
installed OS. In this case, the system automatically reboots one time after the SmartUpdate
installation and one more time after the ISP installation.

After Windows installation, the firewall is enabled by default. However, the unattended files
provided by the SSTK are configured to enable Firewall exception for Remote Desktop.
This enables you to connect to the target server using Remote Desktop. To obtain the target server
IP address, enter the i command at the Windows SAC.

Before initiating a deploy action for Windows Server 2008 SP2 or Windows Server 2008 R2,
you must do the following:

• Upload the Windows installation files

• Upload the OEM device drivers

• Modify the answer file

• Edit the SSTKConfig.cmd file

Uploading the Windows installation files

The os folder contains the Windows answer files and the installation files. Figure 7 shows the
structure of this folder.

Figure 7 Destination folder for Windows installation files

22 Configuring an SSTK action

After the specific Windows folder exists, copy the contents of the Windows installation CD to the
respective folder under os\windows.

Uploading the Integrity Support Pack 7.1

The Integrity Support Pack (ISP) provides a set of tools and device drivers for Integrity servers that
can be automatically installed after Windows installation. Figure 8 shows the destination folder of
ISP installation files.

Figure 8 Destination folder for ISP installation files

Copy all files from contents\supportpack\isp folder on the ISP installation CD to the
windows\ISP\ SSTK folder. For more information, see the ISP documentation.

Uploading the Smart Update Pack

The Smart Update Pack contains high priority operating system updates and security fixes to keep
your Integrity server up-to-date and secure. You can automatically install these files after Windows
installation. Figure 9 shows the destination folder of Smart Update installation files.

Figure 9 Destination folder for Smart Update installation files

To obtain the Smart Update Pack, go to http://www.hp.com/support/itaniumservers and download
Microsoft Integrity Operating System – Enhancements and QFEs. Copy the downloaded components
to the windows\SmartUpdate\2008-server-version SSTK folder.

Preparing for Windows Server 2008 SP2 or R2 deployment

To prepare for Windows Server 2008 SP2 or Windows Server 2008 R2 deployment, follow these
steps:

1. Upload the OEM device drivers

2. Modify the answer file

3. Edit the SSTKConfig.cmd file

deploy action 23

4. Edit the diskpart\default_layout_2008.txt file

Uploading OEM device drivers

Adding OEM drivers for Windows Server 2008 SP2 and Windows Server R2 installation in the
drivers repository folder is not necessary. The Windows Server 2008 SP2 and Windows Server
R2 setup uses the OEM drivers installed in the SSTK boot image. See “Installing OEM drivers in

the boot image” (page 13).

Modifying the answer file

To support unattended installations, the SSTK provides customized answer files for Windows Server
2008 SP2 and R2 in the os\unattended_files folder. You must edit the

os\unattended_files\2008-server-version\unattended.xml answer file (or
unattended-JP.xml for Japanese Windows Server 2008 SP2 and R2) and enter the

Administrator password, disk ID, and Product Key. If you want to PostInstall Smart Update Microsoft
QFEs Hot Fixes and ISP components, you must also enter the AutoLogon password; this must be
identical to the Administrator password.

TIP: For Windows Server 2008 SP2, enter the Product key into Windows PE pass and for

Windows Server 2008 R2, enter the Product Key into Specialize pass. For more information on
setting the unattended file, see the Microsoft AIK documentation.

You can use either a text editor or the Windows System Image Manager (WSIM) to edit the answer
file; you must validate it with WSIM. HP recommends that you use WSIM.

To open WSIM, click Program Files→Microsoft Windows AIK→Windows System Image Manager.
Then, click File→Open Answer File.

To select the Windows Server 2008 SP2 or R2 installation image, click File→Select Windows
Image.

In the SSTK, you can find the installation image in
os\windows\2008-server-version\sources\install.wim.

24 Configuring an SSTK action

Figure 10 Editing the Windows Server 2008 R2 answer file using WSIM

Figure 11 Adding Windows packages to the answer file using WSIM

For information about Windows Server 2008 SP2 and Windows Server 2008 R2 answer files
and WSIM, see the AIK User’s Guide. Click Program Files→Microsoft Windows
AIK→Documentation→Automated Windows Installation Kit User's Guide.

Editing the SSTKConfig.cmd file

The SSTKConfig.cmd file is located in the scripts folder, and is responsible for setting the
SSTK environment variables. You must set the following variables:

default_action Set to deploy. Directs the SSTK to perform a deploy action.

deploy action 25

os_deploy Set to the name of the folder in which the Windows installation files are

stored: 2008-server-sp2 or 2008-server-r2.

languageid By default, set to en. Specifies the Windows target language. For Japanese

Windows Server 2008 deployments, set this to jp.

Editing the default_layout_2008.txt file

The default_layout_2008.txt file is located in the scripts\diskpart folder. To make
changes to this file, follow these steps:

1. Run the hpshowdisk utility.

2. Search for the Disk ID you want.

3. Edit the file and modify the first line select disk X, where X is the Disk ID. By default, the
Disk ID is set to 0 (zero).

NOTE: This value must be the same as the value you specified for DiskID in the answer

file.

Replicating a server configuration

If you already have a server that you can use as a model to configure other servers, follow these
steps:

1. Save the model server configuration as follows:
a. Configure the readhwconf action in the SSTKConfig.cmd file.
b. Boot the model server with the boot image.

2. Apply this configuration and deploy the OS to as many servers as required as follows:
a. Configure the applyhwconf action in the SSTKConfig.cmd file.
b. Boot the target server with the boot image.
c. Configure the deploy action in the SSTKConfig.cmd file.
d. Invoke the SSTKStart.cmd script to deploy as follows:

X:\Windows\System32>SSTKStart.cmd

Alternatively, you can reboot the target Server.

26 Configuring an SSTK action

4 Booting the server

After configuring an SSTK action, you are ready to boot the target server. This chapter describes
how to boot the server (model and target), how to monitor the deployment process, and provides
some troubleshooting information.

Boot instructions

This section describes how to boot from the CD/DVD, USB device, and from the network

Booting from the CD/DVD

1. Insert the CD in the CD drive Integrity server.

2. Reboot the machine.

3. Enter the EFI Boot Manager and select the Internal Bootable DVD.

Boot from the USB flash device

1. Insert the USB flash device into an Integrity server.

2. From the EFI shell, enter reconnect –r to refresh the USB device discovery. The USB device
appears as a file system.

3. Enter the EFI Boot Manager menu, and select Boot Configuration (Figure 12).

4. Select Add Boot Option to add Removable Media Boot for the USB device.

Figure 12 Boot Configuration Selection Window

Booting from the network

To boot from the network, follow these steps:

1. Enter the EFI Boot Manager menu and select the appropriate Core LAN option.

2. If the menu option does not correspond to the network interface suitable for boot from network,
enter the EFI Boot Manager menu, and select Boot Configuration (Figure 12).

3. Select Add Boot Option to add a new LAN boot entry.

Alternatively, from the EFI Shell, enter lanboot select.

Boot instructions 27

SSTK log file

When the SSTK scripts run, SSTK records event messages and errors in a log file. Each time you
boot the target server, a new log file is created with the proper time stamp. SSTK creates a file
with the following name:

SystemName-SerialNumber-yyyymmdd-hhmmss.log

Where:

SystemName The system name.
SerialNumber The system serial number.
yyyymmdd The current date (yyyy = year, mm = month, and dd = day).
hhmmss The current time (hh = hour, mm = minute, and ss = second).

For example: server rx7640-USE46440SD-20080114153020.log.

Log file format

For each command executed by an SSTK script, the following entry is recorded in the log file:

[Thu 12/20/2007] [13:18:00.72] Initializing SSTK ...
[Thu 12/20/2007] [13:18:00.72] "Executing net use ..."
Return number: 0
Standard output:
Standard error:
[Thu 12/20/2007] [13:18:00.74] Setting SSTK environment variables
[Thu 12/20/2007] [13:18:00.76] PATH updated to
[y:\utilities\libs;X:\windows\system32;X:\windows;X:\windows\System32\Wbem]
[Thu 12/20/2007] [13:18:00.76] Initializing SSTK log system
[Thu 12/20/2007] [13:18:00.79] y:\utilities\hwdiscovery.exe -f x:\hwdisc.dat
"Executing hwdiscovery ..."
Return number: -1073740940
Standard output:
Standard error:
[Thu 12/20/2007] [13:18:05.10] Copying temporary log file to y:\data_files\logs\server
rx3600-USE0609KLB-gjkiyr-20071220-31805.log
[Thu 12/20/2007] [13:18:05.13] "Deploying Windows Server 2008 ..."
[Thu 12/20/2007] [13:18:05.15] y:\utilities\hpchkclm.exe -y –n
"Executing hpchkclm ..."
Return number: 0
Standard output:
HP server: rx3600
Threads supported per node: 16
Number of threads detected: 8
Processor architecture: ia64/itanium 2-core
Perf. counter frequency: 399MHz

Numa total memory available: 3GBytes
Node: Memory: Processors:
0 3GB 0, 1, 2, 3, 4, 5, 6, 7,

This system is not capable of NUMA.
Standard error:
[Thu 12/20/2007] [13:18:05.23] diskpart /s y:\scripts\diskpart\default_layout_2008.txt
"Executing diskpart ..."
Return number: 0
Standard output:

Microsoft DiskPart version 6.0.6001
Copyright (C) 1999-2007 Microsoft Corporation.
On computer: MININT-IPVEEKQ
.
.
.

When an SSTK action finishes with success the log system shows the following message:

Action action name Done.

NOTE: After WinPE boots, a temporary SSTK log file is created in the WinPE X:\sstktem.log

root folder. You can use this log file in case the remote share fails to mount.

Monitoring the Deployment

You can monitor the deployment remotely by connecting to the target server Integrated Lights-Out
(ILO) interface or to the HP Management Processor (MP), which enables you to see the server

28 Booting the server

console output. In order to access the server console, type the MP IP address in Internet Explorer
(for iLO interface) or in a telnet session or SSH client (for MP interface).

If you must force the target server to reboot, you can type restart at the WinPE SAC or use the
MP command line interface. To use the MP command line interface, follow these steps:

1. Connect to the target server through either telnet or SSH in order to access the MP. At any
time, type Ctrl+B to return to the MP.

2. Enter the command menu as follows:

servernameMP> CM

3. Reset the system. Enter:

servernameMP> RS

Monitoring the Deployment 29

5 Advanced topics

This chapter describes the following advanced topics:

• Customizing the SSTK boot image

• Enabling a boot device on a SAN

• Increasing security in SSTK

• Checking the CLM mode

• Enabling the maximum payload size

Customizing the SSTK boot image

The mkbootimg.cmd script executes all the steps needed to create a customized SSTK WinPE

3.0 image. The mkbootimg.cmd scripts steps are as follows:

1. Detect the AIK version installed on the system, if any, searching for dism or peimg tools. If
the system has AIK 1.1 installed, the script exits.

2. Verify other system requirements, for example, the presence of sstkmount.cmd and
SSTKStart.cmd files.

3. Mount a copy of the WAIK base image for modification.

4. Add the WinPE-WMI-Package (Windows Management Instrumentation support).

5. Install the Health driver.

6. Copy the SSTK bootstrap script and sstkmount folder to the mounted image folder.

7. Edit startnet.cmd to call SSTKStart.cmd on the WinPE boot.

8. Install the OEM drivers, if any, to the WinPE image.

9. Prepare the image, removing language packs and any other packages that are not needed
in the final image.

10. Finalize the new bootable SSTK WinPE image.

11. Replace the default boot.wim under the iso\sources directory with the new customized
image. The image file name must be boot.wim.

Enabling a boot device on a SAN

In a Storage Area Network (SAN) environment, a disk is uniquely identified by the HBA port
(WWID or WWPN), the Array port (BootDeviceWWID or WWN), and its Logical number
(BootDeviceLUN). Some disks connected through Emulex or Qlogic HBAs might not be available
at EFI. This requires an additional configuration step before installing Windows.

When the readhwconf action executes, the HBA configuration file is saved at data_files
folder. You must edit this file manually to enable the installation disk as a boot device. The following
is a sample HBA configuration file. in which the BootDeviceLUN=1 is set as the boot device
(SelectBootEnable=1).

HBA0]
WWID=10000000c969628a
HostAdapterBiosEnable=1
SelectBootEnable=1
BootDeviceWWID=500508b30090f5b1
BootDeviceLUN=1

[HBA1]
WWID=10000000c969628b
HostAdapterBiosEnable=0
SelectBootEnable=1
BootDeviceWWID=0000000000000000
BootDeviceLUN=0

30 Advanced topics

You can obtain the BootDeviceWWID and BootDeviceLUN information from the
hpacuscripting output, as follows:

; Controller Specifications
; Controller HP MSA1500 CS Controller
Controller= WWN 500508B30090F5B1

1

.
.
.
SSPState= Disabled
; Unassigned Parallel SCSI Drives
; 1:5 (36.4 GB),1:6 (36.4 GB)

; Array Specifications
Array= A
; Array Drive Type is Parallel SCSI
; 1:1 (72.8 GB),1:2 (72.8 GB),1:3 (72.8 GB)
Drive= 1:1,1:2,1:3
OnlineSpare= No

; Logical Drive Specifications
LogicalDrive= 1

2

RAID= 5
Size= 138927
Sectors= 32
StripeSize= 64
ArrayAccelerator= Enabled
; Available SSP Adapters 10000000C969628A (Local,Online),
10000000C969628B (Local,Offline), 10000000C9696304 (Unknown,Offline)
SSPAdaptersWithAccess= None

1

The BootDeviceWWID information

2

The LUN number.

After the applyhwconf action executes, the HBA configuration file is loaded; the device must be
available for booting.

To automatically set the boot device, see “sethbabootdevice action” (page 20).

Increasing security in SSTK

You can increase security in the SSTK by performing the following tasks:

• Encrypting the repository password

• Setting permissions for repository access

Encrypting the repository password

The sstkencrypt utility encrypts the repository password. It is a 32-bit command-line tool designed
to run on the repository system. To set the repository_encrypted_pass variable, run the
following command:

y:\>utilities\win32\sstkencrypt.exe
Type the repository password:
sstkserver
Set the encrypted password in SSTKStart.cmd script to:
a89ea897a9aa9ea298

In this case, set the following variables in the SSTKStart script:

repository_name=192.168.0.220
share_name=sstk_repository
repository_user=Administrator
rem repository_password=
repository_encrypted_pass=a89ea897a9aa9ea298

Increasing security in SSTK 31

repository_letter=y:

For information on valid characters for the repository password, see “Editing the SSTKStart.cmd

file” (page 12).

Setting permissions for repository access

To increase security, restrict write permission for some folders in the SSTK repository. This also
guarantees the integrity of files that must have read-only permission. The repository structure allows
users to have read-write permissions for the data_files folder only. Set all other folders to
read-only permission. Table 1 indicates the appropriate permissions for each SSTK repository
folder.

Table 1 SSTK Repository Permissions

PermissionsFolder

Read and executeboot

Read and writedata_files

Read and executeimages

Read and executeoem

Read and executeos

Read and executescripts

Read and executesoftware

Read and executeutilities

For additional information about sharing permissions and password configurations over a Windows
Network, see the following:

• How To Share Files and Folders over the Network in a Windows Server 2003 Domain

Environment at:

http://support.microsoft.com/kb/324267/EN-US

• How to Configure File Sharing in Windows XP at:
http://support.microsoft.com/kb/B304040

Checking the CLM mode

On mid-range and high end systems, the available system memory can be accessed using the
following methods:

Interleaved memory The average memory latency is constant for all processes in

the system.

Non-interleaved memory Also called cell local memory (CLM) or global non-interleaved

(GNI) memory. This provides lower memory latency for
processes running in the same cell as the memory. Microsoft
Windows has better performance when the memory is
configured with maximum CLM.

During a deploy action, SSTK checks if the memory is correctly configured using the hpchkclm
utility. If the configuration is not optimal, the utility writes the following message to the SSTK log
file:

"This system is NOT properly configured for Cell-Local Memory
mode. In order to obtain optimal system performance it is
recommended that you reconfigure the server."

32 Advanced topics

NOTE: SSTK does not provide a tool to configure Cell-Local Memory mode.

Enabling Max Payload Size

The Max Payload Size (MPS) enables or disables hardware optimizations to the installed operational
system. Enable MPS on the EFI Shell by using the following command:

EFI Shell> ioconfig mps_optimize on

This activates on the PcieMpsOptimization EFI variable. This optimization is implemented in
systems with firmware version 3.01 or greater. Windows Server 2008 can take advantage of the
MPS optimization feature.

Enabling Max Payload Size 33

6 Utilities reference

This chapter contains reference information and usage examples for the utilities provided in the
toolkit. You can get online help for each utility by using the -h or -? option.

conrep

Synopsis

conrep { -s | -l | -c | -d } [-F] [-v] [-f data file] [-x XML file] [-- ]
[--version ] [-h ]

Description

The conrep utility replicates the configuration data stored in the EFI variables. It reads the EFI
variables from the NVRAM of a server and writes the results to a data file. It also reads the data
file and writes the data into the NVRAM of the target server. The conrep utility uses the
conrep.xml configuration file to determine the data to retrieve from the server. You can edit this
file to control the data retrieval.

Options

-s | --read Reads the EFI environment variables from a server and saves

them to the specified data file.

-l | --write Loads the EFI environment variables from the specified data

file and writes them to the server.

-c | --clear Clears all boot entries related to the given partition.

-d | --delete Restores the EFI boot menu to factory defaults.

-F | --force Forces the creation of the new EFI variables listed in the

data file (conrep.dat).

-v | --verbose Specifies verbose execution.

-f data file | --dat data

file

Specifies the name and location of the data file. The default
is conrep.dat.

-x XML file | --config XML

file

Specifies the name and location of the XML definition file.
The default is conrep.xml.

--version Displays version information and exits.

-h | --help Displays usage information and exits.

34 Utilities reference

Examples

Example 1 Sample conrep.dat file

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<conrep_data>
<section name="EFI_general_variables">
<Lang>4c 00 61 00 6e 00 67 00 00 ...</Lang>
<Default>44 00 65 00 66 00 61 00 ...</Default>
<CPUThreadControl>43 00 50 00 55 00 54 ...</CPUThreadControl>
<Timeout>54 00 69 00 6d 00 ...</Timeout>
<ConOut>43 00 6f 00 6e 00 ...</ConOut>
<ConIn>43 00 6f 00 6e 00 49 ...</ConIn>
<ErrOut>45 00 72 00 72 00 ...</ErrOut>
<ConOutUserModified>43 00 6f 00 6e 00 ...</ConOutUserModified>
</section>
<section name="EFI_Non-Cell_variables">
</section>
</digest>39 b9 25 ad c7 d4 e8 0f 32 8e d9 05 94 05 a6 01 </digest>
</conrep>

Example 2 Sample conrep.xml file

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<conrep>
<section name="EFI_general_variables">
<ev>Lang</ev>
<ev>Default</ev>
<ev>UIOption</ev>
<ev>CPUThreadControl</ev>
<ev>Timeout</ev>
<ev>ConOut</ev>
<ev>ConIn</ev>
<ev>ErrOut</ev>
<ev>ConOutUserModified</ev>
</section>
<section name="EFI_Non-Cell_variables">
<ev>AutobootRetry</ev>
</section>
<section name="EFI_Cell_variables">
<ev>AutobootRetries</ev>
</section>
</conrep>

To read variables from the configuration file and write them to the conrep.dat file in verbose
mode, enter:

conrep -s -x conrep.xml -f y:\data_files\conrep.dat –v

To write the contents of the conrep.dat file to NVRAM in verbose mode, enter:

conrep –l –f y:\data_files\conrep.dat -v

Return codes

Table 2 conrep Return Codes

ActionCauseMeaningValue

conrep executed successfully0

Log in as an administrator and rerun
conrep.

The user does not have administrator
privileges.

Permission denied1

conrep 35

Table 2 conrep Return Codes (continued)

ActionCauseMeaningValue

Run conrep -h to display available
options and usage.

An error occurred while using
conrep for some unexpected
reason, such as the wrong
parameters.

Usage error2

Put the data file in the same directory as
the conrep executable or specify the
correct path with the -f option.

The data file was not found in the
current directory or in the path
specified with the -f option.

Data file not found3

Obtain another data file.The data file digest does not match
either because the file is missing
information or someone has modified
it.

The data file is corrupted4

There is an error in the Windows API or

the system hardware.

An error occurred when writing to
NVRAM.

Write variable error5

Put the configuration file in the same

directory as the conrep executable or

specify the correct path with the -x

option.

The configuration was not found in
the current directory or in the path
specified with the -x option.

Configuration file not found6

No action. This is only a warning

message.

At least one variable of the
configuration file was not found in
NVRAM.

Variable not found7

This might be an error in the Windows

API or in the system hardware.

An error occurred when reading a
variable from NVRAM.

Read variable operation error8

This might be an error in the Windows

API or in the system hardware.

An error occurred when deleting
(clearing the value of) a variable
from NVRAM.

Delete variable operation
error

9

Verify whether the XML file is well-formed

and there are no missing values.

A problem occurred while reading
an XML file.

XML parsing error11

No action. This error occurs if conrep

cannot allocate memory to calculate the

digest for the data file.

An error occurred when calculating
the hash (digest) for the data file.

Digest processing error12

An error occurred while writing data
to the data file.

Data writing error13

An error occurred while listing the
EFI variables.

Variables listing error14

An error occurred when converting
strings from Unicode to multibyte.

Unicode conversion error15

hpacuscripting

Synopsis

hpacuscripting [-c | -i] [-internal | -external] [-reset] filename

Description

The Array Configuration Utility (ACU) enables you to configure and manage your storage devices.
The ACU has several modes of execution.

For the SSTK, ACU runs from the command line in Scripting Mode. You can capture the current
configuration to a script file and use it as input to modify the configuration.

36 Utilities reference

Options

-c Captures the current configuration to a script file. The default file is
acuoutput.ini.

-i Inputs configuration information from a script file. The default file is acuinput.ini.

-internal Limits the operation to internal controllers. This is the default.

NOTE: Do not use this option to capture information about Storage Area Network

controllers.

-external Limits the operation to external controllers.

-reset Resets the controller configuration before applying another one.

Sample Script File

The following is a sample script file captured by ACU:

; Date captured: Wed Jan 23 09:33:09 2008
; Version: 8.0.6.0

Action = Configure
Method = Custom

; Controller Specifications
; Controller HP Smart Array 6400
Controller= IOCabinet 0,IOBay 1,IOChassis 3,Slot 10
ReadCache= 50
WriteCache= 50
RebuildPriority= Low
ExpandPriority= Low
SurfaceScanDelay= 15

; Array Specifications
Array= A
; Array Drive Type is Parallel SCSI
; 2:0 (36.4 GB),2:1 (36.4 GB),2:2 (36.4 GB)
Drive= 2:0,2:1,2:2
OnlineSpare= No

; Logical Drive Specifications
LogicalDrive= 1
RAID = 5
Size = 69455
Sectors = 32
StripeSize = 16
ArrayAccelerator = Enabled

; Controller Specifications
; Controller HP Smart Array P600
Controller= Slot 0
ReadCache= 50
WriteCache= 50
RebuildPriority= Low
ExpandPriority= Low
SurfaceScanDelay= 15

; Array Specifications
Array= A
; Array Drive Type is SAS
; 1E:1:1 (36 GB),1E:1:2 (36 GB),1E:1:3 (36 GB)
Drive= 1E:1:1,1E:1:2,1E:1:3
OnlineSpare= No
ReadCache= 50

hpacuscripting 37

WriteCache= 50
RebuildPriority= Low
ExpandPriority= Low
SurfaceScanDelay= 15

; Array Specifications
Array= A
; Array Drive Type is SAS
; 1E:1:1 (36 GB),1E:1:2 (36 GB),1E:1:3 (36 GB)
Drive= 1E:1:1,1E:1:2,1E:1:3
OnlineSpare= No

; Logical Drive Specifications
LogicalDrive= 1
RAID= 5
Size= 69399
Sectors= 32
StripeSize= 16
ArrayAccelerator= Enabled

Error reporting

When using the hpacuscripting utility, any errors are logged to the error.ini file. This file
displays the error code, error message, and if possible, lists the controller, array, or logical drive
associated with the error.

Error codes are also returned to the calling process, enabling scripting clients to use the return
code instead of parsing the error file.

The format of the error file is as follows:

ACU Configuration Replication Error
ERROR: (error code) error description
Controller: Slot # | SerialNumber # | WWN #
Array: #
Logical Drive: #

Table 3 hpacuscripting Warning Codes

ReasonMessage

Warning
Code

The input file specified a license key. However, a license key is
already installed on the controller.

License key is already
installed

4000

The -reset option was used on a controller that does not have
a configuration.

Clear configuration command
failed - configuration is
already cleared

4001

The chassis name is already set to the supplied value. The
command is ignored.

Chassis name is already set
to this value

4002

Certain commands require that the controller be configured before
they can be sent to the controller.

One or more controller
commands were skipped because
the controller is not
configured

4003

Some commands have been ignored because the Repeat
parameter has been specified in the input file.

Using Repeat function4004

38 Utilities reference

Table 4 hpacuscripting Error Codes

ReasonMessageWarning

Code

No error exists. The program completed successfully.—0

The new configuration requires more transformations than are
possible at one time. For example, you cannot expand a logical
volume and transform its RAID level at the same time.

Too many coinciding
expansion, migration, or
extension operations

2053

The controller does not support license key entry or deletion.Controller does not support

license keys

2056

The entered license key is not a valid license key.Invalid license key2059

The controller does not support SSP functions.Controller does not support

SSP

2064

The requested actions are invalid, for example, combining -reset
with capture mode.

Invalid action2817

The method must be either Custom or Auto.Invalid Method2818

The controller specified is not specified correctly.Controller '%s' is invalid2819

An invalid controller value was specified.Invalid Controller2819

No controllers were detected. This error applies to Input mode
only.

No controllers detected2821

The specified rebuild priority is not supported.Invalid Rebuild Priority2823

The specified expand priority is not supported. This error also
occurs if the controller does not allow expansion (does not support
Expand Priority).

Invalid Expand Priority2824

The array ID is invalid.Invalid Array2825

The Array command is missing from the script file. Some
commands were found that require an array to be specified.

Array not specified2826

The array ID in the script file does not match the array ID of the
next available array. For example, if the configuration has Array
A and the input file specifies Array C (without Array B), the script
generates this error.

New Array ID does not match
the next available Array ID

2827

When running in Configure mode, the array ID in the script file
already exists in the configuration. Configure mode can only
create new arrays.

New Array ID already exists2828

The controller does not allow a new array to be created. Possible
causes are there are no unassigned physical drives on the
controller or the maximum number of arrays or logical drives has
already been reached.

Cannot create Array2829

The array cannot be expanded. Possible causes are the controller
has no unassigned physical drives attached or the maximum
number of arrays or logical drives has been reached already.

Cannot expand Array2830

The spare state of the array cannot be changed. This can happen
when adding a spare or dropping a spare, and the current
configuration does not allow a spare state change for the array.

Cannot change Array Spare2831

The specified physical drive is not a valid physical drive, or it
cannot be placed in the array.

Invalid physical drive2832

The specified spare drive is not a valid spare drive, or it cannot
be placed on the array as a spare.

Invalid Spare2833

The logical drive ID is not valid.Invalid logical drive2834

hpacuscripting 39

Table 4 hpacuscripting Error Codes (continued)

ReasonMessageWarning

Code

The script file specifies a logical drive ID that is not the first unused
ID in the sequence. For example, if the controller has only Logical
Drive 1 and the script file attempts to create Logical Drive 3
(without Logical Drive 2), the script generates this error. This error
can occur when using an input file with logical drive numbers that
are not sequential. In this case, you must change the logical drive
numbers so that they are sequential in the input file.

New Logical Drive ID does
not match the next available
Logical Drive ID

If you are attempting to
replicate a configuration
that has non-consecutive
logical drive numbers, then
you must change the script
file so that the logical
drive numbers are
consecutive.

2836

When running in Configure mode, this error occurs when the
Logical Drive ID in the script file already exists in the configuration.
Configure mode can only create new logical drives.

New Logical Drive ID already
exists

2837

The array has no free space, or the maximum number of logical
drives has already been reached.

Cannot create Logical Drive2838

The controller does not support RAID migration, or the current
controller configuration does not allow migration to occur.

Cannot migrate Logical Drive
RAID

2839

The controller does not support extension, or the current controller
configuration cannot be extended. For example, extension is not
possible if the array has no free space.

Cannot extend Logical Drive2841

The specified RAID is invalid or is not possible with the current
physical disk and aarray configuration.

Invalid RAID2842

The specified size is invalid or is not possible with the current
configuration.

Invalid Size2843

The specified stripe size is invalid, not supported with the current
RAID level, or not supported with the current configuration.

Invalid Stripe Size2844

The valid parameters are Yes and No (default).Invalid

ClearConfigurationWithDataLoss
parameter

2849

The controller does not support setting a chassis name.Controller does not support

Chassis Name

2850

The entered chassis name is invalid. The chassis name can only
consist of the following characters: a-z, A-Z, 0-9, !, @, #, *, ( , )
, ,, - , _, +, :, ., /, and [space]. It cannot end with a space
character or exceed the maximum number of characters allowed
by the controller.

Invalid Chassis Name2851

The requested SSP state is not a valid SSP state.Invalid SSP State2852

The SSP settings cannot be changed for the controller or logical
drive.

Cannot change SSP settings2853

The adapter ID is not a valid adapter ID that was detected by the
controller.

Invalid SSP Adapter ID2854

—Invalid Surface Scan Delay2857

The controller is not redundant or does not support redundancy
settings.

Controller does not support
redundancy settings

2861

The preferred path mode specified is not a valid preferred path
mode, or the controller is not available.

Invalid Preferred Path Mode2864

40 Utilities reference

Table 4 hpacuscripting Error Codes (continued)

ReasonMessageWarning

Code

The preferred path specified is not a valid chassis slot for an
available active controller, or the controller is not available.

Invalid Preferred Path2865

—Failure opening capture file

text

2866

—Failure opening input file

text

2867

—Failure opening error file

text

2868

ACU found no drives that can be used as spares for the specified
array.

There are no suitable spares
available

2877

—Invalid Drive Type Specified2880

The specified value for MNP delay is invalid.Invalid MNP delay2882

The value of the option supplied to this parameter is invalid.Invalid Option3000

The controller returned an error for a command.Command Failed3002

ACU is unable to delete the license key.License Key Delete Failed3003

—Invalid Sector Size3004

—Cannot delete Array3005

—Invalid Number of Parity

Groups

3006

—Chassis name is too long3007

Another controller is already using the entered chassis name.Chassis name is already in

use

3008

The Auto Configure mode was unable to complete auto
configuration

Auto Configure failed3009

—Cannot extend logical drive,

not enough free space for
the requested size

3010

—Cannot extend logical drive,

requested size is too small

3011

The input file cannot specify both a SIZE and SHRINKSIZE
parameter.

Cannot specify both SIZE and
SHRINKSIZE

3012

The array shrink operation was not successful.Cannot shrink Array3013

The array move operation was not successful.Cannot move Array3014

The requested operation requires a valid license key to be entered.Invalid operation - Advanced

Pack support required

3015

When in Reconfigure mode, the requested spare drives must be
specified by their addresses. A simple count cannot be used.

Spare drives cannot be
specified by a count in
Reconfigure mode

3016

When in Reconfigure mode, the requested data drives must be
specified by their addresses. A simple count cannot be used.

Disk drives cannot be
specified by a count in
Reconfigure mode

3017

—Invalid number of physical

disks

3018

hpacuscripting 41

Table 4 hpacuscripting Error Codes (continued)

ReasonMessageWarning

Code

ACU cannot create an array unless physical disks are specified
in the input file DRIVE parameter.

Cannot create Array - no
physical disks specified

3019

For the specified operation, ACU requires SSP to be supported
and enabled.

SSP must be enabled in order
to perform this operation

3020

—Invalid connection name3021

—The connectionname cannot

be removed when the hostmode
has a nondefault value.

3022

—Invalid Host Mode3023

—Invalid Adapter ID3024

—This controller does not

have host mode modification
capability

3025

—You need to have

administrator rights to
continue.

3026

—Another instance of ACU is

already running (possibly a
service). Please terminate
the ACU application before
running ACU scripting.

3027

—Invalid Drive Cache setting.

Valid options are ENABLE and
DISABLE.

3028

Verify the ordering of the commands in the input configuration
file.

Invalid or out of order
Command

3029

Expecting a valid array in Reconfigure mode.Inavlid or missing Array for

Reconfigure

3030

hpchkclm

Synopsis

hpchkclm [-y] [-n]

Description

The hpchkclm utility is a command-line tool that checks for the Cell Local Memory mode on HP
Integrity server platforms. On mid-range and high end systems, the available system memory can
be accessed using two different methods:

Interleaved memory The average memory latency is constant for all processes in

the system.

Non-interleaved memory Provides lower memory latency for processes running in the

same cell as the memory.

For each cell, it is possible to determine the amount of memory that must not be interleaved. The
non-interleaved memory is known as cell local memory (CLM) or global non-interleaved (GNI)
memory. The amount of cell local memory can directly affect the system overall performance.
Running Windows, better performance can be obtained with maximum CLM.

42 Utilities reference

Options

-y Eliminates the press any key prompt for automation purposes.

-n Suppress the event logging feature.

Example

C:\>hpchkclm.exe –y –n
HPCHKCLM - HP NUMA Configuration Checker
Version 1.2.0.0, built May 18 2010 16:58:47

Manufacturer: hp
Product name: Integrity rx2800 i2
SKU: AH395A
BIOS version: 01.09
BIOS date: 10/18/2010
Computer name: MININT-8K9IQ46
Windows version: 6.1 Windows 7
Build: 7600
Processor: Itanium 2 4-core
Ident: ia64 Family 32 Model 2 Stepping 2
L1: 16KB I-Cache 4-way 64Byte
L1: 16KB D-Cache 4-way 64Byte
L2: 512KB I-Cache 8-way 128Byte
L2: 256KB D-Cache 8-way 128Byte
L3: 5MB Unified Cache 10-way 128Byte

Known core frequency: 1463MHz
Derived ITC frequency: 797.98MHz
ITC appears to be core frequency invariant.
NT perf counter frequency: 1.56MHz

Total logical threads: 8
Physical processors: 1
Cores per processor: 4
Threads per core: 2
Groups present: 1
Numa nodes present: 1
Numa memory available: 11.03GB
Total memory present: 11.90GB

Group Node Memory Processors
0 0 11.03GB 0:1 2:3 4:5 6:7 ;
Note: CPUs separated by colons denote processor thread groups.
Note: CPUs separated by semicolons denote processor core groups.

This system is not capable of NUMA.

hpshowdisk

Synopsis

hpshowdisk [[[-i index { -d | -s | -c | -w | -l }]] | -n | -V | -h]

Description

The hpshowdisk utility outputs a list of disks grouped by controllers along with their sizes, LUN,
and disk identifiers.

Options

-c Displays the controller WWID in 16-digit hexadecimal format.

-i index Selects a device using its index.

hpshowdisk 43

-d Outputs the PCI ID for the device in the
vendor:device:subvendor:subdevice format.

-l Displays the disk LUN.

-s Displays the size of the disk, in bytes.

-n | -no_showdisk Do not use the Altiris showdisk command to sort the disk list.

-v | --version Outputs the hpshowdisk utility version.

-w Displays the disk WWID in 16-digit hexadecimal format.

-h | --help Prints this help.

NOTE: The -w and -c do not run correctly if the hbaapi.dll file is not present in the utilities

directory under the SSTK repository tree. In order to obtain that DLL, see the following issue in
section 7 of the readme file:

"HPshowdisk utility and SetHBABootDevice action do not work properly
if hbaapi.dll is not present"

Examples

The following figure shows an example of hpshowdisk output in a system with 19 disks:

• 5 smart array disks (disks 15 to 19)

• 3 SAN disks through QLogic HBA cards (disks 9 to 11)

• 6 SAN disks through Emulex HBA cards (disks 3 to 8)

• 5 LSI disks through Emulex HBA cards (disks 1, 2, 12, 13 and 14)

>hpshowdisk.exe
LSI
SAS 1068 - sas1068
Disk ID 1: LUN 0 - 67.99 GB
Disk ID 2: LUN 0 - 67.99 GB

>hpshowdisk.exe -i 1 -d
1000:0054:103c:132c

>hpshowdisk.exe -i 2 -s
72999360000

>hpshowdisk.exe -n
LSI
SAS 1068 - sas1068
Disk ID 0: LUN 0 - 67.99 GB
Disk ID 1: LUN 0 - 67.99 GB

Return Codes

Table 5 hpshowdisk return codes

MeaningName

Return
Code

Success.SUCCESS0

Invalid options or invalid values were specified.ERROR_USAGE1

The specified disks are not in the machine.ERROR_NO_DISKS2

The utility cannot connect to WMI.ERROR_WMI_CONNECTION3

An error occurred while converting a string to a number.ERROR_STRING_CONVERSION4

No controller is listed by WMI.ERROR_NO_CONTROLLER5

No relationship between disks and controllers is listed by WMI.ERROR_NO_RELATION6

44 Utilities reference

Table 5 hpshowdisk return codes (continued)

MeaningName

Return
Code

The Altiris showdisk utility was not found.ERROR_NO_SHOWDISK7

An invalid disk index was specified with the –i option.ERROR_INVALID_DISK8

A problem occurred while invoking the Altiris showdisk utility.ERROR_INVOKING_SHOWDISK9

The utility tried to allocate memory and failed. For example, the system
memory is exhausted.

ERROR_NO_MEMORY10

hwdiscovery

Synopsis

hwdiscovery [-v | --version] [-f filename]

Description

The hwdiscovery utility captures the hardware configuration of a target machine and saves it
to an XML file. Captured information includes the following:

• System Name

• Serial Number

• Asset Tag

• EFI Firmware version

• BMC Firmware version

• MP Firmware version

• Number of Cells

• Total RAM size

• Number of Processors

• PCI devices present in the system

Depending on the system type (Mid-range and high end, Blade, or Virtual Machine), additional
information is captured. For PCI devices, hwdiscovery captures the following device path and
ID information:

• Bus

• Device

• Function

• Device ID

• Device Sub ID

NOTE: Segment or domain information is not necessary on Windows. All PCI devices use

Segment=0.

You can use the ifhw and hwquery utilities to perform queries on the hwdiscovery output. This
enables you to create conditional scripts for the Windows installation process.

Options

-f filename Specifies the output file name. If you do not specify a file name, the default
is hwdisc.dat.

hwdiscovery 45

-v | --version Displays the utility version.

Example

A sample hwdisc.dat output file is as follows:

<!-- generated by hwdiscovery Windows for IPF version 1.01 -->
<HWDiscovery version=”1.01”>
<ServerInformation>
<SystemName>Server rx2660</SystemName>
<SerialNumber>US43880166</SerialNumber>
<AssetTag>abcdef<AssetTag>
<EFIFw>5.48</EFIFw>
<BMCFw>04.03</BMCFw>
<MPFw>E.03.30</MPFw>
<Cells>0</Cells>
<VMHostIPAddress></VMHostIPAddress>
<Blade>
<RackName></RackName>
<EncName></EncName>
<EncModel></EncModel>
<EncMaxSlots></EncMaxSlots>
</Blade>
<Ram>12288</Ram>
<Processors>1</Processors>
<PCIDevices>
<PCIDevice num=”0”>
<Bus>0</Bus>
<Device>3</Device>
<Function>0</Function>
<Id>10024752</Id>
<SubID>0E11001E</SubID>
</PCIDevice>
<PCIDevice num=”1”>
<Bus>0</Bus>
<Device>4</Device>
<Function>0</Function>
<Id>0E11B203</Id>
<SubID>0E11B206</SubID>
</PCIDevice>
.
.
.
</PCIDevices>
</ServerInformation>
</HWDiscovery>

Error Codes

Table 6 hwdiscovery error codes

DescriptionValue

Success0

Invalid number of parameters1

Invalid parameter on the command line2

Missing library4

Error initializing IPMI5

Unknown system6

46 Utilities reference

Table 6 hwdiscovery error codes (continued)

DescriptionValue

Error creating XML file7

General error8

hwquery

Synopsis

hwquery hwdisc.dat allboards.xml [query]...

Description

The hwquery utility is executed from a script file, in conjunction with other utilities, to control the
install process. The hwquery utility uses data from the hardware discovery file in your own scripts.
The hwquery utility cannot alter environment variables directly. To set the variable, the hosting
script must use the output of hwquery. Typically, the script writes the output to an intermediate
script file that is subsequently called by the hosting script.

The hwquery utility returns a string to standard output in the following format:
set variable=XML tag value
You can redirect the output to a batch script to set the variable value.

Options

hwdisc.dat Specifies the hardware discovery XML output file.
allboards.xml Specifies the file that contains descriptions of all supported PCI devices.

query Specifies the query to perform on the hardware discovery file in the following

format:

variable=string

Where: string is case sensitive, and matches either a tag in the hardware
discovery output file or a description of a PCI device in the allboards.xml
file. If string contains spaces, enclose the string in quotation marks.

Examples

y:\utilities>hwquery y:\data_files\hwdisc.dat allboards.xml ARRAY_CTRL="Smart Array"
set ARRAY_CTRL=Smart Array 6402 Controller [A9890A]

ifhw

Synopsis

ifhw [path] [hwdiscfilename] [path] [allboards.xml] [expression]

Description

The ifhw utility is executed from a script file, in conjunction with other utilities, to control the install
process. The ifhw utility queries the hardware discovery file. Queries take the form of a logical
expression, and the result of the expression is returned as the exit status of the tool, which the
hosting script can use to conditionally perform actions.

Options

[path]hwdiscfilename Specifies the hardware discovery file to use to run the query.

hwquery 47

[path]allboards.xml Specifies the allboards.xml PCI device list file, which is used

to convert PCI IDs found in hardware discovery into device names,
such as “Smart Array 6402 Controller.”

expression Specifies the query expression.

Examples

The ifhw utility can use XML files as input to query the hardware discovery file. For example:

ifhw hwdisc.dat allboards.xml "PCI:Smart Array 6402"

• 0 (True) if the Smart Array 6402 is present

• 1 (False) if the device is not present

• 2 (Error) if the expression could not be understood

• -1 or 255 if incorrect number of parameters given

The following expressions used as shown in the Synopsis return the indicated result:

• “PCI:Smart Array 6402”

Returns True if the Smart Array 5i Controller is found in the system.

• HWQ:RAM gte 512

Returns True if the amount of RAM in the hardware discovery file is at least 512.

• HWQ:EFIFw neq “1.10”

Returns True if the EFI Firmware version in the hardware discovery file is not 1.10.

• HWQ:SystemName eq “Server rx4640”

Returns True if the system name in the hardware discovery file exactly matches Server
rx4640.

• “PCI:Smart Array 6402” or “PCI:Smart Array 6404”

Returns True if the system contains a Smart Array 6402 Controller or a Smart Array 6404
Controller

Table 7 ifhw Operators

ResultOperator or

term

True if both operands are true.and

True if either operand is true.or

True if the first operand is greater than the second.gt

True if the first operand is less than the second.lt

True if the first operand is greater than or equal to the second.gte

True if the first operand is less than or equal to the second.lte

True if the two operands are equal.eq

True if the two operands are not equal.neq

True if the operand is false.not

True if a PCI device whose name includes string is found in the hardware discovery file. string
is case-sensitive.

PCI:string

The hardware discovery file is searched for string, and the corresponding value is the value of this
term. string is case-sensitive.

HWQ:string

48 Utilities reference

Table 7 ifhw Operators (continued)

ResultOperator or

term

A literal string, used for comparison.string

A literal number, used for comparison.number

Return Codes

Table 8 ifhw return codes

DescriptionValue

The device is present.0 (True)

The device is not present.1 (False)

The expression was not understood.

1

2 (Error)

An incorrect number of parameters was specified.-1 or 255

1 Because of known issue TT1000754871, error code 2 is never returned. If an invalid expression is found, 1 is returned

instead. This will be fixed in a future release of the SSTK.

sethbaini

Synopsis

sethbaini [c_wwid] [wwid] [lun] [vendor] [hba_ini_file]

Description

When the sethbabootdevice SSTK action is called, the SetHbaBootDevice.cmd script uses the
sethbaini tool. The tool receives parameters generated by hpqlarep or hplpcfg that identify
a SAN disk, SAN vendor, and an hba_ini_file with HBA configurations. Then, it processes
and changes the hba_ini_file and sets the boot device to the specified disk.

Options

c_wwid Specifies the controller WWID retrieved by hpshowdisk.
wwid Specifies the disk WWID retrieved by hpshowdisk.
lun Specifies the LUN number retrieved by hpshowdisk.
vendor Specifies the SAN vendor. Valid values are emulex or qlogic.
hba_ini_file Specifies the path to the .INI file generated by the hpqlarep or hplpcfg

tools.

Example

The following is a sample command line:

sethbaini 10000000c9537540 500805f3000d91111 3 emulex %Path%\hba-emulex.ini

The following is a sample hba-emulex.ini file:

.
.
.
[HBAX]
WWID=10000000c9537540
SelectiveLogin=0
EnableSelectiveLUN=0
BootDeviceWWPN=500805f3000d91111

sethbaini 49

BootDeviceLUN=3
.
.
.

Return Codes

Table 9 sethbaini return codes

DescriptionValueReturn Code

The tool executed successfully.0SUCCESS

You specified an invalid option, or specified invalid values on the command
line.

1ERROR_USAGE

You specified a controller WWID that was not found in the specified file.2ERROR_INVALID_WWID

You specified an invalid controller name. Valid values are emulex or
qlogic.

3ERROR_INVALID_CTRL_NAME

You specified an invalid file path, or the file is not found.4ERROR_FILE_NOT_FOUND

The file was found, but it is not found in any [HBAx] section.5ERROR_INVALID_HBA_INI

sstkencrypt

Synopsis

sstkencrypt

Description

The sstkencrypt utility encrypts the repository password. After it is encrypted, sets the encrypted
password in the SSTKConfig.cmd file. This results in a more secure method of logging in to
remote machines over the network. For information repository password guidelines, see “Editing

the SSTKStart.cmd file” (page 12).

NOTE: The sstkencrypt utility runs on Windows 32-bit systems.

Example

C:\utilities\win32>sstkencrypt.exe
Type the repository password:

password

Set the encrypted password in SSTKConfig.cmd to:
a292a8a5aea3ab94

sstkmount

Synopsis

sstkmount [repository_letter] [\\repository_name\share_name]
[repository_encrypted_password] [/user:repository_user]

Description

The sstkmountt utility maps a remote share folder to a unit letter using the encrypted password
provided by sstkencrypt.

Parameters

repository_letter The letter to be assigned to the remote share folder.

50 Utilities reference

\\repository_name\share_name The address of the remote machine and the share folder

name.

repository_encrypted_password The encrypted password to the share folder obtained using

sstkencrypt.

repository_user The user name with which to log on to the remote machine.

Example

sstkmount z: \\192.168.0.3\sstk_repository a292a8a5aea3ab94 /user:Administrator

sstkmount z: \\remote\sstk_repository a292a8a5aea3ab94 /user:Administrator

sstkmount 51

7 Support and other resources

Contacting HP

For the name of the nearest HP authorized reseller:

In the United States, see the HP US service locator webpage at:

http://www.hp.com/service_locator

In other locations, see the Contact HP worldwide (in English) webpage at:

http://welcome.hp.com/country/us/en/wwcontact.html

For HP technical support:

In the United States, for contact options see the Contact HP United States webpage at:

http://welcome.hp.com/country/us/en/contact_us.html

To contact HP by phone:

Call 1-800-HP-INVENT (1-800-474-6836). This service is available 24 hours a day, 7 days a
week. For continuous quality improvement, calls may be recorded or monitored.

If you have purchased a Care Pack (service upgrade), call 1-800-633-3600. For more information
about Care Packs, see the HP website at http://www.hp.com.

In other locations, see the Contact HP worldwide (in English) webpage at:

http://welcome.hp.com/country/us/en/wwcontact.html

Documentation feedback

HP welcomes your feedback. To make comments and suggestions about product documentation,
send a message to http://www.hp.com/bizsupport/feedback/ww/webfeedback.html.

Include the document title and manufacturing part number. All submissions become the property
of HP.

Typographic conventions

This document uses the following typographical conventions:

Command A command name or qualified command phrase.
Computer output Text displayed by the computer.

Ctrl+x A key sequence. A sequence such as Ctrl+x indicates that you must hold

down the key labeled Ctrl while you press another key or mouse button.

File Name The name of a file name or path, for example, /os/windows.
Key The name of a keyboard key. Return and Enter both refer to the same

key.
Term The defined use of an important word or phrase.
User input Commands and other text that you type.
Variable The name of a placeholder in a command, function, or other syntax display

that you replace with an actual value.

52 Support and other resources

A Support Matrix

For a list of supported servers and components, see the Release Notes for Windows Server 2008
SP2 and Windows Server 2008 R2 SP1, available on Smart Setup CD ISO Image File for HP
Integrity Servers, in the contents\doc\en_us folder.

The Smart Setup CD ISO Image File for HP Integrity Servers is available at http://www.hp.com/

support/itaniumservers.

53