HP AB500A - Integrated Lights-Out Advanced User manual

Abstract.............................................................................................................................................. 3
Integrated Lights-Out technology: Enhancing
the manageability of HP ProLiant Servers
technology brief, 7th edition
Introduction......................................................................................................................................... 3
Naming conventions and capabilities .................................................................................................... 3
Integrated Lights-Out architecture ........................................................................................................... 4
Firmware levels and upgrades ........................................................................................................... 4
Management processor overview....................................................................................................... 5
Integrated Lights-Out technologies.......................................................................................................... 7
Remote Console technologies ............................................................................................................ 7
Text-based remote console with first-generation iLO .......................................................................... 7
Text-based remote console with iLO 2 ............................................................................................. 7
Virtual Serial Port/Remote Serial Console........................................................................................ 8
Integrated Remote Console ............................................................................................................ 9
Console capture and replay........................................................................................................... 9
Shared remote console................................................................................................................ 10
Terminal Services ....................................................................................................................... 11
Virtual media................................................................................................................................. 11
Virtual folders ................................................................................................................................ 12
Web-based or scriptable virtual media ............................................................................................. 12
Power Management Capabilities......................................................................................................... 13
Virtual power control ...................................................................................................................... 13
Managing server power ................................................................................................................. 13
HP Power Regulator.................................................................................................................... 13
Power Meter .............................................................................................................................. 14
HP Power Capping..................................................................................................................... 14
HP Dynamic Power Capping ....................................................................................................... 15
Sensors and fan control .................................................................................................................. 16
Security ............................................................................................................................................ 16
Authorization and authentication ..................................................................................................... 17
Two-factor authentication............................................................................................................. 17
Directory services ....................................................................................................................... 17
Data encryption ............................................................................................................................. 18
SSL Certificate Import.................................................................................................................. 18
Data integrity................................................................................................................................. 18
Event generation for failed login attempts.......................................................................................... 19
Integration with other management tools .............................................................................................. 19
HP Systems Insight Manager ........................................................................................................... 19
SNMP....................................................................................................................................... 19
Discovery of management processors ........................................................................................... 19

Power monitor............................................................................................................................ 20
Single sign-on from HP SIM to iLO................................................................................................ 20
Integration with deployment tools..................................................................................................... 20
Standards-based management......................................................................................................... 21
Accessing and configuring iLO............................................................................................................ 21
Methods to access iLO.................................................................................................................... 21
Configuring iLO ............................................................................................................................. 22
Conclusion........................................................................................................................................ 22
For more information.......................................................................................................................... 23
Call to action .................................................................................................................................... 24

3
Abstract
HP Integrated Lights-Out is an autonomous management subsystem residing on select HP ProLiant and
BladeSystem server platforms. It provides system administrators with secure remote management
capabilities, regardless of server status or location. This technology brief discusses the architecture of
Integrated Lights-Out processors. It also describes key technologies that provide comprehensive
remote management capabilities.
Additional papers about Integrated Lights-Out technology are available from the HP website at
www.hp.com/servers/technology. The final section of this brief titled “For more information” includes
references to specific Integrated Lights-Out web pages and other related material.
Introduction
The globalization of business and proliferation of industry-standard servers have made it impractical
to administer servers locally. To meet increasing demands for IT efficiency and responsiveness, the
need for remote management is critical, especially in corporate data centers. Integrated Lights-Out
(iLO) technology provides hardware-based system management capabilities that enable IT
administrators to control HP ProLiant and BladeSystem servers remotely.
Because iLO is integrated into the server platform, it can provide alerts, server status, power
information, and remote control, regardless of the state of the operating system (OS) or the host
server. Administrators can manage HP ProLiant and BladeSystem servers remotely through their entire
life cycle (initial deployment, operation, and redeployment). Software and firmware can be updated
over the network, and OS or server problems can be diagnosed remotely. The technology within iLO
provides administrators with multiple options for accessing and managing their servers.
Naming conventions and capabilities
Integrated Lights-Out 2 (iLO 2) is the fourth generation in the HP product line for Lights-Out
management and builds on the successful first-generation iLO management processor. In this
technology brief, the iLO designation refers to the general technology or functionality available with
both products: first-generation iLO and iLO 2. A designation of first-generation iLO or iLO 2 indicates
that the functionality is exclusive to that product.
This brief discusses the capabilities supported in the iLO architecture. Some capabilities are supported
by the iLO architecture but are only enabled with iLO Advanced for BladeSystem or iLO Advanced
licensing keys. To determine which capabilities are supported in each of these licensing options, refer
to the HP website www.hp.com/servers/ilo.

