HP Integrity Servers with Microsoft® Windows Server™ 2003 for Itanium-Based Systems Installation Guide HP Part Number: 5992-4479 Published: September 2008
© Copyright 2008 Hewlett-Packard Development Company, L.P. Legal Notices 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.........................................................................................................9 Intended Audience.................................................................................................................................9 New and Changed Information in This Edition.....................................................................................9 Document Organization.....................................................................
Run Windows Setup........................................................................................................................36 Specify Server Settings.....................................................................................................................37 Install from PXE....................................................................................................................................37 Reinstall from a Headless Console.............................................
EFI Boot Manager............................................................................................................................69 EFI Shell...........................................................................................................................................69 Common EFI Shell Commands.......................................................................................................70 EFI-Based Setup Utility................................................................
Booting and Resetting nPartitions...................................................................................................92 Using the MP Command Menu.................................................................................................93 Using the EFI Shell.....................................................................................................................93 Using Microsoft Windows Commands.................................................................................
List of Figures 1-1 1-2 1-3 2-1 2-2 2-3 2-4 2-5 2-6 2-7 2-8 2-9 2-10 2-11 2-12 2-13 3-1 3-2 3-3 3-4 3-5 3-6 3-7 3-8 3-9 3-10 3-11 3-12 3-13 3-14 3-15 B-1 C-1 C-2 E-1 Headless console configurations...................................................................................................18 GUI console configuration............................................................................................................20 PXE/WDS configuration.......................................................
List of Tables 1-1 1-2 1-3 1-4 2-1 B-1 8 Installation matrix.........................................................................................................................14 Locating the Microsoft Certificate of Authenticity (COA) on your server...................................16 Graphics support on server models..............................................................................................20 EFI device mapping fields..............................................................
About This Document This document describes how to install and configure the operating system and HP software on HP Integrity servers running Windows Server 2003. The document printing date and part number indicate the document’s current edition. The printing date changes when a new edition is printed. Minor changes may be made at reprint without changing the printing date. The document part number changes when extensive changes are made.
“EFI Utilities” (page 69) An overview of the server's Extensible Firmware Interface (EFI) and EFI-Based Setup Utility (EBSU). “nPartitioning” (page 77) An overview of how to configure a single system into several independent, partitioned systems, each with hardware and software isolation. “SMH and Management Agents” An overview of the HP Insight Management Agents and how to configure System (page 95) Management Homepage (SMH) to administer your system locally or remotely.
• For technical support resources (drivers, patches, upgrades, migration issues, to sign up for alerts, etc.): http://hp.com/support/itaniumservers/ • For information about HP Integrity Virtual Machines (Integrity VM): http://h71028.www7.hp.com/enterprise/cache/262803-0-0-0-121.html Publishing History The publishing history below identifies the edition dates of this manual. Updates are made to this publication on an unscheduled, as needed, basis.
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 (Microsoft QFEs). 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.
3. Verify storage compatibility by reviewing the HP Integrity Server-Storage support matrices here: http://www.hp.com/products1/serverconnectivity/support_matrices.html This list is not exhaustive. 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.
Table 1-1 Installation matrix (continued) Server Model Installation Method Installation Media rx7620 Headless console Windows Server 2003 OS disc (provided by Microsoft) + HP Smart Setup disc + HP Smart Update disc rx8620 rx8640 HP Reinstallation disc + HP Smart Setup disc + HP Smart Update disc rx7640 Superdome GUI console Windows Server 2003 OS disc (provided by Microsoft) + HP Smart Setup disc + HP Smart Update disc (sx1000 and sx2000) HP Reinstallation disc + HP Smart Setup disc + HP Smart U
Table 1-2 Locating the Microsoft Certificate of Authenticity (COA) on your server 16 Integrity Server Location rx2660 The COA is located on the left side panel, in the middle, as shown here. rx3600 The COA is located on the left side panel, as shown here. rx6600 The COA is located on the left side panel, as shown here. BL860c and BL870c 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.
Table 1-2 Locating the Microsoft Certificate of Authenticity (COA) on your server (continued) Integrity Server Location rx7620 and rx7640 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. rx8620 and rx8640 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.
Task 6: Set up an Installation Method You must choose one of the following methods to install the operating system: • Local installation methods: — Headless console — GUI console • Remote installation methods: — Integrated Remote Console (IRC), available on rx2660, rx3600, rx6600, BL860c, BL870c, rx7640, rx8640, and Superdome/sx2000 servers only — Preboot execution environment (PXE) + Windows Deployment Services (WDS), or PXE/WDS If you are installing locally, you must set up your server with a headless o
You can configure a headless console in one of the following ways: • • • Using a null modem cable Using a cat5 LAN cable Using a Remote Serial Console (for rx2660, rx3600, rx6600, BL860c, BL870c, rx7640, rx8640, and Superdome/sx2000 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.
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.) If a VGA card is not 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 server.
8. The set up is complete. Proceed to the GUI Console installation process: “Install from a GUI Console” (page 34). To install the HP Graphics and USB Combo Card using the Enhanced interface (gray background), complete the following steps: 1. 2. 3. 4. 5. 6. 7. 8. Install the HP Graphics and USB Combo Card in an open PCI slot of the server. Connect a VGA monitor, USB HP keyboard, and USB mouse to the relevant ports. Boot the server to EFI. From the EFI Boot Manager, select Boot Configuration.
2. 3. 4. 5. 6. Enter your user name and password to log in to the System Management Homepage. On the Administration tab, select Licensing in the left panel. Enter the license number. On the Remote Console tab, select Integrated Remote Console in the left panel. Click the Launch button. If Launch is grayed out, the license might be invalid or expired. A new window appears, providing access to the IRC.
Figure 1-3 PXE/WDS configuration NOTE: When you perform a PXE/WDS headless installation, note the following: • Headless installations using PXE/WDS are not supported with Windows Server 2003, Datacenter Edition. Use the HP Reinstallation media instead. • Do not connect the WDS server to the Integrity server using your intranet during initial Windows OS installation. Set up a small private network, populated with the WDS server, a hub, and the system LAN NIC of the HP Integrity server.
For detailed descriptions of the concepts, tasks, best practices, and troubleshooting tips for setting up a WDS server, see the Microsoft Windows Server 2003 Technical Reference website: http://www.microsoft.com/windowsserver2003/proddoc/default.mspx Specifically, go to this link: http://technet2.microsoft.com/WindowsVista/en/library/ 9e197135-6711-4c20-bfad-fc80fc2151301033.mspx?mfr=true Install WDS You can install WDS using the Control Panel or an unattended Setup answer file.
2. 3. 4. 5. 6. 7. In the console tree, go to Active Directory Users and Computers > Applicable domain > Applicable organizational unit (such as Computers/Applicable WDS server), and right-click the applicable WDS server. Click Properties. Then, in the Properties dialog box, go to the Remote Install tab and click Advanced Settings. In the Advanced Settings dialog box, go to the New Clients tab.
• previous installation attempt failed; however, you are not required to answer questions answered in 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 OS. Examples of these tools include system flash BIOS updates, computer diagnostic tools, and virus scanning utilities.
1. From the EFI Shell, enter the reconnect –r command. The reconnect command reconnects drivers from a device, disconnecting drivers from all devices and then reconnecting them. If you do not specify a device handle, the reconnect operation is performed on all handles in the system. If you 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 mappings in a system.
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. 3. If the flag is not set to windows, enter the acpiconfig windows command. Enter the acpiconfig command again to display the settings again and verify that the flag is set correctly. Windows Server 2003 implements the ACPI 1.0b specification with some extensions from version 2.0, whereas HP-UX and Linux implement ACPI 2.0.
2 Installing the OS This chapter provides instructions for installing the operating system (OS) using a headless console, a GUI console, or a Preboot Execution Environment (PXE) enabled network interface card (NIC). This chapter also provides reinstallation instructions for Windows Server 2003. Each method comprises a series of tasks, concluding with two tasks that verify that the OS was installed correctly. You must install the HP Integrity Support Pack after installing the OS.
NOTE: For an overview of the benefits, concepts, and terminology of headless OS installation on HP Integrity servers, see “Headless Windows Installations” (page 103). Run EBSU The EFI-Based Setup Utility (EBSU) provides an easy-to-use interface to flash the firmware, partition the hard disk, install diagnostic tools, configure storage controllers, and run other EFI utilities. NOTE: If you are installing an HP Virtual Machines (HPVM) Windows guest, you do not need to run EBSU as part of your setup.
Figure 2-2 Select Express Setup 6. 7. EBSU displays the Express Setup introduction. Press Enter to continue. EBSU displays the firmware update screen, listing each device, its installed firmware version, and the firmware version on the Smart Setup media. Select the firmware devices you want to update. To continue, select Next and press Enter. Figure 2-3 Firmware update NOTE: You might not be able to use EBSU to flash the firmware of some devices.
Figure 2-4 Partition disk 9. Select the option to install offline diagnostic tools (from the HP Itanium Processor Family offline diagnostics and utilities CD). 10. Also select the option to launch the Windows OS installer, select Setup, and press Enter. Figure 2-5 Install diagnostic tools 11. EBSU displays the partition confirmation window. Select Continue and press Enter.
12. EBSU prompts you to insert the Microsoft Windows Server 2003 CD in the DVD drive. Insert the CD and press Enter. Figure 2-6 Insert the Microsoft Windows Server 2003 CD Run Windows Setup Windows Setup prompts you to create a system partition on the boot disk if needed, copies the OS files on to that partition, and attempts to reboot from the boot disk. To run Windows Setup, complete the following steps: 1. Insert the Microsoft Windows Server 2003 CD in the DVD drive, and Windows Setup launches.
Install from a GUI Console This section describes how to install the OS using a GUI console. Run EBSU EBSU provides an easy-to-use interface to flash the firmware, partition the hard disk, install diagnostic tools, configure storage controllers, and run other EFI utilities. NOTE: If you are installing an HPVM Windows guest, you do not need to run EBSU as part of your setup. Skip this section and go to the next section: “Run Windows Setup” (page 36). To run EBSU, complete the following steps: 1.
6. 7. EBSU displays the Express Setup introduction. Press Enter to continue. EBSU displays the firmware update screen, listing each device, its installed firmware version, and the firmware version on the Smart Setup media. Select the firmware devices you want to update. To continue, select Next and press Enter. Figure 2-9 Firmware update NOTE: You might not be able to use EBSU to flash the firmware of some devices.
Figure 2-11 Install diagnostic tools 11. EBSU displays the partition confirmation window. Select Continue and press Enter. 12. EBSU prompts you to insert the Microsoft Windows Server 2003 with SP2 CD in the DVD drive. Insert the CD and press Enter. Figure 2-12 Insert the Microsoft Windows Server 2003 CD Run Windows Setup Windows Setup prompts you to create a system partition on the boot disk if needed, copies the OS files on to that partition, and attempts to reboot from the boot disk.
3. 4. 5. If Windows Setup cannot find a system partition, when you are prompted, press Enter to continue. Windows creates a partition and then prompts you to format it. Select the partition on which to install the OS and press Enter. Windows formats the partition if necessary, checks the partition for errors, and begins to copy the OS files. Monitor the copy process until it completes. You can monitor installation progress from the SAC command prompt by using these three channels: setuplog.txt, setupact.
2. 3. 4. 5. 6. 7. At the Boot Manager, select the Boot Options menu. From the list of available boot sources, select the NIC to boot from and press Enter. At the PXE boot status window, press Enter to continue. At the login screen, enter a valid user name and password, and press Enter. At the OS selection screen, select the OS to be installed and press Enter to start the installation. Complete the installation by following the instructions on the screen.
7. 8. Log in to the MP port again using HyperTerminal or PuTTY, and enter the MP user name and password. At the MP> prompt, type co and press Enter. NOTE: With rx2660, rx3600, rx6600, BL860c, BL870c, rx7640, rx8640, and Superdome/sx2000 servers, you can also use Remote Serial Console to perform this step. 9. Boot from the Reinstallation media using one of the following methods: • Method 1: Select EFI Boot Manager menu > Internal Bootable DVD from EFI Boot Manager (if this choice is available).
1. 2. 3. 4. 5. Open a terminal server client and log in to Windows Server 2003 by typing Administrator for the user name and Abcdef12 (case-sensitive) for the password. The system prompts you to insert the HP Smart Setup media to install the latest HP drivers and utilities. • Click Yes if you want to do this now. You will be guided through an installation process similar to the one described here: “Install the Integrity Support Pack (ISP)” (page 51).
IMPORTANT: If you are installing an HPVM Windows guest, you must issue an IN command (for “insert”) from the HPVM console menu every time you insert a disc. If you do not issue the command, the server does not recognize the disc and appears to hang. 4. Boot from the Reinstallation media using one of the following methods: • Method 1: Select EFI Boot Manager menu > Internal Bootable DVD from EFI Boot Manager (if this choice is available).
2. 3. 4. The system prompts you to reboot. Click Yes to reboot. To secure your server properly, HP strongly recommends that you change your Administrator password after the reboot. Install any available operating system updates using your HP Smart Update media. For instructions, see: “Apply OS Updates Using the Smart Update Media” (page 42) Your system is now ready to go online. Apply OS Updates Using the Smart Update Media Install the latest OS and security updates from the HP Smart Update media.
1. 2. 3. 4. Select Start > Settings > Control Panel > Network Connections. Right-click the Local Area Connection icon and select Properties. Select Internet Protocol TCP/IP and click Install. Click OK. Install SNMP SNMP support is included in Windows Server 2003. To install the SNMP Protocol, complete the following steps: 1. 2. 3. 4. 5. 6. 7. Select Start > Settings > Control Panel. Click Add or Remove Programs. Click Add/Remove Windows Components.
Enable and Run Remote Desktop Connection The remote administration mode is enabled by default on Windows Server 2003 if you use the HP Reinstall media. If you install or reinstall using Microsoft OS media (for example, if you have a volume license from Microsoft), Remote Desktop functionality is disabled. Users must have unique user names. Windows does not permit two users with the same name to log on simultaneously. To enable remote desktop connections from a GUI console, complete the following steps: 1.
1. 2. Use the arrow key to select EFI Shell, and then press Enter. At the EFI Shell prompt, enter 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 3. Verify the installed version with the version present on the HP Smart Setup media or on the HP Integrity support site at: http://www.hp.
6. Scan the listed devices, verifying that no device displays a yellow bang (!) or a question mark (?). • A yellow bang (exclamation mark) indicates a hardware problem, a device driver problem, a missing .ini file, or a resource conflict with the flagged device. • A question mark indicates that Windows has received information that the flagged device is installed but Windows cannot find or recognize it.
• • • Install the OS remotely from a headless console instead. See “Install from a Headless Console” (page 29). Disconnect the local graphics console before you install Windows using IRC, and then reconnect it afterwards. This method is easy and therefore recommended. Create a boot entry that includes the/NOVESA option. If you select the last option, the Windows installation fails during plug-n-play detection of the system’s monitor and video controller.
• • A VM host (the physical system where the virtual machines reside) Virtual machines, also known as guests Virtual machines, or guests, are abstractions of real, physical machines. They are fully loaded operational systems, complete with OS, system management utilities, applications, and networks, all running in the virtual machine environment that you set up for them.
Enable Hyperthreading Using Partition Manager Another way to enable hyperthreading (on partitionable servers only) is to use the Partition Manager partitioning tool. Partition Manager is a Web-based application for system administrators that provides a convenient GUI for creating, configuring, and managing hard partitions (nPartitions) on an HP Integrity server.
3 Installing and Configuring the Management Tools This chapter describes how to install the tools, applications, and drivers needed to manage your Integrity server. Install the Integrity Support Pack (ISP) This procedure describes how to install the Integrity Support Pack locally (onto the same system that the SmartSetup CD is inserted into) or using the Integrated Remote Console method.
8. 9. The Discovery Progress screen appears as HPSUM checks the local system to see which components are installed. When the discovery process finishes, the Select Bundle Filter screen appears and lists the Integrity Support Packs that were found on the Smart Setup media. Select HP Integrity Support Pack for Windows Server 2003 on Itanium-based Systems (if multiple Integrity Support Packs are available, you must select the one marked “2003”). Also select “FORCE ALL BUNDLE UPDATES”. Then click OK.
Figure 3-3 HPSUM Select Items to be Installed screen Install the Integrity Support Pack (ISP) 53
11. When the installation finishes, the Installation Results screen appears. You might be prompted to reboot the server to complete the installation of some components. Even if you are not prompted, reboot the server by clicking Reboot Now. Figure 3-4 HPSUM Installation Results screen The latest Integrity Support Pack can also be downloaded from the HP Integrity server support website: http://www.hp.com/support/itaniumservers/. On the Technical Support page, click on your Integrity server model number.
Set Up Browser Access To display data from the WebAgents using SMH, you must use a browser that includes support for tables, frames, Java, and JavaScript. You must turn on the following options: • Enable Java • Enable JavaScript • Accept all cookies HP's web-enabled management software requires Java Virtual Machine (JVM) for full functionality. Depending on the web-enabled management software installed, some features might require the presence of Java support in the browser.
IMPORTANT: For Windows operating systems, the file system must be NTFS for the private key to have administrator-only access through the file. If the private key is compromised, the administrator can delete the \hp\sslshare\cert.pem file and restart the server. This causes HP SMH to generate a new certificate and private key. NOTE: Certificate and private key generation only occur the first time HP SMH is started or when no certificate and key pair exist.
Configure the Event Notifier The event notifier monitors agent events and sends email notifications when designated events occur. Use the event notifier configuration wizard to configure email addresses, entity types, and events triggers. Use the configuration wizard to completely configure the notification service. To configure the event notifier, complete the following steps: 1. From Windows, select Start > HP Insight Management Agents > Event Notifier Configuration Wizard. A Welcome screen appears.
Figure 3-8 Event recipients information In this window, you add users to receive event messages. 6. Click Add to add a user or click Edit to edit the properties for an existing user. The following screen appears. Figure 3-9 Adding a new user 7. 8. 9. From the Receiver type drop-down list, select the email recipient type. Click OK to return to the recipient information window. Select a user name and click Edit to edit user properties, or select a user name and click Delete to remove a user. 10.
Figure 3-10 Event selection window 11. Use the Severity and Source filter fields to view selected events only. The event severity levels, source, and message are not user-configurable. 12. Click the check box to enable an event or disable email notification for an event. 13. Click Use Default to load the current default event notification settings. 14. Click Set Default to set and save the current notification settings as the default values. 15.
3. 4. 5. 6. From the Data Collection Interval list box, select a time interval for SNMP data collection. Click the Send Test Trap button (available only if the HP host agent is active) to send a test trap. Click Clear All Thresholds to clear current SNMP trap threshold values. Click OK.
6. 7. 8. Click Delete to delete a process selected from the list. You can only delete processes that a user has created. The Delete button is disabled for system default processes. Click OK to confirm. Click OK when you finish configuring process monitoring. Send SNMP Traps to Management Applications by IP Address Configure SNMP services with specific IP addresses to send SNMP traps to an SNMP management application with an IP address.
Figure 3-14 SNMP traps tab 6. In the Community name field, if a community name exists, select it; if not, enter a community name and click Add to List. The default community string for HP Insight Manager is public. If you enter a different community string here, enter the same string on the management console that is responsible for the system. HP recommends not using the string public because it is the default value, commonly used, and can present a security risk. 7.
Verify nPartition Commands 1. Perform a local management test by opening a command prompt window and issuing the following command: C:\Documents and Settings> parstatus -X If you run this command on an nPartition, it displays information about the local server’s nPartition configuration. No error messages should be returned.
4. In order to test remote IPMI connections, do the following: a. Enter the host name and IP address of the remote management processor that you want to connect to, along with the IPMI password for that MP in the bottom half of the Partition Manager login screen. b. Click OK. 5. Verify correct operation of Partition Manager.
A Preparing the Server for Microsoft SQL Server This appendix describes the server configuration tasks needed to install Microsoft SQL Server.
Install SQL Server from the Command Prompt To install a standalone instance of SQL Server from the command prompt, do the following: 1. Insert the SQL Server 2005 installation media into the disk drive. 2. For instance-aware components (the Database Engine, SQL Server Agent, Analysis Services, and Reporting Services) use the following syntax: Start /wait \setup.
10. On the Instance Name page, select a default or named instance for the installation. If a default or named instance is installed and you select the existing instance for your installation, setup upgrades it and provides you the option to install additional components. To install a new default instance, a default instance must not exist on the computer. To install a new named instance, click Named Instance and then enter a unique instance name in the space provided. 11.
B EFI Utilities This appendix provides an overview of the Extensible Firmware Interface (EFI) and the EFI-Based Setup Utility (EBSU). The EFI provides access to the server before the operating system (OS) stage, which enables you to flash the firmware, partition the hard disk, install diagnostic tools, configure storage controllers, and run other EFI utilities. Introduction to EFI EFI is an interface between operating system, firmware, and hardware.
Common EFI Shell Commands The following table lists common EFI commands. Table B-1 EFI Shell Commands and Descriptions Command Description Boot Commands autoboot Set and view the autoboot timeout variable. bcfg Display and modify the driver and boot configuration. boottest Set and view BootTest bits. dbprofile Display and modify direct boot profiles for use by lanboot. lanboot Boot over the LAN. reconfigreset Reset the system (nPartition) for reconfiguration.
Table B-1 EFI Shell Commands and Descriptions (continued) Command Description connect Bind a driver to a device. dblk Hex dump – BlkIo devices. devices Display devices managed by EFI drivers. devtree Display tree of devices. dh Dump handle information. disconnect Disconnect drivers from devices. drivers Display list of drivers. drvcfg Invoke the Driver Configuration Protocol. drvdiag Invoke the Driver Diagnostics Protocol. guid Dump known GUID IDs. lanaddress Display the MAC address.
Table B-1 EFI Shell Commands and Descriptions (continued) Command Description Memory Commands Commands for listing and managing memory, EFI variables, and NVRAM details. default Set default NVRAM values. dmem Dump memory or memory-mapped I/O. dmpstore Display EFI variables. memmap Display the memory map. mm Display and modify MEM/IO/PCI. pdt View and clear nPartition or cell memory page de-allocation table (PDT).
EFI-Based Setup Utility The EFI-Based Setup Utility (EBSU) provides an easy-to-use interface to flash the firmware, partition the hard disk, install diagnostic tools, configure storage controllers, and run other EFI utilities. EBSU provides the following functions: • Express Setup — Guides you through Windows installation and setup. For detailed information on using Express Setup, see “Run EBSU” (page 34).
You cannot unload or change the virtual floppy file system unless you reset the computer. CAUTION: When Windows installation begins, you are prompted to press F6 to install a third-party SCSI or RAID driver. Do not press F6. Pressing F6 forces Windows to look for the driver on a physical floppy drive, which does not exist. The driver is loaded into memory and installed automatically. • • System Inventory — Retrieves system information and displays a report of the system hardware.
3. 4. 5. 6. At the fs0:> prompt, enter cd MSUTIL. At the fs0:\MSUTIL> prompt, execute the NVRBOOT.EFI boot utility. Enter I to Import. Enter the following path: EFI\Microsoft\Winnt50\boot0001 7. 8. Click Exit to return to the EFI Boot Manager utility. Boot the server using the new Windows entry.
C nPartitioning This appendix introduces node partitions (nPartitions) on cell-based HP Integrity servers running Microsoft® Windows® Server 2003 and describes the tools to manage them. A cell-based HP Integrity server (such as the rx7620, the rx7640, the rx8620, the rx8640, or Superdome) can be configured as a single system or partitioned into several independent systems.
Getting to Know nPartitions Partitions are physical or logical mechanisms for demarcating operational environments within a single system or across multiple systems. Partitioning lets you consolidate systems, allocate computing resources in response to fluctuations in demand, maximize resource use, and protect operating environments from disruptive events. Partitioning Continuum HP offers a continuum of partitioning technologies, as shown in Figure C-2.
The hardware of a cell-based server—including cells, I/O expansion cabinets, cables, cabinet hardware, fans, and power and utility components—is known as a server complex: • A Superdome server complex can consist of one or two server cabinets and can include one or two I/O expansion cabinets (which provide additional I/O chassis). • An rx8620 or rx8640 server complex consists of a single server cabinet and can include one I/O expansion cabinet (which provides two additional I/O chassis).
I/O chassis with core I/O), only one core I/O is actively used in an nPartition. System firmware selects the core cell in the early stages of the nPartition boot process. When none of the core cell choices can serve as the active core cell, the nPartition attempts to select an eligible cell. The core I/O in the I/O chassis connected to the core cell provides console access for the nPartition through the management processor.
3. I/O discovery, and discovery of interconnecting fabric (connections between the cell and other cells, I/O, and system crossbars). The firmware completes self-tests and discovery, reports the hardware configuration of the cell to the management processor (MP), informs the MP that the cell is “waiting at BIB,” and then waits for the cell BIB flag to be cleared. nPartition Boot Phase After its cells have completed their self-tests, the nPartition is booted.
Management processor (MP) menus Management processor menus provide a service interface that provides access to all hardware and nPartitions in the complex. The MP is always available, whether or not nPartitions are configured or booted in the server complex. Management Interface Options You can manage nPartitions remotely using one of two management interfaces: the Intelligent Platform Management Interface (IPMI) and the Web-Based Enterprise Management (WBEM) infrastructure.
The nPartition Provider caches the static data and reuses it for subsequent requests so that future command usage does not incur that initial overhead. If the PC is rebooted or the nPartition Provider is restarted, the cached data is lost. The first request to the MP after the restart requires the same initial overhead. IPMI specifies that data be sent as UDP datagrams over the LAN. UDP does not guarantee delivery of datagrams.
data in a consistent fashion. Client applications can then use this information to manage an enterprise computing environment. Because WBEM supports a distributed management architecture, client applications (nPartition management tools, for example) can run on a remote system and use the WBEM infrastructure to send requests to managed servers. Partition Manager is a WBEM client application. Partition Manager uses WBEM when retrieving information about a server complex.
Running Partition Manager Using WBEM You can run Partition Manager with WBEM in one of two ways: • If you are running Partition Manager on an nPartition: Select the Switch Complexes task from the Tools menu. In the resulting dialog, enter the host name or IP address of the remote nPartition, and supply a user name and that user’s password. To display information about the target complex, specify a user defined on the remote nPartition.
• Simple installation: Install all components on an nPartition (fewer components must be installed manually when reinstall media is used). • Simple connection: Log in to SMH and run Partition Manager, or run nPartition commands with no -g/-u options. No additional authentication or login steps are required to manage the local complex. • Controlled configuration of specific nPartitions with the nPartition Config Privilege option: You can restrict to configuration of certain nPartitions.
• Authentication is implemented by the OS login to the nPartition (the account used to log in to Windows on the nPartition where the tools are run). • For Partition Manager (a web application), you are prompted for login credentials when you first access an SMH or Partition Manager web page (locally or from a remote browser).
Setting up the Management Station A management station is often used to configure and administer nPartitions on an HP Integrity server. If HP provided your management station (for example, the PC-SMS management system supplied with Superdome servers), then nPartition tools and support components are installed.
Telnet Because nPartition commands are executed from a command prompt, you can use a telnet application (the telnet command in Windows or a third-party application, such as Reflection 1) to open a command prompt on the management station. The management station must have the Telnet service installed and started. To execute nPartition commands using a telnet connection to the management station, do the following: 1.
Using the Management Processor Command Menu You can list hardware and nPartition status with the following commands, available from the management processor Command menu. CP List nPartition configurations, including assigned cells. PS List cabinet, power, cell, processor, memory, I/O, and other details. IO List connections from cells to I/O chassis on HP Superdome servers. ID List product and serial numbers.
complex (for example, with the -u... -h... options). For remote administration using IPMI over LAN, the tool accesses the MP (for example, with the -g... -h... options). Modifying nPartitions Modifying an nPartition involves using an nPartition administration tool to revise parts of the server Complex Profile data, which determines how hardware is assigned to and used by nPartitions: • Use parmodify or Partition Manager from an nPartition running in the same complex as the nPartition.
Modifying nPartitions includes the following tasks: • Assign (add) or unassign (remove) cells from an nPartition: — In the Partition Manager Hardware tab, select an nPartition and cell and then select nPartition > Assign cell(s) / Cell > Assign cell(s) or nPartition > Unassign cell(s) / Cell > Unassign cell(s). — Alternatively, use the parmodify -p# -a#... command to add a cell or the parmodify -p# -d#... command to remove a cell from the nPartition (-p#, where # is the partition number).
Using the MP Command Menu The MP provides the following commands, available from the Command menu, to support boot and reset operations: RS Reset an nPartition. Reset an nPartition after self-tests and partition rendezvous are complete. RR Perform a shutdown for reconfig of an nPartition. Reset an nPartition after self-tests and partition rendezvous are complete. BO Boot the cells assigned to an nPartition past the waiting at BIB state and begin the nPartition boot phase.
On mid-range servers, the default behavior is for shutdown /s to cause nPartition hardware to be powered off. Use the EFI Shell command acpiconfig disable softpowerdown instead to make cells remain at a wait at BIB state.
D SMH and Management Agents System Management Homepage (SMH), combined with HP Insight Management Agents, enable you to view subsystem and status information from a Web browser, locally or remotely. You can access HP Insight Management Agents from 32-bit systems and Integrity servers.
System configuration information System Devices Status Device Settings Collects configuration information of server hardware-related devices such as CPU, Memory, I/O, cooling, power supply, and cabinets. Provides dynamic status of monitored devices in the server (for example, cooling devices, temperature sensors, and power supplies) and of the watchdog timer used for automatic server recovery.
Event subsystem information Automatic Server Recovery Enables a service that monitors events from System Events Log (SEL), Forward Progress Log (FPL), and the MP, and generates traps when events are found. Enables a service that checks if the system is frozen and if so, reboots the system. Using SMH SMH enables you to administer systems locally via a web-based GUI. It provides a single, hierarchical menu interface that enables you to quickly find and invoke applications to perform common system tasks.
7. Click a specific device name to see current status for that device. The window that appears depends on the configuration of your server. All SNMP devices are displayed. Navigating SMH SMH displays HP Web-enabled System Management software. In addition, SMH displays the status of the items grouped by category. For more information, see the online help. The SMH interface is separated into the following two frames: Header frame The header frame is constantly visible regardless of the page you are viewing.
• — Integrated agents Contains participants and links to entry points if applicable. You can click an agent link to access the agent. — Other agents Lists the visible HP Web-enabled System Management Software that does not participate in HP SMH. — Management processor Displays a link to the Integrated Lights-Out (iLO) board. — Other software Can provide links to Integrity, Support, and Forums. — Key Displays a list of status icons and a brief description of each.
Network The NIC Management Agents display logical HP NICs that are configured on the system you are viewing. This can be a virtual NIC, single NIC, or teams of NICs. The information displayed depends on the type of NIC, and can include the following: • NIC controller information • NIC interface information • Ethernet statistics • Logical adapter information Storage The Storage section provides an overview of the selected server's mass storage subsystem.
utilization (network utilization in total bytes/second, server sessions, context block queue/second, and % total page file usage). • File System Space Used Information includes volume name, used space, unused space, and percentage of space used. • HP Insight Agents Processes Information includes process name and status (started or stopped).
• System Summary Provides general information that includes system model name, operating system, HP Insight Agents version, system UUID, bay number, blade size, system firmware version, BMC firmware version, management processor firmware version, HPVM firmware version, management processor host name, lights-out management processor IP address, lights-out management processor home page URL, crash dump information, and current and minimum paging file size.
E Headless Windows Installations Users of Microsoft Windows Server 2003 and Windows Server 2008 are familiar with the setup, installation, and operation of systems using a keyboard, video, and mouse. However, these users might not be familiar with the set of headless functionality provided by HP Integrity servers. Integrity servers provide a set of tools to set up, install, manage, and use the system in a headless manner.
For future systems there may be many customized partitions that require careful allocation of IO slots. Avoiding the consumption of slots for non-critical use such as graphics will ease the deployment of future systems. Customers should start to deploy and operate systems using headless methods. How to Access a Headless System Users have full access to the GUI of a system through the use of Remote Desktop. From any client PC on the network, running the Terminal Services Client (mstsc.
This path can host multiple channels of communication, from firmware messages at power-on to a command-line interface when the OS has booted. In Integrity systems, this EMS port is connected to the MP and is accessible from the management LAN or management serial port. Firmware Redirection When the server powers on, the system firmware is responsible for configuring all hardware and loading EFI. This phase is also called FW or BIOS console redirection.
Cellular Systems There are two options for changing network parameters in cellular systems: • Systems can be connected to the LAN one at a time and the user can use telnet to connect to the factory default IP address and change the network address. After this address is changed, the next system can be connected to the LAN without creating an address conflict. • The user can use the management serial port and connect a terminal or a PC running a terminal emulator such as Hyperterm.
