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
If the mouse still fails to operate correctly, or if this situation occurs frequently, verify that your
mouse settings match those recommended in “Optimizing mouse performance for Remote Console
or Integrated Remote Console” (page 88).
Remote Console no longer opens on the existing browser session
With the addition of the Terminal Services passthrough function, the behavior of the Remote Console
applet is slightly different from previous versions of iLO 2 firmware. If a Remote Console session
is already open and the Remote Console link is clicked again, then the Remote Console session
does not restart. The Remote Console session might appear frozen.
For example, if the following steps are executed:
1. From Client-1, log in to iLO 2 and open a remote console session.
2. From Client-2, log in to iLO 2 and try to open a Remote Console session. The following message
displays:
Remote console is already opened by another session
This is expected because only one Remote Console session is supported at a time.
3. Return to Client-1 and close the Remote Console session.
4. From Client-2, click the Remote Console link with the old Remote Console applet still open.
The remote console session does not refresh and the old message discussed in step 2 is still
displayed.
Although this behavior is different than in previous versions of iLO firmware, this is expected
behavior in this version of the iLO firmware. To avoid issues of this nature, always close an open
remote console session prior to trying to reopen it.
Remote console text window not updating properly
When using the Remote Console to display text windows that scroll at a high rate of speed, the
text window might not update properly. This error is caused by video updates occurring quicker
than the iLO 2 firmware can detect and display them. Typically, only the upper left corner of the
text window updates while the rest of the text window remains static. After the scrolling is complete,
click Refresh to properly update the text window.
One known example of this issue is during the Linux booting and posting process, in which some
of the POST messages can be lost. A possible result is that a keyboard response is requested by
the boot process and might be missed. To avoid this issue, the booting and posting process must
be slowed down by editing the Linux startup script to allow more time for keyboard responses.
Remote Console turns gray or black
The Remote Console screen turns gray or black when the server is rebooted from the Terminal
Services client. The screen remains gray or black for 30 seconds to one minute. The client closes
because the Terminal Services server is not available. The iLO 2 remote console takes over, but
the Remote Console screen turns gray or black. When the screen returns, the Remote Console
functions normally.
Remote Serial Console troubleshooting
The Remote Serial Console option relies on the Virtual Serial Port. The Virtual Serial Port must be
correctly enabled and configured in the host RBSU. You can access the Virtual Serial Port using
SSH or Telnet (if enabled). You can access the CLP from a host serial session if the UART and
Virtual Serial Port share the same settings. To access the CLP from a host serial session enter Esc-(
(escape left-parentheses) to switch to the command-line interpreter.
Pop-up blocking applications will prevent the Remote Serial Console option from running. Disable
any pop-up blocking programs before starting the Remote Serial Console option.
Troubleshooting Remote Console issues 193










