HP SmartStart Scripting Toolkit Windows Edition User Guide
Part Number 415598-006 January 2008 (Sixth Edition)
Copyright 2005, 2008 Hewlett-Packard Development Company, L.P. 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. 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 vendors standard commercial license. Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. Windows Server 2003 and Windows Server 2008 are trademarks of Microsoft Corporation. AMD is a trademark of Advanced Micro Devices, Inc.
Audience assumptions The Toolkit is designed for IT experts with experience in scripting operating system installations and configuring HP ProLiant server hardware.

Contents

Introduction..... 5
SmartStart Scripting Toolkit.... 5 Microsoft Windows Preinstallation Environment... 5 Minimum requirements.... 5 New features..... 6 Deployment overview.... 7 Sample deployment procedure.... 7 Creating a network share..... 8 Preparing the bootable media.... 9 Capturing a reference configuration from the source server... 11 Configuring the target server and installing the operating system.. 11 Overview..... 13 Customizing deployment scripts using HPDISCOVERY and IFHW... 13 Querying the HPDISCOVERY file based on system name... 13 Querying the HPDISCOVERY file to determine the presence of a particular card. 13 Querying the HPDISCOVERY file to determine the presence of a card family... 14 Performing an unattended operating system installation and adding mass storage drivers.. 14 Booting Windows PE from a USB drive key... 22 Flashing the ROM in a Windows PE environment... 23 Erasing array configurations.... 24 Adding drivers to Windows PE 2.0.... 25 Syntax conventions..... 26 Utility online help.... 27 Using system utilities..... 27 Using REBOOT..... 27 Using SETBOOTORDER.... 28 Using STATEMGR.... 29 Using RBSURESET.... 30 Using HPDISCOVERY.... 30 Using IFHW..... 31 Using HWQUERY.... 33 Using configuration utilities.... 34 Troubleshooting table.... 51
Deployment using the SmartStart Scripting Toolkit.... 7

Advanced topics.... 13

Toolkit utilities..... 26
Troubleshooting.... 51 Technical support.... 52
Reference documentation.... 52 Toolkit support..... 52 HP contact information..... 52
Acronyms and abbreviations.... 53

Index..... 56

