HP INTEGRITY RX5670 User Manual

HP Integrity Servers for Microsoft Windows Server 2003 Smart Setup Guide

HP Part Number: 5991-3718 Published: March 2007

Legal Notices

Confidential computer software. Valid license from HP required for possession, use or copying. ConsistentwithFAR 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 changewithoutnotice. 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

shall not be liable for technical or editorial errors or omissions contained herein.

Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. Intel and Itanium are registered trademarks of Intel Corporation

or its subsidiaries in the United States and other countries.

Java is a U.S. trademark of Sun Microsystems, Inc.

UNIX is a registered trademark of The Open Group.

1 Preparing for the installation.......................................................................................11

Choosing an installation scenario.........................................................................................................11

Ensuring platform compatibility..........................................................................................................12

Check hardware compatibility........................................................................................................12

Back up existing data.......................................................................................................................12

Choosing an installation environment.................................................................................................12

Choosing the Installation media......................................................................................................13

Using the Microsoft OS media.........................................................................................................13

Using the HP Reinstallation media.................................................................................................14

Locating the Microsoft Certificate of Authenticity...............................................................................14

Setting up a console..............................................................................................................................18

Set up a headless console.................................................................................................................18

Set up the headless console using a null modem cable.............................................................18

Set up the headless console using a LAN..................................................................................19

Set up the headless console using a Remote Serial Console (rx2660, rx3600, rx6600, and BL860c

only)............................................................................................................................................19

Set up a GUI console........................................................................................................................19

Set up an Integrated Remote Console (rx2660, rx3600, rx6600, and BL860c only)..........................20

Set up a Virtual Media (vMedia) drive......................................................................................21

Setting up PXE/RIS................................................................................................................................22

Set up a RIS server...........................................................................................................................23

Install RIS...................................................................................................................................23

Configure RIS.............................................................................................................................24

Authorize a RIS server in Active Directory................................................................................25

Use the Client Installation Wizard.............................................................................................25

Preparing the server hardware.............................................................................................................25

Set up the boot drive........................................................................................................................26

Boot to EFI.......................................................................................................................................26

Locate the DVD/CD drive...............................................................................................................26

Set ACPI flag to windows (cell-based servers only).......................................................................27

Set cell local memory to 100% (cell-based servers only).................................................................28

Specify NIC for a network boot.......................................................................................................28

2 Installing the OS...........................................................................................................29

Installing from a headless console........................................................................................................29

Run EBSU........................................................................................................................................29

Run Windows Setup........................................................................................................................32

Enter the product key......................................................................................................................33

Installing from a GUI console...............................................................................................................33

Run EBSU........................................................................................................................................33

Run Windows Setup........................................................................................................................36

Specify server settings.....................................................................................................................36

Installing from PXE...............................................................................................................................37

Reinstalling from a headless console....................................................................................................37

Load the system image....................................................................................................................37

Specify server settings.....................................................................................................................39

Reinstalling from a GUI console...........................................................................................................39

Load the system image....................................................................................................................39

Specify server settings.....................................................................................................................40

Applying OS updates............................................................................................................................41

Table of Contents 3

Enabling Windows components...........................................................................................................41

Install TCP/IP...................................................................................................................................42

Install SNMP....................................................................................................................................42

Configure SNMP.............................................................................................................................42

Set IP addresses from a headless console........................................................................................42

Set up and run a Remote Desktop Connection...............................................................................43

Updating firmware, drivers, and software...........................................................................................43

Enable greater than 256 interrupts (cell-based servers only)..........................................................44

Update firmware.............................................................................................................................44

Update device drivers.....................................................................................................................45

Install the Integrity Support Pack....................................................................................................45

Install updates from the web...........................................................................................................46

Register for HP support notifications..............................................................................................46

Register for Microsoft security notifications...................................................................................46

Register for Microsoft Windows Update.........................................................................................46

Miscellaneous installation issues..........................................................................................................46

Using Integrated Remote Console to install Windows on rx2660, rx3600, rx6600, and BL860c

servers..............................................................................................................................................47

Installing a Windows guest on an HP Integrity Virtual Machine host...........................................48

Enabling hyperthreading on HP Integrity servers..........................................................................48

Enable hyperthreading using EFI..............................................................................................49

Enable hyperthreading using Partition Manager......................................................................49

3 Installing Management Tools......................................................................................51

Installing System Management Homepage..........................................................................................51

Configure SMH after Support Pack installation..............................................................................51

Install SMH separately....................................................................................................................51

Initializing SMH .............................................................................................................................53

Installing the management agents........................................................................................................53

Configure management agents after Support Pack installation.....................................................54

Install management agents from Smart Setup media.....................................................................54

Activating and configuring agents..................................................................................................54

Activating agents........................................................................................................................54

Configuring the event notifier....................................................................................................55

Setting the agent SNMP data collection interval.......................................................................58

Monitoring server processes......................................................................................................59

Sending SNMP traps to management applications via IP.........................................................60

Installing partition management tools..................................................................................................61

Install nPartition Commands Bundle from the Smart Setup media...............................................62

