HP Integrated Lights-Out 2 User Guide
Table Of Contents
- HP Integrated Lights-Out 2 User Guide
- Contents
- 1 Overview
- 2 Setting up iLO 2
- 3 Configuring iLO 2
- iLO 2 configuration overview
- Upgrading iLO 2 firmware
- Licensing
- User administration
- Configuring iLO 2 access
- Security
- Network
- SNMP/Insight Manager settings
- ProLiant BL p-Class configuration
- 4 Using iLO 2
- System status and status summary information
- iLO 2 Remote Console
- Remote Console overview and licensing options
- Remote Console settings
- IRC Fullscreen
- Integrated Remote Console option
- Multi-user access to the Integrated Remote Console
- Using Console Capture
- Using HP iLO Video Player
- Acquiring the Remote Console
- Remote Console
- Text-based remote console overview
- Virtual media
- Power management
- ProLiant BL p-Class Advanced management
- ProLiant BladeSystem HP Onboard Administrator
- 5 Directory services
- Overview of directory integration
- Benefits of directory integration
- Advantages and disadvantages of schema-free directories and HP schema directory
- Setting up Schema-free directory integration
- Setting up HP schema directory integration
- Features supported by HP schema directory integration
- Setting up directory services
- Schema documentation
- Directory services support
- Schema required software
- Schema installer
- Management snap-in installer
- Directory services for Active Directory
- Active Directory installation prerequisites
- Installing Active Directory on Windows Server 2008
- Directory services preparation for Active Directory
- Snap-in installation and initialization for Active Directory
- Example: Creating and configuring directory objects for use with iLO 2 in Active Directory
- Directory services objects
- Active Directory Lights-Out management
- Directory services for eDirectory
- User login using directory services
- Directory-enabled remote management
- HPQLOMIG directory migration utility
- Introduction to HPQLOMIG utility
- Compatibility
- HP Lights-Out directory package
- Using HPQLOMIG
- Finding management processors
- Upgrading firmware on management processors
- Selecting a directory access method
- Naming management processors
- Configuring directories when HP Extended schema is selected
- Configuring directories when schema-free integration is selected
- Setting up management processors for directories
- Directory services schema
- 6 HP Systems Insight Manager integration
- 7 Troubleshooting iLO 2
- iLO 2 POST LED indicators
- Event log entries
- Hardware and software link-related issues
- JVM support
- Login issues
- Login name and password not accepted
- Directory user premature logout
- iLO 2 Management Port not accessible by name
- iLO 2 RBSU unavailable after iLO 2 and server reset
- Inability to access the login page
- Inability to access iLO 2 using Telnet
- Inability to access virtual media or graphical remote console
- Inability to connect to iLO 2 after changing network settings
- Inability to connect to the iLO 2 Diagnostic Port
- Inability to connect to the iLO 2 processor through the NIC
- Inability to log in to iLO 2 after installing the iLO 2 certificate
- Firewall issues
- Proxy server issues
- Two-factor authentication error
- Troubleshooting alert and trap issues
- Troubleshooting directory issues
- Troubleshooting Remote Console issues
- Remote Console applet has a red X when running Linux client browser
- Inability to navigate the single cursor of the Remote Console to corners of the Remote Console window
- Remote Console no longer opens on the existing browser session
- Remote console text window not updating properly
- Remote Console turns gray or black
- Remote Serial Console troubleshooting
- Troubleshooting Integrated Remote Console issues
- Internet Explorer 7 and a flickering remote console screen
- Configuring Apache to accept exported capture buffers
- No console replay while server is powered down
- Skipping information during boot and fault buffer playback
- Out of Memory error starting Integrated Remote Console
- Session leader does not receive connection request when IRC is in replay mode
- Keyboard LED does not display correctly
- Inactive IRC
- IRC Failed to connect to server error message
- IRC toolbar icons do not update
- GNOME interface does not lock
- Repeating keys on the Remote Console
- Remote Console playback does not work when the host server is powered off
- Troubleshooting SSH and Telnet issues
- Troubleshooting terminal services issues
- Troubleshooting video and monitor issues
- Troubleshooting Virtual Media issues
- Troubleshooting iLO Video Player issues
- Troubleshooting Remote Text Console issues
- Troubleshooting miscellaneous issues
- Cookie sharing between browser instances and iLO 2
- Inability to access ActiveX downloads
- Inability to get SNMP information from HP SIM
- Incorrect time or date of the entries in the event log
- Inability to upgrade iLO 2 firmware
- iLO 2 network flash recovery
- Recovering from a bad iLO 2 flash image using network flash recovery
- Recovering from a bad iLO 2 flash image using the HP Smart Update Firmware DVD
- The iLO 2 firmware does not respond to SSL requests
- Testing SSL
- Resetting iLO 2
- Server name still present after ERASE utility is executed
- Troubleshooting a remote host
- 8 Technical support
- Acronyms and abbreviations
- Index