4
Integrated Lights-Out architecture
The iLO architecture consists of an independent firmware-based operating environment and a
management processor. The management processor resides on the system board, using auxiliary
power and operating independently of the host processor and the OS. This independence means that
iLO has the following characteristics:
•Fully operational during a shut-down and reboot of the server because it does not depend on host
server power
•Not dependent on the host processor for operation and does not use any processing cycles of the
host processor
•Autonomous from the server hardware. Any problems occurring with the server hardware are
isolated from the iLO processor
•Available for out-of-band management without assistance from the OS
Firmware levels and upgrades
The firmware can provide two levels of functionality—Standard and Advanced—depending on which
level is enabled with licensing keys.
iLO Standard functionality includes basic system management functions such as the ability to power
on and off the host server remotely, to access server status and diagnostics such as the Integrated
Management Log, and to access system alerts such as SNMP traps. Because ProLiant BL servers are
designed to be managed remotely, iLO Standard Blade Edition offers additional management and
Lights-Out control features that are essential for headless environments. iLO Advanced for
BladeSystem is designed for select environments such as HP BladeSystem or Linux® networks. iLO
Advanced for BladeSystem supports more advanced capabilities such as virtual power control, virtual
media, and other sophisticated security features. It activates the complete suite of remote management
capabilities for ProLiant BL-based environments. The iLO Advanced Pack, on the other hand, provides
the complete suite of remote management capabilities for ProLiant ML-, DL- and SL-based
environments.
Because HP continually upgrades Lights-Out firmware with additional capabilities, and because server
capabilities may differ, administrators should refer to the HP website at www.hp.com/servers/ilo for
more information. Details are also available by logging in to the iLO or iLO 2 processor, navigating
to the licensing page, and selecting the Help button.
Regardless of the iLO firmware level, administrators can upgrade the firmware by means of a flash
ROM in the management processor. Refer to the iLO User Guide for the most current version of
firmware. Features discussed in this brief require that firmware version as a baseline. The firmware
can be updated in several ways, so administrators can select the method that best suits their data
center environment. After administrators obtain the most recent firmware from the HP website, they
can flash the ROM using one of the following resources:
•iLO web page
•Online ROM Flash Component from the operating system
•Bootable CD-ROM such as the firmware update CD
•Scripting tools such as RIBCL/HPONCFG/CPQLOCFG1over the network or from the host OS
•Command-line interface over telnet/SSH
Firmware updates are backward-compatible, meaning the latest firmware supports previous platforms
with a compatible iLO processor; updates also include enhancements and bug fixes.
1See the HP Integrated Lights-Out Management Processor Scripting and Command Line Resource Guide,
available at http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00294268/c00294268.pdf

Management processor overview
As indicated in Figure 1, the iLO 2 management processor includes the following chip architecture:
•66-MHz RISC processor core with separate instruction set and integrated data cache
•Memory controller
•4 megabytes (MB) of flash ROM
•16 megabytes of memory (SDRAM)
•24-MHz digital video redirection engine
•Dedicated 10/100 or at host NIC speed
Like the first-generation iLO processor, iLO 2 is a 32-bit, PCI-based processor. iLO 2 improvements
include more memory and a new digital video redirection (DVR) engine. The aspects discussed in the
following paragraphs apply to both first-generation iLO and the iLO 2 device.
The NIC and associated RJ-45 management (Mgmt) port are independent of the 10/100/1000
Ethernet interface(s) provided by the host server.
Figure 1. This block diagram shows the configuration of the HP iLO 2 management processor. It is based on thel
iLO processor, and adds enhancements including more memory and an updated digital video redirection.
RJ-45
Ethernet
Management
Port
5