Install Partition Manager Bundle from the Smart Setup media......................................................62

Verifying the installation.................................................................................................................63

Verify nPartition commands......................................................................................................63

Verify Partition Manager installation.........................................................................................63

4 Performing hot-plug operations...................................................................................65

Before you begin...................................................................................................................................65

Adding a PCI card................................................................................................................................66

Hardware interface for all HP Integrity servers except Superdome...............................................66

Hardware interface for Superdome servers....................................................................................67

Software interface............................................................................................................................68

Removing a PCI card............................................................................................................................68

Software interface for all HP Integrity servers except Superdome.................................................68

Software interface for Superdome servers......................................................................................68

4 Table of Contents

Hardware interface for all HP Integrity servers except Superdome...............................................68

Hardware interface for Superdome servers....................................................................................69

A Preparing the server for Microsoft SQL Server 2005..............................................71

SQL Server 2005 installation.................................................................................................................71

Installing SQL Server from the command prompt..........................................................................71

Installing SQL Server from the GUI................................................................................................72

B EFI Utilities.....................................................................................................................75

Introduction to EFI................................................................................................................................75

EFI Boot Manager............................................................................................................................75

EFI Shell...........................................................................................................................................75

Common EFI Shell commands........................................................................................................76

EFI-Based Setup Utility...................................................................................................................79

Creating a new boot file using the EFI Shell.........................................................................................80

Verify successful boot file creation..................................................................................................81

C Management processor and Special Administration Console...............................83

Management processor.........................................................................................................................83

Accessing the MP.............................................................................................................................83

MP Commands................................................................................................................................83

Special Administration Console...........................................................................................................88

SAC Channel Management Commands.........................................................................................90

Table of Contents 5

List of Figures

1-1 Headless console configurations...................................................................................................18

1-2 GUI console configuration............................................................................................................19

1-3 PXE/RIS configuration...................................................................................................................22

2-1 Enter EBSU....................................................................................................................................30

2-2 Select Express Setup......................................................................................................................30

2-3 Update firmware...........................................................................................................................31

2-4 Partition disk.................................................................................................................................31

2-5 Install diagnostic tools...................................................................................................................32

2-6 Insert the Microsoft Windows Server 2003 CD.............................................................................32

2-7 Enter EBSU....................................................................................................................................33

2-8 Select Express Setup......................................................................................................................34

2-9 Update firmware...........................................................................................................................34

2-10 Partition disk.................................................................................................................................35

2-11 Install diagnostic tools...................................................................................................................35

2-12 Insert the Microsoft Windows Server 2003 CD.............................................................................36

2-13 Enabling hyperthreading in the Partition Manager......................................................................50

3-1 HP System Management Homepage for Windows .....................................................................51

3-2 HP Insight Management Agents for Windows Server 2003 on Itanium-based systems..............54

3-3 Services tab screen.........................................................................................................................55

3-4 Welcome message..........................................................................................................................56

3-5 Mail (SMTP) server information...................................................................................................56

3-6 Event recipients information.........................................................................................................57

3-7 Adding a new user........................................................................................................................57

3-8 Event selection window................................................................................................................58

3-9 SNMP Settings tab.........................................................................................................................58

3-10 Process Monitor tab.......................................................................................................................59

3-11 Component Services window.......................................................................................................60

3-12 SNMP traps tab.............................................................................................................................61

3-13 SNMP service configuration..........................................................................................................61

B-1 EFI Boot Manager..........................................................................................................................75

List of Tables

1-1 Installation matrix.........................................................................................................................13

1-2 Locating the Microsoft COA.........................................................................................................14

1-3 Graphics support on server models..............................................................................................20

1-4 EFI device mapping fields.............................................................................................................27

2-1 Integrity servers supporting PXE/RIS installations.......................................................................37

4-1 PCI cards that do not support hot-plug addition..........................................................................66

B-1 EFI Shell Commands and Descriptions.........................................................................................76

C-1 Channel Management commands.................................................................................................90

1 Preparing for the installation

Installing Microsoft® Windows® Server 2003 for Itanium®-based systems on an HP Integrity server involves preparing the hardware for operating system (OS) installation, loading the OS, and updating the system with the latest OS patches. This chapter helps you plan the installation based on the server model, the OS edition, the source of the OS media, and your network environment. Subsequent chapters guide you through the installation process.

NOTE: HP Integrity servers must run Windows Server 2003 with either Service Pack 1 (SP1) or Service Pack 2 (SP2). If you are running an earlier version of Windows Server 2003, you must upgrade your operating system to SP1 or SP2. When updating to SP1 or SP2, perform the update in the following order:

1. Install the latest HP Integrity Support Pack.

2. Reboot the machine.

3. Install the desired Service Pack.

4. Reboot the machine again.

5. Use the Windows Update Service to ensure that you have the latest Microsoft updates.

Choosing an installation scenario

When you purchase an HP Integrity server, you can order additional hardware, support options, and an OS enablement kit (such as the HP Integrity Essentials Foundation Pack for Windows). You can also order factory installation of the OS. Depending on your order (or subsequent use), your system is in one of the following states:

