HP Integrity Mid-Range and High-End Systems Using the HP Rapid Deployment Pack 3.
© Copyright 2007 Hewlett-Packard Development Company, L.P 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 About This Document.........................................................................................................7 Intended Audience.................................................................................................................................7 Typographic Conventions......................................................................................................................7 HP Encourages Your Comments..................................................
Recovering from failures..............................................................................................31 Windows failures..................................................................................................................................31 Linux failures........................................................................................................................................31 A ACPI................................................................................
List of Tables 2-1 2-2 Customization Specifications........................................................................................................12 Firmware Requirements................................................................................................................
About This Document This document describes customizing and using HP Rapid Deployment Pack (RDP) deployment jobs to deploy Windows to HP Integrity mid-range and high-end (cell-based) systems. Intended Audience This document is for system administrators who need to incorporate Integrity mid-range and high-end systems into an RDP-based deployment process.
1 Overview This document describes modifying HP Rapid Deployment Pack (RDP) deployment jobs to deploy tested Microsoft® Windows® Server 2003 IA-64 operating systems to HP Integrity mid-range and high-end systems, including the HP Integrity rx7620, rx7640, rx8620, rx8640, Superdome sx1000, and Superdome sx2000. To perform the procedures described in this document, you must have a good understanding of both RDP and Integrity mid-range and high-end systems.
On bare-metal systems, you can use PXE-boot to connect to the RDP Deployment Server after the first power up. However, HP recommends going to EFI to validate the Advanced Configuration and Power Interface (ACPI) setting before the PXE-boot. For details, see Appendix A (page 33). RDP components requiring customization To deploy Windows to Integrity mid-range and high-end systems, some RDP jobs must be created or customized. For details, see Chapter 2 (page 11) and Chapter 3 (page 15).
2 Customizing RDP jobs RDP jobs, when used to deploy Integrity systems, use both a Linux automation environment and a Windows production environment, switching between them as necessary. On Integrity mid-range and high-end systems, it might be necessary to switch the ACPI configuration because a Linux automation environment (LinuxPE) and a Windows production environment each require a different ACPI mode. This ACPI switching cannot be performed with the standard RDP 3.7 product.
Table 2-1 Customization Specifications Group name Group number Typical initial state Method Document section Read HW Configuration 1 jobs Production Windows A or B “Read HW Configuration jobs (group 1)” (page 18) Read Image jobs 2 Production Windows B “Read Image jobs (group 2)” (page 23) Windows Scripted/Imaged Install jobs 3 Bare metal B “Bare-metal target systems” (page 25) Write/Erase HW Configuration jobs 4 Bare metal No customization needed “Write/Erase HW Configuration jobs (gr
Write/Erase HW Configuration jobs (group 4) The Write/Erase HW Configuration jobs group includes: • Deploy Integrity BL860c SAS Array Configuration (RAID 0) {LinuxPE} • Deploy Integrity BL860c SAS Array Configuration (RAID 1) {LinuxPE} • Deploy Integrity RX/BL Array Configuration (default) {LinuxPE} • Erase Integrity RX/BL Array Configuration {LinuxPE} • Write Integrity RX/BL Array Configuration {LinuxPE} • Write Integrity RX/BL HBA Configuration [server specific] {LinuxPE} • Deploy Integrity RX/BL System C
• • 14 post-operating system installation job, Install Windows 2003 IA64 Integrity Support Pack (latest), on the target system. The SetACPI Mode to Windows task is required if a transition between LinuxPE and production Windows will occur. The SetACPI Mode to Windows task runs in a LinuxPE environment. The SetACPI Mode to Linux task is required if a transition between production Windows and LinuxPE occurs. The SetACPI Mode to Linux task runs in production Windows.
3 Performing customization Creating Set ACPI Mode jobs This section describes how to create two jobs used to set the ACPI Configuration Mode to either Windows or Linux. Creating the Set ACPI Mode to Windows {LinuxPE} job This job consists of one Run Script task, which executes the Linux hpsetacpi utility. To create the job: 1. Create a new job, and rename the job Set ACPI Mode to Windows {LinuxPE}. 2. At the job frame, click Add, and select Run Script. 3. At the Run Script window, select Linux.
4. Paste the following script into the Run this script field: # Set ACPI to Windows /mnt/ds/lib/binia64/linux/hpsetacpi Windows rc=$? case $rc in 0) severity=1 status="hpsetacpi: Completed successfully.";; 1) severity=3 status="hpsetacpi: Fail setting ACPI Mode.";; 2) severity=3 status="hpsetacpi: Wrong option or argument.";; 3) severity=3 status="hpsetacpi: SFW version not supported.";; 4) severity=3 status="hpsetacpi: General failure.";; *) severity=3 status="Unknown error.
To create the job: 1. Create a new job, and rename the job Set ACPI Mode to Linux (Windows). 2. Create the task Copy File to (wlogevent.exe). 3. At the job frame, click Add, and select Copy File to. 4. In the Source Path field, enter: .\TechSup\Windows\ia64\wlogevent.exe 5. In the Destination Path field, enter: C:\Windows\System32\wlogevent.exe 6. 7. 8. Click Next>Finish. At the job frame, click Add, and select Run Script. Ensure that the Windows option is selected.
9. Paste the following script into the Run this script field: rem Set ACPI to Linux set severity=3 hpsetacpi -e hpsetacpi_errorLog.txt Linux if %ERRORLEVEL% if %ERRORLEVEL% if %ERRORLEVEL% if %ERRORLEVEL% if %ERRORLEVEL% goto error5 == == == == == 0 1 2 3 4 goto goto goto goto goto success error1 error2 error3 error4 :success set severity=1 set status="hpsetacpi.exe: Completed successfully." goto done :error1 set status="hpsetacpi.exe: Fail setting ACPI Mode." goto done :error2 set status="hpsetacpi.
In the Altiris Deployment Server console, drag and drop the following jobs, in sequence, to the active target system icon: 1. Set ACPI Mode to Linux (Windows) 2. Set ACPI Mode to Windows {LinuxPE} 3.
Scheduling three Read HW Configuration jobs This example uses the jobs that read the hardware array, HBA, and system configuration. However, you can use any jobs from the Read HW Configuration group in any order.
— — • • Windows Server 2003 SP1 or SP2, Enterprise Edition for IA64 Windows Server 2003 SP2, DataCenter Edition for IA64 The HP ISP version 5.2 or later is correctly installed on the target system. The Altiris Agent is correctly installed and running on the target system and connected to the Altiris Deployment Server. Customizing and running a Read HW Configuration job This example describes customizing and running the Read Integrity Hardware Configuration [server specific] {LinuxPE} job.
4. Copy the single task from the Set ACPI Mode to Windows {LinuxPE} job, and paste it to the Read Integrity Hardware Configuration [server specific] {LinuxPE} job. 5. Click the arrow button to move the copied task up to the third row of the job tasks list just after the Set ACPI to Linux task. 6. Drag and drop the customized Read Hardware Configuration [server specific] {LinuxPE} job to the target system icon.
1. Customize the Read Integrity RX/BL Array Configuration {LinuxPE} job. For instructions, see the “Customizing and running a Read HW Configuration job” (page 21). The customized job results should appear as depicted in the following figure. 2.
Customizing the Capture Windows 2003 IA64 Sysprep Image {LinuxPE} job 24 1. Select the Capture Windows 2003 IA64 Sysprep Image {LinuxPE} job. The job frame in the right pane displays the job tasks. 2. The first task, Run Script, runs in Windows, but the second task, Create Disk Image, runs in LinuxPE. Ensure that the ACPI Mode is set to Linux before the Create Disk Image task runs.
Customizing the Read Integrity RX/BL System and Array Configuration and Linux Image {LinuxPE} job 1. Select the Read Integrity RX/BL System and Array Configuration and Linux Image {LinuxPE} job. The job frame in the right pane displays the job tasks. 2. The Create Disk Image task runs in both Windows and LinuxPE. Ensure that ACPI Mode is set to Linux before the Create Disk Image task runs.
• Windows Scripted/Imaged Install jobs (group 3) • Write/Erase HW Configuration jobs (group 4) For the scope of this document, it is assumed that the jobs from the cited groups are applied to target systems booted to Altiris LinuxPE automation with no production operating system installed. Windows Scripted/Imaged Install jobs (group 3) The Windows Scripted/Imaged Install jobs perform two functions: • Prepare the system to boot to Windows Setup.
Customizing the Write Integrity RX/BL System and Array Configuration and Linux Image {LinuxPE} job 1. Select the Write Integrity RX/BL System and Array Configuration and Linux Image {LinuxPE} job. The job frame in the right pane displays the job tasks. 2. The first two Run Script tasks run in LinuxPE, and the Power Control tasks reboot the client system. The Distribute Disk Image task runs in both LinuxPE and Windows.
2. All tasks except the last are run in LinuxPE. The last task, Finish Install, runs in the newly-installed Windows Server 2003 operating system. When the Start Install task completes, the Altiris Agent detects that there are no remaining LinuxPE tasks and reboots the client system to Windows Setup. Ensure that the ACPI Mode is set to Windows before the system reboots. Copy the Set ACPI to Windows task, and paste it immediately after the Run Script - Start Install task.
2. Copy the Set ACPI to Windows task from the Set ACPI Mode to Windows {LinuxPE} job, and paste it immediately after the Run Script - Start Install task. Write/Erase HW Configuration jobs (group 4) The Write/Erase HW Configuration jobs are typically used along Windows Scripted/Imaged Install jobs to configure the system hardware before applying a Windows image or performing a Windows scripted install.
4 Recovering from failures If a system attempts to boot to an operating system while the ACPI Mode is set incorrectly, the system boot will fail. The following sections instruct you how to recover from this failure when attempting to boot to either Windows or Linux. Windows failures The following figure depicts a Windows failure caused by the wrong ACPI Configuration Mode. To recover, restart the client system to EFI Shell, and set the ACPI Mode to Windows.
To recover, restart the client system to EFI Shell, and set the ACPI Mode to single-pci-domain (sx1000 chipset) or default (sx2000 chipset) For chipset specifications, see Table 2-2 (page 13).
A ACPI Background information ACPI is an open-industry specification codeveloper by HP, Intel, Microsoft, Phoenix, and Toshiba. ACPI establishes industry-standard interfaces for operating system-directed configuration and power management on laptops, desktops, and servers. Because of differences in the operating systems, ACPI tables can vary, making it necessary to set the ACPI mode differently on Integrity mid-range and high-end systems.
The following table displays the required value of ACPI on LinuxPE and Windows Server 2003. Operating System ACPI Value LinuxPE • Default (sx2000 chipset, Arches) • single-pci-domain (sx1000 chipset, Pinnacles) • Windows Server 2003 SP1 or SP2, Enterprise Windows Edition for IA64 • Windows Server 2003 SP2, DataCenter Edition for IA64 On a bare-metal system, the ACPI Mode is always set to default. With this value, you can boot to LinuxPE.
Glossary Bare-metal systems An unconfigured system with no operating system currently installed. HP Integrity entry-class systems Entry-class servers and server blades not based on cellular technology, such as the Integrity rx6600 and BL860c. HP Integrity mid-range and high-end systems Partitionable mid-range and high-end servers based on cellular technology, such as the Integrity rx8640 and Superdome sx2000.
