HP ProLiant Lights-Out 100 Remote Management User Guidecontent.etilize.com/User-Manual/1020446952.pdf · HP ProLiant Lights-Out 100 delivers basic remote control of vital server resources,

HP ProLiant Lights-Out 100 Remote Management User Guide for HP ProLiant ML110 G5 Servers

Part Number 465225-001 November 2007 (First Edition)

© Copyright 2007 Hewlett-Packard Development Company, L.P.

The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license.

Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. Windows Server 2003 is a U.S. trademark of Microsoft Corporation. Java is a U.S. trademark of Sun Microsystems, Inc.

Audience assumptions

This document is for the person who installs, administers, and troubleshoots servers and storage systems. HP assumes you are qualified in the servicing of computer equipment and trained in recognizing hazards in products with hazardous energy levels.

Contents 3

Contents

Operational overview ................................................................................................................... 5 Server management................................................................................................................................... 5 Server management features....................................................................................................................... 5

LO100 standard features.................................................................................................................. 6 LO100 optional features .................................................................................................................. 6

Installation of the HP Lights-Out 100c Remote Management Card....................................................... 7 Remote management card kit contents.......................................................................................................... 7 Preinstallation procedures........................................................................................................................... 7 Installing the remote management card ........................................................................................................ 8 Post-installation procedures ......................................................................................................................... 8

Configuration ............................................................................................................................... 9 Configuring network access........................................................................................................................ 9 Configuring user accounts .......................................................................................................................... 9 Using the serial port .................................................................................................................................. 9

Enabling serial access to the LO100 ................................................................................................ 10 Configuring the LO100 serial port ................................................................................................... 10

Using TCP/IP over Ethernet management port ............................................................................................. 10 Selecting a shared Ethernet management port ................................................................................... 10 Obtaining a DHCP IP address from the BIOS Setup Utility................................................................... 11 Setting up a static IP address from the BIOS Setup Utility .................................................................... 11 Enabling telnet and HTTP services.................................................................................................... 12

Updating the firmware ............................................................................................................................. 12 Updating the firmware remotely ...................................................................................................... 12 Flashing previous firmware versions on an HP ProLiant ML110 G5 Server ............................................ 13

Using LO100 ............................................................................................................................. 14 New features .......................................................................................................................................... 14 Using SSL............................................................................................................................................... 14 Using SSH.............................................................................................................................................. 14

Using the SSH utility....................................................................................................................... 15 Using the PuTTY utility .................................................................................................................... 15 Using the OpenSSH utility............................................................................................................... 15

Using CLP............................................................................................................................................... 16 CLP syntax.................................................................................................................................... 16 Base commands ............................................................................................................................ 17 Specific commands........................................................................................................................ 21

IPMI 2.0 support ..................................................................................................................................... 21 Logging in to LO100 ............................................................................................................................... 21

Logging in through a web browser .................................................................................................. 22 Logging in through the CLP ............................................................................................................. 22

Browser main menu options...................................................................................................................... 23 Controlling server power remotely ............................................................................................................. 24

Controlling server power from a browser.......................................................................................... 24 Controlling server power through the CLP ......................................................................................... 24

Monitoring sensors .................................................................................................................................. 25

Contents 4

Viewing sensors data from a web browser ....................................................................................... 25 Viewing sensors data from the BIOS Setup Utility............................................................................... 25 Platform event filtering configuration ................................................................................................ 26

Using the system event log........................................................................................................................ 27 Accessing the system event log from a web browser .......................................................................... 27 Accessing the system event log from the CLP ..................................................................................... 27 Accessing the system event log from the BIOS Setup Utility.................................................................. 28

Using Virtual KVM................................................................................................................................... 28 Using the remote graphic console .................................................................................................... 30 System buttons .............................................................................................................................. 32

Using Virtual Media................................................................................................................................. 33 Adding a virtual media device ........................................................................................................ 34 Shared virtual media devices .......................................................................................................... 35

Accessing the remote console through telnet ............................................................................................... 35 Redirecting BIOS console text through telnet...................................................................................... 35 Redirecting a Linux console............................................................................................................. 36 Microsoft Windows EMS management ............................................................................................. 37

Hardware Inventory page ........................................................................................................................ 38 User administration.................................................................................................................................. 38

Changing user settings through a web browser ................................................................................. 39 Changing user settings through the CLP ............................................................................................ 39

Network settings ..................................................................................................................................... 40 Configuring network settings using a web browser ............................................................................ 40 Configuring network settings using the CLP ....................................................................................... 40 Configuring network settings using the BIOS Setup Utility.................................................................... 41

Platform event trap configuration ............................................................................................................... 42 Importing a certificate .............................................................................................................................. 42

Creating a certificate ..................................................................................................................... 43 Installing a certificate or private key through a web browser ............................................................... 44 Installing a certificate or private key through the CLP .......................................................................... 44

HP SIM support ....................................................................................................................................... 45

Technical support........................................................................................................................ 46 HP contact information............................................................................................................................. 46 Before you contact HP.............................................................................................................................. 46

Acronyms and abbreviations........................................................................................................ 47

Index......................................................................................................................................... 50

Operational overview 5

Operational overview

Server management HP ProLiant Lights-Out 100 delivers basic remote control of vital server resources, supports IPMI 2.0, and provides system administrators with access to the server at any time, even before an operating system is installed on the server.

HP ProLiant Lights-Out 100 provides text mode console redirection, DMTF SMASH compliant command line interface, and browser access to many of the same system management functions. You can access LO100 through a dedicated Ethernet port or through the server serial port.

Server management features With HP ProLiant Lights-Out 100, you can perform the following tasks:

• Access a remote graphic console (Virtual KVM)

• Access the serial console of the host operating system over the network using standards-based client utilities

• Switch between serial console redirection or the LO100 command line interface

• Communicate securely using SSL and SSH

• Remotely control the power button of the server (power on and off the server), or perform warm or cold server reboots

• Remotely monitor fan speed and system power state (S0 or S5)

• Access the system event log

• Access virtual media

• Configure TCP/IP settings for the LO100 NIC

• Control user access

• Discover, identify, and launch LO100 from HP SIM

• Access LO100 and server controls using a standard browser or new industry-standard SMASH CLP command line interface

• Access command line help

• Manage the server with IPMI 2.0 compliant applications

• Access telnet

Not all of the features displayed and described in the guide are available on all systems. To verify which features are supported on your system, see "LO100 standard features (on page 6)" and "LO100 optional features (on page 6)" for more information.

Operational overview 6

LO100 standard features For HP ProLiant ML110 G5 Servers, LO100 standard features are in-band IPMI 2.0 elements available through the operating system.

LO100 optional features For HP ProLiant ML110 G5 Servers, LO100 optional features are activated with installation of the HP Lights-Out 100c Remote Management Card and include the following:

• Support for SSL, SSH, and IPMI 2.0 security with factory-default self-signed certificates and keys

• Support for imported certificates

• Virtual media access

• Remote graphic console (Virtual KVM) access

Installation of the HP Lights-Out 100c Remote Management Card 7

Installation of the HP Lights-Out 100c Remote Management Card

Remote management card kit contents For HP ProLiant ML110 G5 Servers, installation of the HP Lights-Out 100c Remote Management Card is required to activate the optional features. For more information, see "LO100 optional features (on page 6)".

The HP ProLiant Lights-Out 100c Remote Management Card Kit includes the following components:

• HP Lights-Out 100c Remote Management Card

• Spacer support

• Remote management card installation instructions

Preinstallation procedures The installation procedures in this document are intended for individuals who are qualified in the servicing of computer equipment and trained in recognizing hazards in products with hazardous energy levels.

WARNING: Failure to properly turn off the server before you open the server may cause serious damage to the equipment as well as bodily harm.

CAUTION: Follow the ESD precautions listed in your server guide when handling the remote management card.

IMPORTANT: Observe the pre- and post-configuration procedures described in later sections when installing the remote management card.

NOTE: The procedures described in this section assume that the server is positioned on a flat, stable surface.

1. Back up the server data.

2. Shut down the operating system as outlined in the operation system instructions.

3. Power off the server and all the peripherals connected to it.

4. Unplug all cables from the power outlets to avoid exposure to high energy levels that can cause burns when parts are short-circuited by metal objects such as tools or jewelry.

5. Label each cable, if not already labeled, to expedite reassembly.

6. Disconnect telecommunication cables to avoid exposure to shock hazard from ringing voltages.

7. Open the server according to the instructions described in your server manual.

Installation of the HP Lights-Out 100c Remote Management Card 8

Installing the remote management card 1. Remove the access panel.

2. Carefully lay the server on its unexposed side to gain access to the system board.

3. Locate the remote management card connectors on the system board.

4. Install the remote management card in the connectors on the system board.

Post-installation procedures 1. Be sure all components are installed according to the installation procedures.

2. Be sure you have not left any loose tools or parts inside the server.

3. Reinstall any expansion boards, peripherals, board covers, and system cables previously removed.

4. Reinstall the system covers.

5. Connect all external cables and the AC power cord to the system.

6. Press the power button on the front panel to power on the server.

Configuration 9

Configuration

Configuring network access Through your server network connection, you can access the remote management CLP, verify POST remotely, and access the BIOS Setup Utility remotely.

To configure network access:

1. Connect a standard Ethernet cable from the NIC port on the LO100 to a network jack.