• Factory-installed Windows Server 2003

Windows Server 2003, Datacenter Edition, is usually factory-installed. To get the system up and running, verify that the OS was installed correctly, set up the system, and update it with the latest firmware, drivers, and Microsoft patches and fixes (QFEs) available in the latest HP Integrity Essentials Foundation Pack or from the HP Integrity servers support website:

http://www.hp.com/support/itaniumservers/

• Factory-installed OS other than Windows Server 2003

If you choose to run Windows Server 2003 instead of the factory-installed OS, you can perform the migration yourself on an entry-level server or engage an HP Customer Engineer (CE) to perform the migration on a mid-range or high-end server. Contact HP support or sales to engage the CE.

When you migrate to Windows Server 2003 from another OS, pay close attention to the differences in supported hardware I/O, in particular, between the two operating systems. You must replace incompatible components with those supported on Windows Server 2003. If you want to keep the data residing on the server hard disk, you must back up the data and verify that you can restore it elsewhere. Then prepare the server hardware for installation.

Use the HP Smart Setup media and the Microsoft Windows Server 2003 media to load the OS and HP value-added software (drivers, tools, utilities, and agents) on the server. After installation, set up the system, and update it with the latest firmware, drivers, and Microsoft patches and fixes (QFEs) on the HP Smart Update media included in the latest HP Integrity Essentials Foundation Pack or from the HP Integrity servers support website:

http://www.hp.com/support/itaniumservers/

• No operating system installed

Prepare the server hardware for installation. Use the HP Smart Setup media and the Microsoft Windows Server 2003 media to load the OS on the server. After installation, verify that the

Choosing an installation scenario 11

OS was installed correctly, configure the system, and update it with the latest drivers and

Microsoft patches and fixes (QFEs) on the HP Smart Update media included in the latest

HP Integrity Essentials Foundation Pack or from the HP Integrity servers support website:

http://www.hp.com/support/itaniumservers/

• Installed Windows Server 2003 incorrect or inoperable

Prepare the server hardware for installation. Use the HP Reinstallation media to restore the

OS files. After reinstallation, verify that the OS was installed correctly, configure the system,

and update it with the latest firmware, drivers, and Microsoft patches and fixes (QFEs) on

the HP Smart Update media included in the latest HP Integrity Essentials Foundation Pack

or from the HP Integrity servers support website:

http://www.hp.com/support/itaniumservers/

Ensuring platform compatibility

If you are migrating from another operating system to Windows Server 2003, ensure that the hardware is compatible with Windows Server 2003 and that any data on the server disk is backed up..

Check hardware compatibility

To verify that your existing hardware is compatible with Windows Server 2003, complete the following steps:

1. See the Options & Accessories page for each server to check supported hardware configurations. For example, the Options & Accessories page for the rx8620 server found at

http://h20341.www2.hp.com/integrity/cache/342107-0-0-0-121.html lists the processors,

memory, adapters, cards, and controllers that are available for that server.

2. Verify existing device compatibility at the HP Integrity server connectivity website:

http://www.hp.com/products1/serverconnectivity/index.html

3. Verify storage compatibility by reviewing the HP Integrity Server-Storage support matrices at http://www.hp.com/products1/serverconnectivity/support_matrices.html. This list is not exhaustive because storage vendors can support more configurations than those indicated at the site. As a general rule, check with your storage vendor and an HP sales representative for a definitive statement on server and storage compatibility.

Back up existing data

To restore the data on the hard disk of the server after migrating to Windows, you must first back up the data and verify that you are able to restore it:

1. Perform a complete server backup using your existing backup utilities.

2. Verify the integrity of the backup by restoring samples of data to another server.

3. Store the backup in a safe place.

Choosing an installation environment

The installation environment consists of the server model, the OS edition, a GUI console or a headless console, and the media you need to perform the installation. In addition to installing from Smart Setup and Microsoft media or reinstallation media, you can automate the installation of Windows Server 2003 using a Remote Installation Service (RIS) server on the network and a preboot execution environment (PXE) client on the HP Integrity server.

Table 1-1 lists the HP Integrity server models, the console options, and relevant media choices.

12 Preparing for the installation

Table 1-1 Installation matrix

MediaConsoleServer

rx2620

rx2660

rx3600

rx4640

rx6600

BL860c

Cell-based servers

rx8620

rx8640

rx7640

Superdome

(sx1000 and sx2000)

GUI consolerx1620

Headless console

Integrated Remote Console

(rx2660, rx3600, rx6600, and BL860c only)

PXE/RIS

GUI consolerx7620

Headless console

PXE/RIS

HP Smart Setup, HP Smart Update, and Microsoft Windows Server 2003 with SP2

HP Reinstallation

HP Smart Setup, HP Smart Update, and Microsoft Windows Server 2003 with SP2

HP Reinstallation

Virtual Media (vMedia) + HP Smart Setup, Smart Update, Windows Server 2003 with SP2,

or HP Reinstallation

HP Smart Setup, HP Smart Update, and Microsoft Windows Server 2003 with SP2

