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

NOTE: If autosense is disabled, the network switch must match the iLO 2 settings to prevent
iLO 2 access issues.
You are not permitted to modify the NIC speed settings and autosense options on blade
servers. These settings are auto negotiated between iLO 2 and the Onboard Administrator.
iLO 2 subsystem name limitations
The iLO 2 subsystem name represents the DNS name of the iLO 2 subsystem. For example, ilo
instead of ilo.hp.com. This name can only be used, if DHCP and DNS are configured properly
to connect to the iLO 2 subsystem name instead of the IP address.
• Name service limitations – The subsystem name is used as part of the DNS name and WINS
name. However DNS and WINS limitations differ:
— DNS allows alphanumeric and hyphen. WINS allows alphanumeric, hyphen and
underscore.
— WINS subsystem names are truncated at 15 characters, DNS are not.
If you require underscores, they can be entered in RBSU or using the iLO 2 scripting utility.
NOTE: Name service limitations also apply to the domain name.
To avoid name space issues:
◦ Do not use the underscore character.
◦ Limit subsystem names to 15 characters.
◦ Verify you can ping iLO by IP address and by DNS/WINS name.
◦ Verify NSLOOKUP correctly resolves the iLO network address and that there are no
namespace conflicts.
◦ Verify DNS and WINS both correctly resolve the name (if you are using both).
◦ Flush the DNS name if you make any name space changes.
iLO 2 Shared Network Port
The iLO 2 Shared Network Port enables you to choose either the system NIC or dedicated iLO 2
Dedicated Management NIC for server management. When you enable the iLO 2 Shared Network
Port, both regular network traffic, and network traffic intended for iLO 2 pass through the system
NIC.
iLO 2 provides support for servers that might not have an iLO 2 Dedicated Management NIC. On
servers using the iLO 2 Dedicated Management NIC, the standard hardware configuration provides
iLO 2 network connectivity only through the iLO 2 Shared Network Port connection. iLO 2 detects
the lack of an iLO 2 Dedicated Management NIC and automatically defaults to the Shared Network
Port. On some of these servers, an iLO 2 Dedicated Management NIC might be available as a
hardware option. If an iLO 2 Dedicated Management NIC is available as a hardware option, iLO
2 defaults to the installed iLO 2 Dedicated Management NIC. On servers using the iLO 2 Dedicated
Management NIC, you can enable shared network port operation through the iLO 2 interface.
The iLO 2 Shared Network Port uses the network port labeled NIC 1 on the rear panel of the
server. NIC numbering in the operating system can be different from system numbering. The iLO
2 Shared Network Port does not incur an iLO 2 performance penalty. Peak iLO 2 traffic is less
than 2 MB (on a NIC capable of 1000-Mb speeds), and average iLO 2 traffic is infrequent and
low.
The Shared Network Port is not available on HP ProLiant ML310 G3, ML310 G4, BL20p G4, and
all c-Class blade servers.
Network 61