2. Press the F10 key during POST, and then obtain the IP address from BIOS Setup Utility under the Advanced/IPMI/LAN Setting. For more information, see "Obtaining a DHCP IP address from the BIOS Setup Utility (on page 11)".

By default, LO100 has DHCP enabled and automatically negotiates an IP address.

3. With the DHCP IP address, use telnet to log in to the remote management CLP, or use a web browser to access the HTML interface.

To set up and use a static IP address instead of using DHCP, see "Setting up a static IP address from the BIOS Setup Utility (on page 11)".

Configuring user accounts LO100 supports four accounts types, with varying levels of permissions to view and control features. For more information on user accounts, see the "User administration (on page 38)" section. Two accounts are available by default, one of type administrator and one of type operator.

The administrator account enables the user to execute the full set of CLP commands and change management processor configuration. The default administrator account user name is admin, and the default password is admin.

The operator account enables the user to execute common commands and functions but restricts access to specific functions, such as adding and changing user account information and changing the configuration of the management processor. HP recommends logging in with the operator account to perform common functions. The default user name is Operator, and the default password is Operator.

For more information on how to log in to LO100, see the "Logging in to LO100 (on page 21)" section.

Using the serial port The server serial port provides basic serial port functionality and serves as an interface to LO100. You can configure the system serial port for exclusive use with LO100.

CAUTION: After enabling the serial port for use with LO100, legacy serial devices might not function correctly if attached to the serial port.

Configuration 10

You must configure the LO100 serial port hardware parameters to work with your respective serial port communications software. LO100 serial port configuration is controlled through the BIOS Setup Utility.

Enabling serial access to the LO100 1. Power up the server.

2. When POST displays the message, ROM-Based Setup, press the F10 key. If the server has an administrator password configured, the system prompts you to enter the password. If the server does not have a password configured, the main screen of the BIOS Setup Utility appears.

3. Press the right arrow (→) key to navigate to the Advanced menu.

4. Press the down arrow (↓) key to scroll to IPMI. Press the Enter key.

5. Press the down arrow (↓) key to scroll to Serial Port Assignment. Toggle between System and BMC by pressing the Enter key. Select System.

6. Press the down arrow (↓) key to scroll to Serial Port Switching. Select Enabled.

7. Press the down arrow (↓) key to scroll to Serial Port Connection Mode. Select Direct.

8. Press the Esc key to return to the Advanced menu.

9. Press the down arrow (↓) key to scroll to IO Device Configuration. Press the Enter key.

10. Select Serial Port A, and then toggle between Enabled and Disabled by pressing the Enter key. Select Enabled.

11. Press the F10 key to save and exit.

Configuring the LO100 serial port 1. Power on the server by pressing the Power On/Off button on the front panel.



4. Press the down arrow (↓) key to scroll to the Console Redirection menu. Press the Enter key.

5. Set the Serial Port Address to COM A.

6. Review the serial port settings, and make sure the settings match the serial port communications software settings used to connect to LO100.

7. To return to the previous screen, press the Esc key, or to save the changes and exit Setup, press the F10 key.

Using TCP/IP over Ethernet management port You can configure LO100 LAN port access using two different Ethernet ports: the dedicated 10/100 LO100 management port or through a side-band connection using the server NIC. The side-band, shared, or UMP options utilize one server Ethernet port for both server network traffic and LO100 network traffic reducing the number of network cables that you must attach to the server.

Selecting a shared Ethernet management port 1. Power on the server by pressing the Power On/Off button on the front panel.

Configuration 11



4. Press the down arrow (↓) key to scroll to IPMI Configuration. Press the Enter key.

5. Scroll to the Share NIC Mode option by pressing the down arrow (↓) key. Toggle between Enabled and Disabled by pressing the Enter key. Select Enabled.


The TCP/IP over Ethernet management port, whether dedicated or shared, is a standard Ethernet 10/100Mb interface that is connected to the network using a standard Ethernet cable. Before using the dedicated management port, you must determine the DHCP IP address, set a static IP address, or use the default static IP address.

Obtaining a DHCP IP address from the BIOS Setup Utility By default, LO100 has DHCP enabled and automatically negotiates an IP address. To view the DHCP IP address, run the BIOS Setup Utility, or retrieve the DHCP IP address using CLP through the serial port connection. To view the DHCP IP address using the BIOS Setup Utility:

1. Power on the server by pressing the Power On/Off button on the front panel.




5. Press the down arrow (↓) key to scroll to the end of the menu to display the DHCP IP address.


To configure or change your network settings, see "Network settings (on page 40)".

Setting up a static IP address from the BIOS Setup Utility By default, LO100 has DHCP enabled and automatically negotiates an IP address. To disable DHCP and enable a static IP address:

1. Press the F10 key during POST to enter the BIOS Setup Utility.



4. Press the down arrow (↓) key to scroll to the end, and then select DHCP IP Source.

5. Set DHCP IP Source to Disabled.

6. Press the down arrow (↓) key to scroll down and enter a valid IP address, subnet mask, and gateway address (press the Tab key to move between address fields).


To restore DHCP, see "Configuring network settings using the BIOS Setup Utility (on page 41)."

Configuration 12

Enabling telnet and HTTP services On HP ProLiant ML110 G5 Servers, HTTP and telnet are enabled after installing the HP ProLiant Lights-Out 100c Remote Management Card.

