HP Integrity rx1600 Deployment Manual

Smartsetup scripting toolkit deployment guide: hp integrity servers with linux
Hide thumbs Also See for Integrity rx1600:
Table of Contents

Advertisement

SmartSetup Scripting Toolkit Deployment
Guide
HP Integrity Servers with Linux
HP Part Number: 5991-6250
Published: July 2009
Edition: 8

Advertisement

Table of Contents
loading

Summary of Contents for HP Integrity rx1600

  • Page 1 SmartSetup Scripting Toolkit Deployment Guide HP Integrity Servers with Linux HP Part Number: 5991-6250 Published: July 2009 Edition: 8...
  • Page 2 © Copyright 2007–2009 Hewlett-Packard Development Company, L.P Legal Notice 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.
  • Page 3: Table Of Contents

    Table of Contents Preface..........................9 Intended Audience..........................9 Typographic Conventions........................9 Publishing History..........................11 Related Information..........................12 HP Encourages Your Comments......................12 1 Overview........................13 Introduction............................13 Reviewing the Toolkit...........................14 Planning the Deployment........................15 Selecting a Workstation........................15 Selecting a Boot Mechanism......................15 Configuring the Repository......................16 Using Repository Creation Scripts.....................16 2 Using the SSTK Deployment Workflow..............21 Setting Up a Model Server........................21 Creating a Server Profile........................21 Setting Up the Toolkit Environment.....................22...
  • Page 4 5 Setting Up the Boot Mechanism.................39 Using a Bootable CD or DVD.......................39 Creating a Bootable Disk Image......................39 Creating a CD Build Directory......................40 Creating the ISO File........................40 Booting From the CD or DVD......................40 Using a USB Flash Device........................41 Creating a Bootable USB Flash Device....................41 Booting From a USB Flash Device....................41 Using a USB Flash Device as External Media.................43 Using Network Boot..........................43...
  • Page 5 hpia64info............................71 Synopsis............................71 Description............................71 Output..............................71 hplpcfg...............................71 Synopsis............................71 Description............................72 Format............................72 Examples............................72 hpqlarep.............................72 Synopsis............................72 Description............................72 Format............................72 hpsetacpi............................73 Synopsis............................73 Description............................73 Examples............................73 hpshowdisk............................73 Synopsis............................73 Description............................73 Examples............................74 hwdisc..............................74 Synopsis............................74 Description............................75 Example............................75 hwquery...............................77 Synopsis............................77 Description............................77 Examples............................77 ifhw..............................78 Synopsis............................78 Description............................78 Examples............................78 parted..............................79 Synopsis............................79 Description............................79 Examples............................79 A Known Issues........................83 Pre-OS Linux Prompts Are Not Displayed...................83 Potential RHEL Deployment Errors.....................83 Installing RHEL4U4 with Disks Without Partition Tables..............83...
  • Page 6 List of Tables SSTK Variables..........................33 SSTK Configuration Variables.......................34 Global Options..........................34 Image Options..........................35 SSTK Command Line Options......................35 The mkisofs Command Options....................40 cfggen Commands........................47 CLMChecking Options ........................49 conrep Options ...........................50 conrep Return Codes ........................51 cpqacuxe Options ........................53 Automatic Script File Options.......................54 Custom Script File Options......................57 Error Codes............................63 efibootmgr Options........................67 6-10...
  • Page 7 List of Examples cfggen list Command......................48 cfggen Display Command......................48 Sample conrep.dat file......................50 Sample conrep.xml File......................50 Sample hpia64imfo Utility Output....................71...
  • Page 9: Preface

    Preface This document provides instructions for configuring and using the SmartSetup Scripting Toolkit (SSTK) on HP Integrity servers running Linux. As of this publication, SSTK is supported on the following Linux distributions: • Red Hat Enterprise Linux (RHEL) □ RHEL4U4 (Backward compatible only □...
  • Page 10 The contents are required in formats and command descriptions. If the contents are a list separated by |, you must choose one of the items. The preceding element can be repeated an arbitrary number of times. Separates items in a list of choices.
  • Page 11: Publishing History

    Publishing History The document publishing date and part number indicate the current edition of the document. The publishing date changes when a new edition is printed. Minor changes might be made at reprint without changing the publishing date. The document part number changes when extensive changes are made.
  • Page 12: Related Information

    Manufacturing Supported OS Supported Versions Edition Publication Date Part Number Number 5991-6250 Red Hat Enterprise Linux (RHEL) RHEL4U4, and RHEL4U5 January 2007 SUSE Linux Enterprise Server (SLES) SLES9SP3 5991-6250 Red Hat Enterprise Linux (RHEL) RHEL4U4, and RHEL4U5 November 2006 SUSE Linux Enterprise Server (SLES) SLES9SP3 No testing occurs on older updates or service packs though every effort is made to maintain backward compatibility.
  • Page 13: Overview

    1 Overview The HP SmartSetup Scripting Toolkit (SSTK) enables you to deploy a large number of HP Integrity servers rapidly and efficiently. Using SSTK, you can develop custom scripts that simplify server deployments by automating various hardware configuration and software installation operations. SSTK can set specific Extensible Firmware Interface (EFI) boot variables, create disk partitions, and tie into the standard unattended installation process to install the OS and selected applications.
  • Page 14: Reviewing The Toolkit

    process to apply the server profile to a target server. Finally, you launch this process to replicate the server profile on hundreds of servers. SSTK is not an automated server deployment solution for everyone. The SSTK is an extensible framework for developing hardware configuration and software installation scripts. The SSTK is designed for administrators who have some expertise in unattended installations of RHEL or SLES and familiarity with HP Integrity servers.
  • Page 15: Planning The Deployment

    • The SSTK boot device is a CD, a network share, or a USB flash device—holds files that allow servers to boot to the toolkit environment. You can also use the SSTK boot device to hold the repository of scripts, utilities, configuration files, OS files, and application files. •...
  • Page 16: Configuring The Repository

    Configuring the 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. The Linux boot loader configuration file, which must be manually edited as described in Chapter 4 (page 33), specifies the default location of the repository.
  • Page 17 # ./mkrep.sh The SSTK Repository Maker Linux distribution selection menu is displayed. Select the appropriate Linux distribution, and then select OK. An SSTK Repository Maker menu similar to the following is displayed. The Repository Maker main menu provides the three tasks required to create your repository. Default configurations are provided for the destination directory and CD mount points that can be used to immediately create the repository with the Make Repository selection.
  • Page 18 Select your CD/DVD device by navigating to the correct directory, and then click OK. Select Make Repository and click OK. The script creates the necessary directories, files, and symbolic links. You are prompted to insert the OS distribution media, in order, during this process; an error occurs if the expected media is not inserted.
  • Page 19 To exit the script, select Exit and click OK. The repository structure created in the /repository/SSTKLnx3.3 directory is as follows: SSTKLnx3.3/ |-- SSTK_DeploymentGuide.pdf |-- SSTK_DeploymentGuide.txt |-- boot_files `-- efi `-- boot |-- bootia64.conf |-- bootia64.efi |-- elilo.conf |-- elilo.efi |-- linux `-- rootfs.gz |-- data_files |-- os...
  • Page 20 |-- bld |-- acu.xml |-- ipcelmclient |-- ipcelmclient.php |-- libLLPI.so |-- libcpqhmmo.so |-- libcpqimgr.so |-- libhwmim3.so |-- libossingleton.so |-- locks `-- upgrade.txt |-- cpqacuxe `-- cpqacuxe.license |-- dumppci -- efivar |-- gen-setupldr-options |-- getuuid |-- hpacucli |-- bld |-- hpacucli |-- hpacucli.license |--libhwmim3.so |-- hpacucli-8.25-5.ia64.txt...
  • Page 21: Using The Sstk Deployment Workflow

    2 Using the SSTK Deployment Workflow Server deployments using SSTK involve four main stages. This chapter provides a high level overview of the deployment workflow including the following topics: • “Setting Up a Model Server” (page 21) • “Creating a Server Profile” (page 21) •...
  • Page 22: Setting Up The Toolkit Environment

    Setting Up the Toolkit Environment Setting up the toolkit environment involves the following tasks: Set up the toolkit launch: Setting up the toolkit launch involves editing a script and a configuration file that control the toolkit. The EFI loader launches the Linux boot loader, which executes a bootstrap script in the root file system.
  • Page 23: Capturing Images

    Capturing Images To capture one image, use the following steps: Ensure that the source computer is booted and running SSTK. Edit the sstk.conf file on the repository, and then change the value of IMAGE_FILE variable to the name you want created as a result of this capture operation. The default value for IMAGE_FILE is linux.img.
  • Page 24: San Environment Autoconfiguration

    Edit the sstk.conf file on the repository, and then change the value of RHEL_PROFILE as appropriate by choosing one of the following: — rhel4up6-upgrade-profile for an RHEL 4.6 upgrade — rhel5up1-upgrade-profile for an RHEL 5.1 upgrade Select [2] upgrade (install Linux). Select the target RHEL version, 4.6 or 5.1.
  • Page 25: Logical Volume Manager Support

    Boot the system with the RHEL5 or RHEL5UP1 replicated image in single mode by entering the following at the boot prompt: linux single From the root directory, recursively restore all SELinux configuration files by entering: restorecon -r / The SELinux security policy configuration is closed by default when installing RHEL5U2 using SSTK so this situation does not exist when replicating this release and the correct SELinux extended attributes are in place.
  • Page 27: Creating A Server Profile

    3 Creating a Server Profile A server profile is like the DNA of all the servers in the deployment. It includes the server EFI environment variables, the I/O configuration, the OS and drivers, and installed applications. The server profile is stored in the repository. This chapter describes how to create the server profile. Because you need to perform this task on the workstation using the SSTK, you begin by setting up this workspace.
  • Page 28 Select Error Console. Set the error console to the same as the output console device. Or, at the HP Integrity server (the model server and each target server) using the Legacy interface, perform the following steps: Select EFI Boot Manager > Boot Option Maintenance Menu. Select Select Active Console Input Devices.
  • Page 29: Unpacking The Toolkit

    Unpacking the Toolkit The SSTK software package is an archive that is provided in tar gzip file format. The archive expands into a file structure that also serves as a skeleton for the server profile: • Documentation includes this guide and a readme file with any breaking release information. •...
  • Page 30 and is installed after the OS is first loaded. Files placed under software\EFI_TOOLS are automatically copied to the HP Service Partition. • The os directory contains unattended configuration files for the Linux distributions. The Linux distribution installation files are also placed in the linux directory as follows: |-- os |-- linux |-- rhel4up4...
  • Page 31 This script edits the configuration in the RHEL rhel-setup.sh unattended configuration file and copies the RHEL boot image files to the ESP partition. This script edits the configuration in the SLES sles-setup.sh unattended configuration file, and copies the SLES boot image files to the ESP partition. •...
  • Page 32: Setting Up An Unattended Os Installation

    The parted utility, which creates, destroys, resizes, checks, and copies parted partitions. The acpi mode configuration tool, used to check and modify the acpi hpsetacpi mode on cellular machines. NOTE: The dumppci and gen-setupldr-options utilities are delivered though are not used by SSTK.
  • Page 33: Setting Up The Toolkit Environment

    4 Setting Up the Toolkit Environment Setting up the toolkit environment involves editing scripts that control the boot and operation of the toolkit. The EFI loader launches the Linux boot loader, which in turn executes a bootstrap script in the root file system. The bootstrap script invokes the main toolkit launch script, which uses a Linux setup script to trigger the OS installation.
  • Page 34: Editing The Linux Boot Loader

    Table 4-1 SSTK Variables (continued) Variable Name Description Sets the name of the Linux image file. IMAGE_FILE="" The default value is linux.img. Sets the log level. Set 1 for normal logging or zero (0 ) for extended logging. LOG_LEVEL=0 The default value is zero. Defines the ESP partition size.
  • Page 35: Image Options

    Table 4-3 Global Options (continued) Global Option Description Specifies the number of tenths of seconds to wait before autobooting when not delay=number in interactive mode. Default is 0. Forces interactive mode. prompt Sets level of verbosity [0–5]. Default is 0 (no verbosity). verbose=number Sets global root filesystem for Linux/ia64.
  • Page 36 Table 4-5 SSTK Command Line Options (continued) SSTK Option Description Specifies the network share or device that hosts the repository: ssstk_mount=filename nfs—[hostname|IP]:/directory USB—/dev/devicename Passes extra parameters to the mount command. ssstk_mount_options=string Specifies the name of main launch script. ssstk_script=filename Specifies the default response to the toolkit launch script prompt (readhwconfig, ssstk_action=string bash, capture, deploy, or linux).
  • Page 37: Reviewing The Main_Toolkit_Launch.sh Script

    ssstk_init=/bootstrap ssstk_mount=/dev/sda1 ssstk_script=scripts/main_toolkit_launch.sh ssstk_action=linux" NOTE: During the pre-boot portion of the Linux booting sequence, you may encounter a syntax error in each line of the script, which may indicate that there are extra line-feed characters in the boot loader file. If you modify the elilo.conf file using a Windows-based text editors, you must ensure that the modified script files are UNIX file format by using a utility to convert the script files to UNIX format (such as dos2unix) or by saving the file in UNIX file format.
  • Page 38: Setting Repository Access Permissions

    The script performs the following operations: Creates four partitions: EFI System Partition (ESP), HP Service Partition (HPSP), the Linux-swap partition, and the Linux partition. Formats these partitions. Copies the Linux distribution boot files to the ESP partition. Updates the unattended files. Creates a new boot option in the EFI boot manager, which starts the Linux Setup process.
  • Page 39: Setting Up The Boot Mechanism

    5 Setting Up the Boot Mechanism Setting up the boot mechanism involves one of the following options: creating a bootable CD or DVD, creating a bootable USB device, or setting up a network boot environment. This chapter shows you how to perform each task at a Linux system. This chapter addresses the following topics: •...
  • Page 40: Creating A Cd Build Directory

    Creating a CD Build Directory Create a directory, enter: mkdir ./linuxbootCD Create a subdirectory to store the boot image, enter: mkdir ./linuxbootCD/boot Copy the boot image file, boot.img to the ./linuxbootCD/boot directory, enter: cp /bootable-image/boot.img ./linuxbootCD/boot Creating the ISO File The mkisofs command is used to create an ISO file.
  • Page 41: Using A Usb Flash Device

    Select one of the following options: • Enter readhwconfig to create a configuration file in the repository to save the hardware configuration of the Linux server in the repository, and then reboot the server. • Enter linux to execute the linux-setup.sh to install the Linux OS. •...
  • Page 42 Enter the EFI Boot Manager Menu and select Boot Configuration. Select Add Boot Option to add Removable Media Boot for the USB device. In the EFI Boot Manager, select the Linux USB device to boot from. Setting Up the Boot Mechanism...
  • Page 43: Using A Usb Flash Device As External Media

    Using a USB Flash Device as External Media Assuming the USB device is /dev/sda you can mount your USB device using the following command: mount –t msdos /dev/sda /mnt Using Network Boot The following sections show you how to set up and use a network boot environment Setting Up a Linux Network Boot Server This section contains instructions for performing a Linux boot over a network.
  • Page 44: Populating The Tftp Directory

    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 Use the /tftpboot directory as the directory from which TFTP clients retrieve files.
  • Page 45 Enter the EFI Boot Manager and select the appropriate boot core LAN XX option. Use the Tab key to see the boot labels defined in the elilo.conf file. Perform one of the following actions: • Enter readhwconfig. This creates a configuration file in the repository to save the hardware configuration of the Linux server in the repository.
  • Page 47: Utilities Reference

    6 Utilities Reference This chapter contains reference information and usage examples for the utilities provided in the toolkit. In other words, the manpages associated with SSTK. You can get online help for each utility by using the -h or -? option. This chapter contains the following manpages: •...
  • Page 48: Examples

    Table 6-1 cfggen Commands (continued) Commands Description Turn ON and OFF a drive's Identify LED. LOCATE Display current volume status information. STATUS Bring a hard disk offline (in IM/IME volumes). SETOFFLINE Bring a hard disk online. SETONLINE The <parameters> are command specific values. To obtain command help, you can use cfggen <controller #>...
  • Page 49: Clmchecking

    Target on ID #2 Device is a Hard disk Enclosure # Slot # Target ID State : Ready (RDY) Size (in MB)/(in sectors) : 57231/117210240 Manufacturer : ATA Model Number : FUJITSU MHT2060B Firmware Revision : 034E Serial No : NR0LT5625AAG Drive Type : SATA ------------------------------------------------------------------------...
  • Page 50: Conrep

    conrep Synopsis conrep ( -l [-f <DAT FILENAME] [-F] | -s [–x <XML FILENAME>] [-f <DAT FILENAME>] | -c | -d | -h ) [-v] | -m Description The conrep utility replicates the configuration data stored in the EFI variables. It reads the EFI variables from the NVRAM of the model server and writes the results to a DAT file.
  • Page 51: Conrep Return Codes

    </section> <section name="EFI_Non-Cell_variables"> <ev>AutobootRetry</ev> </section> <section name="EFI_Cell_variables"> <ev>AutobootRetries</ev> </section> </conrep> Table 6-4 conrep Return Codes Value Meaning Cause Action conrep executed successfully Permission denied The user is not a system Log in as root to run conrep. administrator. Usage error An error occurred while using Run conrep -h to get help using conrep for some unexpected...
  • Page 52: Cpqacuxe

    cpqacuxe Synopsis • Capture: CPQACUXE -C FILENAME [-internal | -external] -E FILENAME • Input: CPQACUXE -I FILENAME [-internal | -external] [reset] -E FILENAME • Input with reset: CPQACUXE -i-with-reset FILENAME [-internal | -external] [reset] -E FILENAME Description The cpqacuxe utility operates on the configuration of storage array controllers. The cpqacuxe utility enables the array configuration on one server to be replicated on other servers with similar array storage resources.
  • Page 53: The Cpqacuxe Utility

    Sectors = 32 StripeSize = 256 ArrayAccelerator = Enabled ; HBA SSP Specifications HBA_WW_ID= 10000000C9272B34 ConnectionName= TestConn HostMode= Linux Table 6-5 cpqacuxe Options Option Description Specifies the capture file. The capture filename is optional. If no capture file is specified, -C FILENAME the default capture file is acucapt.ini in the ACU working directory.
  • Page 54: Automatic Script File Format

    These options can be specified in any order, but an option from another category of options cannot occur between any two options from this category. Automatic Script File Format The automatic script is used to apply automatic configuration rules to unconfigured or configured controllers.
  • Page 55 Table 6-6 Automatic Script File Options (continued) Option Value Identifies to which controllers to apply the configuration. This option is required. Controller Slot [N][:N]: The internal controller with slot number N is used. External controllers can be identified by appending the Port Number. For example, an Modular Smart Array (MSA) 1500 connected to a SA6402 might be found at “Slot 4:2,”...
  • Page 56: Custom Script File Format

    Table 6-6 Automatic Script File Options (continued) Option Value Specifies the Rebuild Priority. This option is not required. If this option is not RebuildPriority specified, the Rebuild Priority remains unchanged. • Low • Medium • High Specifies the Expand Priority. This option is not required. If this option is not ExpandPriority specified, the Expand Priority remains unchanged.
  • Page 57: Custom Script File Options

    SurfaceScanDelay= N SSPState = Enable|Disable PreferredPathMode= Auto|Manual ; Array Options ; There can be multiple array specifications in the file Array = A|B|C|D|E|F|…Z|a|b|c|d|e|f OnlineSpare = Port:ID, | Box:Bay, | Port:Box:Bay | None | N Drive = Port:ID, | Box:Bay, | Port:Box:Bay, | N | * DriveType= SCSI | SAS | SATA ;...
  • Page 58 Table 6-7 Custom Script File Options (continued) Option Value Identifies to which controllers to apply the configuration. This option is required. Controller Slot [N][:N]: The internal controller with slot number N is used. External controllers can be identified by appending the Port Number. For example, an MSA1500 connected to a SA6402 might be found at “Slot 4:2,”...
  • Page 59 Table 6-7 Custom Script File Options (continued) Option Value Specifies the Write Cache percentage. This option is not required. If this option WriteCache is not specified, the Read/Write cache ratio remains unchanged. This value is a numeric value from 0 to 100. It must form a valid read/write cache ratio that is supported on the controller with the ReadCache option.
  • Page 60 Table 6-7 Custom Script File Options (continued) Option Value Specifies the physical drives for the array. A comma separated list specifies the Drive location of physical drives that are to be used in the array. In Configure mode, the physical drives listed are used to create the new array. In Reconfigure mode, all physical drives that are in the array must be listed.
  • Page 61 Table 6-7 Custom Script File Options (continued) Option Value Specifies the size of the logical drive. If the logical drive is new, the size is for Size the new logical drive. In Reconfigure mode, if the logical drive already exists and the size is different than the existing size of the logical drive, the cpqacuxe utility attempts to extend the logical drive to the new size.
  • Page 62: Error Reporting

    Table 6-7 Custom Script File Options (continued) Option Value Specifies the SSP State for a logical drive. This command is only valid for LogicalDriveSSPState controllers that support SSP that is enabled/disabled on a logical drive basis. This option is not required. If this option is not specified, the SSP State remains unchanged for existing logical drives and is disabled for new logical drives.
  • Page 63: Error Codes

    The error file displays the error code, error message, and if possible, lists the controller, array, or logical drive associated with the error. The format of the error file is as follows: Line1:ACU Configuration Replication Error Line2:ERROR: (<error code>) <error description> Line3:Controller: Slot # | SerialNumber # | WWN # Line4:Array: # Line5: Logical Drive: #...
  • Page 64 Table 6-8 Error Codes (continued) Code Error Reason 2849 The specified ClearConfigurationWithDataLoss parameter Invalid is not correct. ClearConfigurationWithDataLoss parameter 2825 The Array ID is invalid. Invalid Array 2826 The array command is missing from the script file. Some Array not specified commands were found that require an array to work on.
  • Page 65 Table 6-8 Error Codes (continued) Code Error Reason 2837 When running in Configure mode, this error occurs when New Logical Drive ID already the Logical Drive ID in the script file already exists in the exists configuration. Configure mode can only create new logical drives.
  • Page 66 Table 6-8 Error Codes (continued) Code Error Reason 1114 The controller requires non-failed physical drives for license Controller requires non-failed keys. physical drives to set license keys 1111 The entered license key is not a valid license key. Invalid license key 1112 The controller already has the maximum number of license Controller has maximum number of...
  • Page 67: Efibootmgr

    Table 6-8 Error Codes (continued) Code Error Reason 2878 Spares are not supported in RAID0-only Arrays. Spare Request for RAID0 is Invalid 2879 Mode is Reconfigure and a controller reset with data loss was Reset and Reconfigure combined specified. Error 2880 Invalid Disk Type specified.
  • Page 68: Efibootmgr Commands

    Table 6-10 efibootmgr Commands Commands Description Define the file to include more options. -@ | --@ file Select BootXXXX (hex) variable to be deleted. -b | --bootnum XXXX Device file that the boot loader stores. (defaults to /dev/sda). -d | --disk disk Force EDD 1.0 or 3.0 creation variables, or guess.
  • Page 69: Efivar

    Table 6-1 1 efibootmgr Command Line Input (continued) Command Line Input Result Create a boot entry with the following values: efibootmgr -c -l /bootia64.efi -@ parameter.txt • NAME: Linux • DEVICE: /dev/sda • PARTITION: 1 • BOOT LOADER: /bootia64.efi • LOAD OPTION: data into the parameter.txt file Delete the second boot entry (BOOT0002).
  • Page 70: Hpacucli

    Table 6-13 getuuid Options Options Description Disk to from which information will be retrieved. <disk> Partition number. Shows GUID of partition type (efi, hpsp, etc). hpacucli Description The hpacucli command is a disk configuration tool that can be used to configure and manage Smart Array Controllers and RAID Array Controllers.
  • Page 71: Hpia64Info

    controller slot=3 logicaldrive 2 modify arrayaccelerator=enable ctrl all show status Please use hpacucli help <command> for more information and usage or use the hpacucli help for a list of commands. hpia64info Synopsis hpia64info -v Description The hpia64info utility displays information about management processor and system firmware. The hpia64info utility has one option, -v.
  • Page 72: Description

    Description The hplpcfg utility enables or disables the EFI or BIOS boot setting on Emulex 2G or 4G Fibre Channel Host Bus Adapter (FC HBA). Table 6-15 hplpcfg Options Options Description Saves the HBA configuration to filename. /se <filename> Loads the HBA configuration from filename. /le <filename>...
  • Page 73: Hpsetacpi

    BootDeviceWWPN=2200000000000000 ; input from customer - Boot Device Port name BootDeviceLUN[0]=0 ; input from customer – Boot Device LUN ID For 4G HBAs: [HBA0] ; section for each HBA - HBA No WWID=11223344 ; read-only variable - HBA WWPN SelectiveLogin=1 ; input from customer - 1 (Enable) or 0 (Disable) EnableSelectiveLUN=1 ;...
  • Page 74: Examples

    The hpshowdisk utility is internally used by SSTK scripts to display the “available disks” menu during installations. In addition, it is externally used with the RDP product, which by default it calls the RDP “showdisk” application; SSTK scripts use the -n option to avoid this external application call.
  • Page 75: Description

    Description The hwdisc utility provides an inventory of the server being configured or captured. The hwdisc utility is executed by the server configuration script and captures the following information: • System Name • Serial Number • Asset Tag • EFI Firmware version •...
  • Page 76 </PCIDevice> <PCIDevice num="2"> <Bus>0</Bus> <Device>1</Device> <Function>2</Function> <Id>103300E0</Id> <SubId>103300E0</SubId> </PCIDevice> <PCIDevice num="3"> <Bus>0</Bus> <Device>2</Device> <Function>0</Function> <Id>10950649</Id> <SubId>10950649</SubId> </PCIDevice> <PCIDevice num="4"> <Bus>0</Bus> <Device>3</Device> <Function>0</Function> <Id>80861229</Id> <SubId>103C1274</SubId> </PCIDevice> <PCIDevice num="5"> <Bus>20</Bus> <Device>1</Device> <Function>0</Function> <Id>10000030</Id> <SubId>10001000</SubId> </PCIDevice> <PCIDevice num="6"> <Bus>20</Bus> <Device>1</Device> <Function>1</Function> <Id>10000030</Id> <SubId>10001000</SubId> <DeviceName>/dev/sda</DeviceName>...
  • Page 77: Hwquery

    <Id>10025159</Id> <SubId>103C12AB</SubId> </PCIDevice> </PCIDevices> </ServerInformation> </HWDiscovery> hwquery Synopsis hwquery [path]hwdiscfilename [path]allboards.xml variable=<string> ... 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.
  • Page 78: Ifhw

    The hwquery utility produces MYRAM=768and MYEFIFW=1.10. • If the MYRAM environment variable does not exist, this command creates the variable. To set the value of the <RAM> tag in hwdisc.xml to the MYRAM environment variable use this command. export $( hwquery hwdisc.xml allboards.xml MYRAM=RAM ) ifhw Synopsis ifhw [path]hwdiscfilename [path]allboards.xml <expression>...
  • Page 79: Parted

    Table 6-22 Expressions Operator or Term 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.
  • Page 80 • To print general help, or help on COMMAND: help [COMMAND] • To create a new disk label (partition table): mklabel PARTITION_TYPE The supported values for PARTITION_TYPE are: gpt, bsd, mac, dvh, msdos, pc98, sun, amiga, loop • To make a file system FTYPE on partition MINOR: mkfs MINOR FTYPE FTYPE is file system type: fat16, fat32, ext2 and linux-swap.
  • Page 81 • To create a new GPT partition table in /dev/sda device: parted -s /dev/sda mklabel gpt • To create a partition with 100 MB, starting in LBA 0 and finalizing in LBA 100 in /dev/ cciss/c0d0 device: parted -s /dev/cciss/c0d0 mkpart 0 100 •...
  • Page 83: A Known Issues

    A Known Issues This section provides information on the known issues when using SSTK. IMPORTANT: HP recommends that you review the readme file included with SSTK, which may contain late-breaking known issues for this release that could not be included in this document.
  • Page 84: No Msa Storage Information Displayed By Acu

    To avoid this issue, do not use the SmartArray P600 in slot 0 on HP Integrity Superdome sx2000 server. No MSA Storage Information Displayed by ACU The ACU does not capture configuration information from the Emulex HBA that connects to MSA storage so no information about the storage device is displayed by the ACU.
  • Page 85: Efibootmgr Utility Issues

    efibootmgr Utility Issues When using the efibootmgr utility, you should be aware of the following issues: • It is possible to create entries to nonexistent boot loaders. • The EFI interface menu is does not accurately indicate the Active/Inactive flag for the boot entries.

Table of Contents