Using iLO 2.... 76

System status and status summary information... 76 System Information Summary.... 78 iLO 2 Log..... 80 IML..... 80 Diagnostics..... 81 Insight Agents.... 82 iLO 2 Remote Console..... 83 Remote Console overview and licensing options... 84 Remote Console settings..... 84 Integrated Remote Console Fullscreen.... 88 Integrated Remote Console option.... 88 Shared Remote Console..... 93 Using Console Capture.... 93 Using HP iLO Video Player.... 94 Acquiring the Remote Console.... 96 Remote Console.... 96 Text-based remote console overview... 98 Virtual media..... 107 Using iLO 2 Virtual Media devices.... 108 Virtual folder.... 115 Virtual folder operating system notes.... 115 Power management.... 116 Server power settings.... 117 Server power data.... 119 Processor states..... 120 Power efficiency.... 121 Graceful shutdown..... 122 ProLiant BL p-Class Advanced management.... 122 Rack View..... 123 iLO 2 control of ProLiant BL p-Class server LEDs... 127 ProLiant BL p-Class alert forwarding.... 127 ProLiant BladeSystem HP Onboard Administrator... 127
iLO 2 BL c-Class tab.... 128 Enclosure bay IP addressing.... 128 Dynamic power capping for server blades... 130 iLO 2 Virtual Fan.... 131 iLO option..... 131 Web Administration.... 132 BL p-Class and BL c-Class features... 132
Directory services..... 134
Overview of directory integration... 134 Benefits of directory integration.... 134 Advantages and disadvantages of schema-free directories and HP schema directory.. 135 Schema-free directory integration... 136 HP schema directory integration.... 136 Setup for Schema-free directory integration.... 138 Active Directory preparation.... 138 Schema-free browser-based setup... 139 Schema-free scripted setup... 140 Schema-free HPLOMIG-based setup.... 140 Schema-free setup options... 140 Schema-free nested groups.... 141 Setting up HP schema directory integration.... 142 Features supported by HP schema directory integration... 142 Setting up directory services.... 142 Schema documentation.... 143 Directory services support.... 143 Schema required software... 144 Schema installer.... 144 Management snap-in installer.... 147 Directory services for Active Directory.... 147 Directory services for eDirectory.... 157 User login using directory services.... 165 Introduction to directory-enabled remote management... 166 Creating roles to follow organizational structure... 166 Using existing groups.... 166 Using multiple roles..... 167 How directory login restrictions are enforced.... 168 Restricting roles..... 168 User restrictions..... 169 Creating multiple restrictions and roles... 170 Using bulk import tools..... 171 Introduction to HPQLOMIG utility... 173 Compatibility..... 173 HP Lights-Out directory package.... 173 Using HPQLOMIG.... 174 Finding management processors.... 174 Upgrading firmware on management processors.... 176 Selecting a directory access method.... 177 Naming management processors... 178 Configuring directories when HP Extended schema is selected... 179

Red Hat

Operational overview 14
SUSE LINUX Enterprise Server 10

Operational overview 15

iLO 2 setup

Quick setup

To quickly setup iLO 2 using the default settings for iLO 2 Standard and iLO Advanced features, follow the steps below:

1. 2. 3. 4.

PrepareDecide how you want to handle networking and security ("Preparing to setup iLO 2" on page 16) Connect iLO 2 to the network ("Connecting to the network" on page 18). If you are not using dynamic IP addressing, use the iLO 2 RBSU to configure a static IP address ("Configuring the IP address" on page 18). Log into iLO 2 from a supported browser or command line using the default user name, password, and DNS name provided on the iLO 2 Network Settings tag attached to the server ("Logging in to iLO 2 for the first time" on page 19). Change the default user name and password on the administrator account to your predefined selections If you are using the local accounts feature, set up your user accounts ("Setting up user accounts" on page 19). Activate iLO 2 advanced features ("Activating iLO 2 licensed features using a browser" on page 20). Install the iLO 2 device drivers ("Installing iLO 2 device drivers" on page 21).

5. 6. 7. 8.

Preparing to setup iLO 2
Before setting up your iLO 2 management processors, you must decide how to handle networking and security. The following questions can help you configure iLO 2 for your needs:
How should iLO 2 connect to the network? For a graphical representation and explanation of the available connections, see the section, "Connect to the network ("Connecting to the network" on page 18)." Typically iLO 2 is connected to the network using either:
A corporate network where both the NIC and the iLO 2 port are connected to the corporate network. This connection enables access to iLO 2 from anywhere on the network and reduces the amount of networking hardware and infrastructure required to support iLO 2. However, on a corporate network, network traffic can hinder iLO 2 performance. A dedicated management network with the iLO 2 port on a separate network. A separate network improves performance and security because you can physically control which workstations are connected to the network. A separate network also provides redundant access to the server when a hardware failure occurs on the corporate network. In this configuration, iLO 2 cannot be accessed directly from the corporate network.

How will iLO 2 acquire an IP address?
To access iLO 2 after connecting it to the network, the management processor must acquire an IP address and subnet mask using either a dynamic or static process:
Dynamic IP address is set by default. iLO 2 obtains the IP address and subnet mask from DNS/DHCP servers. This method is the simplest. Static IP address is used to configure a static IP address if DNS/DHCP servers are not available on the network. A static IP address can be configured in iLO 2 using the RBSU. If using a static IP, you must have an IP address before starting iLO 2 setup.
What access security is required and what user accounts and privileges are needed? iLO 2 provides several options to control user access. You must select one of the following methods to prevent unauthorized access to corporate IT assets:
Local accounts with up to 12 user names and passwords can be stored on iLO 2. This is ideal for small environments such as labs and small- and medium-sized businesses. Directory services use the corporate directory (Microsoft Active Directory or Novell eDirectory) to manage iLO 2 user access. This is ideal for environments with a large number of frequently changing users. If you plan to use Directory services leave at least one local account enabled for alternate access. For more information about iLO 2 access security see the section, "Security (on page 41)."
How do you want to configure iLO 2? iLO 2 supports various interfaces for configuration and operation. This guide discusses the following interfaces:
iLO 2 RBSU ("Setting up iLO 2 using iLO 2 RBSU" on page 20) can be used when the system environment does not use DHCP, DNS, or WINS. Browser-based setup ("Setting up iLO 2 using the browser-based option" on page 20) can be used when you can connect to iLO 2 on the network using a browser. This method can also reconfigure a previously configured iLO 2. SMASH CLP can be used when a command line is accessible through telnet, SSH, or physical serial port. See the HP Integrated Lights-Out Management Processor Scripting and Command Line Resource Guide.
The iLO 2 default settings enable you to use most features with no additional configuration. However, the extensive configuration flexibility of iLO 2 enables customization for multiple enterprise environments. See the section, "Configuring iLO 2 (on page 24)" for all available options. For advanced setup of multiple iLO 2 management processors using scripting commands, the following methods are available. Scripts are text files written in an XML-based scripting language called RIBCL. You can use RIBCL scripts to configure iLO 2 on the network, during initial deployment, or from an already deployed host. Each method is described in the HP Integrated Lights-Out Management Processor Scripting and Command Line Resource Guide.

