1. Manuals
  2. Brands
  3. HP Manuals
  4. Server
  5. Integrity rx1620
  6. Deployment manual

HP Integrity rx1620 Deployment Manual

Scripting toolkit deployment guide
Hide thumbs Also See for Integrity rx1620:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Maintenance Manual, Operating Manual
HP Integrity Servers with Microsoft Windows
Server 2003 for Itanium-based systems
SmartSetup Scripting Toolkit Deployment
Guide
HP Part Number: 5992-0954
Published: December 2007

Advertisement

Table of Contents
loading

Related Manuals for HP Integrity rx1620

Summary of Contents for HP Integrity rx1620

  • Page 1 HP Integrity Servers with Microsoft Windows Server 2003 for Itanium-based systems SmartSetup Scripting Toolkit Deployment Guide HP Part Number: 5992-0954 Published: December 2007...
  • Page 2 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...

  • Page 3: Table Of Contents

    Table of Contents About This Document.......................13 Intended Audience..........................13 Typographic Conventions........................13 HP Encourages Your Comments......................13 1 Overview........................15 Introduction............................15 Toolkit components..........................16 Plan the deployment..........................17 Select a workstation.........................17 Select a boot mechanism........................17 Position the repository........................18 Go with the workflow...........................18 Setting up a model server........................18 Creating a server profile........................19...
  • Page 4 From a Linux workstation.......................54 Create a bootable disk image.....................54 Create a CD build directory.......................54 Create the ISO file........................55 Booting from the CD/DVD......................55 Using a USB flash device........................55 Create a bootable USB flash device on a Windows workstation............55 Create a bootable USB flash device on a Linux workstation............56 Boot from the USB flash device.......................56 Using USB flash device as external media..................57 Using network boot..........................57...
  • Page 5 Synopsis............................85 Description............................85 Options............................85 Example............................85 gen-setupldr-options..........................86 Synopsis............................86 Description............................86 Options............................86 getuuid..............................87 Synopsis............................87 Description............................87 Options............................87 hpia64info.............................88 Synopsis............................88 Description............................88 Options............................88 Output..............................88 hplpcfg..............................89 Synopsis............................89 Description............................89 Options............................89 Format..............................89 Example............................89 hpqlarep..............................90 Synopsis............................90 Description............................90 Options............................90 Format..............................90 hpsetacpi...............................91 Synopsis............................91 Description............................91 Options............................91 Example............................91 hpshowdisk............................92 Synopsis............................92 Description............................92 Options............................92 Example............................92 hwdisc..............................94 Synopsis............................94 Description............................94 Options............................94 Example............................94...
  • Page 6 Description............................99 Options............................99 Examples............................99 sstkencrypt............................101 Synopsis............................101 Description.............................101 Example............................101 A Support Matrix......................103 Supported systems..........................103 Supported LSI and SmartArray SCSI/RAID controllers..............103 Supported Emulex and QLogic Fiber Channel controllers..............104 Supported Intel, Broadcom, and Neterion NIC I/O cards..............104 Supported storage..........................105 Table of Contents...
  • Page 7 List of Figures Clone a Server Setup........................15 Main Components of SSTK Deployment..................16 Linux Boot Files..........................17 Console Configuration Window....................24 Console Output Devices Window....................24 SSTK Archive..........................26 /os/windows/2003-enterprise/ Directory..................31 EFI Directory..........................50 Disc Creator Classic Main Window....................51 Roxio Project Area.........................51 Create Disc Image..........................52 New Compilation Window......................53 Burn Tab............................53 Copy Boot files..........................55 EFI shell Window..........................56...
  • Page 9 List of Tables SSTK Repository Permissions.......................29 Global options..........................42 Image options..........................43 SSTK command line options......................43 mkisofs command options......................55 cfggen Command Values.......................63 CLMChecking Options........................65 conrep Options..........................66 conrep Return Codes........................67 cpqacuxe Options..........................69 Automatic script file options......................70 Custom script file options......................73 cpqacuxe Error Codes........................79 efibootmgr Options........................83 5-10 Commands............................83...
  • Page 11 List of Examples cfggen list command........................63 cfggen display command......................63 Sample conrep.dat file........................66 conrep.xml file..........................66 Sample hpia64info utility output....................88...

  • Page 13: About This Document

    Intended Audience This document is for system administrators who need to deploy a large number of HP Integrity® servers rapidly and efficiently. Typographic Conventions This document uses the following typographical conventions: A command name or qualified command phrase.

  • Page 15: Overview

    CDs or people, your approach to deploying a large number of servers is likely to be similar. To deploy a hundred identical HP Integrity servers quickly and efficiently, you would set up a model server manually and then clone this setup...

  • Page 16: Toolkit Components

    The configuration of the storage array controllers installed in the model server sets the standard for all others. You can configure the controllers using the HP Option ROM Configuration for Arrays (ORCA) EFI application before booting the OS or run the Array Configuration Utility (ACU) after the OS is installed.

  • Page 17: Plan The Deployment

    The utilities run in a Linux environment. The kit provides Linux boot files (boot loader, kernel, root file system, and boot configuration) for you to copy onto the boot device (Figure 1-3). Figure 1-3 Linux Boot Files • The SSTK boot device — a CD or DVD, a network share, or a USB flash drive — holds files that allow servers to boot to the toolkit environment.

  • Page 18: Position The Repository

    Configuration Utility (ACU) after the OS is installed. For detailed instructions, see the Smart Setup Guide (on the Smart Setup CD or at http://docs.hp.com/en/windows.html). The Smart Setup CD is included in the HP Integrity Essentials Foundation Pack Kit. You can also download the ISO from http://www.hp.com/support/itaniumservers/. You will also need the Microsoft Windows Server 2003 Enterprise Edition CD.

  • Page 19: Creating A Server Profile

    (for a boot controller) or the graphical mode of Windows Setup. Install additional applications. HP urges you to update the replica servers with the latest drivers and utilities and set it up as a managed system. This involves installing the Integrity Support Pack (ISP) on each server.

  • Page 20: 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.
  • Page 21 If the LOG_LEVEL variable in the sstk.conf file is set to 0 (zero), addition information is added to the log file as indicated in the following example: ============== lspci ============== <output of the lspci command> ============== dmesg ============== <output of the dmesg command> ============== hpbmc ============== <output of the hpbmc utility>...

  • Page 23: Creating A Server Profile

    UNIX file format or a DOS to UNIX file converter. HP urges you to install the 32-bit version of the Partition Manager tool on the workstation. Use this utility to create a partition on the model server and the target server. Partition Manager is available on the Smart Setup CD.

  • Page 24: Console Configuration Window

    Select Error Console. Set error console to the same as the output console device. Figure 2-1 Console Configuration Window At the Integrity server (the model server and each target server) using the Legacy interface: Select EFI Boot Manager->Boot Option Maintenance Menu. Select Select Active Console Input Devices.

  • Page 25: Unpack The Toolkit

    Windows. You can extract files using a ZIP file utility (WinZip). tar gzip file The .tgz file is intended for deployment environments in which most workstations run Linux or HP-UX. You can expand and extract the archive using the tar command. The archive expands into a file structure (Figure 2-3) that also serves as a skeleton for the server profile.

  • Page 26: Sstk Archive

    Figure 2-3 SSTK Archive The following list shows the directory hierarchy and the files within those directories. The root of the directory contains this guide and a README file with late-breaking release information. • The boot_files directory holds the toolkit environment, which you must copy onto the SSTK boot device.
  • Page 27 • The software directory is the placeholder of applications copied to the HP Service Partition or Windows tools that will be installed after the operating system is initially installed. Files placed under software\EFI_TOOLS will be automatically copied to the HP Service Partition.
  • Page 28 partition, copying the setup loader ( setupldr.efi) application to the ESP partition, configuring the winnt.sif file, specifying the Windows Setup boot option, and rebooting the server. In this file, you can set the SSTK variables used by the scripts, such sstk.conf as the default action of SSTK, the disk where windows will be installed, the name of configuration files, and so on.

  • Page 29: Setting Permissions For Repository Access

    The getuuid utility retrieves the universally unique getuuid identifier (UUID) used for identifying a storage device or a single partition. The HP Emulex HBA configuration utility. hplpcfg The HP QLogic HBA configuration utility. hpqlarep The hpshowdisk utility gathers information from...

  • Page 30: Clm Mode Check

    For additional information about sharing permissions and password configurations over a Windows Network, see the following resources: • How To Share Files and Folders over the Network in a Windows Server 2003 Domain Environment http://support.microsoft.com/kb/324267/EN-US • How to Configure File Sharing in Windows XP at http://support.microsoft.com/kb/B304040/EN-US CLM mode check On cellular systems, the available system memory can be accessed using two different approaches:...

  • Page 31: Os/Windows/2003-Enterprise/ Directory

    Figure 2-4 /os/windows/2003-enterprise/ Directory In case you want to configure your repository to enable other Windows operating system versions, you must do the following: Populate the /os/windows/ directory as previously described. Populate the /drivers/ directory for all desired versions. The resulting directory structure is as follows: Upload the operating system installation files...

  • Page 32: Set Up An Unattended Operating System Installation

    +---os \---windows |---2003-enterprise \---2003-enterprise-sp2 +---drivers \---storage |---saP600 \---windows |---2003-enterprise \---2003-enterprise-sp2 \---sa6400 \---windows |---2003-enterprise \---2003-enterprise-sp2 Set up an unattended operating system installation The Windows directory contains a file to drive an unattended Windows installation. This file, which Microsoft refers to as an “answer file”, is called unattended.txt. Even if you maintain multiple Windows versions, the same unattended.txt file will be used for each version.

  • Page 33: Accessing The Server After A Windows Installation

    AutoUsers = "5" [Display] BitsPerPel = 16 XResolution = 800 YResolution = 600 VRefresh = 70 [Branding] BrandIEUsingUnattended = No IEBrandingFile = install.ins [Networking] [WindowsFirewall.Standard] Services = RemoteDesktop [WindowsFirewall.RemoteDesktop] Type = 2 [TerminalServices] AllowConnections = 1 [Identification] JoinWorkgroup = Workgroup [NetOptionalComponents] SNMP=1 WBEMSNMP=1...

  • Page 34: Installing Tools From The Integrity Support Pack

    To install Integrity Support Pack tools, copy the executable file for each tool you want to install into the appropriate directory, \software\windows\ISP, in the repository. The Support Pack tools are located on the HP SmartSetup CD in the \contents\supportpack\isp directory. Edit the PostInstall.cmd file located at \software\windows\, adding command line to install each tool.
  • Page 35 Copy driver files into these directories. If you copied a driver to the TEXTMODE directory, you should also copy it to the other-files/$OEM$/$1 directory. The final repository may resemble the following structure (operating system files were removed for the sake of brevity): readme.txt SSTK_DeploymentGuide.pdf +---boot_files...
  • Page 36 \---other-files \---$OEM$ \---$1 \---PnPDrivers \---Network \---intelNIC e1000645.cat e1000645.din e1000645.inf e1000645.sys e1000msg.dll EtCoIn64.dll generic.dll install.xml intlnc64.dll Ncs2Setp.dll PROUnstl.exe \---neterion \---windows \---2003-enterprise \---other-files \---$OEM$ \---$1 \---PnPDrivers \---Network \---neterion netxena.cat netxena.inf xena64.sys +---Others \---storage +---emulex \---windows \---2003-enterprise +---boot-files \---$OEM$ \---TEXTMODE lpscsi lpsimdev.cat lpsimdev.inf lpxftr.sys lpxnds.cat lpxnds.dll...
  • Page 37 +---qlogic4q \---windows \---2003-enterprise +---boot-files \---$OEM$ \---TEXTMODE ql2300.cat ql2300.sys ql2x00.inf txtsetup.oem \---other-files \---$OEM$ \---$1 \---PnPDrivers \---Storage \---qlogic4g ql2300.cat ql2300.sys ql2x00.inf ql2xhai2.dll qlogic qlogic txtsetup.oem +---sa6400 \---windows \---2003-enterprise +---boot-files \---$OEM$ \---TEXTMODE cpqciss.dll cpqcisse.cat cpqcisse.inf cpqcisse.pdb cpqcisse.sys cpqcissm.cat cpqcissm.dll cpqcissm.inf cpqcissm.pdb cpqcissm.sys install.xml txtsetup.oem \---other-files \---$OEM$...
  • Page 38 cpqcissm.sys install.xml txtsetup.oem \---saP600 \---windows \---2003-enterprise +---boot-files \---$OEM$ \---TEXTMODE generic.dll hpcisss2.cat hpcisss2.sys hpcissx2.inf txtsetup.oem \---other-files \---$OEM$ \---$1 \---PnPDrivers \---Storage \---saP600 generic.dll hpcisss2.cat hpcisss2.sys hpcissx2.inf txtsetup.oem +---software +---EFI_TOOLS +---networking ftp.efi ifconfig.efi ping.efi route.efi SETUPLDR.EFI tcpipv4.efi \---toolkit Readme.txt version.txt \---PYTHON1.5 \---windows PostInstall.cmd \---ISP cp006523.exe cp006535.exe...

  • Page 39: Set Up Driver Installation

    deploy.sh main_toolkit_launch.sh raid1-1si.sh sstk.conf sstkw_functions windows-setup.sh \---utilities CLMChecking allboards.xml cfggen conrep conrep.xml cpqacuxe-X.YY-Z_ia64.tar.gz efibootmgr efivar gen-setupldr-options getuuid hplpcfg hpqlarep hpshowdisk hwdisc hwquery ifhw parted hpsetacpi sstkencrypt windows \---sstkencrypt.exe Set up driver installation To install an OEM driver, the SSTK must copy the driver files from the repository to the target server and update the unattended file which instructs Windows setup to install the driver.
  • Page 40 controller must be loaded. This is specified in the [MassStorageDrivers] and [OEMBootFiles] sections in the unattended file. When you define the target disk where Windows will be installed (either setting the variable $DISK in sstk.conf or through the SSTK menu) the hpshowdisk utility automatically retrieves the controller type, which can be difficult to obtain if the system has a large number of disks and controller types.

  • Page 41: Setting Up The Toolkit Environment

    3 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 Windows setup script to trigger the operating system installation.

  • Page 42: Edit Bootia64.Conf

    Edit bootia64.conf The bootia64.conf file configures how the SSTK boot loader (bootia64.efi) loads the preboot environment. The bootia64.conf file distributed with SSTK is configured to load the Linux PE image and typically does not need to be modified. loader_name = elilo.efi acpi_mode = linux #OS to ACPI mode map (OS detection feature).

  • Page 43: Image Options

    Table 3-1 Global options (continued) Global Option Description Set level of verbosity [0-5]. Default is 0 (no verbose). verbose=number Set global root filesystem for Linux/ia64. root=filename Force root filesystem to be mounted read-only. read-only Append a string of options to kernel command line. append=string Name of initrd file initrd=filename...
  • Page 44 Table 3-3 SSTK command line options (continued) SSTK Option Description Encrypted password created by the sstkencrypt tool for SMB/CIFS repositories ssstk_encryptpass= over a network for security. This option overwrites the password string in encryptpass sstk_mount_option. NOTE: The password length is limited to a maximum of 16 characters. Name of main launch script ssstk_script=filename Default response to the toolkit launch script prompt (win, readhwconfig or bash)

  • Page 45: Review Main_Toolkit_Launch.sh

    NOTE: The repository password can have up to 16 characters, including only uppercase letters, lowercase letters, and digits. No special characters are supported. Special characters include: !, @, #, $, %, ¨, &, *, (, ), ', ", _, +, =, -, {, }, [, ", á, à, â, ã, é, è, ê, í, ì, î, ó, ò, ô, õ, ú, ù.

  • Page 46: Edit Windows-Setup.sh

    $UTILITIES/hpqlarep /S "${CONFIGDIR}/hba.ini Run the hplpcfg utility to enable or disable the EFI boot setting on HP Emulex HBAs. The script writes this data to the hba-emulex.ini file. $UTILITIES/hplpcfg /le "${CONFIGDIR}/hba-emulex.ini • When you select lsi, the raid1-lsi.sh script runs to create RAID1 to the LSI 1068 controller.
  • Page 47 — On drives less than 16 GB, the MSR is 32 MB — On drives greater than or equal to 16 GB, the MSR is 128 MB The windows-setup.sh script defines the size of the MSDATA partition as the remainder of free space on the disk after the MSR on disks not greater than 32 GB.

  • Page 49: Setting Up The Boot Mechanism

    .ima file of 50 MB. Therefore, do not use a partition greater than the capacity of a CD (700 MB). HP suggests a partition size in the range of 20 MB to 512 MB.

  • Page 50: Create The Iso Using Roxio

    Figure 4-1 EFI Directory Create the ISO using Roxio This section shows you how to use the Roxio Easy CD Creator program to create an ISO file containing the bootable image along with the files used by the toolkit. Launch Easy CD Creator and select Disc Creator Classic (Figure 4-2).

  • Page 51: Disc Creator Classic Main Window

    Figure 4-2 Disc Creator Classic Main Window Drag and drop the other files you want on the CD to the Project area (Figure 4-3). Figure 4-3 Roxio Project Area Using a bootable CD/DVD...

  • Page 52: Create The Iso Using Nero

    Select File->Create Disc Image (Figure 4-4). In the dialog box, enter a file name, select the path, and click Save to finalize. Figure 4-4 Create Disc Image Select File->Burn Disc from Image. Create the ISO using Nero To use Nero to create the ISO file: Launch Nero, select the Data icon, and select Make a data disc.

  • Page 53: New Compilation Window

    Figure 4-5 New Compilation Window Select the Burn tab (Figure 4-6). In the Action group, ensure only the Write option is checked. From the Write Method dropdown menu, select Track-At-Once. Check Use Multiple Recorders. Figure 4-6 Burn Tab Click New. The Nero Burning ROM screen appears. Copy the image files to the left pane of the Nero Burning ROM explorer.

  • Page 54: From A Linux Workstation

    From a Linux workstation The following sections show you how to create a bootable CD/DVD from a Linux system. Create a bootable disk image The SSTK includes the files you need to create a bootable disk image. Creating the disk image involves copying these boot files to a small FAT partition and creating the image (.img) file.

  • Page 55: Create The Iso File

    Create the ISO file The mkisofs command is used to create an ISO file. The following table describes the arguments used with this command. Table 4-1 mkisofs command options Option Description Specifies the ISO file. -o linuxbootCD.iso Specifies boot.img as the bootable disk image. -b boot/boot.img Specifies the volume label of the CD.

  • Page 56: Create A Bootable Usb Flash Device On A Linux Workstation

    Create a bootable USB flash device on a Linux workstation To create a bootable USB flash device: Insert the USB flash device and determine the name of the device. Format the USB flash device with FAT file system: mkdosfs -I /dev/sda1 Create a directory and mount the USB flash device on this directory: mkdir –p /mntmount /dev/sda1 /mnt Create the bootable directory for Integrity servers (/efi/boot):...

  • Page 57: Using Usb Flash Device As External Media

    Figure 4-9 Boot Configuration Selection Window In the EFI Boot Manager, select to boot from the Linux USB device (Figure 4-10). Figure 4-10 Boot from Linux USB Device Window Using USB flash device as external media If the USB device is /dev/sda, you can mount your MS-DOS formatted USB device using the following command: mount –t msdos /dev/sda /mnt Using network boot...

  • Page 58: Setting Up A Windows Network Boot Server

    Setting up a Windows network boot server The DHCP server leases dynamic IP addresses. An extension to the DHCP protocol, PXE, allows a system to boot from an initial operating system image bootstrap program downloaded from a TFTP server. To boot a remote operating system image: The client machine boots with a NIC as the first boot device.

  • Page 59: Setting Up A Tftp Server

    host <hostname> { fixed-address <IP>; hardware ethernet <MAC> The next-server command tells the DHCP client where to send the TFTP request. The filename command tells the DHCP client which file to get. In this example, the file is bootia64.efi. When you have finished editing the dhcpd.conf file, restart the dhcpd process: /etc/init.d/dhcpd restart Setting up a TFTP server Most Linux installations include a TFTP server and an automated method of launching the server...

  • Page 60: Setting Up The Integrity Server For Pxe-Enabled Boot

    /tftpboot/rootfs.gz /tftpboot/linux Make sure the ELILO.conf file is configured as stated in Chapter 3 (page 41). Setting up the Integrity server for PXE-enabled boot Be sure the Integrity server has a PXE-compliant NIC and is physically connected to a configured DHCP server.
  • Page 61 On a cell-based Integrity server, a special system ACPI flag must be properly set before the operating system is started. When SSTK is running it always sets the ACPI mode to the single-pci-domain or default state and sets to the Windows mode when deploying Windows. If you are MANUALLY rebooting the server to start the Windows operating system, change the ACPI mode to windows using hpsetacpi from SSTK environment (LinuxPE) or the acpiconfig utility from EFI environment.

  • Page 63: Utilities Reference

    5 Utilities Reference This chapter contains reference information and usage examples for the utilities provided in the toolkit. You can get online help for each utility by using the -h or -? option. cfggen Synopsis cfggen Description The cfggen utility is a RAID Linux configuration utility for LSI controllers, and a counterpart of cpqacuxe.
  • Page 64 Device Function RAID Support : Yes ------------------------------------------------------------------------ IR Volume information ------------------------------------------------------------------------ ------------------------------------------------------------------------ Physical device information ------------------------------------------------------------------------ Initiator at ID #63 Target on ID #1 Device is a Hard disk Enclosure # Slot # Target ID State : Ready (RDY) Size (in MB)/(in sectors) : 57231/117210240 Manufacturer : ATA...

  • Page 65: Clmchecking

    CLMChecking Synopsis CLMChecking Description The CLMChecking utility performs memory optimization in cellular systems. On cellular systems the available system memory can be accessed using two different approaches: interleaved memory, meaning that the average memory latency is constant for all processes in the system;...

  • Page 66: Conrep

    conrep Synopsis conrep ( -l [-f DAT file] [-F] | -s [–x XML FILE] [-f DAT file] | -c | -d | -h ) [-v] 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 67: Return Codes

    <ev>DBPR####</ev> </section> -<section name="EFI_Non-Cell_variables"> <ev>AutobootRetry</ev> </section> -<section name="EFI_Cell_variables"> <ev>AutobootRetried</ev> </section> </conrep> Return codes Table 5-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.

  • Page 68: Cpqacuxe

    cpqacuxe Synopsis • Capture: CPQACUXE -C FILENAME [-internal | -external] -E FILENAME • Input: CPQACUXE -I FILENAME [-internal | -external] [reset] -E FILENAME • Input with reset: CPQACUXE -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 69: Options

    StripeSize = 256 ArrayAccelerator = Enabled ; HBA SSP Specifications HBA_WW_ID= 10000000C9272B34 ConnectionName= TestConn HostMode= Windows Options Table 5-5 cpqacuxe Options Option Description Specifies the capture file. The capture filename is optional. If no capture file is specified, the default -C FILENAME capture file is acucapt.ini in the ACU working directory.

  • Page 70: Automatic Script File Format

    Controller, or HBA_WW_ID option are assumed to belong to the HBA being defined. 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 71 Table 5-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 MSA1500 connected to a SA6402 might be found at “Slot 4:2,”...

  • Page 72: Custom Script File Format

    Table 5-6 Automatic 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 will remain 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 73: Custom Script File 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 5-7 Custom script file options Option Value Defines if you are changing existing arrays and logical drives or adding new ones.
  • Page 74 Table 5-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 75 Table 5-7 Custom 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 will remain unchanged. • Low • Medium • High Specifies the Expand Priority. This option is not required. If this option is not ExpandPriority specified, the Expand Priority will remain unchanged.
  • Page 76 Table 5-7 Custom script file options (continued) Option Value Restricts the array and operations on the array to the specified type of physical DriveType drive. • SCSI: Use only SCSI drives. • SAS: Use only SAS drives. • SATA: Use only SATA drives. Specifies the spare drives for the array.
  • Page 77 Table 5-7 Custom script file options (continued) Option Value Specifies the Max Boot setting (Sectors Per Track) for the logical drive. The Sectors Sectors option is not required. If the logical drive is new, the default is 32. If the logical drive already exists, then the default is the current Sectors setting on the logical drive.

  • Page 78: Error Reporting

    • 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.

  • Page 79: Cpqacuxe Error Codes

    Table 5-8 cpqacuxe Error Codes Code Error Reason Success Success Problem spawning ACU process (user is not authenticated to General error use ACU or ACU is already running). 2866 Error opening capture file. Failure opening capture file '%s' 2867 Error opening input file. Failure opening input file '%s' 2868...
  • Page 80 Table 5-8 cpqacuxe Error Codes (continued) Code Error Reason 2826 The array command is missing from the script file. Some Array not specified commands were found that require an array to work on. 2827 The Array ID in the script file does not match the Array ID of New Array ID does not match the newly created array.
  • Page 81 Table 5-8 cpqacuxe Error Codes (continued) Code Error Reason 2839 The controller does not support migration, or the current Cannot migrate Logical Drive configuration of the controller does not allow migration to occur. Raid 2840 The controller does not support migration, or the current Cannot migrate Logical Drive configuration of the controller does not allow migration to occur.
  • Page 82 Table 5-8 cpqacuxe Error Codes (continued) Code Error Reason 2851 The entered Raid Array ID is invalid. The Raid Array ID can Invalid Raid Array ID only consist of the following characters: a-z, A-Z, 0-9, ! @ # * ( ) , - _ + : .

  • Page 83: Efibootmgr

    efibootmgr Synopsis efibootmgr [command]... [option]... Description The efibootmgr utility is used from a script file to manager the EFI Boot variables. The efibootmgr utility is used for creating or destroying the EFI BOOT variables and to update the BOOT NEXT, BOOT ORDER, and TIMEOUT variables. The BOOT ORDER variable defines the boot entries sequence to be shown in menu.

  • Page 84: Efibootmgr Command Line Input

    Table 5-10 Commands (continued) Commands Description Boot manager display label (defaults to “Linux”). -L | --label label Partition number that containing boot loader (defaults to 1). -p | --part part Be quiet. -q | --quiet Does not write to NVRAM; writes to filename. --test filename Passes extra args as UCS-2 (default is ASCII).

  • Page 85: Efivar

    efivar Synopsis efivar Description The efivar utility is used to set EFI variables from SSTK LinuxPE. Options Option Description The EFI variable GUID (default is 8be4df61-93ca-11d2-aa0d-00e098032b8c) -g | --guid The EFI variable name -n | --name The EFI variable value -v | --value Deletes EFI variable -d | --delete...

  • Page 86: Gen-Setupldr-Options

    gen-setupldr-options Synopsis gen-setupldr-options –d device [-p number] -w path [-o file] [-h] Description The gen-setupldr-options utility generates options for the setup loader, which launches the Windows installation process. Use gen-setupldr-options along with the efibootmgr utility. Options Table 5-12 gen-setupldr-options Options Options Description Sets the device file.

  • Page 87: Getuuid

    getuuid Synopsis getuuid Description The getuuid utility retrieves the UUID (Universally Unique ID) used to identify a storage device or a single partition. Options Option Description The disk to retrieve information from disk Partition number Shows GUID of partition type (EFI, hpsp, and so on) getuuid...

  • Page 88: Hpia64Info

    hpia64info Synopsis hpia64info -v Description The hpia64info utility displays information about management processor and system firmware. Options The hpia64info utility has one option, -v. This option displays the version of the hpia64info utility. Output The hpia64info utility displays the following management processor information: •...

  • Page 89: Hplpcfg

    hplpcfg Synopsis hplpcfg Description The hplpcfg utility enables or disables the EFI or BIOS boot setting on Emulex 2 GB or 4 GB Fibre Channel Host Bus Adapters (FC HBA). Options Table 5-14 hplpcfg Options Option Description Saves the HBA configuration to filename. filename Loads the HBA configuration from filename filename...

  • Page 90: Hpqlarep

    hpqlarep Synopsis hpqlarep Description The hpqlarep utility enables or disable the EFI or BIOS boot setting on QLogic 2 GB or 4 GB HBAs. Options hpqlarep /s filename saves the HBA configuration to filename. hpqlarep /l filename loads the HBA configuration to filename Format The configuration file for EFI boot setting has the following format: •...

  • Page 91: Hpsetacpi

    hpsetacpi Synopsis hpsetacpi Description The hpsetacpi tool sets the ACPI mode to Windows or Linux, according to command line parameter informed. Options Table 5-15 hpsetacpi Options Option Description The new ACPI configuration mode. Available choices include Windows, Longhorn or Linux. Mode Displays debug info Displays the version...

  • Page 92: Hpshowdisk

    hpshowdisk Synopsis hpshowdisk Description The hpshowdisk utility helps to identify disks recognized by the system. This utility can be useful when the system has a large number of disks, typically on SAN architectures. Besides device name and size, the utility includes information about disk controller, SAN storage devices WWIDs, and SAN logical disks LUNs.

  • Page 93: Hpshowdisk Utility

    Figure 5-1 hpshowdisk Utility hpshowdisk...

  • Page 94: Hwdisc

    hwdisc Synopsis hwdisc -f[path]filename 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 •...
  • Page 95 <SubID>0E11001E</SubID> </PCIDevice> <PCIDevice num=”1”> <Bus>0</Bus> <Device>4</Device> <Function>0</Function> <Id>0E11B203</Id> <SubID>0E11B206</SubID> </PCIDevice> </PCIDevices> </ServerInformation> </HWDiscovery> hwdisc...

  • Page 96: Hwquery

    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 97: Ifhw

    ifhw Synopsis ifhw [path]hwdiscfilename [path]allboards.xml expression Description The ifhw utility is executed from a script file, in conjunction with other utilities, to control the install process. The ifhw utility makes 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 exit status of the tool, which the hosting script can use to conditionally perform actions.

  • Page 98: Ifhw Operators

    Table 5-20 ifhw Operators Operator or Result term 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.

  • Page 99: Parted

    parted Synopsis parted [-v | -i | -s | -h]... [DEVICE [COMMAND [PARAMETER]...] ...] Description The parted utility manages disk partitions. It allows you to make a GPT partition table and to create all the partitions needed. It is also able to create hidden partitions and change the partition GUID to HPSP, MSRES, MSDATA, and ESP.
  • Page 100 To set the ESP partition GUID in the first partition on the table: parted -s /dev/cciss/c0d0 set 1 boot on • To set the name of the second partition of the /dev/cciss/c0d0 partition table to “HP Service Partition” use: parted -s /dev/sda name 2 “HP Service Partition”...

  • Page 101: Sstkencrypt

    sstkencrypt Synopsis sstkencrypt Description The sstkencrypt utility is used to encrypt the repository password. After encrypted, it should be set in elilo.conf, resulting in a more secure connection over the network. Example SSTK-v.2.7-8# ./sstkencrypt Type the repository password: password Set the 'encryptpass' parameter in SSTK elilo.conf to: 24732a2730252d75 sstkencrypt...

  • Page 103: A Support Matrix

    HP Integrity rx8640 • HP Integrity Superdome sx1000 • HP Integrity Superdome sx2000 • HP Integrity BL860c server blade • HP Integrity BL870c server blade • HP Virtual Machine systems Supported LSI and SmartArray SCSI/RAID controllers Table A-1 SCSI Controllers...

  • Page 104: Supported Emulex And Qlogic Fiber Channel Controllers

    Supported Emulex and QLogic Fiber Channel controllers Table A-3 QLogic controllers Controller Part Number QLogic 4GB 1P QLA2460 AB429A QLogic 4GB 2P QLA2462 AB379A QLogic 4GB 2P QLA2462 AB379B QLogic 4GB PCIe 1P AE311A QLogic 4GB DC PCIe 2P AE312A QLogic 4GB Mezz 403619-B21 Table A-4 Emulex controllers...

  • Page 105: Supported Storage

    Supported storage • SW43xx • MSA30/SW44xx • MSA 50 • MSA 60 • MSA 70 • MSA 600 • MSA 700 • MSA 1000 • MSA 1500 • • • SB40c Supported storage...

This manual is also suitable for:

Integrity rx2620Integrity rx2660Integrity rx4640Integrity rx6600Integrity rx7620Integrity rx7640 ... Show all

Table of Contents