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
3389. All data received from Terminal Services on this port is forwarded to the server and all data
Terminal Services receives from the server is forwarded back to the socket. The iLO 2 firmware
reads anything received on this port as an RDP packet. RDP packets are exchanged between the
iLO 2 firmware and the server Terminal Services (RDP) server through the local host address on
the server. The service provided facilitates communications between the iLO 2 firmware and the
RDP server. The RDP server interprets the service as an established external RDP connection. For
more information on RDP services, see “Windows RDP Passthrough service” (page 35).
A Terminal Services session provides a performance-enhanced view of the host system console.
When the operating system is unavailable (or the Terminal Services server or client is unavailable),
the traditional iLO 2 Remote Console provides a view of the host system console. For more
information on Remote Console and Terminal Services, see “Remote Console and Terminal Services
clients” (page 37).
To configure the Terminal Services Passthrough option, see the “Terminal Services client
requirements” (page 35) and “Terminal Services Passthrough installation” (page 36).
Terminal Services client requirements
The Terminal Services client is available on Microsoft Windows client machines running:
• Windows Server 2003
On Windows Server 2003 servers, the Terminal Services client and RDP connection is built-in.
The client is part of the operating system and is activated using Remote Desktop sharing. To
activate desktop sharing, select My Computer>Properties>Remote>Remote Desktop. The
Terminal Services client in Windows Server 2003 provides command-line options and seamless
launches from the Remote Console applet.
• Windows Server 2008
On Windows Server 2008 servers, the Terminal Services client and RDP connection is built-in.
The client is part of the operating system and is activated using Remote Desktop sharing. To
activate desktop sharing, select My Computer>Properties>Remote>Remote Desktop. The
Terminal Services client in Windows Server 2008 provides command-line options and seamless
launches from the Remote Console applet.
• Windows XP
On Windows XP servers, the Terminal Services client and RDP connection is built in. The client
is part of the operating system and is activated using Remote Desktop sharing. To activate
desktop sharing, select Start>Programs>Accessories>Communications>Remote Desktop. The
Terminal Services client in Windows XP provides command-line options and launches from
the remote console applet.
Windows RDP Passthrough service
To use the iLO 2 Terminal Services Passthrough feature, you must install a passthrough service on
the host system. This service displays the name of the iLO 2 Proxy in the host list of available
services. The service utilizes Microsoft .NET framework security and reliability. After the service is
started, the service polls iLO 2 to detect if an RDP connection with the client is established. If an
RDP connection with the client is established, the service establishes a TCP connection with local
host and begins exchanging packets. The port used to communicate with the local host is read
from the Windows registry at:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\
Wds\rdpwd\Tds\tcp\PortNumber
The port is typically port 3389.
Configuring iLO 2 access 35










