HP Integrity Servers with Microsoft® Windows Server™ 2003 for Itanium-Based Systems Installation Guide HP Part Number: 5992-5570 Published: May 2009
© Copyright 2009 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.....................................................................
Load the System Image to the Boot Disk.........................................................................................36 Configure after the Initial Boot........................................................................................................37 Reinstall from a GUI Console...............................................................................................................38 Load the System Image to the Boot Disk...............................................................
Common EFI Shell Commands.......................................................................................................70 EFI-Based Setup Utility...................................................................................................................73 Creating a Boot File Using the EFI Shell...............................................................................................74 Verify Successful Boot File Creation..................................................................
Using the EFI Shell.....................................................................................................................93 Using Microsoft Windows Commands......................................................................................93 D SMH and the WBEM Providers/SNMP Management Agents...............................95 WBEM Providers..................................................................................................................................
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 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 3-16 B-1 C-1 C-2 E-1 Headless console configurations...................................................................................................16 GUI console configuration............................................................................................................18 PXE/WDS configuration.......................................................
List of Tables 1-1 1-2 1-3 B-1 8 Installation matrix.........................................................................................................................14 Graphics support on server models..............................................................................................18 EFI device mapping fields.............................................................................................................25 EFI Shell Commands and Descriptions................................
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.
Document Organization This document is organized as follows: “Preparing for the Installation” (page 13) Describes the steps to prepare the server for installation of the operating system, SmartSetup, and management software. “Installing the OS” (page 27) Describes how to install the operating system software. “Installing and Configuring the Describes how to install the server management software.
Related Information You can find more information about HP Integrity servers, server management, and software in the following locations: • For an overview of the HP Integrity server family: http://hp.com/go/integrity • For other documents supporting Windows Server 2003 on HP Integrity Servers: http://docs.hp.com/en/hw.html#Windows%2064-bit%20on%20HP%20Integrity%20Servers • For technical support resources (drivers, patches, upgrades, migration issues, to sign up for alerts, and so on): http://hp.
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 Cell-Based Servers Headless console rx8640 rx7640 Superdome sx2000 Installation Media Windows Server 2003 OS disc (provided by Microsoft) + HP Smart Setup disc + HP Smart Update disc HP Reinstallation disc + HP Smart Setup disc + HP Smart Update disc GUI console Windows Server 2003 OS disc (provided by Microsoft) + HP Smart Setup disc + HP Smart Update disc HP Reinstallation disc + HP Smart Setup disc + HP Smart Update disc PXE
Task 5: 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) — 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 or GUI console.
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 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 from the PuTTY website: http://www.chiark.greenend.org.uk/~sgtatham/putty/download.
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. Figure 1-2 GUI console configuration A GUI console provides complete access to all installation and administration tasks that you can perform on the server.
2. 3. 4. 5. 6. 7. 8. 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. Select Console Configuration. Select Select Output Console. Select the graphics card PCI device and press Enter. The video display is now directed to the GUI console. The set up is complete. Proceed to the GUI Console installation process: “Install from a GUI Console” (page 31).
Set up a Virtual Media (vMedia) Drive Virtual Media (vMedia) provides you with virtual devices that mimic physical hardware devices as if they were physically connected, such as a virtual CD/DVD drive that can connect through a network to the managed server. A 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.
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 105). 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.
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 34). To run EBSU, complete the following steps: 1. Power on the server. The server boots to EFI. You can use the EFI Boot Manager from the Enhanced interface (grey background) or the Legacy interface (black background). 2. 3. Load the HP Smart Setup media into the server DVD drive.
Figure 2-9 Firmware update NOTE: You might not be able to use EBSU to flash the firmware of some devices. You cannot flash the firmware if the installed version is the same or higher than the version on the Smart Setup media. Also, you cannot use EBSU to flash the Management Processor (MP) firmware. You must download the latest MP firmware from the HP Integrity support site and flash it separately: http://www.hp.com/support/itaniumservers/. 8.
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.
Reinstall from a Headless Console HP Integrity servers that are factory-installed with Windows Server 2003 are shipped with HP Reinstallation media, which enables you to restore the system to its factory settings. Reinstalling the operating system involves loading the image from the Reinstallation media onto the boot disk and, after the initial boot, configuring the system. Load the System Image to the Boot Disk To reinstall Windows Server 2003 from a headless console, complete the following steps: 1.
NOTE: 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). If you use this method, you can skip steps 10 and 11 and go directly to step 12. • Method 2: Select EFI Shell and go to the /CDROM(Entry0) file system by typing fs0: and pressing Enter. 10. 11. 12. 13.
• • 3. 4. 5. 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 49). After you finish this reinstallation procedure, you should also perform the other configuration tasks outlined in the chapter: “Installing and Configuring the Management Tools” (page 49) . Click No if you want to do this later and continue.
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 40) 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.
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.com/support/itaniumservers/ NOTE: For rx7640, rx8640, and Superdome servers, contact HP support or an HP Customer Engineer to obtain the latest firmware. The EBSU on the Smart Setup media enables you to update the firmware. You can use this procedure without using Express Setup. 1.
NOTE: A yellow bang might appear under Non-Plug and Play Drivers in the Windows Device Manager when hidden devices are enabled. The yellow bang appears only if the Show hidden devices option is enabled under the Non-Plug and Play Drivers in the Windows Device Manager. 7. If a device is flagged with a fault indicator (a bang or question mark), insert the HP Smart Setup media in the server's drive and accept the End User Licensing Agreement. 8.
2. Key must both come from the same vendor, either Hewlett-Packard, or Microsoft, or some other Microsoft Authorized Reseller. If you use media that is not supplied by Hewlett-Packard, HP recommends using the HP Smart Setup media and HP Smart Update media after the OS installation, in order to obtain the latest HP value-added software (drivers, tools, utilities, manageability agents) for HP Integrity Servers.
8. Enter the line as it currently appears, then add the /NOVESA option at the end. For example, for the example shown in step 6, you would enter OsLoadOptions = /redirect /novesa then press Enter. The EFI displays the boot loader options again (with the /NOVESA option): Enter VAR to modify: LoadIdentifier = Windows Server 2003, Enterprise OsLoadOptions = /redirect /novesa EfiOsLoaderFilePath = cf5f2ddc-b885-11d7-b831-000000000000 :: \efi\microsoft\winnt50\ia64ldr.
simultaneously. This feature makes use of resources that would otherwise sit idle, enabling your HP Integrity server to perform more work in less time. NOTE: When enabled, hyperthreading is activated for all CPUs in the system. You cannot apply hyperthreading to a single CPU, cell, or nPartition. To enable hyperthreading on partitionable and nonpartitionable HP Integrity servers using the Extensible Firmware Interface (EFI), complete the following steps: 1. 2. 3. 4. Reboot the system to the EFI Shell.
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).
Support Packs are available, you must select the one marked “2003”). Also select “FORCE ALL BUNDLE UPDATES”. Then click OK. Figure 3-2 HPSUM Select Bundle Filter screen 10. The Select Items to be Installed screen appears. It lists all of the individual updates in the Integrity Support Pack, with a check mark next to each, by default. Select the “Reboot System After Installation” box and the “Always” radio button, then click Install to install all items. Installation will take a minimum of 15 minutes.
Figure 3-3 HPSUM Select Items to be Installed screen Install the Integrity Support Pack (ISP) 51
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.
The WBEM (Web-Based Enterprise Management) Providers are installed by default when you install the Integrity Support Pack. WBEM is a Web-based approach for exchanging data across different technologies and platforms. WBEM data is usually encoded using Extensible Markup Language (XML) and then transmitted using Hypertext Transfer Protocol (HTTP). The SNMP (Simple Network Management Protocol) Management Agents are also installed by default when you install the Integrity Support Pack.
Enable Access Rights and Group Memberships To enable remote access of the Insight Providers via WMI for non-administrator user accounts: 1. 2. Add the standard user account to the “Distributed DCOM Users” group. Add the standard user account to namespace security for the following namespaces: • root\HPQ • root\HPQ\default • root\HPQ\TestEvent • root\Interop • root\CIMv2 To add the standard user account to namespace security, complete the following steps for each name space: a. b. c. d. e. f.
2. Open the Windows Control Panel and select HP Management Agents for Integrity Servers. The installed agents are listed in the window. All agents except clustering information are activated at installation. Figure 3-6 Services tab 3. 4. 5. From the Services tab, select an agent from either column to change the active or inactive status. Click Add or Remove to change the status of the selected agent. Click OK when you have made all required status changes.
Figure 3-8 Mail (SMTP) server information 3. 4. In the From address field enter a valid email address or leave it blank. In the Mail server field, enter the name of the SMTP mail server you are using. You must enter a valid server address to continue with the setup process. The wizard checks the SMTP mail server address you entered to see if it can be accessed. If the wizard cannot access the mail server address, it displays a warning message and returns you to the SMTP server address window. 5.
Figure 3-10 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. Click Events to display the Event Selection window. A screen similar to the following appears. Figure 3-11 Event selection window 11. Use the Severity and Source filter fields to view selected events only.
1. Open the Windows Control Panel and double-click HP Management Agents. The installed agents are listed in the window. All agents except clustering information are activated at time of installation. 2. Click the SNMP Settings tab. The following screen appears. Figure 3-12 SNMP Settings tab 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.
Figure 3-13 Process Monitor tab This tab displays all active (running) server processes. The Monitor Option column displays the monitoring status for each process listed. 3. 4. Select the desired process. Change its monitoring status by clicking one of these radio buttons: • None — No SNMP traps are generated for this process. • Start — An SNMP trap is generated when this process starts. • Stop — An SNMP trap is generated when this process stops.
1. From the Start menu, select Start → Settings → Control Panel → Administrative Tools → Component Services. The Component Services window appears. Figure 3-14 Component Services window 2. 3. 4. Click Services (Local). From the list of services, double-click SNMP Service. The SNMP Service Properties (Local Computer) window appears. Click the Traps tab.
5. 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. 6. Under the Traps Destinations list, click Add.
On a fresh install, the administrator password, the operator password, and user passwords are configured during installation. For agents running on other operating systems the default passwords are defined in the following table: Account User Name Password user user public operator operator operator administrator administrator administrator anonymous NOTE: These are the only user accounts available in this release, and they cannot be changed except for the password.
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.
For more information regarding the installation of SQL Server 2005 and tuning of system parameters once installed, refer to: http://docs.hp.com/en/8875/WIE-SQLTuning-1006-00.pdf 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.
9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. If you clicked Advanced on the Components to Install page, the Feature Selection page appears. On the Feature Selection page, select the program features to install using the drop-down boxes. To install components to a custom directory, select the feature and then click Browse. For more information about the functionality of this page, click Help.When your feature selections are complete, click Next.
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 31).
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 rx7640, 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 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.
the nPar Provider running on an nPartition in the target 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 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 the WBEM Providers/SNMP Management Agents The WBEM Providers and SNMP Management Agents are two different groups of services whose purpose is the same -- to report system health and status information back to the System Management Homepage (SMH) application, where it can be monitored by the System Administrator. These services provide all of the management data displayed by SMH. Both groups of services are installed at the same time when you install the Integrity Support Pack.
SNMP Management Agents HP Insight Management Agents comprise the following: • HP Insight Foundation Agents • HP Insight Server Agents • HP Insight Network Interface Card (NIC) Agents • HP Insight Storage Agents • HP Insight Management Services You can deactivate and activate the management agents from the HP Management Agents Control Panel, accessible from Start → Control Panel → HP Management Agents. The following sections describe the components of each agent.
HP Insight Storage Agents HP Insight Storage Agents comprise the following: Fibre Array information Enables a service that provides support for Fibre Channel connected Storage Management. This service is not supported on HP Virtual Machines (HPVM). Drive Array information For a physical drive: Each physical drive is listed as a separate entry in the Mass Storage submenu.
NOTE: This section is not intended to be an SMH tutorial. For a complete instructions on how to use this tool, see the HP System Management Homepage User Guide, found here: http://docs.hp.com Accessing WebAgents The following section describes how to access WebAgents through a browser using SMH: 1. From a system connected to the server through the network, open a compatible browser. 2.
• SMH Pages — The Home page — The Settings page — The Tasks page — The Logs page • Support The Support link provides you with links to HP support areas. • Forums The Forums link provides you with links to HP forums. • Help The Help link launches help files in a separate browser window. The help contents can contain a combination of help files related to the HP Web-enabled System Management Software and utilities. • System Model The System Model displays the model of the system.
• — Other software Can provide links to Integrity, Support, and Forums. — Key Displays a list of status icons and a brief description of each. Software Status Categories — Overall System Status — System Report — Network — Storage — Operating System — System — System Configuration System Status The System Status icon indicates the health of the system and HP Web-enabled System Management software.
Storage The Storage section provides an overview of the selected server's mass storage subsystem. The mass storage controllers being used by the server are listed in the Navigation frame on the left side of the screen. The colored ball next to each controller indicates the status of that controller. NOTE: EMC, EVA, VA, and XP storage systems are not supported by WebAgents.
System The System category displays the following information: • Cooling and temperature Provides information about the device environment, including thermal and fan status, temperature sensor condition, sensor location, current temperature, temperature threshold, type of threshold, and fan information. • Memory Provides information about memory modules, including index, location, description, HP serial number, and HP part number.
Provides firmware versions including index, description, revision, location, and status. • Complex-wide Info Provides server complex information, including total number of cabinets, number of compute cabinets, number of IOX cabinets, complex name, and partition number. • Crash Dump Monitoring Allows you to enable or disable the monitoring of a crash dump condition. • Software Version Info Information includes the name of the software and the installed version number.
E Headless Windows Installations Users of Microsoft Windows Server 2003 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.
