Specifications
Table Of Contents
- HP Integrity BL860c Server Blade User Service Guide
- Contents
- About This Document
- 1 Overview
- 2 General Site Preparation Guidelines
- 3 Installing the Server Blade Into the Enclosure
- Safety Information
- Installation Sequence and Checklist
- Unpacking and Inspecting the Server Blade
- Installing Additional Components
- Installing and Powering On the Server Blade
- Accessing the Integrated Lights Out 2 Management Processor
- Configuring the iLO 2 MP
- Accessing EFI or the OS from iLO 2 MP
- Server Blade to Enclosure Interface
- LAN / NIC Configuration
- Configuring the HP 2 Internal Port SAS Host Bus Adapter
- Verify and Install the Latest Firmware
- 4 Booting and Shutting Down the Operating System
- 5 Troubleshooting
- Methodology
- Troubleshooting Tools
- Errors and Error Logs
- Supported Configurations
- Troubleshooting Processors/Memory/SBA
- Enclosure Information
- Cooling Subsystem
- Troubleshooting Communications Modules
- Troubleshooting Management Subsystem
- Firmware
- Troubleshooting the Server Interface (System Console)
- Troubleshooting the Environment
- Reporting Your Problems to HP
- 6 Removing and Replacing Components
- Service Tools Required
- Removing and Replacing a Hot-Plug SAS Disk Drive
- Preparing the Server Blade for Servicing
- Removing and Replacing the Server Blade from the Enclosure
- Removing and Replacing the Server Blade Access Panel
- Removing and Replacing Internal Components
- Removing and Replacing DIMMs
- Removing and Replacing a Processor
- Removing and Replacing the SAS Backplane
- Removing and Replacing the Front Display Assembly
- Removing and Replacing the Server Battery
- Removing and Replacing the Mezzanine Cards
- Removing and Replacing a Cache Module
- Removing and Replacing the Low Profile Battery Backed Write Cache (BBWC) Battery
- Removing and Replacing the Trusted Platform Module
- Removing and Replacing the System Board
- A Parts Information
- B Server Upgrades
- C Utilities
- NVRAM Backup Utility
- Extensible Firmware Interface
- EFI/POSSE Commands
- Specifying Parameters
- Using the Boot Option Maintenance Menu
- Integrated Lights Out 2 Management Processor
- Index
Table 20 SAS Disk Drive LEDs
SAS Disk Drive StateStatus LEDActivity LED
Offline or not configuredOffOff
Normal operation; no disk activityOffSolid green
Normal operation; disk read or write activityOffFlickering green
Offline, no disk activity; predictive failureFlashing amber - 1/secOff
Online, no disk activity; predictive failureFlashing amber - 1/secSolid green
Disk activity; predictive failureFlashing amber - 1/secFlickering green
Offline; no disk activity; critical faultSolid amberOff
Offline; drive selected by locator functionSolid blueOff
Drive rebuildingOffFlashing green - 1/sec
LAN LEDs
There are four LAN LEDs on the front panel of the server blade. They are NIC 1 through NIC 4.
Table 21 details the functions of the LAN LEDs.
Table 21 1 GB LAN States
StateLED Color
No linkOff
Link foundSteady Green
LAN activity on network linkFlashing Green
Boot Process LEDs
Table 22 shows the normal boot process, as reflected in changes to front panel LED states:
Table 22 Normal Boot Process LED States
Normal Power-Up Through HP-UX BootPowerHealthStep
No AC power to the server blade.OffOff1
Server blade is shut down (server is off), AC power and
standby power is active, last health status was healthy.
AmberOff2
Server blade power rails are on when Power switch is
toggled. Hardware drives power LED.
Steady GreenOff3
Server blade has powered up and is either at EFI, booting,
or at OS.
Steady greenSteady green4
The following list itemizes the steps that characterize basic platform boot flow:
1. Server blade power switch requests power from the Management Module (the microcontroller
that manages the enclosure power and cooling). Once the power is request is granted, server
blade power turns on. After the power sequence has completed successfully, BMC releases
system reset.
2. Initial processor firmware code fetch is Platform Abstraction Layer (PAL) code from FEPROM
in processor-dependent hardware (PDH), retrieved 4 bytes at a time by the data
multiplexer/demultiplexer controller (DMDC) in zx1. No shared memory or I/O devices are
available at this time. They are not initially configured.
3. Firmware code stack is initially in battery-backed RAM (BBRAM) in PDH, retrieved 4 byes at
a time, through the PDH and DMD buses.
94 Troubleshooting