Windows Server 2008 SP2 on HP Integrity Servers Installation Guide HP Part Number: T2369-90031 Published: April 2011
© Copyright 2011 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.........................................................................................48 Configure after the Initial Boot........................................................................................................49 Activate the OS......................................................................................................................................50 Apply OS Updates Using the Smart Update Media..............................................
Partitioning Continuum..................................................................................................................80 Cell Structure of nPartitions............................................................................................................80 Properties of nPartitions..................................................................................................................81 Cell and nPartition Boot Phases............................................................
The SMH Home Page....................................................................................................................101 Overall Status Summary...........................................................................................................101 System Status............................................................................................................................101 System Category......................................................................................
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 2-14 2-15 2-16 2-17 2-18 2-19 2-20 2-21 2-22 2-23 2-24 2-25 2-26 2-27 2-28 2-29 3-1 3-2 3-3 3-4 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.........................................................................................................................15 Graphics Support and 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 Microsoft® Windows Server™ 2008 with Service Pack 2 (SP2) for Itanium™-based Systems. The document publication date and part number indicate the document’s current edition. The publication date changes when a new edition is printed. Minor changes may be made at reprint without changing the publication date.
WARNING A warning calls attention to important information that, if not understood or followed, results in personal injury or nonrecoverable system problems. CAUTION A caution calls attention to important information that, if not understood or followed, might result in data loss, data corruption, or damage to hardware or software. IMPORTANT This alert provides essential information to explain a concept or to complete a task.
should subscribe to the appropriate product support service. See your HP sales representative for details. You can find the latest version of this document on line at: http://www.docs.hp.com Manufacturing Part Number Supported Operating Systems Supported Smart Setup Version Supported Products (Servers) Publication Date T2369-90031 Microsoft Windows Server 2008 with Service Pack 2 (SP2) for Itanium-based Systems Version 7.
1 Preparing for Installation Installing Microsoft Windows Server 2008 SP2 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.
size. This can create I/O conflicts that cause the system to lock up with a blue screen, a stopcode of 0X000000D1, and a reference to the file elxstor.sys. The solution to this problem is to make sure that all HBAs in the system are manufactured by the same vendor (and therefore have the same maximum I/O packet size). Current HBA vendors include Emulex and Qlogic. The following lists summarize HBA sourcing, so you can ensure brand similarity in your system.
Table 1-1 Installation Matrix Server Model Installation Method Installation Media Non Cell-Based Servers Headless Console Windows Server 2008 SP2 OS disc (provided by Microsoft) + HP Smart Setup disc + HP Smart Update disc rx2660 HP Reinstallation disc + HP Smart Setup disc + HP Smart Update disc rx3600 rx6600 GUI Console BL860c BL870c Windows Server 2008 SP2 OS disc (provided by Microsoft) + HP Smart Setup disc + HP Smart Update disc HP Reinstallation disc + HP Smart Setup disc + HP Smart Update
Task 5: Set Up an Installation Method 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 by using one of the following: • • • A null modem cable A cat5 LAN cable 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.
7. 8. Select Save Settings to NVRAM; and then, Exit. 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 38). To install the HP Graphics and USB Combo Card using the Enhanced interface (gray background), follow these 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.
6. Click Launch. (If Launch is grayed out, the license might be invalid or expired.) A new window displays, providing access to the IRC. Set Up a 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.
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 2008 SP2. 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 descriptions of the concepts, tasks, best practices, and troubleshooting tips for setting up a WDS server, see the Microsoft Windows Server 2008 Technical Reference website: http://www.microsoft.com/windowsserver2008/en/us/product-documentation.aspx Specifically, see the following web address: http://technet2.microsoft.com/windowsserver2008/en/library/ fbd2d37b-4127-43fd-a079-f78bbd44b7601033.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, click 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, click Remote Install and select Advanced Settings. In the Advanced Settings dialog box, click New Clients. Select the client computer naming format you want to use, or click Customize to create a client computer naming format.
• 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.
The EFI Shell environment creates default mappings for device handles that support a recognized file system. After you change the system configuration or add a new device, you must regenerate these mappings. To enable the EFI Shell to detect and access the DVD/CD drive, follow these steps: 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 purchased your server with a Windows OS option, this flag is set to windows in the factory. If you purchased the server with a different OS or no OS, you must set this flag to windows. CAUTION: If you boot the server to Windows Server 2008 SP2 without setting the ACPI flag to windows, the OS displays a blue screen error. To set the ACPI flag, follow these steps: 1. From the EFI Shell, enter the acpiconfig command. EFI displays the current ACPI settings.
3. 4. At the Select desired LAN: prompt, enter the number of the NIC connected to the PXE server. Exit the EFI Shell.
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 2008 SP2. 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.
3. 4. 5. From the EFI Boot Manager Boot Menu, select Internal Bootable DVD, and press Enter. EBSU starts and displays the Welcome screen. Click OK, and press Enter. From the Main Menu, select Express Setup and press Enter. Figure 2-1 EBSU Main Menu NOTE: In cellular systems (rx7640, rx8640, and Superdome), the EBSU Main Menu includes a Pre-OS Configuration Checking option. In non-cellular systems, this option is not available. 6.
Figure 2-2 EBSU OS Media Select Screen NOTE: The steps that follow apply to users of Microsoft Windows OS media only. If you are using HP Reinstall media, follow the next prompt to load Windows, then go to Step 12 in “Load the System Image to the Boot Disk” (page 45) and continue the rest of your installation from there. 7. EBSU displays the firmware update screen, listing each device, its installed firmware version, and the firmware version on the Smart Setup media.
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. 8. EBSU displays the partition disk screen. Select ESP + HPSP + MSR or ESP Only. HP recommends the default (ESP + HPSP + MSR) as a way to simplify the maintenance of your server. Figure 2-4 EBSU Partition Disk Screen 9. 32 EBSU displays an install options screen.
Figure 2-5 EBSU Install Options Screen 10. EBSU prompts you to execute an unattended Windows Server 2008 installation. Press Yes to continue. Figure 2-6 EBSU Prompt Screen 11. When prompted by EBSU, enter the Product Key, Administrator Password, and OS language. Remember that passwords are case-sensitive.
NOTE: If you are downgrading to an earlier OS version, you may have to obtain your Product Key before completing this step. Figure 2-7 EBSU Product Key Screen 12. EBSU displays a warning that all partitions on the disk will be overwritten. Select Continue and press Enter. 13. EBSU displays a warning that a temporary MSDATA partition will be created. Press Enter. 14. EBSU displays an informational pop-up that the installation will begin. Press Enter. 15.
Figure 2-8 EBSU Instructions Screen 17. When prompted, insert the Microsoft Windows Server 2008 SP2 operating system CD and press Enter. Figure 2-9 EBSU Insert OS Screen 18. Press any key when prompted to boot from the CD or DVD (be ready to do this quickly, or the system could time out). 19. Windows begins loading files from the disk. When the progress bar reaches 100%, the screen displays the message: The CMD command is available. 20. Type cmd to launch a CMD prompt session. 21.
Figure 2-10 EBSU Screen #1 23. Type install.cmd to begin. 24. Press the Esc + Tab keys to open a different command channel. Verify there are no error messages in the SACSetupErr channel. Figure 2-11 EBSU Screen #2 25. The system will restart during the installation. Wait until the EVENT: prompt displays, and then type cmd. 26. Press Esc + Tab, and when prompted, enter the Administrator username and password. Remember that passwords are case-sensitive. Figure 2-12 EBSU Screen #3 27.
Figure 2-13 EBSU Screen #4 29. The system finishes booting to the Desktop for the first time and launches the Initial Configuration Tasks screen. Figure 2-14 Initial Configuration Tasks Screen 30.
I/O, storage, intended use, and so on. See your System Administrator and the operating system online help. 31. Installation of the OS is complete. After installing the OS, perform these tasks next: 1. “Install the Integrity Support Pack (ISP)” (page 59) 2. “Activate the OS” (page 50) 3. “Apply OS Updates Using the Smart Update Media” (page 52) 4. “Enable Windows Components” (page 53) 5. “Verify System Device Drivers and Register for Updates” (page 54) 6.
Figure 2-15 EBSU Main Menu NOTE: In cellular systems (rx7640, rx8640, and Superdome), the EBSU Main Menu includes a Pre-OS Configuration Checking option. In non-cellular systems, this option is not available. 6. In the next screen, choose the type of OS media you are using and select Next to continue.
NOTE: The steps that follow apply to users of Microsoft Windows OS media only. If you are using HP Reinstall media, follow the next prompt to load Windows, then go to Step 7 in “Load the System Image to the Boot Disk” (page 48) and continue the rest of your installation from there. 7. 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.
Figure 2-18 EBSU Partition Disk Screen 9. EBSU displays an install options screen. Accept the default options to install the Drive Explorer utility (for browsing a drive in EFI) and offline diagnostic tools (from the HP Integrity Offline Diagnostics CD) in the HPSP partition. Also, specify which version of the Windows OS Installer to launch (in this case, Windows Server 2008 SP2). Then select Next and press Enter.
10. EBSU prompts you to execute an unattended Windows Server 2008 installation. Press No to continue. Figure 2-20 EBSU Prompt Screen 11. EBSU displays a warning that all partitions on the disk will be overwritten. Select Continue and press Enter. 12. EBSU displays an informational pop-up that the installation begins. Press Enter. 13. The installation begins and progresses through partition creation and firmware updates. Insert the HP Integrity Offline Diagnostics CD when prompted, then press Enter.
Figure 2-22 Install Windows Screen #1 17. 18. 19. 20. 21. At the next screen, click Install Now. At the next screen, enter your product key again and click Next. At the License Terms screen, check the I accept the license terms box and click Next. At the next screen, click Custom (advanced). At the next screen, you are asked on which system partition to install the operating system.
26. The system finishes booting to the desktop for the first time and launches the Initial Configuration Tasks screen. Figure 2-24 Initial Configuration Tasks Screen 27.
Then, see the sections describing configuration of the management tools, and perform these tasks: 1. “Configure System Management Homepage” (page 64) 2. “Configure and Verify the WBEM Providers” (page 62) 3. “Verify Installation of the nPartition Management Tools” (page 65) Install from PXE When a PXE-enabled client connected to the network boots up, the computer initiates a network service request. A DHCP discover packet is sent to the network requesting the IP address of an available WDS server.
5. Deletion of existing Windows Boot Manager entries is recommended. To delete boot entries, choose one of the following methods: • Use the EFI Maintenance menu: — If you are using the Enhanced EFI Boot Manager Menu (gray background), select EFI Boot Manager Menu → Boot Configuration → Remove Boot Entry. — If you are using the Legacy EFI Boot Manager Menu (black background), select EFI Boot Manager Menu → Boot Option Maintenance Menu → Delete Boot Option(s).
23. Go to the next section for instructions on how to specify the server settings and complete the reinstallation. Configure after the Initial Boot To configure Windows Server 2008 SP2 after the initial boot from a headless console, follow these steps: 1. Open a terminal server client and log in to Windows Server 2008 SP2 by typing Administrator for the user name and Abcdef12 (case-sensitive) for the password.
Reinstall from a GUI Console HP Integrity servers that are factory-installed with Windows Server 2008 SP2 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 2008 SP2 from the local GUI console, follow these steps: 1.
14. Select the partition size (64 GB is the default, and in most cases, the minimum recommended size) and press Enter. The maximum partition size is limited to the size of the drive. 15. Select Y to continue. The installation process copies files to the hard disk. Do not power off the server during the installation. 16. When all files from the DVD drive are copied to the server boot disk, read the displayed message.
7. The system reminds you to install the latest system updates from Microsoft using your HP Smart Update media, and prompts you to reboot. Click Yes to reboot. 8. Activate your operating system. For instructions, see: “Activate the OS” (page 50). 9. Install any available operating system updates using your HP Smart Update media. For instructions, see: “Apply OS Updates Using the Smart Update Media” (page 52) 10. Your system is now ready to go online.
NOTE: If you click Change product key instead of Activate Windows now you are prompted to enter the key and then the Activation wizard runs. This method can be used for entering a test product key when the computer is disconnected from the internet. 4. 5. The Windows Activation screen displays. Click Type a different product key. In the next screen, enter your product key.
8. Confirm the activation by going back to the System window and looking at the activation section at the bottom. It should indicate: Windows is activated. Figure 2-29 System Window #2 Apply OS Updates Using the Smart Update Media Install the latest OS and security updates from the HP Smart Update media. You can find the Smart Update media in the Insight Foundation suite for Integrity with Windows kit with the Smart Setup media.
8. 9. 10. 11. 12. 13. 14. To install all Security updates, click Install in the Security Updates section. The HP Package Setup screen appears. Click Install. The HP Setup screen appears. Click Install to continue with the installation or click Close to exit setup. When you click Install, a command window appears, listing each update as it installs. Sometimes these are large updates that can take several minutes each to install. When prompted, click Reboot to complete the installation.
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, follow these steps: 1. 2. 3. 4. From the Windows Desktop, select Start → Server Manager. In the Server Summary section, click Configure Remote Desktop. On the Remote tab, select the desired RDC connection option and assign user access rights as needed. Click Apply and then OK to apply the changes.
4. All of the system devices are shown, grouped by Type. Expand each group, verifying that no devices display 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 cannot find it or recognize it.
• • the purchase of a Windows Server 2008 R2 license the Windows Server 2008 or Windows Server 2003 installation media To perform such a downgrade, use your previously purchased installation media for Windows Server 2008 or Windows Server 2003. The installation media can come from either Hewlett-Packard, Microsoft, or some other Microsoft Authorized Reseller.
Hyperthreading enables each physical processor to present itself to the OS and applications as two virtual processors. This means each processor can work on two or more sets of tasks 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.
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).
8. 9. The Discovery Progress screen displays as HPSUM checks the system to see which components are currently installed. When the discovery process finishes, the Select Bundle Filter screen displays and lists the Integrity Support Packs that were found on the Smart Setup media. Select HP Integrity Support Pack for Windows Server 2008 on Itanium-based Systems (if multiple Integrity Support Packs are available, you must select the one marked “2008”). 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) 61
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.
NOTE: Concurrent installation of the WBEM Providers (from Smart Setup version 6.5 or later) and the HP Insight Management Agents (from earlier versions of Smart Setup) is not supported. If the HP Insight Management Agents were previously installed on the system, you must manually uninstall them before installing the version 6.5 WBEM Providers. If the system has Management Agents version 6.2, you can upgrade from WBEM Providers 6.2 to 6.5 without manually uninstalling Agents 6.2 first.
Enable Auto Page Refresh and Set the Interval You can configure SMH with an Auto Refresh interval to get updates from the WBEM Providers. To enable WBEM Auto Refresh and to set the Refresh interval, follow these steps: 1. 2. 3. Click Settings → Auto Refresh → Configure Page Refresh Settings. Select a refresh interval between 5 seconds and 30 minutes. Use the radio button to enable Auto Refresh. After WBEM Auto Refresh is enabled, the browser refreshes the pages at the specified interval.
1. 2. 3. 4. Click Help on the System Management Homepage. Click System Management Homepage Help. On the left navigation bar, select Settings Tab → Security. Change these settings as necessary for your system and production environment. The SMH Settings tab allows you to set some parameters. This capability requires security that includes the three predefined users. For agents running on Microsoft operating systems, there are no default passwords.
(page 79). For a description of nPartitioning and associated tools and concepts, see the nPartition Administrator's Guide found here: http://docs.hp.com/en/5991-1247B_ed2/5991-1247B_ed2.pdf 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.
3. To test remote WBEM connections, do the following: a. Copy the remote nPartition WBEM certificate into the local WBEM trusted certificate store. b. Enter the host name and IP address of the remote nPartition that you want to connect to, along with an account and password with administrative privileges on the remote nPartition in the top half of the Partition Manager login screen. c. Click OK. 4. In order to test remote IPMI connections, do the following: a.
A Preparing the Server for Microsoft SQL Server This appendix describes the server configuration tasks needed to install Microsoft SQL Server.
4. Verify storage/Fibre Channel HBAs: a. Maximum queue depth: Ensure that the HP AH402A or AH403A (Emulex) driver options set in LPutil are equal to or greater than the number of physical drives (default = 20). b. Maximum queue depth: For HP AH400A or AH401A (Qlogic) NVRAM, ensure that the Sanblade execution throttle setting is equal to or greater than the number of physical drives (default = 16). c. Enable write cache: It is important to have a cached log for the database.
7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. items grouped by result, click Filter and then select a category from the drop-down list. To view a report of SCC results, click Report and then select an option from the drop-down list. To proceed with setup after the SCC scan completes, click Continue. On the Registration Information page, enter the required information, then click Next. On the Components to Install page, select the components to install.
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).
• — Installing offline diagnostic tools — Installing Windows Maintain Firmware — Maintains the firmware for selected devices with flashable firmware. You can flash devices individually or all at once. NOTE: You cannot flash the firmware if the installed version is the same as, or higher, than the version on the Smart Setup media. • • • • • Create Partitions — creates the following partitions: — EFI System Partition. This partition is required to boot the OS.
1. 2. 3. 4. 5. Remove all media from the server's DVD drive. Boot the server into the EFI Boot Manager interface. In the EFI Boot Manager screen, select Boot Option Maintenance Menu. In the Boot Maintenance Manager screen, select Add a Boot Option. In the Add Boot Option screen, select the entry that defines your boot volume (the volume where the boot file and OS are installed). In most cases, where the boot volume has not been named, that entry appears as: NO VOLUME LABEL. 6.
C nPartitioning This appendix introduces node partitions (nPartitions) on cell-based HP Integrity servers running Microsoft® Windows® Server 2008 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.
3. Verify installation of the nPartition tools. See: “Verify Installation of the nPartition Management Tools” (page 65). 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.
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.
To execute nPartition commands using a telnet connection to the management station, do the following: 1. Invoke telnet on the remote terminal, providing the host name or IP address of the management station. 2. Log in to the telnet server with a valid user name and password. 3. From the command prompt, execute nPartition commands as usual. NOTE: The OS might limit the number of telnet connections permitted into the management station.
IO ID List connections from cells to I/O chassis on HP Superdome servers. List product and serial numbers. Using the EFI Shell EFI Shell methods for listing hardware and nPartition status include the following commands. Hardware and nPartition information displayed by the EFI Shell is limited to the local nPartition. info sys List the local nPartition number and active cell details. List the I/O configuration. info io info mem List memory details. info cpu List processor details.
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. You can also modify some nPartition details locally from an nPartition console by using EFI Shell commands.
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 The WBEM Providers are a group of services that report system health and status information back to the System Management Homepage (SMH) application, where it can be monitored by the System Administrator. They 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.
• System thresholds • Diagnostics • Software version control for an individual server Before you can start using SMH you must first complete the tasks described earlier in this document, found here: “Configure and Verify the WBEM Providers” (page 62). 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.
Header Frame The Header Frame is constantly visible regardless of the page you are viewing. Data frame The Data Frame displays the status for HP Management software and utilities on the system. The following informational areas and links appear in the Header Frame: • Master header: The links show the path you are viewing, the user, and a Sign Out link. • Menu. Each item is a direct link to a page or section including: — Home — Settings — Tasks — Tools — Logs — Webapps — Support — Help • Main title area.
— — • • • • • • • • If the user is operating system-based, a Sign Out link displays. If anonymous access is enabled, the Current User displays hpsmh_anonymous and the Sign In link displays. — If Local Access is enabled, the Current User displays hpsmh_local_anonymous or hpsmh_local_administrator, depending on what level of access has been enabled, and local access appears below user type. — If user type is local_access_administrator, no Sign In or Sign Out link displays.
Unknown Informational • Management Processor: Displays a link to the Remote Insight Lights-Out Edition (RILOE) board or the Integrated Lights-Out (iLO) board. This information is provided by the WBEM Providers. If no WBEM Providers are installed, none displays. The SMH Home Page The Home page provides system, subsystem, and status views of the server. Information on the Home page is provided by the integrated Web-Based Enterprise Management (WBEM) property pages and management utilities.
Operating System Category The Operating System category contains links that show basic operating system configuration, usage, state, and other information. The Operating System category displays the following information: • Logical Disks: Information includes volume, free space, queue length, and disk busy time. Network Category The Network category contains links that display basic network system configuration, usage, state, and other information.
• • • • 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. System Resources: Information includes resource type, value, and slot.
E Headless Windows Installations Users of Microsoft Windows Server 2008 SP2 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.
