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
Terminal Services Passthrough installation
The following section describes how to install Terminal Services Passthrough on Windows Server
2008, Windows Server 2003, and Microsoft Windows XP.
• Windows Server 2003 and Windows Server 2008
Windows servers require Microsoft .NET Framework to support the use of iLO 2 Terminal
Services. The Terminal Services Passthrough service and the iLO 2 Management Interface
driver for Windows Server 2008 and Windows Server 2003 must be installed on the server
that has the iLO 2.
1. Install the iLO 2 Management Interface driver.
2. Install the passthrough service. To install the service, launch the component installer and
follow the directions in the installation wizard.
If the service is already installed, then you must manually restart or reboot the server when
the driver is installed.
3. Activate the Terminal Services client.
On Windows Server 2003 and Windows Server 2008, you can activate Remote Desktop
sharing by clicking the Remote tab under My Computer and Properties.
If the iLO 2 installation is complete, and if iLO 2 Terminal Services passthrough option is set
to automatic, then Terminal Services launches when the installation is complete.
• Microsoft Windows XP
On Windows XP, the Remote Desktop Connection is built-in and has no other installation
requirements.
Errors that occur during installation and execution of the passthrough service are logged in the
server Application Event Log. You can remove the passthrough service using Add or Remove
Programs in the Control Panel.
Enabling the Terminal Services Passthrough option
By default, the Terminal Services Passthrough feature is disabled and can be enabled on the
Administration>Access>Services page. The Terminal Services button in the Remote Console is
deactivated until the Terminal Services passthrough feature is enabled.
To use of the Terminal Services Passthrough feature, install the latest Lights-Out Management
Interface Driver and then install Terminal Services passthrough service for Microsoft Windows on
the server.
When the Terminal Services Passthrough option is set to Enabled or Automatic on the
Administration>Access>Services page and the Terminal Services Client is installed on the Windows
client (installs by default on Windows XP), the Terminal Services button is enabled. When you click
the Terminal Services button, the applet tries to launch the Terminal Services, even if the server is
not running a Windows operating system.
You must comply with Microsoft license requirements which are the same as connecting through
the server's NIC. For instance, when set for administrative access, Terminal Services does not allow
more than two connections, regardless of whether the connections are through the server's NIC,
or iLO 2, or both.
Terminal Services warning message
Terminals Services users operating on Windows 2003 Server might notice the following when
using the Terminal Services passthrough feature of iLO 2. If a Terminal Services session is established
through iLO 2 and a second Terminal Services session is established by a Windows administrator
(Console mode), the first Terminal Services session is disconnected. However, the first Terminal
Services session does not receive the warning message indicating the disconnection until
approximately one minute later. During this one-minute period, the first Terminal Services session
36 Configuring iLO 2