Regular firmware updates essential for optimal performance and functionality of hp proliant servers (9 pages)
Summary of Contents for HP ProLiant DL320e
Page 1
HP Scripting Toolkit for Linux User Guide Abstract This document provides information about the Scripting Toolkit for Linux utilities and how best to use the Scripting Toolkit for Linux to configure HP ProLiant servers and BladeSystem infrastructure in a Linux environment. This document is intended for IT experts with experience in scripting operating system installations and configuring HP ProLiant servers and BladeSystem infrastructure.
Contents 1 Introduction....................7 Scripting Toolkit........................7 Minimum requirements......................7 2 Deployment using the Scripting Toolkit............8 Deployment overview........................8 Sample deployment procedure....................8 Creating a network share......................9 Capturing a reference configuration from the source server............9 Creating an ISO image to be written to media...............10 Configuring the target server....................10 Installing the operating system.....................11 3 Booting and OS installation...............12 SYSLINUX..........................12...
1 Introduction Scripting Toolkit The Scripting Toolkit is a server deployment product for IT experts that delivers an unattended automated installation for high-volume server and BladeSystem infrastructure deployments. This document describes how to best use the Scripting Toolkit to configure HP ProLiant servers and BladeSystem infrastructure.
2 Deployment using the Scripting Toolkit Deployment overview The 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 minimal user interaction. IMPORTANT: HP ProLiant 100 series servers previous to Gen8 do not support all Scripting Toolkit commands.
Creating a network share To create a network share: Download the appropriate Scripting Toolkit package from the Scripting Toolkit website at http://www.hp.com/go/ProLiantSTK. Extract the package on a common server that resides on the same network as the servers to be deployed. Use the Linux NFS Server Configuration Tool to share the directory in which you extracted the Toolkit package and to assign read and write permissions for all hosts.
To add a new device driver name: modprobe f hpsa Load the channel interface driver for iLO: insmod /opt/hp/hp-ilo/bin/`uname -r`/hp_ilo.ko Mount the network share: mkdir /mnt/toolkit_share Capture a hardware discovery report using the HPDISCOVERY utility: cd /mnt/toolkit_share/utilities Capture the system BIOS configuration using the CONREP utility: cd /mnt/toolkit_share/utilities ./conrep -s -f/mnt/toolkit_share/data_files/conrep.dat 10.
At the boot prompt, type bash and then press Enter. When the process is complete, a command prompt appears. Load the network drivers using the loadnet script: /loadnet.sh Load appropriate storage controller drivers: modprobe -f cciss Load the channel interface driver for iLO: insmod /opt/hp/hp-ilo/bin/`uname -r`/hp_ilo.ko Mount the network share: mkdir /mnt/toolkit_share...
3 Booting and OS installation SYSLINUX SYSLINUX is a free third-party bootloader available on the SYSLINUX web page at http:// syslinux.zytor.com/index.php. SYSLINUX is a suite of programs that perform various boot functions. The Scripting Toolkit uses the following bootloader programs: isolinux.bin—Boot from ISO media.
Setting up a PXE boot environment requires the following general steps: Set up a DHCP server with the appropriate options. Set up a TFTP server with the appropriate options. Populate the TFTP directory share with the Scripting Toolkit boot components. These steps assume that a Linux workstation is used as the DHCP/TFTP server.
server = /usr/sbin/in.tftpd server_args = -s /tftpboot disable = yes per_source = 11 cps = 100 2 In this example, disabled is the default setting, and /tftpboot is the root directory for all client access. To enable the TFTP service on your server, edit the disable line to read: disable = no Populating the TFTP directory share Use the /tftpboot directory from the...
Booting from a USB drive key Some applications require the use of a writable medium. While booting from CD is not suitable for this purpose, a USB drive key provides the ideal medium as a writable medium. NOTE: Booting from a USB drive key is supported only on certain HP ProLiant servers. For more information, see the HP SPP website at http://www.hp.com/go/spp.
Page 16
The scripting for these steps must be adapted to your server deployment process. In particular, be sure to change the IP address and path of the NFS server to match your environment. You might also need to make other modifications, such as adding extra configuration steps (for instance, running HPONCFG to configure iLO) or additional servers.
Page 17
./ifhw ${HPDISCOVERY_FILE} allboards.xml "PCI:Smart Array 6i Controller" 2> /dev/null if [ $? = 0 ] ; then cd ${TOOLKIT}/hpacuscripting ./hpacuscripting -i ../data_files/dl380g4_sa6i_hpacuscripting.dat # Apply Array Configuration for Smart Array P600 Controller if present ./ifhw ${HPDISCOVERY_FILE} allboards.xml "PCI:Smart Array P600 Controller" 2> /dev/null if [ $? = 0 ] ;...
Page 18
echo "" echo "Rerun hardware discovery to find boot device" ./hpdiscovery -f ${HPDISCOVERY_FILE} ## use hwquery to fetch the boot dev node from hardware discovery file. if [ -z ${BOOTDEVNODE} ]; then export `./hwquery ${HPDISCOVERY_FILE} allboards.xml BOOTDEVNODE=DevNode` echo "Boot Device=${BOOTDEVNODE}" if [ -z ${BOOTDEVNODE} ];...
umount /mnt/dos umount ${NFS_MAIN} ## unmount everything else #umount -a #echo "Rebooting" #sleep 5 #/bin/reboot c: Microsoft Windows install_win.sh sample script The install_win.sh sample script performs many of the same hardware configuration tasks described in “Performing an unattended operating system installation” (page 15).
Page 21
authconfig autoconf automake yp-tools ypbind ypserv zlib zlib-devel %post The previous example contains a limited list of packages to be installed. Add to this section any other packages to be installed. The server deployment configuration and operating system installation process is complete. Performing an unattended operating system installation...
4 Scripting Toolkit utilities Native package formats The Scripting Toolkit utilities are available as standalone RPM and DEB packages. The Scripting Toolkit utilities are published to the HP Software Delivery Repository under the Extras directory at http://downloads.linux.hp.com/SDR/downloads/Extras. Get started at http://downloads.linux.hp.com/SDR/getting_started. Syntax conventions Syntax refers to the way a command and parameters must be entered.
Using Scripting Toolkit utilities The Scripting Toolkit utilities control the installation process, read the source server configuration, and duplicate the configuration on a target server through a generated script file. The Scripting Toolkit utilities include: REBOOT SETBOOTORDER (Limited functionality for HP ProLiant 100 series servers) STATEMGR (Utility is not supported on 100 series servers) RBSURESET BOOTEXTRACT...
REBOOT command-line examples Command-line argument Description This command reboots the system to the A: drive. REBOOT A: This command reboots the system by itself to the PXE NIC. REBOOT PXE Using SETBOOTORDER SETBOOTORDER enables you to set the order in which devices are booted, including diskette drives, CD-ROM drives, hard drives, PXE, and USB devices.
NOTE: The STATEMGR utility is not supported on 100 series servers. STATEMGR command-line syntax STATEMGR [/R | -R] [EVNAME] [/?] - or - STATEMGR [/W | -W] [EVNAME] [VALUE] [/?] STATEMGR command-line arguments Command-line argument Description This argument reads the state of the environment variable /R or –R defined by [EVNAME].
RBSURESET command-line syntax rbsureset [/?] RBSURESET command-line arguments Command-line argument Description This argument displays help information. [/?] RBSURESET return codes Value Meaning The BIOS settings have been successfully reset to the factory default. The BIOS settings have not been reset. Using BOOTEXTRACT BOOTEXTRACT is used to extract the boot sector files from Windows Server 2003.
Processor information NIC information PCI devices present in the system HP Smart Array controller information User process decisions can be made based on data that is in the file created by this utility. NOTE: Information may not be as detailed on HP ProLiant 100 series servers. HPDISCOVERY command-line syntax hpdiscovery [-f filename] [/?] HPDISCOVERY command-line arguments...
Command-line argument Description discovery into device names, such as "Smart Array 5i Controller." This argument specifies the query expression. See <expression> “Expression operators and terms” (page 28). IFHW return codes Value Meaning The expression is true. The expression is false. The expression was not understood or an argument was invalid.
Expression examples Expression input Result True if the Smart Array 5i Controller is found in the system "PCI:Smart Array 5i" True if the amount of RAM in the hardware discovery file HWQ:TotalRAM gte 512 is at least 512 True if the ROM date in the hardware discovery file is not HWQ:ROMDate neq 1 1/12/2004 "11/12/2004"...
HWQUERY command-line examples Command-line argument Description For a hpdiscovery.xml file that contains hwquery hpdiscovery.xml allboards.xml MY_SYS_RAM=TotalRAM <TotalRAM>768</TotalRAM>, HWQUERY produces the following: MY_SYS_RAM=768 For a hpdiscovery.xml file that indicates a Smart Array hwquery hpdiscovery.xml allboards.xml "TEST=Smart Array" 5i Controller is present, HWQUERY produces the following: TEST=Smart Array 5i Controller For a hpdiscovery.xml file that contains hwquery hpdiscovery.xml allboards.xml...
CONREP screen output A typical screen output generated by CONREP is similar to the following: conrep 3.00 3.10 - Scripting Toolkit Configuration Replication Program Copyright (c) 2007-2012 Hewlett-Packard Development Company, L.P. System Type: ProLiant DL360 G4 ROM Date: 08/16/2005 ROM Family: P52 XML System Configuration: conrep.xml...
To extract the BIOS settings from an SL160z G6 server and save the configuration to an "sl160zconrep.dat" data file: [root@ilo002481b08134 conrep]# ./conrep -s -xconrepSL160zg6_20090728.xml -fsl160zconrep.dat conrep 3.00 - Scripting Toolkit Configuration Replication Program Copyright (c) 2007-2012 Hewlett-Packard Development Company, L.P. System Type: ProLiant SL160z G6 ROM Date : 07/28/2009 ROM Family : O33 Processor Manufacturer : Intel XML System Configuration : conrep_SL160zg6_20090728.xml...
HPRCU command line arguments Command line argument Description This argument saves the system configuration to a file. This argument loads the system configuration from a file and writes it to the target server. Name of the input or output file. If not specified, the XML -f{file.xml} configuration defaults to hprcu.xml.
</hprcu> Using HPACUSCRIPTING Starting with version 8.28.13.0, ACU Scripting is now a standalone application that is distributed with the ACU CLI application. In ACU versions prior to 8.28.13.0, the scripting executable was provided with the ACU GUI component. For more information, see the Configuring Arrays on HP Smart Array Controllers Reference Guide on the HP website at http://www.hp.com/support/CASAC_RG_en.
Creating an ACU script file To create a valid ACU script file, use one of the following methods: Modify the sample custom input script (page 37). Create a Capture file for capturing a configuration (page 36). You can create a capture file from any server that has ACU loaded, and then modify the values of options in the file as necessary for the target system.
PreferredPathMode = Auto|Manual ; COMMENT: the following five entries are used to optimize the controller performance for video MNPDelay = 0|1|2|...|60 ; units are minutes, zero indicates disabled IRPEnable = Yes|No DPOEnable = Yes|No ElevatorSortEnable = Yes|No QueueDepth = 2|4|8|16|32|Auto Array = A|B|C|D|E|F|G|...Z|a|b|c|d|e|f OnlineSpare = None | N | Port:ID,Port:ID...
The options for each category are listed in the following table and described in more detail in the remainder of this section. Category Options Description Control Action Use these options to define the overall behavior of ACU when it processes scripts and creates configurations.
Action mode You must specify an Action mode: In Configure mode, you can create new arrays, but you cannot modify existing arrays. The controller must be connected to unassigned physical drives for this mode to be available. In Reconfigure mode, you can modify existing arrays. For example, you can set up an array expansion, a logical drive extension, or a migration.
ChassisName Enter the user-defined character string that identifies the controller. You can use any of the following characters in the string: a–z, A–Z, 0–9, !, @, #, *, (, ), ,, -, _, +, :, ., /, [space] You do not need to use quotation marks around the string, but doing so allows the string to begin with a space character.
Read:write ratio RA4x00 with 16MB RA4x00 with 48MB All other controllers All other controllers cache cache with battery-backed without write cache battery-backed write cache 70:30 – – 60:40 – – 50:50 – 40:60 – – – 30:70 – – – 25:75 –...
Array category The Array category has the following options: “Array” (page 43) “Drive” (page 43) “DriveType” (page 43) “OnlineSpare” (page 44) Array Enter a letter or pair of letters to identify the array you are creating or reconfiguring, and observe these additional limitations: In Configure mode, ACU creates a new array.
OnlineSpare The value for this option determines whether the array specified previously in the script will be configured with spare drives. Method mode Possible values Default value Custom To specify exactly which drives to use as spares, In Configure action mode: None. use the applicable convention (port:ID, box:bay, In Reconfigure action mode, ACU ignores any or port:box:bay).
The following defaults apply: For new logical drives, the default value is Disabled. For existing logical drives, the default value is the current logical drive setting. ParityGroups When you create a RAID 50 or RAID 60 configuration, you must also set the number of parity groups.
array, as long as the operating system supports logical drive extension. You cannot reduce the size of the logical drive. CAUTION: Back up all data before extending a logical drive. SSPAdaptersWithAccess Enter values here to identify the SSP adapters that you want to have access to a logical drive. The values are processed only if either SSPState or LogicalDriveSSPState is set to Enable.
The string can consist of the following: A maximum of 16 characters Embedded space characters but cannot end with a space character Any of the following characters: a–z, A–Z, 0–9, !, @, #, *, (, ), -, _, +, :, ., /, and [space] HBA_WW_ID This option specifies which HBA, based on its assigned WWN, is modified by the configuration changes.
Page 48
Error code Error message Comment or clarification between operations. Limit the number of such configuration changes in the script. 1091 Controller does not support SSP. — 1093 Controller requires physical drives to set — license keys. 1 102 Slot information is not available. You cannot run a script in Input mode on internal controllers that do not have slot information online.
Page 49
Error code Error message Comment or clarification 2831 Cannot change array spare. This error message appears if you try to change the number of spares in an array when the configuration does not support the addition or subtraction of spares. 2832 Invalid physical drive.
Page 50
Error code Error message Comment or clarification 2851 Invalid RAID Array ID. The scripted RAID Array ID is invalid. Use characters from the set a–z, A–Z, 0–9, !, @, #, *, (, ), ,, -, _, +, :, ., /, and [space].
Error code Error message Comment or clarification 2882 Invalid value for MNPDelay. Valid range — is 0 (disabled) to 60 minutes. 2883 Invalid controller configuration value. — Expecting Yes or No. 2884 Invalid value for QueueDepth. Valid range — is from 2 to 32, or Auto. Using HPLPCFG You must edit the text file to insert the WWID of the boot volume and the LUN number that the WWID boots from.
Value Meaning There was no adapter or Emulex HBA found on this host. There was an error retrieving the I/O address. The WWID was invalid because of one of the following: An invalid value for WWID and BootDeviceWWID, and not a hex value The WWID specified for HBA in the .ini file does not match any HBAs found on the host (for the /l option only) The LUN was invalid.
LO100CFG command-line arguments Command-line argument Description This argument displays example XML to perform configuration. This argument outputs the current copyright and version information and then exits. This argument captures the current status and outputs it to the console. The argument lists basic command line arguments and supported XML tags.
<serial_port mode="dedicated" /> <nic mode="dhcp"> <ipv4 address="10.10.10.18" mask="255.255.252.0" gateway="10.10.10.1" /> <firewall http_active="yes" ping_active="yes" telnet_active="yes" /> </nic> <users> <user id="1" name="" privilege_level="user" /> <user id="2" name="operator" privilege_level="operator" /> <user id="3" name="admin" privilege_level="admin" /> <user id="4" name="oem" privilege_level="oem" /> </users> </lo100cfg> To disable the shared NIC configuration and make the Lights-Out 100 NIC dedicated, enter the following in your data file: <lo100cfg>...
HPQLAREP return codes Value Meaning The command was completed successfully. There was an invalid command line option. There was a file open error. There was an NVRAM checksum error. There was an NVRAM data error. There was no adapter found on this host. There was an error retrieving the I/O address.
You must then invoke the tool to load the contents of hba.ini input to the HBA NVRAM: hpqlarep /l hba.ini. Using HPONCFG HP offers support for the iLO features available on HP ProLiant servers with the HPONCFG utility. HPONCFG is an online configuration tool used to set up and reconfigure iLO without requiring a reboot of the server operating system.
HPONCFG return codes Value Meaning The script was sent successfully to the device. The script could not be sent to the device. There is an error in xml. The Management processor is not present, or the driver is not running. The iLO flash is still in progress.
<DNS_NAME VALUE = "ILOD234KJ44D002"/> <PRIM_DNS_SERVER value = "16.16.1.161"/> <DHCP_ENABLE VALUE = "Y"/> <DOMAIN_NAME VALUE = "americas.cpqcorp.net"/> <DHCP_GATEWAY VALUE = "Y"/> <DHCP_DNS_SERVER VALUE = "Y"/> <DHCP_STATIC_ROUTE VALUE = "Y"/> <DHCP_WINS_SERVER VALUE = "Y"/> <REG_WINS_SERVER VALUE = "Y"/> <PRIM_WINS_SERVER value = "16.16.6.161"/> <STATIC_ROUTE_1 DEST = "0.0.0.0"...
<F8_PROMPT_ENABLED VALUE="Y"/> <REMOTE_CONSOLE_PORT_STATUS VALUE="3"/> <REMOTE_CONSOLE_ENCRYPTION VALUE="N"/> <PREFER_TERMINAL_SERVICES VALUE="N"/> <HTTPS_PORT VALUE="443"/> <HTTP_PORT VALUE="80"/> <REMOTE_CONSOLE_PORT VALUE="23"/> <TERMINAL_SERVICES_PORT VALUE="3389"/> <VIRTUAL_MEDIA_PORT VALUE="17988"/> <MIN_PASSWORD VALUE="4"/> </GET_GLOBAL_SETTINGS> Setting a configuration A specific configuration can be sent to the iLO by using the command format: HPONCFG /f add_user.xml /l log.txt In this example, the input file has the following contents: <!-- Add user with minimal privileges to test default setting of assigned privileges to 'N' -->...
5 Troubleshooting Troubleshooting table Issue Troubleshooting 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.
6 Support and other resources Information to collect before contacting HP Be sure to have the following information available before you contact HP: Software product name Hardware product model number Operating system type and version Applicable error message Third-party hardware or software Technical support registration number (if applicable) How to contact HP Use the following methods to contact HP technical support:...
Scripting Toolkit support E-mail support for the Scripting Toolkit is available from the HP support website at http:// h18013.www1.hp.com/products/servers/management/toolkit/smartsetup_E-support.html. Typographic conventions Table 1 Document conventions Convention Element Blue text: Table 1 (page 62) Cross-reference links and e-mail addresses Blue, underlined text: http://www.hp.com Website addresses Bold text...
Page 63
can be easily integrated to work with a supported version of HP Systems Insight Manager. HP Insight Remote Support 7.x provides anytime, anywhere personalized access to your IT environment through HP Insight Online, and is also the recommended version for HP Proactive Care Service.
7 Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.
Acronyms and abbreviations Array Configuration Utility BIOS Basic Input/Output System CONREP Configuration Replication utility CPQACUXE Array Configuration Utility XE CPQLOCFG Lights-Out Configuration Utility DHCP Dynamic Host Configuration Protocol disk operating system file allocation table graphical user interface host bus adapter HPDISCOVERY HP Discovery Utility HPONCFG...
Page 66
TFTP Trivial File Transfer Protocol universal serial bus vital product data Wake-on LAN WWID World Wide ID World Wide Name WWPN worldwide port name extensible markup language Acronyms and abbreviations...
Page 67
Index acronyms and abbreviations, hardware ACU script file, configuration, anaconda-ks.cfg HPACUSCRIPTING, sample file, ACU script file, ACU scripting errors, configuration, BOOTEXTRACT, input script, arguments, sample input script, command-line syntax, script file options, return codes, array category, control category, controller category, clearing a configuration, HBA category, configuration...