Selected servers offer a Shared Network Port (SNP) that allows network access to both iLO and the
host server through a single network port (see Figure 2), rather than dedicating a second port to the
management processor. An SNP allows HP ProLiant servers to deliver optimal performance with fewer
required ports, which can reduce recurring port use costs. With the SNP, iLO network traffic can be
routed through a sideband connection on one of the NIC interfaces. Although the iLO traffic shares a
port with the server OS traffic, both iLO and the server NIC have their own Media Access Control
(MAC) address. Having separate MAC addresses lets iLO and the server have separate Internet
Protocol (IP) addresses. For increased security and network consolidation, administrators can use
optional virtual LAN (vLAN) tagging with manageable network switches to segregate iLO and host
traffic, creating separate logical networks for host and management traffic. Using the SNP also
simplifies hardware installation and reduces overall hardware costs because both corporate and iLO
network traffic comes through the system NIC.
Figure 2. These diagrams illustrate three possible port configurations for system management traffic.
The iLO processor provides logic functions that monitor and control the host server. This logic
implements Automatic Server Recovery-2 (ASR-2), which reboots the server automatically after
recoverable faults and before imminent failures. Additional monitoring and control capabilities have
expanded over time. For servers that support system-embedded health monitoring, the iLO 2 processor
can monitor fans, power supplies, and temperatures. Server documentation for specific servers
provides sensor and temperature information available through the Lights-Out processor.
The host firewall and bridge logic let the embedded processor control the flow of information between
the host server and the management console. It protects against unauthorized access through the
system PCI interface, and it shields sensitive information that may be stored in the memory or
firmware. For additional information about host firewall and bridge logic, refer to the “HP Integrated
Lights-Out security” technology brief at this URL:
http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c00212796/c00212796.pdf.
Essentially, host power and fault isolation logic split the management processor into two separate
areas: one operating under normal host system power; the other connected to the auxiliary power
plane of the server. Even when the host server is powered down, the iLO processor will continue to
operate, although the portions of iLO that communicate with the host processor are isolated. If the
host server has redundant power supplies, power redundancy protects both the iLO processor and the
host processor if a power supply fails.
6