Communication between the iLO 2 and Remote Console is always encrypted. Remote Console/Telnet Port Web Server Non-SSL Port Web Server SSL Port Terminal Services Passthrough 443 Disabled This setting enables you to specify which port the iLO 2 Remote Console uses for remote console communications. This setting enables you to specify which port the embedded web server in iLO 2 uses for unencrypted communications. This setting enables you to specify which port the embedded web server in iLO 2 uses for encrypted communications. This setting enables you to control the ability to support a connection through iLO 2 between a Microsoft Terminal Services client and Terminal Services server running on the host. The following settings are valid:
AutomaticWhen remote console is started, the Terminal Services client is launched. EnabledThe pass-through feature is enabled and can connect the Terminal Services client directly to the iLO 2 without logging-into the iLO 2. DisabledThe pass-through feature is off.
Terminal Services Port 3389
This setting enables you to specify the Terminal Services Port that the iLO 2 uses for encrypted communications with Terminal Services Pass-through software on the server. If the Terminal Services port is configured to anything other than the default, you must manually change the port number. This setting enables you to specify the port for virtual media support in iLO 2 communications. This setting enables you to specify the Shared Remote Console Port. The Shared Remote Console Port is opened on the client to allow additional users to connect to remote console in a peer-to-peer fashion. This port is only open when Shared Remote Console is in use.
Virtual Media Port Shared Remote Console Port

17988 9300

Configuring iLO 2 34

Console Replay Port

This setting enables you to specify the Console Replay Port. The Console Replay Port is opened on the client to enable the transfer of internal capture buffers to the client for replay. This port is only open when a capture buffer is being transferred to the client. This setting specifies the Raw Serial Data port address.The Raw Serial Data port is only open while the WiLODbg.exe utility is being used to debug the host server remotely.

Terminal Services Passthrough option display
The iLO 2 firmware might not accurately display the Terminal Services Passthrough option. The Terminal Services Passthrough option might appear active even if the operating system is not Terminal Services enabled (for example, if the host operating system is Linux, which does not support Terminal Services operation).
Remote Console and Terminal Services clients
Using the management network connection to the iLO 2, an iLO 2 Remote Console session can be used to display a Terminal Services session to the host. When the iLO 2 Remote Console applet runs, it launches the Terminal Services client based on user preference. The Sun JVM must be installed to obtain full functionality of this feature. If the Sun JVM is not installed, then the Remote Console cannot automatically launch the Terminal Services client. If Terminal Services pass-through is enabled, and the Terminal Services server is available, switching between iLO 2 Remote Console and the Terminal Services client will be seamless as the server progresses from pre-operating system environment to operating system-running environment, to operating system-not available environment. The seamless operation is available as long as the Terminal Services client is not started before Remote Console is available. If Remote Console is available and the Terminal Services client is available, Remote Console will start the Terminal Services client when appropriate.

Configuring iLO 2 37

When using the Terminal Services pass-through option with Windows Server 2003 and Windows Server 2008, there is approximately a 30-second delay after the CTRL-ALT-DEL dialog box appears before the Terminal Services client launches. The 30-second delay represents how long it takes for the service to connect to the RDP client running on the server. If the server is rebooted from the Terminal Services client, the Remote Console screen turns grey or black for up to one minute while iLO 2 determines that the Terminal Services server is no longer available. If Terminal Services mode is set to Enabled, but you want to use the Remote Console, then launch the Terminal Services client directly from the Terminal Services client menu. Launching directly from the client menu enables simultaneous use of the Terminal Services client and the Remote Console. Terminal Services can be disabled or enabled at any time. Changing the Terminal Services configuration causes the iLO 2 firmware to reset. Resetting the iLO 2 firmware interrupts any open connections to iLO 2. When the Terminal Services client is launched by the Remote Console, Remote Console goes into a sleep mode to avoid consuming CPU bandwidth. Remote Console still listens to the Remote Console default port 23 for any commands from the iLO 2. iLO 2 passes through only one Terminal Services connection at a time. Terminal Services has a limit of two concurrent sessions. The Remote Console activates and becomes available if the Remote Console is in sleep mode and the Terminal Services client is interrupted by any of the following events:

Using iLO 2 121

Graceful shutdown
The ability of the iLO 2 microprocessor to perform a graceful shutdown requires cooperation from the operating system. In order to perform a graceful shutdown, the health driver must be loaded. iLO 2 communicates with the health driver, and the appropriate operating system method of safely shutting the system down to ensure data integrity is performed. In cases where the health driver is not loaded, the iLO 2 processor attempts using the operating system to perform a graceful shutdown through the power button. iLO 2 emulates a physical power button press in order to prompt the operating system to shutdown gracefully. The behavior of the operating system is dependent on its configuration and settings for a power button press. The EAAS configuration of the HOST ROM RBSU allows for the disabling of this automatic shutdown feature. This configuration allows for the disabling of the automatic shutdown event except for in the most extreme conditions where physical damage would result. Starting with Windows Server 2003, the computer group policy disables a graceful shutdown of the system using a momentary press unless an Administrator is logged in to the operating system. To change this setting and enable a graceful shutdown, do the following:
From a command prompt, execute the command gpedit.misc.
Set Computer Configuration>Windows Settings>Security Settings>Local Policies>Security Options>Shutdown: Allow system to be shut down without having to log on to Enabled.
ProLiant BL p-Class Advanced management
iLO 2 Advanced is a standard component of ProLiant BL p-Class server blades that provides server health and remote server blade manageability. Its features are accessed from a network client device using a supported Web browser. In addition to other features, iLO 2 Advanced provides keyboard, mouse, and video (text and graphics) capability for a server blade, regardless of the state of the host operating system or host server blade. iLO 2 includes an intelligent microprocessor, secure memory, and a dedicated network interface. This design makes iLO 2 independent of the host server blade and its operating system. iLO 2 provides remote access to any authorized network client, sends alerts, and provides other server blade management functions. Using a supported Web browser, you can:

Rack name Rack serial number Enclosure name Enclosure serial number Enclosure type Firmware revision Hardware revision Load balance wire Enclosure temperature Enclosure temperature side A and B Management Module UID
Network component information
Network component information displays the status of the patch panel or interconnect switch that has been selected. The information displayed includes Fuse A, Fuse B, and Network Component Type.

Using iLO 2 126

iLO 2 control of ProLiant BL p-Class server LEDs
iLO 2 can monitor BL p-Class servers through POST tracking and the Server Health LED.

Server POST tracking