Updating the firmware To update the LO100 firmware, use the ROMPaq utility. Downloads for the ROMPaq utility are available on the HP website (http://www.hp.com/support). For more information about using the ROMPaq utility, refer to the HP website (http://www.hp.com/servers/manage).

NOTE: LO100 does not support ROMPAQ flashing from a virtual floppy.

After the ROMPaq utility flashes the selected device, cycle power manually to reboot the operating system.

Updating the firmware remotely Use the load command to update the LO100 firmware remotely. The firmware file must be an uncompressed firmware image file created using the DOS ROMPAQ utility found on the Lights-Out 100 Firmware Upgrade Diskette Utility, which is available for download from the HP website (http://www.hp.com/servers/lights-out).

To create an uncompressed image file, enter the following command at the DOS prompt: ROMPAQ /D <infile> <outfile>

where <infile> is the ROMPAQ firmware image file and <outfile> is the file name for the uncompressed binary image file. For example:

ROMPAQ /D cpqq0801.D14 ldrImage.bin

ROMPAQ Firmware Upgrade Utility, Version 5.02 (R)

Copyright (c) Hewlett-Packard Corporation, 1994-2006

Input file: CPQQ0801.D14

Output file: LDRIMAGE.BIN

The load command is used to retrieve a binary image from a specific source location (specified as a URL) and place it at the specified target address.

The load command can download and flash an ldr firmware image file using TFTP from the specified location.

To flash the firmware using TFTP settings on Windows®:

1. Copy the BMC firmware into a directory on the server.

2. Run TFTP by launching the executable file tftpd32.exe.

3. Navigate to TFTP configuration>Settings, and set Timeout to 30 seconds and Max Retransmit to 6.

4. Enter File Name and TFTP Server IP Address. File Name is the path where the BMC firmware is residing. TFTP Server IP Address is the IP address of the TFTP server (for example, 10.141.38.157).

Flashing the firmware using TFTP settings on Linux:

1. Navigate to Applications>Systems Settings>Server Settings>Services and make sure that TFTP and xinetd are running.

http://www.hp.com/support

http://www.hp.com/servers/manage

http://www.hp.com/servers/lights-out

Configuration 13

2. Open the /etc/xinetd.d/tftp file and modify the parameter server_args to include -T 15000000. For example, server_args = -c -s /tftpboot -T 15000000.

3. If a firewall is enabled, disable it or modify the settings to allow the firewall to connect to the TFTP port. To change the firewall settings, navigate to Applications>System Settings>Security Level, and enter 69:udp in the parameter of the other port.

To update the firmware, log in to LO100 as the administrator through the CLP interface, and issue the load command to upload and install the firmware from the map1/firmware directory.

1. Start a CLP session. To access CLP:

a. Navigate to Start>All Programs>Accessories>Command Prompt.

b. At the command prompt, enter telnet <IP address>.

2. At the CLP prompt, enter cd map1/firmware.

3. At the CLP prompt, enter load -source <URI> -oemhpfiletype csr

where:

o <URI> is the //<tftp server IP>/<filename> to be downloaded.

o <tftp server IP> is the URL or IP address of the TFTP server containing the firmware.

o <filename> is the file name of the image file (LdrImage.bin in this example).

For example, enter load -source //10.141.38.157/LdrImage.bin - oemhpfiletype csr.

The TFTP application might report an error in the early part of the firmware upload process, during the firmware image validation process. An error does not necessarily indicate failure of the firmware upload and does not prevent successful firmware uploads. A successful firmware upload typically takes several minutes. After the firmware upgrade process is complete, verify that the new version of the firmware is active.

If the firmware upgrade process fails after sufficient time (at least 5 minutes), reboot the server, and verify that the previous version of the firmware is still active. Always reboot the server before retrying the firmware upgrade process.

After installing the firmware, the IP address of the server might reset to the default value. You must locally reset the IP address to the desired address.

NOTE: After using the load command LO100 will reset ending your CLP interface session. You must reconnect to the CLP interface.

NOTE: When you use the CLP load command with TFTPD32, HP recommends using a 30-second timeout and 6 retries.

Flashing previous firmware versions on an HP ProLiant ML110 G5 Server

When an HP Lights-Out 100c Remote Management Card is installed in an HP ProLiant ML110 G5 Server, you can flash the LO100 to an earlier version. In the map1 directory, enter the CLP command oemhp i 20 20 c0 18 00 04 04 e0. This command reactivates the previous version.

Using LO100 14

Using LO100

New features This release of LO100 adds support for the following:

• Virtual DVD-R

• Virtual media ISO images

• DMTF SMASH Profiles

• WS-Management

• HP SIM License Manager support

Using SSL SSL is a protocol used to transmit private documents through the Internet. SSL uses a private key or certificate to encrypt data transferred over the SSL connection. The Lights-Out 100 remote management processor provides security for remote management in distributed IT environments by using an industry-standard encryption protocol for data traveling on unsecured networks.

SSL is an advanced feature available by installing the Lights-Out 100c Remote Management Card or purchasing the Lights-Out 100i Select Pack or the Lights-Out 100i Advanced Pack. For more information, see the section, "LO100 optional features (on page 6)."

LO100 comes preinstalled with a certificate. To install a user-specific certificate, see the one-time "Importing a certificate (on page 42)" setup procedure.

If you cannot access the login page, you must verify the SSL encryption level of your browser is set to 128 bits. The SSL encryption level within the management processor is set to 128 bits and cannot be changed. The browser and management processor encryption levels must be the same.

To use the preinstalled certificate, enter https://ipaddress in the address line of the browser, which uses SSL-encrypted communication. Enter http://ipaddress to use non-SSL encrypted communication.

Using SSH SSH is a telnet-like program for logging in to and executing commands on a remote machine, which includes security with authentication, encryption, and data integrity features. The Lights-Out 100 remote management processor can support simultaneous access from two SSH clients. After SSH is connected and authenticated, the command line interface is available. LO100 supports two simultaneous SSH connections.

SSH is an advanced feature available by installing the Lights-Out 100c Remote Management Card or purchasing the Lights-Out 100i Select Pack or the Lights-Out 100i Advanced Pack. For more information, see the section, "LO100 optional features (on page 6)."

Using LO100 15

LO100 supports the following protocols:

• SSH protocol version 2

• PuTTY 0.54 or later.

• OpenSSH

LO100 comes preinstalled with a certificate. To install a user-specific certificate, see the one-time "Importing a certificate (on page 42)" setup procedure.

Using the SSH utility When using a SSH utility to connect to a server for the first time, the utility prompts you to accept the server public key, sometimes referred to as a host key. Accepting this key authorizes the utility to store a copy of the public key in its own database. The utility recognizes the server when future connections are attempted by comparing the public key to the one stored in its database.

NOTE: Logging in to an SSH session could take up to 90 seconds. Depending on the client used, you might not see on-screen activity during this time.

To access the remote management processor using SSH:

1. Open an SSH window.

2. When prompted, enter the IP address, login name, and password.

Using the PuTTY utility PuTTY 0.54 is a terminal emulation product that includes support for telnet and the SSH protocol. PuTTY 0.54 is available for download from the Internet.

• To start a PuTTY session, double-click the PuTTY icon in the directory in which PuTTY is installed.

• To start a PuTTY session from the command line:

o To start a connection to a server called host, enter: putty.exe [-ssh | -telnet | -rlogin | -raw] [user@]host

o For telnet sessions, you can also enter the following alternative syntax: putty.exe telnet://host[:port]/

o To start an existing saved session called session name, enter: putty.exe -load "session name"

When you press Enter using PuTTY versions earlier than 0.54, two line feeds might appear on a single line feed. To avoid this issue and for best results, HP recommends using version 0.54 or later.

Using the OpenSSH utility OpenSSH is a free version of the SSH protocol available for download on the Internet.

To start an OpenSSH client in Linux, at the command prompt enter: ssh -l loginname ipaddress/dns name

Using LO100 16

Using CLP HP has worked with key industry partners within Distributed Management Task Force, Inc. to define an industry-standard set of commands. The SMASH suite will standardize manageability interfaces for servers. The Lights-Out 100 remote management processor implements the command set defined in the Server Management Command Line Protocol Specification, 1.00 Draft. The CLP replaces the simple CLI that was released previously and is no longer supported.

The management processor functionality accessible from the SMASH CLP is a low-bandwidth interface and provides similar functionality to the web interface. The CLP is designed for users who prefer a nongraphical interface. The CLP is accessible through the following methods:

• Telnet

• SSH connection

• Physical serial port

LO100 CLP supports two simultaneous SSH connections, two SSH connections and one telnet connection, or one SSH connection and two telnet connections. You cannot have more than two simultaneous SSH connections and up to three (telnet and SSH) connections at a time.

CLP syntax The general syntax of CLP command is:

<verb> <target> <option> <property>

• Verbs—The following verbs are supported: o cd

o help

o load

o reset

o set

o show

o start

o stop

o exit

o version

• Target—The default target is the /. The target can be changed by the cd command or by specifying a target on the command line.

• Options—The following options are valid: o -help/-h

o -all/-a

• Properties are the attributes of the target that can be modified.

• Output—The output syntax is text.

The valid Boolean values for any command are true and false.

General notes

Using LO100 17

If the commands on the CLP command span more than one line, you cannot navigate between different lines.

Operating system-specific notes

• The Microsoft® Windows® 2000 telnet client does not support the Functions keys F1 through F12, Insert, Home, and End keys. These keys will not work in a Lights-Out 100 command line session.

• The Backspace key in the Lights-Out 100 CLP implementation is mapped to the value 0x8. Some client operating systems, Novell Linux Desktop and Red Hat Enterprise Linux 4 Desktop, map the Backspace key to the value 0x7f, which is used for the Delete key in the Windows® telnet client. The Backspace key will not work from a client from which it has value of 0x7f. For the Linux clients, using the Home or the End key enables the Lights-Out 100 CLP service to remap the Backspace key to use the value 0x7f, making the key functional.

In the Windows® PuTTY client, the Backspace key can be mapped to a value of 0x8 by changing the setting for Terminal Keyboard to Control-H.

Base commands • The help command displays context-sensitive help.

Entering help displays all the supported commands. Entering <command help/?> displays the help message specific to that command.

o Help for verbs

Calling help for a verb returns the general syntax and usage associated with issuing that verb. Calling help for a verb that is not present in the current directory returns an Unsupported Command message. The following examples are all valid ways to call help for a verb.

— /./-> help show Usage: show [<target>][<options>][<properties>]

— /./-> show -h Usage: show [<target>][<options>][<properties>]

— /./-> show -help Usage: show [<target>][<options>][<properties>]

— /./->

o Help for targets

Calling help for a target returns any information about the target and what it contains. You can call help for any target that is not contained in the current directory (help map1 can be called from system1).

— /./-> system1 -h Invalid command

— /./-> system1 -help Invalid command

— /./-> help system1 Host System Directory

— /./-> help map1 Management Service Processor Directory

Using LO100 18

— /./-> cd system1

— /./system1/-> help map1 Management Service Processor Directory

o Help for properties

Calling help for a property or any other option for which there is no help information returns an Unsupported Command or Invalid command message. For example: /./system1/-> show

/./system1

Targets

log1

Properties

name=Hewlett-Packard

enabledstate=enabled

Verbs

cd

version

exit

show

reset

start

stop

help

/./system1/-> help name

Unsupported Command

/./system1/-> help enabledstate

Unsupported Command

/./system1/-> help properties

Unsupported Command

/./system1/-> name -h

Invalid command

/./system1/->

• The exit command terminates the CLP session.

• The cd command sets the current default target. The context works like a directory path. The root context for the server and the starting point for a CLP system is /. (forward slash period). By changing the context, you can shorten commands.

For example:

Using LO100 19

o The cd command changes the directory.

o The cd .. command moves up the tree one directory.

o The cd myfolder command moves to the myfolder folder assuming myfolder is in the current directory.

To move to a directory not in the current directory, you must enter the full path. The root in the command line is forward slash, period, forward slash (/./).

If you are in the system1 folder and want to move to the map1 folder, issue the command cd /./map1. Neither cd /map1 nor cd map1 works. The filename is not case-sensitive, whereas the command is case-sensitive (cd MaP1 works while CD map1 does not).

• The show command displays values of a property or contents of a collection target. For example: /./> show

/.

Targets

system1

map1

Properties

Verbs

cd

version

exit

show

help

The first line of information returned by the show command is the current context. In the example, / is the current context. Following the context is a list of subtargets (Targets) and properties (Properties) applicable to the current context. The verbs section (Verbs) shows what commands are available in this context.

The show command can also be specified with an explicit or implicit context and a specific property. An explicit context is /map1/firmware and is not dependent on the current context. An implicit context assumes that the context specified is a child of the current context. If the current context is /map1, then a show firmware command displays the /map1/firmware data. If a property is not specified, then all properties are shown.

• The load command moves a binary image from a URL to the map. The load command is used to take a binary image from a specific source location (specified as a URL) and place it at the specified target address. In a remote management processor implementation, the firmware downloads a full image file using TFTP from the specified location and programs flash with the image.

In a remote management processor implementation, /map1/firmware is a valid target.

The load command supports usage only with the following options.

o -source <location>—This option must be specified.

o (h)elp—This option appears on the command line, the command ignores all options and properties except -output (for terse or verbose output). These options are only valid for this command when the -help option is used.

o source <value>—This option specifies the target from which it transfers the binary image. The value specified must be a valid URL. The format is //tftpserverip/path/filename. This

Using LO100 20

option is required in the command line every time the load command is executed unless -help is used. The file must be an uncompressed firmware image file that you create using the DOS ROMPAQ utility found on the Lights-Out 100 Firmware Upgrade Diskette Utility available for download from the HP website (http://www.hp.com/servers/lights-out).

To create the uncompressed image file, enter the following command from DOS: ROMPAQ /D <infile> <outfile>

where <infile> is the ROMPAQ firmware image file and <outfile> is the filename for the uncompressed binary image file.

The load command returns any status data on the first lines. After the status data appears, one of the following lines of text displays on the next line:

— <URL> transferred to <target address> (if the file is transferred)

— <URL> not transferred (if the file is not transferred)

Example: load -source //192.168.2.1/pub/firmwareimage.bin -oemhpfiletype csr

//192.168.2.1/pub/firmwareimage.bin transferred to /map1/firmware/fullimage

• The reset command causes a target to cycle from enabled to disabled and then back to enabled.

• The set command assigns a specific value to a property or group of properties. The standard syntax for the set command is set property = new value.

The set command is used to change any changeable property. If the current directory does not contain the property you want to change, the target of the property must be specified before entering the property you want to change.

• The start command causes a target to change state to a higher run level.

• The stop command causes a target to change state to a lower run level.

• The version command queries the version of the CLP implementation or other CLP elements. For example: /./map1/-> version Version 1.00 /./map1/-> cd firmware /./map1/firmware/-> version Version 1.00 /./map1/firmware/-> show

/./map1/firmware

Targets

Properties

fwversion=0.59

Verbs

cd

version

exit

show

reset

load

http://www.hp.com/servers/lights-out

Using LO100 21

help /./map1/firmware/-> show fwversion fwversion=0.59 /./map1/firmware/-> fwversion Invalid command /./map1/firmware/->

Specific commands CLP syntax for specific commands is found in the sections that also describe the functionality through the Web interface.

IPMI 2.0 support LO100 supports the industry-standard IPMI 2.0. The IPMI specification defines standardized, abstracted interfaces that can be used for monitoring and control functions that are built in to the platform hardware.

In addition to supporting the mandatory commands for IPMI 2.0, the following additional IPMI 2.0 features are supported by LO100:

• Additional IPMI 2.0 commands

o Get Channel Cipher Suites

o Set/Get Channel Security Keys

o Suspend/Resume Payload Encryption

• Payload types

o IPMI Message

o RMCP+ Open Session Request/Response

o RAKP Message 1 / 2

o RAKP Message 3 / 4

• Authentication algorithms

o RAKP-none

o RAKP-HMAC-SHA1

• Integrity algorithms

o None

o HMAC-SHA1-96

• Confidentiality algorithms

o None

o AES-CBC-128

Logging in to LO100 You can log in to the remote management processor through a web browser ("Logging in through a web browser" on page 22) or through the CLP ("Logging in through the CLP" on page 22). If you are unsure of your DHCP IP address, refer to the "Configuring network access (on page 9)" section.

Using LO100 22

Logging in through a web browser 1. Browse to the IP address of the remote management processor to access the login screen.

2. Enter your user name and password. The default user name for the Administrator account is admin, and the default password is admin. The default user name for the Operator account is Operator, and the default password is Operator.

Logging in through the CLP 1. Establish a connection to the remote management processor by launching a telnet session or an SSH

session.

2. Enter the user name at the login prompt. The default user name for the Administrator account is admin. The default user name for the Operator account is Operator.

3. Enter the password at the password prompt. The default password for the Administrator account is admin. The default password for the Operator account is Operator.

4. To exit the CLP and enter Console mode, enter the exit command at the command prompt.

Using LO100 23

Browser main menu options Using a web browser, you can access all of the basic remote management capabilities of LO100. Not all of the features displayed and described in the guide are available on all systems. To verify which features are supported on your system, see "LO100 standard features (on page 6)" and "LO100 optional features (on page 6)" for more information.

Option Description

Summary Accesses or returns you to the main menu navigation bar

Virtual Power Accesses system power and UID control options

Monitoring Sensors Lists all sensor information, including type, name, status, reading, and PEF settings

System Event Log Displays the system event log

Virtual KVM/Media Accesses virtual media or the remote graphic console

Hardware Inventory Displays system hardware information

User Administration Accesses the user configuration screen

Network Settings Accesses the network parameter settings screen

IMPI PET Configuration Accesses the PET destinations and alert policy table

Application License Key Displays the licensing screen

Security Settings Accesses LO100 security, personal certificate and key installation options

NOTE: The Virtual KVM / Media option is an advanced feature and not available on all systems. This link may appear as Virtual Media or not at all depending on your system implementation. To verify which features are supported on your system, see "LO100 standard features (on page 6)" and "LO100 optional features (on page 6)" for more information.

Using LO100 24

Controlling server power remotely LO100 enables you to remotely operate the power button of a host server using a web browser or the CLP. LO100 virtual power support enables you to power on, power off, and power cycle the host server. This virtual power support operates independently of the state of the operating system.

Controlling server power from a browser The Virtual Power screen displays current power status, how long the server has been powered on, and the reason for the last server restart. To display the Virtual Power screen, on the main menu navigation bar, click Virtual Power.

To modify Chassis Actions, select a Power Control Option in the Chassis Actions section, and then click Apply.

To identify the server in the rack and illuminate the UID (the LED on the front panel of the server), from the UID list, select the length of time for the UID to illuminate, and then click Identify.

A restore policy controls how the system responds when power is connected to the server. To set a restore policy:

1. Select the Power Restore Policy by choosing one of the following options:

o Always power up—Powers on the server immediately after power is supplied.

o Restore to powered state prior to power loss—Powers on the system if the system was in the powered on state before a loss of power.

o Power pushbutton or command required to power on system—Causes the server to wait for external action before powering on the system.

2. Click Set.

Controlling server power through the CLP 1. Log in to LO100 CLP as described in the "Logging in to LO100 (on page 21)" section.

2. Change to the system1 target by entering cd system1.

3. To power on the server, enter start /system1. For example:

Using LO100 25

/./system1/> start /system1 System1 started.

4. To power off the server, enter stop /system1. For example: /./system1/> stop /system1 System1 stopped.

The -force option can also be used with the stop command. This option forces the implementation to stop the target, ignoring any policy that might cause the implementation to normally not execute the command. In remote management processor implementation, this process is equivalent to a hard power down.

5. To reset the server, enter reset /system1. For example: /./system1/> reset System1 reset.

Monitoring sensors LO100 provides operating system-independent remote monitoring of the current status of major sensors of a target server including system temperature, fans, and voltage. You can view the data for this feature on the Monitoring Sensors Page through a web browser or through the BIOS Setup Utility.

Viewing sensors data from a web browser The Monitoring Sensors screen displays a snapshot of the temperature, fans, and voltage sensor data, including sensor type, name, status, and current reading. To access this page from a web browser, click Monitoring Sensors on the main menu navigation bar.

To update the display, click the Refresh button. To view or add a PEF action, click PEF. See "Platform Event Filtering configuration (on page 26)" for more information.

Viewing sensors data from the BIOS Setup Utility 1. Press the F10 key during POST to enter the BIOS Setup Utility.



Using LO100 26

4. Scroll to Realtime Sensor Data by pressing the down arrow (↓) key. Press the Enter key.

The Loading data. Please wait message appears. After this message disappears, the Temperature and Voltage sensor data appears. This data is real-time data and is updated on a periodic basis.

Platform event filtering configuration The PEF Configuration screen enables you to configure LO100 to take selected actions on received or internally generated event messages. These actions include powering down the system, system reset, and triggering the generation of an alert.

If you want to enable PEF functionality you must issue the following commands in the CLP: cd map1 oemhp i 20 10 D0 18 00 12 01 03 D2 oemhp i 20 10 D0 18 00 12 02 3F 95

To configure a PEF for a particular sensor, click the PEF button to the far right of that sensor on the Monitoring Sensors screen. The PEF button adjacent to each sensor opens a PEF Configuration page for that sensor.

The PEF Configuration screen contains two sections: Current PEF Entries and Add PEF Entry. The Current PEF Entries section includes Sensor Type, Sensor Name, PEF Action, and PEF Control information. The Add PEF Entry section enables you set an action.

Initially, no entries are in the Current PEF Entries section because no PEFs are defined. When PEF entries are defined, the PEF Control field is active and allows individual entries to be enabled, disabled, or deleted.

To configure an action (PEF entry) select the desired Event Offsets and PEF Action settings and click Add.

• Event Offsets are trip points (movements across thresholds) that define what type of sensor event triggers an action. The information in the Events Offsets section varies with the type of sensor. Not all options are available for all sensors. You can select any of the available options.

• PEF Action displays the same information for all sensors:

o Sensor Type displays the type of sensor selected.

o Sensor Name displays the name of the sensor.

Using LO100 27

o PEF Action enables you to select from Power Off, Power Cycle, Hard Reset, and Send Alert (requires a systems management console supporting IPMI 1.5 or later).

o PEF Control enables or disables the sensor.

o Alert Policy (dropdown list adjacent to the Add button) enables you to select an alert policy (if defined). Alert policies are defined on the PET Configuration screen. See "Platform event trap configuration (on page 42)" for more information.

If alert policies are not defined (default), the Alert Policy dropdown list displays No Alert Policy. The Alert Policy dropdown list populates after alert policies are defined and configured. After configuring your alert policies, you can select from the defined alert policies for this sensor and PEF.

o Add adds the new entry to the PEF Current Entry table at the top of the page.

Using the system event log LO100 captures and stores the IPMI event log for access through a browser, CLP, BIOS Setup Utility, and RBSU even when the server is not operational. The system event log displays a short description of each system event. Recorded events include abnormal temperature, fan and voltage events, system resets, and system power loss.

Accessing the system event log from a web browser The System Event Log screen displays a brief description of the event, including event type, date, time, source, description, and direction.

To access the System Event Log from a web browser, click System Event Log on the main menu navigation bar. To clear the system event log, click Clear Event Log.

Accessing the system event log from the CLP 1. Log in to the CLP as described in the "Logging in to LO100 (on page 21)" section.

2. Enter cd /./system1/log1

3. Enter show to display the total number of system event records.

Using LO100 28

4. Enter show record<n> to display the details of a specific record. For example: /system1/log1/record1 Targets Properties

number=1

date=12/20/2004

time=15:22:05

sensordescription= Backplane +12V

eventdescription= Upper Critical-going high

eventdirection=Assertion Verbs

cd

version

exit

show

reset

oemhp

help

Accessing the system event log from the BIOS Setup Utility 1. Press the F10 key during POST to enter the BIOS Setup Utility.



4. Scroll to the bottom of the IPMI page to access the System Event Log or the System Event Log (list mode).

5. To view the highlighted setup item, press the Enter key.


Using Virtual KVM The Virtual KVM feature of LO100 is a remote graphic console that turns a supported browser into a virtual desktop and provides full control over the display, keyboard, and mouse of the host server. The operating system-independent console supports graphic modes that display remote host server activities, including shutdown and startup operations.

Virtual KVM is an advanced feature available by installing the Lights-Out 100c Remote Management Card. For more information, see the section, "LO100 optional features (on page 6)."

When connecting to the Virtual KVM applet for the first time, the applet reports an error. To clear the error and connect to the Virtual KVM applet, close your browser session, and then reconnect to the Virtual KVM applet.

The Virtual KVM applet is not compatible with standard VNC clients and does not implement standard VNC protocols. You must use the supplied Java™ applet to connect to the server. The Virtual KVM applet cannot pass the F10 key sequence to the target system. To work around this issue, use the virtual keyboard on the remote server to transmit the F10 key.

Using LO100 29

The KVMS option (link) does not appear or function on HP ProLiant ML110 G5 Servers, if shared NIC mode is enabled through the BIOS Setup Utility. If the HP Lights-Out 100c Remote Management Card is installed, you must use the dedicated NIC port on the HP Lights-Out 100c Remote Management Card.

The remote graphic console requires JVM version 1.4.2 or later on the client system. To download the recommended JVM for your system configuration, refer to the HP website (http://www.hp.com/servers/manage/jvm).

To start the LO100 remote graphic console using a web browser:

1. Log in to LO100.

2. Click Virtual KVM / Media. The LO100 remote graphic console window appears.

NOTE: The Virtual KVM / Media option is an advanced feature and not available on all systems. This link may appear as Virtual Media or not at all depending on your system implementation. To verify which features are supported on your system, see "LO100 standard features (on page 6)" and "LO100 optional features (on page 6)" for more information.

3. Click OK to take full control of the system, or click Cancel to access the system in a view-only mode.

Before using the mouse in LO100 remote graphic console, HP recommends synchronizing your local mouse pointer and the remote mouse pointer. See "Mouse synchronization (on page 32)" for more information.

There are three different menus in the remote graphic console menu bar: Virtual KVM, Preferences, and Help.

• Virtual KVM enables you to access virtual media devices and the virtual keyboard as well as refresh the screen and exit the client. See "Using the remote graphic console (on page 30)" for more information.

• Preferences enables you to set mouse, keyboard, and logging options. See "Remote graphic console preference settings ("Remote graphic console settings" on page 31)" for more information.

• Help displays an About box, which specifies the LO100 remote graphic console version, build date, and time.

http://www.hp.com/servers/manage/jvm

Using LO100 30

Using the remote graphic console The Control menu of the remote graphic console has several different options.

• Virtual Media—Displays the Virtual Media Devices page. The Virtual Media Devices page displays

all accessible media drives of the storage server. Supported devices are CD-ROM, DVD-ROM floppy disk, and mass storage devices. See "Using Virtual Media (on page 33)" for more information.

• Virtual Keyboard—Opens a virtual keyboard enabling you to change the language of the virtual keyboard. To change keyboard settings, see "Remote graphic console preference settings ("Remote graphic console settings" on page 31)" for more information.

Lock is a special button on the Virtual Keyboard that is added to each language. If you click the Lock button, special keys, such as Shift, Alt, Ctrl, context and Windows that you press remain in a pressed status. To release the special keys, click the Lock button and the pressed special keys.

• Turn local monitor on—Powers on the local monitor.

• Turn local monitor off—Powers down the local monitor.

• Refresh Screen—Updates the information on the screen.

Using LO100 31

• Take Full Control—Enables you to take control of the remote console if you are currently in view-only mode. Only one remote console user can control the remote console at a time. Clicking Take Full Control displays a dialog box that prompts you to click OK to take full control of the system or click Cancel to access the system in a view-only mode.

• Disconnect Session—Disconnects the selected user session.

• Relinquish Full Control—Releases control of the session and remains in a view-only status.

• Exit—Closes the remote session.

NOTE: The Keyboard, Refresh Screen, Take Full Control, Disconnect Session, and Relinquish Full Control menu options are an advanced feature available with full Virtual KVM access only.

Remote graphic console settings To change the mouse, keyboard, and logging settings, select Preferences.

• The Mouse tab enables you to set the Mouse mode. Select Mouse to display the Mouse Mode list, which has the following options:

o Hide Mode (Relative) causes the LO100 remote graphic console to choose to change to Relative mode.

Relative mouse mode hides the remote mouse cursor. Use Hide Mode Relative if you are running a DOS-based program and the mouse is not tracking correctly.

o Absolute Mode causes the LO100 remote graphic console to send raw x and y coordinates to the server.

o Relative Mode sends the LO100 remote graphic console relative mouse position coordinates (+/- previous mouse pointer position) to the server. This mode is the default for Linux and Windows®.

• The Keyboard tab enables you to set the language of the virtual keyboard and the type of connection you are using. English is the default language. You can change the language of the virtual keyboard by selecting one of the 12 languages.

The remote side server and local side server (the LO100 remote graphic console) must use the same language for the virtual keyboard to function properly.

• The Logging tab enables you to view log messages in a Java™ console.

Global Logging is disabled by default. If you enable this option, you can view log messages in a Java™ console.

Do not run the console longer than 2 hours. The console uses all available memory and might cause the LO100 remote graphic console and the user web browser to crash. You should periodically clear the event log to prevent a slow connection or possible crash.

To record all log messages to the console from the Logging list, select Console. To check log messages in the Java™ console window from the list on the Tools menu of Internet Explorer menu bar, select Sun Java Console.

To record all log messages to a file, select Log File from the Logging list, enabling the Console Log File textbox. To select a file in which log messages will be stored, click the Browse button or enter the fully qualified file name of the selected file in the textbox. To send log messages to both a file of your choice and to the Java™ console, select Console and Log File.

Using LO100 32

Mouse synchronization To synchronize the local mouse pointer and the server mouse pointer, bring the local mouse to the top left corner to attract the server mouse pointer to the top left corner. Both pointers become synchronized when they overlap as one pointer.

For mouse synchronization to work correctly, you must change the Enhance Mouse pointer and Hardware Acceleration options on the remote machine (server side) using the LO100 remote graphic console.

For Windows® operating systems, perform the following steps:

To change the Enhance Mouse pointer option:

1. Select Start>Control Panel.

2. Double-click Mouse. The Mouse Properties window appears.

3. Select Pointer Options.

4. In the Pointer Options window:

a. Set the Pointer speed bar in the middle.

b. Be sure the Enhance pointer precision option is not selected.

To change the Hardware Acceleration option:

1. Right-click the desktop screen

2. Select Properties. The Display Properties window appears.

3. Click Settings>Advanced. The video card and monitor properties window appears.

4. Click Troubleshoot.

5. Set hardware acceleration to None to disable cursor and bitmap accelerations (one scale or option below Full).

6. Click Apply.

7. Click OK to exit the Display Properties window.

For Linux operating systems, perform the following steps:

• For SLES 9:

a. Determine which mouse device is the remote console mouse using the xsetpointer -l command to list all mouse devices.

b. Determine which mouse to modify by cross-referencing the output of xsetpointer with the X configuration (either /etc/X11/XF86Config or /etc/X11/xorg.conf.)

c. Select the remote console mouse as the mouse to modify. For example: xsetpointer Mouse[2]

d. Set the acceleration parameters. For example: xset m 1/1 1

• For Red Hat Enterprise Linux, set the acceleration parameters using: xset m 1/1 1

System buttons On the virtual keyboard, there are eight different system buttons: LCtrl, LWin, LAlt, RAlt, RWin, RCtrl, Context, and [Lock]. These buttons can be used as virtual keys and are similar to the keys the physical keyboard of your local machine.

Using LO100 33

For example, when you press the Ctrl+Alt+Del keys on the physical keyboard, the Task Manager of your local machine appears in addition to the task manager on the server, or the key combination unlocks the server for login. To display the Task Manager of the remote server by pressing similar virtual keys, on the LO 100 remote graphic console window, click LCtrl click LAlt, and then press the Del key on your physical keyboard. Using this key combination displays the LO100 remote graphic console Task Manager. You can use any combination of virtual and physical Alt, Ctrl, and Del keys.

• Lock and special buttons, when pressed, remain in a pressed state until released. To release special buttons, click [Lock], and press the system buttons.

• Selecting or pairing LCtrl and RCtrl, LAlt and RAlt, LWin and RWin function as they would on an English language keyboard. However, they might function differently on keyboards of other languages.

• Clicking Context is equivalent to right-clicking the LO100 remote graphic console window.

Using Virtual Media LO100 Virtual Media enables you to add, browse, remove, and share media devices and refresh the virtual media devices list that appears. LO100 Virtual Media is an advanced feature available by installing the Lights-Out 100c Remote Management Card. For more information, see the section, "LO100 optional features (on page 6)."

To access LO100 Virtual Media:

1. Click Virtual KVM / Media or Virtual Media (depending on your system implementation.) The Virtual KVM screen appears.

2. On the Virtual KVM menu, select Storage. The Storage Devices window appears and has the following options:

o Clicking Add adds a new virtual media device to the storage devices list. See "Adding a virtual media device (on page 34)" for more information.

o Clicking Connect shares the selected device. See "Shared virtual media devices (on page 35)" for more information. Only one device can be shared at one time.

o Selecting a device and clicking Remove removes devices from the virtual media devices list.

o Clicking Browse enables you to change the selected device path to another path.

o Clicking Refresh rescans and displays the current devices on your machine.

A CD-ROM, DVD-ROM, or ISO image mounted through the Virtual KVM or Virtual Media applet functions and appears (in boot order) the same as a locally mounted media device.

Using LO100 34

Adding a virtual media device The LO100 virtual media option provides you with a virtual media drive, which can direct a remote host server to boot and use standard media from anywhere on the network. Virtual media devices are available while the host system boots.

To add a new virtual media device, click Add on the Virtual Media Devices page. The Add Virtual Media Devices window appears. This window has the following options:

• The Look In list enables you to change your directory or drive.

• The Virtual Media Type list enables you to specify the file type that you want to share. You must declare a Virtual Media Type before LO100 recognizes they type of device it is sharing.

• The File Name textbox is the shared name of the device or images. See "Shared virtual media devices (on page 35)". There must be a disk in the device. If a disk is not present the Invalid file or directory message appears. If you are sharing a device, enter the Device Letter and a colon (:). Adding the colon distinguishes a device from a file.

• Select a value from the Files of Type list to select the files you want to share.

Using LO100 35

Shared virtual media devices You can share a virtual media device from the Storage Devices window. Only one device may be shared at a time.

To share a virtual media device, do the following:

1. On the Virtual KVM menu, select Storage. The Storage Devices window appears.

2. Click Add. A dialog box appears, enabling you to specify which device you would like to share.

3. In the File Name field, enter either the file name or the drive you want to share. If you are sharing a drive, enter a colon (:) after the drive letter.

4. In the Storage Type dropdown list, select the storage type that matches the selected resource and click Select.

You must have valid media in the drive if a removable media device type is selected. The selected device displays in the dialog box.

5. Select the device and click Connect. A message box appears, indicating either the device has been successfully connected or a problem has occurred.

6. Click OK to close the Storage Device window.

To remove a shared virtual media device, do the following:

Before removing a shared device, verify the device is safe to remove. If necessary, perform any required steps necessary to ensure the safe removal of removable media devices on the server.

1. On the Virtual KVM menu, select Storage. The Storage Devices window appears, displaying all previously added devices currently available.

2. Select the device you want to remove and click Remove. A dialog box appears, indicating that the device has been successfully disconnected.

3. Click OK to close the Storage Device window.

Accessing the remote console through telnet You can access the remote console through either the BIOS console text-redirection functionality or a Microsoft® Windows Server™ 2003 text-based console. Only one Remote Console window can be open at a time.

To start a remote console session, press the Esc+Q keys. To end a remote console session and return to the CLP press the Esc+( keys.

Redirecting BIOS console text through telnet LO100 BIOS console text redirection enables you to view the entire boot process remotely and make changes in the BIOS Setup Utility from a remote computer. This tool is valuable in troubleshooting and managing servers remotely.

To configure the BIOS Setup Utility on the target system:



3. Press the down arrow (↓) key to scroll down to the Console Redirection option, and then press the Enter key.

Using LO100 36

4. Verify the following settings:

o EMS Support (SPCR)—Enabled

o Serial Port Address—COM A

o Baud Rate—115.2k

o Console Type—VT100/PC

o Continue C.R. after POST—Off

5. To return to the previous screen, press the Esc key.

6. Scroll to the I/O Device Configuration option, and press the Enter key.

7. Verify that Serial Port is set to Shared.

8. To set or obtain a valid IP address, follow the instructions in the "Network settings (on page 40)" section.


After completing the console redirection process, you can view the boot process remotely from a client PC through an established telnet session to the IP address of LO100. See your operating system documentation for instructions on establishing telnet sessions.

To redirect the console to the telnet session and view the boot process, press the Esc+Q keys in the telnet session during server boot. If you reset the server using the telnet connection, and then press the Esc+Q keys, the boot process might not appear immediately. The boot process appears after the server resets. You can end the session by pressing the Esc+( keys.

NOTE: If you encounter problems logging in to the remote console, be aware that some telnet programs might require you to enable their send line feed at end of line option. If the remote console does not respond to the Enter key, try setting this option in your telnet program.

NOTE: You must follow the instructions in the "Network settings (on page 40)" section to configure the network access properly.

Redirecting a Linux console In the remote console and servers with the Linux operating system, you can enable a remote login on ttyS0 by making the following changes to the BIOS Setup Utility and boot documents.

NOTE: The actual steps will vary depending on your version of Linux.

1. Using the BIOS Setup utility, verify or change the following settings:

o Configure Console Redirection

— Console Redirection—Enabled

— EMC Support (SPCR)—Enabled

— Flow Control—None

— Redirection After BIOS POST—Always

— Terminal Type—VT100

— Sredir Memory Display Delay—No Delay

Using LO100 37

o I/O Device Configuration—Configure IO Port

— Serial Port 1 Address—3F8/IRQ4

2. In the /boot/grub/menu.lst file, append the following to the kernel startup line: console=ttyS0 115200

Comment out the line GRAPHICAL DISPLAY LINE # splashimage=(hd0,0)/grub/splash.xpm.gz

3. Add an entry to allow serial console login in /etc/inittab. For example: S0:12345:respawn:/sbin/agetty -L 115200 ttyS0 vt102

4. In /etc/securetty enable root access to ttyS0 by adding ttyS0.

5. In /etc/sysconfig/kudzu, set kudzu to not perform serial port probing during boot. For example: SAFE=yes

6. After modifying and saving the previous files, reboot the server. You can now log in to the operating system through remote console.

After POST, in the remote console, the server prompts you with a login. Enter a valid login and use the server as you normally would. Use the ESC+Q keys to start remote console through the telnet and the ESC+( keys to exit the remote console in telnet.

Microsoft Windows EMS management Microsoft® Windows Server™ 2003 provides text-based console access. You can connect a notebook to LO100 to perform basic management tasks on the target system. The Windows® EMS Console, if enabled, displays the processes that are running and enables administrators to halt processes. This capability is important in cases in which video, device drivers, or other operating system features have prevented normal operation and normal corrective actions.

To enable Windows® EMS management on the target system:


2. Press the right arrow (→) key to navigate to the Advanced>Console Redirection menu.

3. Press the down arrow (↓) key to scroll down to the EMS Console option, and then to access the submenu, press the Enter key. Verify the following settings:

o Console Redirection—Enabled

o Baud Rate—115.2K

o Terminal Type—VT100+

o Flow Control—None

o Redirection after BIOS POST—On

4. To return to the previous screen, press the Esc key, or to save the changes and exit setup, press the F10 key.

After enabling Windows® EMS management, you can view the Windows® EMS management console remotely from a client PC through an established telnet session to the IP address of the target server by pressing the Esc+Q keys. You can end an EMS session by pressing the Esc+( keys. See your operating system documentation for instructions on establishing telnet sessions.

Using LO100 38

NOTE: If you encounter problems logging in to the remote console, be aware that some telnet programs might require you to enable their send line feed at end of line option. If the remote console does not respond to the Enter key, try setting this option in your telnet program.

Hardware Inventory page The Hardware Inventory page enables you to remotely identify the presence of processors on a target server. To access this page from a web browser on the main menu navigation bar, click Hardware Inventory.

User administration The User Administration option on the main menu navigation bar enables you (if authorized) to edit the user name and password for existing users. You cannot create a new user. The user password is stored in nonvolatile memory and can be changed through a web browser ("Changing user settings through a web browser" on page 39) or through the CLP ("Changing user settings through the CLP" on page 39).

When using CLP, if you do not have the correct privileges, you are not prompted to log in with the correct credentials. If you have insufficient access, a warning message appears. If you receive a warning message, you must end the telnet connection and re-establish a connection. There are no restrictions when logged in as either oemhp or administrator. User and operator accounts have the following access.

Option User Operator

Hardware Inventory Yes Yes

Virtual Power No Yes

Monitoring Sensors View only Yes

System Event Log Yes Yes

Network Settings No No

PET Configuration No No

User Configuration No No

Virtual KVM No No

Using LO100 39

Option User Operator

Application License Key No No

Security Settings No No

Changing user settings through a web browser The User Administration screen displays user information, enables you to modify user settings, and enable or disable user accounts. The first user is a FIXED NULL value. You cannot change the properties of the first user or use it to log in with. Only the first two users (after the fixed null value) are enabled for login by default. Users can only be enabled from the browser interface.

WARNING: Do not disable all user accounts. If you disable all user accounts you will not be able to log in to LO100. HP recommends always leaving at least one user with administrative privileges.

To modify user settings:

1. Click User Administration on the main menu navigation bar.

2. Enter the password in the Password and Confirm Password fields.

3. Select the User Privilege level from the dropdown list. See "User administration (on page 38)" for more information on user privileges and access rights.

4. Change the user name, if needed.

5. Click the Set button to save the changes.

Changing user settings through the CLP The first user is a fixed null value. Customizable users start at user2 and continue through user16. You can only enable users for log in through the browser. However, you can change the values through any connection.

1. Log in to the CLP as described in the "Logging in to LO100 (on page 21)" section.

2. At the command prompt, enter cd map1/accounts.

Using LO100 40

3. Select a user by entering cd user1 or cd user#, where # is the user you want to modify and a whole number between 2 and 16.

4. To change the user name, enter set username=<new username>. For example: /./map1/accounts/user2/> set username=testuser2

5. To change the user password, enter set password=<new password> and enter the new password when prompted. For example: /./map1/accounts/user2/> set password=testpswd2

Passwords are case-sensitive and can contain up to 16 characters.

6. To change the group name enter, set group=<new group name>. Valid group settings are administrator, user, oemhp, and operator. For example: /./map1/accounts/user2/> set group=user

Network settings You can view and modify network settings for LO100 using a web browser, CLP, or the BIOS Setup Utility. If you change the IP address, the connection to the server terminates. You must reconnect to the server using the new IP address.

Configuring network settings using a web browser The Network Settings screen displays IP address, subnet mask, and other TCP/IP-related settings. From the Network Settings screen, you can enable or disable DHCP, and you can configure a static IP address for servers not using DHCP. You can view and modify the network settings when logged in as either OEM or administrator (admin).

To modify the network settings, click Network Settings on the browser main menu navigation bar, enter the new settings, and click Apply.

Configuring network settings using the CLP 1. Log in to LO100 CLP as described in the "Logging in to LO100 (on page 21)" section.

2. At the command prompt, enter cd map1/nic1.

Using LO100 41

3. Configure the network settings by entering the following: set <network property>=<new setting>. Configurable valid network properties are:

o networkaddress specifies the IP address for the NIC. This setting is dynamic.

o oemhp_nonvol_networkaddress specifies the IP address stored in non-volatile memory.

o oemhp_mask specifies the subnet mask for NIC. This setting is dynamic.

o oemhp_nonvol_mask specifies the subnet mask stored in non-volatile memory.

o oemhp_gateway specifies the gateway IP address for the NIC. This setting is dynamic.

o oemhp_nonvol_gateway specifies the gateway IP address stored in non-volatile memory.

o oemhp_dhcp_enable specifies whether DHCP is enabled for the NIC. Boolean values are accepted

o oemhp_nonvol_dhcp_enable specifies whether DHCP is enabled for the NIC and address stored in non-volatile memory.

Configuring network settings using the BIOS Setup Utility To enable a static IP address:





5. Set DHCP IP Source to Disabled.

6. Press the down arrow (↓) key to scroll down and enter a valid IP address, subnet mask, and gateway address (press the Tab key to move between address fields).


To enable a DHCP assigned address:





5. Set DHCP IP Source to Enabled.

6. To save and exit, press the F10 key, or to view the new IP Address, allow the server to reset and reenter the BIOS setup utility.

To enable telnet and HTTP services:

On HP ProLiant ML110 G5 Servers, HTTP and telnet are enabled after installing the HP ProLiant Lights-Out 100c Remote Management Card.

Using LO100 42

Platform event trap configuration The IPMI PEF Configuration screen enables you to set an alarm or specified condition originating on the server to alert an IPMI 2.0-supported systems management console. To access this page from a browser, click IPMI PEF Configuration on the main menu navigation bar.

The Global PEF Enable section enables you to set a global PEF action. To enable, select Enabled in the PEF Enable drop down box, select the PEF action, and click Apply.

The PET Destinations section indicates where LO100 sends the PET (if configured.) This section has up to eight entries specifying IP and MAC addresses. Enter either an IP address or a MAC address and click Apply. If both the MAC and an IP address are entered, the IP address is used.

To set a policy:

1. Select the Policy Enable state and enter the Policy Number and Destination Selector information.

o The Policy Enable field enables you to selectively enable and disable trap forwarding.

o The Policy Number field enables you to select a policy that will be used in PEF configuration.

o The Destination Selector field specifies where to send the PET trap from the destinations defined in the PET Destinations section.

2. Click Apply.

Importing a certificate If you do not want to use the preinstalled public key (certificate), create and install your own private key (certificate). Importing a key or certificate is a one-time procedure that supports both SSH and SSL. The key must be generated using external third-party software, placed on a TFTP server, and uploaded to the

Using LO100 43

LO100. For Microsoft® Windows®, if you do not have a TFTP software package, use TFTPD32.EXE, which is available on the Internet. Linux generally has a TFTP server installed with the operating system. If it is not, see your Linux documentation for more information.

NOTE: When you use the CLP load command with TFTPD32, HP recommends using a 30-second timeout and 6 retries.

NOTE: When using the CLP load command in Linux set the timeout to 15000000. The firewall built into some Linux systems might not allow the TFTP server to send and receive information. You might have to disable the firewall to allow these connections. If you are experiencing firewall issues, change the firewall settings to allow connections on port 69 (the default port for TFTP servers). See your firewall documentation for additional information.

Creating a certificate LO100 requires a 1,024-bit DSA key stored in PEM (Base64-encoded) format to be located on a TFTP server. For example, the following process uses Win32 OpenSSL, downloaded from the Shining Light Productions website (http://www.slproweb.com/products/Win32OpenSSL.html), and the commands issued in a DOS window to generate the certificate. To generate a certificate using Win32 OpenSSL:

1. Download Win32 OpenSSL.

2. Install and set up OpenSSL.

3. Using OpenSSL, generate a DSA parameters file: openssl dsaparam -out server_dsaparam.pem 1024

4. Generate the DSA private key file, called server_privkey.pem: openssl gendsa -out server_privkey.pem server_dsaparam.pem

5. Generate the DSA certificate (public key) file, called server cacert.pem: openssl req -new -x509 -key server_privkey.pem -out server_cacert.pem -days 1095

6. When prompted for a distinguished name, enter an appropriate domain name for the servers that will be receiving the certificate.

7. After creating the certificate, copy it to a TFTP server that is accessible on the same network as LO100.

Before importing a certificate or key, you must disconnect from any remote KVMS sessions. Importing a key or certificate will disconnect your session and reset the LO100 processor. After importing a key or certificate and LO100 confirms a successful upload, you must log back into LO100.

http://www.slproweb.com/products/Win32OpenSSL.html

Using LO100 44

Installing a certificate or private key through a web browser The Security Settings page enables you to install new keys and certificates for SSL and SSH connections.

To install a certificate through the browser:

1. Log in to LO100 as an administrator.

2. Click Security Settings on the browser main menu navigation bar.

3. Enter the IP address of the TFTP server in the tftp server IP address field.

4. On the dropdown menu under File type, select Certificate.

5. Enter the file name of the certificate created (server_cacert.pem in this example) in the File Name field. Include the path relative to the tftp server root in the file name.

6. Click Apply.

To install the private key through the browser:

1. Log in to LO100 as an administrator.

2. Click Security Settings on the browser main menu navigation bar.

3. Enter the IP address of the TFTP server in the tftp server IP address field.

4. On the dropdown menu under File type, select Key.

5. Enter the file name of the key created (server_privkey.pem in this example) in the File Name field. Include the path relative to the tftp server root in the file name.

6. Click Apply.

Installing a certificate or private key through the CLP To install a certificate, log in to LO100 as administrator through the CLP interface and issue the load command to upload and install the certificate. For example:

load -source <URI> -oemhpfiletype cer

where:

o <URI> is the //tftpserver IP/path/filename to be downloaded.

o tftpserver is the URL or IP address of the TFTP server containing the certificate.

Using LO100 45

o Path is the path of the file relative to the TFTP server root.

o filename is the file name of the certificate file (server_cacert.pem in this example).

You can also find these commands in /map1/firmware directory.


To install a private key, log in to LO100 as administrator through the CLP interface and issue the load command to upload and install the certificate. For example:

load -source <URI> -oemhpfiletype key

where:

o <URI> is the //tftpserver IP/path/filename to be downloaded.

o tftpserver is the URL or IP address of the TFTP server containing the private key file.

o Path is the path of the file relative to the TFTP server root.

o filename is the file name of the private key file (server_privkey.pem in this example).

You can also find these commands in /map1/firmware directory.


HP SIM support HP SIM discovers LO100 and enables you to identify and launch LO100. See your HP SIM user guide for more information on using HP SIM with LO100.

Technical support 46

Technical support

HP contact information For the name of the nearest HP authorized reseller:

• In the United States, see the HP US service locator webpage (http://www.hp.com/service_locator).

• In other locations, see the Contact HP worldwide (in English) webpage (http://welcome.hp.com/country/us/en/wwcontact.html).

For HP technical support:

• In the United States, for contact options see the Contact HP United States webpage (http://welcome.hp.com/country/us/en/contact_us.html). To contact HP by phone:

o Call 1-800-HP-INVENT (1-800-474-6836). This service is available 24 hours a day, 7 days a week. For continuous quality improvement, calls may be recorded or monitored.

o If you have purchased a Care Pack (service upgrade), call 1-800-633-3600. For more information about Care Packs, refer to the HP website (http://www.hp.com).

• In other locations, see the Contact HP worldwide (in English) webpage (http://welcome.hp.com/country/us/en/wwcontact.html).

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

http://www.hp.com/service_locator

http://welcome.hp.com/country/us/en/wwcontact.html

http://welcome.hp.com/country/us/en/contact_us.html

http://www.hp.com/

http://welcome.hp.com/country/us/en/wwcontact.html

Acronyms and abbreviations 47

Acronyms and abbreviations

BIOS Basic Input/Output System

BMC baseboard management controller

CLI Command Line Interface

CLP command line protocol

DHCP Dynamic Host Configuration Protocol

DSA Digital Signature Algorithm

EMS

Emergency Management Services

HTTP hypertext transfer protocol

IP Internet Protocol

IPMI Intelligent Platform Management Interface

JVM

Java Virtual Machine

KVM keyboard, video, and mouse


LO100 HP Lights-Out 100 Remote Management processors

MAC

Media Access Control

NIC network interface card

OS operating system

PEF Platform Event Filtering

PEM Privacy Enhanced Mail

PET Platform Event Trap

POST Power-On Self Test

RBSU ROM-Based Setup Utility

SLES SUSE Linux Enterprise Server

SMASH System Management Architecture for Server Hardware

SSH Secure Shell

SSL Secure Sockets Layer

TCP/IP Transmission Control Protocol/Internet Protocol


TFTP Trivial File Transfer Protocol

UID

unit identification

URL uniform resource locator

VNC virtual network computing

Index 50

A access options 21 accessing software, browser 22 administration 9 alert messages 42 authorized reseller 46

B base management controller (BMC) 9, 10, 11, 12,

28, 36, 41 Basic Input/Output System (BIOS) 9, 11, 12, 25,

27, 28, 35, 36, 37, 40, 41 BIOS (Basic Input/Output System) 9, 11, 12, 25,

27, 28, 35, 36, 37, 40, 41 BIOS console, text redirection 35 BIOS upgrade 12 BMC (base management controller) 9, 10, 11, 12,

28, 36, 41 browser-based setup 40

C certificates 42 certificates, generating 43 certificates, importing 42 certificates, installing 44 CLP (Command Line Protocol) 16, 17, 21, 22, 24,

27, 35, 39, 40, 44 CLP overview 16 CLP, base commands 17 CLP, commands 24, 27, 40 CLP, connection options 16 CLP, general syntax 16, 17 CLP, specific commands 21 Command Line Protocol (CLP) 16, 17, 21, 22, 24,

27, 35, 39, 40, 44 configuration procedures 9 configuration, network 9, 40 configuring the LOM processor 9 configuring, PET 42 connectors, illustrated 8 console redirection 10 contact information 46

D data protection methods 14 dedicated management port 10 defining hot keys 32 DHCP (Dynamic Host Configuration Protocol) 9, 10,

11, 21, 40, 41, 42 DHCP addresses 11 DHCP, disabling 11 DHCP, enabling 11 Digital Signature Algorithm (DSA) 43 DSA (Digital Signature Algorithm) 43 Dynamic Host Configuration Protocol (DHCP) 9, 10,

11, 21, 40, 41, 42

E Emergency Management Services (EMS) 37 EMS (Emergency Management Services) 37 EMS Console 37 enabling HTTP 12 enabling telnet 12 encryption 14 Ethernet connections 10 event log 27 event log entries 27 event log, BIOS setup access 28 event log, browser access 27 event log, CLP access 27

F features, CLP 16 features, IPMI 2.0 21 features, new 14 features, optional 6 features, overview 5 features, SSL 14 features, standard 6 firmware, updating 12, 13 flash ROM 12

G graphic remote console 28

Index

Index 51

H hardware inventory 38 help resources 46 HP Systems Insight Manager, support 45 HP technical support 46 HP website 46 HP, contacting 46 HTTP (hypertext transfer protocol) 6, 9, 10, 12, 14,

41 hypertext transfer protocol (HTTP) 6, 9, 10, 12, 14,

41

I importing, certificates 42 installation instructions 7, 8 installation requirements 7 installation, management card 7, 8 installing management card 8 Intelligent Platform Management Interface (IPMI) 5,

9, 21, 26, 27, 42 Internet Protocol (IP) 9, 11, 23, 41 IP (Internet Protocol) 9, 11, 23, 41 IP address assignment 11 IPMI (Intelligent Platform Management Interface) 5,

9, 21, 26, 27, 42 IPMI support 21

K key, private 44 key, public 42 keyboard, video, mouse (KVM) 5, 28, 31, 38 keys, system 32 kit contents, LO 100c management card 7 KVM, (keyboard, video, mouse) 5, 28, 31, 38

L Linux procedures 36 Linux, console redirection 36 LO100, logging in through browser 22 LO100c connectors 8 logging in 21, 22 logging in, through a browser 22 logging in, through the CLP 22

M MAC (medium access control) 32, 42 main menu functions 23 management card, installing 8

medium access control (MAC) 32, 42 monitoring sensors 25 mouse settings 32

N network access 9 network access, configuring 9 network interface card (NIC) 5, 7, 9, 10, 40 network settings 9, 40 network settings, configuring through a browser 40 network settings, configuring through the BIOS

setup 41 network settings, configuring through the CLP 40 NIC (network interface card) 5, 7, 9, 10, 40

O OpenSSH, using 15 operational overview 5 overview, CLP 16 overview, server management 5 overview, SSH 14 overview, SSL 14

P password, changing through a browser 39 password, changing through the CLP 39 passwords 39 PEF (Platform Event Filtering) 25, 26, 42 PEF entries, configuration 26 PEM (Privacy Enhanced Mail) 43, 44 PET (Platform Event Trap) 43, 44 phone numbers 46 Platform Event Filtering (PEF) 25, 26, 42 Platform Event Trap (PET) 43, 44 POST (Power-On Self Test) 8, 9, 36 post-installation procedures 8 power control options 24 power cycle server 24 powering up/down 24 Power-On Self Test (POST) 8, 9, 36 preinstallation, guidelines 7 Privacy Enhanced Mail (PEM) 43, 44 private key 44 private key, installing 44 privileges, user 38 processors 38 public key 42 PuTTY, using 15

Index 52

R RBSU (ROM-Based Setup Utility) 27 remote console, applet settings 31 remote console, using 35 remote graphic console, applet 30 remote management card connectors 8 remote management processor, logging in through

CLP 22 remote management, browser main menu 23 remote server power, controlling 24 required information 46 requirements, SSH 14 ROM-Based Setup Utility (RBSU) 27 ROMPaq utility 12

S safety considerations 7 Secure Shell (SSH) 5, 6, 14, 16, 22, 42, 44 Secure Sockets Layer (SSL) 5, 6, 14, 42, 43, 44 sensor data, BIOS access 25 sensor data, browser access 25 sensor data, viewing 25 serial port 9 serial port, BIOS console configuration 10 serial port, enabling 10 server management 5 settings, mouse 32 settings, network 40 settings, PEF 26 settings, power options 24 shared storage devices, adding 35 shared storage devices, removing 35 side-band connection 10 SLES (SUSE LINUX Enterprise Server) 32 SMASH (System Management Architecture for Server

Hardware) 5, 6, 16 SSH (Secure Shell) 5, 6, 14, 16, 22, 42, 44 SSH keys, importing 42, 44 SSH, using 14, 15 SSL, (Secure Sockets Layer) 5, 6, 14, 42, 43, 44 SSL, importing key and certificate 42 SSL, overview 14 SSL, using 14 static IP addresses 11 storage devices, adding 34 storage devices, sharing 35 storage devices, using 33 support, HP Systems Insight Manager 45 support, IPMI 21

SUSE LINUX Enterprise Server (SLES) 32 system buttons 32 system event log, access through the BIOS 28 system event log, access through the CLP 27 system event log, using 27 System Management Architecture for Server

Hardware (SMASH) 5, 6, 16

T technical support 46 telephone numbers 46 telnet 12, 35 TFTP (Trivial File Transfer Protocol) 12, 17, 42, 43,

44 Trivial File Transfer Protocol (TFTP) 12, 17, 42, 43,

44

U UID (unit identification) 5, 6, 16 uniform resource locator (URL) 12, 44 unit identification (UID) 5, 6, 16 URL (uniform resource locator) 12, 44 user access 9, 38 user account, modifying 9, 38, 39 user and configuration settings 9, 38, 39 using Virtual Media 33 using, LO100 14

V virtual devices 33 virtual KVM 28 Virtual Media, using 33 virtual network computing (VNC) 31 virtual power 24 VNC (virtual network computing) 31

W website, HP 46 Windows® EMS Console, enabling 37

Documents

HP ProLiant Lights-Out 100 Remote Management User Guidecontent.etilize.com/User-Manual/1020446952.pdf · HP ProLiant Lights-Out 100 delivers basic remote control of vital server resources,