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
iLO 2 RBSU unavailable after iLO 2 and server reset
If the iLO 2 processor is reset and the server is immediately reset, there is a small chance that the
iLO 2 firmware will not be fully initialized when the server performs its initialization and attempts
to invoke the iLO 2 RBSU. In this case, the iLO 2 RBSU is unavailable or the iLO 2 Option ROM
code is skipped altogether. If this situation occurs, reset the server a second time. To avoid this
issue, wait a few seconds before resetting the server after resetting the iLO 2 processor.
Inability to access the login page
If you cannot access the login page, you must verify the SSL encryption level of your browser is
set to 128 bits. The SSL encryption level in iLO 2 is set to 128 bits and cannot be changed. The
browser and iLO 2 encryption levels must be the same.
Inability to access iLO 2 using Telnet
If you cannot access iLO 2 using Telnet, you must verify the Remote Console Port Configuration
and Remote Console Data Encryption on the Global Settings screen. If Remote Console Port
Configuration is set to Automatic, the Remote Console applet enables port 23, starts a session,
and then closes port 23 when the session is completed. Telnet cannot automatically enable port
23, so it fails.
Inability to access virtual media or graphical remote console
Virtual media and graphical Remote Console are only enabled by licensing the optional iLO
Advanced Pack. A message appears, informing the user that the features are not available without
a license. Although up to 10 users are allowed to log in to iLO 2, only one user can access the
remote console. A warning message appears indicating that the Remote Console is already in use.
Inability to connect to iLO 2 after changing network settings
Verify that both sides of the connection, the NIC and the switch, have the same settings for
transceiver speed autoselect, speed, and duplex. For example, if one side is autoselecting the
connection, then the other side must as well. The settings for the iLO 2 NIC are controlled in the
Network Settings screen.
Inability to connect to the iLO 2 Diagnostic Port
If you cannot connect to the iLO 2 Diagnostic Port through the NIC, be aware of the following:
• The use of the diagnostic port is automatically sensed when an active network cable is plugged
in to it. When switching between the diagnostic and back ports, allow one minute for the
network switchover to be complete before attempting to connect through the web browser.
• If a critical activity is in progress, the diagnostic port cannot be used until the critical activity
is complete. Critical activities include the following:
— Firmware upgrade
— Remote Console session
— SSL initialization
• If you are using a client workstation that contains more than one enabled NIC, such as a
wireless card and a network card, a routing issue might prevent you from accessing the
diagnostic port. To resolve this issue:
188 Troubleshooting iLO 2