7
Host power and fault isolation logic monitors the host system for any unexpected behavior such as a
system power fault or PCI bus fault. The iLO management processor records power faults and
operates normally on auxiliary power to provide key functions such as web browser access, alerting,
and access to event logs. The host power and fault isolation logic allows either the management
processor or the host processor to reset independently of the other. Server resets have no effect on the
iLO processor; it provides administrators with continuous access to the server, which means that they
can upgrade the iLO firmware without resetting or affecting the host server.
Integrated Lights-Out technologies
Through key iLO technologies such as remote console, virtual media, virtual power, and virtual serial
port, system administrators can control iLO-managed servers efficiently from a remote location.
Administrators can deploy new servers, install patches and hot-fixes, perform routine maintenance
tasks, or troubleshoot platform issues from any remote location.
Remote Console technologies
Having full access to the host server using remote console technologies is one of the most important
reasons to use an iLO processor. Remote console technologies provide system administrators with
access to the managed server at any time, even before the OS is installed and if the OS is not
functioning. For example, being able to see the host server console on the management client allows
administrators to watch the entire boot process remotely.
Remote console technologies include a text-based console, a Java-based graphical console, and a
Microsoft® ActiveX™-based graphical console. First-generation iLO and iLO 2 differ in the way that
they capture text-based and graphical data; therefore, the following sections describe each method.
Additional remote console technologies include screen capture and replay capabilities, a shared
remote console, and Terminal Services integration.
Text-based remote console with first-generation iLO
The first-generation iLO processor supports a text-based remote console. iLO monitors the screen
frame buffer through the PCI bus. When it detects changes in the text information, iLO captures,
encrypts, and transmits the data—including screen positioning information—to text-based client
applications. The advantages of this method are compatibility with standard text-based clients, good
performance, and simplicity. Disadvantages include the inability to display non-ASCII or graphical
information, and the possibility that screen positioning information (displayed characters) might be
sent out-of-order.
System administrators can use the text-based remote console to view the managed server and interact
with the Option ROM setup menus during POST. For ProLiant ML, DL, and SL servers, administrators
must have a license key to access the remote console after the OS loads and goes into graphical
mode.
Text-based remote console with iLO 2
The iLO 2 management processor has a DVR engine that uses the digital video output (DVO) port of
the video adapter to directly access video output for high performance video monitoring. This method
significantly increases iLO 2 graphical console performance. However, the available digital video
stream represents graphical data (pixels); therefore, it does not provide a true text-based (ASCII
characters) console. This video data cannot be rendered by a text-based application such as a telnet
or Secure Shell (SSH) client.
The redirection of text during the server boot process is available as an iLO Standard feature on iLO 2
systems through the end of POST. Redirection of either text or graphics with iLO 2 after POST requires

8
an iLO Advanced license for ProLiant ML, DL and SL-systems, but that functionality is included with the
iLO Blade Standard package for ProLiant BL systems.
Administrators can access the iLO Virtual Serial Port using Remote Serial Console in the iLO 2
firmware. They can use the iLO Virtual Serial Port for text console access during POST and OS
operation. The iLO processor contains hardware that can replace the physical serial port on the
server's motherboard, and the iLO firmware provides a Java applet that connects to the server serial
port. If the serial redirection feature is enabled on the host server, iLO intercepts the data coming from
the serial port, encrypts it, and sends it to the Remote Serial Console applet or another application
such as a telnet or SSH client. The iLO 2 Remote Serial Console applet appears as a text-based
console, but the information is rendered using graphical video data.
Access to the iLO 2 Remote Serial Console is a standard feature and does not require a license key.
Virtual Serial Port/Remote Serial Console
Some operating systems, such as Microsoft® Windows® Server 2008 and Linux, provide text-based
access to the server from the host server serial port. An administrator can connect a terminal to the
serial port of the host server and perform basic management tasks. For example, if it is enabled, the
Windows EMS Console displays the processes that are running and allows administrators to halt
processes. This capability can be important in cases where video, device drivers, or other OS features
have prevented normal operation and normal corrective actions.
An administrator can remotely access a console application, such as Windows EMS over the network
using the iLO virtual serial port. As described in the previous section, the iLO management processor
contains the functional equivalent of the standard serial port (16550 UART) register set, and the iLO
firmware provides a Java applet that connects to the serial port. If the serial redirection feature is
enabled on the host server,2iLO intercepts the data coming from the serial port, encrypts it, and
sends it to the web browser applet or telnet application.
For Linux users, the iLO virtual serial port feature provides an important function for remote access to
the Linux server. An administrator can configure a Linux login process attached to the serial port, and
then use the iLO virtual serial port to remotely login to the Linux operating system over the
management network.
Additional details about using the Virtual Serial Port are available in the document titled “Integrated
Lights-Out Virtual Serial Port configuration and operation.” This is available at:
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00263709/c00263709.pdf
Digital Video Redirection (DVR) engine operation
The iLO first generation processor acquired management console video by monitoring the PCI bus for
data sent to the video controller. In-band video monitoring is simple, cost effective, and adequate for
emergency or part-time management console operation. As administrators began using iLO remote
console for routine operations in addition to emergency management, improved video monitoring
became necessary. The iLO 2 management processor uses a DVR engine for video capture. The DVR
engine includes a video capture buffer (Figure 3) that monitors the Digital Video Output (DVO) of the
host video controller (not the PCI bus). The DVR engine captures the screen image one stripe at a time.
2Linux users must also set up a login shell to the serial port (TTYS0) and configure the host server to allow root
access.

