HP BL860c Administrator's Manual
  1. Manuals
  2. Brands
  3. HP Manuals
  4. Software
  5. Integrity BL860c
  6. Administrator's manual
HP BL860c Administrator's Manual

HP BL860c Administrator's Manual

Microsoft windows server 2008 sp2 and windows server 2008 r2 on integrity servers
Hide thumbs Also See for BL860c:
Table of Contents

Advertisement

Quick Links

Download this manual See also: User and Service Manual, Operating Manual
Microsoft Windows Server 2008 SP2 and
Windows Server 2008 R2 on HP Integrity
Servers
SmartSetup Scripting Toolkit Administrator's
Guide
Abstract
This document describes how to use the SmartSetup Scripting Toolkit (SSTK). This document is for system administrators who
write scripts to automate hardware configuration and software installation operations for HP Integrity® server deployments.
You must have some expertise in unattended installations of Windows Server 2008 and in configuring Integrity server hardware.
HP Part Number: T2369-96019
Published: April 201 1

Advertisement

Table of Contents
loading

Related Manuals for HP BL860c

Summary of Contents for HP BL860c

  • Page 1: Windows Server 2008 R2 On Hp Integrity Servers

    Microsoft Windows Server 2008 SP2 and Windows Server 2008 R2 on HP Integrity Servers SmartSetup Scripting Toolkit Administrator's Guide Abstract This document describes how to use the SmartSetup Scripting Toolkit (SSTK). This document is for system administrators who write scripts to automate hardware configuration and software installation operations for HP Integrity® server deployments. You must have some expertise in unattended installations of Windows Server 2008 and in configuring Integrity server hardware.
  • Page 2 © Copyright 201 1 Hewlett-Packard Development Company, L.P Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.21 1 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

    Contents 1 Overview....................6 Minimum requirements......................6 SSTK environment........................6 SSTK boot image.........................7 SSTK repository........................7 The deployment process......................7 Extracting the SSTK package......................8 2 Creating an SSTK boot image..............12 Editing the SSTKStart.cmd file....................12 Installing OEM drivers in the boot image...................13 Creating the boot image......................13 Setting up the boot mechanism....................14 Creating a bootable CD/DVD or virtual media..............14 Creating a Bootable USB flash device..................16...
  • Page 4 Enabling a boot device on a SAN....................30 Increasing security in SSTK.......................31 Encrypting the repository password..................31 Setting permissions for repository access................32 Checking the CLM mode......................32 Enabling Max Payload Size.....................33 6 Utilities reference..................34 conrep..........................34 Synopsis...........................34 Description........................34 Options..........................34 Examples..........................35 Return codes........................35 hpacuscripting........................36 Synopsis...........................36 Description........................36 Options..........................37 Sample Script File......................37...
  • Page 5 sstkencrypt..........................50 Synopsis...........................50 Description........................50 Example...........................50 sstkmount..........................50 Synopsis...........................50 Description........................50 Parameters........................50 Example...........................51 7 Support and other resources..............52 Contacting HP........................52 Documentation feedback......................52 Typographic conventions......................52 A Support Matrix..................53 Contents...

  • Page 6: Overview

    1 Overview The SmartSetup Scripting Toolkit (SSTK) provides utilities and scripts that simplify the tasks of deploying Windows on HP Integrity® servers by automating hardware configuration and software installation. Using the SSTK, you can deploy a large number of servers efficiently by replicating a server configuration and performing a Windows unattended installation.

  • Page 7: Sstk Boot Image

    Figure 1 Simple SSTK Deployment Scenario CommandPrompt ReadHWConf ApplyHWConf, ApplySASConf and Deploy SSTK repository SSTK boot image (Workstation) (Target Server) You use a workstation to unpack the toolkit, edit the configuration files, and set up the boot mechanism. The workstation typically hosts the SSTK repository, which holds the configuration files, scripts, utilities, and Windows installation files.

  • Page 8: Extracting The Sstk Package

    Typically, you perform steps 1 and 2 only once. Steps 3 and 4 are performed multiple times, depending on the number of target servers you need to deploy. The following section describes how to extract the SSTK package. The remaining chapters describe the other steps. Extracting the SSTK package The SSTK software package is a self-extracting package component.
  • Page 9 applied to Smart Array controllers with the hpacuscripting tool. This file is created when the readhwconfig option is executed. A file into which the conrep tool saves conrep.dat the values of the EFI variables contained in the conrep.xml configuration file. This file is created when the readhwconf action is executed.
  • Page 10 CaptureArrayConfiguration capture the Smart Array RAID configuration. Applies RAID 1 configuration to an LSI ApplySaSConf 1068 controller on BL860c systems and RAID1 + RAID1 configuration to an LSI 1068 controller on and BL870c systems. “applysasconf action” (page 21). Manages the SSTK log system. See “SSTK...
  • Page 11 After Windows installation, the post-Install CopyISP, CopySmartUpdate, script calls the Integrity Support Pack (ISP) PostInstall2008SP2, installer if ISP installation files are PostInstall2008R2 available on the repository. For information on configuring the SSTK repository, see “Uploading the Windows installation files” (page 22).

  • Page 12: Creating An Sstk Boot Image

    2 Creating an SSTK boot image After you set up the workstation, you create an SSTK boot image. The boot image starts the target server in order to execute an SSTK action. NOTE: The network location of the SSTK repository share is configured in the boot image. If you want to change or access a different repository share, you must edit the SSTKStart.cmd file and create the boot image again.

  • Page 13: Installing Oem Drivers In The Boot Image

    SSTK only supports DHCPv6 and Router Advertisement IPv6 addresses. If you need to use the IPv6 address directly, you must convert the IPv6 address to the Microsoft ipv6-literal namespace format. Convert the colon symbol (:) to the hyphen symbol (-) and append ipv6-literal.net .

  • Page 14: Setting Up The Boot Mechanism

    NOTE: The repository must be on the same letter drive on which the AIK was installed. Creates the default path for EFI booting in the winpe\iso folder as follows: efi\boot\bootia64.efi Where: bootia64.efi is the SSTK boot loader utility. After creating a boot image, you must set up a boot mechanism (CD/DVD, USB or PXE). See “Setting up the boot mechanism”...
  • Page 15 Figure 4 Configuring virtual media using the iLO interface Figure 5 shows this process for the iLO 3 interface. Setting up the boot mechanism...

  • Page 16: Creating A Bootable Usb Flash Device

    Figure 5 Configuring virtual media using the iLO 3 interface When the EFI Shell starts at the target server, a virtual file system is available with the SSTK boot files. You can add a new boot entry using the EFI Boot Manager. Creating a Bootable USB flash device To create a bootable USB flash device, use the xcopy command to copy the appropriate files from your workstation to the USB flash device.

  • Page 17: Windows Deployment Services

    Figure 6 Sample SSTK Network Environment CORPNET Gateway/VPN Isolated network - 10.51.201.0/24 Target / dynamic IP Active Directory / DHCP / SSTK Repository Windows Deployment Services Windows Deployment Services (WDS) is included in Windows Server 2003 SP2. You can integrate the SSTK with the WDS Server Components, which include a Pre-Boot Execution Environment (PXE) server.
  • Page 18 Enter the name and description of the boot image or accept the defaults. When the image copy has completed successfully, click Finish to exit the wizard. To add another image, repeat the preceding steps. WDS now displays a boot menu. NOTE: You must use the default IA64 boot loader, which is already set to bootmgfw.efi in WDS.

  • Page 19: Configuring An Sstk Action

    3 Configuring an SSTK action After you create the boot image, you must configure an SSTK action. When the target server boots up, the SSTK boot image initiates the SSTK action (ReadHWConf, ApplyHWConf, ApplySASConf, CommandPrompt, SetHBABootDevice, or Deploy) specified in the repository. The process runs without user intervention.

  • Page 20: Configuring Conrep

    Configuring conrep By default, the conrep utility reads the following EFI variables as configured in the conrep.xml file and saves the variable data saved to conrep.dat file: Lang Default UIOption CPUTreadControl Timeout AutobootRetry or AutobootRetries To read (replicate) another EFI variable, edit the conrep.xml file and add it. Use the EFI Shell dmpstore command to list the variables and their values on the target server.

  • Page 21: Applysasconf Action

    When the default_action variable is set to applysasconf, the ApplySASConf.cmd script executes. If the target system is a BL860c, it applies RAID1 array configuration. If it is a BL870c, it applies RAID1 + RAID1 array configuration. Choosing the installation disk By default, the toolkit installs Windows at the first disk (disk ID 0).

  • Page 22: Deploy Action

    Edit the file with a text editor or by using SIM as explained in “Modifying the answer file” (page 24). NOTE: For Storage Area Network (SAN) disks, make sure the installation disk is a boot device (available on EFI for booting). For information on how to set a boot device, see “Enabling a boot device on a SAN”...

  • Page 23: Uploading The Integrity Support Pack 7.1

    After the specific Windows folder exists, copy the contents of the Windows installation CD to the respective folder under os\windows. Uploading the Integrity Support Pack 7.1 The Integrity Support Pack (ISP) provides a set of tools and device drivers for Integrity servers that can be automatically installed after Windows installation.

  • Page 24: Uploading Oem Device Drivers

    Edit the diskpart\default_layout_2008.txt file Uploading OEM device drivers Adding OEM drivers for Windows Server 2008 SP2 and Windows Server R2 installation in the drivers repository folder is not necessary. The Windows Server 2008 SP2 and Windows Server R2 setup uses the OEM drivers installed in the SSTK boot image. See “Installing OEM drivers in the boot image”...

  • Page 25: Editing The Sstkconfig.cmd File

    Figure 10 Editing the Windows Server 2008 R2 answer file using WSIM Figure 1 1 Adding Windows packages to the answer file using WSIM For information about Windows Server 2008 SP2 and Windows Server 2008 R2 answer files and WSIM, see the AIK User’s Guide. Click Program Files Microsoft Windows AIK Documentation Automated Windows Installation Kit User's Guide.

  • Page 26: Editing The Default_Layout_2008.Txt File

    Set to the name of the folder in which the Windows installation files are os_deploy stored: 2008-server-sp2 or 2008-server-r2. By default, set to en. Specifies the Windows target language. For Japanese languageid Windows Server 2008 deployments, set this to jp. Editing the default_layout_2008.txt file The default_layout_2008.txt file is located in the scripts\diskpart folder.

  • Page 27: Booting The Server

    4 Booting the server After configuring an SSTK action, you are ready to boot the target server. This chapter describes how to boot the server (model and target), how to monitor the deployment process, and provides some troubleshooting information. Boot instructions This section describes how to boot from the CD/DVD, USB device, and from the network Booting from the CD/DVD Insert the CD in the CD drive Integrity server.

  • Page 28: Sstk Log File

    SSTK log file When the SSTK scripts run, SSTK records event messages and errors in a log file. Each time you boot the target server, a new log file is created with the proper time stamp. SSTK creates a file with the following name: SystemName-SerialNumber-yyyymmdd-hhmmss.log Where:...
  • Page 29 console output. In order to access the server console, type the MP IP address in Internet Explorer (for iLO interface) or in a telnet session or SSH client (for MP interface). If you must force the target server to reboot, you can type restart at the WinPE SAC or use the MP command line interface.

  • Page 30: Advanced Topics

    5 Advanced topics This chapter describes the following advanced topics: Customizing the SSTK boot image Enabling a boot device on a SAN Increasing security in SSTK Checking the CLM mode Enabling the maximum payload size Customizing the SSTK boot image The mkbootimg.cmd script executes all the steps needed to create a customized SSTK WinPE 3.0 image.

  • Page 31: Increasing Security In Sstk

    You can obtain the BootDeviceWWID and BootDeviceLUN information from the hpacuscripting output, as follows: ; Controller Specifications ; Controller HP MSA1500 CS Controller Controller= WWN 500508B30090F5B1 SSPState= Disabled ; Unassigned Parallel SCSI Drives ; 1:5 (36.4 GB),1:6 (36.4 GB) ; Array Specifications Array= A ;...

  • Page 32: Setting Permissions For Repository Access

    repository_letter=y: For information on valid characters for the repository password, see “Editing the SSTKStart.cmd file” (page 12). Setting permissions for repository access To increase security, restrict write permission for some folders in the SSTK repository. This also guarantees the integrity of files that must have read-only permission. The repository structure allows users to have read-write permissions for the data_files folder only.

  • Page 33: Enabling Max Payload Size

    NOTE: SSTK does not provide a tool to configure Cell-Local Memory mode. Enabling Max Payload Size The Max Payload Size (MPS) enables or disables hardware optimizations to the installed operational system. Enable MPS on the EFI Shell by using the following command: EFI Shell>...

  • Page 34: Utilities Reference

    6 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. conrep Synopsis conrep { -s | -l | -c | -d } [-F] [-v] [-f data file] [-x XML file] [-- ] [--version ] [-h ] Description The conrep utility replicates the configuration data stored in the EFI variables.

  • Page 35: Examples

    Examples Example 1 Sample conrep.dat file <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <conrep_data> <section name="EFI_general_variables"> <Lang>4c 00 61 00 6e 00 67 00 00 ...</Lang> <Default>44 00 65 00 66 00 61 00 ...</Default> <CPUThreadControl>43 00 50 00 55 00 54 ...</CPUThreadControl> <Timeout>54 00 69 00 6d 00 ...</Timeout>...

  • Page 36: Hpacuscripting

    Table 2 conrep Return Codes (continued) Value Meaning Cause Action Usage error An error occurred while using Run conrep -h to display available conrep for some unexpected options and usage. reason, such as the wrong parameters. Data file not found The data file was not found in the Put the data file in the same directory as current directory or in the path...

  • Page 37: Options

    Options Captures the current configuration to a script file. The default file is acuoutput.ini. Inputs configuration information from a script file. The default file is acuinput.ini. Limits the operation to internal controllers. This is the default. -internal NOTE: Do not use this option to capture information about Storage Area Network controllers.

  • Page 38: Error Reporting

    WriteCache= 50 RebuildPriority= Low ExpandPriority= Low SurfaceScanDelay= 15 ; Array Specifications Array= A ; Array Drive Type is SAS ; 1E:1:1 (36 GB),1E:1:2 (36 GB),1E:1:3 (36 GB) Drive= 1E:1:1,1E:1:2,1E:1:3 OnlineSpare= No ; Logical Drive Specifications LogicalDrive= 1 RAID= 5 Size= 69399 Sectors= 32 StripeSize= 16 ArrayAccelerator= Enabled...
  • Page 39 Table 4 hpacuscripting Error Codes Warning Message Reason Code — No error exists. The program completed successfully. 2053 The new configuration requires more transformations than are Too many coinciding possible at one time. For example, you cannot expand a logical expansion, migration, or volume and transform its RAID level at the same time.
  • Page 40 Table 4 hpacuscripting Error Codes (continued) Warning Message Reason Code 2836 The script file specifies a logical drive ID that is not the first unused New Logical Drive ID does ID in the sequence. For example, if the controller has only Logical not match the next available Drive 1 and the script file attempts to create Logical Drive 3 Logical Drive ID...
  • Page 41 Table 4 hpacuscripting Error Codes (continued) Warning Message Reason Code 2865 The preferred path specified is not a valid chassis slot for an Invalid Preferred Path available active controller, or the controller is not available. 2866 — Failure opening capture file text 2867 —...

  • Page 42: Hpchkclm

    Table 4 hpacuscripting Error Codes (continued) Warning Message Reason Code 3019 ACU cannot create an array unless physical disks are specified Cannot create Array - no in the input file DRIVE parameter. physical disks specified 3020 For the specified operation, ACU requires SSP to be supported SSP must be enabled in order and enabled.

  • Page 43: Options

    Options Eliminates the press any key prompt for automation purposes. Suppress the event logging feature. Example C:\>hpchkclm.exe HPCHKCLM - HP NUMA Configuration Checker Version 1.2.0.0, built May 18 2010 16:58:47 Manufacturer: hp Product name: Integrity rx2800 i2 SKU: AH395A BIOS version: 01.09 BIOS date: 10/18/2010 Computer name: MININT-8K9IQ46 Windows version: 6.1...

  • Page 44: Examples

    Outputs the PCI ID for the device in the vendor:device:subvendor:subdevice format. Displays the disk LUN. Displays the size of the disk, in bytes. Do not use the Altiris showdisk command to sort the disk list. -n | -no_showdisk Outputs the hpshowdisk utility version. -v | --version Displays the disk WWID in 16-digit hexadecimal format.

  • Page 45: Hwdiscovery

    Table 5 hpshowdisk return codes (continued) Return Code Name Meaning ERROR_NO_SHOWDISK The Altiris showdisk utility was not found. ERROR_INVALID_DISK An invalid disk index was specified with the i option. ERROR_INVOKING_SHOWDISK A problem occurred while invoking the Altiris showdisk utility. ERROR_NO_MEMORY The utility tried to allocate memory and failed.

  • Page 46: Example

    Displays the utility version. -v | --version Example A sample hwdisc.dat output file is as follows: <!-- generated by hwdiscovery Windows for IPF version 1.01 --> <HWDiscovery version=”1.01”> <ServerInformation> <SystemName>Server rx2660</SystemName> <SerialNumber>US43880166</SerialNumber> <AssetTag>abcdef<AssetTag> <EFIFw>5.48</EFIFw> <BMCFw>04.03</BMCFw> <MPFw>E.03.30</MPFw> <Cells>0</Cells> <VMHostIPAddress></VMHostIPAddress> <Blade> <RackName></RackName> <EncName></EncName>...

  • Page 47: Hwquery

    Table 6 hwdiscovery error codes (continued) Value Description Error creating XML file General error hwquery Synopsis hwquery hwdisc.dat allboards.xml [query]... 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. The hwquery utility cannot alter environment variables directly.

  • Page 48: Examples

    [path]allboards.xml 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.” Specifies the query expression. expression Examples The ifhw utility can use XML files as input to query the hardware discovery file. For example: ifhw hwdisc.dat allboards.xml "PCI:Smart Array 6402"...

  • Page 49: Return Codes

    Table 7 ifhw Operators (continued) Operator or Result term A literal string, used for comparison. string A literal number, used for comparison. number Return Codes Table 8 ifhw return codes Value Description 0 (True) The device is present. 1 (False) The device is not present.

  • Page 50: Return Codes

    BootDeviceLUN=3 Return Codes Table 9 sethbaini return codes Return Code Value Description The tool executed successfully. SUCCESS You specified an invalid option, or specified invalid values on the command ERROR_USAGE line. You specified a controller WWID that was not found in the specified file. ERROR_INVALID_WWID You specified an invalid controller name.

  • Page 51: Example

    \\repository_name\share_name The address of the remote machine and the share folder name. repository_encrypted_password The encrypted password to the share folder obtained using sstkencrypt. The user name with which to log on to the remote machine. repository_user Example sstkmount z: \\192.168.0.3\sstk_repository a292a8a5aea3ab94 /user:Administrator sstkmount z: \\remote\sstk_repository a292a8a5aea3ab94 /user:Administrator sstkmount...

  • Page 52: Support And Other Resources

    7 Support and other resources Contacting HP For the name of the nearest HP authorized reseller: In the United States, see the HP US service locator webpage at: http://www.hp.com/service_locator In other locations, see the Contact HP worldwide (in English) webpage at: http://welcome.hp.com/country/us/en/wwcontact.html For HP technical support: In the United States, for contact options see the Contact HP United States webpage at:...

  • Page 53: A Support Matrix

    A Support Matrix For a list of supported servers and components, see the Release Notes for Windows Server 2008 SP2 and Windows Server 2008 R2 SP1, available on Smart Setup CD ISO Image File for HP Integrity Servers, in the contents\doc\en_us folder. The Smart Setup CD ISO Image File for HP Integrity Servers is available at http://www.hp.com/ support/itaniumservers.

This manual is also suitable for:

Smartsetup scripting toolkit

Table of Contents