After the server completes POST, the server system ROM transfers control to the operating system
boot loader. If you are using Linux, you can configure the operating system boot loader to interact
with the server serial port instead of the keyboard, mouse, and VGA console. This configuration
enables you to view and interact with the operating system boot sequence through the Remote
Serial console. For an example of a Linux operating system boot loader, see “Linux configuration
example” (page 101).
After the operating system boot loader completes, the operating system continues to load. If you
are using a Linux operating system, you can configure the operating system to provide a login
session to the system through the serial port, enabling the Remote Serial Console to prompt you
for the system user login ID and password. Using this configuration enables you to interact with
the operating system as an operating system user or as a system administrator.
Although additional configuration steps are required to use Remote Serial Console (as compared
to using the remote console or IRC), the Remote Serial Console allows Telnet or SSH users to interact
with the server remotely and without requiring an iLO 2 Advanced license and is the only way a
true text-based remote console is presented by iLO 2.
Linux configuration example
The boot loader is the application that loads from the bootable device when the server system
ROM finishes POST. For Linux operating systems, the boot loader that is usually used is GRUB. To
configure GRUB to use the Remote Serial Console, modify the GRUB configuration file to look like
the following (Red Hat Linux 7.2 sample shown):
serial -unit=0 -speed=115200
terminal -timeout=10 serial console
default=0
timeout=10
#splashimage=(hd0,2) /grub/splash.zpm.gz
title Red Hat Linux (2.4.18-4smp)
root (hd0,2)
kernel /vmlinuz-2.4.18-4smp ro root=/dev/sda9 console=tty0 console=ttyS0,115200
initrd /initrd-2.4.18-rsmp.img
After Linux is fully booted, a login console can be redirected to the serial port. The /dev/ttyS0
and /dev/ttyS1 devices, if configured, enable you to obtain serial tty sessions through the
Remote Serial Console. To begin a shell session on a configured serial port, add the following line
to the /etc/inittab file to start the login process automatically during system boot (this example
invokes the login console on /dev/ttyS0):
Sx:2345:respawn:/sbin/agetty 115200 ttyS0 vt100
For more information about configuring Linux for use with the Remote Serial Console, see the
technical publication Integrated Lights-Out Virtual Serial Port configuration and operation HOWTO
on the HP website at http://www.hp.com/servers/lights-out.
Virtual Serial Port enhancements
iLO 2 firmware 1.35 implements a dynamic flag that instantly informs the server system ROM of
an iLO 2 Remote Serial Console connection. After the system ROM POST code recognizes the
Remote Serial Console connection, the system begins redirecting the console input and output to
the server serial port and the Remote Serial Console. You can establish a Remote Serial Console
session at any time before or during the system POST sequence, and you can view and modify
the POST. After disconnecting the Remote Serial Console session, the iLO 2 firmware resets the
dynamic flag to inform the server system ROM that the session is no longer active. Then, the server
system ROM cancels the redirection to the server serial port.
The system ROM RBSU setup must be configured to use iLO 2 Virtual Serial Port for this enhancement
to be operational. For more information, see “Configuring Remote Serial Console” (page 100).
iLO 2 Remote Console 101










