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
Dynamic power capping for server blades
Dynamic power capping is an iLO 2 feature available for c-Class server blades and accessed
through HP Onboard Administrator. For more information on all the power setting options for
c-Class server blades, see the HP BladeSystem Onboard Administrator User Guide.
Dynamic power capping is only available if your system hardware platform, BIOS (ROM), and
power micro-controller firmware version support this feature. If your system is capable of performing
dynamic power capping, iLO 2 automatically functions in Dynamic Power capping mode.
In Onboard Administrator, there are two Dynamic Power capping options:
• Dynamic Power
If enabled, Dynamic Power automatically places unused power supplies in standby mode to
increase enclosure power supply efficiency, thereby minimizing enclosure power consumption
during lower power demand. Increased power demands automatically return standby power
supplies to full performance. If Dynamic Power is:
— Enabled (default setting) – Some power supplies can be automatically placed on standby
to increase overall enclosure power subsystem efficiency.
— Disabled – All power supplies share the load. The power subsystem efficiency varies
based on load.
• Enclosure Dynamic Power Cap
An optional setting that enables you to set a cap on a group of servers in an enclosure. Set
the cap between the values shown above the Enclosure Dynamic Power Cap field. These
values are based on the enclosure's current configuration.
As the servers run, the demand for power varies for each server. A power cap for each server
is set to provide the server with enough power to meet its workload demands while still
conforming to the Enclosure Dynamic Power Cap.
You can use either the Static Power Limit or the Enclosure Dynamic Power Cap in the following
situations:
— If the facility power is limited to the enclosure, you can enter a fixed limit into each
enclosure. For example, if the hosted location limits the enclosure to 5000 W. In the limit
Enclosure Input Watts field, enter 5000. The Onboard Administrator limits total power
allocation to 5000 W, which might result in denying power to some of the server blades.
— If the facility limits cooling capacity to the enclosure, then divide the limit of Btu/hr
available to the enclosure by 3.41 to determine the watts limit for that enclosure. Enter
that watts limit to restrict the heat load of the enclosures. For example: If the facility limits
individual enclosure to 27,280 Btu/hr, then 27,280 divided by 3.41 yields 8,000 W.
Enter the watts limit to restrict that enclosure to 27,280 Btu/hr. This limit can result in
denying power to some of the server blades.
— If you need to restrict an enclosure's electrical load or thermal output, an Enclosure
Dynamic Power Cap is better. It enables more blades to power on than a Static Power
Limit does. A Static Power Limit is better in the following cases:
– You do not want caps dynamically adjusted on your server blades.
– You prefer to not power on a server blade if it cannot be allocated full power (even
if it typically consumes less).
– More than 1/4 of the blades in the enclosure do not meet hardware or firmware
requirements for the Enclosure Dynamic Power Cap.
– You do not have redundant AC power supplies.
– Do not set a cap on an empty enclosure. This disables both the Static Power Limit
and the Enclosure Dynamic Power Cap.
ProLiant BladeSystem HP Onboard Administrator 127