HP Reinstallation

HP Smart Setup, HP Smart Update, and Microsoft Windows Server 2003 with SP2

HP Reinstallation

Choosing the Installation media

The HP Integrity Essentials Foundation Pack for Windows includes the HP Smart Setup media. You can use the HP Smart Setup media both before and after you install the OS.

• Before installing the OS, boot the server with the Smart Setup media in the CD/DVD drive.

The server boots to the EFI-Based Setup Utility (EBSU). EBSU provides an easy-to-use interface for offline setup and configuration tasks, such as creating hard disk partitions and updating the firmware. Moreover, EBSU provides a utility called Express Setup, which guides you through the process of installing the OS. EBSU works in conjunction with the Microsoft media, which holds the OS image. HP strongly recommends that you use EBSU to install the OS. For more information about EBSU, see Appendix B.

• After installing the OS, use the Smart Setup media to install drivers, utilities, and important

fixes to ensure the stability and performance of the system. You can also use Smart Setup to browse the documentation for the server, including an electronic version of this document. Then use the Smart Update media to update the server with critical operating system and security QFEs from Microsoft.

Using the Microsoft OS media

You can purchase the Microsoft OS media either with the HP Integrity Essentials Foundation Pack for Windows from HP or separately from a Windows reseller. Possibly your organization already has a volume license for Windows Server 2003, Enterprise Edition with SP2 for Itanium-based servers. You need this media and the license key to install Windows Server 2003 (if Windows is not factory-installed) on HP Integrity servers.

HP ReinstallationGUI console

HP ReinstallationHeadless console

Choosing an installation environment 13

Using the HP Reinstallation media

HP Integrity servers factory-installed with Windows Server 2003 provide the HP Reinstallation media, which you can use to restore the server to its factory condition if necessary. You must have the corresponding license key to reinstall Windows Server 2003. The license key is found on your server’s Certificate of Authenticity (COA).

Locating the Microsoft Certificate of Authenticity

The certificate contains the CD key for Microsoft Windows Server 2003. You must enter this key as part of the installation procedure. The physical location of the Certificate of Authenticity (COA) depends on the server model. Table 1–2 identifies the locations of COAs for supported HP Integrity servers.

Table 1-2 Locating the Microsoft COA

LocationIntegrity Server

rx1620

rx2620

The COA is on the underside of the pullout strip located near the power switch, as shown here (server is upside down in the image):

The COA is on a pullout strip located on the front of the system, adjacent to the hard drives, as shown here:

14 Preparing for the installation

Table 1-2 Locating the Microsoft COA (continued)

LocationIntegrity Server

The COA is located on the left side panel, in the middle, as shown here:rx2660

The COA is located on the left side panel, as shown here:rx3600

The COA is located on the left side panel, as shown here:rx4640

The COA is located on the left side panel. It as shown here:rx6600

Locating the Microsoft Certificate of Authenticity 15

Table 1-2 Locating the Microsoft COA (continued)

LocationIntegrity Server

BL860c

rx7620 and rx7640

The COA is located on the left side panel. If there is more than one label on the side panel, the COA is the one farthest left, as shown here:

The COA is located on the front of the system, above the light panel, next to the UUID label, as shown in the first illustration that follows. Additional COAs are shown in the second illustration.

16 Preparing for the installation

Table 1-2 Locating the Microsoft COA (continued)

LocationIntegrity Server

rx8620 and rx8640

Superdome (sx1000 and sx2000)

The COA is located in the front of the system, at the bottom, near the power supply as shown in the first illustration that follows. If additional COAs are required, they are located as shown in the second illustration.

The COA is located inside the unit, on the left, in the open space between the cells and the extended I/O cabinet (IOX), as shown here:

Locating the Microsoft Certificate of Authenticity 17

Setting up a console

Set up your server with a GUI console or a headless console.

Set up a headless console

A headless console is a PC running terminal emulation software, such as PuTTY (available on the Smart Setup media or from the web) or HyperTerminal, connected to the server through the management processor (MP) serial port or LAN port.

Figure 1-1 shows headless consoles connected to an HP Integrity rx4640 server.

Figure 1-1 Headless console configurations

When you use a headless console to install Windows, you can view detailed installation information for each component by monitoring the setup log channels. See “Special Administration

Console” (page 88) for more information.

From the headless console, you can access the EFI Shell, the management processor (MP), and the Microsoft Special Administration Console (SAC). You can use these utilities while installing and administering Windows Server 2003 on HP Integrity servers. For more information about the MP and SAC, see “Special Administration Console” (page 88).

You can configure a headless console in the following ways:

• Using a null modem cable

• Using a cat5 LAN cable

• Using a Remote Serial Console (rx2660, rx3600, rx6600, and BL860c servers only)

The first two methods require a terminal emulation application such as HyperTerminal or PuTTY. PuTTY is a free implementation of telnet and SSH for 32-bit Windows and UNIX. PuTTY provides an X terminal. You must use PuTTY Version 0.59 or higher, available on the Smart Setup media or from the PuTTY website at:

http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html

Set up the headless console using a null modem cable