Feedback is limited while the server is booting because of the headless nature of the ProLiant BL p-Class servers. iLO 2 provides boot-time feedback by flashing the Server Health LED green during server POST. The LED is set to solid amber if the boot is unsuccessful. The LED is set to solid green at the end of a successful boot. After a successful boot, control of the Server Health LED is returned to the server, which can turn the LED off or set it to some other color to represent the health of the server hardware.
Insufficient power notification
iLO 2 turns the Server Health LED solid red if iLO 2 cannot power on the server because insufficient power is in the rack infrastructure.
ProLiant BL p-Class alert forwarding
iLO 2 supports blade infrastructure SNMP traps on a pass-through basis. Reporting of blade infrastructure status by iLO 2 does not require operating system support. The alerts (traps) originate from the Enclosure Manager and Power Supply Manager and are transmitted to iLO 2. iLO 2 p-Class firmware forwards infrastructure alerts as SNMP traps to a correctly configured management console. These alerts allow the monitoring of p-Class alerts to take place in an SNMP management console. p-Class alert forwarding is disabled by default and can be enabled from the SNMP/Insight Manage Settings web page. The following alerts are identified and forwarded by iLO 2: Alert ID

22015 22023

Enclosure temperature failure Enclosure temperature degradation Enclosure temperature OK Enclosure fan failed Enclosure fan degraded Enclosure fan OK Rack power failure Rack power degraded Rack power supply OK Rack server failed; not enough power
ProLiant BladeSystem HP Onboard Administrator
HP BladeSystem Onboard Administrator is the enclosure management processor, subsystem, and firmware base used to support the HP BladeSystem and all the managed devices contained within the enclosure.

Using iLO 2 127

You can access iLO 2 through the HP Onboard Administrator iLO option (on page 131) using the Web Administration (on page 132) link or directly. To log in to iLO 2 directly, see the "Log into iLO 2 for the first time ("Logging in to iLO 2 for the first time" on page 19)" section for more information.

Is your configuration scalable?
The following questions can help you determine if your configuration is scalable:

Directory services 135

