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

Using bulk import tools
Adding and configuring large numbers of LOM objects is time consuming. HP provides several
utilities to assist in these tasks.
• HP Lights-Out Migration utility
The HP Lights-Out Migration utility, HPQLOMIG.EXE, imports and configures multiple LOM
devices. HPQLOMIG.EXE includes a GUI that provides a step-by-step approach to implementing
or upgrading large numbers of management processors. HP recommends using this GUI
method when upgrading numerous management processors. For more information, see
“HPQLOMIG directory migration utility” (page 162).
• HP Lights-Out Migration Command utility
The HP Lights-Out Migration Command utility, HPQLOMGC.EXE, offers a command-line
approach to migration, rather than a GUI-based approach. This utility works in conjunction
with the Application Launch and query features of HP SIM to configure many devices at a
time. Customers that must configure only a few LOM devices to use directory services might
also prefer the command-line approach. For more information, see “HPQLOMIG directory
migration utility” (page 162).
• HP SIM utilities:
Manage multiple LOM devices.◦
◦ Discover the LOM devices as management processors using CPQLOCFG to send a RIBCL
XML script file to a group of LOM devices to manage those LOM devices. The LOM
devices perform the actions designated by the RIBCL file and send a response to the
CPQLOCFG log file. For more information, see the HP Integrated Lights-Out Management
Processor Scripting and Command Line Resource Guide at http://h20000.www2.hp.com/
bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManual&lang=en&
cc=us&docIndexId=64179&taskId=135&prodTypeId=18964&prodSeriesId=1146658.
• Traditional import utilities
Administrators familiar with tools such as LDIFDE or the NDS Import/Export Wizard can use
these utilities to import or create many LOM device objects in the directory. However,
administrators must still configure the devices manually, as described previously, but can do
so at any time. Programmatic or scripting interfaces can also be used to create the LOM device
objects in the same way as users or other objects. For details on attributes and attribute data
formats when creating LOM objects, see “Directory services schema” (page 171).
HPQLOMIG directory migration utility
Introduction to HPQLOMIG utility
The HPQLOMIG utility is for customers with previously installed management processors who want
to simplify the migration of these processors to management by directories. HPQLOMIG automates
some of the migration steps necessary for the management processors to support Directory Services.
HPQLOMIG can do the following:
• Discover management processors on the network.
• Upgrade the management processor firmware to the version that supports Directory Services
or schema-free directories.
• Name the management processors to identify them in the directory.
• Create objects in the directory corresponding to each management processor and associate
them to a role.
• Configure the management processors to enable them to communicate with the directory.
162 Directory services