To set up the headless console using a null modem cable, complete the following steps:

1. Connect the PC to the server MP serial port with a null modem cable.

2. Install PuTTY on the client PC and specify these port settings:

• Bits per second: 9600

• Data bits: 8

• Parity: none

18 Preparing for the installation

• Stop bits: 1

• Flow control: Xon/Xoff

3. Use the Keyboard Configuration Panel to map the backspace key to Control + H.

4. Boot the server.

5. Run PuTTY and press Enter. The MP login prompt appears.

6. Enter your user name and password, and the MP command prompt appears.

7. Enter the CO command to access the headless console.

Set up the headless console using a LAN

To set up the headless console over a LAN, complete the following steps:

1. Connect the PC to the server LAN port with a cat5 cable.

2. Use telnet to access the MP. The MP login prompt appears.

3. Enter your user name and password, and the MP command prompt appears.

4. Enter the CO command to access the headless console.

Set up the headless console using a Remote Serial Console (rx2660, rx3600, rx6600, and BL860c only)

To set up the headless console (on rx2660, rx3600, rx6600, and BL860c servers only) using Remote Serial Console, complete the following steps:

1. Point a secure web browser at the name or IP address of the server MP.

2. Enter your user name and password to log in to the System Management Homepage.

3. On the Remote Console tab, and select Remote Serial Console in the left panel.

4. Click the Launch button and a new window appears, providing access to the headless

console.

Set up a GUI console

A GUI console is a VGA monitor, a USB HP keyboard, and a USB mouse connected to the server. (You can use a USB-to-PS2 converter to connect to a console switch).

NOTE: If a VGA card is not already installed, you must install the HP Graphics and USB Combo Card to use a GUI console. No other graphics card is supported by HP Integrity servers. Also, only HP keyboards are supported with this card.

Figure 1-2 shows a GUI console connected to an HP Integrity rx4640 server.

Figure 1-2 GUI console configuration

Setting up a console 19

A GUI console provides complete access to all the installation and administration tasks that you can perform on the server. You can use the GUI console to prepare the server for installation, install the OS, and check server status after installation.

On servers configured with an internal graphics card, you can connect a monitor, keyboard, and mouse directly to the appropriate ports. On servers without an internal graphics card, you must first install an HP Graphics and USB Combo Card and connect the console to the appropriate ports. Then, from an existing headless console, modify system configuration to redirect the output to the GUI console.

Table 1-3 Graphics support on server models

Graphics CardServer Model

Built-in video graphicsrx1620, rx2660, rx3600, rx4640, rx6600,

BL860c

Optional HP Graphics and USB Combo Card (HP part number A6968A)rx7620, rx8620, Superdome/sx1000

Optional HP Graphics and US Combo Card (HP part number A6968B)rx7640, rx8640, Superdome/sx2000

To install the HP Graphics and USB Combo Card using the Legacy interface (black background), complete the following steps:

1. Install the HP Graphics and USB Combo Card in an open PCI slot in the server.

2. Connect a VGA monitor, USB HP keyboard, and USB mouse to the appropriate ports.

3. Boot the server to EFI.

4. At the headless console, from the EFI Boot Manager, select Boot Option Maintenance Menu.

5. Select Select Active Console Output Devices.

6. Highlight the line with the graphics card PCI device.

If the line does not begin with an asterisk, the device is disabled. Use the space bar to toggle the state of the card from disabled to enabled (as indicated by the asterisk).

7. Select Save Settings to NVRAM and then Exit. The video display is now directed to the GUI console.

To install the HP Graphics and USB Combo Card using the Enhanced interface (grey background), complete the following steps:

1. Install the HP Graphics and USB Combo Card in an open PCI slot of the server.

2. Connect a VGA monitor, USB HP keyboard, and USB mouse to the appropriate ports.

3. Boot the server to EFI.

4. From the EFI Boot Manager, select Boot Configuration.

5. Select Console Configuration.

6. Select Select Output Console.

7. Select the graphics card PCI device and press Enter. The video display is now directed to the GUI console.

Set up an Integrated Remote Console (rx2660, rx3600, rx6600, and BL860c only)

The Integrated Remote Console (IRC) lets you use Windows clients running Internet Explorer to remotely view and manage HP Integrity servers featuring the iLO 2 management processor. This functionality is supported on rx2660, rx3600, rx6600, and BL860c servers only.

The IRC combines keyboard, video, and mouse into a remote, virtual interface. Use it to view the server’s display and directly interact with it. When you use IRC in combination with Virtual Media (See “Set up a Virtual Media (vMedia) drive” (page 21)), you can perform remote GUI installations of server operating systems and software. You can also use the IRC to perform server maintenance tasks and run applications remotely that require keyboard and mouse input.

20 Preparing for the installation

NOTE: You can use the Integrated Remote Console in place of the GUI Console method of installation anywhere the GUI method is described in this document.

The IRC and vMedia features are enabled only after you have obtained and installed an iLO 2 MP Advanced Pack license (part number AB500A). If you are not licensed and try to use these features, you see the message: iLO 2 feature not licensed. Free limited-term trial licenses are also available.