Figure 3. This diagram represents an overview of how the iLO 2 digital video redirection (DVR) engine operates.
An encoding process uses video characteristics such as changed/unchanged data and
repetition/alternation for efficient video compression. Before it is sent over the network to the remote
console, the video is encrypted and packetized. Either a Java or an ActiveX application on the client
decodes and displays the data. With most of the video processing off-loaded from the management
processor, overall performance substantially increases. Video refresh rates for the monitored video
increase from a previous iLO average of 0.32 frames per second to over 6 frames per second.
Operational bandwidth bottlenecks are reduced and the client system acts as the remote console.
Virtually all browser types support the Java-based remote console applet. HP refers to this functionality
as Virtual KVM. Because of the high-performance DVR engine, administrators can rely on the iLO DVR
for remote console operation. This reduces the need for KVM over IP solutions and the associated
hardware.
Integrated Remote Console
The iLO 2 Integrated Remote Console combines the remote control capabilities of iLO—virtual KVM
plus server power control and virtual media—into a single user interface. The Integrated Remote
Console uses an ActiveX client application for the graphical remote console. The ActiveX client
provides native operation in a Windows environment, as compared to the interpretive mode that the
Virtual KVM application must run in a Java virtual machine. Thus, the Integrated Remote Console can
provide better performance than the Java-based remote console. The DVR engine operation remains
the same, regardless of which console an administrator uses. Additional iLO 2 capabilities, such as
console capture/reply, shared remote console, and virtual folders, are also available through the
Integrated Remote Console.
Console capture and replay
Using console capture, administrators can record and replay a video stream of events such as the last
boot sequence, ASR-2 events, and OS faults. Administrators can manually start and stop the video
capture so that any action an administrator takes using the remote console can be recorded.
9

The iLO 2 processor stores captured video data in an internal buffer area for boot sequences and for
ASR-2 and OS faults. With additional configuration, iLO 2 can export the captured data to an
external file after the buffer fills. The external file is stored on a web server on the network. The iLO 2
processor continues to export captured files to the specified web server every time there is a reboot or
an OS failure, as long as space is available. These files, each typically 2- to 3-MB, include a time
stamp and an indicator of which type of data they contain. If administrators manually run the capture
function, the data is stored on the client machine. Files created in this manner can be of any size.
Administrators can view the exported video capture files using the Integrated Remote Console
application as well as a stand-alone tool for Windows called the HP iLO Video Player available for
download from www.hp.com/support/ilo2.
Shared remote console
iLO 2 supports sharing a remote console session with up to four users, including the session leader.
The administrator who initiates a remote console session connects to the host server normally and is
designated the session leader. When another administrator tries to connect to the iLO 2 processor in
a second remote console session, the iLO 2 processor transmits the IP address of the session leader
computer back to the new client session. Thus, subsequent shared remote consoles become satellite
clients in a peer-to-peer configuration, as illustrated in Figure 4.
Figure 4. This diagram represents a host server and a remote server console session. The first user in a shared
remote console session becomes the session leader, while up to three others are satellite clients in a peer-to-peer
configuration.
For each satellite client request, a pop-up window appears on the session leader’s desktop,
identifying the requester’s user name and DNS name (if available) or IP address. All console sessions
are encrypted through client authentication first, and then the session leader decides whether or not to
allow the new connection to the remote console session. The session leader controls the remote
console session. All satellite client sessions terminate when the session leader terminates the session.
The shared remote console allows administrators at multiple locations to collaborate on
troubleshooting or maintaining the remote server for greater IT efficiency and system availability.
10