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
Shared Remote Console is a licensed feature available with the purchase of optional licenses. For
more information, see “Licensing” (page 26).
Shared Remote Console and Forced Switch mode are disabled by default. You must enable and
configure these features through the browser, SMASH CLI (OEM), or RIBCL. All console sessions
are encrypted by authenticating the client first, and then the session leader decides whether to
allow the new connection.
The first user to initiate a Remote Console session connects to the server normally and is designated
as the session leader (session host.) Any subsequent user requesting Remote Console access initiates
an access request, requesting a satellite client connection, calling the session leader. A pop-up for
each satellite client request appears on the session leader's desktop, identifying the requester's
user name and DNS name (if available) or IP address.
Session hosts have the option to grant or deny access. A list of users and session host names
appears within the remote console browser frame. Satellite client sessions terminate when the
session host is terminated.
Shared sessions do not operate well with the Console Capture and replay features of iLO 2. If a
satellite session is viewing a captured session, during the playback time, the satellite session will
not receive session leader control messages. If the session host starts to view captured video data
during a shared session, the video appears on all satellite Remote Console sessions.
Using Console Capture
Console Capture is a Remote Console feature that enables you to record and replay a video stream
of events such as booting, ASR events, and sensed operating system faults. You can also manually
start and stop the recording of console video. Console Capture is only available through the iLO
2 user interface and cannot be accessed through XML scripting or the CLP. Console Capture is a
licensed feature available with the purchase of optional licenses. For more information, see
“Licensing” (page 26).
A buffer area is set aside in the management processor to store captured video data. This buffer
area is shared with the firmware update buffer, so any information captured is lost when you start
the firmware update process. You cannot capture video data during the firmware update process.
Buffer space is limited. Only one of each type of event is stored in the buffer area at a time. You
can transfer captured data buffers to a client running the IRC for replay. You can also configure
iLO 2 to automatically send captured video data to a web server on the same network as the iLO
2 when an event occurs. The web server must accept POST-method data transfers. You can select
Boot buffer only, Fault buffer, or combine them both as one large buffer to have more room to
capture Linux boot sequences.
Exported buffer data is given a unique name to easily identify the data for playback. Playback
requires a licensed iLO 2 on the network. Some operating systems (such as Linux) can fill the buffer
quickly. If you leave the system console in text mode, it helps maximize the amount of information
captured. Also, closing or reducing the number of active graphical console elements helps optimize
internal buffer space.
You can manually capture video of the server console using the IRC Record feature. All manually
captured data is stored in a local file on the client for later playback.
Using HP iLO Video Player
HP iLO Video Player enables you to playback iLO 2 console capture files without installing iLO 2
on your local system. iLO Video Player is designed as a typical media player with similar controls.
You can run iLO Video Player as a standalone application on either a server or client. Typically,
the application is located on the client. iLO 2 capture files are created using iLO 2 Console Capture
feature, see “Using Console Capture” (page 90).
To use iLO Video Player, you must have a Microsoft Windows 2000, Windows XP, or Windows
Vista operating systems, and Internet Explorer (version 7 or later) installed on your system.
90 Using iLO 2