Schema-free directory integration
Using the schema-free directory integration method, users and group memberships reside in the directory, but group privileges reside in the individual iLO 2. iLO 2 uses login credentials to read the user object in the directory and retrieve the user group memberships, which are compared to those stored in iLO 2. If there is a match, authorization is granted. For example:
Advantages of using schema-free directory integration:
There is no need to extend the directory schema. When ActiveX controls are enabled in the browser and login, NetBIOS and e-mail formats are supported. Little or no setup is required for users in the directory. If there is no setup, the directory uses existing users and group memberships to access iLO 2. For example, if you have a domain admin named User1, you can copy the distinguished name of the domain admin security group over to iLO 2 and give it full privileges. User1 would then have access to iLO 2. Supports only Microsoft Active Directory Group privileges are administered on each iLO 2. However, this disadvantage is minimized by group privileges rarely changing, and the task of changing group membership is administered in the directory and not on each separate iLO 2. HP provides tools that enable changes to a large number of iLO 2 to be made at the same time.
Disadvantages of using schema-free directory integration
HP schema directory integration
HP schema directory integration consists of a class called hpqRole (which is a sub-class HP schema directory integration and consists of a class called hpqRole (a subclass of Group), one called hpqTarget (a sub-class of User), along with other helper classes. An instance of an hpqRole is simply a role. An instance of an hpqTarget is equivalent to one iLO 2.

Directory services 136

A role contains one or more iLO 2 and one or more users, and has a list of privileges that these users have with the iLO 2 in the role. All iLO 2 access is managed by adding and removing users and iLO 2 to and from the role, and by managing the privileges on the role. For example:

in region1, and a "remoteAdmins" and a "remoteMonitors" role in roles in region2.
Assign rights to the role and associate the roles with users and devices using the HP provided ConsoleOne snap-ins tool.
a. Right-click the remoteAdmins role in the roles organizational unit in the region1 organizational
unit, and select Properties.
b. Select the Role Managed Devices tab of the HP Management option and click Add. c.
Using the Select Objects page, browse to the hp devices organizational unit in the region1 organizational unit. Select the three LOM objects created in step 2. Click OK>Apply. page. Devices and users are now associated.
d. Click the Members tab, and add users to the role by clicking the Add button on the Select Object e. Set the rights for the role using the Lights Out Management Device Rights option on the
HP Management tab. All users within the role have the rights assigned to the role on all of the iLO 2 devices managed by the role. In this example, the users in the remoteAdmins role are

Directory services 159

given full access to the iLO 2 functionality. Select the check boxes next to each right, and click Apply. To close the property sheet, click Close.
Using the same procedure as in step 4, edit the properties of the remoteMonitors role:
a. Add the three iLO 2 devices within hp devices under region1 to the Managed Devices list on the
Role Managed Devices option of the HP Management tab.
b. Add users to the remoteMonitors role using the Members tab. c.
Select the Login check-box, and click Apply>Close. Using the Lights Out Management Device Rights option of the HP Management tab, members of the remoteMonitors role will be able to authenticate and view the server status.
User rights to any LOM device are calculated as the sum of all the rights assigned by all the roles in which the user is a member, and in which the LOM device is a managed device. Following the preceding examples, if a user is in both the remoteAdmins and remoteMonitors roles, they will have all the rights, because the remoteAdmins role has those rights. To configure a LOM device and associate it with a LOM object used in this example, use settings similar to the following on the Directory Settings page. NOTE: Commas, not periods, are used in LDAP distinguished names to separate each component. RIB Object DN = cn=rib-email-server,ou=hp devices,ou=region1,o=samplecorp Directory User Context 1 = ou=users,o=samplecorp For example, user CSmith, located in the users organizational unit within the samplecorp organization, who is also a member of one of the remoteAdmins or remoteMonitors roles, would be allowed to log in to the iLO 2. The user enters csmith (case insensitive) in the Login Name field of the iLO 2 login screen and uses the eDirectory password in the Password field of that screen to gain access.

Directory services 165

Directory-enabled remote management
Introduction to directory-enabled remote management
This section is for administrators who are familiar with directory services and the iLO 2 product and want to use the HP schema directory integration option for iLO 2. You must be familiar with the Directory services (on page 134)" section and comfortable with setting up and understanding the examples. Directory-enabled remote management enables you to:
Create Lights-Out Management Objects You must create one LOM device object to represent each device that will use the directory service to authenticate and authorize users. Refer to the "Directory services (on page 134)" section for additional information on creating LOM device objects for Active Directory ("Directory services for Active Directory" on page 147) and eDirectory ("Directory services for eDirectory" on page 157). In general, you can use the HP provided snap-ins to create objects. It is useful to give the LOM device objects meaningful names, such as the device network address, DNS name, host server name, or serial number.
Configure the Lights-Out management devices Every LOM device that uses the directory service to authenticate and authorize users must be configured with the appropriate directory settings. Refer to "Configuring directory settings (on page 52)" for details on the specific directory settings. In general, you can configure each device with the appropriate directory server address, LOM object distinguished name, and any user contexts. The server address is either the IP address or DNS name of a local directory server or, for more redundancy, a multi-host DNS name.
Creating roles to follow organizational structure
Often, the administrators within an organization are placed into a hierarchy in which subordinate administrators must assign rights independently of ranking administrators. In this case, it is useful to have one role that represents the rights assigned by higher-level administrators and to allow the subordinate administrators to create and manage their own roles.

Using existing groups

Many organizations will have their users and administrators arranged into groups. In many cases, it is convenient to use the existing groups and associate the groups with one or more Lights-Out Management role objects. When the devices are associated with the role objects, the administrator controls access to the Lights-Out devices associated with the role by adding or deleting members from the groups. When using Microsoft Active Directory, it is possible to place one group within another or nested groups. Role objects are considered groups and can include other groups directly. Add the existing

Directory-enabled remote management 172
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.
The HPQLOMIG utility operates on Microsoft Windows and requires Microsoft.NET Framework. For additional information and to download.NET framework, see the Microsoft website (http://www.microsoft.com/net). The HPQLOMIG utility supports the following operating systems:

Active Directory

Windows 2000 Windows Server 2003 Windows 2000 Windows Server 2003

Novell eDirectory 8.6.2

HP Lights-Out directory package
All of the migration software, as well as the schema extender and management snap-ins, are packaged in an HP Smart Component. To complete the migration of your management processors, you must extend the schema and install the management snap-ins before running the migration tool. The Smart Component is located on the HP Lights-Out management website (http://www.hp.com/servers/lights-out). To install the migration utilities, click LDAP Migration Utility in the Smart Component. A Microsoft MSI installer launches and installs HPQLOMIG, the required DLLs, the license agreement, and other files into the C:\Program Files\Hewlett-Packard\HP Lights-Out Migration Tool directory. You can select a different directory. The installer creates a shortcut to HPQLOMIG on the Start menu and installs a sample XML file.

LED indicator

POST code (activity completed)
00 02Normal operation 0a 0b 0c

Failure indicated

None 1 or and 3 and 2 3, 2, and 4 and and 2 4, 2, and and 3
Set up chip selects. Determine platform. Set RUNMAP bit. Initialize SDRAM controller. Activate the I cache. Initialize (only) the D cache. Copy secondary loader to RAM. Verify secondary loader. Begin secondary loader. Copy ROM to RAM. Verify ROM image in RAM. Could not copy secondary loader. Did not execute secondary loader. SDRAM memory test failed. Could not copy boot block. Boot block failed to execute.
Troubleshooting iLO 2 188
4, 3, and 1 None 4, 3, and 2 Varies 4, 3, 2, and 1 None HB and 7
Boot Block Main started. Start C Run time initialization.
Boot block could not find a valid image.

0e Varies 0f 00

Main() has received control. Each subsystem may selftest. Start ThreadX. Main_init() completed. Flashes as the iLO 2 processor executes firmware code. It does not change the value of the lower six LEDs.

Main self-test failed.

RTOS startup failed. Subsystem startup failed.
The iLO 2 microprocessor firmware includes code that makes consistency checks. If any of these checks fail, the microprocessor executes the FEH. The FEH presents information using the iLO 2 POST LED indicators. The FEH codes are distinguished by the alternating flashing pattern of the number 99 plus the remainder of the error code. FEH code

Consistency check

TXAPICHK

Explanation

An RTOS function was called with an inappropriate value or from an inappropriate caller. The saved context of one or more threads has been corrupted. A stack probe failed, the return address is invalid, or an illegal trap instruction has been detected. An unexpected write to low memory has occurred. The reset vector has been modified.

9966 99C1

TXCONTEXT TRAP NMIWR CHKNULL

Event log entries

Event log display
Server power failed Browser login: IP address Server power restored Browser logout: IP address Server reset Failed Browser login IP Address: IP address

Event log explanation

Displays when the server power fails. Displays the IP address for the browser that logged in. Displays when the server power is restored. Displays the IP address for the browser that logged out. Displays when the server is reset. Displays when a browser login fails.

diskette, changing 112 display settings 98 DLL (dynamic link library) 173, 210 DNS (domain name system) 150, 155, 157, 163, 166, 169, 215 DNS name 62 DNS server 62 DNS settings 65 domain name system (DNS) 150, 155, 157, 163, 166, 169, 215 domain/name login 199 drive key, support 109 DVD-ROM, virtual 112 Dynamic Host Configuration Protocol (DHCP) 16, 60, 61, 65, 80, 132 dynamic link library (DLL) 173, 210
EBIPA (Enclosure Bay IP Addressing) 128 EBIPA, settings 128 eDirectory 142, 145, 157, 161, 162, 163, 164, 166, 168 Emergency Management Services (EMS) 35, 102, 103, 105, 183 EMS (Emergency Management Services) 35, 102, 103, 105, 183 EMS Console 105 enable SSH 45 enable, Terminal Services pass-through 37 enabling 134 enclosure fan, control 131 enclosure information 125 enclosure information, status 125 enclosure, temperature 131 encryption 54 encryption settings 55 encryption, connecting to iLO 2 with 55 end user license agreement (EULA) 20, 223 error messages 198 EULA (end user license agreement) 20, 223 event capture, remote console 83 event log entries 80, 189 event log, date entries 210 event logs 80 events, WS-Management 12
fan management 78, 131 feature, comparison 10

Index 230

features, new 9 file transfer, virtual folder 115 Firefox support 13 firewall, allowing traffic 196 firmware, downgrading 26 firmware, updating 24, 25, 26, 176, 210 folder, virtual 115
G1 BL-series blade enclosure 69 GNOME, troubleshooting 205 graceful shutdown 122 graphical remote console 83 graphical user interface (GUI) 13 Group Administration 32 groups 166 GUI (graphical user interface) 13
hpqLOMRightVirtualMedia 218 hpqLOMvhpqPolicy 214 hpqPolicyDN 214 hpqRole 214 hpqRoleIPRestrictionDefault 215 hpqRoleIPRestrictions 215 hpqRoleMembership 215 hpqRoleTimeRestriction 216 hpqTarget 213 hpqTargetMembership 215
iLO 2 access 33 iLO 2 advanced features 20, 187 iLO 2 configuration, BL p-Class 69, 73 iLO 2 firmware upgrade 24 iLO 2 IRC 88 iLO 2 server reset 194 iLO 2 setup 16 iLO 2 telnet access 195 iLO 2 user administration 28 image files, disk 114 IML (Integrated Management Log) 22, 76, 78, 79, 80, 124 initial access 19 install, Terminal Services pass-through 36 installation overview 142, 147, 183 installing software 21, 22, 157 Integrated Management Log (IML) 22, 76, 78, 79, 80, 124 integrated remote console 88 Integrated Remote Console (IRC) 64, 88, 93, 103, 115, 116, 119, 167, 197, 203 Intelligent Platform Management Interface (IPMI) 11 interface, browser 13, 207 international keyboard 88 Internet Explorer support 13 IP address assignment 72 IP addresses, setting up 18, 61, 72, 169 IPMI (Intelligent Platform Management Interface) 11 IRC (Integrated Remote Console) 64, 88, 93, 103, 115, 116, 119, 167, 197, 203 IRC, sharing 93 IRC, troubleshooting 201, 204, 205
hardware troubleshooting 192 health, system 78 high performance mouse 91 host server troubleshooting 212 hot keys, international keyboards 88 hot keys, remote 86 hot keys, supported 86 HP BladeSystem information 127 HP BladeSystem setup 72 HP Extended schema 135, 142, 146, 173, 179 HP Extended schema options 135, 136 HP Lights-Out Migration Command Line (HPQLOMGC) 171, 173, 224 HP Onboard Administrator 127 HP Onboard Administrator, iLO option 131 HP Onboard Administrator, Web Administration 132 HP schema directory integration 142, 166 HP SIM trusted servers, adding 57 HP SIM, SNMP information 210 HP Systems Insight Manager 184, 185, 186 HP technical support 221 HPQLOMGC (HP Lights-Out Migration Command Line) 171, 173, 224 HPQLOMIG (HP Lights-Out Migration) 140, 171, 173 hpqLOMRightConfigureSettings 219 hpqLOMRightLogin 218 hpqLOMRightRemoteConsole 218 hpqLOMRightServerReset 219

Log on to the iLO web page. Click the Information>Diagnostic page, and click the Reset button. Use the CLP with the following commands:
Ssh to iLO Login to iLO Cd/map1 reset What features are now available with the iLO 3 Advanced?
Virtual media Boot a remote server to: a standard 1.44-MB diskette, CD or USB flash key on a client machine, a network based floppy, an ISO 9660 CD, or a flash key image from any network location Virtual graphical remote console Use a standard browser as a virtual desktop with full control over a remote server's video display, keyboard, and mouse during any system state Directory services integration Use directory services, such as Microsoft Active Directory and Novell eDirectory, to authorize user access to Integrated Lights-Out processors Power management reporting From any iLO interface, monitor current and historical power levels. Flexible key acquisition and management Purchase single or multiple system keys and automate key activation to groups of systems with scripted deployment. This information can change without notice. Not all features are supported by all operating systems. Not all features are supported by all platforms. Some features might require configuration and additional support. The supported features and license requirements might change.

Introduction to iLO 3

Guide overview
HP iLO 3 provides multiple ways to configure, update, and operate servers remotely. The HP Integrated Lights-Out 3 User Guide describes these features and how to use them with the browser-based interface and RBSU. Some features are licensed features and can only be accessed after purchasing an optional license. For more information, see "Licensing (on page 23)." The HP Integrated Lights-Out Management Processor Scripting and Command Line Resource Guide describes the syntax and tools available to use iLO 3 through a command-line or scripted interface. This documentation discusses HP Integrated Lights-Out for ProLiant ML/DL servers, as well as ProLiant BladeSystem server blades. For information on iLO for Integrity servers and server blades, see the HP website (http://www.hp.com/go/integrityiLO).

Linux device driver support
You can download the LSP files containing the iLO 3 driver, the foundation agents, and health agents from the HP website (http://www.hp.com/support). The instructions on how to install or update the iLO 3 driver are available on the website. The HP Management Agents for Linux are:
The hp-ilo driver comes in stock for SLES11 SP1, and Redhat 5. For SLES10, it is available in the SmartStart CD. The hp-health has the hpasmd, hpasmlited, hpasmpld, and hpasmxld drivers. The hp-ilo driver is in the hp-ilo-8.x.x-xxx.sles10.x86_64.rpm.
To load the health and iLO 3 driver packages, use the following commands: rpm ivh hp-snmp-agents-d.vv.v-pp.Linux_version.i386.rpm rpm ivh hp-iLO-d.vv.v-pp.Linux_version.i386.rpm rpm ivh hp-health-d.vv.v-pp.Linux_version.i386.rpm where d is the Linux distribution and version and vv.v-pp are version numbers. For additional information, see the Software and Drivers website (http://www.hp.com/support). To remove the rpm e rpm e rpm e health and iLO 3 drivers, use the following commands: hp-iLO hp-snmp-agents hp-health
For additional information, see the Software and Drivers website (http://www.hp.com/support).

Setting up iLO 3 20

Configuring iLO 3
iLO 3 configuration overview
Typically, an advanced or administrative user who must manage users and configure global and network settings configures iLO 3. You can configure iLO 3 using the iLO 3 browser-based GUI or scripting tools such as CPQLOCFG and HPONCFG (described in the HP Integrated Lights-Out Management Processor Scripting and Command Line Resource Guide.) The iLO 3 Administration tab enables you to configure and manage user settings, SNMP alerting (through integration with HP SIM), security settings, licensing, certificate administration, directory settings, and network environment settings. The Administration tab includes the following menu options:
iLO 3 Firmware ("Upgrading iLO 3 firmware" on page 21) Licensing (on page 23) User Administration (on page 25) Access Settings Security (on page 31) Network (on page 43) Management (on page 48)

Upgrading iLO 3 firmware

Firmware upgrades enhance the functionality of iLO 3. You can find the latest firmware on the HP website (http://www.hp.com/servers/lights-out). Select your iLO 3 product and then select Software & Drivers. After the software and drivers page appears, select your iLO 3 product and operating system, and then click Locate Software. You can also locate your iLO 3 software by selecting the Operating System and Category options. You must have the Configure iLO 3 privilege (configure local device settings) to update the firmware unless you set then the security override switch ("iLO 3 Security Override Switch administration" on page 33). If the security override switch is set, any iLO 3 user can update the firmware. You must run firmware updates from an Administrator or root context on the host operating system. To update the iLO 3 choose one of the following methods:

The following is a list of recommended password guidelines. Passwords should:
Never be written down or recorded Never be shared with others Not be words generally found in a dictionary, or easy to guess words, such as the company name, product names, the user's name, or the user's User ID Include at least three of the four following characteristics:

o o o o

At least one numeric character At least one special character At least one lowercase character At least one uppercase character
Passwords issued for a temporary user ID, password reset, or a locked-out user ID should also conform to these standards. Each password must be a minimum length of zero characters and a maximum length of 39 characters. The default minimum length is set to eight characters. Setting the minimum password length to fewer than eight characters is not recommended unless you have a physically secure management network that does not extend outside the secure data center.

Configuring iLO 3 32

Securing RBSU
iLO 3 RBSU enables you to view and modify the iLO 3 configuration. RBSU access settings can be configured using RBSU, a web browser (Access options (on page 29)), RIBCL scripts, or the iLO 3 Security Override Switch. RBSU has three levels of security:
RBSU Login Not Required (default) Anyone with access to the host during POST can enter the iLO 3 RBSU to view and modify configuration settings. This is an acceptable setting if host access is controlled.
RBSU Login Required (more secure) If RBSU login is required, then the active configuration menus are controlled by the authenticated user's access rights.
RBSU Disabled (most secure) If iLO 3 RBSU is disabled, user access is prohibited. This prevents modification using the RBSU interface.
iLO 3 Security Override Switch administration
The iLO 3 Security Override Switch allows the administrator full access to the iLO 3 processor. This access may be necessary for any of the following conditions:
iLO 3 must be re-enabled after it has been disabled. All user accounts with the Administer User Accounts privilege have been locked out. A bad configuration keeps the iLO 3 from displaying on the network and RBSU has been disabled. The boot block must be flashed.

iLO 3 Subsystem Name is a name used by the iLO 3 subsystem. If DHCP and DNS are configured correctly, this name can be used to connect to the iLO 3 subsystem instead of the IP address. See "iLO 3 subsystem name limitations (on page 44)" for more information.

DHCP/DNS Settings

The iLO 3 IP Address Settings page displays DHCP/DNS configuration information for iLO 3. The following options are available:

Configuring iLO 3 43

Domain Name is the name of the domain where the iLO 3 subsystem resides. This name is assigned by DHCP (if DHCP is enabled). Enabling DHCP allows you to configure the following DHCP options:
Use DHCP Supplied GatewayToggles if iLO 3 uses the DHCP server-supplied gateway. If not, enter an gateway address in the Gateway IP Address box. Use DHCP Supplied DNS ServersToggles if iLO 3 uses the DHCP server-supplied DNS server list. If not, enter the DNS server address in the Primary, Secondary, and Tertiary DNS Server fields. Use DHCP Supplied WINS ServersToggles if iLO 3 uses the DHCP server-supplied WINS server list. If not, enter the WINS server address in the Primary and Secondary WINS Server fields. Use DHCP Supplied Static RoutesToggles if iLO 3 uses the DHCP server-supplied static route. If not, enter the static route address in Static Route #1, Static Route #2, or Static Route #3 fields. Use DHCP Supplied Domain NameToggles if iLO 3 uses the DHCP server-supplied domain name. If not, enter a domain name in the Domain Name box.
WINS Server Registration toggles if iLO 3 registers its name with a WINS server. DDNS Server Registration toggles if iLO 3 registers its name with a DDNS server. Ping Gateway on Startup option causes iLO 3 to send four ICMP echo request packets to the gateway when iLO 3 initializes. This option ensures that the ARP cache entry for iLO 3 is up-to-date on the router responsible for routing packets to and from iLO 3. DHCP Server is the IP address of the DHCP server. This field cannot be assigned. It is received from DHCP if DHCP is enabled and represents the last known valid DHCP server address. Primary, Secondary, and Tertiary DNS Server are the IP addresses of the DNS servers. If supplied by the DHCP server, these fields are automatically populated. Otherwise, enter the IP addresses manually. Primary and Secondary WINS Server are the IP addresses of the WINS servers. If supplied by the DHCP server, these fields are automatically populated. Otherwise, enter the IP addresses manually. Static Route #1, Static Route #2, and Static Route #3 (destination, gateway) are the network destination gateway addresses. Enter up to three network destination/gateway routing pairs.
iLO 3 subsystem name limitations
The iLO 3 subsystem name represents the DNS name of the iLO 3 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 3 subsystem name instead of the IP address.

SNMP generated trap definitions
You can generate the following SNMP traps on BL c-Class servers and iLO 3:
ALERT_TEST is used to verify that the SNMP configuration, client SNMP console, and network are operating correctly. You can use the iLO 3 interface to generate this alert to verify receipt of the alert at the SNMP console. You can also generate this alert using the iLO 3 Option ROM to verify SNMP configuration settings. ALERT_SERVER_POWER occurs when the iLO 3 management processor detects an unexpected transition of the host system power, either from ON to OFF, or OFF to ON. Transitions of the host system power are unexpected when the change takes place because of events unknown to the management processor. This alert is not generated when the system is powered up or down using

Configuring iLO 3 49

the iLO 3 interface, CLI, RIBCL or other management feature. If the server is powered down because of the operating system, physical power button presses, or other methods, the alert is generated and sent.
ALERT_SERVER_RESET occurs when the iLO 3 management processor is used to perform a cold boot or warm boot of the host system. This alert is also sent when the iLO 3 management processor detects the host system is in reset because of events unknown to the management processor. Certain operating system behavior or actions can cause this type of event to be detected, and the alert transmitted. ALERT_ILLEGAL_LOGIN is an SNMP alert transmitted when a connection is attempted using an invalid username and password. This alert is transmitted regardless of connection type; web interface, serial port, SSH, or RIBCL. ALERT_LOGS_FULL is an SNMP alert transmitted when the iLO 3 Event Log is full and an attempt to log a new event occurs. ALERT_SELFTEST_FAILURE is an SNMP alert transmitted when iLO 3 detects an error in any one of the monitored internal components. If an error is detected an SNMP alert is transmitted. ALERT_SECURITY_ENABLED alert is transmitted when the iLO 3 management processor detects a change in the Security Override Switch to enabled. ALERT_SECURITY_DISABLED alert is transmitted when the iLO 3 management processor detects a change in the Security Override Switch to disabled. ALERT_HOST_GENERATED alert is generated when the iLO 3 management processor was asked to transmit a Host (SNMP passthrough) alert and the management processor was unable to transmit the original SNMP alert. iLO 3 attempts to transmit this generic alert to notify the SNMP management console that an alert intended to be transmitted from the host system was not transmitted.
Configuring Insight Manager Integration
The Insight Manager Web Agent URL (DNS name or IP address) sets the browser destination of the Insight Agent link on iLO 3 pages. Typically, this link is the IP address or DNS name of the management agent running on the host server operating system. Enter the IP address of the host server. The protocol (https://) and port number (:2381) are automatically added to the IP address or DNS name to allow access to the Insight Management Web Agents from iLO 3. If the Insight Manager Web Agent URL is set through another method (for example, CPQLOCFG), click the refresh button of your browser to display the updated URL. The Level of Data Returned setting controls the content of an anonymous discovery message received by iLO 3. The information returned is used for Insight Manager HTTP identification requests. The following options are available:

Using HP iLO Video Player
HP iLO Video Player enables you to playback iLO 3 console capture files without installing iLO 3 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 3 capture files are created using iLO 3 Console Capture feature, see "Using Console Capture (on page 62)." To use iLO Video Player, you must have a Microsoft Windows 2000, Windows XP, or Windows Vista operating systems, and Internet Explorer (version 6 or later) installed on your system.

Using iLO 3 63

iLO Video Player user interface
When you launch HP iLO Video Player, the user interface appears and serves as the control point for all playback functions.
iLO Video Player menu options:
OpenOpens a video capture file. ExitCloses the iLO Video Player. PlayPlays or restart the current video capture file. StopStop playback of the current video capture file. Skip to StartRestarts playback of the current video capture file. Change SpeedChanges playback speed of the current iLO video capture file. Help TopicsOpens the iLO Video Player help file. AboutOpens the iLO Video Player About page.

Controls

Using iLO 3 64
iLO Video Player controls

Control Name

Play/Pause

Function

Starts playback if the currently selected file is not playing or is paused. If playback is in progress, it pauses the file. If no file is selected, the button is disabled. Stops playback. If no file is selected, the button is disabled. Restarts playback from the beginning of the file. If no file is selected, the button is disabled. Moves the playback video forward or backward. If no file is selected, the button is disabled. Changes the playback speed of the currently selected file. The available playback speeds are 1x, 2x, 4x, 8x, and 16x. The speeds are cycled through with successive presses in the following order: 2x, 4x, 8x, 16x, and 1x. If no file is selected, the button is disabled. Displays the time parameters of the currently selected file and appears as in a HH:MM:SS format.

Stop Skip to Start Seek

Change Speed

File Position

The left time on the left indicates the current playback position of the file. The time on the right indicates the total playback time of the file.

Using iLO 3 65

Acquiring the Remote Console
If you have opened the Remote Console page and are notified that another user is currently using Remote Console, clicking the Acquire button ends the other user's Remote Console session and starts a Remote Console session in your current window.

Using iLO 3 66

When you click Acquire, you are prompted to verify that you want to interrupt the other user's Remote Console session. The other user receives a notification that another user has acquired the Remote Console session after losing the connection. No prior warning is given.
Only one acquire attempt can be made per Remote Console session window. If you have successfully acquired the Remote Console, and someone subsequently acquires it from you, you must open a new Remote Console window to attempt to acquire the Remote Console session again.

Using iLO 3 67

Java Integrated Console
Java Integrated Remote Console is a Java applet that renders the remote console with broad browser compatibility including Windows and Linux browsers. Supported browsers are listed in the "Supported browsers and client operating systems (on page 12)" section. Remote Console is a licensed feature available with the purchase of optional licenses. For more information, see "Licensing (on page 23)".
Remote Console features and controls
The Remote Console applet contains buttons that provide iLO 3 with enhanced features and control. These options are:
Refresh causes iLO 3 to refresh the screen. Ctrl-Alt-Del enters the key sequence Ctrl+Alt+Del in the Remote Console. Alt Lock, when selected, sends any key pressed to the server as if you pressed the Alt key and another key simultaneously. Character Set changes the default character set used by the Remote Console. Modifying the Remote Console character set ensures the correct display of characters. Close ends the Remote Console session and closes the Remote Console window.
Recommended client settings
Ideally, the remote server operating system display resolution should be the same resolution, or smaller, than that of the browser computer. Higher server resolutions transmit more information, slowing the overall performance. Use the following client and browser settings to optimize performance:

Display Properties

Select an option greater than 256 colors. Select a greater screen resolution than the screen resolution of the remote server.

Using iLO 3 68

Linux X Display PropertiesOn the X Preferences screen, set the font size to 12. For Remote Console speed, HP recommends using a 700-MHz or faster client with 128 MB or more of memory. For the Remote Console Java applet execution, HP recommends using a single processor client. Set the Mouse Pointer speed to the middle setting. Set the Mouse Pointer Acceleration to low or disable the pointer acceleration.

Mouse Properties

Recommended server settings
The following is a list of recommended server settings based on the operating system used. NOTE: To display the entire host server screen on the client Remote Console applet, set the server display resolution less than or equal to that of the client.

SLES 9 , SLES10 and SLES 11 The SLES 9 operating system places USB-connected CD/DVD-ROMs in a different location and the virtual CD/DVD-ROM can be found at /dev/scd0, unless there is already a USB-connected local CD/DVD-ROM, in which case, it would be /dev/scd1. The virtual CD/DVD-ROM can be mounted as a normal CD/DVD-ROM device using: mount /dev/scd0 /media/cdrom11
See "Mounting USB Virtual Media CD/DVD-ROM in Linux (on page 79)" for step-by-step instructions.
Mounting USB Virtual Media CD/DVD-ROM in Linux
Access iLO 3 through a browser. Select IRC within Remote Console section. Select the Virtual Drive tab. Select the CD/DVD-ROM to be used. Mount the drive using the following command: mount /dev/cdrom1 For SLES 9: /mnt/cdrom1

Using iLO 3 79

mount /dev/scd0

/media/cdrom1

Creating iLO 3 disk image files
The iLO 3 virtual media feature enables you to create diskette and CD-ROM image files within the same applet. Creation of DVD image files using the Virtual Media applet is not supported. The image files created from the applet are ISO-9660 file system images. The performance of iLO 3 virtual media is faster when image files are used. The utility to create iLO 3 Virtual Floppy and CD-ROM disk image files is integrated into the Virtual Media applet; however, images can also be created using industry-standard tools, such as DD. To create an image file:
Select Java Integrated Remote Console within the Remote Console section. Select the Create Disk Image option from the Virtual Drive tab. Enter the path or file name in the text box or click Browse to select an existing image file or to change the directory in which the image file will be created. Click Create. The virtual media applet begins the process of creating the image file. The process is complete when the progress bar reaches 100%. To cancel the creation of an image file, click Cancel.
The Disk>>Image option is used to create image files from physical diskettes or CD-ROMs. The Image>>Disk option is not valid for a Virtual CD-ROM image. The Disk>>Image button changes to Image>>Disk when clicked. Use this button to switch from creating image files from physical diskettes to creating physical floppy diskettes from image files.

Utility allows Lights-Out import and export and supports different user credentials for each Lights-Out processor.

Schema documentation

To assist with the planning and approval process, HP provides documentation on the changes made to the schema during the schema setup process. To review the changes made to your existing schema, refer to "Directory services Schema (on page 147)."
Directory services support
Using HP schema directory integration, iLO 3 supports the following directory services:
Microsoft Active Directory Microsoft Windows Server 2003 Active Directory Microsoft Windows Server 2008 Active Directory Novell eDirectory 8.7.3 Novell eDirectory 8.7.1
iLO 3 software is designed to run within the Microsoft Active Directory Users and Computers and Novell ConsoleOne management tools, enabling you to manage user accounts on Microsoft Active Directory or Novell eDirectory. This solution makes no distinction between eDirectory running on NetWare, Linux, or Windows. Spawning an eDirectory schema extension requires Java 1.4.0 or later for SSL authentication. iLO 3 supports Microsoft Active Directory running on one of the following operating systems:
Windows Server 2008 Windows Server 2003
iLO 3 supports eDirectory running on Novell.

Schema required software

iLO 3 requires specific software, which will extend the schema and provide snap-ins to manage the iLO 3 network. An HP Smart Component is available for download that contains the schema installer and the management snap-in installer. The HP Smart Component can be downloaded from the HP website (http://www.hp.com/servers/lights-out). You cannot run the schema installer on a domain controller that hosts Windows Server 2008 Core. Windows Server 2008 Core does not use a GUI (for security and performance reasons). To use the schema installer, you must install a GUI on the domain controller or use a domain controller that hosts an earlier version of Windows.

Schema installer

Bundled with the schema installer are one or more.xml files. These files contain the schema that will be added to the directory. Typically, one of these files will contain core schema that is common to all the supported directory services. Additional files contain only product-specific schemas. The schema installer requires the use of the.NET framework.

Directory Services objects for eDirectory
Directory Services objects enable virtualization of the managed devices and the relationships between the managed device and user or groups already contained within the directory service.

Role managed devices

The Role Managed Devices subtab under the HP Management tab is used to add the HP devices to be managed within a role. Clicking Add allows you to browse to the specific HP device and add it as a managed device.
After user objects are created, the Members tab allows you to manage the users within the role. Clicking Add allows you to browse to the specific user you want to add. Highlighting an existing user and clicking Delete removes the user from the list of valid members.
eDirectory Role Restrictions

IP/mask IP range

DNS name
You can manage the hours available for logon by members of the role by using the time grid displayed in the Role Restrictions subtab. You can select the times available for logon for each day of the week in halfhour increments. You can change a single square by clicking it, or a section of squares by clicking and holding the mouse button, dragging the cursor across the squares to be changed, and releasing the mouse button. The default setting is to allow access at all times.
In the By Default dropdown menu, select whether to Allow or Deny access from all addresses, except the specified IP addresses, IP address ranges, and DNS names. Select the addresses to be added, select the type of restriction, and click Add. In the Add New Restriction pop-up window, enter the information and click OK. The Add New Restriction pop-up for the IP/Mask option is shown. The DNS Name option allows you to restrict access based on a single DNS name or a subdomain, entered in the form of host.company.com or *.domain.company.com.
Click Apply to save the changes.
To remove any of the entries, highlight the entry in the display field and click Delete.
eDirectory Lights-Out Management
After a role is created, rights for the role can be selected. Users and group objects can now be made members of the role, giving the users or group of users the rights granted by the role. Rights are managed on the Lights Out Management Device Rights subtab of the HP Management tab.

To name the management processors, click the Name field, and enter the name, or:
After the names are correct, click Next.
Configuring directories when HP Extended schema is selected
The Configure Directory screen enables you to create a device object for each discovered management processor and to associate the new device object to a previously defined role. For example, the directory defines a user as a member of a role (such as administrator) who has a collection of privileges on a specific device object (such as a RILOE II card). The fields in the Configure Directory screen are:
Network AddressThe network address of the directory server and can either be a valid DNS name or IP address. PortThe SSL port to the directory. The default entry is 636. Management processors can only communicate with the directory using SSL. Login Name and PasswordThese fields are used to log in with an account that has domain administrator access to the directory.
Container DNAfter you have the network address, port, and login information, you can click Browse to navigate for the container and role distinguished name. The container Distinguished Name is where the migration utility will create all of the management processor objects in the directory. Role DNThe role distinguished name is where the role to be associated with the device objects resides and must be created before to running this utility. Enter the network address, login name, and password for the designated directory server. Enter the container distinguished name in the Container DN field, or click Browse. Associate device objects with a member of a role by entering the role distinguished name in the Role DN field, or click Browse. Click Update Directory. The tool will connect to the directory, creates the management processor objects, and adds them to the selected roles. After the device objects have been associated with a role, click Next.
To configure the device objects to be associated with a role:
Configuring directories when schema-free integration is selected
The fields in the Configure Management Processors screen are:
Network AddressThe network address of the directory server, which can be a valid DNS name or IP address. Login Name and PasswordThese fields are used to log in with an account that has domain administrator access to the directory. Security Group Distinguished NameThe distinguished name of the group in the directory that contains a set of iLO 3 users with a common set of privileges. If the directory name, login name, and password are correct, you can click the Browse button to navigate to and select the group. PrivilegesThe iLO 3 privileges associated with the selected group. The login privilege is implied if the user is a member of the group.

The network connection is severed. The directory server is shut down.
iLO 3 Management Port not accessible by name
Solution: The iLO 3 Management Port can register with a WINS server or DDNS server to provide the name-to-IP address resolution necessary to access the iLO 3 Management Port by name. The WINS or DDNS server must be up and running before the iLO 3 Management Port is powered on, and the iLO 3 Management Port must have a valid route to the WINS or DDNS server. In addition, the iLO 3 Management Port must be configured with the IP address of the WINS or DDNS server. You can use DHCP to configure the DHCP server with the necessary IP addresses. You can also enter the IP addresses through RBSU or by selecting Network Settings on the Administration tab. The iLO 3 Management Port must be configured to register with either a WINS server or DDNS server. These options are turned on as factory defaults and can be changed through RBSU or by selecting the Network Settings option on the Administration tab. The clients used to access the iLO 3 Management Port must be configured to use the same DDNS server where the IP address of the iLO 3 Management Port was registered.
Troubleshooting iLO 3 159
If you are using a WINS server and a non-dynamic DNS server, the access to the iLO 3 Management Port might be significantly faster if you configure the DNS server to use the WINS server for name resolution. For more information, see the appropriate Microsoft documentation.
iLO 3 RBSU unavailable after iLO 3 and server reset
Solution: Reset the server a second time. To avoid this issue, wait a few seconds before resetting the server after resetting the iLO 3 processor. If the iLO 3 processor is reset and the server is immediately reset, iLO 3 firmware might not be fully initialized when the server performs its initialization and attempts to invoke the iLO 3 RBSU. In this case, the iLO 3 RBSU is unavailable, or the iLO 3 Option ROM code is skipped altogether.
Unable to access the login page
Solution: Verify the SSL encryption level of your browser is set to 128 bits. The SSL encryption level in iLO 3 is set to 128 bits and cannot be changed. The browser and iLO 3 encryption levels must be the same.
Unable to return to login page after an iLO flash or reset
Solution: Clear your browser cache and restart the browser.
Unable to access virtual media or graphical remote console
Solution: Virtual media and graphical Remote Console are only enabled by licensing the optional iLO Advanced Pack. A message is displayed to inform the user that the features are not available without a license. Although up to 10 users can to log in to iLO 3, only one user can access the remote console. A warning message is displayed indicating that the Remote Console is already in use.
Unable to connect to iLo 3 after changing network settings
Solution: Verify that both sides of the connection, the NIC and the switch, have the same settings for transceiver speed autoselect, speed, and duplex. For example, if one side is autoselecting the connection, then the other side should as well. The settings for the iLO 3 NIC are controlled in the Network Settings screen.

Before you contact HP

Be sure to have the following information available before you call HP:
Technical support registration number (if applicable) Product serial number Product model name and number Product identification number Applicable error messages Add-on boards or hardware Third-party hardware or software Operating system type and revision level
Acronyms and abbreviations
Advanced Configuration and Power Interface
Address Resolution Protocol
American Standard Code for Information Interchange
Advanced Server Management
Automatic Server Recovery
baseboard management controller

certificate authority

Command Line Interface

command line protocol

Certificate Request
certificate revocation list
Distributed Authoring and Versioning
Dynamic Domain Name System
Dynamic Host Configuration Protocol

dynamic link library

Distributed Management Task Force

domain name system

Digital Video Out
Environment Abnormality Auto-Shutdown
Enclosure Bay IP Addressing
Emergency Management Services
end user license agreement

fatal exception handler

GNU Network Object Model Environment

graphical user interface

heartbeat

High Efficiency Mode

human interface device

HP SIM

HP Systems Insight Manager

HPONCFG

HP Lights-Out Online Configuration utility

HPQLOMGC

HP Lights-Out Migration Command Line

HPQLOMIG

HP Lights-Out Migration
Internet Control Message Protocol

Integrated Lights-Out

Integrated Lights-Out 2

Internet Protocol

Intelligent Platform Management Interface
Integrated Remote Console

interrupt request

Java Virtual Machine
Keyboard Controller Style
K Desktop Environment (for Linux)
keyboard, video, and mouse