For more information about the iLO 2 MP Advanced Pack licensing, or to obtain a free limited-term license, go to:

http://h71028.www7.hp.com/enterprise/cache/279991-0-0-0-121.html.

Follow the factory installation or manual installation instructions located on the Integrated

Lights-Out Advanced Pack for HP Integrity Servers; Certificate of License to Use; License Installation Card to activate your license.

This document is not intended to be a complete description of IRC or vMedia. For more information about these powerful features, see the HP Integrity rx3600 and HP Integrity rx6600: Integrated Lights-Out 2 Management Processor Operations Guide at:

http://docs.hp.com/en/AD217-9001A/index.html or http://docs.hp.com/en/AD217-9001A/AD217-9001A.pdf

To set up an Integrated Remote Console (on rx2660, rx3600, rx6600, and BL860c servers only), complete the following steps:

1. Point a secure web browser at the name or IP address of the server MP.

2. Enter your user name and password to log in to the System Management Homepage.

3. On the Administration tab, select Licensing in the left panel.

4. Enter the license number.

5. On the Remote Console tab, select Integrated Remote Console in the left panel.

6. Click the Launch button. If Launch is greyed out, the license might be invalid or expired.

A new window appears, providing access to the IRC.

Set up a Virtual Media (vMedia) drive

Virtual Media (vMedia) provides you with virtual devices that mimic physical hardware devices just as if they were physically connected, such as a virtual CD/DVD drive that can connect through a network to the managed server. The vMedia device can be a physical CD/DVD drive on the management workstation, or it can be an image file stored on a local disk drive or network drive. Floppy disk or USB memory devices are not supported.

Booting from the iLO 2 MP CD/DVD enables you to upgrade the host system ROM, upgrade device drivers, deploy an OS from network drives, and perform disaster recovery of failed operating systems, among other tasks.

The iLO 2 MP device uses a client/server model to perform the vMedia functions. The iLO 2 MP device streams the vMedia data across a live network connection between the remote management console and the host server. The vMedia Java™ applet provides data to the iLO 2 MP as required.

NOTE: You can use a vMedia drive in place of a local CD or DVD drive anywhere that a local CD/DVD drive is described in this document.

To set up a vMedia drive (on rx2660, rx3600, rx6600, and BL860c servers only), complete the following steps:

1. Point a secure web browser at the name or IP address of the server MP.

2. Enter your user name and password to log in to the System Management Homepage.

3. On the Administration tab, select Licensing in the left panel.

4. Enter the license number.

Setting up a console 21

5. On the Virtual Devices tab, select Virtual Media in the left panel.

6. Click the Launch button. If Launch is greyed out, the license might be invalid or expired. A new window appears, providing access to Virtual Media. Do on of the following actions:

• Select Local Media Drive, specify the CD or DVD drive on your client machine, and

insert the CD or DVD into that drive.

• Select Local Image File, and specify the ISO image of the desired CD or DVD.

7. Click Connect. The server now detects a new USB drive attached to it. This is the vMedia drive.

Setting up PXE/RIS

A Remote Install Server (RIS) is a specialized Windows server used to perform multiple software installations across a network. The RIS server, working in conjunction with an agent (the PXE client) residing on target systems, performs automated installations. This method of installation offers the following advantages:

• Installations are automated; no user intervention is needed

• You can install multiple servers in one batch job

• Each server receives a standardized image

• You can perform an installation from anywhere on the intranet

Figure 1-3 shows a sample PXE/RIS setup.

Figure 1-3 PXE/RIS configuration

22 Preparing for the installation

NOTE: When you perform a PXE/RIS headless installation, note the following:

• Headless installations using PXE/RIS are not supported with Windows Server 2003, Datacenter Edition. Use the HP Reinstallation media instead.

• Do not connect the RIS server to the Integrity server using your intranet during initial Windows OS installation. Set up a small private network, populated with the RIS server, a hub, and the system LAN NIC of the HP Integrity server. This protects the intranet from errors that might occur during the Windows installation process. When the Windows OS installation has completed, connect the RIS to the target Integrity servers using your intranet.

Remote Installation Services (RIS) enables you to create, maintain, and quickly install identical OS and software configurations on multiple headless systems with a predefined level of user interaction. RIS uses the preboot execution environment (PXE) to enable client computers without an operating system to boot remotely to a RIS server. The RIS server then installs the operating system over a TCP/IP network connection. You can create different sets of RIS images for different groups of client computers. You can also use Group Policy settings to limit the installation options that RIS presents to clients. In addition, you can configure RIS for either interactive or fully automated installations.

Set up a RIS server

Setting up one or more RIS servers in your network requires careful planning, design, and implementation. The following checklist provides an overview of the tasks involved in setting up a RIS server:

• Ensure that both your RIS server and client (Integrity server) hardware meet the Remote Installation Services (RIS) hardware requirements. The server hardware must meet the minimum requirements for the version of Windows Server 2003 that you are installing.

• Ensure that your network is based on TCP/IP, and that a Domain Name System (DNS) server exists on the network. You do not need to use the Microsoft version of DNS.

