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
is available or active. This is normal behavior, but it is different than the behavior observed when
both Terminal Services sessions are established by Windows administrators. In that case, the
warning message is received by the first Terminal Services session immediately.
Terminal Services Passthrough option display
The iLO 2 firmware might not accurately display the Terminal Services Passthrough option. The
Terminal Services Passthrough option might appear active even if the operating system is not
Terminal Services enabled (for example, if the host operating system is Linux, which does not
support Terminal Services operation).
Remote Console and Terminal Services clients
Using the management network connection to the iLO 2, an iLO 2 Remote Console session can
be used to display a Terminal Services session to the host. When the iLO 2 Remote Console applet
runs, it launches the Terminal Services client based on user preference. The Sun JVM must be
installed to obtain full functionality of this feature. If the Sun JVM is not installed, then the Remote
Console cannot automatically launch the Terminal Services client.
If Terminal Services passthrough is enabled, and the Terminal Services server is available, switching
between iLO 2 Remote Console and the Terminal Services client will be seamless as the server
progresses from pre-operating system environment to operating system-running environment, to
operating system-not available environment. The seamless operation is available as long as the
Terminal Services client is not started before Remote Console is available. If Remote Console is
available and the Terminal Services client is available, Remote Console will start the Terminal
Services client when appropriate.
When using the Terminal Services passthrough option with Windows Server 2003 and Windows
Server 2008, a 30-second delay occurs after the CTRL-ALT-DEL dialog box appears before the
Terminal Services client launches. The 30-second delay represents how long it takes for the service
to connect to the RDP client running on the server. If the server is rebooted from the Terminal Services
client, the Remote Console screen turns grey or black for up to one minute while iLO 2 determines
that the Terminal Services server is no longer available.
If Terminal Services mode is set to Enabled, but you want to use the Remote Console, then launch
the Terminal Services client directly from the Terminal Services client menu. Launching directly from
the client menu enables simultaneous use of the Terminal Services client and the Remote Console.
Terminal Services can be disabled or enabled at any time. Changing the Terminal Services
configuration causes the iLO 2 firmware to reset. Resetting the iLO 2 firmware interrupts any open
connections to iLO 2.
When the Terminal Services client is launched by the Remote Console, Remote Console goes into
a sleep mode to avoid consuming CPU bandwidth. Remote Console still listens to the Remote
Console default port 23 for any commands from iLO 2.
The iLO 2 firmware passes through only one Terminal Services connection at a time. Terminal
Services has a limit of two concurrent sessions.
The Remote Console activates and becomes available if the Remote Console is in sleep mode and
the Terminal Services client is interrupted by any of the following events:
• The Terminal Services client is closed by the user.
• The Windows operating system is shut down.
• The Windows operating system locks up.
Terminal Services troubleshooting
To resolve issues with iLO 2 Terminal Services Passthrough:
Configuring iLO 2 access 37










