SmartSetup Scripting Toolkit Deployment Guide HP Integrity Servers with Linux HP Part Number: 5991-6250 Published: July 2010 Edition: 9
© Copyright 2007–2010 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. The information contained herein is subject to change without notice.
Table of Contents Preface.................................................................................................................................8 Intended Audience.................................................................................................................................8 Typographic Conventions......................................................................................................................8 Publishing History...............................................
Using a USB Flash Device as External Media.................................................................................44 Using Network Boot.............................................................................................................................44 Setting Up a Linux Network Boot Server........................................................................................44 Setting Up a DHCP Server.......................................................................................
Synopsis...........................................................................................................................................71 Description.......................................................................................................................................72 Format........................................................................................................................................72 hpsetacpi...........................................................
List of Tables 4-1 4-2 4-3 4-4 4-5 5-1 6-1 6-2 6-3 6-4 6-5 6-6 6-7 6-8 6-9 6-10 6-11 6-12 6-13 6-14 6-15 6-16 6-17 6-18 6-19 6-20 6-21 6-22 6-23 6 SSTK Variables...............................................................................................................................34 SSTK Configuration Variables.......................................................................................................35 Global Options.......................................................................
List of Examples 6-1 6-2 6-3 6-4 6-5 cfggen list Command.............................................................................................................48 cfggen Display Command..........................................................................................................48 Sample conrep.dat file..............................................................................................................50 Sample conrep.xml File.......................................................
Preface This document provides instructions for configuring and using the SmartSetup Scripting Toolkit (SSTK) on HP Integrity servers running Linux.
[ERRORNAME] The name of an error, usually returned in the errno variable. Key The name of a keyboard key. Return and Enter both refer to the same key. Term The defined use of an important word or phrase. UserInput Commands and other text that you type. Variable The name of a placeholder in a command, function, or other syntax display that you replace with an actual value. [] The contents are optional in formats and command descriptions.
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. Document updates might be issued between editions to correct errors or document product changes.
Manufacturing Part Number Supported OS Supported Versions Edition Number Publication Date RHEL4U5, RHEL4U6, and RHEL5U1 SLES9SP3 (Backward compatible only1), SLES9SP4, and SLES10SP1 5991-6250 Red Hat Enterprise Linux (RHEL) RHEL4U4 (Backward SUSE Linux Enterprise Server (SLES) compatible only1), RHEL4U5, and RHEL5 SLES9SP3 (Backward compatible only1) and SLES10SP1 3 August 2007 5991-6250 Red Hat Enterprise Linux (RHEL) RHEL4U4, and RHEL4U5 SUSE Linux Enterprise Server (SLES) SLES9SP3 2 January 2
HP Encourages Your Comments HP encourages your comments concerning this document. We are committed to providing documentation that meets your needs. Send any errors found, suggestions for improvement, or compliments to: docsfeedback@hp.com Include the document title, manufacturing part number, and any comment, error found, or suggestion for improvement you have concerning this document.
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.
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. The SSTK provides sample scripts and utilities that run in a staging environment based on Debian Linux for HP Integrity servers.
• • 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. The target servers are the machines you want to set up as replicas.
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 34), specifies the default location of the repository. It can be modified to specify a repository location of your choosing thereby customizing the SSTK environment.
1. As root, extract the SSTK-LinuxIntegrity-3.4.tgz package, located on your HP Integrity CD, into the directory location that to host the repository. For example, creating the repository in the repository directory you would use the following commands: cp SSTK-LinuxIntegrity-3.4.tgz /repository cd /repository tar zxvf SSTK-LinuxIntegrity-3.4.tgz 2. Edit the /etc/fstab configuration file and append the following line to it: /dev/cdrom 3.
6. a. Select Destination Directory and click OK. b. c. Select the destination directory by navigating to the correct directory, and then click OK. Select CDROM Device and click OK. d. 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.
8. 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.
| |-- sles10sp3 | |-- sles11sp1 `-- utilities |-- CLMChecking |-- allboards.xml |-- cfggen |-- conrep |-- conrep.xml |-- cpqacuxe | |-- bld | | |-- acu.xml | | |-- ipcelmclient | | |-- ipcelmclient.php | | |-- libLLPI.so | | |-- libcpqhmmo.so | | |-- libcpqimgr.so | | |-- libhwmim3.so | | |-- libossingleton.
| | `-- upgrade.txt | |-- cpqacuxe | `-- cpqacuxe.license |-- dumppci -- efivar |-- gen-setupldr-options |-- getuuid |-- hpacucli | |-- bld | | |-- hpacucli | | |-- hpacucli.license | | |--libhwmim3.so | | |-- hpacucli-8.25-5.ia64.txt | | |--libcpqimgr.so | | |-- libossingleton.so | |--hpacucli |-- hplpcfg |-- hpqlarep |-- hpsetacpi |-- hpshowdisk |-- hwdisc |-- hwquery |-- ifhw `-- linux |-- getmediacode.sh |-- mke2fs |-- mkrep-rhel4up4.sh |-- mkrep-rhel4up5.sh |-- mkrep-rhel4up6.sh |-- mkrep-rhel4up7.
2 Using the SSTK Deployment Workflow Server deployments using SSTK involve four main stages.
Setting Up the Toolkit Environment Setting up the toolkit environment involves the following tasks: 1. 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. The bootstrap script invokes the main toolkit launch script, which uses a Linux setup script to trigger the OS installation.
Capturing Images To capture one image, use the following steps: 1. Ensure that the source computer is booted and running SSTK. 2. 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. 3. 4. Select [2] capture (capture Linux image). Select the disk to be imaged.
Customizing the Toolkit Environment After you have gained some familiarity with the SSTK, you might find yourself eager to take advantage of its flexibility using your own scripts and customizations. HP suggests the following ways in which you can extend the capabilities of the toolkit environment.
2. Configure the IPv6 static address: # ifconfig inet6 add netmask up For example: # ifconfig eth3 inet6 3ffe:501:ffff:100:205:5dff:fea1:b73c/64 netmask 255.0.0.0 up 3.
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.
4. 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: 1. Select EFI Boot Manager > Boot Option Maintenance Menu. 2. Select Select Active Console Input Devices. Select only one Acpi(HWP—2,700)PCI ~~/Uart~~ device. 3. Select Select Active Console Output Devices. Set input console to be the same as the output console device. 4.
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. • The boot_files directory holds the toolkit environment, which you must copy onto the SSTK boot device. The boot_files\efi\boot\ directory contains the following files: bootia64.efi The \efi\boot\bootia64.
software/EFI_TOOLS A placeholder directory, which you can populate with applications that are copied to the HP Service Partition 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.
utilities into the RAMdisk, running I/O hardware inventory, and prompting the you to select a deployment task. • linux-setup.sh This script launches Linux installation by creating and formatting disk partitions, specifying the Linux Setup boot option, and rebooting the server. rhel-setup.sh This script edits the configuration in the RHEL unattended configuration file and copies the RHEL boot image files to the ESP partition. sles-setup.
hpia64info The hpia64info utility, which displays information about Management Processor and system firmware. hwdisc The hardware discovery utility, which creates an inventory of the server and writes this data to a file. hwquery The hardware query utility, which reads the file created by the hardware discovery utility and provides this data in a usable form. ifhw The if hardware utility, which makes user process decisions based on data from the file created by the hardware discovery utility.
NOTE: SSTK supports unattended OS installations on HP Integrity Virtual Machines.
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. This chapter provides guidance on editing these files. This chapter addresses the following topics: • “Editing the sstk.
Table 4-1 SSTK Variables (continued) Variable Name Description IMAGE_FILE="" Sets the name of the Linux image file. The default value is linux.img. LOG_LEVEL=0 Sets the log level. Set 1 for normal logging or zero (0 ) for extended logging. The default value is zero. ESP_SIZE=128 Defines the ESP partition size. HPSP_SIZE=400 Defines the HPSP partition size 0. SWAP_SIZE=500 Defines the SWAP partition size. AUTO_CONFIGURE_SAN="yes" Enables automatic configuration for the SAN environment.
Table 4-3 Global Options (continued) • Global Option Description delay=number Specifies the number of tenths of seconds to wait before autobooting when not in interactive mode. Default is 0. prompt Forces interactive mode. verbose=number Sets level of verbosity [0–5]. Default is 0 (no verbosity). root=filename Sets global root filesystem for Linux/ia64. read-only Forces root filesystem to be mounted read-only. append=string Appends a string of options to kernel command line.
Table 4-5 SSTK Command Line Options (continued) SSTK Option Description USB—/dev/devicename ssstk_mount_options=string Passes extra parameters to the mount command. ssstk_script=filename Specifies the name of main launch script. ssstk_action=string Specifies the default response to the toolkit launch script prompt (readhwconfig, bash, capture, deploy, or linux). idebus=xx Reports the VESA/PCI bus speed in MHz to the IDE driver, where xx is between 20 and 66 inclusive.
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. Reviewing the main_toolkit_launch.
1. 2. 3. 4. 5. 6. 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. Reboots the server. NOTE: The parted utility uses decimal, instead of binary, units to measure disk size.
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.
Creating a CD Build Directory 1. Create a directory, enter: mkdir ./linuxbootCD 2. Create a subdirectory to store the boot image, enter: mkdir ./linuxbootCD/boot 3. 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. The following table describes the arguments used with this command. Table 5-1 The mkisofs Command Options Option Description -o linuxbootCD.
5. 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. • Enter bash to go to the bash prompt. At the bash prompt enter the dmesg command to determine the name of the SCSI device. Edit the linux-setup.sh script, and then reboot.
3. 4. Enter the EFI Boot Manager Menu and select Boot Configuration. Select Add Boot Option to add Removable Media Boot for the USB device. 5. In the EFI Boot Manager, select the Linux USB device to boot from.
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. NOTE: File locations and process names in this section might vary slightly depending on your Linux distribution.
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. To populate the TFTP directory: 1. Create a /tftpboot directory, if needed. 2.
1. 2. 3. 46 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. Reboot the server. • Enter linux to execute the linux-setup.sh utility to install the Linux OS.
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.
Table 6-1 cfggen Commands (continued) Commands Description LOCATE Turn ON and OFF a drive's Identify LED. STATUS Display current volume status information. SETOFFLINE Bring a hard disk offline (in IM/IME volumes). SETONLINE Bring a hard disk online. The are command specific values. To obtain command help, you can use cfggen . Examples Example 6-1 cfggen list Command SSTK-v.2.6-4# cfggen list LSI Logic IR Configuration Utility 2.00.
Device is a Hard disk Enclosure # : 1 Slot # : 2 Target ID : 2 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 -----------------------------------------------------------------------Enclosure information -----------------------------------------------------------------------Enclosure# : 1 Logical ID : 50060b00:00c13846 Numslots : 8 StartSlot : 1 Start TargetID : 0 Start Bus
conrep Synopsis conrep ( -l [-f ] [-f ] | -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. It also reads the DAT file and writes this data into the NVRAM of the target server. The conrep utility uses the conrep.xml file to determine what data to retrieve from the server.
Table 6-4 conrep Return Codes Value Meaning Cause Action 0 conrep executed successfully 1 Permission denied The user is not a system administrator. Log in as root to run conrep. 2 Usage error An error occurred while using conrep for some unexpected reason, such as the wrong parameters. Run conrep -h to get help using conrep.
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.
Sectors = 32 StripeSize = 256 ArrayAccelerator = Enabled ; HBA SSP Specifications HBA_WW_ID= 10000000C9272B34 ConnectionName= TestConn HostMode= Linux Table 6-5 cpqacuxe Options Option Description -C FILENAME Specifies the capture file. The capture filename is optional. If no capture file is specified, the default capture file is acucapt.ini in the ACU working directory. -E FILENAME Specifies the error file. The error filename is optional.
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. If the -i-with-reset or –reset command line switch is used, the existing controller configuration is cleared with data loss before the new configuration is applied, effectively making it an unconfigured controller.
Table 6-6 Automatic Script File Options (continued) Option Value IOCabinet [N], IOBay [N], IOChassis [N],Slot [N], Cabinet [N], Cell [N]: The controller identified by the IPF Slot path information is used. Use of the -internal” and -external command line switches influences what is regarded as the first controller. For example, if the -external switch is used, the first controller is the first external controller discovered, regardless of the number of internal controllers in the host system.
Table 6-6 Automatic Script File Options (continued) Option Value SurfaceScanDelay Specifies the Surface Scan Delay in seconds. This option is not required. If this option is not specified, the Surface Scan Delay remains unchanged. N: This value is a numeric value between 1 and 30 seconds. OnlineSpare Specifies if Automatic Configuration should attempt to add spares. This option is not required. This option is ignored in Reconfigure mode if there is an existing configuration on the controller.
Size = [N]|Max Sectors = 32|63 StripeSize = 8|16|32|64|128|256 ArrayAccelerator= Enable|Disable ResourceVolumeOwner= N LogicalDriveSSPState = Enable|Disable SSPAdaptersWithAccess = [N],[N]…|None PreferredPath = 1|2 ; HBA Options ; There can be multiple HBA specifications in the file HBA_WW_ID = WWN ConnectionName = UserDefinedName HostMode = Default|Windows|Windows(degrade |OpenVMS|Tru64|Linux|Solaris|Netware|HP|Windows_SP2_and_ Table 6-7 Custom Script File Options Option Value Action Defines if you are
Table 6-7 Custom Script File Options (continued) Option Value RAIDArrayID Specifies the RaidArrayID for controllers that support RaidArrayID. This is a user-defined string to identify controllers. Currently, RaidArrayIDs are only supported by Fibre and shared-storage controllers. "XXXXXXXXXXXXXXXXXXXX" Varying length string that can consist of any of the following characters: a-z A-Z 0-9 ! @ # * ( ) , - _ + : . / [space] This string has a maximum length that varies depending on the type of controller.
Table 6-7 Custom Script File Options (continued) Option Value SSP only remains enabled if the SSPAdaptersWithAccess command specifies an adapter for one or more logical drives. If no adapters with access are specified for any logical drives, the SSP State reverts back to disabled. PreferredPathMode Specifies the preferred path mode when redundant array controllers are in an active-active configuration. This option is only available for certain redundant array controllers.
Table 6-7 Custom Script File Options (continued) Option Value existing configuration to create a new logical drive. In most cases logical drives must appear in the configuration file in increasing order. RAID Specifies the RAID level for the current logical drive. In Configure mode, the RAID is the RAID for the new logical drive. In Reconfigure mode, if the logical drive already exists and the RAID is different than the existing RAID on the logical drive.
Table 6-7 Custom Script File Options (continued) Option Value • RAID 5: 8, 16, 32, 64 (default is 16) • RAID ADG: 8, 16, 32, 64 (default is 16) ArrayAccelerator Specifies the Array Accelerator setting for the logical drive. • Enable: Enables the Array Accelerator for the logical drive. This is the default setting for new logical drives. • Disable: Disables the Array Accelerator for the logical drive.
Table 6-7 Custom Script File Options (continued) Option Value • • • • • • • OpenVMS TRU64 Linux Solaris Netware HP Windows_SP2 Error Reporting When using the cpqacuxe utility, any errors that are encountered are logged to the error.ini file or the specified error file. Error codes are also returned to the calling process, allowing scripting clients to key off the return code instead of having to parse the error file.
Table 6-8 Error Codes (continued) Code Error Reason 2819 Controller '%s' is invalid The controller specified is not specified correctly. 2820 Could not detect Controller '%s' The controller specified was not detected. 2818 Invalid Method Invalid Method value. 2819 Invalid Controller Invalid Controller value. 2822 Invalid Read Cache/Write Cache Ratio The specified Read Cache/Write Cache Ratio is not supported either by the controller or the current controller configuration.
Table 6-8 Error Codes (continued) Code Error Reason error does not occur. However, if the controller does not support migration, this error occurs. 64 2834 Invalid Logical Drive The Logical Drive ID is not valid. 2835 Logical Drive not specified The Logical Drive command is missing from the script file. Some commands were found that require a Logical Drive to work on.
Table 6-8 Error Codes (continued) Code Error Reason 278-282, 2564 Controller is locked by another One or more controllers is locked by another machine or user. machine or user 268 Error saving Controller There was a problem saving one or more controller configurations. 1065-1066 Too many coinciding expansion, migration, or extension operations This error is the “invalid increase/decrease” in logical drive offset error.
Table 6-8 Error Codes (continued) Code Error Reason 2860 Cannot change Resource Volume Owner The Resource Volume owner cannot be changed if it is a configured logical drive. 2861 Controller does not support redundancy settings The controller is not redundant or does not support redundancy settings. 2864 Invalid Preferred Path Mode The preferred path mode is not a valid preferred path mode or the controller is not available.
Table 6-9 efibootmgr Options (continued) Options Description -o | --bootorder XXXX,YYYY,ZZZZ,... Explicitly set BootOrder. The values must be in hex. -O | --delete-bootorder Delete BootOrder -t | --timeout seconds Set boot manager timeout waiting for user input. -T | --delete-timeout Delete Timeout. -V | --version Return version and exit. Table 6-10 efibootmgr Commands Commands Description -@ | --@ file Define the file to include more options.
Table 6-11 efibootmgr Command Line Input (continued) Command Line Input Result • BOOT LOADER: /efi/boot/bootia64.efi • LOAD OPTION: LINUX efibootmgr -c -L "Boot" -l /bootia64.efi --test bootentry.bin Generate a boot entry but do not save it in NVRAM. The boot entry values are: • NAME: Boot • DEVICE: /dev/sda • PARTITION: 1 • BOOT LOADER: /bootia64.efi • LOAD OPTION: none efibootmgr -c -l /bootia64.efi -@ parameter.
getuuid Synopsis getuuid | -p| -t Description The getuuid utility retrieves the UUID (Universally Unique ID) used for identifying a storage device or a single partition. Table 6-13 getuuid Options Options Description Disk to from which information will be retrieved. -p Partition number. -t Shows GUID of partition type (efi, hpsp, etc).
Table 6-14 hpacucli Commands (continued) Commands Description delete The delete command deletes part of an existing configuration.
Example 6-5 Sample hpia64imfo Utility Output Format: 1 MP Version: F.01.55 MP Lan Status: Enabled MP Host Name: superbird MP IP Address: 16.89.144.239 MP Netmask: 255.255.252.0 MP Gateway: 16.89.144.1 MP MAC Address: 00-14-C2-9C-07-6C Asset Tag: hello world BMC Version: 05.07 SFW Version: 01.31 EFI Version: 05.
Description The hpqlarep utility enables or disable the EFI or BIOS boot setting on QLogic 2G or 4G HBAs. Table 6-16 hpqlarep Options Options Description /s Saves the HBA configuration to . /l Loads the HBA configuration to .
SSTK-v.3.2# ./hpsetacpi linux ACPI mode was properly set hpsetacpi 89 hpshowdisk Synopsis hpshowdisk -v | -h | -n | -I | -p| -d | -s Description The hpshowdisk utility helps with the identification of the disks recognized by the system. It can be very useful in situations where the system has lots of disks, typically on SAN architectures.
hwdisc Synopsis hwdisc -f[path]filename Description The hwdisc utility provides an inventory of the server being configured or captured.
Example hwdisc –f/mnt/data/hwdisc.xml This command generates the file hwdisc.xml in the /mnt/data location. A typical file generated by the hwdisc command is similar to the following: server rx2600 US21729947 1.22 1.53 E.03.
1 10000030 10001000 /dev/sda 34732 20 2 0 14E41645 103C12A4 E0 1 0 103C1290 103C1291 E0 1 1 103C1048
Table 6-20 hwquery Options (continued) Command Line Argument Description variable= In this argument, variable is the name of an environment variable and is a PCI device name or the name of an element from the hardware discovery file. Arguments must be in quotes if contains spaces. The name is case-sensitive. ... You can specify multiple variable=arguments. Examples • To produce an hwdisc.
Table 6-21 ifhw Options Option Description [path]hwdiscfilename This argument specifies the hardware discovery file used to run the query. [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 6402 Controller." expression This argument specifies the query expression. Examples The ifhw utility might use XML files as input to query the hardware discovery file.
Table 6-22 Expressions (continued) Operator or Term Result HWQ:string The hardware discovery file is searched for string, and the corresponding value is the value of this term. string is case-sensitive. string A literal string, used for comparison. number A literal number, used for comparison. parted Synopsis parted [-v | -i | -s | -h]... [DEVICE [COMMAND [PARAMETER]...] ...] Description The parted utility manages disk partitions.
• To create a partition with a file system: mkpartfs PTYPE FTYPE START END PTYPE is partition type: primary, logical or extended. For GPT partition table only “primary” is used. FTYPE is file system type: fat16, fat32, ext2 and linux-swap.
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. Pre-OS Linux Prompts Are Not Displayed The pre-OS Linux prompts are visible through the MP LAN connections.
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. This is a known issue with the ACU. To avoid this issue, configure Emulex boot devices with hplpcfg. Incorrect Logical Disk Drive Size Displayed The logical disk size was not specified with the cfggen utility.
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. • The labels of the boot entries are not updated. SSTK Image Does Not Boot and LSI Driver Loops The LSI controller driver does not respond to hardware failures correctly.
*5991-6250* Printed in the US