• Ensure that a Dynamic Host Configuration Protocol (DHCP) server exists on the network. You do not need to use the Microsoft version of DHCP.

• Ensure that Active Directory exists on the network.

• Install the RIS component on the RIS server.

• Run the RIS Setup Wizard.

Install RIS

Configure RIS

After the Remote Installation Services Setup Wizard completes, depending on the settings chosen, the RIS server either services client computers or pauses while you configure advanced settings using the RIS administration settings. The following list describes the available configuration options.

• Specify which RIS servers are allowed to run on your network. This option prevents

• Use the Active Directory Users and Computers snap-in to set properties on individual RIS

• Use Group Policy to specify which installation options are presented to different groups of

• Use security descriptors or discretionary access control lists (ACLs) to specify which users

To configure settings for new clients for RIS, complete the following steps:

1. Open Active Directory Users and Computers.

2. In the console tree, go to Active Directory Users and Computers > Applicable domain

3. Click Properties. In the Properties dialog box, go to the Remote Install tab and click

4. In the Advanced Settings dialog box, go to the New Clients tab.

5. Select the client computer naming format you want to use, or click Customize to create a

6. To specify where to create the client computer account, click one of the following options:

to unknown client computers if you want the RIS server to respond only to prestaged client computers in Active Directory.

3. c. Enter the location of the client images. This can be either the Windows Server 2003

Enterprise Edition with SP2 CD or a shared folder on the network that contains the installation files.

4. d. Enter help text that describes the operating system installation choices to users or

clients of RIS.

unauthorized (often referred to as rogue) RIS servers, ensuring that only those RIS servers authorized by administrators can service clients. If an attempt is made to start an unauthorized RIS server on the network, it will be shut down automatically and thus unable to service client computers. A RIS server must be authorized before it can service client computers.

servers that control how the server supplies RIS to requesting clients. To access the snap-in go to Start > Programs > Administrative Tools, and then clicking Active Directory Users and Computers.

users by the Client Installation wizard (CIW). For example, you can choose to allow a group of users access only to the automatic setup option, and restrict access to all other options to administrators.

or group of users can have access to the operating system images available on the RIS server. You can use this method to guide users through the selection of the unattended OS installation appropriate for their account privileges. By default, when an operating system image is added to a RIS server, the image is available to all users serviced by that RIS server.

> Applicable organizational unit (such as Computers/Applicable RIS server) and right-click the applicable RIS server.

Advanced Settings.

client computer naming format.

• Default directory service location

• Same location as the user setting up the client computer

• The following directory service location

7. If you choose the last option, click Browse and specify where to create the computer accounts.

24 Preparing for the installation

Authorize a RIS server in Active Directory

A RIS server must be authorized in Active Directory to be able to respond to clients requesting service. If RIS is installed on a server that is not an authorized DHCP server, or added to a DHCP server that is not authorized in Active Directory, you must complete the following steps:

1. Log in to the domain in which the RIS server resides. (The account you use must be a member of the Enterprise Admins group.)

2. From the Start menu, point to Programs and Administrative Tools and click DHCP from the list. This starts the DHCP Management snap-in.

3. Right-click the DHCP root node in the scope pane, and then click Manage Authorized Servers.

4. Click Authorize, enter the IP address or name of the RIS server, and then click OK. When prompted to ensure that this is the correct RIS server to authorize, click Yes.

The server will not respond to client requests until the changes to Active Directory have taken effect. For these rights to apply immediately, on the domain controller on which your rights have been set, complete the following steps:

1. On the Start menu, click Run.

2. Enter the cmd command.

3. At the command prompt, enter:

secedit /refreshpolicy /MACHINE_POLICY

Use the Client Installation Wizard

The following installation options are included in the Client Installation Wizard (CIW). Automatic setup is available by default. RIS uses Group Policy settings to allow access to the automatic setup option only, and to restrict all users and administrators from the rest of the installation options described in the following list:

• Automatic Setup—This option allows you to select which operating system to install, but it does not prompt you for specific configuration settings. If only one operating system option is offered, you are not prompted, and an unattended installation of the operating system image starts automatically.

• Custom Setup—This option allows you to override the automatic computer naming process and the default location within the Active Directory where client computer accounts will be created. Help desk or administrators can use this option to preinstall a client computer for someone else within the enterprise.

• Restart a Previous Setup Attempt—This option automatically restarts the operating system installation process when an installation attempt fails before completion. This option does not copy files from where the previous installation attempt failed; however, you are not required to answer any questions answered within the CIW from the previous setup attempt.

• Maintenance and Troubleshooting—This option provides access to third-party maintenance and troubleshooting tools that you can use before installing the operating system. Examples of these tools include system flash BIOS updates, computer diagnostic tools, and virus scanning utilities.

Preparing the server hardware

To set up the server hardware for OS installation, set up the boot drive, set up the CD/DVD drive, and—if the server is cell-based—verify that the ACPI boot flag is set to ‘windows’ (see “Set ACPI

flag to windows (cell-based servers only)” (page 27)).