Introduction
SmartStart Scripting Toolkit
The SmartStart Scripting Toolkit is a server deployment product that delivers an unattended automated installation for high-volume server deployments. This document describes how to best utilize the Toolkit to configure HP ProLiant servers. It also contains information about the Toolkit utilities and how to use them in an unattended environment. This document does not include information about installing the operating system. The Toolkit is designed for IT experts with experience in scripting operating system installations and configuring ProLiant server hardware. CAUTION: Improper use of the Toolkit utilities can result in loss of critical data. Because of the potential data-loss risk, only experienced individuals should use the Toolkit utilities. Before using the Toolkit, all necessary precautions must be taken to ensure that mission-critical systems remain online if a failure occurs.
Microsoft Windows Preinstallation Environment
Microsoft Windows Preinstallation Environment 2005 is a small footprint of the Microsoft Windows Server 2003 environment that replaces MS-DOS and enables you to run tools in a 32- or 64-bit Windows environment. Because Windows PE 2005 is based on the Windows Server 2003 SP1 kernel running in protected mode, only a subset of features and APIs are available in this environment. This document is applicable to Windows PE 2005 only. It is not backward compatible with previous versions of Windows PE. Windows PE enables you to install the Windows operating system, establish a connection with network servers, and perform hardware configuration using the SmartStart Scripting Toolkit. You can use Windows PE to customize and configure your servers before the operating system is installed. A bootable image of Windows PE is available from Microsoft through the Open Value program. You can also obtain tools, scripts, and documentation that enable you to create and customize your own Windows PE image. You are required to have the Microsoft Enterprise Agreement or Software Assurance Membership to gain access to the Windows PE Build Tools. For more information, refer to the Microsoft Windows PE website (http://www.microsoft.com/licensing/programs/sa/support/winpe.mspx).

Minimum requirements

This document is intended for IT personnel who are familiar with creating scripts, using a scripting language, creating bootable media, and performing unattended installations. Before beginning the deployment process, be sure to have the following items available:
SmartStart Scripting Toolkit Windows Edition
HP SmartStart Scripting Toolkit Windows Edition User Guide Microsoft Windows PE Build Tools 2005 (for the creation of Windows PE) The operating system to be deployed (Microsoft Windows 2000 or Microsoft Windows Server 2003, SP1)

New features

The SmartStart Scripting Toolkit 1.9 has the following new features:
Windows PE 2.1 supportDrivers can be added to WinPE 2.1 either offline or online. Windows 2008 supportCompatible with the Microsoft Windows Server 2008.
Deployment using the SmartStart Scripting Toolkit

Deployment overview

The SmartStart Scripting Toolkit includes a set of utilities for configuring and deploying servers in a customized, predictable, and unattended manner. These utilities enable you to duplicate the configuration of a source server on target servers with minimum user interaction. You can perform server deployments in many different ways using the Toolkit, but every deployment must include the following basic steps:

1. 2. 3. 4. 5.

Creating a network share Preparing the bootable media (CD/DVD, USB drive key, or PXE) Configuring the system and storage hardware on the target server Installing the operating system Updating drivers and agents as needed IMPORTANT: Not all options can be configured using Toolkit utilities. Some options must be configured manually or with other configuration utilities, which are available online, before they can be used with the Toolkit. See the option documentation for more information on configuration.
The utilities are provided in both 32- and 64-bit form: The 32-bit version of Microsoft Windows PE can be used with the 32-bit Toolkit utilities to deploy the x86-based version Microsoft Windows 2000 or Microsoft Windows Server 2003. The 64-bit version of Microsoft Windows PE can be used with the 64-bit Toolkit utilities to deploy the x64-based version of Microsoft Windows Server 2003.
Sample deployment procedure
The following procedure is a case study of a typical deployment. This procedure assumes that you are performing a CD-based installation and that you want to replicate an existing server configuration. The process described in this section can vary depending on your specific requirements. This section provides a simple overview of a basic deployment, but the flexibility of the SmartStart Scripting Toolkit enables you to do much more. With an understanding of the basic steps and your own deployment environment, you can use the Toolkit to further customize and automate the deployment process. For information on automating deployments, see the "Advanced topics (on page 13)" section of this document.

Deployment using the SmartStart Scripting Toolkit 7

Creating a network share

To create a network share:
Download the appropriate SmartStart Scripting Toolkit SoftPaq from the Toolkit website (http://www.hp.com/servers/sstoolkit). The Windows Toolkit is available in both 32- and 64-bit versions. Install the Toolkit SoftPaq on a common server that resides on the same network as the servers to be deployed. Share the folder in which you installed the Toolkit. Be sure that the account you use has read and write access. Create an empty directory called \DATA in the Toolkit folder for configuration files. Captured files will be stored in this directory.

2. 3. 4.

HP also recommends installing the latest version of the ProLiant Service Pack. To obtain the most current PSP, see the PSP website (http://www.hp.com/servers/psp).
Deployment using the SmartStart Scripting Toolkit 8
Preparing the bootable media
This section describes how to create a bootable CD by building and customizing a Windows PE base image. The following figure provides an overview of this process.
For detailed information about customizing a Windows PE base image, see the Windows PE documentation. The following table describes the directories and paths that you must define for the Windows PE base image build procedure. Directory or path
OptionalComponentsDirectory PathToOSFiles PathToWinPEFiles WinPEBuildTools WinPE_Directory

Description

Target directory in which the Windows optional components will be stored Path to the operating system CD or directory Path to the original Windows PE files Build location for the Windows PE tools Target directory in which the flat Windows PE image will be created
In the following examples, italicized text indicates user-defined variables.
Deployment using the SmartStart Scripting Toolkit 9
To build a Windows PE base image on the administrator workstation:
At the command console, set an environment variable for the platform. Set the variable to x86 for 32-bit systems and x64 for 64-bit systems. For example: set platform = x86 Copy the Windows PE Build Tools and files for the appropriate target server platform to a temporary directory:

a. Create the temporary build directory:

mkdir WinPEBuildTools

b. Copy the files to the temporary build directory:
xcopy /s /e PathToWinPEFiles\WinPE\*.* WinPEBuildTools At the prompt, press D to define WinPEBuildTools as a directory. xcopy /s /e PathToWinPEFiles\Tools\Platform\*.* WinPEBuildTools At the prompt, press Y to overwrite existing files.
Run the mkimg batch file to build the folder structure of Windows PE image with PnP and WMI support enabled (step A in the figure): cd WinPEBuildTools mkimg.cmd PathToOSFiles WinPE_Directory /PnP /WMI IMPORTANT: HP software requires that PnP and WMI support be enabled to function properly.
A message appears, indicating that you have successfully created the Windows PE image.
To help you customize the Windows PE image with HP ProLiant drivers, the Toolkit provides a driver component that automatically registers and copies the drivers to the appropriate folders (step B in the figure). To extract the component:
a. Double-click the self-extracting executable, which is located in the \toolkit\hpdrivers
directory of the network share you created previously.
b. Click Extract to extract all the files and drivers to the directory that is appropriate to your
environment: WinPE_Directory\i386 for 32-bit systems or WinPE_Directory\amd64 for 64-bit systems. IMPORTANT: HP ProLiant drivers must be added during Windows PE customization to ensure the Toolkit utilities function properly. The component uses drivers shipped with the SmartStart Scripting Toolkit to customize the Windows PE image. The component must be run after the Windows PE base image is built, but before other modifications are made to that image.
Modify the startnet.cmd file, located in the WinPEDirectory\i386\system32 directory or the WinPEDirectory\amd64\system32 directory, by adding the following line: net use s: \\server\share password /user:server\username where \server is the common server and \share is the network share you created previously.

For information on automated, unattended installation, see the following resources:
Deployment using the SmartStart Scripting Toolkit 12

Advanced topics

Overview
The advanced topics addressed in this section cover some of the most common deployment tasks that can be automated using the Toolkit. IMPORTANT: The script files and script segments in this section are provided only as examples. You must modify the scripts for your environment. When creating or modifying your own scripts, the pause command is a valuable tool to help you determine that each step of the script is functioning as desired.
Customizing deployment scripts using HPDISCOVERY and IFHW
The HPDISCOVERY utility enables you to determine which devices and capabilities are available in a particular ProLiant server. HPDISCOVERY generates an XML-based output file that provides information such as system ROM version, amount of RAM available, and the types of devices present in the system. Then, the HWQUERY and IFHW files can then be used to query the output file, enabling you to add conditional tests to a script so that it performs different operations based on the outcome of the tests.
Querying the HPDISCOVERY file based on system name
In the following script, the IFHW utility checks the HPDISCOVERY data in the hpdiscovery.xml file for the system name ProLiant BL20p. If the system name is found, the script calls the bl20p.cmd file. ifhw.\hpdiscovery.xml allboards.xml HWL:SystemName eq "ProLiant BL20p" if errorlevel 1 goto NEXT1 call.\BL20p.cmd goto end :NEXT1 ifhw.\hpdiscovery.xml allboards.xml HWL:SystemName eq "ProLiant DL380 G4" if errorlevel 1 goto NEXT2 call.\ DL380G4.cmd goto end
Querying the HPDISCOVERY file to determine the presence of a particular card
Using IFHW to detect a particular PCI card or device can be valuable in determining which settings to apply. For example, an array controller used as a boot controller might require a RAID 1 setting, while an optional array controller used for a database (such as a Smart Array 5312 Controller) might require a

Advanced topics 13

RAID 5 ADG setting. The following example demonstrates how to use IFHW to detect a particular card or device: REM *** Configure the array controllers by reading the configuration REM *** information in the script file and stamping it onto the array REM *** controllers of the target server echo Configuring the Array Controllers. ifhw.\hpdiscovery.xml allboards.xml PCI:"Smart Array 5i Controller" if errorlevel 1 GOTO NEXT1.\ACU\bin\cpqacuxe.exe -i.\ArraySettings\SA5iArray.ini :NEXT1 ifhw.\hpdiscovery.xml allboards.xml PCI:"Smart Array 6i Controller" if errorlevel 1 GOTO NEXT2.\ACU\bin\cpqacuxe.exe -i.\ArraySettings\SA6iArray.ini :NEXT2 \ifhw.\hpdiscovery.xml allboards.xml PCI:"Smart Array 5312" if errorlevel 1 GOTO NEXT3.\ACU\bin\cpqacuxe.exe -i.\ArraySettings\SA5312Array.ini :NEXT3

Querying the HPDISCOVERY file to determine the presence of a card family
IFHW and HWQUERY can perform queries based on partial name information, enabling you to verify the presence of a whole family of cards by using a partial query such as Smart Array. NEXT1: ifhw.\hpdiscovery.xml allboards.xml PCI:"Smart Array" if errorlevel 1 GOTO NEXT2.\ACU\bin\cpqacuxe.exe -i.\ArraySettings\GeneralArrayConfig.ini NEXT2: Before creating a test condition, refer to the allboards.xml file to determine the correct name for the device or group of devices you want to query. IMPORTANT: IFHW is case-sensitive. Incorrect case, misspellings, and incorrect spacing cause the query to fail.
Performing an unattended operating system installation and adding mass storage drivers
After the data files captured from the source servers are generated and modified for the target servers, modify and save a copy of the following script files to the appropriate location:
STARTDEPLOY.CMD SERVERDETECT.CMD DEPLOYSERVER.CMD UNATTEND.TXT

Advanced topics 14

See the operating system documentation for a complete description of the options that can be modified in the unattended installation file to customize the installation. To perform an unattended operating system installation and add mass-storage drivers:
Using a standard text editor, create or modify the following additional Toolkit files for the unattended install:
a. Edit the STARTDEPLOY.CMD file, which is executed by STARTNET.CMD in Windows PE, to
modify the environment variables to match the locations of the utilities and data files specific to your deployment infrastructure. You must customize this file for your environment. In the following example, lines in bold type indicate information that must be modified for your environment. The STARTDEPLOY.CMD file is similar to the following: rem @echo off REM REM This is the first Script called from Startnet.cmd stub in REM the WinPE REM REM Make sure that the network is fully started. REM Sometimes it requires a bit of time ipconfig REM Map a drive to the share you are working from net use s: \\server\share password /user: server\username REM If none ignore this step and set the drive letter in REM the following statements to appropriate drive REM============================================================ set Tools=s:\tkdemoarea\HP\Tools set MSTools=X:\i386\system32 set GlobalData=s:\tkdemoarea\HP\DeploymentScripts\datafiles set MSDistribution=s:\tkdemoarea\w2k3entsp1 set HPQFlatFiles=s:\tkdemoarea\hpqflatfiles set HPQComponents=s:\tkdemoarea\ntcsp set SystemScripts=s:\tkdemoarea\HP\DeploymentScripts REM============================================================ net start sysmgmt REM Call the first Script call %SystemScripts%\ServerDetect.cmd echo Done!

REBOOT command line examples

REBOOT A: REBOOT PXE

This command reboots the system to the A: drive. This command reboots the system by itself to the PXE NIC.

Using SETBOOTORDER

SETBOOTORDER enables you to set the order in which devices are booted, including diskette drives, CDROM drives, hard drives, PXE, and USB devices. This utility sets the boot order only for devices that exist for a server. The devices can be set to boot in any order. SETBOOTORDER cannot be used to set the storage controller order. You must use the CONREP utility. For more information about setting the controller order, see "Using CONREP (on page 35)." NOTE: Any changes you make to the SETBOOTORDER will take affect at the next reboot.
SETBOOTORDER command line syntax
setbootorder [floppy cdrom pxe hd usb | default] [/?]
SETBOOTORDER command line arguments
Options are disabled if not listed in the argument. Command line argument

floppy cdrom pxe hd usb

The order of these arguments sets the boot order for the system devices. Each term can be used only once in any order. It is not necessary to use all terms. This argument resets the boot order to the factory default. This argument displays help information.

default /?

SETBOOTORDER return codes
The boot order was set successfully.
SETBOOTORDER command line examples
SETBOOTORDER cdrom hd pxe usb floppy
This command sets the system devices to boot in this order: CD-ROM drive, hard drive, PXE, USB, diskette drive. This command sets the boot order to the factory default.

SETBOOTORDER default

Using STATEMGR
STATEMGR enables the user to keep track of the execution state during system reboots. This utility saves persistent state information across reboots of the system.
STATEMGR command line syntax
STATEMGR [/R | -R] [EVNAME] [/?] - or STATEMGR [/W | -W] [EVNAME] [VALUE] [/?]
STATEMGR command line arguments

/R or R

This argument reads the state of the environment variable defined by [EVNAME]. The value of the environment variable is returned as a return code. This argument writes the state defined by [VALUE] to an environment variable defined by [EVNAME]. This argument creates an environment variable used to represent the state to manage. The variable can be any word that is eight characters or less. This argument is used only with the /W or -W arguments to indicate the value of the environment variable to maintain. [VALUE] is limited to integers between 0 and 254. If no value is provided when using /W or -W, the state environment variable is cleared. This argument displays help information.

HPDISCOVERY return codes

0 1.255
The command was completed successfully. A usage message might appear. An error has occurred. See error message for details.
HPDISCOVERY command line examples
NOTE: Before running HPDISCOVERY, you must install WMI. For details on installing extra packages in Windows PE, see the Windows PE documentation. Command line argument Description
hpdiscovery /f x:\hpdiscovery.xml This command generates the hpdiscovery.xml file in the x:\ location. hpdiscovery /p plugin storage.dll This command only loads and executes the storage plug-in. hpdiscovery This command generates the hpdiscovery.xml file in the current directory.

Using IFHW

IFHW is used from a script file, in conjunction with other utilities, to control the deployment. The IFHW utility enables you to make intelligent queries against the hardware discovery file. Queries take the form of a logical expression, and the result of the expression is returned as the return code of the tool, which the hosting script can use to conditionally perform actions.

IFHW command line syntax

ifhw [drive:][path]hpdiscoveryfilename [drive:][path]allboards.xml <expression>
IFHW command line arguments
Command line argument Description
[drive:][path]hpdiscoveryfilename This argument specifies the hardware discovery file used to run the query. [drive:][path]allboards.xml This argument 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 5i Controller." This argument specifies the query expression. Refer to "Expression operators and terms (on page 32)."

<expression>

IFHW return codes
The expression is true. The expression is false. The expression was not understood, or an argument was invalid.
IFHW command line examples
ifhw hpdiscovery.xml allboards.xml "PCI:Smart Array 5i"
This command returns the following error levels:
ERRORLEVEL 0 (True) if the Smart Array 5i is present ERRORLEVEL 1 (False) if the device is not present ERRORLEVEL 2 (Error) if the expression could not be understood
Expression operators and terms

Operator or term

and or gt lt gte lte eq neq not PCI:<string>

Result

True if both operands are true True if either operand is true True if the first operand is greater than the second True if the first operand is less than the second True if the first operand is greater than or equal to the second True if the first operand is less than or equal to the second True if the two operands are equal True if the two operands are not equal True if the operand is false True if a PCI device whose name includes <string> is found in the hardware discovery file. <string> is case-sensitive.

CPQACUXE command file contents
A typical array configuration script file generated by CPQACUXE displays a script similar to the following: NOTE: An asterisk next to a line indicates that the line is not required in Automatic mode. ; Control Options Action = Configure Method = Custom ; Controller Options ; Controller Compaq Smart Array 5300 Controller = Slot 5 ClearConfigurationWithDataLoss = No LicenseKey = XXXXX-XXXXX-XXXXX-XXXXX-XXXXX DeleteLicenseKey = XXXXX-XXXXX-XXXXX-XXXXX-XXXXX RAIDArrayID = "XXXXXXXXXXXXXXXXXXXX" ReadCache = 50 WriteCache = 50 RebuildPriority = Low ExpandPriority = Low SurfaceScanDelay = N * SSPState = Disable ; Array Options * Array = A OnlineSpare = None * Drive = 2:0,2:1 ; Logical Drive Options * LogicalDrive = 1 RAID = 1 * Size = 17359 * Sectors = 32 * StripeSize = 256 * ArrayAccelerator = Enable * ResourceVolumeOwner = N * LogicalDriveSSPState = Disable * SSPAdaptersWithAccess = None ; HBA SSP Specifications * HBA_WW_ID = XXXXXXXXXXXXXXXX * ConnectionName = TestConn * HostMode = Windows
The data file used by CPQACUXE is a text file that contains options and parameters required to configure HP array controllers. The CPQACUXE utility parses the data file in a case-insensitive manner. Lines of the data file can be blank lines or lines in the form option = value. Semicolons are used for comments within data files, and CPQACUXE ignores everything after a semicolon up to the next line. The following options are valid in data files generated and read by CPQACUXE:
Control options define the overall behavior of CPQACUXE when it processes the scripts and creates configurations. Control options can occur only once in a data file and must be the first options listed. Controller options define the controller that is to be configured (or the controller that has had its configuration captured). The Controller option must be placed at the beginning of this section in the data file, but other options in this category can be scripted in any order. One data file can be used to configure several controllers if all controllers are to be configured identically or if each controller is defined separately. When defining each controller configuration separately, all other category options for a defined controller must be entered before starting a new controller listing. Array options define an array that is to be configured on the controller that is identified previously in the data file. If no controller is previously identified, CPQACUXE sends an error message. The Array option must be at the beginning of this section in the data file, but other options in this category can be scripted in any order. Logical drive options define a logical drive that is to be configured on an array that is defined previously in the data file. If no array is previously defined, CPQACUXE sends an error message. The LogicalDrive option must be placed at the beginning of this section in the data file, but other options in this category can be scripted in any order. HBA options define an HBA SSP configuration for a logical drive that is previously defined in the data file. If no logical drive is previously defined, CPQACUXE sends an error message. The HBA_WW_ID option must be at the beginning of this section in the data file, but other options in this category can be scripted in any order.

RAID This option specifies the RAID level for this logical drive.

0, 1, 4, 5, ADG

SIZE This option specifies the size of the logical volume in megabytes.
This value specifies the size of the logical drive in megabytes.

MAX (default)

This value specifies that all the remaining space on the array must be allocated to this logical drive. In Reconfigure mode, the default setting is the existing size of the logical drive. If you enter a larger value, CPQACUXE extends the logical drive to the new size if there is unused drive capacity on the same array, as long as the operating system supports logical drive extension. You cannot reduce the size of the logical drive. SECTORS (required) This option specifies the Max Boot setting (the number of sectors per track) to be used for this logical volume. 32, 63 Enter 32 to disable Max Boot. Enter 63 to enable Max Boot.
For new logical drives, the default setting is 32. For an existing logical drive, the default setting is the existing setting.
Logical drive performance is likely to decrease with Max Boot enabled.
STRIPESIZE This option specifies the stripe size of the logical drive in kilobytes. If the stripe size is not specified, the default based on the RAID level is chosen automatically. ARRAYACCELERATOR This option enables the array accelerator for this logical drive.

8, 16, 32, 64, 128, 256

RAID 0 and RAID 1 drives can use any of the listed stripe sizes. RAID 4, RAID 5, and RAID ADG drives are limited to 8, 16, 32, or 64. ENABLE (default)
Enables the array accelerator for this logical drive.

DISABLE

Disables the array accelerator for this logical drive. RESOURCEVOLUMEOWNER This option specifies the logical drive as the owner of a resource volume. LOGICALDRIVESSPSTATE This option is valid only for controllers that enable SSP on a logical drive basis. For other controllers that support SSP, see the SSPState command. N This value is the logical drive ID of an existing logical drive that owns the resource volume.

ENABLE DISABLE

This argument enables SSP for the logical drive. This argument disables SSP for the logical drive. For existing logical drives, the default setting is the current logical drive setting. For new logical drives, the default setting is Disable.
SSPADAPTERSWITHACCESS This option identifies the SSP adapters that have access to a logical drive.

Using HPONCFG

HP offers support for the RILOE II, iLO, and iLO 2 features available on ProLiant servers with the HPONCFG utility. HPONCFG is an online configuration tool used to set up and reconfigure RILOE II, iLO, and iLO 2 without requiring a reboot of the server operating system. The utility runs in a command line mode and must be executed from an operating system command line. HPONCFG enables you to initially configure features exposed through the RBSU or the RILOE II, iLO, or iLO 2 GUI. This utility is not intended for continued administration. CPQLOCFG should be used for ongoing administration of user rights and network functionality on the server. Observe the following requirements before using HPONCFG:
The RILOE II, iLO, or iLO 2 Management Interface Driver must be loaded on the server. HPONCFG displays a warning if the driver is not installed. HPONCFG requires minimum RILOE II, iLO, and iLO 2 firmware versions. To determine the minimum firmware version required, see the HP SmartStart Scripting Toolkit Linux and Windows Editions Support Matrix.
For more information, see the Remote Management website (http://www.hp.com/servers/lights-out).
HPONCFG command line syntax
hponcfg [-help][-?][-reset][-f filename][-l filename] [-w filename][-get_hostinfo][-m firmwarelevel] [-mouse | -mouse -dualcursor | -mouse -allusers] IMPORTANT: Because the -w argument does not capture certain types of information, such as the administrator password, data files created with HPONCFG using the -w argument cannot then be used as input files for HPONCFG, unless they are modified first.
HPONCFG command line arguments

-help or -?

These arguments display simple help messages.
-reset -f filename -l filename -w filename -get_hostinfo -m
This argument resets the RILOE II, iLO, or iLO 2 to factory defaults. This argument sets the RILOE II, iLO, or iLO 2 configuration based on the information in the XML input file named filename. This argument logs replies to the text log file named filename. This argument writes the RILOE II, iLO, or iLO 2 configuration obtained from the device to the XML output file named filename. This argument returns the host server name and serial number. This argument indicates to HPONCFG the minimum firmware level that must be present in the management device to execute the RIBCL script. If the minimum level is not met, HPONCFG returns an error without performing any additional actions. This argument causes HPONCFG to configure the server for optimized mouse handling.

-mouse

HPONCFG return codes
The script was sent successfully to the device, or there is no RILOE II, iLO, or iLO 2 present in the system. The script could not be sent to the device.
If the script itself fails, errors are reported in the log file created by HPONCFG.
HPONCFG command file contents

HPONCFG command line examples
For HPONCFG command line examples, see the appropriate user guide at the Remote Management website (http://www.hp.com/servers/lights-out).

Troubleshooting

Troubleshooting table

Data loss in Toolkit

Improper use of the Toolkit utilities and modification of the CONREP data files can result in loss of critical data. Because of the potential data-loss risk, only experienced individuals should use the Toolkit utilities. Before using the Toolkit, all necessary precautions must be taken to ensure that mission-critical systems remain online if a failure occurs. Not all options can be configured using Toolkit utilities. Some options must be configured manually or with other configuration utilities, which are available online, before they can be used with the Toolkit. See the option documentation for more information on configuration. Because the -w argument does not capture certain types of information, such as the administrator password, data files created with HPONCFG using the -w argument cannot then be used as input files for HPONCFG, unless they are modified first. The script files and script segments in this guide are provided only as examples. You must modify the scripts for your environment. When creating or modifying your own scripts, the pause command is a valuable tool to help you determine that each step of the script is functioning as desired. HP ProLiant drivers must be added during Windows PE customization to ensure the Toolkit utilities function properly. HP software requires that PnP and WMI support be enabled to function in Windows PE properly. IFHW is case-sensitive. Incorrect case, misspellings, and incorrect spacing cause the query to fail. The file format for the DOS version of CONREP and the current version of CONREP are not compatible. CPQACUXE supports only HP Smart Array controllers. Review the CPQACUXE documentation for the latest information. Booting from a USB drive key is supported only on certain ProLiant servers. For more information, see the ProLiant USB support website (http://h18004.www1.hp.com/products/servers/platforms/usb-support.html). The IFHW and HWQUERY utilities can be used to assist in customizing the DEPLOYSERVER.CMD script for your environment. For more information about these utilities, see the Toolkit utilities (on page 26) section. Any changes you make to the SETBOOTORDER will take affect at the next reboot.
Configuring options using Toolkit utilities
Input files for HPONCFG Sample script files
HP ProLiant drivers PnP and WMI support Non-functioning IFHW CONREP version compatibility CPQACUXE support Booting from a USB drive key Customizing the DEPLOYSERVER.CMD script SETBOOTORDER changes

Troubleshooting 51

Technical support

Reference documentation

For support software and drivers, see the HP software and drivers website (http://www.hp.com/support/files). For more information on the Toolkit, see the additional documentation found on the Toolkit website (http://www.hp.com/servers/sstoolkit). For more information on unattended installation, see the following resources:

HP StorageWorks SmartStart EVA Storage 3.1 release notes
Part number: T5505-96032 First edition: June 2009
Legal and notice information Copyright 2009 Hewlett-Packard Development Company, L.P. Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation.

Version:

Description
HP StorageWorks SmartStart EVA Storage is an application that helps you install software programs and drivers and configure an HP StorageWorks 4400 Enterprise Virtual Array (EVA4400) storage system. HP StorageWorks Command View EVA 9.1 is included in HP SmartStart EVA Storage 3.1. These release notes contain information specific to HP SmartStart EVA Storage 3.1. NOTE: For information about layered application support, see HP StorageWorks Command View EVA 9.1 release notes. These release notes are included in the 9.1 download, available on the HP Download drivers and software website: http://www.hp.com/support/downloads. Under Storage, click Storage Software, and then under Storage Device Management Software, click HP StorageWorks Command View EVA Software. Next, select HP StorageWorks Command View EVA V9.1 Media Kit, and then select your operating system.

Enhancements

This release includes: Updated HBA drivers Updated MPIO components New HP VDS Hardware Provider component

Product models

HP SmartStart EVA Storage is supported on EVA4400 storage systems.

Operating systems

HP SmartStart EVA Storage 3.1 is supported on Windows 2003 and Windows 2008 operating systems. For information about installing HP Command View EVA including prerequisites, see HP StorageWorks Command View EVA installation guide.

Important notes

This section identifies important notes and workarounds for your HP EVA4400 storage system and HP SmartStart EVA Storage.

Video tutorials

This version contains video tutorials that describe HP SmartStart EVA Storage concepts. The tutorials can be accessed from: Online helpRequires a Flash player and a 32-bit system (x86) GUIAvailable to run on all systems
Running tutorials from online help
The tutorials are located in the HP SmartStart EVA Storage online help under Contents > Whats new > Online help video tutorials.
Running tutorials from the GUI
The tutorials can be viewed from the HP SmartStart EVA Storage GUI main menu through the following three paths: Introduction to HP SmartStart EVA Storage > Video Tutorials HP EVA Storage Concepts > Video Tutorials FAQ > Video Tutorials
Provisioning storage errors with Windows 2003 SP1
Windows 2003 SP1 has limited functionality for LUN provisioning. If you have issues provisioning storage from HP SmartStart EVA Storage in a Fibre Channel configuration, upgrade your Windows 2003 server to SP2. Alternately, you can provision storage directly from HP Command View EVA and manually setting the new device as available to Windows.
Inconsistent behavior while trying to provision storage
After provisioning storage in Configure Fibre Channel application server, you are unable to provision storage. Verify the following: The array is managed by the HP Command View EVA management station you specified. Ensure that all arrays that HP Command View EVA can discover are managed by that instance of HP Command View EVA. The storage arrays are in an operational state.
Japanese virtual disk names
Virtual disk names cannot contain Japanese characters. If they do, errors occur while provisioning storage for Fibre Channel and iSCSI application servers.

Emulex 8 Gb/s HBAs require Windows hotfix
If the management server is running Microsoft Windows 2003 and has Emulex 8 Gb/s HBAs (HP part numbers AJ762A and AJ763A) installed, HP Command View EVA 8.x might not display any arrays.
To resolve this issue, you must install a Microsoft hotfix. Go to the following link for details and the hotfix download: http://support.microsoft.com/kb/945119 NOTE: If you are using the server for storage only, not as a management server, you do not need to install this hotfix.
No administrator rights error for member of Administrators group
HP SmartStart EVA Storage reports an error indicating that although the current user is a member of the Administrators group on the local machine, he does not have sufficient privileges to continue. For example: Your account does not have sufficient access to create the necessary credentials. Please login as an administrator and try again. This error occurs when the Microsoft User Account Control (UAC) security system seeks additional confirmations before a task is performed. UAC can prevent unauthorized changes to your computer by prompting you for permission when a task requires administrative rights, such as installing software or changing settings that affect other users. To resolve this issue: 1. 2. Log off the system. Do one of the following: Log in as an Administrator. Reset User Account Control: 1. Open User Accounts. 2. 3. 4. 5. Click Turn User Account Control on or off. If prompted, enter an administrator password or confirmation. Select the Use User Account control (UAC) to help protect your computer box to turn on UAC, or clear the box to turn off UAC. Click OK.
IMPORTANT: HP recommends that you not turn UAC off permanently. If you do turn it off, you must turn it back on as soon as possible.
Allow HP Command View EVA time to gather information after a reboot
When HP SmartStart EVA Storage initiates a server reboot, HP Command View EVA and HP SmartStart EVA Storage restart automatically. It is possible for you to advance through the HP SmartStart EVA Storage application dialog boxes before all configuration information is available. Be sure to wait a minute to allow HP Command View EVA to gather the requisite storage array information before
proceeding. Otherwise, you might need to return to the main menu and restart HP SmartStart EVA Storage.

Troubleshooting the HP VDS Hardware Provider installation
When using HP SmartStart EVA Storage to provision storage to your server, you may receive the following message: The HP VDS Hardware Provider may not be installed properly. If the installation of the VDS Hardware Provider was successful, verify the Fibre Channel switch zoning using the guidelines provided in the HP StorageWorks SAN design reference guide.
Running HP SmartStart EVA Storage from a network share
To run HP SmartStart EVA Storage from the Intranet or Internet network share, the Intranet zone security level must be set to Full Trust. Otherwise, the operation fails and A.NET Security Exception has occurred error message is displayed. To change the zone security level: 1. Select Control Panel > Administration Tools > Microsoft.NET 2.0 Framework Configuration to run the.Net Framework Configuration utility (mscorcfg.msc). A.NET configuration window opens. NOTE: This utility is not part of the.NET 2.0 Redistributable package. It is part of the.NET Framework Software Development Kit (SDK). You can download an SDK for your system from the Microsoft Download Center website: http://www.microsoft.com/downloads/browse.aspx?displaylang=en& productID=363FAD1D-FC68-461A-B459-BE5D41B521B2. 2. 3. 4. 5. 6. Navigate to Console Root >.NET Framework 2.0 Configuration > Runtime Security Policy. In the Tasks pane, click Adjust Zone Security. A Security Adjustment Wizard window opens Select Make changes to this computer, and then click Next. Select Local Intranet, move the trust level slider to Full Trust, and then click Next. Click Finish to exit the utility.

Javascript error message

After using HP SmartStart EVA Storage to install HP Command View EVA, a Javascript error messages can appear when you attempt to run HP Command View EVA. This can occur if your browser is not configured correctly. To avoid these error messages, ensure that your browser is configured as described in HP StorageWorks Command View EVA installation guide.
Format prompt on Windows 2008
After creating a Windows 2008 storage volume with HP SmartStart EVA Storage, a popup window appears, prompting you to format the drive associated with the storage volume.
However, HP SmartStart EVA Storage has already formatted the drive, therefore you can cancel this prompt. If you choose to format the drive, the operating system will format it.
Creating a storage volume results in an error
HP SmartStart EVA Storage can appear to hang when creating a storage volume, and then displays the following error: Storage volume creation and mounting was not successful. Reason: The storage volume you created has not been detected. (7007, blm_storage_volume_not_found) This error occurs when the host on which you attempted to create the storage volume cannot connect to the array through the fabric. Other management operations succeed because they use connections to HP Command View EVA over Ethernet. To resolve this situation, verify the zone configuration of the switch.

HP SmartStart ProLiant and HP SmartStart EVA Storage CDs
If you have an HP SmartStart ProLiant CD and an HP SmartStart EVA Storage CD, ensure that you install the HBA drivers from the HP SmartStart EVA Storage CD. Do not use the HBA drivers from the HP SmartStart ProLiant CD. However, if the management server is a ProLiant Storage Server, you must install specific HBA drivers separately using the HP SmartStart ProLiant CD. Use the HP SmartStart EVA Storage CD to install HP Command View EVA, but ignore the recommendations in the HBA Configuration page (click Next; do not update the drivers for the HBA in a ProLiant Storage Server from the HP SmartStart EVA Storage CD). NOTE: HP SmartStart EVA Storage does not support ProLiant servers running Microsoft Storage Server 2003.
javaw.exeUnable to locate component error
During HP Command View EVA installation, the following error message can appear: javaw.exe - Unable To Locate Component; This application has failed to start because WINSPOOL.DRV was not found. Re-installing the application may fix this problem. This error occurs when the HP Command View EVA installer attempts to create desktop icons for the applications that it installed. Because the error occurs after HP Command View EVA installed all applications, you do not need to reinstall the applications. To continue, click OK.
If the desktop shortcuts do not appear, you can create them manually. Common executable files and shortcuts are located as follows:
C:\Program Files\Hewlett-Packard\Sanworks\ Element Manager for StorageWorks HSV\ sssu.exe https://localhost:2372 C:\Program Files\Hewlett-Packard\EVA Performance Monitor\evaperf.exe
HP StorageWorks Storage System Scripting Utility
HP StorageWorks Command View EVA HP StorageWorks Command View EVAPerf