HP Integrity BL860c Server Blade User Service Guide HP Part Number: AD217-9015C Published: November 2011 Edition: 11
© Copyright 2007, 2011 Hewlett-Packard Development Company, L.P Legal Notices The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Printed in U.S.A.
Contents About This Document...................................................................................10 Intended Audience..................................................................................................................10 New and Changed Information in This Edition............................................................................10 Publishing History...................................................................................................................
Installing a Processor.....................................................................................................30 Installing DIMMs...........................................................................................................32 Installing Mezzanine Cards............................................................................................33 Installing a Mezzanine Card in Port 1.........................................................................
Exit the SAS Configuration Utility Screen..........................................................................61 CFGGEN Utility.................................................................................................................61 Starting CFGGEN.........................................................................................................62 CFGGEN Operation.....................................................................................................
Front Panel LEDs................................................................................................................91 Locator LED..................................................................................................................92 Server Health LED.........................................................................................................92 Internal Health LED........................................................................................................
Replacing a SAS Disk Drive...............................................................................................109 Removing and Replacing Disk Drive Blanks.........................................................................109 Removing a Disk Drive Blank........................................................................................109 Replacing a Disk Drive Blank........................................................................................
C Utilities.................................................................................................150 NVRAM Backup Utility..........................................................................................................150 Downloading and Installing the NVRAM Backup Utility.........................................................150 Using the NVRAM Backup Utility.......................................................................................150 Syntax...............................
sysmode.........................................................................................................................168 Syntax.......................................................................................................................168 Parameters.................................................................................................................168 Operation..................................................................................................................
About This Document This document provides information and instructions on servicing the HP Integrity BL860c server blade. The document publishing date and part number indicate the document’s current edition. The publishing date changes when a new edition is updated. The document part number changes when extensive changes are made. Document updates may be issued between editions to correct errors or document product changes.
Chapter 2 General Site Preparation Guidelines Use this chapter to learn about the necessary steps needed to properly install your server blade in a data center. This includes environmental and facility characteristics. Chapter 3 Installing the Server Blade Use this chapter to learn about installing the server blade into the enclosure. Chapter 4 Booting and Shutting Down the Operating System Use this chapter to learn about booting and shutting down the operating system on the server blade.
CAUTION A caution calls attention to important information that if not understood or followed will 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 NOTE A note contains additional information to emphasize or supplement important points of the main text. HP-UX Release Name and Release Identifier Each HP-UX 11i release has an associated release name and release identifier.
• Applicable error message • Add-on boards or hardware • Third-party hardware or software • Operating system type and revision level HP Contact Information For the name of the nearest HP authorized reseller: • In the United States, see the HP US service locator webpage (http://welcome.hp.com/country/ us/en/wwcontact.html.) • In other locations, see the Contact HP worldwide (in English) webpage: http://welcome.hp.com/country/us/en/wwcontact.html.
1 Overview The HP Integrity BL860c server blade is a dense, low-cost, c-Class enclosure based Intel Itanium Dual-Core processor server blade. The BL860c server blade supports the HP-UX, HP OpenVMS, Linux, and Windows operating systems. The BL860c server blade is designed for commercial server blade customers deploying c-Class blade enclosures. The BL860c server blade is consistent with other full-slot, single-width c-Class blades.
Figure 1 BL860c Server Blade Components 1 2 3 4 5 SAS backplane DIMMs Mezzanine card 1 Mezzanine card 2 Mezzanine card 3 6 7 8 9 10 Processors System board Trusted Platform module Front display panel SAS disk drives SAS Disk Drives There are two SAS disk drive slots on the server blade. The SAS disk drives have identical LEDs that show the drive status. Figure 2 shows the slot numbers of the SAS hard disk drives.
Figure 2 SAS Disk Drive Slots For the location of the SAS disk LEDs, see Figure 5. SAS Backplane The SAS disk backplane supports two small form factor (SFF) hard disk drives. The backplane supports hot-plugging a single SAS drive at a time. The activity LEDs and drive present LEDs shall be controlled by a preprogrammed system-on-chip (PSOC). The system board hosts the SAS controller, and supplies 12 V, 5 V, and 3.3 V standby power to the backplane.
To enable PCIe MPS optimization use the ioconfig mps_optimize command. See “ioconfig” (page 165). For non-PCIe systems, ioconfig and info io will not display the MPS optimization policy setting. The Set PCIe MPS Optimization boot manager menu also will not be displayed. Running the ioconfig mps_optimize [on|off] command from a non-PCIe system, displays the following output: ------------Shell> ioconfig mps_optimize ioconfig: PCIe MPS optimization is not supported.
Table 4 Server Blade Memory Array Capacities (continued) Min / Max Memory Size Single DIMM Sizes 4 GB / 24 GB 2 GB 8 GB / 48 GB 4 GB NOTE: Installing DIMMs as a pair (two identical DIMMs) enables lock-step mode and chip sparing. Install DIMMs from highest capacity to lowest capacity (for example, install the 4-GB DIMMs first, then the 2-GB DIMMs, then the 1-GB DIMMs, and so forth). For more information, see “Removing and Replacing DIMMs” (page 114).
USB Bot Mass Storage Driver: 00000020 Generic USB Mass Storage Driver: 00000020 CLPrelay App: 00000100 * Indicates active system firmware image. In this case =>3.02 indicates that this server does not need system firmware updated to use the memory modules described in this document. The firmware upgrade instructions are included in the Release Notes on the firmware package download page for your server product. To locate the Release Notes and download the firmware: 1. Go to http://www.hp.com/bizsupport. 2.
Front Panel View The server blade has seven server LEDs, one Power button, two Reset buttons, SAS disk drive LEDs and one front panel port that accepts the serial, USB, video (SUV) cable for configuration and troubleshooting. Figure 3 shows the LEDs, ports, and controls on the front panel of the server blade.
Figure 4 shows the front panel LEDs. Figure 4 Front Panel LEDs on the Server Blade 1 2 3 UID LED Server health LED Internal health LED 4 5 NIC 1 LED 6 NIC 2 LED 7 NIC 3 LED NIC 4 LED Table 5 details the functions of the front panel LEDs. Table 5 BL860c Server Blade Front Panel Item LED Description 1 Unit identification (UID) 2 Server health 3 Internal health 4 NIC 1 5 NIC 2 6 NIC 3 7 NIC 4 SAS Disk Drive LEDs There are two SAS disk drives on the server blade.
Figure 5 SAS Disk Drive LEDs 1 Activity LED 2 Status LED Controls and Ports The following section identifies the locations and functions of the front panel controls and ports. The Power button, and server blade extraction lever, and the SUV cable port are located on the front of the server. For more information about the Power button and server blade power states, see “Server Power States” (page 39).
SUV Cable and Ports The server blade has an SUV port used by the SUV cable. This port is located on the front of the server blade. Figure 6 (page 22) shows the location of the SUV port. The SUV cable connects the server to external devices, such as: a terminal emulator, an external DVD drive, or a monitor. Figure 7 shows the ports on the SUV cable. CAUTION: The SUV cable is not designed to be used as a permanent connection. Use caution when walking near the server blade when the SUV cable is installed.
Figure 8 BL860c Server Blade Rear Panel Ports 1 24 GBX signal connector Overview 2 Power connector
2 General Site Preparation Guidelines The HP Integrity BL860c server blade does not have cooling or power systems as part of the server blade. Cooling and power is provided by the c-Class enclosure. Therefore, the server blade power, cooling, and site specifications are included in the c-Class enclosure documentation. For more information on the c-Class enclosures, see: http://h71028.www7.hp.com/enterprise/ cache/316735-0-0-0-121.html.
3 Installing the Server Blade Into the Enclosure This chapter covers the procedures for installing the server blade into a c-Class enclosure. Safety Information When removing and replacing server components, use care to prevent injury and equipment damage . Many assemblies are sensitive to damage by electrostatic discharge.
Verify Site Preparation Verifying site preparation is an essential factor of a successful server installation, and includes the following tasks: • Gather LAN information. Determine the two IP addresses for the Integrated Lights Out 2 Management Processor (iLO 2 MP) LAN and the server blade LAN. • Establish a method to connect to the server console. For more information on console connection methods, see Section : “Accessing the Integrated Lights Out 2 Management Processor” (page 40).
Service Tools Required Service of this product can require the following tools: • An IPF Processor Install Tool Kit, consisting of: • Disposable ESD Kit • Processor installation tool (2.5 mm hex and Torx 15 screwdriver) NOTE: If you purchased an additional processor, the IPF Processor Install Toolkit is included with the processor. The server blade has a Torx T–15 screwdriver mounted on the inside of the access panel.
2. Close the lever to lock the drive into place (2). Figure 10 Installing a Hot-Plug SAS Disk Drive Installing Internal Components Use these procedures to install internal components that were not installed into your server blade. Before you can install the internal components, you must remove the access panel. Removing the Access Panel To remove the access panel: 1.
Figure 11 Removing the Server Blade Access Panel After the access panel is off, you can do the following: • Add an additional processor. See “Installing a Processor” (page 30). • Add additional memory DIMMs. See “Installing DIMMs” (page 32). • Add additional mezzanine cards. See “Installing Mezzanine Cards” (page 33) Installing a Processor Use this procedure to install an additional processor into the server blade. To install a processor: 1.
Figure 12 Unlocked ZIF Socket CAUTION: Do not tighten the ZIF socket lock more than 180 degrees in either direction. This severely damages the socket and processor, and renders the processor slot unusable. 3. Install the processor into processor slot 1 on the system board by lining up the alignment pins on the processor with the holes in the processor slot. NOTE: Processor 0 is already installed in the server blade. See Figure 13 for slot locations on the server blade system board.
7. Tighten the captive screws (5 – 6) on the processor with the Torx T-15 screwdriver until snug Figure 14 Installing a Processor on the Server Blade System Board 8. Connect the power cable to the processor power connector using the clips shown circled in Figure 14 (page 32). If you are only adding a processor to your server blade, and not adding memory DIMMs or mezzanine cards, go to “Replacing the Access Panel” (page 37). If you are adding DIMMs, go to “Installing DIMMs” (page 32).
1. Locate the DIMM slots on the server blade system board. See Figure 15. NOTE: The server blade ships with at least two DIMMs installed in slots 0A and 0B. Figure 15 DIMM Slot Locations 2. Ensure the DIMM slot latches are open. CAUTION: Use only HP low profile (1.2 in.) DIMMs. DIMMs from other sources might adversely affect data integrity. DIMMs do not seat fully if turned the wrong way. DIMMs in a pair must be identical. 3. Insert a DIMM in a slot and push down firmly until the latches click shut.
Figure 16 Mezzanine Port Locations on the System Board 1 2 3 The 1. 2. 3. Mezzanine port 1: PCIe x4 port Mezzanine port 2: PCIe x8 port Mezzanine port 3: PCIe x8 port install order for the mezzanine cards is: PCIe x4 card – Install into mezzanine port 1 PCIe x8 card – Install into mezzanine port 2 PCIe x8 card – Install into mezzanine port 3 If you are only loading PCIe x8 cards, install them into port 2, then port 3.
Figure 17 Mezzanine Port Heights Installing a Mezzanine Card in Port 1 To insert a mezzanine card into the PCIe x4 port 1 on the system board: 1. Line up the plastic pins on the mezzanine card connector with the PCIe x4 port on the system board. 2. Push down on the card directly above the port to seat the card into the port (1).
3. Tighten the thumbscrews on the mezzanine card until snug to secure the card to the system board (2). See Figure 18. Figure 18 Mezzanine Card 1 Installed on the Server Blade System Board Installing a Mezzanine Card to Ports 2 and 3 To insert a mezzanine card into the PCIe x8 ports 2 and 3 on the system board: 1. Line up the plastic pins on the mezzanine card connector on the PCIe x8 port 2 on the system board. 2. Push down on the card directly above the port to seat the card into port 2 3.
6. Tighten the thumbscrews on the mezzanine card until snug to secure it to the system board. Figure 19 shows all three mezzanine cards installed on the server blade system board. Figure 19 Mezzanine Cards 2 and 3 Installed on the Server Blade System Board 1 2 3 Mezzanine card 1 (PCI–e x4) Mezzanine card 2 (PCI–e x8) Mezzanine card 3 (PCI–e x8) Replacing the Access Panel To replace the access panel: 1. Make sure the access panel latch is in the open position (pointing up). See Figure 20 (page 38). 2. 3.
Figure 20 Replacing the Access Panel 4. Lock the access panel cam (if necessary) by turning the cam clockwise with the Torx T–15 or flathead screwdriver. Installing and Powering On the Server Blade This section describes how to install the server blade into a standard c-Class enclosure and power it on. When you install the server blade into the enclosure, the server blade powers up to standby mode.
5. Close the extraction lever (2). The server blade should come up to standby power. The server blade is at standby power if the server health LED is amber. IMPORTANT: If the server health LED turns green, and the fan noise gets louder, then the server blade has powered on. Skip the rest of this procedure, and proceed to “Accessing the Integrated Lights Out 2 Management Processor” (page 40).
power on to standby power when installed in a server blade enclosure. Verify the power state by looking at the LEDs on the front panel, and using Table 7. For more front panel LED information, see “Front Panel LEDs” (page 20).
2. Use the down arrow on the front display panel to highlight Blade or Port Info. Figure 22 shows the Blade or Port Info selection highlighted on Main Menu of the front display panel. Figure 22 Main Menu of the Front Display Panel 3. Press OK. The View Blade and Port Info screen displays on the front display panel. See Figure 23. Figure 23 The View Blade and Port Info Screen 4. 5. Using the left/right arrows, highlight Blade Info on the bottom of the front display panel.
Figure 24 The View Blade Info Screen 6. 7. 8. 9. Write down the iLO 2 MP IP address that displays on the View Blade Info screen. Access the iLO 2 MP through telnet, SSH, or through the web using the assigned DHCP IP address. This ends the “Accessing the iLO 2 MP with DHCP Enabled” procedure. Continue to “Configuring the iLO 2 MP” (page 44). Accessing the iLO 2 MP with No Network Connection You need to have a terminal emulator (for example, a laptop using hyperterm) to connect to the server blade.
Figure 25 Connecting the SUV Cable to the Server Blade Connecting a Terminal to the Server Blade To establish a connection from your server to your terminal (or emulator device): CAUTION: Disconnect the SUV cable from the port when not in use. The port and connector are not intended to provide a permanent connection. 1. Connect the standard DB9f to DB9f modem eliminator cable to the RS-232 port on the SUV cable. See Figure 26. Figure 26 Serial Connector on the SUV Cable 2.
4. 5. 6. 7. To set the parameters, click OK. If running an emulator, launch it now. This ends the “Accessing the iLO 2 MP with No Network Connection” procedure. Continue with “Configuring the iLO 2 MP” (page 44). Configuring the iLO 2 MP Use this procedure to configure iLO 2 MP settings after establishing a connection to iLO 2 MP using one of the two methods discussed in Section : “Accessing the Integrated Lights Out 2 Management Processor”.
iLO 2 MP Security Requirements Depending on how you set up your server blade, there are security concerns regarding whether you allow remote access to the server blade. It is highly recommended that you allow remote access to the server blade. Remote access allows for remote system event log analysis, troubleshooting, and general system administration. During the login process, a warning message displays. If you log in through a terminal (serial or telnet) an ASCII message scrolls by.
2. Enter on to set the power restore configuration to power on to full power as shown below: 3. 4. Enter y to confirm changing the power restore configuration setting. Power on the server through the iLO 2 MP by accessing the Power Control menu. Access the Power Control menu by entering pc from the MP Main Menu. 5. Enter on to power on the server blade as shown below: 6. Enter y to confirm changing the power control setting.
Remote Access Allowed NOTE: If your server blade has a DHCP server connected to the OA/iLO port on the rear of the enclosure, this procedure is not required. Proceed to “Accessing EFI or the OS from iLO 2 MP” (page 48). To allow remote access, you should have changed your iLO 2 MP password to secure your server blade. If you have a DHCP server connected to the OA/iLO port on the rear of the enclosure, your access is set.
Remote Access Not Allowed If you do not want to allow remote access to the server blade, use the following steps to disable DHCP and other remote connections on your server blade. CAUTION: Only use this procedure if you are disabling remote access to the server blade. Do not disable remote access if you have a DHCP server connected to the OA/iLO port on the rear of the enclosure. This procedure disables all remote access to the server blade and you lose your remote access the server blade. 1. 2.
• From the MP Main Menu, enter co to access the Console Menu. Depending on how the server blade was configured from the factory, and if the OS is installed at the time of purchase, you should be in one of two places: • EFI Boot Manager menu • OS login prompt If the server blade has a factory-installed OS, you can interrupt the boot process to configure your specific EFI parameters. If you are at the EFI Shell prompt, go to “EFI Boot Manager” (page 49).
Server Blade to Enclosure Interface This section describes the interface between the server blade and the server blade enclosure. This sections also shows the RJ-45 LAN interconnect ports on the rear of the server blade enclosure, and how they correspond with the Network Interface Controller (NIC) LEDs on the front of the server blade. Port Locations on the Rear of the Server Blade Enclosure LAN port mapping depends on the type of I/O card that is installed into the server blade.
Table 8 Server Blade to Enclosure Interconnect Mapping (continued) Server Blade to c-Class Enclosure Mapping Mezzanine Slot 2 Slots 5 and 6 Mezzanine Slot 3 Slots 7 and 8 NOTE: Dual-width interconnect modules cannot be used in slots 1 or 2. Only single- or dual-port mezzanine cards are supported. LAN / NIC Configuration Table 9 shows how the EFI and HP-UX LAN ports and front panel NIC numbers match up on the server blade enclosure.
3. To determine the current version of the firmware: a. At the EFI Shell, enter mptutil from the directory that contains mptutil.efi. The following example indicates that the EFI Serial Attached SCSI card utility version is 1.01.12.00: fs0:EFI\HP\TOOLS\NETWORK> mptutil MPTUTIL-1.01.12.00 Vendor Device Choice ID ID Bus Device ------ ------ ------ --- -----0 1000h 0054h 14h 01h LSI Logic SAS1068 Host Adapter 1 - Refresh b. 4. 5. Press Enter. To update the firmware, use the mptutil command.
Common Questions About Flashing Firmware Question After I update firmware on my SAS HBA, why doesn't the version string change in the menu? Answer The firmware you flashed on the HBA does not run until a diagnostic reset occurs. If you exit the utility and reenter it, the version string is updated. Question This image does not contain a valid nvdata image when I try to flash the firmware. Why? Answer You are expected to concatenate a proper nvdata image to the firmware.
There are general key inputs throughout the configuration utility that apply on all screens: F1 Help Context sensitive help for the cursor-resident field. Arrow Keys Select up, down, left, or right to position the cursor. Home/End Select up, down, left, or right to position the cursor. +/- Use to change items with values in [ ] brackets. Numeric keypad + and numeric keypad - (minus) update a modifiable field to its next relative value.
You can view and modify the SAS controller whether it is enabled or disabled. You can use the Boot Support setting in the Adapter Properties menu to change the status of this setting. You must reconnect the EFI Driver for a new Boot Support setting to take effect. The following are descriptions for the Adapter List screen.
PCI Address FW Revision Displays the PCI Address assigned by the system BIOS to the adapter. • Bus value range 0x00 - 0xFF, 0 - 255 decimal • Device value range 0x00 - 0x1F, 0 - 31 decimal • Function range 0x00 - 0x7, 0 - 7 decimal Displays the MPT firmware version and type. The format is x.xx.xx.xx-yy where: x.xx.xx.xx refers to the FW version yy refers to the type. The currently supported type is IR.l). SAS Address Displays the SAS Address assigned to this adapter.
Figure 30 Select New Array Type Screen Select New Array Type Screen The Select New Array Type screen enables you to view an existing array or create an Integrated Mirror array of two disks, plus an optional hot spare. • To go to the Create New Array screen, select Create IM Volume. • To go to the View Array screen, select View an Existing Array. Create New Array Screen The Create New Array screen enables you to create an array.
in an IM. You can specify a hot spare at array creation, or after creation, if the array uses five disks or fewer. This field is grayed out under the following conditions: Drive Status • The device does not meet the minimum requirements for use in an IM array. • The array has a hot spare. • The array is made up of the maximum number of devices (six). • The device isn't large enough to mirror existing data on the primary.
View Array Screen The View Array screen enables you to view the current array configuration. To access the View Array screen, press Enter on the View Existing Array field from the Select New Array Type screen. You can perform the following actions on the View Array screen: • To view the next array, press N. • To create a new array, press C. The following are descriptions for the View Array screen: Array Displays the number of this array. Identifier Displays the array identifier.
Offline Disk is offline for some other reason. Inactive Disk has been set inactive. Not Syncd Data on disk is not synchronized with the rest of the array. Primary Disk is the primary disk for a two disk mirror and is OK. Secondary Disk is the secondary disk for a two disk mirror and is OK. Wrg Type Device is not compatible for use as part of an IM array. Too Small Disk is too small to mirror data.
Synchronize Array To synchronize the IM array, press Enter on Synchronize Array. The screen prompts you to perform this action. Press Y for yes or N for no. This field is grayed out under the following conditions: • The array is inactive. • The array does not need to be resynchronized. • The adapter's MPT firmware does not support the feature • Non-IR firmware is used. • IR is disabled. The array is inactive. Activate Array To activate an IM array, press Enter for Activate Array.
Starting CFGGEN The 1. 2. 3. cfggen utility is located on the HP IPF Offline Diagnostic and Utilities CD. To use cfggen: Insert the CD into the drive. Boot the server to the EFI Shell prompt. From the EFI Shell prompt, change to the CD drive: shell> fs0: Enter fs0:> 4. Change to the directory that contains cfggen.efi. fs0:> cd EFI\HP\TOOLS\NETWORK Enter fs0: EFI\HP\TOOLS\NETWORK> 5. From this directory, use cfggen. CFGGEN Operation The cfggen command is not case sensitive.
CREATE Command The CREATE command creates IM volumes on the SAS controller. Firmware and hardware limitations for this family of cards limit the number of configurations that are possible. Syntax cfggen create [qsync] [noprompt] Parameters Volume type for the volume to be created. Valid value is IM. Size of the IM volume in megabytes, or “MAX” for the maximum size available. [qsync] Quick synchronization of the volume created.
Parameters A SAS controller number between 0 and 255. [DELETE] Specifies that the hot spare is to be deleted (omit the DELETE keyword to specify hot-spare creation). : Enclosure number and Bay number that identify the disk drive that becomes the hot spare. Operation The number of disks in an IM array plus the hot spare cannot exceed three. You can create only one hot spare disk.
5. 6. 7. Choose the OS. Choose the firmware category you want to download. Download the firmware to a CD. Install the Latest Version of Firmware on the Server To install the firmware on the server: 1. Connect to the server console. See “Accessing the Integrated Lights Out 2 Management Processor” (page 40). 2. Make sure the external USB DVD drive is connected and turned on. See “Installing the OS Using a USB DVD Drive and the OS Disks” (page 66). 3.
4 Booting and Shutting Down the Operating System This chapter covers procedures for booting and shutting down operating systems that run on the server blade. The operating systems that run on the server blade are HP-UX 11i Version 2 (B.11.23), HP-UX 11i Version 3 (B.11.31), HP OpenVMS v8.3, Microsoft Windows Enterprise Server 2003, Red Hat Enterprise Linux 4 update 4, and Novell SuSE Linux Enterprise Server 10.
Figure 32 Ports on the SUV Cable Serial port USB ports (2) 3 Video port Reset (or reconnect) the server blade, and reboot to EFI. Turn on the external USB DVD device. 1 2 3. 4. Installing the OS from the External USB DVD Device To install the OS from an external USB DVD device: 1. Insert the CD with the OS into the external USB DVD drive. 2. Use the EFI Boot Manager Menu and boot to the drive that contains the CD with the OS. 3. From the boot menu, select EFI Shell (Built In). 4.
5. 6. The OS now starts loading onto the server blade. Follow the onscreen instructions to fully install the OS. Continue with “Configuring System Boot Options” (page 68) Installing the OS Using HP Ignite–UX The Ignite-UX product is an HP-UX administration tool that helps you install the HP-UX OS on multiple server blades on your network.
| Security Configuration | | | \----------------------------------/ | 1 2 1.4 GHz Active | | | | | | | | | \----------------------------------/ Use ^ and v to change option(s). Use Enter to select an option ◦ To correctly view the operating system console messages, go to the EFI Boot Manager Menu under the EFI Boot Manager Menu. From the Boot Configuration Menu, select Console Configuration. The Console Configuration screen displays the current configuration of the system console.
Examples of autoboot commands for HP-UX: ◦ Disable autoboot from the EFI Shell by issuing autoboot off ◦ Enable autoboot with the default timeout value by issuing autoboot on ◦ Enable autoboot with a timeout of 60 seconds by issuing the autoboot time 60 ◦ Set autoboot from HP-UX using setboot ◦ Enable autoboot from HP-UX using setboot -b on ◦ Disable autoboot using setboot -b off Examples of autoboot commands for Linux: • Disable autoboot from the EFI Shell by issuing autoboot off • Enable au
1. Access the EFI Shell environment. a. Log in to iLO 2 for Integrity and enter CO to access the system console. When accessing the console, confirm that you are at the EFI Boot Manager Menu (the main EFI menu). If you are at another EFI menu, choose the Exit option from the submenus until you return to the screen with the EFI Boot Manager heading. b. 2. Choose the EFI Shell menu option from the EFI Boot Manager Menu to access the EFI Shell environment.
3. 4. Press Enter to initiate booting using the chosen boot option. Exit the console and iLO 2 MP interfaces when finished using them. Press Ctrl-B to exit the system console and return to the MP Main Menu. To exit the MP Main Menu, enter X at the MP Main Menu. Booting HP-UX (EFI Shell) From the EFI Shell environment, boot HP-UX on a device by first accessing the EFI System Partition (for example fs0:) for the root device, then entering HPUX to initiate the loader. 1.
All rights reserved HP-UX Boot Loader for IA64 Revision 1.723 Press Any Key to interrupt Autoboot \efi\hpux\AUTO ==> boot vmunix Seconds left till autoboot 9 5. Exit the console and iLO 2 MP interfaces when finished using them. Press Ctrl-B to exit the system console and return to the MP Main Menu. To exit the MP Main Menu, enter X at the MP Main Menu. Booting HP-UX in Single-User Mode (EFI Shell) To boot HP-UX in single-user mode from the EFI Shell: 1. Stop the boot process at the HPUX.
........ (complete) loading symbol table loading System Directory(boot.sys) to MFS .... loading MFSFILES Directory(bootfs) to MFS ...... Launching /stand/vmunix SIZE: Text:25953K + Data:3715K + BSS:3637K = Total:33306K Console is on a Serial Device Booting kernel... 8. Exit the console and iLO 2 MP interfaces when finished using them. Press Ctrl-B to exit the system console and return to the MP Main Menu. To exit the MP, enter X at the MP Main Menu.
2. Issue the shutdown command with the appropriate command-line options. The command-line options you specify dictate the way in which HP-UX shuts down, and whether the server is rebooted. Use the following list to choose an HP-UX shutdown option for your server: • Shut down HP-UX and halt (power off) the server using shutdown -h Reboot a halted server by powering on the server using the PC command at the iLO 2 MP Command menu. • Shut down HP-UX and reboot the server by issuing shutdown -r.
• bcfg boot mv #a #b – Move the item number specified by #a to the position specified by #b in the boot options list. • bcfg boot add # file.efi "Description" – Add a new boot option to the position in the boot options list specified by #. The new boot option references file.efi and is listed with the title specified by Description. For example, bcfg boot add 1 \EFI\VMS\VMS_LOADER.EFI “OpenVMS V8.3–1H1” adds an OpenVMS item as the first entry in the boot options list.
3. At the EFI Shell environment, issue the map -Fs command to list all currently mapped bootable devices. The bootable file systems are listed as fs0:, fs1:, and so on. 4. Access the bootable partition (fsX: where X is the file system number) for the device you want to boot OpenVMS. For example, enter fs2: to access the bootable partition for the bootable file system number 2. The EFI Shell prompt changes to reflect the file system currently accessed.
2. At the OpenVMS DCL prompt issue the @SYS$SYSTEM:SHUTDOWN command and specify the shutdown options in response to the prompts given. NOTE: Use the command in step 2 when you shut down OpenVMS the first time. If you have shut down OpenVMS more than once, use the $ shutdown command.
2. Access the EFI System Partition (fsX: where X is the file system number) for the device from which you want to boot Windows. For example, enter fs2: to access the EFI System Partition for the bootable file system number 2. The EFI Shell prompt changes to reflect the file system currently accessed. The full path for the Microsoft Windows loader is \efi\microsoft\winnt50\ ia64ldr.efi and it should be on the device you are accessing.
1. 2. From the EFI Boot Manager Menu, choose an item from the boot options list to boot Windows using the chosen boot option. Access the EFI Boot Manager Menu for the server on which you want to boot Windows. Log in to the iLO 2 MP and enter CO to choose the system console. When accessing the console, confirm that you are at the EFI Boot Manager Menu (the main EFI menu).
You can use this method when using a graphical interface to the server. • Issue the shutdowncommand from the Windows command line. You can issue this command from a command prompt through the Special Administration Console (SAC) or from any other command line. The Windows shutdown command includes the following options: /s Shuts down and halts (power off) the server. This is the equivalent of Start—>Shut Down, Shut down. To power on the server, use the iLO 2 MP PC command.
Booting and Shutting Down Linux This section covers booting and shutting down Linux on the server blade. Procedures for Red Hat Enterprise Linux and SuSE Linux Enterprise Server are given in this section. • To add a Linux entry to the boot options list, see “Adding Linux to the Boot Options List” (page 82). • To boot Linux: • ◦ For details on Red Hat Enterprise Linux, see “Booting the Red Hat Enterprise Linux Operating System” (page 83).
• bcfg boot mv #a #b – Moves the item number specified by #a to the position specified by #b in the boot options list. • bcfg boot add # file.efi "Description" – Adds a new boot option to the position in the boot options list specified by #. The new boot option references file.efi and is listed with the title specified by Description. For example, bcfg boot add 1 \EFI\redhat\elilo.efi "Red Hat Enterprise Linux" adds a Red Hat Enterprise Linux item as the first entry in the boot options list.
4. Allow the ELILO.EFI loader to proceed with booting the Red Hat Enterprise Linux kernel. By default, the ELILO.EFI loader boots the kernel image and options specified by the default item in the elilo.conf file. To interact with the ELILO.EFI loader, interrupt the boot process (for example, enter a space) at the ELILO boot prompt. To exit the loader, use the exit command.
Shutting Down Linux Use the shutdown command to shut down Red Hat Enterprise Linux or SuSE Linux Enterprise Server. The Red Hat Enterprise Linux and SuSE Linux Enterprise Server shutdown command has the following options: Halts (power off) after shutdown. -h Use the PC command at the iLO 2 MP Command menu to manually power on or power off server hardware, as needed. -r Reboots after shutdown -c Cancels an already running shutdown time When to shut down (required.
5 Troubleshooting This chapter provides a preferred methodology (strategies and procedures) and tools for troubleshooting server blade error and fault conditions. Methodology General Troubleshooting Methodology There are multiple entry points to the troubleshooting process, dependent upon your level of troubleshooting expertise; the tools, processes, and procedures which you have at your disposal; and the nature of the server fault or failure. 1.
Should a failure occur, the front panel LEDs and the SEL helps you identify the problem or FRU: • The front panel LEDs and LAN LEDs of the server blade change color and blink to help identify specific problems, and display LAN activity. • The SEL provides detailed information about the errors identified by the LEDs. For server alerts of levels 3-5, the attention condition on the server LED can be cleared by accessing the logs using the sl command, available in the iLO 2 MP command mode.
Basic and Advanced Troubleshooting Tables Use the following troubleshooting tables to determine the symptoms or condition of a suspect server blade. Be aware that the state of the front panel LEDs can be viewed locally; or remotely using the vfp command from the MP. The tables are designed to cover troubleshooting symptoms from AC power-on up to booting the OS, specifically in Steps 1-5.
Table 13 Basic Low End Troubleshooting (continued) Step Condition Action 3. Examine the iLO 2 MP subsystem logs for events related to DC power rails. Preceding problem is fixed when the front panel LEDs are as follows: Health is off and power is steady green. 3a Server health LED is off and Internal health LED A fatal fault has been detected and logged while booting is steady green, iLO 2 MP is not running. or running System F/W. 1.
Table 13 Basic Low End Troubleshooting (continued) Step Condition Action 4. As a last resort, replace the server blade. Preceding problem is fixed when all boot paths are found. 5 Cannot see OS prompt on system console. BMC Nothing may be logged for this condition. and iLO 2 MP are running. 1. Examine the iLO 2 MP logs for entries related to processors, processor power modules (PPM)s, and shared memory, and core I/O devices (see “Errors and Error Logs” (page 98)).
Table 14 Advanced Low End Troubleshooting (continued) Step Symptom/Condition Action You must hard reset the server Preceding problem is fixed when the MCA does not repeat. blade to clear the fatal condition and boot the OS. Troubleshooting Tools The HP Integrity BL860c server blade uses LEDs and other tools to help troubleshoot problems that occur in the server blade.
Table 15 Server Blade Front Panel LEDs (continued) Item LED Description Status Off = Not flagged 2 Server health Off = Power is off Steady Green = Power is on Flashing Amber = Server is degraded (power is on or off) Flashing Red = Server critical (power is on or off) 3 Internal health Green = On Amber = Standby power (main power off, iLO 2 MP power on) Flashing Red = Critical internal error Off = Unit off (no power from enclosure) 4–7 NIC 1 Steady Green = Linked to network NIC 2 Flashing Green
Internal Health LED The internal health LED indicates the internal health of the server blade. If the LED is red, the server blade needs attention. Examine the event logs (on iLO 2 MP) for details of the problem. Table 18 details the states of the internal health LEDs.
Table 20 SAS Disk Drive LEDs Activity LED Status LED SAS Disk Drive State Off Off Offline or not configured Solid green Off Normal operation; no disk activity Flickering green Off Normal operation; disk read or write activity Off Flashing amber - 1/sec Offline, no disk activity; predictive failure Solid green Flashing amber - 1/sec Online, no disk activity; predictive failure Flickering green Flashing amber - 1/sec Disk activity; predictive failure Off Solid amber Offline; no disk act
4. 5. PAL code configures all processors. System Abstraction layer (SAL) code configures all platform central electronic complex (CEC) chips, including shared memory and all responding I/O devices. 6. Firmware code and stack are relocated to shared memory, after all x4 DIMM ranks in shared memory are configured and tested. 7. EFI Shell is launched from shared memory, and cache lines are retrieved 128 bytes at a time by the memory controller in zx1. 8. HP-UX loader is launched using the EFI device driver.
Online Support Tool Availability Online diagnostics are included in the HP-UX OE media, and are installed by default. Online Support Tools List The following online support tools are available on HP-UX 11.23 and HP-UX 11.31 hosted server blades. In some cases, a tool, such as a disk exerciser, is generic to many types of hardware; in other cases, a tool, such as a tape diagnostic, is specific to a particular technology or type of tape drive.
Table 24 Offline Support Tools List (continued) Offline Tool Functional Area CIODIAG2 Core I/O Diagnostic Specific Card I/O Diagnostics Card-Specific I/O Diagnostics/BIST General Diagnostic Tools Table 25 details the general diagnostic tools available for most HP Integrity server platforms. The distribution method is through the web.
WBEM indication providers and EMS Hardware Monitors Hardware monitors are available to monitor the following components (these monitors are distributed free on the OE media): • Chassis/Fans/Environment • CPU monitor • UPS monitor • FC Hub monitor • FC Switch monitor • Memory monitor • Core Electronics Components • Disk drives • Ha_disk_array Errors and Error Logs Event Log Definitions Often the underlying root cause of an MCA event is captured by server blade or BMC firmware in both the Sy
NOTE: The SEL E shows only event logs with alert level 2 or higher. The SEL defaults to alert level 2 on the server blade because there are some level 2 events related to rack infrastructure change. The alert level can be changed. The SEL is never overwritten unless first manually cleared. It does get full. The Forward Progress Log (F) shows all event log outputs. The FPL log is circular. It wraps, automatically replacing the oldest events with the newest. It never get full.
Enter menu item or [Ctrl-B] to Quit: e Log Name Entries % Full Latest Timestamped Entry --------------------------------------------------------------------------E - System Event 12 1 % 31 Oct 2003 23:37:45 Event Log Navigation Help: + View next block (forward in time, e.g. from 3 to 4) View previous block (backward in time, e.g.
6. To decode the blinking state of server LED, review the entire SEL and look at events with alert level 2 and above.
Sensor: Entity Presence 0x2000000009020050 FF01807115250300 If you do not get the above Alert Level 7 (IPMI) event, but get another high level alert, replace the server blade. 8. 9. Add at least one rank of memory DIMMs. Enter the DF command. The following displays: Display FRU Information Menu: S - Specific FRU A - All available FRUs V - Display Mode: Text 10. Enter S to show the FRU IDs.
Processor Installation Order For a minimally loaded server blade, one IPF processor module must be installed in processor slot 0. Slot 0 is the slot closer to the server blade chassis. Install a processor of the same version into processor slot 1 (if purchased). Processor Module Behaviors All physical processors become functional after server power is applied. Each processor is in a race to fetch their instructions from their processor instruction and data caches to complete early self test and rendezvous.
ropes to support 4 Lower Bus Adapter (LBA) chips.
Table 26 Rope-to-ACPI Paths (continued) PCI Bus Physical Rope # Logical ACPI Path Acpi(HWP0002,PNP0A03,0)/Pci(1 | 2) Fast core @ 66 MHz 1 Acpi(HWP0002,PNP0A00,400)/Pci(1 | 0) Dual FibreChannel @ 133 MHz 2, 3 Acpi(HWP0002,PNP0A03,400)/Pci(2 | 0) Acpi(HWP0002,PNP0A03,400)/Pci(2 | 1) Pair of dual LAN @ 133 MHz Acpi(HWP0002,PNP0A03,500)/Pci(0 | 0) 4, 5 Troubleshooting Management Subsystem Both the iLO 2 MP and the BMC are integrated components (not FRUs) on the server blade.
4. On the server blade you are updating, issue the fweupdate.efi command from the EFI command prompt by entering: fweupdate.BL860c.sxxxx.byyyy.mzzzz.efi. where: s means system firmware; xxxx is the system firmware version number b means BMC firmware; yyyy is the BMC firmware version number m means iLO 2 MP firmware; zzzz is the iLO 2 MP firmware version number This command updates the system firmware, BMC firmware, and iLO 2 MP firmware.
Online Support To contact HP Customer Support online, see the Worldwide Limited Warranty and Technical Support Guide or visit us at http://www.hp.com/bizsupport. On our web page, enter the server blade model number (for example, “BL860c”) and search the field.
6 Removing and Replacing Components This chapter provides information on removing and replacing components in the server blade. Service Tools Required Service of this product may require the following tools: • The CPU Install Tool Kit, consisting of: • Disposable ESD Kit • Labelless CPU install tool (2.
Figure 35 Removing a SAS Disk Drive CAUTION: Always populate hard drive bays with a SAS disk drive or a hard drive blank. Operating the server blade without a SAS disk drive or disk drive blank causes improper airflow and cooling, which can lead to thermal damage. Replacing a SAS Disk Drive To replace a SAS disk drive: 1. Slide the drive into the cage until it is fully seated. 2. Close the lever to lock the drive into place.
Figure 36 Removing a Disk Drive Blank Replacing a Disk Drive Blank To replace the hard drive blank, slide the blank into the bay until it locks into place. The hard drive blank is keyed to fit only one way. Preparing the Server Blade for Servicing To service an internal server blade component, power down the server blade and remove it from the server blade enclosure. CAUTION: Electrostatic discharge can damage electronic components.
Removing and Replacing the Server Blade from the Enclosure The following procedures describe how to remove and replace the server blade from the enclosure. Removing the Server Blade From the Enclosure To remove the server blade from the enclosure: 1. Press the Release button on the server blade (1). See Figure 37. CAUTION: After you press the Release button, the server blade is unlocked from the enclosure. Use both hands to support the server blade when you remove it from the rack.
1. 2. Slide the server blade back into the enclosure until flush with the enclosure. Close the lever. NOTE: After you install the server blade back into the enclosure, the server blade might go to standby power (Internal health LED is amber), or full power (internal health LED is green, and the fans may get louder). 3. If the server blade does not come up to full power, push the Power button to get the server to full power. The fans might get louder as the server powers up to full power.
1. Ensure the access panel latch is in the open position (pointing up) before replacing the access cover. See Figure 39 (page 113). 2. Place the access panel on the blade with the panel hanging over the back of the enclosure about 1.25 cm (0.5 in).(1). See Figure 39. 3. 4. 5. 6. Slide the access panel toward the front of the server until the access panel clicks into place (2). Close the access panel latch (3).
• TPM module • System board NOTE: The server blade must be removed from the enclosure to access the internal components; therefore, no internal devices are hot-swappable or hot-pluggable in the server blade. Removing and Replacing DIMMs There are 12 DIMM slots located on the system board. The following procedures describe how to remove and replace memory DIMMs in the server blade. Removing a DIMM To remove a failed DIMM from the server blade: 1.
5. 6. Slots DIMM 4A and DIMM 4B Slots DIMM 5A and DIMM 5B The server blade uses a minimum of 1 GB of memory (two 512-MB DIMMs), and a maximum of 96 GB of memory (twelve 8-GB DIMMs). If you purchased additional memory, use these procedures to install more memory into your server blade. Load DIMMs from highest capacity to lowest capacity (for example, load the 8-GB DIMMs first, then the 4-GB DIMMs, then the 2-GB DIMMs, and so forth). The memory subsystem supports chip spare functionality.
Figure 41 Processor Slot Locations on the System Board Removing a Processor To remove a processor: Removing processor 0 is shown in this procedure. If you are only adding a processor, remove the dust cover from the processor socket, and proceed to “Installing a Processor” (page 117). 1. Power off the server, and remove it from the enclosure. See “Preparing the Server Blade for Servicing” (page 110). 2. Remove the access panel. See “Removing the Server Blade Access Panel” (page 112). 3. 4.
Figure 43 ZIF Socket on the Processor 8. 9. Carefully remove the processor module by lifting it straight up from the system board. Place the processor module in an antistatic bag. Installing a Processor To install the processor: 1. Ensure the ZIF socket for the processor you are installing is open. Insert the 2.5 mm hex end of the Torx T-15 screwdriver into the ZIF socket and gently try to rotate the socket 180 degrees counter clockwise. If the socket doesn’t turn, the socket is open.
Figure 45 Alignment Holes in Processor Slot 0 3. 4. Slide the processor sequencer to the right and hold it to uncover the ZIF socket. Tighten the ZIF socket with the with the 2.5-mm hex end of the processor installation tool by turning the socket 180 degrees clockwise. See Figure 46. Figure 46 ZIF Socket on Processor Slot 0 5. 6. Release the processor sequencer. Tighten the captive shoulder screws (1 - 4) on the processor heat sink with the Torx T-15 screwdriver. See Figure 47 (page 119). 7.
Figure 47 Installing a Processor in Slot 0 8. 9. Connect the power cable to the power connector on the processor. Install the access panel. See “Replacing the Server Blade Access Panel” (page 112). 10. Place the server blade back into the enclosure and power it up. See “Replacing the Server Blade in the Enclosure” (page 111). Removing and Replacing the SAS Backplane The following procedures describe how to remove and replace a failed SAS backplane.
5. Remove the SAS backplane by lifting it straight out of the server by the backplane handle. See Figure 48. Figure 48 Removing the SAS Backplane 1 SAS backplane handle 2 SAS backplane Installing the SAS Backplane To install the SAS backplane into the server blade after a SAS backplane failure: 1. Slide the SAS backplane into the slot on the system board. See Figure 48 (page 120). 2. Install the SAS disk drives, or disk drive blanks, into the server blade.
Figure 49 Removing the Front Display Assembly Housing Screws 4. Remove the front display assembly from the front of the server blade by pulling it straight off the front of the server. See Figure 50 (page 121). Figure 50 Removing the Front Display Assembly from the Front of the Server Blade Replacing the Front Display Assembly To install the new front display assembly into the server blade after a front display board failure: 1. Slide the front display assembly onto the front of the server blade chassis.
Removing the Server Battery IMPORTANT: Removing the server battery results in a permanent loss of important information that was stored in the server’s nvram. Removing the server battery results in losing boot configurations and the system logs. To create a backup of any valued configurations before you remove the battery, HP recommends using nvrambkp. Also, be sure to obtain copies of the system logs before removing the battery. To remove the server battery from the system board: 1.
Figure 51 Server Battery Location Server battery on the system board Dispose of the server battery by following your local requirements. 1 5. Replacing the Server Battery To replace the server battery: 1. Install the new server battery by gently pushing the battery into the socket. Move the processor 0 power cable if necessary. IMPORTANT: engaged. 2. 3. Ensure that the new battery is fully seated and that all locking tabs are correctly Install the access panel.
4. Grasp the mezzanine card by the edges and lift it off of the port. NOTE: Mezzanine card 2 is installed above mezzanine card 1 on the system board. If you remove mezzanine card 1, remove mezzanine card 2 to access it (if it is installed).
Removing a Cache Module CAUTION: To avoid bending the controller board, only remove or replace the cache module when it is installed in the server blade. To remove a cache module: 1. If the BBWC battery will also be removed: a. Back up all data. b. Close all applications. 2. Power of the server blade and remove it from the enclosure. See “Preparing the Server Blade for Servicing” (page 110). 3. Remove the access panel. See “Removing the Server Blade Access Panel” (page 112). 4.
6. If only replacing the cache module, unplug the battery cable from the cache module. Figure 54 Disconnecting the Battery Replacing the Cache Module CAUTION: To avoid bending the controller board, only remove or replace the cache module when it is installed in the server blade.
1. With the cache module battery connector facing the side of the server blade that memory cell 1 abuts, line up the cache module's two connectors with the two corresponding slots on the mezzanine controller board. Figure 55 Lining Up the Cache Module 2. Press straight down on the cache module until it snaps into place. Figure 56 Pressing Down the Cache Module 3. Plug the battery cable into the cache module battery connector.
Figure 57 Attaching the Battery Cable NOTE: Only use the 24 inch BBWC cable. IMPORTANT: The BBWC battery must remain connected to the cache module to preserve the data when removing the cache module to transfer data. Therefore, route the BBWC cable so that the cache module and battery can be removed together. 4. 128 If the controller is in mezzanine slot 1 or 2 route the cable along the following path: a. Under the CPU 0 power pod wires b. Along the rear of the server blade c.
e. Between the outermost mezzanine 2 post and the server blade power connector cables Figure 58 Mezzanine Slot 1 or 2 BBWC Cable Routing 5. If the controller is in mezzanine slot 3 route the cable along the following path: a. Under the CPU 0 power pod wires b. Along the rear of the server blade c. Inside the mezzanine posts near the rear chassis plug d.
e. Between mezzanine slots 1 and 2. Figure 59 Mezzanine Slot 3 BBWC Cable Routing 6. Replace any mezzanine cards that were removed. See “Replacing a Mezzanine Card” (page 124). 7. Install the access panel. See “Replacing the Server Blade Access Panel” (page 112). 8. Place the server blade back into the enclosure and power it up. See “Replacing the Server Blade in the Enclosure” (page 111).
6. CAUTION: The BBWC battery must remain connected to the cache module to preserve the data when removing the cache module to transfer data. If replacing the battery, unplug the battery cable from the cache module. Figure 60 Disconnecting the BBWC Cable from the Cache Module 7. Remove CPU 0. See “Removing a Processor” (page 116). 8. Starting from the end near the rear of the server blade, pry the BBWC battery off the chassis.
9. If replacing the battery, invert the BBWC battery and push the battery plug out of the battery connector. Figure 62 Releasing the Battery Cable from the Battery Replacing the BBWC Battery To replace the BBWC battery: 1. Invert the BBWC battery (print side down) and with the cable plug label (contoured) side up, line up the plug edges with the thin slits on the sides of the battery. Figure 63 Lining up the Plug 2. 132 Push the battery cable plug into the battery connector until it snaps into place.
Figure 64 Connecting the Battery Cable 3. Remove CPU 0. See “Removing a Processor” (page 116). 4. If this is the first BBWC battery to ever have been installed in the server blade: a. NOTE: If the bottom of the battery or top of the battery holder are dirty or oily, clean their surfaces with a 50–50 mixture of Isopropyl alcohol and water before applying the stickers. Remove the protector from the sticky side of one of the plastic Dual Lock hook and loop stickers.
Figure 66 Placing the Sticker c. Line up the wavy side of the second sticker with the wavy side of the first sticker and press down until they stick together. Figure 67 Connecting the Stickers d. Remove the protector from the second sticker to expose the sticky surface.
e. IMPORTANT: The battery must be positioned so it does not block access to the system battery, does not rest on the system board, and is about 1/4 inch below the top of the chassis wall so that it will clear the access cover. Press the side of the battery with the exposed Dual Lock hook and loop sticker against the side of the chassis wall next to the CPU 0 position.
Figure 71 Placing Sticker c. Line up the sticker with the Daul Lock hook and loop sticker on the chassis wall by CPU 0. Figure 72 Lining Up the Sticker d. Press against the battery until the two stickers stick together to hold the battery in place.
6. Replace CPU 0. See “Installing a Processor” (page 117). Figure 74 CPU 0 Replaced 7. Remove any mezzanine cards blocking access to the mezzanine controller board. See “Removing a Mezzanine Card” (page 123). IMPORTANT: The BBWC battery must remain connected to the cache module to preserve the data when removing the cache module to transfer data. Therefore, route the BBWC cable so that the cache module and battery can be removed together. NOTE: 8. Only use the 24 inch BBWC cable.
e. Between the outermost mezzanine 2 post and the server blade power connector cables Figure 75 Mezzanine Slot 1 or 2 BBWC Cable Routing 9. 138 If the controller is in mezzanine slot 3 route the cable along the following path: a. Under the CPU 0 power pod wires b. Along the rear of the server blade c. Inside the mezzanine posts near the rear chassis plug d.
e. Between mezzanine slots 1 and 2. Figure 76 Mezzanine Slot 3 BBWC Cable Routing 10. Plug the battery cable into the cache module battery connector. NOTE: The lip of the battery cache module plug has three tiny tabs that should face down.
11. Replace any mezzanine cards that were removed. See “Replacing a Mezzanine Card” (page 124). 12. Install the access panel. See “Replacing the Server Blade Access Panel” (page 112). 13. Place the server blade back into the enclosure and power it up. See “Replacing the Server Blade in the Enclosure” (page 111). NOTE: After installing a BBWC battery, you might see a POST message during reboot indicating the array accelerator (cache module) is temporarily disabled.
5. Grasp the failed TPM and pull it straight up off the system board. See Figure 78 (page 141) for the location of the TPM on the system board. Figure 78 TPM Location on the System Board Replacing the TPM To install the TPM: IMPORTANT: component. You must be running the supported version of the HP-UX OS to use the TPM security The TPM replacement must be performed by an HP CE. 1. Install the new TPM on the system board by pushing it down onto the posts on the system board.
Removing and Replacing the System Board The following procedures describe how to remove and replace the system board from the server blade. When a system board fails, you must remove the following components from the failed system board (unless they caused the failure), and install them on the new system board: • SAS disk drives • Memory DIMMs • Processors • SAS backplane • Mezzanine cards • TPM CAUTION: Electrostatic discharge can damage electronic components.
Figure 79 Air Baffle Locations 2 Processor air baffle Controller air baffle 10. Remove the rear air baffle and the CPU power cable holder from the system board (Figure 80). 1 Figure 80 Rear Air Baffle and CPU Power Cable Holder Location 11. Remove the TPM. See “Removing the TPM” (page 140). NOTE: The system board is attached to the front display panel. 12. Loosen the two captive thumbscrews toward the back of the system board. See Figure 81 (page 144) for the thumbscrew locations.
Figure 81 System Board 13. To disengage the system board from the connector on the front display board and the keyways on the server blade chassis, use the two thumbscrews as handles to slide the system board out the back of the sheet metal frame. 14. Lift the system board out of the server blade. Replacing the System Board NOTE: The system board comes with the server battery already installed. To install a system board in the server blade after a system board failure: 1.
IMPORTANT: Make sure the front display panel connector fully seats into the system board connector. If the connector is not fully seated, the server blade can have intermittent failures. See Figure 82. Figure 82 System Board / Front Panel Connection In Figure 1–Bad connection, the connector is not properly seated. In Figure 2–Good connection, the connector is properly seated. 6. Install the TPM. See “Replacing the TPM” (page 141). 7. Install the air baffles. See Figure 79 (page 143). 8.
A Parts Information This appendix provides parts information for the HP Integrity BL860c server blade components (customer replaceable units [CRUs]). Server Blade Components List Table 29 details the part numbers of the components (or CRUs) in the server blade. NOTE: Part numbers are found by using the part nomenclature from this list to select the correct part from the HP Partsurfer. If a part that is not listed in the CRU list needs to be replaced, the Base Unit Repair Kit is required.
Table 29 CRU List (continued) Description Manufacturing Part Replacement Number Part Number Exchange Part Number Direct adapter mezzanine card for connecting to the direct attach storage blade 431644–B21 436010–001N 463010–001 Dual-port 4x InfiniBand mezzanine card 410533–B21 410500–001N 410500–001 HPC 4x DDR IB mezzanine HCA 406855–001 410500–001N 410500–001 HP HPDC 4x DDR IB Cisco mezzanine HCA 438760-B21 410500–001N 410500–001 SPS-Mod BLSYS ENet 1 GB / 10 GB 399593-B22 399725–001 SP
B Server Upgrades This appendix provides information for upgrading processors. Processor Upgrades The HP Integrity BL860c server blade supports upgrades from Intel Itanium Montecito to Intel Itanium Montvale processors. CAUTION: Ensure that processor speed and cache size are identical for all processors. Failure to observe this caution results in performance degradation or system failure. To ensure compatibility, use processors with identical part numbers.
OpenVMS OpenVMS must be upgraded to OpenVMS V8.3-1H1 to support the processor upgrade. Windows Windows® supports the processor upgrade. Linux Linux supports the processor upgrade. If you choose to move any I/O cards or storage during this upgrade, Linux must be reinstalled.
C Utilities This appendix describes the utilities that are part of the server blade. These include the EFI Boot Manager and EFI-POSSE. NVRAM Backup Utility The HP Integrity Non-Volatile RAM (NVRAM) configuration backup utility provides the capability to store and restore critical server settings and EFI Boot Manager options on the server blade. This utility is available as an offline EFI application.
Example 1 nvrambkp -h Hewlett-Packard (R) IPF Non-Volatile Configuration Back-up Utility Version 01.03.01 Copyright (C) Hewlett-Packard. All rights reserved. Usage: Purpose: The application provides the capability to archive & restore critical system settings.
Figure 83 EFI Boot Sequence The EFI boot manager loads EFI applications (including the OS first stage loader) and EFI drivers from an EFI-defined file system or image loading service. Non-volatile RAM (NVRAM) variables point to the file to be loaded. These variables contain application-specific data that is passed directly to the EFI application. EFI variables provides system firmware a boot menu that points to all the operating systems, even multiple versions of the same operating systems.
Table 31 EFI Commands EFI Shell Command BCH Command Equivalent (PA-RISC) BCH Command Parameters (PA-RISC) Definition These commands are found in all other menus info boot Boot [PRI|HAA|ALT|] Boot from specified path help HElp [
Table 31 EFI Commands (continued) EFI Shell Command BCH Command Equivalent (PA-RISC) BCH Command Parameters (PA-RISC) Definition info io IO Display firmware version for PDC, ICM, and complex lanaddress LanAddress Display core LAN station address info mem Memory Display memory information info cpu PRocessor Display processor information errdump clear CLEARPIM Clear (zero) the contents of PIM mm MemRead pdt page deallocation table (pdt) errdump mca processor internal memory (PIM) SERvi
a list of commands that appear under that BCH menu. You can then invoke help followed by bch, the menu name, and a BCH command name to display information on that command. This points you to the command that has taken the place of that BCH functionality, or will inform you that the functionality no longer exists. As a shortcut, enter help followed by bch and a BCH command name to go straight to that command.
Example 2 help Command Shell> help List of classes of commands: boot configuration devices memory shell scripts -- Booting options and disk-related commands -- Changing and retrieving system information -- Getting device, driver and handle information -- Memory related commands -- Basic shell navigation and customization -- EFI shell-script commandsType "help" followed by a class name for a list of commands in that class Type "help" followed by command name for full documentation Example 3 help bch Comman
Example 5 help cpuconfig Command Shell> help cpuconfig CPUCONFIG [cpu] [on|off] cpu Specifies which cpu to configure on|off Specifies to configure or deconfigure a cpu Notes: 1.
boottest off boottest [test] boottest [test] [on|off] Skip all tests (for a faster boot time) Displays status of specific Speedy Boot bit Sets or clears a specific Speedy Boot bit Parameters [test] Each test can be set or cleared: booting_valid Enable/disable system firmware response to BOOTING bit. If OS Speedy Boot aware set to on. early_cpu Enable/disable early CPU selftests. late_cpu Enable/disable late CPU selftests. platform Enable/disable system board hardware tests.
state is entered and is different from the current state of a processor, its status changes on the next boot. The last remaining configured processor in a server cannot be deconfigured. Example 8 cpuconfig Command Shell> cpuconfig PROCESSOR INFORMATION # of CPU Logical Slot CPUs Speed ----------------0 1 1 GHz 1 1 1 GHz L3 Cache Size ---1.5 MB 1.5 MB L4 Cache Size ----None None Family/ Model (hex.) Rev --------1F/01 B1 1F/01 B1 Processor State ---------Active Active Family/ Model (hex.
Example 11 conconfig 2 primaryCommand To change primary operating system console Shell> conconfig 2 primary CONSOLE CONFIGURATION Index Status Type Device Path ----- ------ -------------1 NC Serial Acpi(PNP0501,0) 2 P Serial Acpi(HWP0002,0)/Pci(1|1) 3 S VGA Acpi(HWP0002,0)/Pci(4|0) Example 12 conconfig 3 offCommand To disable a console Shell> conconfig 3 off CONSOLE CONFIGURATION Index Status Type Device Path ----- ------ -------------1 NC Serial Acpi(PNP0501,0) 2 P Serial Acpi(HWP0002,0)/Pci(1|1 3 NC VGA
Parameters mca cpe cmc init la clear dumps the Machine Check Abort error log dumps the Corrected Platform Error log dumps the Corrected Machine Check log dumps the Initialization log dumps the Logic Analyzer log erases all of the logs (mca, cpe, cmc, init, la) Operation If a user enters no parameters, the usage is displayed. Otherwise, the specified error log displays. Adding -n to the clear parameter disables the confirmation prompt (Access the errdumpcommand from the System Configuration menu).
Example 14 info all Command Shell> info all SYSTEM INFORMATION Date/Time: Oct 31, 2003 22:03:39 (20:03:10:31:22:03:39) Manufacturer: hp Product Name: server BL860c Product Number: A9901A Serial Number: MYJ3350026 UUID: 48B4F371-E34C-11D6-A8D6-07A8C14CB68B System Bus Frequency: 200 MHz PROCESSOR MODULE INFORMATION CPU Slot # of Logical CPUs ---0 1 ------1 1 Speed L3 Cache Size L4 Cache Size Family/ Model (hex.) Rev Processor State -------1 GHz 1 GHz -----1.5 MB 1.
Selftest --------early_cpu late_cpu platform chipset io_hw mem_init mem_test Setting -------------Run this test Run this test Run this test Run this test Run this test Run this test Run this test LAN Address Information: LAN Address ----------------Mac(00306E4C4F1A) *Mac(00306E4C0FF2) Path ---------------------------------------Acpi(HWP0002,0)/Pci(3|0)/Mac(00306E4C4F1A)) Acpi(HWP0002,100)/Pci(2|0)/Mac(00306E4C0FF2)) FIRMWARE INFORMATION Firmware Revision: 1.10 [4341] PAL_A Revision: 7.31/5.
Example 15 info cpu Command Shell> info cpu PROCESSOR MODULE INFORMATION # of Logical CPUs ------1 1 CPU Slot ---0 1 Speed -------1 GHz 1 GHz L3 Cache Size -----1.5 MB 1.5 MB L4 Cache Size -----None None Family/ Model (hex.
Example 18 info boot Command Shell> info boot BOOT INFORMATION Monarch CPU: Current Preferred Monarch Monarch Possible Warnings -------- -------------------------0 0 AutoBoot: on - Timeout is : 7 SEC Boottest: boottest Settings Default Variable OS is not speedy boot aware.
Example 19 ioconfig command Shell> ioconfig Deconfigure or reconfigure IO components or settings IOCONFIG [fast_init | wol [on | off]] fast_init Specifies device connection policy setting mps_optimize Specifies PCIe optimization setting wol Specifies System Wake-On-LAN setting on | off Specifies to configure or deconfigure a feature or component Note: 1. If fast_init is enabled, firmware will connect only the minimum set of devices during boot.
Syntax monarch Parameters specifies a cpu Operation If specified with no parameters, monarch displays the Monarch processor for the server. Specifying a processor number alters the preferred Monarch processor. None of these changes takes affect until after a reboot.
Example 22 pdt Command Shell> pdt PDT Information Last Clear time: PDT has not been cleared Number of total entries in PDT: 50 Number of used entries in PDT: 0 Number of free entries in PDT: 50 Number of single-bit entries in PDT: 0 Number of multi-bit entries in PDT: 0 Address of first multi-bit error: x0000000000000000 Example 23 pdt clear Command Shell> pdt clear Are you sure you want to clear the PDT? [y/N] y Shell> Shell> pdt PDT Information Last Clear time: 10/21/01 5:00p Number of total entries in P
Example 24 sysmode Command Shell> sysmode System Mode: NORMAL Shell> sysmode admin You are now in admin mode. Shell> sysmode service You are now in service mode.
1. To map the parameters for all PCI cards installed in the server, enter the info io command at the EFI Shell prompt. A list of all the devices that are installed in the server blade and managed by EFI drivers displays.
Shell> devtree Device Tree Ctrl[04] Ctrl[0A] Ctrl[12] Ctrl[13] Ctrl[14] Ctrl[15] Ctrl[48] Ctrl[83] Ctrl[16] Ctrl[49] Ctrl[0B] Ctrl[17] Ctrl[18] Ctrl[19] Ctrl[4B] Ctrl[0C] Ctrl[0D] Ctrl[0E] Ctrl[1A] Ctrl[1B] Ctrl[36] Ctrl[37] Ctrl[31] Ctrl[32] Ctrl[30] Ctrl[1C] Ctrl[32] Ctrl[30] Ctrl[33] Ctrl[34] Ctrl[35] Ctrl[31] Ctrl[32] Ctrl[30] Ctrl[44] Ctrl[46] Acpi(HWP0002,0) Usb Open Host Controller Usb Open Host Controller Acpi(HWP0002,0)/Pci(1|2) PCI IDE/ATAPI Controller DW-28E FAT File System [FAT32] 118 MB Acpi(H
This listing shows which driver controls which device (controller). In the above example, the interface information is shown highlighted bold. You can tell the information is for this interface because the values shown for Ctrl—17 and 18—are the controller’s handles for the interface two channels (from the information displayed by the devtree command). NOTE: The EFI driver’s handle values change on every boot.
PCI Device, and PCI Function to the Bus #, Dev #, and Fnc # values from the info io command. CAUTION: Do not change the value for any of these fields on the Adapter Properties screen: • Auto Termination • Parity • Bus Scan Order • Spinup Delay (Secs) Changing any of these fields can cause unpredictable results.
Using the Boot Option Maintenance Menu This menu enables you to select console output and input devices as well as various boot options. In all the following sections, the menus enable the following functionality: • Help to display the help available for the command • Exit to return to the main Boot Options Maintenance menu • Enter to select an item after using the arrow keys to highlight the item • Save Settings to NVRAM to save your changes NOTE: The options shown here are examples.
• Removable Media Boot allows you to boot from a removable media drive (CD/DVD drive). This option does not support booting from a specific file on a specific removable media disc. • The two Load Files are the EFI Shell and the LAN. Add a Boot Option Use this option to add items to the EFI boot menu. This option displays the file systems that are on your server and lets you browse these file systems for applications or drivers that are executable. Executable files end with the .efi extension.
For example, if you normally boot using a configuration on your LAN but would like to boot from a local hard drive if the LAN is unavailable, move the LAN boot option to the top of the list, followed by the hard drive boot option. The menu lists boot options that currently exist in the main Boot Manager menu. Change the priority of the items by moving them up or down in the list: • Press U to move an option up. • Press D to move an option down.
Interrupting the timeout during the countdown stops the Boot Manager from loading any boot options automatically. If there is no countdown, boot options must be selected manually. • To set the auto boot timeout value, in seconds, select Set Timeout Value and enter the desired value. • To disable the timeout function, select Delete/Disable Timeout. NOTE: When this option is selected, the server does not automatically boot. The server stops at the EFI boot menu and waits for user input.
This option displays the console devices on your server. This normally includes a standard keyboard and mouse, and a serial port for receiving output from a terminal emulation package on a laptop. Several different terminal emulation protocols are supported. • When changing serial devices, changes must be made to Output, Input, and Error menus for proper operation. NOTE: Some Operating Systems support multiple input devices, such as a simultaneous serial and keyboard input.
• Reset Configuration to Default lets you restore server settings to their original configuration • Help displays additional information about the available options • Exit returns to the EFI startup menu Security/Password Menu You can set administrator and user passwords to provide different levels of access to the system firmware: Resetting Passwords If you forget your passwords, they can be reset using an iLO 2 MP command. • Run the MP BP command to reset the iLO 2 MP and reset the password.
Index A access panel removing, 29, 112 replacing, 37, 112 accessing iLO 2 MP, 40 ACPI pathing, 104 adapter path, determining with info command, 170 slot number, determining with info command, 170 adding Windows to the boot options list, 78 allowing remote access, 47 antistatic wrist strap, 26 autoboot, 69 B battery see server battery BBWC cable routing, 128, 129, 137, 138 BBWC battery removing, 130 replacing, 132 boot option add, 175 change boot order, 175 delete, 175 manage bootnext setting, 176 set auto
replacing, 114, 115 slot locations, 33, 114 disabling remote access, 48 disk drive backplane see SAS backplane see SAS backplane disk drive blank removing, 28, 109 replacing, 110 disk drives see SAS disk drives drvcfg command EFI configurable components, displaying, 171 EFI driver handle, determining, 172 EFI Setup Utility, starting, 172 drvcfg utility, 53 adapter list screen, 54 adapter properties screen, 55 create new array screen, 57 manage array screen, 60 RAID properties screen, 56 select new array typ
DIMMs, 32, 115 front display assembly, 121 mezzanine card, 124 mezzanine cards, 33 NVRAM utility, 150 operating system with DVD drive, 66 operating system with HP-UX Ignite, 68 operating system with vMedia, 68 processor, 30, 117 SAS backplane, 120 SAS disk drives, 28 server battery, 123 server blade into enclosure, 38 system board, 144 TPM, 141 installing components, 29 installing the PCI expansion blade, 39 integrated Lights Out Management Processor see iLO 2 MP integrated mirroring array see IM array inte
slot locations, 31, 115 R RB command obtaining the enclosure name, 46 rear panel ports, 23, 50 remote access allowing, 47 configuring, 46 disabling, 47, 48 securing, 45 removing access panel, 29 BBWC battery, 130 cache module, 125 DIMMs, 114 disk drive blank, 28, 109 front display assembly, 120 mezzanine card, 123 processor, 116 SAS backplane, 119 SAS disk drive, 108 server battery, 122 server blade access panel, 112 server blade from enclosure, 111 system board, 142 TPM, 140 replacing access panel, 37 BBW
connecting to server blade, 42 SUV cable port, 20 SUV cable port location, 22 system board removing, 142 replacing, 144 system boot options, 68 system configuration menu, 178 system event log, 87, 98, 99 T ToC button location, 22 tools required, 28, 108 TPM location, 141 removing, 140 replacing, 141 troubleshooting basic, 88 BMC and MP firmware, 105 communications modules, 104 environment, 106 management subsystems, 105 memory, 103 methodology, 87 online support, 107 overview, 86 phone support, 107 process