Preparing the server hardware 25

Set up the boot drive

The operating system installs through the boot controller detected as adapter zero to the drive detected as drive zero.

CAUTION: HP strongly recommends that only the target OS drive be connected during installation. This ensures that the OS is installed on the correct drive. Make sure that the Z: drive letter is free. Windows Server 2003 with SP1 or SP2 creates the EFI partition here.

To set up the boot drive, complete the following steps:

1. Power off the server.

2. Make a note listing all device connections so you can reconnect them after the installation completes.

3. Disconnect all mass storage devices from all controllers except the boot controller.

4. Configure the boot controller and boot drive. HP recommends that you install the boot controller in the root cell.

NOTE: If you are using an HP Smart Array controller, see the controller’s user guide for more information. You can interrupt the boot process to invoke the EFI-Based Option ROM Configuration for Arrays (ORCA). To invoke this utility:

1. 1. Press F8 on the GUI console.

2. 2. Press ESC 8 on the headless console.

Boot to EFI

To launch the EFI Shell, complete the following steps:

1. Boot the server. The server automatically goes to the EFI Boot Manager Menu.

2. Arrow down to select EFI Shell.

3. Press Enter.

• If you are using the Enhanced EFI Boot Manager Menu (grey background), select EFI

Boot Manager Menu > EFI Shell

• If you are using the Legacy EFI Boot Manager Menu (black background), select EFI

Boot Manager Menu > EFI Shell [Built-in].

Locate the DVD/CD drive

When hardware (for example, HDD, a USB device, or a DVD-ROM drive) is added to a system after it has booted to EFI, the EFI Shell environment does not automatically detect the new device. You must reconnect the device driver for the EFI Shell to recognize the device.

The EFI Shell environment creates default mappings for all the device handles that support a recognized file system. After you change the system configuration or add a new device, you must regenerate these mappings.

To enable the EFI Shell to detect and access the DVD/CD drive, complete the following steps:

1. From the EFI Shell, enter the reconnect –r command.

The reconnect command reconnects one or more drivers from a device, disconnecting all the drivers from all the devices and then reconnecting them. If you do not specify a device handle, the reconnect operation is performed on all the handles in the system. If you do specify a device handle, only the device handle and the devices below it are reconnected.

2. From the EFI Shell, enter the map -r command.

The -r option regenerates all the mappings in a system. The EFI Shell displays the device mapping table, as follows.

26 Preparing for the installation

fs0 : Acpi(PNP0A03,0)/Pci(2|0)/Ata(Primary,Master)/CDROM(Entry1) blk0 : Acpi(PNP0A03,1)/Pci(1|0)/Scsi(Pun0,Lun0) blk1 : Acpi(PNP0A03,0)/Pci(2|0)/Ata(Primary,Master) blk2 : Acpi(PNP0A03,0)/Pci(2|0)/Ata(Primary,Master)/CDROM(Entry1

3. Note the device name of the CD device:

fs0

You use this to explore the contents of the CD or DVD.

The map command displays or defines a mapping between a user-defined name and a device handle. The most common use of this command is to assign drive letters to device handles that support a file system protocol. When these mappings are created, the drive letters can be used with all the file manipulation commands.

Use the map command to create new mappings or delete an existing mapping with the -d option. If you use the map command without any parameters, all the current mappings are listed. If you use the -v option, the mappings are shown with additional information on each mapped handle. The following table describes the device mapping fields.

Table 1-4 EFI device mapping fields

DescriptionItem

blkn

Acpi(Device,X)

Pci(D/F)

Scsi(Pun.Lun)

HD(Part,Sig)

This indicates a physical drive or a partition on a physical drive. A physical drive can be a hard disk drive or a removable media drive. A

Partn

(in parentheses) appears when a disk drive contains a partition.

Acpi is Advance Configuration and Power Interface. The device type is the first entry in parentheses. The second entry, X, is the PCI host number.

This indicates PCI-related information. D is the PCI device/slot number and F is the PCI function number.

This denotes the physical characteristic of the SCSI disk. Pun is the SCSI number and Lun is the LUN number on the physical device.

This indicates the partition Part and EFI signature Sig on the partition.

Set ACPI flag to windows (cell-based servers only)

On cell-based servers, you must set the Advanced Configuration and Power Interface (ACPI) flag to the value appropriate for the operating system it boots. For the server to boot to Windows Server 2003, set the ACPI flag to windows.

If you purchased your server with a Windows operating system option, this flag is set to windows in the factory. If you purchased the server with a different OS or no OS, you must set this flag to windows.

CAUTION: If you boot the server to Windows Server 2003 without setting the ACPI flag to windows, the OS displays a blue screen error.

To set the ACPI flag, complete the following steps:

1. From the EFI Shell, enter the acpiconfig command.

EFI displays the current ACPI settings. If the flag is set to windows, EFI displays:

acpiconfig: windows

2. If the flag is not set to windows, enter the acpiconfig windows command.

3. Enter the acpiconfig command again to display the settings again and verify that the flag

is set correctly.

Preparing the server hardware 27

+ 63 hidden pages