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
Windows EMS Console
The Windows EMS Console, if enabled, provides the ability to perform Emergency Management
Services in cases where video, device drivers, or other operating system features have prevented
normal operation and normal corrective actions from being performed.
iLO 2, however, enables you to use EMS over the network through a Web browser. Microsoft EMS
enables you to display running processes, change the priority of processes, and halt processes.
The EMS console and the iLO 2 Remote Console can be used at the same time.
The Windows EMS serial port must be enabled through the host system RBSU. The configuration
allows for the enabling or disabling of the EMS port, and the selection of the COM port. The iLO
2 system automatically detects whether the EMS port is enabled or disabled, and the selection of
the COM port.
To obtain the SAC> prompt, entering Enter might be required after connecting through the Virtual
Serial Port console.
For more information on using the EMS features, see the Windows Server 2003 documentation.
Virtual serial port raw mode
You can use the virtual serial port capability of iLO 2 to connect a Windows Kernel Debugger
from a remote client using WiLODbg.exe. WiLODbg.exe bypasses the decoding of bytes by the
iLO 2 firmware. After bypassing the decoding of bytes, the virtual serial port is in RAW mode
(unprocessed) and sent directly to the serial port.
The WiLODbg.exe utility is executed on a client system with the Microsoft application WinDBG.exe
or KD.exe installed. When you execute WiLODbg.exe, it establishes a virtual serial port connection
to iLO 2 and enables RAW mode. WiLODbg.exe also automatically launches WinDBG.exe with
the appropriate switches necessary for WinDBG.exe to connect to the remote iLO 2 device.
To configure the server, you must configure the System RBSU:
1. To enable a virtual serial port, assign Virtual Serial Port a COM port from the System Options
menu.
2. Set BIOS Serial Console Port and EMS Console to Disable, or set it to the same port as an
embedded serial port.
3. Set the Microsoft Windows debug port to the same port as the virtual serial port. You can use
the bootcfg command or modify the boot.ini file.
Example using the bootcfg command:
At the command prompt on a Windows server, issue the following command:
Bootcfg /debug on /port com2 /baud 115200 /id 1
Example of a modified boot.ini file:
[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows
Debug (com2)" /fastdetect /debug /debugport=com2 /baudrate=115200
If the server is configured to boot into debug mode, and a normal virtual serial port connection
is established while the server is booting, several bytes of debug data are sent to the virtual
serial port client. To avoid this, do not boot the server into debug mode while a normal virtual
serial port connection is in use.
102 Using iLO 2










