Hp INTEGRITY RX5670 Smart Setup Guide

Smart Setup Guide

HP Integrity Servers for Microsoft Windows Server 2003

Manufacturing Part Number: 5990-8222

January 2005

Hewlett-Packard Development Company, L.P.

Legal Notices

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. 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. Linux is a U.S. registered trademark of Linus Torvalds.

1. Planning the installation

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Choosing an installation scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Choosing an installation environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Using a local console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Using a remote console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Using PXE/RIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Using the HP Smart Setup media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Using the Microsoft RTM media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Using the HP Reinstallation media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Using EFI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

EFI Boot Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

EFI Shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Installation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2. Preparing for installation

Ensuring platform compatibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Check system firmware version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Check hardware compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Preparing servers with 4GB DIMMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Back up existing data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Setting up a console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Set up a remote console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Set up a local console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

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

Set up RIS server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Set up PXE on the HP Integrity server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Preparing the server hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Set up the boot drive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Locate the DVD/CD drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

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

Set Cell Local Memory to 100% (cell-based servers only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Locating the Microsoft Certificate of Authenticity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Contents

3. Installing the OS

Installing from a local console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Run EBSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Run Windows Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Set NOVESA option (cell-based server with Graphics USB combo) . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Specify server settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Installing from a remote console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Run EBSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Run Windows Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Set NOVESA option (cell-based server with Graphics USB combo) . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Enter the product key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Installing from PXE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

iii

Contents

Reinstalling from a local console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Load the system image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Specify server settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Reinstalling from a remote console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Load the system image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Specify server settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Verifying the installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Check hardware status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Install new device drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Set up a Remote Desktop Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

4. Updating the server

Updating your system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Install updates from the HP Smart Update CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Install updates from the HP Smart Setup CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Install updates from the web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Register for HP support notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Register for Microsoft security notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Register for Microsoft Windows Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Administering the system remotely . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Special Administration Console (SAC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

1 Planning the installation

Installing a Microsoft Windows Server 2003 64-bit version operating system on an HP Integrity server involves preparing the hardware for the 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, and the source of the OS media, and your network environment. Subsequent chapters guide you through the installation process.

Chapter 1

Planning the installation

Overview

The HP Integrity server family, based on the Intel Itanium 2 processor, supports 64-bit Windows Server 2003 on a full range of server models, from entry-level servers such as the 2-processor rx1620, through mid-range servers such as the rx7620 and rx8620, up to the high-end 128-processor Superdome. Some HP Integrity servers, such as rx7620, rx8620, and Superdome, are based on the HP Super-Scalable Processor chipset (sx1000). They are composed of basic building blocks known as cells. These cell-based servers can be set up either as a single system or divided into multiple partitions, where each partition is assigned memory, processors, and I/O resources for its exclusive use. Each partition can execute its own OS image.

The Windows Server 2003 operating system family consists of several product editions which share core functionality but offer varying levels of features and scalability. HP Integrity servers support the following editions:

• Datacenter Edition is designed for servers running mission-critical applications

such as databases, enterprise resource planning, high-volume real-time transaction processing, and server consolidation. The 64-bit version supports up to 64 processors, 512 GB memory, and the ability to cluster up to 8 nodes.

• Enterprise Edition is recommended for servers running applications such as

networking, messaging, inventory and customer service systems, databases, and e-commerce Web sites in medium and large enterprises. The 64-bit version supports up to 8-processors, 64 GB memory, and the ability to cluster up to 8 nodes.

The following table shows the certification matrix for HP Integrity server models and Windows Server 2003 OS editions:

Model Enterprise Edition Datacenter Edition

rx1600

rx1620

rx2600

rx2620

rx4640

rx5670

Asia-Pacific region only

✔

Cell-based servers

rx7620

rx8620

Superdome

✔✔

✔

Chapter 1

Planning the installation

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 may be in one of the following states:

• Factory-installed Windows Server 2003

The Windows Server 2003, Datacenter edition is always factory-installed. To get the system up and running, verify the OS was installed correctly, set up the system, and update the system with the latest firmware, drivers, and Microsoft QFEs (patches and fixes) available at the HP Integrity servers support web site or from the latest HP Smart Setup media.

• Factory-installed OS other than Windows Server 2003

If you choose to run Windows Server 2003 instead of an alternate 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 migrating to Windows Server 2003 from another OS, pay close attention to the differences in supported hardware 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.

You can now prepare the server hardware for installation. Use the HP Smart Setup media and the Microsoft Windows Server 2003 RTM (released-to-manufacturing) media to load the OS files on the server (just as in a fresh installation). After installation, set up the system, and update it with the latest firmware, drivers, and Microsoft QFEs (patches and fixes) available at the HP Integrity servers support web site or from the latest HP Smart Setup media.

• 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 files on the server. After installation, verify that the OS was installed correctly, configure the system, and update it with the latest firmware, drivers, and Microsoft QFEs (patches and fixes) available at the HP Integrity servers support web site or from the latest HP Smart Setup media.

• Installed Windows Server 2003 incorrect or inoperable

Prepare the server hardware for installation. Use the HP Re-installation media to copy the OS files, firmware, drivers, and QFEs onto the server. After re-installation, verify that the OS was installed correctly, configure the system, and update it with the latest firmware, drivers, and Microsoft QFEs (patches and fixes) available at the HP Integrity servers support web site or from the latest HP Smart Setup media.

Chapter 1

Planning the installation

Choosing an installation environment

The installation environment consists of the server model, the OS edition, a local console or a remote console, and the media you need to perform the installation. In addition to installing from Smart Setup and Microsoft RTM media or Re-installation media, you can automate the installation of Windows Server 2003 using a Remote Installation Service (RIS) server on the network and a Pre-Boot eXecution Environment (PXE) client on the HP Integrity server.

Table 1-1 lists the HP Integrity server models, the OS edition supported on those models, the console options, and relevant media choices.

Table 1-1 Installation matrix

Server OS Edition Console Media

rx1620 rx2600 rx2620 rx4640 rx5670

Cell-based servers

rx7620 rx8620

Enterprise Local HP Smart Setup and

Enterprise

Datacenter (factoryinstalled)

Microsoft RTM

HP Reinstallation

Remote (headless server)

PXE/RIS

Local HP Smart Setup and

Remote (headless server)

PXE/RIS

Local HP Reinstallation

Remote (headless server)

HP Smart Setup and Microsoft RTM

HP Reinstallation

Microsoft RTM

HP Reinstallation

HP Smart Setup and Microsoft RTM

HP Reinstallation

Superdome Datacenter

(factoryinstalled)

Local HP Reinstallation

Remote (headless server)

HP Reinstallation

Chapter 1

Using a local console

A local console is a VGA monitor, a USB keyboard, and a USB mouse connected to the server. (You may use a USB-to-PS2 dongle to connect to a console switch). If a VGA card is not already installed, you must install the HP Graphics and USB Combo Adapter (A6869A) to use a local console. No other graphics card is supported by HP Integrity servers.

Figure 1-1 shows a local console connected to an HP Integrity rx4640 server:

Figure 1-1 Local console configuration

Choosing an installation environment

HP Integrity rx4640 server (rear)

System Input Power

VAC 200-240 8 A ma x

50/60 Hz

10 00T LAN

PCI- X 66 ( SCS I)

PCI-X 66 (LAN)

Dual SCSI

PCI-X 133

PCI-X 66

Planning the installation

PCI-X 133

USB

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

Advantages • Can specify server settings at the time of installation

• Can log on immediately to Windows after installation completes

• Can perform any administrative tasks directly

Disadvantages • Requires a graphics card to be installed in the server (which may not be the norm in

your server environment)

Chapter 1

Planning the installation

Choosing an installation environment

Using a remote console

A remote console is a PC running terminal emulation software, such as PuTTY (can be installed from the Smart Setup media or from the Web) or the server via the Management Processor (MP) serial port or LAN port.

Figure 1-2 shows remote consoles connected to an HP Integrity rx4640 server:

Figure 1-2 Remote console configurations

SCSI

LVD/SE USB

LAN 10/

100

Management Card

PWR1PWR2

LAN Gb

VGA

RESETSSOF

100

GSP

HAR

CONSOLE /

REMOTE / UPS

TOC

CONSOLE

SERIAL A

SERIAL B

PCI-X 133

PCI-X 133LAN 10/

PUT

AGP

null modem cable to

remote serial port

putty

AUT

INP

putty

LVD/SEUSB

SCSI

LAN 10/

100

Management Card

PWR1PWR2

LAN Gb

VGA

SOFTHARD

100

GSPRESETS

CONSOLE /

REMOTE / UPS

TOC

SERIAL A

SERIAL B

CONSOL

PCI-X 133

PCI-X 133LAN 10/

AGP

HyperTerminal, connected to

HP Integrity rx4640 server (rear)

System Input Power

VAC 200-240 8 A max

50/60 Hz

10 00T LAN

PCI- X 66 ( SCS I)

PCI-X 66 (LAN)

PCI-X 66

Dual SCSI

PCI-X 133

PCI-X 66

cat5 cable to MP LAN port

network

You can install Windows using a remote console. You cannot, however, specify the operating system settings during the installation process.

Advantages • Do not need to install a local console (enables installation of headless server)

Disadvantages • Cannot specify operating system settings at the time of installation

• If you use the MP LAN port, you must assign an IP address to the MP LAN interface. To assign the IP address, you must connect the workstation to the MP serial port, access the MP command menu, enable LAN access, and specify the LAN password.

Chapter 1

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

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

Figure 1-3 PXE/RIS configuration

Planning the installation

Choosing an installation environment

HP Integrity rx4640 server (rear)

System Input Power

VAC 200-240 8 A max

50/60 Hz

null modem cable to

remote serial port

HP Integrity rx4640 server (rear)

PCI-X 133

PCI-X 66

System Input Power

VAC 200-240 8 A max

50/60 Hz

1000T LAN

PCI-X 66 (S CS I)

PCI-X 66 (LAN)

PCI-X 66

Dual SCSI

cat5 cable

to MP LAN port

LAN

1000T LAN

PCI-X 66 (SCSI)

PCI-X 66 (LAN)

Dual SCSI

putty

AUT

INP

RIS

PWR

LAN 10/

100

Management Card

PWR

LAN GbSCSILVD/SE USB

VGA CONSOLE /REMOTE / UPS

LAN 10/100

RESETSSOF

GSP

HAR

putty

LVD/SEUSB

SCSI

LAN 10/ 100

Management Card

PWR1PWR2

LAN Gb

VGA

SOFTHARD

100

GSPRESETS

CONSOLE /

REMOTE / UPS

TOC

SERIAL A

SERIAL B

CONSOL E

PCI-X 133

PCI-X 133LAN 10/

AGP

VISUALIZE

HP Integrity rx4640 server (rear)

TOC

CONSOLESERIAL A

SERIAL B

PCI-X 133

System Input Power

VAC 200-240 8 A max

50/60 Hz

AGP

1000T LAN

PCI-X 66 (SCSI)

PCI-X 66 (LAN)

PCI-X 66

Dual SCSI

Advantages • Installations are automated; no user intervention is needed

PCI-X 66

345

PCI-X 133

PCI-X 66

• Multiple servers can be installed in one batch job

• Installations are standardized; each server receives the same image

• Installations can be done from anywhere on the intranet

Disadvantages • Cannot customize individual installations

• Not supported with Windows Server 2003, Datacenter edition

NOTE Avoid connecting your RIS server to your Integrity server using your intranet during

initial Windows OS installation. You should set up a small “private” network, populated with your RIS server, a hub, and the system LAN NIC on your HP Integrity server. This protects your intranet from errors that might occur during the Windows install process. After you are satisfied the installation process runs smoothly, connect the RIS to target

Integrity servers using your intranet.

Chapter 1

Planning the installation

Using EFI

Using the HP Smart Setup 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 the OS is installed:

• 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 RTM media, which holds the OS image. We strongly recommend that you use EBSU to install the OS.

• After installing the OS, use the Smart Setup media to install drivers, utilities, and important fixes that will ensure the stability and performance of the system.

Using the Microsoft RTM media

You can purchase the Microsoft RTM media, which contains the OS image, either with the HP Integrity Essentials Foundation Pack for Windows from HP or separately from a Windows reseller. Or, your organization may have a volume license for Windows Server 2003, 64-bit version. You will need this media and the license key to install Windows Server 2003 (if Windows is not factory-installed) on HP Integrity servers.

The OS, regardless of source, can easily be installed using the EFI-Based Setup Utility (EBSU) available on the HP Smart Setup media. To access the EBSU, simply boot your server from the HP Smart Setup media, automatically loading the EBSU.

Using the HP Reinstallation media

HP Integrity servers factory-installed with the Windows Server 2003 OS provide the HP Reinstallation media, which allows you to restore the server to its factory condition if necessary. You need the corresponding license key to re-install Windows Server 2003.

Using EFI

The Intel Extensible Firmware Interface (EFI) specification defines a new model for the interface between the operating system, the firmware, and the hardware. EFI serves the same purpose on Itanium-based computers as BIOS on x86-based computers. EFI provides a standard environment for running pre-boot applications and for booting an OS.

HP Integrity servers use EFI to initialize the platform firmware and load the operating system. After the system is initialized, EFI provides two interfaces with which you can interact:

Chapter 1

EFI Boot Manager

First displayed when you power on the server, the EFI Boot Manager provides a menu-based interface (use arrow keys to traverse menus) with options for booting the OS, loading EFI applications, configuring the server, and other pre-boot operations.

Figure 1-4 EFI Boot Manager

Planning the installation

Using EFI

EFI Shell

Available as a selection from the EFI Boot Manager, the EFI Shell provides a command-line interface from which you can get information about the system, install an OS, boot the OS, execute batch scripts, launch EFI applications, load EFI drivers, and manage files and system variables.

See Also • EFI Documentation: http://developer.intel.com/technology/efi/help/efidocs.htm

• EFI Shell commands: From the EFI Shell, type

help or ?

Chapter 1

Planning the installation

Installation Process

The installation process involves preparing the server for the OS, loading the OS on the server, and updating the system with the latest firmware, drivers, utilities, security fixes, and OS fixes. Figure 1-5 shows the main tasks involved in each stage.

Figure 1-5 Installation Overview

Install Microsoft Windows Server 2003 on an HP Integrity server

PREPARE

Start Run setupldr

Set up a console

remote local

Ensure platform compatibility

Check har dw ar e

Check firmware

Back up data

Set u p PXE/RIS

Set up RIS server

Inst all PXE client

LOAD UPDATE

Install OS fixes and security

fixes from the Smart Update CD

Run EBSU

Expr ess/C ustom

Update firmwar e

Create disk partitions

Install diagnostic tools

Run Windows Installer

Expr ess/C ustom

Format syst em p ar tit ion

Copy installer files

Download and install latest OS

fixes , security fixes , and updates

to drivers and documentation at

HP Integrity servers support site:

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

Subscribe to update notifications

at the HP Integrity support site

Run Integrity Support Pack

from the Smart Setup CD

Install nPartition Man agement

Utilities f rom the Smart Setup

itaniumservers/

Prepare hardware

Flash the firmware and install the latest u tilities

available at the HP

Integrity support site:

http://www.hp.com/

support/itaniumservers/

Set up boot drive

Set up CD/DVD drive

Verify acpi flag is set to

windows

Set CLM to 100%

cell-based server with graphics/USB combo car d?

Specify /novesa Osloa d

Set up Windows

Boot to Windows

Complete installation

Specif y system settings

yes

option

Chapter 1

Planning the installation

Installation Process

In practice, there are minor differences—based on the choice of console and installation media—in the sequence of tasks or the interface you would use to perform them. Before perfoming these tasks, refer to the detailed task instructions in the following chapters, noting any warnings or cautions that applying to a given task.

Chapter 1

Planning the installation

Installation Process

Chapter 1

2 Preparing for installation

Getting your server ready to undergo an operating system install involves setting up a console (either local or remote, or both), optionally setting up a PXE/RIS environment, if applicable, and preparing the hardware for installation. If you are migrating from another OS, you must also ensure that the server platform and its peripheral cards are compatible with Windows Server 2003 before proceeding. This chapter provides detailed instructions for each task.

Chapter 2

Preparing for installation

Ensuring platform compatibility

If you are migrating from another operating system to Windows Server 2003, ensure that the firmware is up to date, that the hardware is compatible, and any data on the

server disk is backed up.

Check system firmware version

To check the system firmware version:

Step 1. Boot the server to EFI.

Step 2. At the EFI Shell prompt, type info fw.

The EFI shell lists the firmware version as follows:

FIRMWARE INFORMATION Firmware Revision: All CELLS - 1.12 Thu Oct 16 08:10:32 2003

Step 3. Check the installed version against the version present on the HP Smart Setup media or

on the HP Integrity support site at http://www.hp.com/support/itaniumservers/.

NOTE For rx7620, rx8620, and Superdome servers, contact HP support or an HP CE to obtain

the latest firmware.

Check hardware compatibility

To verify that your existing hardware is compatible with Windows Server 2003:

Step 1. Refer to the Supplies and Accessories page for each server to check supported hardware

configurations. For example, the Supplies and Accessories page for the rx8620 server at http://www.hp.com/products1/servers/integrity/mid_range/rx8620/supplies.html lists the processors, memory, adapters, cards, and controllers that are available for that server.

Step 2. Verify existing device compatibility at the HP Integrity server connectivity site at

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

Step 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 may 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-storage compatibility.

Preparing servers with 4GB DIMMs

You must install a Microsoft QFE (KB867582) for a successful Windows Server 2003 install. To install the OS on a server with 4GB DIMMs, you install the OS, then install the Microsft QFE (the QFE is installed automatically if you install your OS using the HP Re-install CD).

Chapter 2

Preparing for installation

Ensuring platform compatibility

Back up existing data

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

Step 1. Perform a server-wide backup using your existing backup utilities.

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

Step 3. Store the backup in a safe place.

Chapter 2

+ 43 hidden pages