HP Integrated Lights-Out Management Processor Scripting and Command Line Resource Guide

June 2006 (Third Edition) Part Number 382328-003

© Copyright 2005, 2006 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. Intel is a trademark or registered trademark of Intel Corporation or its subsidiaries in the United States and other countries. Java is a U.S. trademark of Sun Microsystems, Inc.

June 2006 (Third Edition)

Part Number 382328-003
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
Introduction .................................................................................................................................. 7
Guide overview ........................................................................................................................................ 7 New in this version.................................................................................................................................... 7 HP ProLiant Essentials Rapid Deployment Pack Integration .............................................................................. 7 Server management through IPMI version 2.0 compliant applications............................................................... 8

Command line.............................................................................................................................. 9
Command line interface overview................................................................................................................ 9 Command line access ................................................................................................................................ 9 Using the command line............................................................................................................................. 9 Escape commands................................................................................................................................... 11 Base commands ...................................................................................................................................... 11 Specific commands.................................................................................................................................. 12 User commands ............................................................................................................................ 12 Network commands....................................................................................................................... 13 iLO 2 settings................................................................................................................................ 15 iLO 2 embedded health settings ...................................................................................................... 16 SNMP settings............................................................................................................................... 18 License commands ......................................................................................................................... 18 Directory commands ...................................................................................................................... 19 Virtual media commands ................................................................................................................ 20 Start and reset commands............................................................................................................... 23 Firmware update ........................................................................................................................... 24 Eventlog commands ....................................................................................................................... 25 Blade commands........................................................................................................................... 25 Boot commands............................................................................................................................. 26 LED commands.............................................................................................................................. 27 System target and properties........................................................................................................... 27 Other commands........................................................................................................................... 29

Telnet ........................................................................................................................................ 30
Telnet support ......................................................................................................................................... 30 Using Telnet............................................................................................................................................ 30 Telnet simple command set ............................................................................................................. 30 Telnet security ............................................................................................................................... 31 Supported key sequences ......................................................................................................................... 31 iLO 2 VT100+ key map ................................................................................................................. 31 VT100+ codes for the F-keys ........................................................................................................... 33 Linux codes for the F-keys ............................................................................................................... 34

Secure Shell ............................................................................................................................... 35
SSH overview ......................................................................................................................................... 35 SSH features supported by iLO 2............................................................................................................... 35 Using Secure Shell................................................................................................................................... 36 SSH key authorization ............................................................................................................................. 36 Tool definition files......................................................................................................................... 37 Mxagentconfig.............................................................................................................................. 37 Importing SSH keys from PuTTY ....................................................................................................... 37

Group administration and iLO 2 scripting...................................................................................... 40
Lights-Out Configuration Utility .................................................................................................................. 40 Unauthenticated XML query ...................................................................................................................... 40

Contents

3

......................Group administration using the Lights-Out Configuration Utility........................................... 46 XML enhancements ...................................... 52 Setting up IIS for scripted virtual media .............................................................................................................................................................................................................................................................................................................................. 60 Setting a configuration ....................................................................................................................................................................................................................................................................................................................... 58 HPONCFG command line parameters.......................................................................... 56 HPONCFG.................................................................................................................................................................... 50 Using Virtual Media on Linux servers through an SSH connection ......................................................... 56 HPONCFG requirements ........................................ 67 LOGIN runtime errors ........................................................................................... 59 Obtaining a specific configuration................... 50 Using virtual media scripting................................................................................................................... 56 HPONCFG supported operating systems ....................................................................................................................................................................................................... 42 Application Launch using HP SIM ....................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................... 67 USER_INFO....................................................................................... 57 Linux server installation................. 68 ADD_USER .................................................................................................................................................................................... 66 Data types .......................................................................................................................................................................................................................................................................................................................................................... 47 Sending the XML header and script body ............................................................................................................... 41 Query definition in HP SIM ................. 62 Remote Insight command language..................................................................................................................................................................... 66 Response definitions ....................................................................................... 52 CGI helper application .................................................. 65 Overview of the Remote Insight Board Command Language ............................................................................................................................. 67 LOGIN .. 65 RIBCL and ProLiant BL p-Class Servers ....................... 57 Windows server installation ........... 46 Using Perl with the XML scripting interface ............................ 65 XML header ............. 50 Scripting Web server requirements .................................................................................................................................. 70 DELETE_CURRENT_USER ...................................................................................................................................................................................... 51 Virtual media image files................ 44 Lights-Out Configuration Utility parameters ............................ 70 GET_USER.......................................... 68 DELETE_USER........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................ 61 Capture and restore a configuration ............................................. 57 Using HPONCFG..................................... 67 LOGIN parameters ........................................ 41 Using the Lights-Out Configuration Utility with HP SIM ............................................................................... 66 RIBCL.............................................................................................................................. 67 RIBCL parameters ....................................................................... 43 Batch processing using the Lights-Out Configuration Utility .............................................................................. 44 Perl scripting ............................................................................................................................................................................................................ 48 Virtual Media scripting ............... 67 RIBCL runtime errors........................................ 46 Opening an SSL connection............... 65 RIBCL sample scripts ........................................................................................................................................................................................................................... 61 Variable substitution................................................................... 65 RIBCL general guidelines ................ 58 Obtaining an entire configuration............ 56 Installing HPONCFG ........... 71 Contents 4 ............................................. 53 HPONCFG online configuration utility...............................................................................................................................................................................................................................

.................. 105 GET_RACK_SETTINGS ............................................. 77 CLEAR_EVENTLOG......................................................................................................................................................................................................................... 107 GET_ENCLOSURE_IP_SETTINGS ...... 90 GET_FW_VERSION ....................................................................................................................................................................... 97 IMPORT_CERTIFICATE............................ 120 HOLD_PWR_BTN .......... 95 CERTIFICATE_SIGNING_REQUEST........................................................................................................................................................ 94 SET_VM_STATUS ......................................................... 122 SERVER_AUTO_PWR ........................................................................................................................................................................................................................................................................ 116 SET_HOST_POWER_SAVER........................................ 92 INSERT_VIRTUAL_MEDIA.................................................................................................................................................................................................................................................................................................................................. 108 MOD_ENCLOSURE_IP_SETTINGS .................................................................................MOD_USER .................................................................................................................................................................................................................................................................................................................................................................................................................. 75 RIB_INFO.......................................................... 115 GET_HOST_POWER_SAVER_STATUS .............................................................................................................................. 111 SERVER_INFO ................................. 121 COLD_BOOT_SERVER ........................... 106 MOD_DIAGPORT_SETTINGS...... 122 GET_SERVER_AUTO_PWR...................................... 101 GET_DIR_CONFIG ................................................................................................................................................................................. 124 GET_VPB_CABLE_STATUS (RILOE II only).. 98 MOD_TWOFACTOR_SETTINGS ........................................................................................................................................................................................................................................................ 119 RESET_SERVER ............................................................................................................. 110 MOD_BLADE_RACK ....................................................... 103 RACK_INFO ................................... 76 GET_EVENT_LOG ................................................................................................................................................................................................................................................................................................. 101 MOD_DIR_CONFIG ..... 119 SET_HOST_POWER.............................. 112 GET_EMBEDDED_HEALTH ........................................................................................ 125 Contents 5 ................................ 85 GET_SNMP_IM_SETTINGS ......... 121 WARM_BOOT_SERVER ................................................................ 89 UPDATE_RIB_FIRMWARE .................................................................................................................................................................................................................................................................................................................................................................................... 123 GET_UID_STATUS .............. 99 DIR_INFO ............................................................................................................................................................... 93 EJECT_VIRTUAL_MEDIA.............................................................................. 117 GET_HOST_POWER_REG_INFO...................................................................... 109 GET_TOPOLOGY ...................................... 72 GET_ALL_USERS................................................................................................................................................................................... 84 MOD_GLOBAL_SETTINGS ........................................................................................................................................................................................................................................................................................................................................................................................................ 94 GET_VM_STATUS....................................................................................................................................................... 120 PRESS_PWR_BTN .................. 106 GET_DIAGPORT_SETTINGS................................................................ 117 GET_HOST_POWER_STATUS ................... 113 GET_POWER_READINGS .............................................................................................................................................................................................................................. 91 LICENSE........................................................ 80 GET_GLOBAL_SETTINGS .............................................................................................................................................................................. 90 HOTKEY_CONFIG ................................................................................................. 79 MOD_NETWORK_SETTINGS ......................................................... 88 MOD_SNMP_IM_SETTINGS .................................................................................................................................................................................................................................................................................................................... 97 GET_TWOFACTOR_SETTINGS ........ 79 GET_NETWORK_SETTINGS ...................................................................................................................................... 74 GET_ALL_USER_INFO ........................................................................................................................................... 124 UID_CONTROL ................................................................................................................................... 76 RESET_RIB ..............................................................

.............................. 128 iLO 2 parameters...........................................................................HPQLOMGC command language ....................................................... 130 iLO 2 Status parameters ................................................................................................................... 139 iLO Advanced Pack License Key.................................................. 138 BL p-Class parameters ....................................................................................................................................................... 130 Server Status parameters ......... 135 SNMP/Insight Manager settings parameters ..................................................................................................... 131 User Administration parameters........................................................................................................................ 141 HP contact information ....................................................... 142 Index...... 140 Technical support............................. 141 Acronyms and abbreviations............................................................................................................................... 148 Contents 6 ....................................................................................................... 137 Directory settings parameters ........................................................................................................................................................................................................................................................................................................................................................................... 127 iLO 2 ports............................................................................... 126 Using HPQLOMGC .......................................................................................................................................................... 128 Re-enabling the dedicated NIC management port................................................................................................................................................................................................. 131 Global Settings parameters............................................................................................................................................................................................................................ 132 Network Settings parameters ....................................... 126 ILO_CONFIG ...................................................................................................................................................... 128 Enabling the iLO 2 Shared Network Port feature through XML scripting ........................................................................................................................................... 141 Before you contact HP.......

. IP address....... For more information about the ProLiant Essentials Rapid Deployment Pack......... The HP Integrated Lights-Out 1. 7 HP ProLiant Essentials Rapid Deployment Pack Integration.....................................hp........... If installed.............1x............... The Deployment Server provides the ability to use the power management features of iLO 2 to power on......10...... Each time a server connects to the Deployment Server.... iLO 2.......... and RILOE II firmware. The HP Integrated Lights-Out Management Processor Scripting and Command Line Resource Guide describes in detail the syntax and tools available to use iLO 2 through a command line or scripted interface.............. the Deployment Server polls the target server to see if a LOM management device is installed..............com/support/files/lights-out/us/index..... the server gathers information including the DNS name..... 7 Server management through IPMI version 2... or cycle power on the target server................. examples in this guide are written for iLO 2 firmware version 1.. Sample XML scripts downloaded from the HP website contain commands for all iLO....................................html)............................. New in this version The command line guide has been updated to support changes in the iLO 2 firmware.... refer to the documentation that ships on the ProLiant Essentials Rapid Deployment Pack CD or the HP website (http://www...........2x.... and iLO 2 1............ 7 New in this version............. and operate ProLiant servers remotely..com/servers/rdp)........Introduction In this section Guide overview ......www1.......... and first user name. HP ProLiant Essentials Rapid Deployment Pack Integration HP ProLiant Essentials Rapid Deployment Pack integrates with iLO 2 to allow the management of remote servers and the performance of remote console operations regardless of the state of the operating system or hardware. This guide covers iLO 1............ read the firmware support information in each sample script to tailor the script for the intended firmware and version...... Introduction 7 ...................... Before using XML sample scripts downloaded from the HP website (http://h18004.....0 compliant applications.. iLO 2 1....hp.. update....82............ Security is maintained by requiring the user to enter the correct password for that user name............................... power off..................80 User Guide and the HP Integrated Lights-Out 2 User Guide describe each feature and how to use the feature with the browser-based interface and RBSU...... 8 Guide overview The HP iLO 2 provides multiple ways to configure.. Unless otherwise specified..

Also. iLO 2 supports all the mandatory commands listed in the IPMI version 2.Server management through IPMI version 2.0 specification. Examples of these commands include any that sets or changes IPMI parameters.htm). The IPMI specification defines a standardized interface for platform management.com/design/servers/ipmi/tools. see the IPMI specification on the Intel® website (http://www. any IPMI traffic through the KCS interface can affect the performance of the health driver and overall health performance of the system.intel. The IPMI specification defines the following the type of platform management: • • • • Monitoring of system information. using the Get Device ID command). and power supplies Recovery capabilities. such as Get Device ID and Get Sensor Reading.com/design/servers/ipmi/tools.0 specification. You can locate this tool on the Intel® website (http://www. • IPMI functionality provided by iLO 2 When emulating a BMC for the IPMI interface. If the server operating system is running and the health driver is enabled. such as fans. Do not issue any IPMI commands through the KCS interface that could have a detrimental affect on the monitoring performed by the health driver. for abnormal events such as over-temperature readings or fan failures Inventory capabilities.net/index.html). iLO 2 emulates the BMC functionality and the SMS functionality can be provided by various industry-standard tools. IPMItool is a utility for managing and configuring devices that support the IPMI version 1. iLO 2 provides server management based on the IPMI version 2. for SMS communications.0 specifications and can be used in a Linux environment. The KCS interface is accessible to SMS software that is running on the local system.intel. For additional information. iLO 2 provides the KCS interface. temperatures. You can locate this tool on the IMPItool website (http://ipmitool.0 Command Test Tool is a low-level MS-DOS command line tool that enables hexformatted IPMI commands to be sent to an IPMI BMC that implements the KCS interface.5 and version 2. The KCS interface provides a set of I/O mapped communications registers. The BMC manages the interface between the SMS and the platform management hardware. such as Set Watchdog Timer and Set BMC Global Enabled. See the IPMI version 2.0 compliant applications Server management through the IPMI is a standardized method for controlling and monitoring the server. Introduction 8 . Any IPMI command that simply returns data is safe to use.htm). Examples of compatible SMS software applications are as follows: • IPMI version 2. The default system base address for the I/O mapped SMS Interface is 0xCA2 and is byte aligned at this system address.sourceforge.0 specification for a listing of these commands. such as identifying failed hardware components IPMI communications are dependent on the BMC and the SMS. such as system resets and power on/off operations Logging capabilities. or open interface. the SMS should use the methods described in the specification for determining which IPMI features are enabled or disabled in the BMC (for example.

...................................................................... Telnet protocol using three simultaneous connections................................... the output returned will follow this general format: hpiLO-> {CLI command} status=0 status_tag=COMMAND COMPLETED … output returned… Command line 9 ................... 11 Base commands .......................... the iLO 2 CLI is invoked by entering ESC (............................................................ 11 Specific commands....... After serial CLI is enabled on the Global Settings screen.................. you will be presented with the iLO 2 CLI prompt......... Any three network connections can be active simultaneously..... hpiLO-> Each time a CLI command is executed..................................................................................................................... login name. 9 Using the command line......... The iLO 2 uses the command set defined in the Server Management Command Line Protocol Specification... There are two interfaces through which the command line option can be accessed: • • Serial port using one connection Network using: • • SSH allowing two simultaneous connections.............................. 12 Command line interface overview HP has worked with key industry partners within Distributed Management Task Force.............. Each time a command is executed (or you exit the Remote Console or VSP) you will be returned to the CLI prompt as shown in the following example..... 9 Command line access...................... Systems Management Architecture for Server......... The CLP is intended to replace the simple CLI.................. Using the command line After initiating a command line LI session............. DMTF is working on a suite of specifications......... 9 Escape commands.... to define an industry-standard set of commands.. 1...................................................... Inc............. The SSH and telnet sessions start the after authentication.. to standardize manageability interfaces for servers..........................................................................................................Command line In this section Command line interface overview ........ and password are required to start a session using SSH.......... IP address or DNS name.............................. Command line access iLO 2 enables you to execute the supported commands from a command line.............00 Draft.....................................

Command line 10 . t.hpiLO-> If an invalid command is entered. If the serial command line session status is set to Enabled-No Authentication. Options—The valid options are: • • -help/-h -all/-a • • Properties are the attributes of the target that can be modified. no. The target can be changed by the cd command or by specifying a target on the command line. true. and f. n. The general syntax of CLP command is: <verb> <target> <option> <property> • Verbs—The supported verbs are: • • • • • • • • • • • • cd create delete help load reset set show start stop exit version • • Target—The default target is the /. y. then all the commands are executed without checking the privilege level. The same command set is supported through the serial port. hpiLO-> The following commands are supported in this release of CLP. The command is only executed if the privilege levels match. SSH. false. the response is slightly different: hpiLO-> show /bad status=2 status_tag=COMMAND PROCESSING FAILED error_tag=COMMAND ERROR-UNSPECIFIED Invalid property. The privilege level of the logged in user is checked against the privilege required for the command. then the status and status_tag values will reflect the error as shown: hpiLO-> boguscommand status=2 status_tag=COMMAND PROCESSING FAILED error_tag=COMMAND NOT RECOGNIZED If an invalid parameter is given to a valid command. and telnet connections. Output—The output syntax is: • • • status status_tag status_msg The valid Boolean values for any command are yes.

ESC Q stops the CLI session and terminates the SSH and telnet connection. ESC ESC erases the current line. Entering help displays all the supported commands. In the Windows Putty client. you can shorten commands. The context works like a directory path. making the key functional. • • • • • ESC ( invokes the serial CLI connection. then a simple show version command will display the information. Insert. Some client operating systems. ESC R ESC r ESC R resets the system. For example. the Backspace key can be mapped to a value of 0x8 by changing the setting for Terminal Keyboard to Control-H. By changing the context. you will not be able to navigate between different lines.General notes: If the commands on the CLP command span more than one line. The root context for the server is "/" and this is the starting point for a CLP system. Base commands • help displays context-sensitive help. The Backspace key will not work from a client where it has value of 0x7f. Escape commands The escape key commands are short-cuts to popular tasks.. There is a one second timeout for entering any of the escape sequence characters. Novell Linux Desktop and Red Hat Enterprise Linux 4 Desktop. • • exit terminates the CLP session. • show displays values of a property or contents of a collection target... Operating system-specific notes: • • Windows 2000 telnet client does not support the Functions keys F1. cd sets the current default target. For the Linux clients. Entering <command help/?> displays the help message specific to that command. to find the current iLO 2 firmware version. For example: hpiLO-> show status=0 status_tag=COMMAND COMPLETED / Targets system1 map1 Command line 11 . and End keys. using the Home or the End key lets the iLO 2 CLP service remap the Backspace key to use the value 0x7f. you could issue the command show /map1/firmware version. This is not necessary for SSH or telnet sessions because they automatically start a CLI session after a successful login. F12. ESC ^ powers on the system. if you issue the cd /map1/firmware command. Home. These keys will not work in an iLO 2 command line session. However. map the Backspace key to the value 0x7f which is used for the Delete key in Windows® telnet client. The Backspace key in iLO 2's CLP implementation is mapped to the value 0x8.

User commands User commands enable you to display and modify user settings.0 Specific commands The following describes specific commands available when using the command line. then valid targets would be: • • • Administrator admin test Properties Property username password Access read/write read/write Description Corresponds to the iLO 2 login name. • • • • • • • • create—Creates a new instance in the name space of the MAP. The show command can also be specified with an explicit or implicit context as well as a specific property desired. if three local users with the login names of Administrator. delete—Destroys instances in the name space of the MAP. An explicit context is /map1/firmware and is not dependant on the current context. For example. / is the current context. then all properties are shown.Properties Verbs cd version exit show The first line of information returned by the show command is the current context. If you execute show /map1/firmware date only the date is shown. reset—Causes a target to cycle from enabled to disabled and back to enabled. load—Moves a binary image from an URI to the MAP. In the example. For example: hpiLO-> version status=0 status_tag=COMMAND COMPLETED SM-CLP Version 1. stop—Causes a target to change state to a lower run level. and test exist. there are two properties available: version and date. Targets All the local users are valid targets. set—Sets a property or set of properties to a specific value. Command line 12 . Password for the current user. version—Queries the version of the CLP implementation or other CLP elements. User settings are located at /map1/accounts. If the current context is /map1 then a show firmware command will display the /map1/firmware data. In the case of the /map1/firmware context. An implicit context assumes that the context specified is a child of the current context. admin. The verbs (Verbs) section shows what commands are applicable to this context. start—Causes a target to change state to a higher run level. Following the context is a list of sub-targets (Targets) and properties (Properties) applicable to the current context. If a property is not specified.

Boolean values accepted. Specifies the privilege level. username corresponds to the login name. Specifies if the autosense feature is enabled. The network subsystem is located at: /map1/nic1 Targets No targets Properties Property enabledstate oemhp_shared_network oemhp_vlan_enablestate oemhp_vlan _id autosense speed fullduplex Access Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Description Specifies if iLO 2 NIC is enabled. The valid values are: • • • • • admin config oemhp_power oemhp_rc oemhp_vm group read/write If group is not specified. Boolean values accepted. Network commands oemhp_vlan_enablestate network commands enable you to display or modify network settings. Boolean values accepted. Specifies the VLAN ID. Only values from 1 to 4094 are valid. by default use the same value as the login name (username). lname1 is the login name of the user. • • create username=lname1 password=password In the example. Specifies if iLO 2 shared network VLAN ID is enabled. no privileges are assigned to the user. This value corresponds to the iLO 2 user name property. Examples The current path is /map1/accounts.Property name Access read/write Description Displays the name of the user. it will. Specifies if iLO 2 shared network port is enabled. Command line 13 . Boolean values accepted.oemhp_rc In the example. 10 or 100 Mb/s.oemhp_vm. Specifies the network speed. Boolean values accepted.configure. If this is not specified. set lname1 username=lname2 password=password1 name=name2 group=admin.oemhp_power. Specifies if the full duplex feature is enabled.

Specifies the destination IP address for the second static route. Boolean values accepted. Specifies the DNS name of NIC. Specifies if the registration with the DNS server is required. Boolean values accepted. Specifies the subnet mask of NIC.Property ipv4address subnetmask oemhp_gateway oemhp_dhcp_enable oemhp_dhcp_gateway oemhp_dhcp_dns oemhp_dhcp_wins oemhp_dhcp_route Access Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Description Specifies the IP address of the NIC. Command line 14 . If multiple properties are given on the same command line. Specifies the destination IP address for the first static route. Specifies if the DNS server address has to be obtained from the DHCP server. Specifies the IP address of the secondary DNS server.168. Specifies the destination IP address for the third static route. Specifies the gateway IP address for the second static route.0. Specifies the gateway IP address for the NIC. Boolean values accepted. Specifies the gateway IP address for the first static route. Specifies the gateway IP address for the third static route. Specifies if the IP server address has to be obtained from the DHCP server. Specifies the IP address of the primary DNS server. they must to be separated by a space. Boolean values accepted. oemhp_dhcp_domain oemhp_wins_register oemhp_wins_primary oemhp_wins_secondary oemhp_dns_primary oemhp_dns_secondary oemhp_dns_tertiary oemhp_ddns_register oemhp_route_dest1 oemhp_route_gateway1 oemhp_route_dest2 oemhp_route_gateway2 oemhp_route_dest3 oemhp_route_gateway3 name domainname Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Examples set /map1/nic1 enabledstate=yes speed=100 ipv4address=192. Boolean values accepted. Specifies the IP address of the secondary IP server. Specifies if the domain name has to be obtained from the DHCP server. Specifies the domain name for NIC. Boolean values accepted. Boolean values accepted Specifies if the gateway address has to be obtained from the DHCP server. Specifies if the static route addresses have to be obtained from the DHCP server. iLO 2 will be reset after network settings have been applied. Boolean values accepted.13 One or more properties can be specified on the command line. Specifies if the registration with the IP server is required. Specifies the IP address of the primary IP server. Specifies the IP address of the tertiary DNS server. Specifies if DHCP is enabled for the NIC.

Valid values are enabled. Boolean values are accepted. 30. Boolean values are accepted. iLO 2 settings are located at /map1/config. Boolean values are accepted. Enables or disables RBSU prompt during POST. and 120. Enables or disables authorization requirement for CLP session through serial port. Boolean values are accepted. Boolean values are accepted. Sets the remote console configuration. Sets the SSH port value. The valid values are 9600. Boolean values are accepted. Sets session timeout in minutes. Sets remote console port value. Sets terminal services port value. Sets the HTTP port value. Enables or disables terminal services passthrough. Enables or disables SSH. Boolean values are accepted. 57600. 19200. Sets the SSL port value. and 115200. 60. Enables or disables iLO 2 IP address display during POST. Sets virtual media port value. or automatic. disabled. Enables or disables telnet. Targets No targets Properties Property oemhp_enable oemhp_timeout Access Read/Write Read/Write Description Enables or disables the iLO 2. 38400. Enables or disables login requirement for accessing RBSU.iLO 2 settings iLO 2 settings commands enable you to display or modify iLO 2 settings. Sets the serial port speed for the CLP session. Valid values are 15. Boolean values are accepted. oemhp_passthrough Read/Write oemhp_rbsuenable Read/Write oemhp_rbsulogin Read/Write oemhp_rbsushowip Read/Write oemhp_rcconfig Read/Write oemhp_telnetenable oemhp_httpport oemhp_sslport oemhp_rcport oemhp_vmport oemhp_tsport oemhp_sshport oemhp_sshstatus oemhp_serialclistatus Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write oemhp_serialcliauth Read/Write oemhp_serialclispeed Read/Write Command line 15 . Enables or disables CLP session through serial port.

Sets the value for hotkey Ctrl-Y. they must be separated by a space. or power supply location Displays fan. Enable/Disable high performance mouse. If multiple properties are given on the same command line. Sets the value for hotkey Ctrl-T. and the power supply.00) oemhp_high_perf_mouse Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Examples set /map1/config oemhp_enable=yes oemhp_timeout=30 One or more properties can be specified on the command line. sensor. and /system1/powersupply*. or power supply operational status Displays if fan is operating at variable speed Displays the current fan speed Displays the health status of the fan. sensor. Targets • • • Fan Sensor Power supply Properties Property DeviceID ElementName Operationalstatus VariableSpeed Desired Speed HealthState Access Read Read Read Read Read Read Description Displays fan. or power supply Command line 16 . Sets the value for hotkey Ctrl-X. Sets the value for hotkey Ctrl-U. /system1/sensor*. sensor. temperature sensors. Enables/disables remote console acquire operations. voltage sensors. Sets the value for hotkey Ctrl-W. iLO 2 embedded health CLP settings are located at /system1/fan*. sensor. iLO 2 embedded health settings iLO 2 embedded health commands enable you to display system embedded health information for fans. Sets the value for hotkey Ctrl-V. oemhp_hotkey_t oemhp_hotkey_u oemhp_hotkey_v oemhp_hotkey_w oemhp_hotkey_x oemhp_hotkey_y oemhp_rc_aquire (not supported in iLO 2 v1. or power supply label number Displays fan.Property oemhp_minpwdlen oemhp_remotekbd Access Read/Write Read/Write Description Sets the minimum password length requirement. Sets the layout for the remote keyboard for remote console session.

Property RateUnits CurrentReading SensorType Oemhp_CriticalValue Access Read Read Read Read Description Displays the reading units for temperature and voltage sensors Displays the current reading of sensor Displays the sensor type Displays temperature sensor caution value Displays temperature sensor critical value Oemhp_CautionValue Read Examples The command show system1/fan1 displays the system fan1 properties. The command show system1/sensor3 displays one of the temperature zone properties. VRM power supplies are usually mapped to the sensor targets. For example: /system1/fan1 Targets Properties DeviceID=Fan 1 ElementName=I/O Board OperationalStatus=Ok VariableSpeed=Yes DesiredSpeed=40 HealthState=Ok. The command show system1/sensor1 displays the VRM 1 properties. For example: /system1/sensor1 Targets Properties DeviceID=VRM 1 ElementName=CPU 1 OperationalStatus=Ok RateUnits=Volts CurrentReading=0 SensorType=Voltage HealthState=Ok oemhp_CautionValue=0 oemhp_CriticalValue=0 Other sensor targets show system temperatures. For example: /system1/sensor3 Targets Properties DeviceID=Temp 1 ElementName=I/O Board Zone OperationalStatus=Ok RateUnits=Celsius CurrentReading=32 SensorType=Temperature HealthState=Ok Command line 17 .

SNMP settings are available at: /map1/snmp Targets No targets Properties Property accessinfo1 accessinfo2 accessinfo3 oemhp_iloalert oemhp_agentalert oemhp_snmppassthru Access Description Read/Write Sets the first SNMP trap destination address. Read/Write Sets the Insight Manager agent URL. Valid selections are enabIed and disabled. Boolean values accepted.168. License commands are available at /map1/. Read/Write Determines if the LOM device will respond to anonymous XML queries. they must be separated by a space. Targets No targets Commands Command cd show set Description Changes the current directory Displays license information Changes the current license Command line 18 . Boolean values accepted. Read/Write Enables or disables host agent SNMP alerts. Read/Write Sets the third SNMP trap destination address. Read/Write Enables or disables iLO 2 SNMP passthrough. Read/Write Sets the second SNMP trap destination address. oemhp_imagenturl oemhp_imdatalevel Examples set /map1/snmp accessinfo1=192.oemhp_CautionValue=68 oemhp_CriticalValue=73 SNMP settings SNMP settings commands enable you to display and modify SNMP settings. License commands License commands enable you to display and modify the iLO 2 license.50 oemhp_imdatalevel=medium One or more properties can be specified on the command line. If multiple properties are given on the same command line.0. Read/Write Enables or disables iLO 2 SNMP alerts. Boolean values accepted.

Examples • • • set /map1 license=1234500000678910000000001 show /map1 license delete /map1 license Directory commands Directory commands enable you to display and modify directory settings. The schema-free directory configuration requires a DNS name. This can be disabled only if directory authentication is enabled. 2. This field is ignored when the schema-free directory configuration is used. oemhp_dirsrvaddr oemhp_ldapport oemhp_dirdn oemhp_dirpassword oemhp_usercntxt1. Valid settings are: • • • oemhp_localacct extended_schema—Use HP's extended schema default_schema—Use schemafree directories disabled—Directory-based authentication is disabled Read/Write Enables or disables local account authentication.6 Command line 19 . Boolean values accepted. Read/Write Sets the directory server IP address or DNS name. Read/Write Sets the directory server port. or 3 oemhp_group{n}_name where n = 1. Read/Write Sets the LOM object password. Read/Write Security group distinguished name.. Not necessary when the schema-free directory configuration is used. This field is ignored when the default schema configuration is used. Read/Write Displays the directory user login search context. Read/Write Displays the LOM object distinguished name. Used with the schema-free directory configuration only. Directory settings are available at: /map1/oemhp_dircfg Targets No targets Properties Property oemhp_dirauth Access Description Read/Write Enables or disables directory authentication.

DC=demo.Property oemhp_group{n}_priv where n = 1.com oemhp_group1_name="CN=iLOAdmins. Targets You can access the following sub-components of the virtual media.. Displays if a virtual media device is already connected through the CLP or scriptable virtual media.CN=Users.2. they must be separated by a space. oemhp_connect Read Command line 20 . A comma-separated list of the following: • • • • • 1 (Administer Group Accounts) 2 (Remote Console Access) 3 (Virtual Power & Reset) 4 (Virtual Media) 5 (Configure iLO 2 Settings) Used with the schema-free directory configuration only. Examples • • set /map1/oemhp_dircfg set /map1/oemhp_dircfg oemhp_dirauth=groups oemhp_dirsrvaddr=adserv.6 Access Description Read/Write Privileges to assign to this group. If multiple properties are given on the same command line.5" Additional groups can be defined using additional set commands. Virtual media commands Access to the iLO 2 virtual media is supported through the CLP. One or more properties can be specified on the command line. See the user guide for more information.3.DC=com" oemhp_group1_priv="1.demo.4. The value is a URL with a maximum length of 80 characters. The virtual media subsystem is located at /map1/oemhp_vm. Target /map1/oemhp_vm/floppydr /map1/oemhp_vm/cddr Description Virtual floppy or key drive device Virtual CD-ROM device Properties Property oemhp_image Access Read/Write Description The image path and name for virtual media access.

Indicates if the Java applet is connected. The username:password field is optional. The URL is limited to 80 characters. The valid values are: • • • • Never—Do not boot from the device. Disconnect—Disconnects the virtual media device and sets the oemhp_boot to No_Boot. Examples • • set oemhp image=http://imgserver. • • The path is the URL to the media image Boot options are boot_once. specifies the location of the virtual media image file on an HTTP server. • oemhp_wp oemhp_applet_connected Read/Write Read Enables or disables the write protect flag. The hostname field is mandatory. The CLP only performs a cursory syntax verification of the <URL> value.Property oemhp_boot Access Read/Write Description Sets the boot flag.company.bin set oemhp image=http://john:abc123@imgserver.com/image/dosboot. connect. Image URL The oemhp image value is a URL. The port field is optional. The value is displayed as Always. boot_always. The filename field is mandatory.com/VMimage/installlDisk.iso iLO 1. no_boot. Boolean values are accepted. Connect—Connect the virtual media device. and is in the same format as the scriptable virtual media image location.company. URL example: protocol://username:password@hostname:port/filename • • • • • The protocol field is mandatory and must be either HTTP or HTTPS. You must visually ensure the URL is valid. The value is displayed as No_Boot. The value is displayed as Once.60 CLI support The vm simple CLI commands are still supported for virtual media: • • • • vm device insert path—Inserts an image vm device eject—Ejects an image vm device get—Gets the status of the virtual media vm device set boot access—Sets the status of the virtual media Command options: • Valid device names are floppy or cdrom NOTE: USB key drives must be used with the floppy keyword syntax. Once—Boot from the device once and then not thereafter. Sets oemhp_connect to Yes and oemhp_boot to Always. Always—Boot from the device each time the server is rebooted. or disconnect Command line 21 .

• Access options are write_protect or write_allow. Connect the media. See the "Virtual media scripting (on page 50)" section for more information. See the commands INSERT_VIRTUAL_MEDIA.com/floppyimg. Tasks • Insert a floppy USB key image into the Virtual Floppy/USBKey: cd /map1/oemhp_vm/floppydr show set oemhp_image=http://my.iso set oemhp_boot=connect show for which the example executes the following: • • • • Change the current context to the CD-ROM drive. • Eject a CD-ROM image from the Virtual CD-ROM: cd /map1/oemhp_vm/cddr set oemhp_boot=disconnect where the example executes the following: • • Change the current context to the CD-ROM drive. Show the current status to verify that the media is not in use.imageserver.bin set oemhp_boot=connect show for which the example executes the following: • • • • Change the current context to the floppy or key drive. The boot setting will automatically be connected Always.com/ISO/install_disk1. Issue the disconnect command that disconnects the media and clears the oemhp_image. GET_VM_STATUS. • Insert a CD-ROM image and set for single boot: cd /map1/oemhp_vm/cddr set oemhp_image=http://my. EJECT_VIRTUAL_MEDIA. Multi-device Virtual Media is not supported using the CLI. • Eject a floppy or USB key image from the Virtual Floppy/USBKey: cd /map1/oemhp_vm/floppydr set oemhp_boot=disconnect for which the example executes the following: • • Change the current context to the floppy or key drive. and SET_VM_STATUS in the "Remote Insight Command Language (on page 65)" section for more details on how to use these commands.com/ISO/install_disk1.imageserver. Connect the media.iso set oemhp_boot=connect set oemhp_boot=once show where the example executes the following: Command line 22 .imageserver. Issue the disconnect command that disconnects the media and clears the oemhp_image. Insert the desired image into the drive. You must specify virtual media images. The boot setting will automatically be connected Always. Insert the desired image into the drive. • Insert a CDROM image into the virtual CD-ROM: cd /map1/oemhp_vm/cddr show set oemhp_image=http://my. Show the current status to verify that the media is not in use.

the following examples show the new CLP format: Command line 23 . Insert the desired image into the drive. Eject a CD-ROM image from the virtual CD-ROM in a single command: set /map1/oemhp_vm/cddr oemhp_boot=disconnect If you attempt to disconnect when the drive is not connected. The boot setting will automatically be connected Always. Start and reset commands Start and reset commands enable you to power on and reboot the server containing iLO 2 or the iLO 2 itself.60 CLI support • power—Displays the current server power state power on—Turns the server on power off—Turns the server off power reset—Resets the server (server power off followed by server power on) power warm—Warm boots the server start /system1—Turns the server on stop /system1—Turns the server off reset /system1—Resets the server reset /system1 hard—Performs a coldstart reboot of the server reset /system1 soft—Performs a warmstart reboot of the server Instead of using the simple commands. you will receive an error. the following commands are supported: • • • • start stop reset hard reset soft reset reset soft power The power command is used to change the power state of the server and is limited to users with the Power and Reset privilege. Connect the media. • • • • • • • • • • If the current target is /map1. Command start stop reset hard reset soft Description Turns server power on Turns server power off Power cycles the server Warm boots the server Examples If the current target is /system1. Override the boot setting to Once. the following commands are supported: • • iLO 1.• • • • • • Change the current context to the CD-ROM drive. Show the current status to verify that the media is not in use.

the following example shows the new CLP format: start /system1/console1 Firmware update Firmware commands enable you to display and modify the iLO 2 firmware version. Instead of using the simple commands. similar to a telnet session. Command line 24 .• • show /system1 enabledstate—Shows the current power state. Command format load -source <URL> [<target>] where <URL> is the URL of firmware update image file on web server. The hostname field is mandatory. and is optional if it is already the default target.com/firmware/iloFWimage. Targets No targets Properties Property version date Access read read Description Displays the current firmware version. The CLP only performs a cursory syntax verification of the <URL> value. vsp The vsp command invokes a virtual serial port session. the following example shows the new CLP format: start /system1/oemhp vsp1 • remcons The remcons command starts a Remote Console session and is limited to users with the Remote Console privilege. enter Esc( to return to the CLI.bin The [<target>] field is /map1/firmware.company. When in Remote Console session. Only a text-based remote console is supported.bin load -source http://john:abc123@imgserver.70 release of the firmware. Firmware settings are available at /map1/firmware. Examples load -source http://imgserver. You must visually ensure the URL is valid. URL example: protocol://username:password@hostname:port/filename • • • • • The protocol field is mandatory and must be either HTTP or HTTPS. The username:password field is optional. The URL is limited to 50 characters in the iLO 1.com/firmware/ilo. When in virtual serial port session. press Esc( to return to the CLI.company. The port field is optional The filename field is mandatory. Instead of using the simple commands. Displays the release date of the current firmware version. for which enabled is powered on and disabled is powered off.

Targets You can access the following subcomponents of the blade: Target /map1/blade/diagport /map1/blade/rack /map1/blade/rack/enclo sure Description Displays and modifies the blade enclosure settings. Displays the event date. Displays and modifies the blade rack settings. where n is the total number of records Properties Property number severity Access read read Description Displays the record number for the event. delete /map1/log1—Deletes iLO 2 event log. Blade commands Blade commands enable you to display and modify the values on a p-Class server. noncritical. It can be informational. show /map1/log1—Displays the iLO 2 event log show /system1/log1/recordn—Displays record n from the system event log show /map1/log1/recordn—Displays record n from the iLO 2 event log. These values are available at /system1/map1/blade. Displays and modifies the front diagnostic port settings.. Properties Property bay_name bay_number Access read read Description Displays and modifies the blade bay name Displays the blade bay number Command line 25 . Eventlog settings are available at: • • /system1/log1 for the system event log /map1/log1 for the iLO 2 event log Targets record:1. or unknown. Displays a description of the event. critical. Displays the severity of the event. date time description read read read Examples • • • • • • show /system1/log1—Displays system event log. delete /system1/log1—Deletes system event log.n.Eventlog commands Eventlog commands enable you to display or delete the logs of both the system and iLO 2. Displays the event time.

Targets bootsource1.. Displays and modifies the rack name Displays the rack serial number Displays and modifies the enclosure name Displays the enclosure serial number Displays the enclosure type ipaddress mask rack_name rack_sn encl_name ser encl_type read/write read/write read/write read read/write read read Examples • • • set /map1/blade/bay_name=BayOne—Sets the blade's bay name to BayOne show /map1/blade/diagport/ipaddress—Displays the IP address of the front diagnostic port show /map1/blade/rack/enclosure(N)/encl_type—Displays the enclosure type for blade enclosure N Boot commands Boot commands enable you to modify the boot source and boot order of the system.Property facility_power auto_power log_alerts autoselect speed fullduplex Access read read read/write read/write read/write read/write Description Displays and modifies if the blade's 48-V power is provided by the facility Displays and modifies if the blade is enabled to automatically power on Displays and modifies if rack alert logging is enabled Displays and modifies the diagnostic port autoselect setting Displays and modifies the diagnostic port speed setting Displays and modifies if the diagnostic port supports full-duplex or half-duplex mode Displays and modifies the IP address for the diagnostic port Displays and modifies the subnet mask for the diagnostic port. Boot settings are available at /system1/bootconfig1. The possible values are: • • • • • • • BootFmCd : bootsource1 BootFmFloppy : bootsource2 BootFmDrive: bootsource3 BootFmNetwork or BootFmCd : bootsource1 BootFmFloppy : bootsource2 BootFmDrive : bootsource3 : bootsource4 Command line 26 .n. where n is the total number of boot sources Sets the boot source for the system.

Turns the LED off.60 are still supported. Displays if the server is powered on. Displays the system serial number. uid off—Turns the UID light off. LED settings are available at /system1/led1. Property start stop show Description Turns the LED on.• • BootFmUSBKey : bootsource4 BootFmNetwork : bootsource5 Properties Property bootorder Access read/write Description Sets the boot order for a given boot source Examples • • • set /system1/bootconfig1/bootsource(n) bootorder=(num) show /system/bootconfig1—Displays the complete boot configuration show /system1/bootconfig1/bootsource1—Displays bootorder for bootsource1 LED commands LED commands are used to change the state of the UID light on the server. • • • uid—Displays the current UID state on the server. The following properties are available in /system1: Property name number enabledstate Access Read Read read Description Displays the system name. the following examples show the new CLP format: • • • System target and properties The targets and properties described in this section provide information about the server. Command line 27 . Examples • • • show /system1/led1—Displays current LED status start /system1/led1—Turns LED on stop /system1/led1—Turns LED off iLO 1.60 CLI support Simple UID CLI commands introduced in iLO 1. Displays the LED status. show /system1/led1—verifies LED status start /system1/led1—Turns LED on stop /system1/led1—Turns LED off Instead of using the simple commands. uid on—Turns the UID light on.

or min.0 pstate1_avg=100. Command line 28 .0 pstate7_avg=0.0 pstate2_avg=0.Property oemhp_powerreg Access Description Read/write Displays the setting for dynamic power saver mode. max. Examples • • • show /system1 show /system1 name set /system1 oemhp_powergov=auto The following additional targets are available in /system1: Cpu displays information about the system processor.0 pstate5_avg=0. Example: The command show cpu1/logical_processor1 displays the p-states of the processor: For example: /system1/cpu1/logical_processor1 Targets Properties current_pstate=1 pstate0_avg=0. CPU power state values are shown as a part of the cpu target and uses an additional property of logical_processor<n>. The following properties are available in /system1/cpu<n>: Property speed cachememory1 cachememory2 Access Description Read Read Read Displays the processor speed Displays the size of the processor level 1 cache Displays the size of the processor level 2 cache Displays the logical processor logical_processor<n> Read The CPU power state command allows you to examine the CPU power states. The following properties are available in /system1/memory<n>: Property size speed location Access Read Read Read Description Displays the memory size Displays the memory speed Displays the location of the memory Slot displays information about the system slots.0 pstate3_avg=0.0 Memory displays information about the system memory.0 pstate4_avg=0.0 pstate6_avg=0. Valid values are auto.

The following properties are available in /system1/firmware: Property version date Access Read Read Description Displays the version for system ROM Displays the date for the system ROM Examples • • • • show /system1/cpu1 displays information on one CPU. system1/memory. show /system1/firmware displays information about system ROM. show /system1/memory1 displays information on one memory slot. show /system1/slot1 displays information on one slot. The following properties are available in /system1/slot<n>: Property type width Access Read Read Description Displays the slot type Displays the slot width Firmware displays information about the system ROM. Press ESC( to revert back to the CLI session. For example: /system1/firmware Targets Properties version=P56 date=01/05/2006 NOTE: system1/cpu.Slot displays information about the system slots. Command line 29 .81. and system1/slot are not supported in iLO 1. nmi server—Generates and sends an NMI to the server and is limited to users with the Power and Reset privilege. Other commands • • start /system1/oemhp vsp1—Starts virtual serial port session.

30 Supported key sequences ......... If you see an extra carriage return each time the Enter key is pressed........ To access iLO 2 using telnet: 1.. 30 Using Telnet. the iLO 2 Remote Console Port Configuration and Remote Console Data Encryption on the Global Settings screen must be configured as follows: 1....................... which can invoke a Remote Console connection as well as a Virtual Serial Port connection...... if the remote console port configuration on the Global Settings tab is set to Disabled or Automatic. press the Ctrl+] keys and enter set crlf off at the prompt.............Telnet In this section Telnet support .... Open a telnet window............. 2............. enter the IP address or DNS name............ and password................... An error message is generated if both sessions are opened simultaneously........................................................ or if remote console data encryption is enabled....... Telnet 30 ........ These commands are available only when in a telnet-based Remote Console or Virtual Serial Port session..... Press the Ctrl+] keys and press the Enter key at the prompt......... You cannot open both at the same time......... Refer to "iLO 2 VT100+ Key Map (on page 31)" for a complete list of key sequences....... Telnet access to iLO 2 supports the CLI...... You can open either a telnet based Remote Console session or a browser-based Remote Console session........................ Set the Remote Console Port Configuration to Enabled................... Set the Remote Console Data Encryption to No... Using Telnet To use telnet.......... 2............... NOTE: Access through telnet will be disabled................. Telnet simple command set The following key sequences for simple command set are available for use during telnet sessions......... When prompted...... To terminate a telnet session: 1..................................................... 2....................... Refer to the "Command line (on page 9)" section for more information.... login name... 31 Telnet support iLO 2 supports the use of telnet to access the iLO 2 command line interface.........

with \?. Some programs use the following mapping for HOME and END: sequence "\e[H" = HOME_KEY sequence "\e[F" = END_KEY ALT_CAPITAL_O and ALT_LEFT_SQBRACKET are ambiguous. The 6 indicates an ACPI power press. Sequence "\r\n" = '\r' Some terminals send ASCII 127 (DEL) when they mean backspace. To reduce any security risks: • • Use SSH instead of telnet. The 1 indicates an ON selection. CTRL P is the prefix for the Power commands. The ACPI power press is equivalent to holding the power button for approximately 6 seconds. Telnet security Telnet is an unsecured network protocol. Supported key sequences iLO 2 supports the VT100+ protocol. CTRL P is the prefix for the Power commands. The ! indicates an immediate emergency reboot. CLI is supported through telnet as well as SSH. Terminate longer sequences that start with \eO and \e[). • • • Many terminal programs send CR-LF when they mean ENTER. POWER OFF CTRL P 0 ACPI PRESS CTRL P 6 SYSTEM REBOOT CTRL P ! UID ON CTRL U 1 UID OFF CTRL U 0 The keys do not work before authentication. SSH is essentially secure or encrypted telnet.Action POWER ON Key sequence CTRL P 1 Comment CTRL P is the prefix for the Power commands. • • Telnet 31 . The 0 indicates an OFF selection. The 0 indicates an OFF selection. The Delete key never sends DEL. iLO 2 VT100+ key map The following are VT100+ key sequences. Preventing unauthorized access to the network segment prevents unauthorized activity. It sends "\e[3~". The 1 indicates an ON selection. The following tables define the supported key sequences. CTRL U is the prefix for the UID commands. CTRL U is the prefix for the UID commands. The power control requests are correctly ignored when you do not have the correct power control privileges. CTRL P is the prefix for the Power commands. Use a segregated management network.

\e\e.Key \010 UP_KEY DOWN_KEY RIGHT_KEY LEFT_KEY ALT_A ALT_B ALT_C ALT_D ALT_E ALT_F ALT_G ALT_H ALT_I ALT_J ALT_K ALT_L ALT_M ALT_N ALT_O ALT_P ALT_Q ALT_R ALT_T ALT_U ALT_V ALT_W ALT_X ALT_Y ALT_Z ALT_LOWER_A ALT_LOWER_B ALT_LOWER_C ALT_LOWER_D Sequence \177 \e[A \e[B \e[C \e[D \eA \eB \eC \eD \eE \eF \eG \eH \eI \eJ \eK \eL \eM \eN \eO\? \eP \eQ \eR \eT \eU \eV \eW \eX \eY \eZ \ea \eb \ec \ed Key ALT_AMPER ALT_APOS ALT_OPAREN ALT_CPAREN ALT_STAR ALT_PLUS ALT_COMMA ALT_MINUS ALT_PERIOD ALT_SLASH ALT_COLON ALT_SEMICO ALT_LESS ALT_EQUAL ALT_MORE ALT_QUES ALT_AT ALT_OPENSQ ALT_BSLASH ALT_CLOSESQ ALT_CARAT ALT_USCORE ALT_ACCENT ALT_PIPE ALT_CBRACK ALT_TILDE ALT_TAB ALT_BS ALT_CR ALT_ESC ALT_F1 ALT_F2 ALT_F3 ALT_F4 Sequence \e& \e' \e( \e) \e* \e+ \e. \e< \e= \e> \e? \e@ \e[\? \e\\ \e] \e^ \e_ \e` \e| \e} \e~ \e\t \e\010 \e\r \e\e\? \e\eOP \e\eOQ \e\eOR \e\eOS Telnet 32 . \e/ \e: \e.

Key ALT_LOWER_E ALT_LOWER_F ALT_LOWER_G ALT_LOWER_H ALT_LOWER_I ALT_LOWER_J ALT_LOWER_K ALT_LOWER_L ALT_LOWER_M ALT_LOWER_N ALT_LOWER_O ALT_LOWER_P ALT_LOWER_Q ALT_LOWER_R ALT_LOWER_S ALT_LOWER_T ALT_LOWER_U ALT_LOWER_V ALT_LOWER_W ALT_LOWER_X ALT_LOWER_Y ALT_LOWER_Z ALT_SPACE ALT_EXCL ALT_QUOTE ALT_POUND ALT_DOLLAR ALT_PERCENT Sequence \ee \ef \eg \eh \ei \ej \ek \el \em \en \eo \ep \eq \er \es \et \eu \ev \ew \ex \ey \ez \e\040 \e! \e\" \e# \e$ \e% Key ALT_F5 ALT_F6 ALT_F7 ALT_F8 ALT_F9 ALT_F10 ALT_F11 ALT_F12 ALT_F5 ALT_F6 ALT_F7 ALT_F8 ALT_F9 ALT_F10 ALT_F11 ALT_F12 ALT_HOME ALT_INS ALT_DEL ALT_END ALT_PGUP ALT_PGDN ALT_HOME ALT_END ALT_UP ALT_DOWN ALT_RIGHT ALT_LEFT Sequence \e\eOT \e\eOU \e\eOV \e\eOW \e\eOX \e\eOY \e\eOZ \e\eO[ \e\e[15~ \e\e[17~ \e\e[18~ \e\e[19~ \e\e[20~ \e\e[21~ \e\e[23~ \e\e[24~ \e\e[1~ \e\e[2~ \e\e[3~ \e\e[4~ \e\e[5~ \e\e[6~ \e\e[H \e\e[F \e\e[A \e\e[B \e\e[C \e\e[D VT100+ codes for the F-keys Key F1_KEY Sequence \eOP Telnet 33 .

Key F2_KEY F3_KEY F4_KEY F5_KEY F6_KEY F7_KEY F8_KEY F9_KEY F10_KEY F11_KEY F12_KEY Sequence \eOQ \eOR \eOS \eOT \eOU \eOV \eOW \eOX \eOY eOZ \eO[ Linux codes for the F-keys Key F5_KEY F6_KEY F7_KEY F8_KEY F9_KEY F10_KEY F11_KEY F12_KEY HOME_KEY INSERT_KEY DELETE_KEY END_KEY PG_UP PG_DOWN Sequence \e[15~ \e[17~ \e[18~ \e[19~ \e[20~ \e[21~ \e[23~ \e[24~ \e[1~ \e[2~ \e[3~ \e[4~ \e[5~ \e[6~ Telnet 34 .

................. SSH features supported by iLO 2 The iLO 2 library supports only version 2 (SSH-2) of the protocol........ To avoid this issue and for best results... which includes security with authentication....54 or later.... the RSA and DSA keys are erased and are regenerated on the next boot.......................Secure Shell In this section SSH overview ..................... aes128-cbc hmac-sha1...... the command line interface is available................ • When upgrading the firmware.. The features that are supported are listed in the following table..... iLO 2 generates the 1024-bit RSA and DSA keys.......... hmac-md5 ssh-dss................... 36 SSH overview SSH is a telnet-like program for logging into and for executing commands on a remote machine......................................................... encryption...............54........................ iLO 2 can support simultaneous access from two SSH clients..... If iLO 2 is reset to factory defaults........................... versions before 0.. ssh-rsa 3des-cbc.. ssh-rsa Diffie-hellman-group1-sha1 None English Password Secure Shell 35 ........... 36 SSH key authorization ........ OpenSSH........ 35 Using Secure Shell... These keys are saved by iLO 2 for future use..................................... which is a free version of telnet and SSH protocol available for download on the Internet...................... When using PuTTY........ there is a one-time 25-minute delay before SSH functionality is available............................................. and data integrity features........................................ HP recommends using version 0.... During this time...... which is a free version of the SSH protocol available for download on the Internet..............54 might display 2 line feeds instead on a single line feed.............. Feature Server host key algorithms Encryption (same set supported both ways) Hashing algorithms Public key algorithms Key exchange Compression Language Client/User authentication method Supported algorithm ssh-dsa ..... 35 SSH features supported by iLO 2 .................... when the ENTER key is pressed....... After SSH is connected and authenticated... iLO 2 supports: • • SSH protocol version 2 PuTTY 0.......

at scheduled times. enter the IP address or DNS name. 2. or automatically with the mxagentconfig utility. Using OpenSSH To start an OpenSSH client in Linux.Feature Authentication timeout Authentication attempts Default SSH port Supported algorithm 2 minutes 3 22 Using Secure Shell Using SSH To access iLO 2 using SSH: 1.exe -load "session name" SSH key authorization SSH key-based authentication enables HP SIM to connect to LOM devices through SSH and be authenticated and authorized to perform administrative-level tasks. Enhancements to HP SIM are provided by tool definition files. The CLP is utilized to perform tasks.exe telnet://host[:port]/ To start an existing saved session called sessionname: putty. To use SSH in interactive mode. the following alternative syntax is supported: putty. double-click the PuTTY icon in directory where PuTTY is installed.exe [-ssh | -telnet | -rlogin | -raw] [user@]host For telnet sessions. HP SIM can perform actions on target devices utilizing an SSH interface that requires private key-based authentication. HP SIM provides a menu-driven interface to manage and configure multiple targets. login name. If HP SIM is enabled to integrate more fully with LOM devices. and password. HP SIM can perform these tasks on multiple LOM devices nearly simultaneously. see the "SSH overview (on page 35)" section. SSH keys do not need to be created to use SSH in interactive mode. This is completed either manually through a Web-based GUI. use: ssh -l loginname ipaddress/dns name Using PuTTY • • To start a PuTTY session. Open an SSH window. When prompted. An HP SIM instance will be established as a trusted SSH client by installing its public key in iLO 2. SSH key-based authentication is implemented in iLO 2. Secure Shell 36 . To Start a PuTTY session from the command line: • • • To start a connection to a server called host: putty.

iLO 2 stores this key as a trusted SSH client key. iLO 2 expects public key file information on a single line.exe) utility to import a correctly formatted SSH key for use with iLO 2. and transmit the necessary public key. Importing SSH keys from PuTTY The public key file format generated by PuTTY is not compatible with iLO 2. and click Generate. This utility simplifies the process and can install the public key on many systems simultaneously.BEGIN SSH2 PUBLIC KEY ---Comment: "Administrator" AAAAB3NzaC1yc2EAAAABJQAAAIB0x0wVO9itQB11o+tHnY3VvmsGgwghCyLOVzJl 3A9F5yzKj+RXJVPxOGusAhmJwF8PBQ9wV5E0Rumm6gNOaPyvAMJCG/l0PW7Fhac1 VLt8i5F3Lossw+/LWa+6H0da13TF2vq3ZoYFUT4esC6YbAACM7kLuGwxF5XMNR2E Foup3w== ---. Double-click the PuTTY Key Generator icon to launch the utility. Mxagentconfig will make an SSH connection to iLO 2. Secure Shell 37 . a PuTTY generated public key file looks like this: ---. For example. 2.END SSH2 PUBLIC KEY ---PuTTY generated public key files are not compatible with iLO 2. You must use the PuTTY Key Generator (puttygen. To import SSH keys to iLO 2 from PuTTY: 1.Tool definition files TDEF files extend the menu system of HP SIM to provide the CLP commands that HPSIM will transmit to iLO 2 through an SSH connection. Select SSH-2 RSA. authenticate with a user name and password. Mxagentconfig Mxagentconfig is a utility used to export and install HP SIM public SSH keys into other systems.

On the key area. Click Authorize Key. 4. 5. and locate the public key file.pub. 9. 13. Copy the key and paste it into a Notepad session. move the mouse around to generate the key. Click Save private key to save and enter a file name when prompted. Save the public key file. 10. Secure Shell 38 . Select SSH>Auth on the menu. 7. 11. Log into iLO 2 (if not already open). Return to Notepad. Return to the PuTTY Key Generator utility. After the key is generated. c:\bchan. On the iLO 2 SSH Key Administration page. (The user name is case-sensitive and must match the case of your iLO 2 user name. Click File>Save As. and enter a file name when prompted.) Select all the text in the public key area. Launch PuTTY. replace the key comment with your iLO 2 user name. 3. c:\bchan. 6. 12. 8.ppk. for example. A new Authorized SSH key will appear in the list. click Browse. You must keep moving the mouse until the key generation process is complete. for example.

Configure your iLO 2 IP. Enter the logon name associated with the public key. iLO 2 will respond and ask for a user name. 15. you will be prompted for the key passphrase before you log into iLO 2. Keys can be created with a key passphrase. If a key passphrase was used to generate the public key.14. and click Open. If the keys match. Click Browse and locate the public key file. Secure Shell 39 . The public key in iLO 2 will handshake with the private key in PuTTY. you are logged into iLO 2 without using a password. 16.

.......................................html)............. Runtime errors are logged to the C:\PROGRAM FILES\INSIGHT MANAGER\HP\SYSTEMS directory..................25 or later of CPQLOCFG......00............ The Lights-Out Configuration Utility sends a RIBCL file to a group of iLO 2s to manage the user accounts for those iLO 2s................... Syntax errors take the format of Syntax error: expected X but found Y... For example: Syntax error: expected USER_LOGIN=userlogin but found USER_NAME=username............ Syntax errors occur when an invalid XML tag is encountered......... By default............................................ When a syntax error occurs................. 40 Unauthenticated XML query ........... submit the following command to the iLO 2 web server port: https://<iloaddress>/xmldata?item=all Group administration and iLO 2 scripting 40 ........ This utility can be downloaded from the HP website (http://h18004.... iLO 2s then perform the action designated by the RIBCL file and send a response to the log file.... To disable this feature....... RIBCL scripts are passed to the iLO 2 over the secure connection to CPQLOCFG.......Group administration and iLO 2 scripting In this section Lights-Out Configuration Utility..... • • Runtime errors occur when an invalid action is requested. Version 2. 40 Group administration using the Lights-Out Configuration Utility ................................ The CPQLOCFG utility can be launched from HP SIM for Group Administration or used independently from a command prompt for batch processing......... Unauthenticated XML query If configured to do so...... This utility requires a valid user ID and password with the appropriate privileges.....................hp.com/support/files/lights-out/us/index.....www1............... the LightsOut Configuration Utility stops running and logs the error in the runtime script and output log file........................... set the CIM_SECURITY_MASK in the MOD_SNMP_IM_SETTINGS command to disallow returned information....................EXE is required to support all features of iLO 1.......... the iLO 2 is configured to return this information.... the iLO 2 device will return some identifying information in response to an unauthenticated XML query........................ The Lights-Out Configuration Utility is used to execute RIBCL scripts on the iLO 2 and must reside on the same server as HP SIM....EXE) is a Microsoft® Windows®-based utility that connects to the iLO 2 using a secure connection over the network....80 and later and iLO 2 1.............. HP SIM discovers iLO 2 devices as management processors.......... 44 Lights-Out Configuration Utility parameters ............................................. See to the RIBCL section ("Remote Insight command language" on page 65) for a complete listing of errors. The Lights-Out Configuration Utility generates two types of error messages: runtime and syntax... To obtain unauthenticated identifying information. 41 Batch processing using the Lights-Out Configuration Utility ..... 44 Lights-Out Configuration Utility The Lights-Out Configuration Utility (CPQLOCFG...

Group administration and iLO 2 scripting 41 . Using CPQLOCFG with HP SIM requires: 1.10</FWRI> <HWRI>ASIC: 5</HWRI> <SN>ILO0004PBM158</SN> <UUID>ILO1226570004PBM158</UUID> </MP> </RIMP> Group administration using the Lights-Out Configuration Utility The IT administrator can manage multiple iLO 2s through HP SIM. In the Customize Lists window. Creating a customized list Creating a custom command Creating a task Create a customized list A customized list allows you to create a list of a group of management processors and run a task on that list. In the Systems List pane in the left window. To create a customized list: 1.0" ?> <RIMP> <HSI> <SBSN>0004PBM158</SBSN> <SPN>ProLiant DL380 G5</SPN> <UUID>1226570004PBM158</UUID> <SP>1</SP> </HSI> <MP> <ST>1</ST> <PN>Integrated Lights-Out 2 (iLO 2)</PN> <FWRI>1. The components of Group Administration are: • • • • • RIBCL ("Remote Insight command language" on page 65) Lights-Out Configuration Utility (on page 40) Creating a Customized List ("Create a customized list" on page 41) Creating a Custom Command ("Create a custom command" on page 42) Creating a Task ("Create a task" on page 42) Using the Lights-Out Configuration Utility with HP SIM HP SIM can manage the group administration of iLO 2 devices using query definitions ("Query definition in HP SIM" on page 42) and Application launch ("Application Launch using HP SIM" on page 43).A typical response to this command is: <?xml version="1. click Customize. 2. 2. select System List using the Show dropdown menu and click New List. 3.

To clear an added variable. and the status. select the variable. If the CPQLOCFG.3. Click Next to specify the tool parameters. Select the custom command from the Tools>Custom Commands dropdown menu. 6. the Task Results screen appears with a summary of the task. 3. Click Go. Log in to HP SIM. log in to HP SIM and create a query. In the Command field. Description. Select the search parameters using the Search for and where dropdown menus. then the path is C:\cpqlocfg. Create a task Create a task to execute a custom command on specific systems or events. 2. 2. Group administration and iLO 2 scripting 42 . and click Delete. When the systems display. Choose targets by selecting either: • • All systems in the list—Selecting an option in the drop-down menu automatically targets all systems in that list. 4. Enter the Parameters. 1.exe. Create a custom command To create a custom command: 1. • If you click Schedule. 5. 3. The Schedule option is available only if the tool can be scheduled. Click Apply Selections. 4. the schedule task screen appears. If the systems selected are not compatible with the tool. The Target Selection page is displayed. The items selected display in the Verify Target Systems page.EXE file is in the root directory of the C:\ drive. see the HP Systems Insight Manager documentation. 4. Select the target system. Click Tools>Custom Commands>New Custom Command. Click Add after entering each set of variables and values. In the New Custom Command screen. Click OK. The new tool is added to the dropdown menu Tools>Custom Commands. To create the query: 1. If you want to remove the system selected. enter the appropriate information in the Name. Enter the Variable Name and Value. click Save As. the target details. For more information on the scheduling options. 6. • Query definition in HP SIM To group all of the iLO 2 devices. To change the selected target list click Change Targets. be sure to enter the full path and the file name of the application. click OK. Schedule the task. and Comments fields. Individual systems in the list—Selecting an option in the drop-down menu displays the available systems for the selected list. the Tool Launch OK column provides a brief explanation of the problem. 5. Enter a name for your list and where it is to be saved. Click either Schedule or Run Now. 5. click Remove and you will return to the Select Target Systems page. If you click Run Now. After entering the Custom Command information. The Next option displays only if the tool parameters need to be specified.

defining the query association. Click Tasks to open the Tasks screen. Click Device in the navigation bar on the top left side of the screen. Click Create Category. 10. Select the query that had been created earlier. and setting a schedule for the task. 7. -V is the verbose message (optional). Click New Control Task and select Application Launch from the dropdown menu to open the Create/Edit Task screen. Click type in the Query Description field. within the appropriate query category. 7. then the path is C:\cpqlocfg. If the CPQLOCFG. Group administration and iLO 2 scripting 43 . and the query definition to manage the Group Administration of the iLO 2s. Enter the parameters in the area provided.2. A screen displays the options for naming the task. Click Queries>Device. 3. to open the Create/Edit Query screen where the query definition is created. the Lights-Out Configuration Utility. Click Save to return to the Device Query screen. and then select Devices by product name. The initial page for devices opens. 9. 6. If the RIBCL file is in the root directory of on the C:\ drive. the name of the new category is RIB Cards. 14. and click the query name to run it for verification. 8. 5. Define the query name. A window opens where you define the device type. Click New to create a new category. then the parameters are: -F C:\MANAGEUSERS. proceed to step 7. otherwise proceed to step 5. Click Overview on the left side of the screen after the verification has taken place. A schedule configuration window appears. Enter the full path and name for the Lights-Out Configuration Utility in the area provided. for example "Mgmt Processors. 8. 5. 9. set the product name to HP Integrated Lights-Out 2. To create an Application Launch task: 1. Click Device in the navigation bar on the top left side of the screen." Click Schedule to define when the Application Launch task will run. Locate the Personal Queries section in the main window. HP SIM requires the following parameters for the LightsOut Configuration Utility: -F is the full path of the RIBCL file name. A default log file named with the DNS name or the IP address is created in the same directory where CPQLOCFG is launched. 6. Click Queries to return to the Device Queries screen. 11. Select Management Processor and click OK. Application Launch using HP SIM The Application Launch combines the RIBCL. Enter a task name in the Enter a name for this task field. Click Next.xml -V NOTE: The -L parameter cannot designate an output log file. 4." Select Device(s) of type. If a query category exists. for example "Mgmt Processors. 4. 12. 3. 13. Find the newly created query in the appropriate query category. For this example. 2. Click New.exe.EXE file is in the root directory of the C:\ drive. In the criteria windows.

Lights-Out Configuration Utility parameters • -S is the switch that determines the iLO 2 that is to be updated.XML -L RIB3LOG. a default log file with the DNS name or the IP address is created in the same directory used to launch CPQLOCFG. NOTE: The default schedule for a control task is Now. Any log files generated are placed in the same directory as the Lights-Out Configuration Utility executable The switches -L and -V might or might not be set depending on the IT administrator's preferences. Batch processing using the Lights-Out Configuration Utility Group Administration can also be delivered to iLO 2 through batch processing.... Click the Execute a Task icon (the green triangle) to execute the Group Administration..XML -L RIB1LOG. If this switch is omitted. all responses from the Remote Insight board. and any errors. Click OK to set the schedule.SCRIPT. NOTE: The output values might need to be modified to match the RIBCL syntax. Do not use this switch if you are launching from HP SIM. By default. an RIBCL file. -U and -P specify the user login name and password. Click Finish to save the Application Launch task. This switch is either the DNS name or IP address of the target server. • • -F is the switch that gives the full path location and name of the RIBCL file that contains the actions to be performed on the board.TXT -V CPQLOCFG -S RIB3 -F C:\. 11.XML -L RIB2LOG. The resulting log file contains all commands sent to the Remote Insight board.. and a batch file.TXT -V .SCRIPT. . Do not use this switch if launching from HP SIM..SCRIPT. HP SIM will provide the address of the iLO 2 when CPQLOCFG. RIBNLOG -S RIBN -F C:\.10. These options allow the login information within the script file to be overridden.EXE is launched. • -V is the optional switch that turns on the verbose message return.TXT -V The Lights-Out Configuration Utility overwrites any existing log files.SCRIPT. only errors and responses from GET commands are logged without this switch.TXT -V CPQLOCFG -S RIB2 -F C:\. Be sure that the Lights-Out Configuration Utility is in a directory referenced by the PATH environment variable. • -L is the switch that defines where the log file will be generated and what the file name will be. Group administration and iLO 2 scripting 44 .. .XML -L LOGFILE. The components used by batch processing are the Lights-Out Configuration Utility. A default log file named with the DNS name or the IP address is created in the same directory where CPQLOCFG is launched. 12. The following example shows a sample batch file that can be used to perform the Group Administration for iLO 2: REM Updating the HP Integrated Lights-Out 2 board REM Repeat line for each board to be updated REM CPQLOCFG -S RIB1 -F C:\. NOTE: The -L parameter cannot designate an output log file..

hp.com/servers/lightsout) in the Best Practices section. Sample XML scripts are available on the HP website (http://www. Group administration and iLO 2 scripting 45 .See the "Remote Insight Command Language (on page 65)" section for information on the syntax of the XML data files.

............ Administrators can also use Perl to perform more complex tasks than cpqlocfg......... 48 Using Perl with the XML scripting interface The scripting interface provided enables administrators to manage virtually every aspect of the device in an automated fashion........21"> into the script sent to iLO 2...................................... Perl scripts require a valid user ID and password with appropriate privileges........ such as Perl scripts...... # Send the XML header and begin processing the file print $client '<?xml version="1.... • Perl script modification … # Open the SSL connection and the input file my $client = new IO::Socket::SSL->new(PeerAddr => $host).... the following steps can help ensure the iLO 2 firmware returns properly formatted XML............................51... If the iLO 2 firmware determines the client utility being used does not support the return of properly formatted XML syntax...... "\r\n"... open(F..... then the bold line in the following example can be added to return properly formatted XML syntax................ administrators use tools like the cpqlocfg...... Perl scripting 46 ..........exe.... the tag should be sent after <?xml version="1.............exe is currently 2.......0">............ You must incorporate <LOCFG version="2..............com/servers/lights-out) in the Best Practices section.... 46 XML enhancements.............0"?> and before the XML script is sent... This section discusses how to use Perl scripting in conjunction with the Lights-Out XML scripting language..... Administrators using a non-Windows® client can use Perl scripts to send XML scripts to the LightsOut devices... For customers using a utility other than cpqlocfg.... Primarily............ "<$file") || die "Can't open $file\n"..... If you are using the Perl script provided by HP. If placing the tag in the XML script...exe to assist deployment efforts... the tag should be placed before <RIBCL version="2.................................... If placing this tag in the Perl script.........Perl scripting In this section Using Perl with the XML scripting interface .. Sample XML scripts for Lights-Out devices and a sample Perl script are available on the HP website (http://www................... This tag can be placed in either the Perl script or the XML script......... the following message appears: <INFORM>Scripting utility should be updated to the latest version................................. Placement of this tag is important................. #Send tag to iLO firmware to insure properly formatted XML is returned............... XML enhancements Previous versions of iLO 2 firmware do not return properly formatted XML syntax...hp....... 46 Opening an SSL connection ....exe can perform... 47 Sending the XML header and script body.......0"?>' ....................</INFORM> This message informs the customer to update to a later version of the cpqlocfg scripting utility............. The latest version of cpqlocfg.............

… • XML script modification <!-The bold line could be added for the return of properly formatted XML. &SOCK_STREAM. Net::SSLeay::load_error_strings(). $sin. by default port 443. $ssl. use Net::SSLeay qw(die_now die_if_ssl_error). # # opens an ssl connection to port 443 of the passed host # sub openSSLconnection($) { my $host = shift. 0) or die "ERROR: socket: $!". &AF_INET. $ctx = Net::SSLeay::CTX_new() or die_now("ERROR: Failed to create SSL_CTX $! "). my ($ctx. if (not $ip = inet_aton($host)) { print "$host is a DNS Name. --> <LOCFG version="2. performing lookup\n" if $debug. socket (S.21">' . $sin) or die "connect: $!". "\r\n".\n".print $client '<LOCFG version="2. Net::SSLeay::SSLeay_add_ssl_algorithms(). print STDERR "Connecting to $nip:443\n".21"/> <RIBCL version="2. For example: use Socket. Net::SSLeay::randomize(). } $nip = inet_ntoa($ip). $ip = gethostbyname($host) or die "ERROR: Host $hostname not found. $ip.0"> <LOGIN USER_LOGIN="Adminname" PASSWORD = "password"> <!-Add XML script here. connect (S. $sin = sockaddr_in(443. $nip). --> </LOGIN> </RIBCL> </LOCFG> Opening an SSL connection Perl scripts must open an SSL connection to the device's HTTPS port. $ip). Perl scripting 47 .

Net::SSLeay::CTX_set_options($ctx, &Net::SSLeay::OP_ALL); die_if_ssl_error("ERROR: ssl ctx set options"); $ssl = Net::SSLeay::new($ctx) or die_now("ERROR: Failed to create SSL $!"); Net::SSLeay::set_fd($ssl, fileno(S)); Net::SSLeay::connect($ssl) and die_if_ssl_error("ERROR: ssl connect"); print STDERR 'SSL Connected '; print 'Using Cipher: ' . Net::SSLeay::get_cipher($ssl) if $debug; print STDERR "\n\n"; return $ssl;

}

Sending the XML header and script body
After the connection is established, the first line of script sent must be an XML document header, which tells the device's HTTPS web server that the following content is an XML script. The header must match the header used in the example exactly. After the header has been completely sent, the remainder of the script can be sent. In this example, the script is sent all at once. For example: # usage: sendscript(host, script) # sends the xmlscript script to host, returns reply sub sendscript($$) { my $host = shift; my $script = shift; my ($ssl, $reply, $lastreply, $res, $n); $ssl = openSSLconnection($host); # write header $n = Net::SSLeay::ssl_write_all($ssl, '<?xml version="1.0"?>'."\r\n"); rint "Wrote $n\n" if $debug; # write script $n = Net::SSLeay::ssl_write_all($ssl, $script); print "Wrote $n\n$script\n" if $debug; $reply = ""; $lastreply = ""; READLOOP: while(1) { $n++; $reply .= $lastreply; $lastreply = Net::SSLeay::read($ssl);

Perl scripting

48

die_if_ssl_error("ERROR: ssl read"); if($lastreply eq "") { sleep(2); # wait 2 sec for more text. $lastreply = Net::SSLeay::read($ssl); last READLOOP if($lastreply eq ""); } sleep(2); # wait 2 sec for more text. $lastreply = Net::SSLeay::read($ssl); last READLOOP if($lastreply eq ""); } print "READ: $lastreply\n" if $debug; if($lastreply =~ m/STATUS="(0x[0-9A-F]+)"[\s]+MESSAGE= '(.*)'[\s]+\/>[\s]*(([\s]|.)*?)<\/RIBCL>/) { if($1 eq "0x0000") { print STDERR "$3\n" if $3; } else { print STDERR "ERROR: STATUS: $1, MESSAGE: $2\n"; } } } $reply .= $lastreply; closeSSLconnection($ssl); } return $reply;

PERL scripts can also send a portion of the XML script, wait for the reply, and send more XML later. Using this technique, it is possible to use the reply produced by an earlier command as input to a later command. However, the PERL script must send data within a few seconds or the device will time out and disconnect. When using the XML scripting interface with PERL scripts, the following restrictions apply:
• • • •

PERL scripts must send the XML header before sending the body of the script. PERL scripts must provide script data fast enough to prevent the device from timing out. Only one XML document is allowed per connection, which means one pair of RIBCL tags. The device will not accept additional XML tags after a syntax error occurs. To send additional XML, a new connection must be established.

Perl scripting

49

Virtual Media scripting
In this section
Scripting Web server requirements........................................................................................................... 50 Using virtual media scripting ................................................................................................................... 50 Using Virtual Media on Linux servers through an SSH connection ................................................................ 51 Virtual media image files......................................................................................................................... 52 CGI helper application ........................................................................................................................... 52 Setting up IIS for scripted virtual media ..................................................................................................... 53

Scripting Web server requirements
Virtual Media scripting uses a media image that is stored and retrieved from a Web server accessible from the management network. The web server must be a HTTP 1.1 compliant server that supports the Range header. Furthermore, for write access to the file, the Web server should support DAV and must support the Content-Range header for DAV transactions. If the Web server does not meet the requirements for DAV, a helper CGI program may be used. The Web server may optionally be configured for basic HTTP authentication SSL support, or both.
Web Server Microsoft® IIS 5.0 Apache Apache/Win32 Read Support Yes Yes Yes Write Support Yes* Yes Yes Authorization Not tested Yes Yes SSL Support Not Tested Yes Yes

*IIS does not support Content-Range for DAV transactions. A CGI helper program must be used for write support.

Using virtual media scripting
Virtual media scripting is a method for controlling virtual media devices without going through the browser. Scriptable virtual media supports insert, eject, and status commands for floppy, USB key, and CD-ROM images. Virtual media scripting enables you to use other methods than a browser to configure iLO 2 for virtual media use. iLO 2 can be configured remotely using CPQLOCFG XML commands, locally using HPONCFG XML commands, or locally, using the HPLOVM utility that replaces the VFLOP utility from the SmartStart Scripting toolkit. NOTE: Virtual media scripting does not operate Virtual Media using the browser. Likewise, the browser does not support scripting capabilities. For example, a floppy disk mounted using the browser cannot later be dismounted using the scripting interface. The XML commands enable you to configure virtual media in the same manner as the virtual media applet. The one exception is that the actual image will be located on a Web server on the same network as iLO 2. After the image location is configured, iLO 2 retrieves the virtual media data directly from the web server.

Virtual Media scripting

50

eject. the VFLOP. 3. Command line syntax: HPLOVM [-device <floppy | cdrom>] [-insert <url>] [-eject] [-wp <y | n>] [-boot <once | always | never>] [-mgmt <ilo | riloe>] [-ver] [-?] Command Line Input [-device <floppy | cdrom>] [-insert <url>] [-eject] Result Defines which virtual media device is active. The default setting of this argument is iLO 2. 4. Defines how the virtual media drive is used to boot the target server.EXE is a new scripting utility that enables you to script insert. Log in to the iLO 2 through SSH (SSH connection from another Linux system. Enter vm floppy set connect to make the floppy or key drive available to the operating system. For example: VM Applet = Disconnected Boot Option = BOOT_ONCE Write Protect = Yes Image Inserted = Connected Virtual Media scripting 51 .NOTE: Virtual media scripting does not support composite devices. boot_always. the options are boot_once. Defines the write-protected status of the Virtual Floppy/USBKey drive. This argument has no effect on the Virtual CD-ROM drive.exe utility which is part of the SmartStart Scripting Toolkit. Displays help information. using PuTTY from Windows®). (Boot options can be configured with vm floppy set <option>. If RILOE is specified. Ejects the media that is currently connected through the virtual media drive. but no media is present in the drive. NOTE: USB key drives must be used with the floppy keyword syntax. The image is available to boot from. Enter vm floppy insert http://<address>/<image-name>. Only single Virtual Media devices (either Virtual Media Floppy/USBKey or Virtual Media CD-ROM) are supported. Defines the location of the virtual media image file that will be connected. 2. Enter vm floppy get to display the current status. The virtual media drive is still connected. 5.) Boot options from a USB key drive are only valid on servers with ProLiant USB key drive support. and no_boot. Displays the HPLOVM utility version. HPLOVM. HPLOVM is intended to be used in place of the VFLOP. but will not be seen by the operating system.EXE utility is used. Defines which management processor is being used with LOVM utility. and set boot options for virtual media devices. [-wp <y | n>] [-boot <once | always | never>] [-mgmt <ilo | riloe>] [-ver] [-?] Using Virtual Media on Linux servers through an SSH connection 1. Enter vm to display a list of commands available for Virtual Media.

or images created by the CPQIMAGE utility. Use lsmod to check that the following modules are loaded: • • • • usbcore usb-storage usb-ohci sd_mod If any of the modules are missing. Many CD-ROM burning utilities can create ISO-9660 images. Mounting Virtual Media on the Linux server: 1. unless a Virtual Floppy/USBKey or CD-ROM is connected through the graphical iLO 2 interface. use modprobe <module> to load them. The images created by the Virtual Media applet are raw disk images in the case of diskettes and ISO9660 images in the case of CD-ROMs.) mount /dev/scd0 /mnt/cdrom—Mounts a virtual CD-ROM on a SUSE system.The status of the Virtual Media applet is always disconnected.. The CD-ROM image should be in . No other type of CD-ROM images are supported. mount /dev/sda1 /mnt/keydrive—Mounts a virtual USB key drive. The Virtual Floppy/USBKey can be disconnected using the vm floppy set disconnect or vm floppy eject commands." or it might involve transforming an aliased URL path into the true path on the file system. produced by the iLO 2 Virtual Media applet.iso format. The helper script must transform the file parameter into a path relative to its working directory. It is not possible to specify a drive letter. 2. Virtual media image files Valid diskette images may be raw disk images. The floppy image can be created from a physical floppy by using rawrite or the image creation tool included with the Virtual Media applet in the graphical iLO 2 interface. The range parameter contains an inclusive range (in hexadecimal) designating where to write the data. the iLO 2 firmware posts a request to this application with three parameters: • • • The file parameter contains the name of the file provided in the original URL. mount /dev/cdrom1 /mnt/cdrom—Mounts a virtual CD-ROM on a Red Hat system. the DOS utility rawrite. Refer to the documentation of your utility for additional information. CD-ROM images must be ISO-9660 file system images. Diskette image files must have the appropriate permissions./. This function might involve prefixing it with ". The data parameter contains a hexadecimal string representing the data to be written. The helper script requires write access to the target file. the UNIX® utility dd. use cdrom instead of floppy. CGI helper application The following perl script is an example of a CGI helper application that allows diskette writes on Web servers that cannot perform partial writes. Mount the drive using one of following: • • • • mount /dev/sda /mnt/floppy -t vfat—Mounts a virtual floppy. To connect or disconnect a Virtual CD-ROM. When using the helper application. (Use /dev/cdrom if the server does not have a locally attached CD-ROM drive. The link to the Virtual Floppy/USBKey or CD-ROM image must be a URL. Example: Virtual Media scripting 52 .

$start + 1. # And the data my $data = $q->param('data'). # # Change the filename appropriately # $file = $prefix . # Byte range $range = $q->param('range'). binmode(F). make sure IIS is operational. a. $len = $end . } # # Decode the data (it's a big hex string) # $decode = pack("H*". $end = hex($2). $len. Use Internet Information Services (IIS) Manager to set up a simple website and verify that it is working correctly by browsing to the site. $data). my ($start.#!/usr/bin/perl use CGI. O_RDWR). # Get file to be written my $file = $q->param('file'). syswrite(F. SEEK_SET). $decode. $file. $start. Add a directory to your website and place your images in the directory. $file. Setting up IIS for scripted virtual media Before setting up IIS for scripted media. Configure IIS to serve diskette or ISO-9660 CD-ROM images for read-only access. # # The prefix is used to get from the current working # directory to the location of the image file# my ($prefix) = ". # # Write it to the target file # sysopen(F. close(F). $decode). # Get CGI data my $q = new CGI(). sysseek(F. 1. $end. $len). Virtual Media scripting 53 .. # # Decode the range # if ($range =~ m/([0-9A-Fa-f]+)-([0-9A-Fa-f]+)/) { $start = hex($1).". "/" . use Fcntl.

a. If not. and copy the script to that location. Verify that Perl is set up as a script interpreter. The IMAGE_URL can be either an http or https URL to a diskette or CD_ROM image. c. HP recommends you add the following types: . When present. The basic format of the URL is protocol://user:password@servername:port/path. The icon for you directory in IIS manager should change from a folder to a gear.iso—application/octet-stream 2. if you name your diskette images with the extension . Click Configuration on the properties page to view the application associations.POST. Using the properties page for your directory.img—application/octet-stream . # # The prefix is used to get from the current working directory # to the location of the image file you are writing # Virtual Media scripting 54 . servername is mandatory and is either the hostname or IP address of the web server. click Web Service Extensions and set Perl CGI Extension to Allowed. e. Verify your Web Service Extensions allows Perl scripts to execute. Set Execute Permissions to Scripts Only. Create a directory on your web site to hold the virtual media helper script. port is optional and specifies a web server on a non-standard port. Use the IIS manager to access the Properties dialog of your website. b. g. you must add a MIME type for that extension. Verify the prefix variable in the helper script is set correctly.b. For example. f. Verify that IIS can access the MIME type for the files you are serving. path is mandatory and refers to the image file being accessed. Additional information: The basic format for the XML insert command is: <INSERT_VIRTUAL_MEDIA DEVICE="device" IMAGE_URL="http://servername/path/to/file"/> • • The device field can be either FLOPPY or CDROM.img. click MIME Types to add additional MIME types. On the HTTP Headers tab. under Application Settings. helper-script is optional and refers to the location of the helper script on IIS web servers.exe "%s" %s GET. click Create to create an application directory.HEAD.helperscript where: • • • • • • protocol is mandatory and can be either http or https. Configure IIS for read/write access. d. http basic authorization is used. user:password portion is optional. Helper script: The following Perl script is a sample CGI helper script: #!/usr/bin/perl use CGI. Perl should be configured as pl c:\perl\bin\perl. Install Perl (if necessary). use Fcntl.

$data). close(F).$start + 1. print "\r\n". SEEK_SET). O_RDWR). $decode). syswrite(F. # Data to be written # # Merges the filename correctly # $file = $prefix .my ($prefix) = "c:/inetpub/wwwroot". sysseek(F. # Get CGI data my $file = $q->param('file'). # # Write it to the target file # sysopen(F. $start. # # Decode the range # if ($range =~ m/([0-9A-Fa-f]+)-([0-9A-Fa-f]+)/) { $start = hex($1). binmode(F). $end = hex($2). $end. $file. "/" . my $q = new CGI(). } $len = $end . Virtual Media scripting 55 . # File to be written my $range = $q->param('range'). print "Content-Length: 0\r\n". # # Decode the data (a large hex string) # $decode = pack("H*". $len). $len. my ($start. # Byte range to be written my $data = $q->param('data'). $decode. $file.

............................. HPONCFG online configuration utility 56 ..... If the driver is not installed......................................0/SUSE LINUX Enterprise Server 8 SUSE LINUX Enterprise Server 9 HPONCFG requirements • iLO 2-based server For an iLO 2-based server.... it must be downloaded and installed on the serve......... If the driver is not installed......... You can download the driver from the HP website (http://h18023. HPONCFG will warn if it cannot find the driver......... During execution.....................hp........................... the server must have the iLO 2 Management Interface Driver loaded................................... During execution.... The SmartStart operating system install process normally installs this driver.............. You can download the driver from the HP website (http://h18023........1 Red Hat Linux Enterprise Linux 3 Red Hat Linux Enterprise Linux 4 United Linux 1....................... 56 HPONCFG supported operating systems............................................ • RILOE II-based server For RILOE II-based servers..........................................html)................................................. 57 Using HPONCFG.................................com/support/files/lights-out/us/locate/20_5868...... The utility runs in a command line mode and must be executed from an operating system command line using an account with administrator or root access.................. 56 HPONCFG requirements...............html#0)................ 56 Installing HPONCFG .......hp. 58 HPONCFG The HPONCFG utility is an online configuration tool used to set up and configure the iLO 2 and RILOE II from within the Windows® and Linux operating systems without requiring a reboot of the server operating system.... HPONCFG supported operating systems HPONCFG is supported on: • • • • • • • Windows® 2000 Server Windows Server™ 2003 Red Hat Linux Enterprise Linux 2............com/support/files/lights-out/us/locate/20_5867................................................HPONCFG online configuration utility In this section HPONCFG..................................... it must be downloaded and installed on the server....www1............... HPONCFG will warn if it cannot find the driver..........www1... the server must have the RILOE II Management Interface Driver loaded.............................................

For Linux systems.dll file can be found in this subdirectory.exe. In the temporary directory.0-4. locate CP004791. This file can be installed separately from the component HP Insight Management Agents for Windows® 2000/Windows Server™ 2003.www1. The sm2user. The following is a list of supported HPONCFG rpm files and the Linux distributions they support.1 Red Hat Enterprise Linux 3. This will be the directory from which the HPONCFG utility is executed.0-4.40 is installed.2. See the "HPONCFG requirements (on page 56)" for details on where to obtain this driver and file.dll file.2.0 SUSE Linux Enterprise Server 9 HPONCFG online configuration utility 57 .hp.0-4.rpm Distribution Red Hat Enterprise Linux 2. that can be downloaded as a part of the ProLiant Support Pack on the HP website (http://h18004.For RILOE II-based servers.40 is installed.4 is part of SmartStart 7.html).rpm hponcfg-1.hp.linux.1.2. extract its contents to a temporary directory.2. This directory will also contain the XML-formatted input scripts.hp. Copy the sm2user. Installing HPONCFG The HPONCFG utility is delivered in separate packages for Windows® and Linux systems. HPONCFG 1. HPONCFG requires RILOE II firmware version 1. the server must have sm2user. The individual HPONCFG 1. For Windows® systems.2. • All servers For both iLO 2-based servers and RILOE II-based servers.www1.rpm hponcfg-1. During execution.dll file to the following directory on the server: Winnt\system32\. RPM supported hponcfg-1.dll file must also be installed. Extract the contents of this component to a temporary directory. To install HPONCFG. Be sure that the appropriate Management Interface Driver is installed.40. run the self-extracting executable delivered in this package from within a directory of your choice on the managed server.linux. and will store the output files from execution of the utility.com/support/files/server/us/download/18416.4 component cp005464.2. it is delivered as an RPM package file.2.com/support/files/lights-out/us/download/22834.rpm hponcfg-1.0 Red Hat Enterprise Linux 4 SUSE Linux Enterprise Server 8/ United Linux 1. For a server Windows® 2000/Windows® 2003.linux.com/support/files/lights-out/us/). Windows server installation HPONCFG will be installed automatically when ProLiant support pack version 7. After downloading the ProLiant Support Pack. In the temporary directory.0 for the respective Linux distributions can be downloaded from the HP website (http://h18023.13 or later. The rpm of HPONCFG 1.linux.linux. The sm2user.www1.rpm hponcfg-1. This file is automatically loaded along with the HP Insight Management Agents.2. HPONCFG will warn if it cannot find the sm2user. it requires RILOE II Management Interface Driver version 3.0 or later.exe can be downloaded from the HP website (http://h18023. Linux server installation HPONCFG will be installed automatically when ProLiant support pack version 7.2.0-4. locate the subdirectory cqmgserv. it is delivered as a smart component.0-4.dll loaded.html).

See the "HPONCFG requirements (on page 56)" for details on where to obtain this driver and file. The dualcursor command line option along with the mouse option will optimize mouse handling as suited for remote console dual cursor mode. Any data will be accepted in these fields.txt HPONCFG online configuration utility 58 . As an example for package installation. • The options must be preceded by a / (slash) for Windows® and . run the following command to remove the older version before installing the new version of HPONCFG: rpm –e hponcfg The hprsm RPM package must be installed on the system before installing the hponcfg RPM package. /get_hostinfo—Gets the host information. The 'allusers' command line option will optimize the mouse handling for all the users on the system.linux.or . /l <filename>—Log replies to the text log file that has name filename.html).Install the appropriate package using the RPM installation utility.txt > output.2. and that these fields contain data. formatted according to the rules of the RIBCL language. /m—Indicates to HPONCFG the minimum firmware level that should be present in the management device to execute the RIBCL script. the XML syntax requires that the USER_LOGIN and PASSWORD tags be present in the LOGIN tag.hp. there by optimizing graphical remote console performance.com/support/files/lightsout/us/download/24181. If at least this level of firmware is not present. although no authentication to the iLO 2 or the RILOE II is required. /reset—Resets the RILOE II or iLO 2 to factory default values.xml /l log. This option is available only for Windows®. Note that. An error message will be returned by HPONCFG if the user does not possess sufficient privileges.www1. A few sample scripts are included in the HPONCFG delivery package. Be sure that the appropriate Management Interface Driver is installed. Returns the server name and server serial number. By default it optimizes for remote console single cursor mode for the current user. After installation. the HPONCFG executable can be found in the /sbin directory. Using HPONCFG The HPONCFG configuration utility reads an XML input file. and produces a log file containing the requested output.rpm If an older version of hponcfg RPM package is already installed on the system. HPONCFG returns an error without performing any additional action.0-4. the utility must be invoked as Administrator on Windows® servers and as root on Linux servers.for Linux as specified in the usage string. /f <filename>—Sets the RILOE II or iLO 2 configuration from the information given in the XML input file that has name "filename. /mouse—Tells HPONCFG to configure the server for optimized mouse handling. A package containing various and comprehensive sample scripts is available for download on the HP website (http://h18004. hponcfg RPM on Red Hat Enterprise Linux 3 can be installed by: rpm -ivh hponcfg-1. HPONCFG command line parameters HPONCFG accepts the following command line parameters: • • • • • • • /help or ?—Displays the help page. To successfully execute HPONCFG." /w <filename>—Writes the RILOE II or iLO 2 configuration obtained from the device to the XML output file that has name filename. Example HPONCFG command line: HPONCFG /f add_user. Typical usage is to select a script that is similar to the desired functionality and modify it for the exact desired functionality.

Obtaining an entire configuration HPONCFG can be used to obtain an entire configuration from an iLO 2 or a RILOE II. HPONCFG accepts a correctly formatted XML script. HPONCFG displays a usage page if HPONCFG is entered with no command line parameters. HPONCFG displays a usage page if it is entered with no command line parameters.1"> <!--.Using HPONCFG on Windows servers Start the HPONCFG configuration utility from the command line.xml In this example. The following is a typical example of the contents of the output file: <HPONCFG VERSION = "1.exe is available by selecting Start>Run>cmd. the utility executes from the command line without specification of an input file.Generated 04/15/04 15:20:36 ---> <MOD_DIR_CONFIG> <DIR_AUTHENTICATION_ENABLED VALUE = "N"/> <DIR_LOCAL_USER_ACCT VALUE = "Y"/> <DIR_SERVER_ADDRESS VALUE = ""/> <DIR_SERVER_PORT VALUE = "25"/> <DIR_OBJECT_DN VALUE = " "/> <DIR_OBJECT_PASSWORD VALUE = ""/> <DIR_USER_CONTEXT_1 VALUE = ""/> <DIR_USER_CONTEXT_2 VALUE = "_"/> <DIR_USER_CONTEXT_3 VALUE = ""/> </MOD_DIR_CONFIG> HPONCFG online configuration utility 59 . HPONCFG sample scripts are included in the HPONCFG package. When using Microsoft® Windows®. Refer to the "Remote Insight Command Language (on page 65)" section for more information on formatting XML scripts. Using HPONCFG on Linux servers Invoke the HPONCFG configuration utility from the command line. For example: HPONCFG /w config. the utility indicated that it obtained the data successfully and wrote it to the output file as requested. The command line format is: HPONCFG [ /help | /? | /m firmwarelevel | /reset [/m firmwarelevel] | /f filename [/l filename][/xmlverbose or /v][/m firmwarelevel] | /w filename [/m firmwarelevel] | /get_hostinfo [/m firmwarelevel] | /mouse [/dualcursor][/allusers] ] Refer to the "HPONCFG command line parameters (on page 58)" section for an explanation of the usage. cmd. In this case. The name of the output file is given on the command line. The command line format is: hponcfg -? hponcfg -h hponcfg -m minFw hponcfg -r [-m minFw ] hponcfg -w filename [-m minFw] hponcfg -g [-m minFw] hponcfg -f filename [-l filename] [-v] [-m minFw] See the "HPONCFG command line parameters (on page 58)" section for an explanation of the usage. HPONCFG accepts as input an XML script formatted according to the rules of RIBCL (documented in the user guide in the section describing the use of CPQLOCFG).

net"/> <DHCP_GATEWAY VALUE = "Y"/> <DHCP_DNS_SERVER VALUE = "Y"/> <DHCP_STATIC_ROUTE VALUE = "Y"/> <DHCP_WINS_SERVER VALUE = "Y"/> <REG_WINS_SERVER VALUE = "Y"/> <PRIM_WINS_SERVER value = "16. <GET_GLOBAL_SETTINGS> <SESSION_TIMEOUT VALUE="15"/> <ILO_FUNCT_ENABLED VALUE="Y"/> HPONCFG online configuration utility 60 .txt.0" GATEWAY = "0. the following are the contents of a typical XML input file.0" GATEWAY = "0.0. is named log.0.81.xml: <!-.0.242"/> <DHCP_ENABLE VALUE = "Y"/> <DOMAIN_NAME VALUE = "americas.0.252.255.0" GATEWAY = "0.xml /l log.xml and are processed by the device: HPONCFG /f get_global.cpqcorp.<MOD_NETWORK_SETTINGS> <SPEED_AUTOSELECT VALUE = "Y"/> <NIC_SPEED VALUE = "100"/> <FULL_DUPLEX VALUE = "Y"/> <IP_ADDRESS VALUE = "16.100.0. Obtaining a specific configuration A specific configuration can be obtained using the appropriate XML input file. which.0.0.229"/> <SUBNET_MASK VALUE = "255.txt The requested information is returned in the log file.240. For example. in this example.81.0.0.0.0"/> <STATIC_ROUTE_2 DEST = "0.0"/> <GATEWAY_IP_ADDRESS VALUE = "16.1"/> <DNS_NAME VALUE = "ILOD234KJ44D002"/> <PRIM_DNS_SERVER value = "16.241.3. the user passwords are not returned. get_global.0.247"/> <STATIC_ROUTE_1 DEST = "0.0"> <LOGIN USER_LOGIN="x" PASSWORD="x"> <RIB_INFO MODE="read"> <GET_GLOBAL_SETTINGS /> </RIB_INFO> </LOGIN> </RIBCL> The XML commands are read from the input file get_global.Sample file for Get Global command --> <RIBCL VERSION="2.100.0"/> </MOD_NETWORK_SETTINGS> <ADD_USER USER_NAME = "Administrator" USER_LOGIN = "Administrator" PASSWORD = ""> </ADD_USER> <ADD_USER USER_NAME = "Landy9" USER_LOGIN = "mandy9" PASSWORD = ""> </ADD_USER> <RESET_RIB VALUE = "Y"/> </HPONCFG> For security reasons.0"/> <STATIC_ROUTE_3 DEST = "0.txt > output.3.0.

xml /l log. the input file has contents: <RIBCL VERSION="2. This feature would help to avoid re-writing HPONCFG online configuration utility 61 .txt In this example.2 and greater enables you to specify variables in the XML RIBCL script and to assign values to those variables when HPONCFG is executed. Variable substitution HPONCFG version 1.<F8_PROMPT_ENABLED VALUE="Y"/> <F8_LOGIN_REQUIRED VALUE="N"/> <TELNET_ENABLE VALUE="N"/> <PASSTHROUGH_CONFIG VALUE="1"/> <HTTPS_PORT VALUE="443"/> <HTTP_PORT VALUE="80"/> <REMOTE_CONSOLE_PORT VALUE="23"/> <TERMINAL_SERVICES_PORT VALUE="3389"/> <VIRTUAL_MEDIA_PORT VALUE="17988"/> <SSH_PORT VALUE="22"/> <SSH_STATUS VALUE="Y"/> <SERIAL_CLI_STATUS VALUE="Enabled-Authentication Required"/> <SERIAL_CLI_SPEED VALUE="9600"/> <MIN_PASSWORD VALUE="8"/> <REMOTE_KEYBOARD_MODEL VALUE="US"/> <RBSU_POST_IP VALUE="Y"/> <HIGH_PERFORMANCE_MOUSE VALUE="Automatic"> <REMOTE_CONSOLE_ACQUIRE VALUE="N"/> </GET_GLOBAL_SETTINGS> Setting a configuration A specific configuration can be sent to the iLO 2 or RILOE II by using the command format: HPONCFG /f add_user.0"> <LOGIN USER_LOGIN="x" PASSWORD="x"> <USER_INFO MODE="write"> <ADD_USER USER_NAME="Landy9" USER_LOGIN="mandy8" PASSWORD="floppyshoes"> <ADMIN_PRIV value ="No"/> <REMOTE_CONS_PRIV value ="Yes"/> <RESET_SERVER_PRIV value ="No"/> <VIRTUAL_MEDIA_PRIV value ="No"/> <CONFIG_ILO_PRIV value="Yes"/> </ADD_USER> </USER_INFO> </LOGIN> </RIBCL> The specified user will be added to the device.

HPONCFG /f add_user.xml. Any thing enclosed in between two ‘%’ characters in the XML file is considered as a variable.HOST_POWER="No" (Turns host server power off) --> <!-.login=”testlogin”.’ (comma).2" --> <!-.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <SERVER_INFO MODE="write"> <!-.Add user with minimal privileges to test default setting of assigned privileges to 'N' --> <RIBCL version="1. %loginname%.HPONCFG VERSION = "1. The name and location of the output file must be specified on the command line HPONCFG /w config.the file containing the XML script every time with different values.Modify the HOST_POWER attribute to toggle power on the host server --> <!-.xml /s username=”test user”. The variable name and its value must be separated by an equal sign (=).HOST_POWER="Yes" (Turns host server power on) --> <SET_HOST_POWER HOST_POWER="%host_power%"/> </SERVER_INFO> </LOGIN> </RIBCL> To power on the system.Generated 07/06/05 09:06:51 --> <RIBCL VERSION="2. Capture and restore a configuration HPONCFG can be used to capture the basic configuration of LOM management processors or a RILOE II in an XML readable file format. <!-. The argument to the option must be a string of variable name and value pairs separated by delimiter ‘.1"> <LOGIN USER_LOGIN="Administrator" PASSWORD="password"> <DIR_INFO MODE="write"> <MOD_DIR_CONFIG> HPONCFG online configuration utility 62 .A graceful shutdown will be attempted for ACPI-aware --> <!-. <RIBCL VERSION="2. and %password% are variables.password=testpasswd Example 2: In the this example %host_power% is a variable. The following is an example of the contents of the output file: <!-. --> <!-.xml /s host_power=NO. Example 1: In this example. %username%. enter HPONCFG /f Set_Host_Power.xml /s host_power=YES. enter HPONCFG /f Set_Host_Power.operating systems configured to support graceful shutdown. To power off the system. The utility displays a message when it successfully writes the configuration information to the output file as requested.2"> <LOGIN USER_LOGIN="x" PASSWORD="x"> <USER_INFO MODE="write"> <ADD_USER USER_NAME="%username%" USER_LOGIN="%loginname%" PASSWORD="%password%"> <RESET_SERVER_PRIV value="Y" /> <ADMIN_PRIV value="Y" /> </ADD_USER> </USER_INFO> </LOGIN> </RIBCL> Values for these variables can be specified at execution time using ‘substitute’ option.

252.240.0.0" GATEWAY = "0.0.0.0"/> <STATIC_ROUTE_3 DEST = "0.0"/> <PRIM_WINS_SERVER value = "16.255.0.0.0.100.net"/> <PRIM_DNS_SERVER value = "16.cpqcorp.0.0.0.0"/> <TER_DNS_SERVER value = "0.0.0" GATEWAY = "0.3.0"/> <STATIC_ROUTE_1 DEST = "0.0"/> </MOD_NETWORK_SETTINGS> <USER_INFO MODE="write"> <ADD_USER USER_NAME = "Username1" USER_LOGIN = "User1" PASSWORD = "%user_password%"> <ADMIN_PRIV value = "N"/> <REMOTE_CONS_PRIV value = "Y"/> <RESET_SERVER_PRIV value = "N"/> HPONCFG online configuration utility 63 .0.0.81.0.0"/> <GATEWAY_IP_ADDRESS VALUE = "16.241.0.0.0"/> <STATIC_ROUTE_2 DEST = "0.81.1"/> <DNS_NAME VALUE = "ILOD234KJ44D002"/> <DOMAIN_NAME VALUE = "americas.0.3.0.0.<DIR_AUTHENTICATION_ENABLED VALUE = "N"/> <DIR_LOCAL_USER_ACCT VALUE = "Y"/> <DIR_SERVER_ADDRESS VALUE = ""/> <DIR_SERVER_PORT VALUE = "636"/> <DIR_OBJECT_DN VALUE = ""/> <DIR_OBJECT_PASSWORD VALUE = ""/> <DIR_USER_CONTEXT_1 VALUE = ""/> <DIR_USER_CONTEXT_2 VALUE = ""/> <DIR_USER_CONTEXT_3 VALUE = ""/> </MOD_DIR_CONFIG> </DIR_INFO> <RIB_INFO MODE="write"> <MOD_NETWORK_SETTINGS> <SPEED_AUTOSELECT VALUE = "Y"/> <NIC_SPEED VALUE = "100"/> <FULL_DUPLEX VALUE = "Y"/> <DHCP_ENABLE VALUE = "Y"/> <DHCP_GATEWAY VALUE = "Y"/> <DHCP_DNS_SERVER VALUE = "Y"/> <DHCP_STATIC_ROUTE VALUE = "Y"/> <DHCP_WINS_SERVER VALUE = "Y"/> <REG_WINS_SERVER VALUE = "N"/> <IP_ADDRESS VALUE = "16.242"/> <SEC_DNS_SERVER value = "0.247"/> <SEC_WINS_SERVER value = "0.0" GATEWAY = "0.100.229"/> <SUBNET_MASK VALUE = "255.

2 and greater which writes the configuration information in HP RIBCL format. For example: HPONCFG /f config. A default password for all the users that will be added can be given using the substitute or s option. the configuration file must be given to HPONCFG as input to the “/f” or “-f” option. To restore the iLO or RILOE II configuration.xml /s user_password=password HPONCFG online configuration utility 64 . You can also be manually changed before using the file to restore configuration.<VIRTUAL_MEDIA_PRIV value = "N"/> <CONFIG_ILO_PRIV value = "N"/> </ADD_USER> </USER_INFO> </LOGIN> </RIBCL> The default user Administrator and user passwords are not captured in the configuration file or returned in the response for security reasons. A variable is provided in its place which can be used with the substitute option to provide a default password for all users when restoring the configuration. The configuration file generated by HPONCFG can be directly used to set or restore the configuration of the management processor. This feature is available with HPONCFG version 1.

.................... all of the commands are grouped by functionality............... All changes made within a single command block are applied simultaneously when the database is closed............................ an error message will be generated...................................................................................................... RIBCL sample scripts Sample scripts for all iLO 2 commands described in this section are available for download from the HP website (http://www........... refer to the "BL p-Class Configuration" section..................... 112 Overview of the Remote Insight Board Command Language The Remote Insight Board Command Language enables you to write scripts to manage user accounts and to configure settings.............................................. Any errors within the block cause the enclosed changes to be discarded....................................................... 105 SERVER_INFO ..... 67 LOGIN.................................................................................................................................................................... similar to a text document................................................................ 68 RIB_INFO ..................................Remote Insight command language In this section Overview of the Remote Insight Board Command Language.................................com/servers/lights-out)........... Grouping commands allows the firmware to view the data to be manipulated as a block of information.......... Remote Insight command language 65 ......... RIBCL and ProLiant BL p-Class Servers The "Remote Insight Command Language" section describes the XML commands and their parameters common to most LOM products and servers. For more information on ProLiant BL p-class server and rack XML commands............................................................................................................................................... If they do.......... allowing for multithreaded access to the different kinds of information........................hp............................................ An example of an opening command and its matching closing command are as follows: <USER_INFO> </USER_INFO> In all examples................ An opening command opens a database........................ The database remains open until the matching closing command is sent.... 65 RIBCL ............ IMPORTANT: Comments should not interrupt a command........ the opening and closing commands are displayed............................. 67 USER_INFO............. 76 DIR_INFO............................................ RIBCL general guidelines In this section................ All commands that manipulate user information are grouped together................................... 101 RACK_INFO ............................

The response indicates whether the command succeeded or failed.0”?> Data types The three data types that are allowed in the parameter are: • • • String Specific string Boolean string String A string is any text enclosed in quotes.XML header The XML header ensures the connection is an XML connection." These strings are not case sensitive. MSG This element contains a message describing the error that happened. Specific string A specific string is one that is required to contain certain characters. numbers." "false. or any printable character. The number 0x0000 indicates that there is no error. if a string is started with a double quote. Response definitions Every command that is sent to the iLO 2 generates a response. a single quote can be used within the string and the string must be closed with a double quote. Remote Insight command language 66 . Acceptable Boolean strings are "yes. The XML header is built into the cpqlocfg utility and has the following format: <?xml version=”1. The additional information is displayed in execution sequence. Example: <RESPONSE STATUS=“0x0001” /> • MSG=“There has been a severe error." "n. If no error occurred. A string may start with either a double or single quote and it must end with the same type of quote. For example. Some commands generate additional information." "no. The string may contain a quote if it is different from the string delimiter quotes. provided no errors occurred. the message No error appears." "t." and "f. you have a choice of words that are accepted as correct syntax and all other words produce an error. • • STATUS This parameter contains an error number.” RESPONSE This tag name indicates that the iLO 2 is sending a response to the previous commands back to the client application to indicate the success or failure of the commands that have been sent to the iLO 2." "true. It can include spaces. Boolean string A Boolean string is a specific string that specifies a "yes" or "no" condition." "y. not an HTTP connection. In general.

The RIBCL tags are required to mark the beginning and the end of the RIBCL document. The VERSION string is compared to the version of the RIBCL that is expected. and it must be the first command to display in the script. The preferred value for the VERSION parameter is "2. The specified user must have a valid account on the respective iLO 2 to execute RIBCL commands. however. and an error is returned if the privilege level does not match." The VERSION parameter is no longer checked for an exact match. Password must not be blank. This parameter is case sensitive and must never be blank. the utility returns an Overriding credentials warning message but still shows the error log message entry as Login name must not be blank. Example: <LOGIN USER_LOGIN="username" PASSWORD="password"> </LOGIN> Alternatively. Logged-in user does not have required privilege for this command. this parameter can never be blank. This parameter is case sensitive and can be a combination of any printable characters. You can use it only once to start an RIBCL session. The user's privileges are checked against the required privilege for a particular command.0. LOGIN The LOGIN command provides the information that is used to authenticate the user whose permission level will be used when performing RIBCL actions. the CPQLOCFG utility can specify the login information as parameters on its command line: cpqlocfg -u <username> -p <password> When using this format.RIBCL This command is used to start and end an RIBCL session. Example: <RIBCL VERSION="2. RIBCL runtime errors The possible RIBCL error messages include: Version must not be blank. LOGIN runtime errors The possible runtime error messages include: • • • User login name was not found. Remote Insight command language 67 . and an error is returned if the string and the version do not match. LOGIN parameters USER_LOGIN is the login name of the user account. PASSWORD is the password associated with the user.0"> </RIBCL> RIBCL parameters VERSION is a string that indicates the version of the RIBCL that the client application is expecting to use.

MODE is a specific string parameter with a maximum length of 10 characters that specifies what you intend to do with the information. Example: <USER_INFO MODE="write"> ……… USER_INFO commands …… </USER_INFO> ADD_USER The ADD_USER command is used to add a local user account. Only commands that are USER_INFO type commands are valid inside the USER_INFO command block. For this command to parse correctly. and USER_INFO MODE must be set to write. The USER_INFO command generates a response that indicates to the host application whether the database was successfully read or not. The USER_NAME and USER_LOGIN parameters must not exist in the current user database. The user must have the administrative privilege. This parameter can be a combination of any printable characters up to a maximum length of 39 characters. it reads the local user information database into memory and prepares to edit it.USER_INFO The USER_INFO command can only appear within a LOGIN command block. This parameter is case sensitive and must never be blank. All of the attributes that pertain to the user are set using the following parameters.0"> <LOGIN USER_LOGIN="loginname" PASSWORD="password"> <USER_INFO MODE="write"> <ADD_USER USER_NAME="User" USER_LOGIN="username" PASSWORD="password"> <ADMIN_PRIV value ="No"/> <REMOTE_CONS_PRIV value ="Yes"/> <RESET_SERVER_PRIV value ="No"/> <VIRTUAL_MEDIA_PRIV value ="No"/> <CONFIG_ILO_PRIV value ="No"/> </ADD_USER> </USER_INFO> </LOGIN> </RIBCL> ADD_USER parameters USER_NAME is the actual name of the user. USER_INFO requires the MODE parameter with a value of read or write. This parameter is case sensitive and must never be blank. <RIBCL VERSION="2. then this call will fail. When the command is parsed. USER_LOGIN is the name used to gain access to the respective iLO 2. the command must appear within a USER_INFO command block. Remote Insight command language 68 . Write mode enables both reading and writing of iLO 2 information. If database is open for writing by another application. Read mode prevents modification of the iLO 2 information. This parameter can be a combination of any printable characters up to a maximum length of 39 characters. Use the MOD_USER command to change an existing user's information.

This parameter is optional. the Boolean string value must never be blank. Remote Insight command language 69 . Insight Manager settings. and delete users. the Boolean string value must never be blank. and the Boolean string must be set to "Yes" if the user should have this privilege. REMOTE_CONS_PRIV is a Boolean parameter that gives permission for the user to access the Remote Console functionality.1x and higher. CONFIG_ILO_PRIV is a Boolean parameter that allows the user to configure iLO settings. This parameter is optional. VIEW_LOGS_PRIV is a Boolean parameter that gives the user permission to view the iLO 2 system logs. The parameters will parse correctly. CONFIG_RACK_PRIV is a Boolean parameter that gives the user permission to configure and manage the server rack resources.PASSWORD is the password associated with the user. This parameter is optional. This parameter is case sensitive and can be a combination of any printable characters. This parameter is optional. DIAG_PRIV is a Boolean parameter that gives the user permission to view diagnostic information about iLO 2. Omitting this parameter prevents the user from manipulating the server power settings. If this parameter is used. the Boolean string value must never be left blank. and SNMP settings. the Boolean string value must never be blank. This parameter is optional. and the Boolean string must be set to "Yes" if the user should be allowed to view logs. This parameter is optional. Omitting this parameter denies the user access to Remote Console functionality. The user can modify their account settings. CLEAR_LOGS_PRIV is a Boolean parameter that gives the user permission to clear the event log. This parameter is optional. the Boolean string value must never be blank. This parameter is optional. the Boolean string value must never be left blank. ADMIN_PRIV is a Boolean parameter that allows the user to administer user accounts. This parameter is optional. add users. the Boolean string value must never be blank. deleting. Omitting this parameter prevents the user from manipulating the current iLO 2 configuration. If this parameter is used. and the Boolean string must be set to "Yes" if the user should be allowed to clear the iLO 2 event log. The following parameters are not applicable to a user's privileges in the iLO firmware versions 1. If this parameter is used. If this parameter is used. This privilege includes network settings. If this parameter is used. UPDATE_ILO_PRIV is a Boolean parameter that allows the user to copy a new firmware image into the iLO 2 system ROM. If this parameter is used. Omitting this parameter denies the user virtual media privileges. If this parameter is used. and the Boolean string must be set to "Yes" if the user should be allowed to use EMS services. If this parameter is used. modify other user account settings. and the Boolean string must be set to "Yes" if the user should have this privilege. the Boolean string value must never be blank. and the Boolean string must be set to "Yes" if the user should have this privilege. EMS_PRIV is a Boolean parameter that gives the user permission to use the Windows® Server 2003 EMS service.40 and higher and iLO 2 firmware versions 1. and the Boolean string must be set to "Yes" if the user should have diagnostic privileges. If this parameter is used. The minimum length is defined in the iLO 2 Global Settings and has a default value of eight characters. but user privileges will not be affected. This parameter is applicable to ProLiant BL p-Class servers only. This parameter is optional. and the Boolean string must be set to "Yes" if the user should be allowed to configure iLO 2. the Boolean string value must never be left blank. and the Boolean string must be set to "Yes" if the user should have this privilege. RESET_SERVER_PRIV is a Boolean parameter that gives the user permission to remotely manipulate the server power setting. If this parameter is used. VIRTUAL_MEDIA_PRIV is a Boolean parameter that gives the user permission to access the virtual media functionality. global settings. the Boolean string value must never be blank. Omitting this parameter prevents the user from adding. and the Boolean string must be set to "Yes" if the user should be allowed to manage or configure rack resources. or configuring user accounts. The length is user defined and can be a minimum of zero characters and a maximum of 39 characters.

The user must have the administrative privilege.ADD_USER runtime errors The possible ADD_USER error messages include: • • • • • • • • • • Login name is too long. User does not have correct privilege for action. Password is too long. Cannot add user. User information is open for read-only access. No room for new user. For this command to parse correctly. DELETE_USER The DELETE_USER command is used to remove an existing local user's account. Boolean value not specified. User login name was not found. and USER_INFO MODE must be set to write. User does not have correct privilege for action. the command must appear within a USER_INFO command block. Write access is required for this operation. DELETE_USER runtime errors The possible DELETE_USER errors include: • • • • • User information is open for read-only access. User table is full. User login ID cannot be blank. Cannot delete user information for currently logged in user. The user name already exists. Password is too short. For this command to parse Remote Insight command language 70 . This parameter is case sensitive and must never be blank. The USER_LOGIN parameter must exist in the current user database. DELETE_CURRENT_USER The DELETE_CURRENT_USER command is used to remove the user account defined by the USER_LOGIN attribute. The USER_LOGIN parameter must exist in the current user database.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <USER_INFO MODE="write"> <DELETE_USER USER_LOGIN="username"/> </USER_INFO> </LOGIN> </RIBCL> DELETE_USER parameter USER_LOGIN is the login name of the user account. ADMIN_PRIV required. User login name must not be blank. Write access is required for this operation. Example: <RIBCL VERSION="2. ADMIN_PRIV required. User name cannot be blank.

0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <USER_INFO MODE="write"> <DELETE_CURRENT_USER/> </USER_INFO> </LOGIN> </RIBCL> DELETE_CURRENT_USER parameters None DELETE_CURRENT_USER runtime errors The possible DELETE_CURRENT_USER errors include: User information is open for read-only access. the command must appear within a USER_INFO command block. the command must appear within a USER_INFO command block. Example: <RIBCL VERSION="2. GET_USER The GET_USER command will return a local user's information. The user must have the administrative privilege. The USER_LOGIN parameter must exist in the current user database. User login name was not found. Remote Insight command language 71 . The user must have the administrative privilege to retrieve other user accounts. For this command to parse correctly. and USER_INFO MODE must be set to write. and USER_INFO MODE can be in read or write. User does not have correct privilege for action. Example: <RIBCL VERSION="2. else the user can only view their individual account information. Write access is required for this operation. ADMIN_PRIV required. excluding the password. GET_USER runtime errors The possible GET_USER error messages include: • • • User login name must not be blank. This parameter is case sensitive and must never be blank.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <USER_INFO MODE="read"> <GET_USER USER_LOGIN="username"/> </USER_INFO> </LOGIN> </RIBCL> GET_USER parameter USER_LOGIN is the login name of the user account. This command is intended for customers who desire to delete all user accounts on iLO 2.correctly.

For this command to parse correctly. the command must appear within a USER_INFO command block. The USER_LOGIN parameter must exist in the current user database. The user must have the administrative privilege. and USER_INFO MODE must be set to write. A user without the administrative privilege can only modify their individual account password.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <USER_INFO MODE="write"> <MOD_USER USER_LOGIN="loginname"> <USER_NAME value="username"/> <USER_LOGIN value="newloginname"/> <PASSWORD value="password"/> <ADMIN_PRIV value="No"/> <REMOTE_CONS_PRIV value="Yes"/> <RESET_SERVER_PRIV value="No"/> <VIRTUAL_MEDIA_PRIV value="No"/> <CONFIG_ILO_PRIV value="Yes"/> </MOD_USER> </USER_INFO> </LOGIN> </RIBCL> Reset administrator password example: <RIBCL VERSION="2. Example: <RIBCL VERSION="2.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <USER_INFO MODE="write"> <MOD_USER USER_LOGIN="Administrator"> <PASSWORD value="password"/> Remote Insight command language 72 .GET_USER return messages A possible GET_USER return message includes: <RESPONSE STATUS="0x0000" /> MSG="No Errors" <GET_USER USER_NAME="Admin User" USER_LOGIN= "username" ADMIN_PRIV="N" REMOTE_CONS_PRIV="Y" RESET_SERVER_PRIV="N" VIRTUAL_MEDIA_PRIV="N" /> CONFIG_ILO_PRIV value ="No" MOD_USER The MOD_USER command is used to modify an existing local user’s account.

Omitting this parameter prevents the user from adding. or configuring user accounts. ADMIN_PRIV is a Boolean parameter that allows the user to administer user accounts. This parameter is case sensitive. This parameter is optional. Omitting this parameter denies the user access to Remote Console functionality. Insight Manager settings. VIRTUAL_MEDIA_PRIV is a Boolean parameter that gives the user permission to access the virtual media functionality. This parameter is case sensitive and must never be blank. This parameter is case sensitive and must never be blank. deleting. Omitting this parameter prevents the user from manipulating the server power settings. and the Boolean string must be set to "Yes" if the user should have this privilege. If this parameter is used. RESET_SERVER_PRIV is a Boolean parameter that gives the user permission to remotely manipulate the server power setting. This parameter is case sensitive and can be a combination of any printable characters. This string is used for display only and must never be blank. add users. PASSWORD is the password associated with the user. If this parameter is used. and the Boolean string must be set to "Yes" if the user should have this privilege. USER_LOGIN is the name used to gain access to the respective iLO 2. and the Boolean string must be set to "Yes" if the user should have this privilege. This parameter is optional. and has a maximum length of 39 characters.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <USER_INFO MODE="write"> <MOD_USER USER_LOGIN="username"> <PASSWORD value="newpassword"/> </MOD_USER> </USER_INFO> </LOGIN> </RIBCL> MOD_USER parameters USER_LOGIN is the login name of the user account. If the following parameters are not specified. the Boolean string value must never be left blank. the Boolean string value must never be left blank. The user can modify their account settings. Remote Insight command language 73 . REMOTE_CONS_PRIV is a Boolean parameter that gives permission for the user to access the Remote Console functionality. and delete users. This privilege includes network settings. This parameter is optional. CONFIG_ILO_PRIV is a Boolean parameter that allows the user to configure iLO settings. The minimum length is defined in the iLO 2 Global Settings and has a default value of eight characters. This parameter can be a combination of any printable characters up to a maximum length of 39 characters. global settings. the Boolean string value must never be blank. and the Boolean string must be set to "Yes" if the user should have this privilege. If this parameter is used. If this parameter is used. then the parameter value for the specified user is preserved. The length is user defined and can be a minimum of zero characters and a maximum of 39 characters. and SNMP settings. can be any valid string.</MOD_USER> </USER_INFO> </LOGIN> </RIBCL> Change password example: <RIBCL VERSION="2. USER_NAME is the actual name of the user to be added. modify other user account settings. Omitting this parameter prevents the user from manipulating the current iLO 2 configuration. This parameter is optional. the Boolean string value must never be left blank. Omitting this parameter denies the user virtual media privileges.

ADMIN_PRIV required. User does not have correct privilege for action. User login name must not be blank. ADMIN_PRIV required. GET_ALL_USERS The GET_ALL_USERS command will return all USER_LOGIN parameters in the user database. and USER_INFO MODE can be in read or write. the command must appear within a USER_INFO command block. GET_ALL_USERS return messages A possible GET_ALL_USERS return message is: <RESPONSE STATUS="0x0000" MESSAGE='No Error' /> <GET_ALL_USERS> <USER_LOGIN VALUE="username"/> <USER_LOGIN VALUE="user2"/> <USER_LOGIN VALUE="user3"/> <USER_LOGIN VALUE="user4"/> <USER_LOGIN VALUE="user5"/> <USER_LOGIN VALUE="user6"/> Remote Insight command language 74 . Write access is required for this operation. User information is open for read-only access. For this command to parse correctly. Cannot modify user information for currently logged user. Example: <RIBCL VERSION="2.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <USER_INFO MODE="read"> <GET_ALL_USERS /> </USER_INFO> </LOGIN> </RIBCL> GET_ALL_USERS parameters None GET_ALL_USERS runtime errors The possible GET_ALL_USERS error messages include: User does not have correct privilege for action. Password is too long. Password is too short.MOD_USER runtime errors The possible MOD_USER error messages include: • • • • • • • Login name is too long. The user must have the administrative privilege to retrieve all user accounts.

<USER_LOGIN VALUE="user7"/> <USER_LOGIN VALUE="user8"/> <USER_LOGIN VALUE="user9"/> <USER_LOGIN VALUE="user10"/> <USER_LOGIN VALUE=""/> <USER_LOGIN VALUE=""/> </GET_ALL_USERS> A possible unsuccessful request is: <RESPONSE STATUS="0x0023" MESSAGE='User does NOT have correct privilege for action. ADMIN_PRIV required.'

/>

GET_ALL_USER_INFO
The GET_ALL_USER_INFO command will return all local users information in the user database, excluding passwords. For this command to parse correctly, the command must appear within a USER_INFO command block, and USER_INFO MODE can be in read or write. The user must have administrative privilege to execute this command. Example: <RIBCL VERSION="2.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <USER_INFO MODE="read"> <GET_ALL_USER_INFO /> </USER_INFO> </LOGIN> </RIBCL>

GET_ALL_USER_INFO parameters
None

GET_ALL_USER_INFO runtime errors
The possible GET_ALL_USER_INFO error message include: User does not have correct privilege for action. ADMIN_PRIV required.

GET_ALL_USER_INFO return messages
A possible GET_ALL_USER_INFO return message is: <GET_ALL_USER_INFO/> <GET_USER USER_NAME="Admin" USER_LOGIN="Admin" ADMIN_PRIV="Y" CONFIG_RILO_PRIV="Y" LOGIN_PRIV="Y"

Remote Insight command language 75

REMOTE_CONS_PRIV="Y" RESET_SERVER_PRIV="Y" VIRTUAL_MEDIA_PRIV="Y" /> ...... The same information will be repeated for all the users. </GET_ALL_USER_INFO> A possible unsuccessful request is: <RESPONSE STATUS="0x0023" MESSAGE='User does NOT have correct privilege for action. ADMIN_PRIV required.'

/>

RIB_INFO
The RIB_INFO command can only appear within a LOGIN command block. When the command is parsed, it reads the iLO 2 configuration information database into memory and prepares to edit it. Only commands that are RIB_INFO type commands are valid inside the RIB_INFO command block. The RIB_INFO command generates a response that indicates to the host application whether the database was successfully read or not. If the database is open for writing by another application, then this call will fail. RIB_INFO requires the MODE parameter with a value of read or write. MODE is a specific string parameter with a maximum length of 10 characters that specifies what you intend to do with the information. Write mode enables both reading and writing of iLO 2 information. Read mode prevents modification of the iLO 2 information. Example: <RIB_INFO MODE="write"> ……… RIB_INFO commands …… </RIB_INFO> Clear iLO 2 event log example: <RIBCL VERSION="2.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <RIB_INFO MODE="write"> <CLEAR_EVENTLOG/> </RIB_INFO> </LOGIN> </RIBCL>

RESET_RIB
The RESET_RIB command is used to reset iLO 2. For this command to parse correctly, the command must appear within a RIB_INFO command block, and RIB_INFO MODE can be set to read or write. The user must have the configure iLO 2 privilege to execute this command. Example: <RIBCL VERSION="2.0"> <LOGIN USER_LOGIN="Admin" PASSWORD="Password"> <RIB_INFO MODE = "write"> <RESET_RIB/>

Remote Insight command language 76

</RIB_INFO> </LOGIN> </RIBCL>

RESET_RIB parameters
None

RESET_RIB runtime errors
The possible RESET_RIB error message include: User does not have correct privilege for action. CONFIG_ILO_PRIV required.

GET_EVENT_LOG
The GET_EVENT_LOG command retrieves the iLO 2 Event Log or the Integrated Management log, depending on the context of the command. For this command to parse correctly, the command must appear within a RIB_INFO or SERVER_INFO command block. To retrieve the iLO 2 Event Log, use the RIB_INFO command block. To retrieve the Integrated Management log use, the SERVER_INFO command block. Examples:

iLO 2 Event Log example: <RIBCL version="2.21"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <RIB_INFO MODE="READ"> <GET_EVENT_LOG /> </RIB_INFO> </LOGIN> </RIBCL>

Integrated Management log example: <RIBCL version="2.21"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <SERVER_INFO MODE="READ"> <GET_EVENT_LOG /> </SERVER_INFO> </LOGIN> </RIBCL>

GET_EVENT_LOG parameters
None

GET_EVENT_LOG runtime errors
GET_EVENT_LOG returns a runtime error if it is not called from within the RIB_INFO or SERVER_INFO block. For example: <RIBCL VERSION="2.21"> <RESPONSE STATUS="0x0001" MESSAGE='Syntax error: Line #3: syntax error near ">" in the line: " GET_EVENT_LOG >"'

Remote Insight command language 77

power. This might not indicate a platform issue. rack infrastructure. REPAIRED indicates that an event or component failure has been addressed. </EVENT_LOG> Remote Insight command language 78 . Each event includes a common set of attributes: • SEVERITY indicates the importance of the error and how it might impact server or iLO 2 availability. • • • • FAILED indicates a problem or component failure that might impact operational time if it is not addressed. Events are not sorted by severity or other criteria. CAUTION indicates an event that is not expected during normal system operation.. DESCRIPTION indicates the nature of the event and all recorded details. and can include iLO 2." /> . in the order that they occurred. system error. environment. INFORMATIONAL indicates that something noteworthy occurred. INITIAL_UPDATE indicates when this event first occurred. The following response is typical of the data returned from the iLO 2 Event Log: <EVENT_LOG DESCRIPTION="iLO Event Log"> <EVENT SEVERITY="Caution" CLASS="iLO" LAST_UPDATE="04/04/2004 12:34" INITIAL_UPDATE="04/04/2004 12:34" COUNT="1" DESCRIPTION="Server reset./> </RIBCL> GET_EVENT_LOG return messages The response includes all of the events recorded.. LAST_UPDATE indicates the most recent time this event was modified. • • • • • CLASS indicates the subsystem that generated the event. and more. COUNT indicates the number of times a duplicate event happened.ProLiant Storage System not Responding" /> . </EVENT_LOG> The following response is typical of the data returned from the Integrated Management Log: <EVENT_LOG DESCRIPTION="Integrated Management Log"> <EVENT SEVERITY="Caution" CLASS="POST Message" LAST_UPDATE="04/04/2004 12:34" INITIAL_UPDATE="04/04/2004 12:34" COUNT="1" DESCRIPTION="POST Error: 1775-Drive Array . but operational time is not impacted...

and RIB_INFO MODE must be set to write. the command must appear within a RIB_INFO command block. For this command to parse correctly. The user must have the configure iLO 2 privilege to execute this command. User does not have correct privilege for action. GET_NETWORK_SETTINGS The GET_NETWORK_SETTINGS command requests the respective iLO 2 network settings. the command must appear within a RIB_INFO command block. CONFIG_ILO_PRIV required.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <RIB_INFO MODE="read"> <GET_NETWORK_SETTINGS/> </RIB_INFO> </LOGIN> </RIBCL> GET_NETWORK_SETTINGS parameters None GET_NETWORK_SETTINGS runtime errors None GET_NETWORK_SETTINGS return messages A possible GET_NETWORK_SETTINGS return message is: <ENABLE_NIC VALUE="Y"/> <SHARED_NETWORK_PORT VALUE="N"/> Remote Insight command language 79 .CLEAR_EVENTLOG The CLEAR_EVENTLOG command clears the iLO 2 Event Log.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <RIB_INFO MODE="write"> <CLEAR_EVENTLOG/> </RIB_INFO> </LOGIN> </RIBCL> CLEAR_EVENTLOG parameters None CLEAR_EVENTLOG runtime errors The possible CLEAR_EVENTLOG error messages are: • • RIB information is open for read-only access. Example: <RIBCL VERSION="2. For this command to parse correctly. Example: <RIBCL VERSION="2. and RIB_INFO MODE can be set to read or write. Write access is required for this operation.

0.255.0"/> <STATIC_ROUTE_3 DEST="0.163.0.0.<VLAN ENABLED="N"/> <VLAN_ID VALUE="0"/> <SPEED_AUTOSELECT VALUE="Y"/> <NIC_SPEED VALUE="10"/> <FULL_DUPLEX VALUE="N"/> <DHCP_ENABLE VALUE="Y"/> <DHCP_GATEWAY VALUE="Y"/> <DHCP_DNS_SERVER VALUE="Y"/> <DHCP_WINS_SERVER VALUE="Y"/> <DHCP_STATIC_ROUTE VALUE="Y"/> <DHCP_DOMAIN_NAME VALUE="Y"/> <REG_WINS_SERVER VALUE="Y"/> <REG_DDNS_SERVER VALUE="Y"/> <PING_GATEWAY VALUE="N"/> <MAC_ADDRESS VALUE="00:12:79:a5:25:42"/> <IP_ADDRESS VALUE="170.100. the command must appear within a RIB_INFO command block. the management processor ignores commands Remote Insight command language 80 .0.199"/> <SEC_WINS_SERVER VALUE="0.0. When modifying network settings.8.0" GATEWAY="0. The user must have the configure iLO 2 privilege to execute this command.0. For this command to parse correctly.0"/> <STATIC_ROUTE_2 DEST="0.0.199"/> <SEC_DNS_SERVER VALUE="0.0.com"/> <PRIM_DNS_SERVER VALUE="172.0.0.8. The iLO 2 scripting firmware does not attempt to decipher if the network modifications are appropriate for the network environment.0"/> <TER_DNS_SERVER VALUE="0.0. and RIB_INFO MODE must be set to write.0.0"/> <GATEWAY_IP_ADDRESS VALUE="170.0. In some cases.0"/> <PRIM_WINS_SERVER VALUE="172.0.100.255.0"/> <STATIC_ROUTE_1 DEST="0.0"/> </GET_NETWORK_SETTINGS> A possible unsuccessful request is: <RESPONSE STATUS = "0x0001" MSG = "Error Message"/> MOD_NETWORK_SETTINGS MOD_NETWORK_SETTINGS is used to modify network settings.0" GATEWAY="0.25.254"/> <DNS_NAME VALUE="ILO000FWDC451"/> <DOMAIN_NAME VALUE="ferrari.0.0. be aware of the network commands provided to the management processor.163.0" GATEWAY="0.10"/> <SUBNET_MASK VALUE="255.0.0.25.

0. Changing the network settings to values that are not correct for the network environment might cause a loss of connectivity to iLO 2.0.0. If connectivity to iLO 2 is lost.0.0.60.in a server enclosure.0.0.1"/> <DNS_NAME value="demoilo"/> <DOMAIN_NAME value="internal.0.0"/> <PRIM_WINS_SERVER value="0.20.xml --> <!-.<ENCLOSURE_IP_ENABLE VALUE="Yes"/> --> </MOD_NETWORK_SETTINGS> </RIB_INFO> </LOGIN> Modify VLAN example: Remote Insight command language 81 .0" GATEWAY="0.0"/> <TER_DNS_SERVER value="0.0.0.and no error is returned.0.255.0.0.0"/> <SEC_WINS_SERVER value="0.0"/> <STATIC_ROUTE_3 DEST="0.This tag can be used on an iLO blade server to force iLO <!-.0"/> <SEC_DNS_SERVER value="0.0"/> <STATIC_ROUTE_1 DEST="0. Example: <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <RIB_INFO MODE="write"> <MOD_NETWORK_SETTINGS> <ENABLE_NIC value="Yes"/> <REG_DDNS_SERVER value="Yes"/> <PING_GATEWAY value="No"/> <DHCP_DOMAIN_NAME value="Yes"/> <SPEED_AUTOSELECT value="YES"/> <NIC_SPEED value="100"/> <FULL_DUPLEX value="Yes"/> <DHCP_ENABLE value="No"/> <IP_ADDRESS value="172.0" GATEWAY="0. --> <!-.0. The iLO 2 management processor reboots to apply the changes after the script has successfully completed.0"/> <!-.to attempt to get an IP address from the signal backplane --> The IP address must be set prior --> <!-.0.0.0"/> <GATEWAY_IP_ADDRESS value="172.with Mod_Enc_Bay_IP_Settings.0.152"/> <SUBNET_MASK value="255.0.com"/> <DHCP_GATEWAY value="Yes"/> <DHCP_DNS_SERVER value="Yes"/> <DHCP_WINS_SERVER value="Yes"/> <DHCP_STATIC_ROUTE value="Yes"/> <REG_WINS_SERVER value="Yes"/> <PRIM_DNS_SERVER value="0.255.0.20.0" GATEWAY="0.0.0"/> <STATIC_ROUTE_2 DEST="0. the IP address is ignored. use RBSU to reconfigure the network settings to values that are compatible with the network environment.60. For example.0.0. when a script includes the command to enable DHCP and a command to modify the IP address.

" It is case insensitive. ProLiant server DL320G3 DL360 G4 Minimum iLO firmware version 1. Consequently. The values are "Yes" or "No. an empty string deletes the current value in some fields.Desired NIC: Substitute: --> <!-.21"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <RIB_INFO MODE="WRITE" > <MOD_NETWORK_SETTINGS> <!-.64 1. The values are "Yes" or "No. ENABLE_NIC enables the NIC to reflect the state of iLO 2. both the NIC and iLO 2 firmware must support the feature.iLO NIC <SHARED_NETWORK_PORT VALUE="N"/> --> <!-.21"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <RIB_INFO MODE="WRITE" > <MOD_NETWORK_SETTINGS> <SHARED_NETWORK_PORT VALUE="Yes"/> <VLAN_ENABLED VALUE="Yes"/> <VLAN_ID VALUE="1"/> </MOD_NETWORK_SETTINGS> </RIB_INFO> </LOGIN> </RIBCL> RBSU POST IP example: <RIBCL version="2. then the parameter value for the specified setting is preserved.<RIBCL version="2. In addition to the hardware.Host NIC <SHARED_NETWORK_PORT VALUE="Y"/ --> <SHARED_NETWORK_PORT VALUE="N"/> </MOD_NETWORK_SETTINGS> </RIB_INFO> </LOGIN> </RIBCL> MOD_NETWORK_SETTINGS parameters If the following parameters are not specified.60 Remote Insight command language 82 .21"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <RIB_INFO MODE="write" > <MOD_GLOBAL_SETTINGS> <RBSU_POST_IP VALUE="Y"/> </MOD_GLOBAL_SETTINGS> </RIB_INFO> </LOGIN> </RIBCL> Shared network port example: <RIBCL version="2. SHARED_NETWORK_PORT is used to set the iLO 2 Shared Network Port value." The iLO 2 Shared Network Port feature is only available on servers with hardware that supports this feature. Zero values are not permitted in some fields.

64 When using the iLO 2 Shared Network Port. The possible values are "Yes" or "No. the current value is deleted. GATEWAY_IP_ADDRESS is used to select the default gateway IP address for the iLO 2 if DHCP is not enabled. The possible values are "Yes" or "No. This selection is only valid if DHCP is enabled. SUBNET_MASK is used to select the subnet mask for the iLO 2 if DHCP is not enabled. IP_ADDRESS is used to select the IP address for the iLO 2 if DHCP is not enabled. DHCP_WINS_SERVER specifies if the DHCP-assigned WINS server is to be used." SPEED_AUTOSELECT is a Boolean parameter to enable or disable the iLO 2 transceiver to auto-detect the speed and duplex of the network." Any other values will result in a syntax error. FULL_DUPLEX is used to decide if the iLO 2 is to support full-duplex or half-duplex mode. the current value is deleted. Values must be between 1 and 4094. It is only applicable if SPEED_AUTOSELECT was set to "No." It is case sensitive. NIC_SPEED is used to set the transceiver speed if SPEED_AUTOSELECT was set to "No.60 1. Remote Insight command language 83 . The possible values are "Yes" or "No. If an empty string is entered. the Boolean string value must never be left blank.ProLiant server DL360 G4 DL380 G4 DL385 G1 DL580 G3 ML370 G4 ML570 G3 Minimum iLO firmware version 1. flashing the iLO 2 firmware through the XML interface will take approximately 7 minutes to complete. REG_DDNS_SERVER VALUE is used to instruct iLO 2 to register the management port with a DDNS server. The possible values are "Yes" or "No. This selection is only valid if DHCP is enabled." SHARED_NETWORK_PORT_VLAN_ID VALUE is used to set the VLAN ID value. This selection is only valid if DHCP is enabled. and the Boolean string must be set to "Yes" if this behavior is desired." It is case sensitive.64 1. the current value is deleted.64 1.64 1. DHCP_ENABLE is used to enable DHCP. DHCP_STATIC_ROUTE specifies if the DHCP-assigned static routes are to be used. The possible values are "Yes" or "No. If an empty string is entered." The possible values are "Yes" or "No." It is case insensitive. If an empty string is entered. If an empty string is entered. The possible values are "Yes" or "No. This selection is only valid if DHCP is enabled." It is case sensitive. DHCP_GATEWAY specifies if the DHCP-assigned gateway address is to be used." It is case sensitive. The possible values are "Yes" or "No. the current value is deleted. DOMAIN_NAME is used to specify the domain name for the network where the iLO 2 resides. This parameter is optional." The possible values are "10" or "100.60 1. the current value is deleted." It is case insensitive." It is case insensitive. DNS_NAME is used to specify the DNS name for the iLO 2. If this parameter is used. The possible values are "Yes" or "No. DHCP_DNS_SERVER specifies if the DHCP-assigned DNS server is to be used. SHARED_NETWORK_PORT_VLAN VALUE is used to enable iLO 2 Shared Network Port VLAN ID tagging. If an empty string is entered.

the current value is deleted. MOD_NETWORK_SETTINGS runtime errors The possible MOD_NETWORK_SETTINGS error messages include: • • RIB information is open for read-only access. If an empty string is entered. If an empty string is entered. This parameter is only relevant if the DHCP-assigned static route feature is disabled. STATIC_ROUTE_1. PRIM_WINS_SERVER specifies the IP address of the primary WINS server. If an empty string is entered. the current value is deleted. If an empty string is entered. the current value is deleted. • WEB_AGENT_IP_ADDRESS specifies the address for the Web-enabled agents. This parameter is only relevant if the DHCP-assigned DNS server address feature is disabled. STATIC_ROUTE_2. This parameter is only relevant if the DHCP-assigned WINS server address feature is disabled. the current value is deleted. Example: <RIBCL VERSION="2. If an empty string is entered. the current value is deleted. This parameter is only relevant if the DHCP-assigned DNS server address feature is disabled. and STATIC_ROUTE_3 are used to specify the destination and gateway IP addresses of the static routes. This parameter is only relevant if the DHCP-assigned WINS server address feature is disabled. GATEWAY specifies the gateway IP addresses of the static route. and RIB_INFO MODE can be set to read or write. Write access is required for this operation. CONFIG_ILO_PRIV required. If an empty string is entered. SEC_DNS_SERVER specifies the IP address of the secondary DNS server. If an empty string is entered.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <RIB_INFO MODE="read"> <GET_GLOBAL_SETTINGS/> </RIB_INFO> </LOGIN> </RIBCL> Remote Insight command language 84 .REG_WINS_SERVER specifies if the iLO 2 must be register with the WINS server. The possible values are "Yes" or "No. If an empty string is entered. For this command to parse correctly. the current value is deleted. If an empty string is entered. TER_DNS_SERVER specifies the IP address of the tertiary DNS server. User does not have correct privilege for action. the command must appear within a RIB_INFO command block. PRIM_DNS_SERVER specifies the IP address of the primary DNS server. This parameter is only relevant if the DHCP-assigned DNS server address feature is disabled. This parameter is only relevant if the DHCP-assigned static route feature is disabled. • DEST specifies the destination IP addresses of the static route. The following two parameters are used within the static route commands. the current value is deleted. GET_GLOBAL_SETTINGS The GET_GLOBAL_SETTINGS command requests the respective iLO 2 global settings. the current value is deleted. the current value is deleted." It is case sensitive. SEC_WINS_SERVER specifies the IP address of the secondary WINS server. This selection is only valid if DHCP is enabled.

Example: <RIBCL VERSION="2. MOD_GLOBAL_SETTINGS MOD_GLOBAL_SETTINGS is used to modify global settings.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <RIB_INFO MODE="write"> <MOD_GLOBAL_SETTINGS> <SESSION_TIMEOUT value="60"/> <F8_PROMPT_ENABLED value="Yes"/> <HTTP_PORT value="80"/> Remote Insight command language 85 . and RIB_INFO MODE must be set to write. For this command to parse correctly. The user must have the configure iLO 2 privilege to execute this command. the command must appear within a RIB_INFO command block.GET_GLOBAL_SETTINGS parameters None GET_GLOBAL_SETTINGS runtime errors None GET_GLOBAL_SETTINGS return messages A possible GET_GLOBAL_SETTINGS return message is: <GET_GLOBAL_SETTINGS> <SESSION_TIMEOUT="120"> <ILO_FUNCT_ENABLED VALUE="Y"/> <F8_PROMPT_ENABLED="Y"/> <F8_LOGIN_REQUIRED="Y"/> <REMOTE_CONSOLE_PORT_STATUS VALUE="2"/> <REMOTE_CONSOLE_ENCRYPTION VALUE="Y"/> <REMOTE_CONSOLE_ACQUIRE VALUE="Y"/> <PASSTHROUGH_CONFIG VALUE=”3”/> <HTTPS_PORT VALUE="443"/> <HTTP_PORT VALUE="80"/> <REMOTE_CONSOLE_PORT VALUE="23"/> <TERMINAL_SERVICES_PORT VALUE="3389"/> <VIRTUAL_MEDIA_PORT VALUE="17988"/> <MIN_PASSWORD VALUE="8"/> <REMOTE_KEYBOARD_MODEL VALUE="US"/> <SSH_PORT value="22"/> <SSH_STATUS value="YES"/> <SERIAL_CLI_STATUS value="3"/> <SERIAL_CLI_SPEED value="1"/> </GET_GLOBAL_SETTINGS> This reply differs from RILOE II.

ILO_FUNCT_ENABLED determines if the Lights-Out functionality is enabled or disabled for iLO 2. The possible values are "Yes" or "No. then the parameter value for the specified setting is preserved. The remote console port will remain closed unless a remote console session is started. The possible values are: • • • • 0—No change 1—Disabled (The remote console port is disabled. 30. SESSION_TIMEOUT determines the maximum session timeout value in minutes." REMOTE_CONSOLE_PORT_STATUS determines the behavior of remote console service. F8_PROMPT_ENABLED determines if the F8 prompt for ROM-based configuration is displayed during POST. The possible values are "Yes" or "No.) 2—Automatic (This is the default setting. If a parameter is not specified. This will allow remote console and telnet sessions to be utilized." It is case insensitive.) 3—Enabled (The remote console port is always enabled.) Remote Insight command language 86 . This will prevent remote console and telnet sessions from being utilized. 60. The possible values are "Yes" or "No. The accepted values are 15.<HTTPS_PORT value="443"/> <REMOTE_CONSOLE_PORT value="23"/> <REMOTE_CONSOLE_PORT_STATUS value="2"/> <REMOTE_CONSOLE_ENCRYPTION value="Yes"/> <MIN_PASSWORD value="8"/> <ILO_FUNCT_ENABLED value="Yes"/> <VIRTUAL_MEDIA_PORT value="17988"/> <F8_LOGIN_REQUIRED value="No"/> <REMOTE_KEYBOARD_MODEL value="US"/> <PASSTHROUGH_CONFIG value="1"/> <TERMINAL_SERVICES_PORT value="3389"/> <SSH_PORT value="22"/> <SSH_STATUS value="Yes"/> <SERIAL_CLI_STATUS value="3"/> <SERIAL_CLI_SPEED value="1"/> <RBSU_POST_IP value="Y"/> <TELNET_ENABLE value="yes"/> <HIGH_PERFORMANCE_MOUSE value="Yes" /> <REMOTE_CONSOLE_ACQUIRE value="Yes" /> </MOD_GLOBAL_SETTINGS> </RIB_INFO> </LOGIN> </RIBCL> MOD_GLOBAL_SETTINGS parameters All of the following parameters are optional." F8_LOGIN_REQUIRED determines if login credentials are required to access the RBSU for iLO 2. and 120.

REMOTE_KEYBOARD_MODEL determines the remote keyboard language translation used during remote console operation. VIRTUAL_MEDIA_PORT specifies the port used for virtual media. The possible values are: • • • • 0—No change 1—Disabled 2—Enabled (no authentication required) 3—Enabled (authentication required) 0—No change 1—9. SERIAL_CLI_STATUS specifies the status of the CLI." PASSTHROUGH_CONFIG determines the behavior of a Microsoft® Terminal Services client. The possible values are: US Danish French Canadian Japanese Spanish Swiss German Belgian Finnish German Latin American Swedish British French Italian Portuguese Swiss French SSH_PORT specifies the port used for SSH connection on iLO 2. REMOTE_CONSOLE_PORT specifies the port used for remote console. The valid values are Yes or No. TERMINAL_SERVICES_PORT specifies the port used for terminal services. The terminal services feature is enabled but will not automatically be launched when remote console is started. MIN_PASSWORD command specifies how many characters are required in all user passwords.600 bps 2—19.) 2—Automatic (The Terminal Services client will be launched when remote console is started. NOTE: If port changes are detected. The processor must be reset if this value is changed. The possible values are "Yes" and "No.) HTTPS_PORT specifies the HTTPS (SSL) port number. HTTP_PORT specifies the HTTP port number. The possible values are: • • • • 0—No change 1—Disabled (The Terminal Services feature is disabled.REMOTE_CONSOLE_ENCRYPTION determines if remote console data encryption is enabled or disabled. SSH_STATUS determines if SSH is enabled." REMOTE_CONSOLE_ACQUIRE determines if the remote console acquire operation will be enabled or disabled. which enables or disables SSH functionality. the iLO 2 management processor will be rebooted to apply the changes after the script has completed successfully.) 3—Enabled (This is the default setting. The possible values are: • • • Remote Insight command language 87 .200 bps SERIAL_CLI_SPEED specifies the CLI port speed. The possible values are "Yes" and "No. The value can be from zero to 39 characters.

168.600 bps 5—115. User does not have correct privilege for action.168.122”/> <SNMP_ADDRESS_3 VALUE=“192.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <RIB_INFO MODE="read"> <GET_SNMP_IM_SETTINGS/> </RIB_INFO> </LOGIN> </RIBCL> GET_SNMP_IM_SETTINGS parameters None GET_SNMP_IM_SETTINGS runtime errors None GET_SNMP_IM_SETTINGS return messages A possible GET_SNMP_IM_SETTINGS return message is: <GET_SNMP_IM_SETTINGS> <SNMP_ADDRESS_1 VALUE=“192. GET_SNMP_IM_SETTINGS The GET_SNMP_IM_SETTINGS command requests the respective iLO 2 SNMP IM settings. CONFIG_ILO_PRIV required.121”/> <SNMP_ADDRESS_2 VALUE=“192. Write access is required for this operation.168.400 bps 4—57.• • • 3—38. and RIB_INFO MODE can be set to read or write. the GET_SNMP_IM_SETTINGS command must appear within a RIB_INFO command block. Unrecognized keyboard model.123”/> <OS_TRAPS VALUE=“Yes”/> <RIB_TRAPS VALUE=“No”/> <SNMP_PASSTHROUGH_STATUS VALUE=“No”/> <WEB_AGENT_IP_ADDRESS VALUE=“192.200 bps MOD_GLOBAL_SETTINGS runtime errors The possible MOD_GLOBAL_SETTINGS error messages include: • • • RIB information is open for read-only access.125.120”/> <CIM_SECURITY_MASK VALUE=“3”/> </GET_SNMP_IM_SETTINGS> Remote Insight command language 88 .125. Example: <RIBCL VERSION="2.168.125.125. For this command to parse correctly.

MOD_SNMP_IM_SETTINGS
MOD_SNMP_IM_SETTINGS is used to modify SNMP and Insight Manager settings. For this command to parse correctly, the command must appear within a RIB_INFO command block, and RIB_INFO MODE must be set to write. The user must have the configure iLO 2 privilege to execute this command. Example: <RIBCL VERSION=“2.0”> <LOGIN USER_LOGIN=“adminname” PASSWORD=“password”> <RIB_INFO MODE=“write”> <MOD_SNMP_IM_SETTINGS> <WEB_AGENT_IP_ADDRESS value=“192.168.125.120”/> <SNMP_ADDRESS_1 value=“192.168.125.121”/> <SNMP_ADDRESS_2 value=“192.168.125.122”/> <SNMP_ADDRESS_3 value=“192.168.125.123”/> <OS_TRAPS value=“Yes”/> <RIB_TRAPS value=“No”/> <SNMP_PASSTHROUGH_STATUS value=“No”/> <CIM_SECURITY_MASK value=“3”/> </MOD_SNMP_IM_SETTINGS> </RIB_INFO> </LOGIN> </RIBCL>

MOD_SNMP_IM_SETTINGS parameters
All of the following parameters are optional. If a parameter is not specified, then the parameter value for the specified setting is preserved. WEB_AGENT_IP_ADDRESS is the address for the Web-enabled agents. The value for this element has a maximum length of 50 characters. It can be any valid IP address. If an empty string is entered, the current value is deleted. SNMP_ADDRESS_1, SNMP_ADDRESS_2, and SNMP_ADDRESS_3 are the addresses that receive traps sent to the user. Each of these parameters can be any valid IP address and has a maximum value of 50 characters. OS_TRAPS determines if the user should receive SNMP traps that are generated by the operating system. The possible values are "Yes" and "No." By default, the value is set to "No." RIB_TRAPS determines if the user should receive SNMP traps that are generated by the RIB. The possible values are "Yes" and "No." By default, the value is set to "No." SNMP_PASSTHROUGH_STATUS determines if iLO can receive/ send SNMP request from/ to the host OS. By default, the value is set to "Yes." CIM_SECURITY_MASK accepts an integer between 0 and 4. The possible values are:
• • • •

0—No change 1—None (No data is returned.) 2—Low (Name and status data are returned. Associations are present if SNMP pass-through is supported. If not, the server and management processor are separate entities in the device list.) 3—Medium (iLO 2 and server associations are present but the summary page contains less detail than at high security.)

Remote Insight command language 89

4—High (Associations are present and all data is present on the summary page.)

Each value indicates the level of data returned over the HTTP port.

MOD_SNMP_IM_SETTINGS runtime errors
The possible MOD_SNMP_IM_SETTINGS error messages include:
• •

RIB information is open for read-only access. Write access is required for this operation. User does not have correct privilege for action. CONFIG_ILO_PRIV required.

UPDATE_RIB_FIRMWARE
The UPDATE_RIB_FIRMWARE command copies a specified file to iLO 2, starts the upgrade process and reboots the board after the image has been successfully flashed. For this command to parse correctly, the command must appear within a RIB_INFO command block, and RIB_INFO MODE must be set to write. The user must have the configure iLO 2 privilege to execute this command. Example: <RIBCL VERSION="2.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <RIB_INFO MODE="write"> <UPDATE_RIB_FIRMWARE IMAGE_LOCATION="C:\firmware.bin"/> </RIB_INFO> </LOGIN> </RIBCL>

UPDATE_RIB_FIRMWARE parameters
IMAGE_LOCATION takes the full path file name of the firmware upgrade file.

UPDATE_RIB_FIRMWARE runtime errors
The possible UPDATE_RIB_FIRMWARE error messages include:
• • • • • • • • •

RIB information is open for read-only access. Write access is required for this operation. Unable to open the firmware image update file. Unable to read the firmware image update file. The firmware upgrade file size is too big. The firmware image file is not valid. A valid firmware image has not been loaded. The flash process could not be started. IMAGE_LOCATION must not be blank. User does not have correct privilege for action. CONFIG_ILO_PRIV required.

GET_FW_VERSION
The GET_FW_VERSION command requests the respective iLO 2 firmware information. For this command to parse correctly, the command must appear within a RIB_INFO command block, and RIB_INFO MODE must be set to write. The user must have the configure iLO 2 privilege to execute this command. Example: <RIBCL VERSION="2.0">

Remote Insight command language 90

<LOGIN USER_LOGIN="adminname" PASSWORD="password"> <RIB_INFO MODE="read"> <GET_FW_VERSION/> </RIB_INFO> </LOGIN> </RIBCL>

GET_FW_VERSION parameters
None

GET_FW_VERSION runtime errors
None

GET_FW_VERSION return messages
The following information is returned within the response: <GET_FW_VERSION FIRMWARE_VERSION = <firmware version> FIRMWARE_DATE = <firmware date> /> MANAGEMENT_PROCESSOR = <management processor type>

HOTKEY_CONFIG
The HOTKEY_CONFIG command configures the remote console hot key settings in iLO 2. For this command to parse correctly, the command must appear within a RIB_INFO command block, and RIB_INFO MODE must be set to write. The user must have the configure iLO 2 privilege to execute this command. Uppercase letters are not supported, and they will be converted automatically to lowercase. If either a double quote or a single quote is used, it must be different from the delimiter. Specifying a blank string removes the current value. Refer to the "Supported Hot Keys" section for a complete list of supported hotkeys. Example: <RIBCL VERSION="2.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <RIB_INFO MODE="write"> <HOTKEY_CONFIG> <CTRL_T value="CTRL,ALT,ESC"/> <CTRL_U value="L_SHIFT,F10,F12"/> <CTRL_V value=""/> <CTRL_Y value=""/> <CTRL_X value=""/> <CTRL_Y value=""/> </HOTKEY_CONFIG> </RIB_INFO> </LOGIN>

Remote Insight command language 91

ALT. Example: <RIBCL VERSION="2.ESC." Up to five keystrokes can be configured for each hot key. CTRL_U specifies settings for the CTRL_U hot key. CTRL_U="CTRL. Write access is required for this operation. For example. CTRL_V="CTRL. Advanced features are automatically activated. The hot key parameter specified is not valid. then the parameter value for the specified setting is preserved. For example. For example. The settings must be separated by commas." Up to five keystrokes can be configured for each hot key. CTRL_T="CTRL. The settings must be separated by commas. CTRL_Y specifies settings for the CTRL_Y hot key. For this command to parse correctly.ESC. The settings must be separated by commas. CTRL_V specifies settings for the CTRL_V hot key." Up to five keystrokes can be configured for each hot key. and RIB_INFO MODE must be set to write. On a ProLiant BL Class server.ALT. CTRL_X specifies settings for the CTRL_X hot key. HOTKEY_CONFIG runtime errors The possible HOTKEY_CONFIG error messages include: • • • • RIB information is open for read-only access.ALT. there is no need for a licensing key. For example. The user must have the configure iLO 2 privilege to execute this command. The maximum allowed is five. For example. If a parameter is not specified. Remote Insight command language 92 .ALT. The settings must be separated by commas." Up to five keystrokes can be configured for each hot key. CONFIG_ILO_PRIV required." Up to five keystrokes can be configured for each hot key. CTRL_W="CTRL.ALT. For example. CTRL_X="CTRL.ESC. The settings must be separated by commas. the command must appear within a RIB_INFO command block. LICENSE The LICENSE command activates or deactivates the iLO's advanced features. User does not have correct privilege for action. CTRL_T specifies settings for the CTRL_T hot key. Invalid number of hot keys.</RIBCL> HOTKEY_CONFIG parameters All of the following parameters are optional.ALT.ESC.ESC. CTRL_W specifies settings for the CTRL_W hot key. CTRL_Y="CTRL. The settings must be separated by commas." Up to five keystrokes can be configured for each hot key.ESC.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <RIB_INFO MODE="write"> <LICENSE> <ACTIVATE KEY="1111122222333334444455555"/> </LICENSE> </RIB_INFO> </LOGIN> </RIBCL> LICENSE parameters ACTIVATE followed by a valid KEY value signals the activation of the iLO 2 advanced pack licensing.

The INSERT_VIRTUAL_MEDIA command must display within a RIB_INFO element./cgibin/hpvfhelp.bin. The cgi-helper field is optional. periods. CONFIG_ILO_PRIV required. The possible values are FLOPPY or CDROM. The URL format is as follows: protocol://username:password@hostname:port/filename.bin Remote Insight command language 93 . and RIB_INFO must be in write mode. Example: <RIBCL VERSION="2. The key should be entered as one continuous string. The key will only accept 25 characters.company.cgi-helper • • • • • • The protocol field is mandatory and must be either http or https.company. The hostname field is mandatory. the filename field may contain tokens that expand to host specific strings: • • • Examples: http://john:abc123@imgserver. If the DEVICE is not specified. INSERT_VIRTUAL_MEDIA This command notifies iLO 2 of the location of a diskette image.KEY specifies the license key value. User does not have correct privilege for action. In addition. DEACTIVATE signals the deactivation of the iLO 2 advanced pack licensing. This value is case-sensitive. IMAGE_URL specifies the URL to the diskette image.pl http://imgserver. %m expands to the iLO 2 MAC address. The port field is optional The filename field is mandatory. or other characters should not separate the key value. LICENSE runtime errors The possible LICENSE error messages include: • • • License key error. other characters entered to separate key values will be interpreted as a part of the key and result in the wrong key being entered.com/disk/boot%m.com/disk/win98dos.0"> <LOGIN USER_LOGIN = "adminname" PASSWORD = "password"> <RIB_INFO MODE = "write"> <INSERT_VIRTUAL_MEDIA DEVICE="FLOPPY" IMAGE_URL= "http://servername/path/to/file"/> </RIB_INFO> </LOGIN> </RIBCL> INSERT_VIRTUAL_MEDIA Parameters DEVICE specifies the Virtual Media device target. %i expands to the iLO 2 IP address in dotted-quad form. Commas. License is already active. The username:password field is optional. FLOPPY is assumed. %h expands to the iLO 2 hostname.

Unable to parse Virtual Media URL An invalid Virtual Media option has been given. EJECT_VIRTUAL_MEDIA runtime errors The possible EJECT_VIRTUAL_MEDIA errors are: • • • • RIB information is open for read-only access. EJECT_VIRTUAL_MEDIA EJECT_VIRTUAL_MEDIA ejects the Virtual Media image if one is inserted. VIRTUAL_MEDIA_PRIV required. If the DEVICE is not specified. After an image is inserted using this command. An invalid Virtual Media option has been given. GET_VM_STATUS GET_VM_STATUS returns the Virtual Media drive status. User does not have correct privilege for action. the appropriate BOOT_OPTION must be specified using the SET_VM_STATUS command. You must eject or disconnect before inserting new media. This command must display within a RIB_INFO element. IMAGE_URL must not be blank. FLOPPY is assumed. Virtual Media already connected through a script. VIRTUAL_MEDIA_PRIV required. the Virtual Media applet cannot connect its Virtual Media devices and subsequent scripts cannot use the INSERT_VIRTUAL_FLOPPY command until the image is ejected. User does not have correct privilege for action. This value is case-sensitive. Write access is required for this operation. For the image to be connected to the server. No image present in the Virtual Media drive. Remote Insight command language 94 .This command only specifies the location of the image to be used. Example: <RIBCL VERSION="2. The possible values are FLOPPY or CDROM. If BOOT_OPTION is set to BOOT_ONCE and the server is rebooted. Write access is required for this operation.0"> <LOGIN USER_LOGIN="Admin" PASSWORD="Password"> <RIB_INFO MODE="write"> <EJECT_VIRTUAL_MEDIA DEVICE="FLOPPY"/> </RIB_INFO> </LOGIN> </RIBCL> EJECT_VIRTUAL_MEDIA parameters DEVICE specifies the Virtual Media device target. any subsequent server reboots eject the image. INSERT_VIRTUAL_FLOPPY runtime errors The possible INSERT_VIRTUAL_FLOPPY error messages include: • • • • • • RIB information is open for read-only access. The EJECT_VIRTUAL_MEDIA command must display within a RIB_INFO element and RIB_INFO must be in write mode.

If the DEVICE is not specified. and NO_BOOT means that the Virtual Media will not be connected during a server reboot. This command must display within a RIB_INFO element. Specifically BOOT_OPTION = NO_BOOT.Example: <RIBCL VERSION="2. BOOT_ALWAYS means that the server will always use the Virtual Media device for booting. WRITE_PROTECT = NO. and RIB_INFO must be in write mode.0"> <LOGIN USER_LOGIN = "adminname" PASSWORD = "password"> <RIB_INFO MODE = "read"> <GET_VM_STATUS DEVICE="CDROM"/> </RIB_INFO> </LOGIN> </RIBCL> GET_VM_STATUS parameters DEVICE specifies the Virtual Media device target. all scriptable virtual media parameters are reset to default settings after the server boots. This value is case-sensitive. The BOOT_OPTION shows the current setting. BOOT_ONCE means that the server will boot to the Virtual Device once and then disconnect the Virtual Media on the subsequent server reboot. GET_VM_STATUS return messages The return message displays the current state of the Virtual Media. and IMAGE_INSERTED = NO. then the Virtual Media is already in use and cannot be connected via scriptable Virtual Media or Virtual Media XML commands.0"> <LOGIN USER_LOGIN = "adminname" PASSWORD = "password"> <RIB_INFO MODE = "write"> <SET_VM_STATUS DEVICE = "CDROM"> <VM_BOOT_OPTION value = "BOOT_ONCE"/> <VM_WRITE_PROTECT value = "Y"/> Remote Insight command language 95 . If the VM_APPLET = CONNECTED. The possible values are FLOPPY or CDROM. GET_VM_STATUS runtime errors The possible GET_VM_STATUS error is: An invalid Virtual Media option has been given. All the parameters in the command are optional. FLOPPY is assumed. SET_VM_STATUS SET_VM_STATUS sets the Virtual Media drive status. The VM_APPLET parameter shows if a virtual media device is already connected via the Virtual Media Applet. The DEVICE parameter tells which device this return message is for. Example: <RIBCL VERSION="2. The IMAGE_INSERTED parameter tells if the Virtual Media device is connected via the scriptable Virtual Media or the Virtual Media XML command. The WRITE_PROTECT_FLAG parameter shows if the Virtual Media image can be written to. A possible GET_VM_STATUS return message is: VM_APPLET = CONNECTED | DISCONNECTED DEVICE = FLOPPY | CDROM BOOT_OPTION = BOOT_ALWAYS | BOOT_ONCE | NO_BOOT WRITE_PROTECT_FLAG = YES | NO IMAGE_INSERTED = YES | NO NOTE: If the BOOT_ONCE boot option is selected.

These settings only take affect if the Virtual Media device is connected at server boot. respectively. CONNECT and DISCONNECT are also possible values. Setting the VM_BOOT_OPTION to CONNECT is equivalent to clicking the device Connect button on the Virtual Media Applet. FLOPPY is assumed. Setting the VM_BOOT_OPTION to DISCONNECT is equivalent to clicking the device Disconnect button on the Virtual Media Applet. the VM_GET_STATUS command will show the VM_BOOT_OPTION as BOOT_ALWAYS. The Virtual Media device is not connected immediately when the VM_BOOT_OPTION is set. The Virtual Media device will be disconnected on the next server boot following the setting of the VM_BOOT_OPTION. The Virtual Media device is not connected during the next server boot. but on any subsequent server boots. The BOOT_ONCE option is intended to boot one time to the Virtual Media device. use that device while the server is running. Whenever the CONNECT or DISCONNECT parameters are set. The Virtual Media device is connected on the next server boot following the setting of the VM_BOOT_OPTION. The Virtual Media device is connected on the next server boot after setting of the VM_BOOT_OPTION. Additionally. These values control how the Virtual Media device behaves during the boot phase of the server. The possible values are BOOT_ALWAYS. BOOT_ONCE. The Virtual Media device is immediately connected to the server. the Virtual Media device immediately connects or disconnects. or NO_BOOT. The Virtual Media device is connected during the next server boot. to the server. DISCONNECT sets the VM_BOOT_OPTION to DISCONNECT.</ SET_VF_STATUS> </RIB_INFO> </LOGIN> </RIBCL> SET_VM_STATUS parameters DEVICE specifies the Virtual Media device target. it will not be connected. After setting the VM_BOOT_OPTION to CONNECT. BOOT_ONCE sets the VM_BOOT_OPTION to BOOT_ONCE. on the subsequent server reboot. • Remote Insight command language 96 . The Virtual Media device is immediately disconnected from the server. the Virtual Media device will not be connected and the following Virtual Media device settings will be reset to their default values: • • BOOT_OPTION = NO_BOOT IMAGE_INSERTED = NO In addition to the VM_BOOT_OPTIONS. • CONNECT sets the VM_BOOT_OPTION to CONNECT. This is by design and shows that the Virtual Media device is connected like the Virtual Media device in the applet which with always be connected during all server boots. The Virtual Media device is not disconnected immediately when the VM_BOOT_OPTION is set. The Virtual Media device is not connected immediately when the VM_BOOT_OPTION is set. Setting these values does not affect the current state of the Virtual Media device. The Virtual Media device will always be connected during server boot. This value is case-sensitive. The possible values are FLOPPY or CDROM. If the DEVICE is not specified. VM_BOOT_OPTION specifies the boot option parameter for the Virtual Media. After the server has booted once with the Virtual Media device connected. and then not have the Virtual Media device available on subsequent server reboots. After the server has booted. the Virtual Media device will not be connected and the following Virtual Media device settings will be reset to their default values: • • • BOOT_OPTION=NO_BOOT IMAGE_INSERTED = NO • NO_BOOT sets the VM_BOOT_OPTION to NO_BOOT. • BOOT_ALWAYS sets the VM_BOOT_OPTION to BOOT_ALWAYS. The CONNECT and DISCONNECT settings can be used to control the Virtual Media devices in the same way that they are controlled in the Virtual Media applet.

This value is not significant for the Virtual Media CD-ROM. CERTIFICATE_SIGNING_REQUEST errors There are no errors for this command. Write access is required for this operation. An invalid Virtual Media option has been given.setting the VM_BOOT_OPTION to DISCONNECT is equivalent to issuing the EJECT_VIRTUAL_MEDIA command. Example: <RIBCL VERSION="1. When the VM_BOOT_OPTION is set to DISCONNECT. This command requires CPQLOCFG version 2.23 or later. Remote Insight command language 97 . the Virtual Media device will not be connected and the following Virtual Media device settings will be reset to their default values: • • BOOT_OPTION = NO_BOOT IMAGE_INSERTED = NO VM_WRITE_PROTECT sets the write protect flag value for the Virtual Floppy. The signed certificate must be a signed version of a certificate signing request. SET_VM_STATUS runtime errors The possible runtime errors are: • • • RIB information is open for read-only access.23 or later. When this command is received iLO 2 generates a certificate signing request. User does not have correct privilege for action.2"> <LOGIN USER_LOGIN = "adminname" PASSWORD = "password"> <RIB_INFO MODE = "write"> <IMPORT_CERTIFICATE> -----BEGIN CERTIFICATE----…. This command requires CPQLOCFG version 2. The request is returned to the user enclosed in a CERTIFICATE_SIGNING_REQUEST tag. VIRTUAL_MEDIA_PRIV required. IMPORT_CERTIFICATE The IMPORT_CERTIFICATE command imports a signed certificate into iLO 2. CERTIFICATE_SIGNING_REQUEST This command requests a certificate from iLO 2. Example: <RIBCL VERSION="1.2"> <LOGIN USER_LOGIN = "adminname" PASSWORD = "password"> <RIB_INFO MODE = "write"> <CERTIFICATE_SIGNING_REQUEST/> </RIB_INFO> </LOGIN> </RIBCL> CERTIFICATE_SIGNING_REQUEST parameters There are no parameters for this command. The possible values are Y or N.

the response to GET_TWOFACTOR_SETTINGS will contain different data. GET_TWOFACTOR_SETTINGS The GET_TWOFACTOR_SETTINGS command requests the respective iLO 2 Two-Factor Authentication settings.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <RIB_INFO MODE="read"> <GET_TWOFACTOR_SETTINGS/> </RIB_INFO> </LOGIN> </RIBCL> GET_TWOFACTOR_SETTINGS parameters None GET_TWOFACTOR_SETTINGS runtime errors None GET_TWOFACTOR_SETTINGS return messages Starting with iLO 2 1. Certificate signature does not match private key: The certificate does not correspond to the private key stored in iLO 2. the GET_TWOFACTOR_SETTINGS command must appear within a RIB_INFO command block. Write access is required for this operation. Example: <RIBCL VERSION="2. For this command to parse correctly. Error reading certificate: The imported certificate is invalid. users can be authenticated with a digital certificate.-----END CERTIFICATE----</IMPORT_CERTIFICATE> </RIB_INFO> </LOGIN> </RIBCL> IMPORT_CERTIFICATE parameters There are no parameters for this command.20. Depending on the iLO 2 Two-Factor Authentication settings. Invalid certificate common name: The common name in the certificate does not match iLO 2's hostname. and RIB_INFO MODE can be set to read or write. IMPORT_CERTIFICATE errors The possible IMPORT_CERTIFICATE error messages include: • • • • RIB information is open for read-only access. Examples of GET_TWOFACTOR_SETTINGS return messages are: Example of a Two-Factor Authentication settings return message with default settings: <GET_TWOFACTOR_SETTINGS> <AUTH_TWOFACTOR_ENABLE VALUE="N"/> Remote Insight command language 98 .

24.80 requires CPQLOCFG version 2.25. However. and iLO 1. only a single factor is required to access the iLO 2 with telnet. client certificate mapping to local user accounts is optional. A Trusted CA Certificate is required for Two-Factor Authentication to function.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <RIB_INFO MODE="write"> <MOD_TWOFACTOR_SETTINGS> <AUTH_TWOFACTOR_ENABLE value="Yes"/> <CERT_REVOCATION_CHECK value="No"/> <CERT_OWNER_SAN/> </MOD_TWOFACTOR_SETTINGS> </RIB_INFO> </LOGIN> Remote Insight command language 99 . However.10 requires CPQLOCFG version 2. You must have the configure RILOE II privilege to execute this command. To provide the necessary security. SSH or Serial CLI access is required. • Example of enabling Two-Factor Authentication: <RIBCL VERSION="2. iLO 1. or serial CLI. For this command to parse correctly. the following configuration changes are made when Two-Factor Authentication is enabled: • • • Remote Console Data Encryption: Yes (this will disable telnet access) Enable Secure Shell (SSH) Access: No Serial Command Line Interface Status: Disabled If telnet. NOTE: The GET_TWOFACTOR_SETTINGS and MOD_TWOFACTOR_SETTINGS commands are supported with iLO firmware version 1.10 and above. re-enable these settings after Two-Factor Authentication is enabled.80 and above and with iLO 2 firmware version 1. because these access methods do not provide a means of Two-Factor Authentication. The iLO 2 will not allow the AUTH_TWOFACTOR_ENABLE setting to be set to Yes if a Trusted CA certificate has not been configured. access with the CPQLOCFG utility is disabled because CPQLOCFG does not supply all authentication requirements. When Two-Factor Authentication is enabled. Also.<CERT_REVOCATION_CHECK VALUE="N"/> <CERT_OWNER_SUBJECT/> </GET_TWOFACTOR_SETTINGS> Example of a Two-Factor Authentication settings return message when SAN field in the certificate for directory authentication is enabled: <GET_TWOFACTOR_SETTINGS> <AUTH_TWOFACTOR_ENABLE VALUE="Y"/> <CERT_REVOCATION_CHECK VALUE="N"/> <CERT_OWNER_SAN/> </GET_TWOFACTOR_SETTINGS> MOD_TWOFACTOR_SETTINGS The MOD_TWOFACTOR_SETTINGS command is used to modify the Two-Factor Authentication settings on the iLO 2. the MOD_TWOFACTOR_SETTINGS command must appear within a RIB_INFO command block. Changing the value of AUTH_TWOFACTOR_ENABLE will cause the iLO 2 to reset for the new setting to take effect. If the iLO 2 is using directory authentication. and RIB_INFO MODE must be set to write. a client certificate must be mapped to a local user account if local user accounts are being used. since administrator privileges on the host system are required to execute this utility. SSH. the HPONCFG utility is functional.

DC=com. and use that for authentication with the directory. 9gVCPSOQUGMMZUeNYOBkTE0e+MrPGL+TqQEyIakF3rjA2PbL1uSY6d4dlCx7izkO buEpHTPDqs9gZ3U5ht9bjES93UHnDENLopkZ2JgGwH8Y50eBnjq4xml9psbYZn5Y yWpONE/IjIjJyww= -----END CERTIFICATE----</IMPORT_CA_CERTIFICATE> <IMPORT_USER_CERTIFICATE USER_LOGIN="apollo"> -----BEGIN CERTIFICATE----CZImiZPyLGQBGRYDTEFCMRUwEwYKCZImiZPyLGQBGRYFSkpSSUIxHjAcBgNVBAMT ODU5NDRaMFYxEzARBgoJkiaJk . If a parameter is not specified. if the subject name is "/DC=com/DC=domain/OU=organization/CN=user.0"> <LOGIN USER_LOGIN="test" PASSWORD="password"> <RIB_INFO MODE="write"> <MOD_TWOFACTOR_SETTINGS> <CERT_OWNER_SAN/> <IMPORT_CA_CERTIFICATE> -----BEGIN CERTIFICATE----MIIEtzCCA5+gAwIBAgIQBGg9C0d7B5pF/l4bVA44hjANBgkqhkiG9w0BAQUFADBM MRMwEQYKCZImiZPyLGQBGRYDTEFCMRUwEwYKCZImiZPyLGQBGRYFSkpSSUIxHjAc ." CERT_REVOCATION_CHECK causes iLO 2 to use the CRL distribution point attribute of the client certificate to download the CRL and check against revocation.. CERT_OWNER_SAN causes iLO 2 to extract the User Principle Name from the Subject Alternative Name.extension. For example. The possible values are "Yes" and "No." If this setting is set to Yes. CERT_OWNER_SUBJECT causes iLO 2 to derive the user's distinguished name from the subject name.. for example: username@domain. authentication will be denied. Remote Insight command language 100 ." iLO 2 will derive: "CN=user. and the CRL cannot be downloaded for any reason. AUTH_TWOFACTOR_ENABLE enables or disables Two-Factor authentication." The CERT_OWNER_SAN and CERT_OWNER_SUBJECT settings are only used if directory authentication is enabled. The possible values are "Yes" and "No.OU=organization.</RIBCL> • Importing a CA and a user certificate example: <RIBCL VERSION="2. then the parameter value for the specified setting is preserved.DC=domain.. sjbbpNGpxGsK9GZi5j6UeOYklePyau0TJ3KIm2RPlR2C6XAGz2PTWgsxGlUP9lNH bfz0+TD0JsschjqK23/vr2GxQ9C/835zRxdu5Dn8JGm3/dFHR2VxgCetIxyR9TQC ZKTfvIa8N9KvMLZdclSj94jUyMZjYYmCWULW8WySMV70nclvrsI2hi3nwMtt2Zvj WnbeZujBX9LGz3HdmghgUw4GTwYl3ZG88snuTyXliLPFXVYXvNAhGeWqXtrh7A90 3NprjG7DM1uw -----END CERTIFICATE----</IMPORT_USER_CERTIFICATE> </MOD_TWOFACTOR_SETTINGS> </RIB_INFO> </LOGIN> </RIBCL> MOD_TWOFACTOR_SETTINGS parameters All of the following parameters are optional..

User does not have correct privilege for action.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <DIR_INFO MODE="read"> Remote Insight command language 101 . Example: <DIR_INFO MODE="read"> ……… DIR_INFO commands …… </DIR_INFO> GET_DIR_CONFIG The GET_DIR_CONFIG command requests the respective iLO 2 directory settings. it reads the local directory information database into memory and prepares to edit it. For this command to parse correctly. which will not function if Two-factor authentication is enabled • • This setting cannot be enabled unless a trusted CA certificate has been imported. A Trusted CA certificate must be configured in iLO 2 for Two-Factor authentication to function. This setting cannot be changed while Shared Network port is enabled. iLO 2 will only allow client certificates that are issued by this CA. A CA certificate must be imported before enabling Two-factor authentication. The DIR_INFO command generates a response that indicates to the host application whether the database was successfully read or not. Write mode enables both reading and writing of iLO 2 information. When the command is parsed. then this call will fail. IMPORT_USER_CERTIFICATE imports the certificate into iLO 2 and maps it to the specified local user. The IMPORT_CA_CERTIFICATE and IMPORT_USER_CERTIFICATE settings require that base64-encoded certificate data be included between the BEGIN and END tags. CONFIG_ILO_PRIV required. iLO 2 has been configured to use shared network port. Write access is required for this operation. Example: <RIBCL VERSION="2. Only commands that are DIR_INFO type commands are valid inside the DIR_INFO command block. Any client that authenticates with this certificate will authenticate as the local user to which it is mapped. the GET_DIR_CONFIG command must appear within a DIR_INFO command block.IMPORT_CA_CERTIFICATE imports the certificate into iLO 2 as the trusted Certificate Authority. client certificate mapping to local user accounts is optional and only necessary if authentication with local accounts is desired. If iLO 2 is using directory authentication. DIR_INFO requires the MODE parameter with a value of read or write. DIR_INFO The DIR_INFO command can only appear within a LOGIN command block. MODE is a specific string parameter with a maximum length of 10 characters that specifies what you intend to do with the information. The SHA1 hash of this certificate will be displayed on the Modify User website for the user to whom it is mapped. MOD_TWOFACTOR_SETTINGS runtime errors The possible MOD_TWOFACTOR_SETTINGS error messages include: • • RIB information is open for read-only access. Read mode prevents modification of the iLO 2 information. and DIR_INFO MODE can be set to read or write. If the database is open for writing by another application.

4.demo.DC=demo.2.DC=demo. Possible GET_DIR_CONFIG return messages are: • Example of a directory services (with schema extension) return message: <GET_DIR_CONFIG> <DIR_AUTHENTICATION_ENABLED VALUE="Y"/> <DIR_LOCAL_USER_ACCT VALUE="Y"/> <DIR_SERVER_ADDRESS VALUE="adserv.80. Depending on your directory configuration.demo. DC=LABS"/> <DIR_USER_CONTEXT1 VALUE="CN=Users0.DC=HPRIB1.com"/> <DIR_SERVER_PORT VALUE="636"/> <DIR_OBJECT_DN VALUE=""/> <DIR_USER_CONTEXT1 VALUE="CN=Users.OU=RIB.DC=com"/> <DIR_USER_CONTEXT2 VALUE=""/> <DIR_USER_CONTEXT3 VALUE=""/> <DIR_ENABLE_GRP_ACCT VALUE="Y"/> <DIR_GRPACCT1_NAME VALUE="CN=iLOAdmins.com"/> <DIR_SERVER_PORT VALUE="636"/> <DIR_OBJECT_DN VALUE="CN=SERVER1_RIB.DC=HPRIB0. DC=LABS"/> <DIR_USER_CONTEXT2 VALUE="CN=Users1. directory integration can work with HP Lights-Out schema with or without extensions (schema-free).<GET_DIR_CONFIG/> </DIR_INFO> </LOGIN> </RIBCL> GET_DIR_CONFIG parameters None GET_DIR_CONFIG runtime errors None GET_DIR_CONFIG return messages Starting with iLO 2 1.DC=com"/> <DIR_GRPACCT1_PRIV VALUE="1.DC=HPRIB.CN=Users. the response to GET_DIR_CONFIG contains different data.5"/> <DIR_GRPACCT2_NAME VALUE="" /> <DIR_GRPACCT2_PRIV VALUE="" /> <DIR_GRPACCT3_NAME VALUE="" /> Remote Insight command language 102 . DC=LABS"/> <DIR_USER_CONTEXT3 VALUE=""/> <DIR_ENABLE_GRP_ACCT VALUE="N"/> </GET_DIR_CONFIG> • Example of a schema-free directory (without schema extension) return message: <GET_DIR_CONFIG> <DIR_AUTHENTICATION_ENABLED VALUE="Y"/> <DIR_LOCAL_USER_ACCT VALUE="Y"/> <DIR_SERVER_ADDRESS VALUE="adserv.3.

xml example: <RIBCL VERSION="2.Set the value to "NO" to enable the HP Extended Schema --> <!-. --> <!-.run Mod_Schemaless_Directory. For this command to parse correctly. --> <DIR_ENABLE_GRP_ACCT value = "yes"/> </MOD_DIR_CONFIG> </DIR_INFO> </LOGIN> </RIBCL> NOTE: When using directory integration with schema extension.xml example: <RIBCL VERSION="2. DC=HPRIB. OU=RIB.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <DIR_INFO MODE="write"> <MOD_DIR_CONFIG> <DIR_AUTHENTICATION_ENABLED value="Yes"/> <DIR_LOCAL_USER_ACCT value="Yes"/> <DIR_SERVER_ADDRESS value="16. Examples: • Mod_Directory. the following tags must not be used: • DIR_ENABLE_GRP_ACCT • DIR_GRPACCT1_NAME • DIR_GRPACCT1_PRIV • Mod_Schemaless_Directory.To set Group Accounts and privileges for Default Schema --> <!-.0"> <LOGIN USER_LOGIN="admin" PASSWORD="password"> <DIR_INFO MODE = "write"> <MOD_DIR_CONFIG> Remote Insight command language 103 .44"/> <DIR_SERVER_PORT value="636"/> <DIR_OBJECT_DN value="CN=server1_rib. DC=HPRIB.and Value "YES" to enable Default Directory Login. DC=LABS"/> <!-.100. the MOD_DIR_CONFIG command must appear within a DIR_INFO command block. The user must have the configure iLO 2 privilege to execute this command.<DIR_GRPACCT3_PRIV VALUE="" /> <DIR_GRPACCT4_NAME VALUE="" /> <DIR_GRPACCT4_PRIV VALUE="" /> <DIR_GRPACCT5_NAME VALUE="" /> <DIR_GRPACCT5_PRIV VALUE="" /> <DIR_GRPACCT6_NAME VALUE="" /> <DIR_GRPACCT6_PRIV VALUE="" /> </GET_DIR_CONFIG><GET_DIR_CONFIG> MOD_DIR_CONFIG MOD_DIR_CONFIG command is used to modify the directory settings on iLO 2.141.xml. DC=LABS"/> <DIR_OBJECT_PASSWORD value="password"/> <DIR_USER_CONTEXT_1 value="CN=Users. and DIR_INFO MODE must be set to write.

NOTE: When using directory integration with schema extension. 3. 2.2." When using schema-free directory integration. The possible values are "Yes" and "No. These privileges are expressed as a comma separated list of numbers (1. 4.3.3. If a parameter is not specified. and the corresponding member iLO 2 privileges are stored in iLO 2. then the parameter value for the specified setting is preserved.4. DIR_AUTHENTICATION_ENABLED enables or disables directory authentication. the following tags must not be used: • DIR_OBJECT_DN • DIR_OBJECT_PASSWORD MOD_DIR_CONFIG parameters All of the following parameters are optional. Users.5"/> </MOD_DIR_CONFIG> </DIR_INFO> </LOGIN> </RIBCL> NOTE: When using schema-free directories.5) which correlate to: Administer Group Accounts Remote Console Access Virtual Power and Reset Virtual Media Configure iLO 2 Settings 1. • • DIR_GRPACCT1_NAME identifies a group container in the directory. such as Administrators." DIR_ENABLE_GRP_ACCT causes iLO 2 to use schama-less directory integration. These groups are contained in the directory. The possible values are "Yes" and "No. the following tags must not be used: Remote Insight command language 104 . or Power Users. You can mix and match privileges by including more than one value.2. iLO 2 supports variable privileges associated with different directory groups. DIR_GRPACCT1_PRIV numerically identify iLO 2 privileges for members of the group.4. 5.<DIR_ENABLE_GRP_ACCT value = "yes"/> <DIR_GRPACCT1_NAME value = "test1"/> <DIR_GRPACCT1_PRIV value = "1"/> <DIR_GRPACCT2_NAME value = "test2"/> <DIR_GRPACCT2_PRIV value = "2"/> <DIR_GRPACCT3_NAME value = "test3"/> <DIR_GRPACCT3_PRIV value = "3"/> <DIR_GRPACCT4_NAME value = "test4"/> <DIR_GRPACCT4_PRIV value = "4"/> <DIR_GRPACCT5_NAME value = "test5"/> <DIR_GRPACCT5_PRIV value = "5"/> <DIR_GRPACCT6_NAME value = "test6"/> <DIR_GRPACCT6_PRIV value = "1.

This value is obtained from the directory administrator. then the parameters specified in the second and third paths are used. The values for these parameters are obtained from the directory administrator. Passwords are limited to 39 characters. the following tags must not be used: • DIR_OBJECT_DN • DIR_OBJECT_PASSWORD DIR_LOCAL_USER_ACCT enables or disables local user accounts. DIR_USER_CONTEXT_1. Directory User Contexts are limited to 128 characters each. Distinguished names are limited to 256 characters. This value is obtained from the directory administrator. MOD_DIR_CONFIG runtime errors The possible MOD_DIR_CONFIG error messages include: • • Directory information is open for read-only access. If the user could not be located using the first path. RACK_INFO requires the MODE parameter with a value of read or write. The secure LDAP port is 636. The possible values are "Yes" and "No. MODE is a specific string parameter with a maximum length of 10 characters that specifies what you intend to do with the information. DIR_OBJECT_PASSWORD specifies the password associated with the iLO 2 object in the directory server. Example: <RACK_INFO MODE=”read”> ……… RACK_INFO commands ……… Remote Insight command language 105 . Only commands that are RACK_INFO type commands are valid inside the RACK_INFO command block. The RACK_INFO command generates a response that indicates to the host application whether the database was successfully read or not. DIR_USER_CONTEXT_2. Server is not a rack server. The possible RACK_INFO error messages include: • • Invalid Mode. When the command is parsed. and DIR_USER_CONTEXT_3 specify searchable contexts used to locate the user when the user is trying to authenticate using directories. DIR_OBJECT_DN specifies the unique name of iLO 2 in the directory server. CONFIG_ILO_PRIV required. Read mode prevents modification of the iLO 2 information. Write access is required for this operation. RACK_INFO The RACK_INFO command can only appear within a LOGIN command block. rack commands do not apply. This command block is only valid on ProLiant BL Class servers. User does not have correct privilege for action. then this call will fail. If the database is open for writing by another application. The directory server location is specified as an IP address or DNS name. Write mode enables both reading and writing of iLO 2 information. DIR_SERVER_PORT specifies the port number used to connect to the directory server. but the directory server can be configured for a different port number.• • • DIR_ENABLE_GRP_ACCT DIR_GRPACCT1_NAME DIR_GRPACCT1_PRIV NOTE: When using schema-free directories. it reads the rack infrastructure database into memory and prepares to edit it." DIR_SERVER_ADDRESS specifies the location of the directory server.

0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <RACK_INFO MODE="read"> <GET_RACK_SETTINGS/> </RACK_INFO> </LOGIN> </RIBCL> GET_RACK_SETTINGS parameters None GET_RACK_SETTINGS runtime errors None GET_RACK_SETTINGS return messages A possible GET_RACK_SETTINGS return message is: <GET_RACK_SETTINGS> <RACK_NAME VALUE="HPspace"/> <ENCLOSURE_NAME VALUE="Home"/> <ENCLOSURE_SN VALUE="44XP0606XP33"/> <BAY_NAME VALUE="Library"/> <BAY VALUE="2"/> <FACILITY_PWR_SOURCE VALUE="N"/> <RACK_AUTO_PWR VALUE="Y"/> <SNMP_RACK_ALERTS VALUE="Y"/> <LOG_RACK_ALERTS VALUE="N"/> </GET_RACK_SETTINGS > GET_DIAGPORT_SETTINGS The GET_DIAGPORT_SETTINGS command requests the respective iLO diagnostic port settings. the GET_DIAGPORT_SETTINGS command must appear within a RACK_INFO command block. For this command to parse correctly. Example: <RIBCL VERSION="2. and RACK_INFO MODE can be set to read or write. the GET_RACK_SETTINGS command must appear within a RACK_INFO command block.</RACK_INFO> GET_RACK_SETTINGS The GET_RACK_SETTINGS command requests the respective iLO 2's rack settings. and RACK_INFO MODE can be set to read or write. Example: <RIBCL VERSION="2.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <RACK_INFO MODE="read"> <GET_DIAGPORT_SETTINGS/> Remote Insight command language 106 . For this command to parse correctly.

</RACK_INFO> </LOGIN> </RIBCL> GET_DIAGPORT_SETTINGS parameters None GET_DIAGPORT_SETTINGS runtime errors None GET_DIAGPORT_SETTINGS return messages A possible GET_DIAGPORT_SETTINGS return message is: <GET_DIAGPORT_SETTINGS> <DP_SPEED_AUTOSELECT value="No"/> <DP_NIC_SPEED value="100"/> <DP_FULL_DUPLEX value="Yes"/> <DP_IP_ADDRESS value="192. If a parameter is not specified.255. The possible values are "Yes" or "No. The user must have the configure iLO 2 privilege to execute this command.0"> <LOGIN USER_LOGIN="username" PASSWORD="password"> <RACK_INFO MODE="write"> <MOD_DIAGPORT_SETTINGS> <DP_SPEED_AUTOSELECT value="No"/> <DP_NIC_SPEED value="100"/> <DP_FULL_DUPLEX value="Yes"/> <DP_IP_ADDRESS value="192.0"/> </GET_DIAGPORT_SETTINGS > MOD_DIAGPORT_SETTINGS The MOD_DIAGPORT_SETTINGS command is used modify the diagnostic port network settings on iLO 2. then the parameter value for the specified setting is preserved. For this command to parse correctly. the MOD_DIAGPORT_SETTINGS command must appear within a RACK_INFO command block.0.0.56"/> <DP_SUBNET_MASK value="255.255. Remote Insight command language 107 .142." It is case insensitive.168.0"/> </MOD_DIAGPORT_SETTINGS> </RACK_INFO> </LOGIN> </RIBCL> MOD_DIAGPORT_SETTINGS parameters All of the following parameters are optional. Example: <RIBCL VERSION="2. DP_SPEED_AUTOSELECT is used to automatically select the transceiver speed.56"/> <DP_SUBNET_MASK value="255. and RACK_INFO MODE must be set to write.168.142.

12.12.100.22"> <RESPONSE STATUS="0x0000" MESSAGE='No error' /> <GET_ENCLOSURE_IP_SETTINGS> <BAY_ENABLE MASK="0x0002"/> <IP_ADDRESS VALUE="170. Write access is required for this operation. DP_IP_ADDRESS is used to select the IP address for the iLO 2 Diagnostic Port.DP_NIC_SPEED is used to set the transceiver speed if DP_SPEED_AUTOSELECT was set to "No.XXX. CONFIG_ILO_PRIV required.XXX.XXX.XXX. If an empty string is entered. The expected format is XXX. the current address is unchanged.0"?> <RIBCL VERSION="2. User does not have correct privilege for action.0"> <LOGIN USER_LOGIN="Admin" PASSWORD="password"> <RACK_INFO MODE="write"> <GET_ENCLOSURE_IP_SETTINGS/> </RACK_INFO> </LOGIN> </RIBCL> GET_ENCLOSURE_IP_SETTINGS parameters None GET_ENCLOSURE_IP_SETTINGS return messages A possible GET_ENCLOSURE_IP_SETTINGS return message is: <?xml version="1.255. the current address is unchanged. DP_SUBNET_MASK is used to select the subnet mask for the iLO 2 Diagnostic Port. The RACK_INFO command block can be set to read or write. Example: <RIBCL VERSION="2. MOD_DIAGPORT_SETTINGS runtime errors Possible MOD_DIAGPORT_SETTINGS error messages include: • • iLO 2 information is open for read-only access. This attribute must appear inside the RACK_INFO command block.XXX.0"/> <GATEWAY_IP_ADDRESS VALUE="170.101"/> <SUBNET_MASK VALUE="255.255.254"/> Remote Insight command language 108 ." The possible values are "Yes" or "No." The possible values are 10 or 100. GET_ENCLOSURE_IP_SETTINGS GET_ENCLOSURE_IP_SETTINGS requests iLO 2 Static IP Bay Configuration settings. The expected format is XXX.100." It is case insensitive. It is only applicable if DP_SPEED_AUTOSELECT was set to "No. Any other value results in a syntax error. DP_FULL_DUPLEX is used to decide if the iLO 2 diagnostic port is to support full-duplex or half-duplex mode.XXX. If an empty string is entered. The iLO 2 management processor will be rebooted to apply the changes after the script has completed successfully.

0"/> <PRIM_WINS_SERVER VALUE="0.0.here.0. The logged-in user must have the configure iLO 2 privilege.0.100. The RACK_INFO command block can be set to write.0.0"/> <SEC_WINS_SERVER VALUE="0.0.33.0.0"/> <STATIC_ROUTE_1 DESTINATION="0.0.0.0.2. This command is only valid inside a RACK_INFO block. This attribute must appear inside the RACK_INFO command block.0.0.100.3.252.0"> <LOGIN USER_LOGIN="Admin" PASSWORD="password"> <RACK_INFO MODE="write"> <MOD_ENCLOSURE_IP_SETTINGS> <BAY_ENABLE MASK="0x3FE"/> <IP_ADDRESS VALUE="16.0.0"/> <TER_DNS_SERVER VALUE="0.0"> <LOGIN USER_LOGIN="Admin" PASSWORD="password"> Remote Insight command language 109 .0.0.111"/> <SUBNET_MASK VALUE="255.0.222"/> <SEC_WINS_SERVER VALUE=""/> <STATIC_ROUTE_1 DEST="16.222.0.0.1"/> <DOMAIN_NAME VALUE="sum.<DOMAIN_NAME VALUE=""/> <PRIM_DNS_SERVER VALUE="0.111"/> <SEC_DNS_SERVER VALUE=""/> <TER_DNS_SERVER VALUE=""/> <PRIM_WINS_SERVER VALUE="16.11.now"/> <PRIM_DNS_SERVER VALUE="16.0"/> <SEC_DNS_SERVER VALUE="0.0.0"/> <STATIC_ROUTE_2 DESTINATION="0.0"/> </GET_ENCLOSURE_IP_SETTINGS> </RIBCL> MOD_ENCLOSURE_IP_SETTINGS MOD_ENCLOSURE_IP_SETTINGS modifies the Static IP Bay Configuration settings.1.0.0"/> <STATIC_ROUTE_3 DESTINATION="0.100.0.0.won.0" GATEWAY="0.0.0"/> <GATEWAY_IP_ADDRESS VALUE="16. Modify settings example: <RIBCL VERSION="2.11"/> <STATIC_ROUTE_2 DEST="" GATEWAY=""/> <STATIC_ROUTE_3 DEST="" GATEWAY=""/> </MOD_ENCLOSURE_IP_SETTINGS> </RACK_INFO> </LOGIN> </RIBCL> Modify network settings to enable static IP bay configuration example: <RIBCL VERSION="2.11.0" GATEWAY="0.33" GATEWAY="16.22.255.222.0" GATEWAY="0.

Write access is required for this operation. the MASK="0x0001" only allows slot 1 to use Static IP Bay Configuration. GET_TOPOLOGY The GET_TOPOLOGY command requests the respective iLO 2 to return the current topology of the rack infrastructure." It is case insensitive. MOD_ENCLOSURE_IP_SETTINGS runtime errors The possible MOD_ENCLOSURE_IP_SETTINGS error messages include: • • Rack information is open for read-only access. that particular slot is assigned to use the Static IP Bay Configuration settings. ENCLOSURE_IP_ENABLE enables or disables the use of Static IP Bay Configuration. the GET_TOPOLOGY command must appear within a RACK_INFO command block. If the bit is set. CONFIG_ILO_PRIV is required. This attribute is only applicable on blade servers.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <RACK_INFO MODE="read"> <GET_TOPOLOGY/> </RACK_INFO> </LOGIN> </RIBCL> GET_TOPOLOGY parameters None GET_TOPOLOGY return message An example of a successful request follows: <RK_TPLGY CNT="3"> <RUID>xxxxxx</RUID> <ICMB ADDR="0xAA55" MFG="232" PROD_ID="NNN" SER="123" NAME="Power_1"> <LEFT/> <RIGHT ADDR="0xAB66" SER="123" NAME="Server_1"/> </ICMB> Remote Insight command language 110 . This command must appear inside the MOD_ENCLOSURE_IP_SETTINGS block. The LSB represents slot 1. This number can be either a hexadecimal number or a decimal number. The possible values are "Y" or "N. Each bit represents a slot in the enclosure. For example. User does not have correct privilege for action. This attribute must appear inside the MOD_NETWORK_SETTINGS command block. Example: <RIBCL VERSION="2. For this command to parse correctly. and RACK_INFO MODE can be set to read or write. The attribute MASK is a 16-bit number.<RIB_INFO MODE="write"> <MOD_NETWORK_SETTINGS> <ENCLOSURE_IP_ENABLE VALUE="Yes"/> </MOD_NETWORK_SETTINGS> </RIB_INFO> </LOGIN> </RIBCL> MOD_ENCLOSURE_IP_SETTINGS parameters BAY_ENABLEMASK enables the use of Static IP Bay Configuration addressing.

ENCLOSURE_NAME is the name used to logically group together the ProLiant BL-Class servers that compose a single enclosure. This parameter can be a combination of any printable characters up to a maximum length of 31 characters. The user must have the configure iLO 2 privilege to execute this command. RACK_AUTO_PWR determines if the blade server should automatically power when inserted into the enclosure. A value of "Yes" causes the blade server to automatically power up and begin normal booting process if power is available. then the parameter value for the specified setting is preserved. This parameter can be a combination of any printable characters up to a maximum length of 31 characters. Example: <RIBCL VERSION="2. RACK_NAME is the name used to logically group together enclosures in a single rack infrastructure. the MOD_BLADE_RACK command must appear within a RACK_INFO command block. BAY_NAME is the name used to identify a particular ProLiant BL-Class server.<ICMB ADDR="0xAB66" MFG="232" PROD_ID="NNN" SER="456" NAME="Server_1"> <LEFT ADDR="0xAA55" SER="123" NAME="Power_1"/> <RIGHT ADDR="0xAC77" SER="123" NAME="Power_2"/> </ICMB> <ICMB ADDR="0xAC77" MFG="232" PROD_ID="NNN" SER="789" NAME="Power_2"> <RIGHT/> </ICMB> </RK_TPLGY> MOD_BLADE_RACK MOD_BLADE_RACK command is used to modify the rack infrastructure settings. Remote Insight command language 111 . and RACK_INFO MODE must be set to write. This parameter can be a combination of any printable characters up to a maximum length of 31 characters.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <RACK_INFO MODE="write"> <MOD_BLADE_RACK> <RACK_NAME value="CPQ_Rack_1"/> <ENCLOSURE_NAME value="CPQ_Enclosure_1"/> <BAY_NAME value="CPQ_Bay_5"/> <FACILITY_PWR_SOURCE value="Yes"/> <RACK_AUTO_PWR value="Yes"/> <SNMP_RACK_ALERTS value="Yes"/> <LOG_RACK_ALERTS value="Yes"/> </MOD_BLADE_RACK> </RACK_INFO> </LOGIN> </RIBCL> MOD_BLADE_RACK parameters All of the following parameters are optional. For this command to parse properly. A value of "No" requires the blade server to be manually powered on. A value of "Yes" directs the server to use facility power and a value of "No" directs the server to use the server blade power supplies. FACILITY_PWR_SOURCE determines the source of power for the blade servers. If a parameter is not specified.

Rack Name too long.A graceful shutdown will be attempted for ACPI-aware <!-. Bay Name too long. SERVER_INFO requires the MODE parameter with a value of read or write.HOST_POWER="Yes" (Turns host server power on) --> Remote Insight command language 112 . LOG_RACK_ALERTS determines if alerts from the rack infrastructure should be logged. Write mode enables both reading and writing of iLO 2 information. MODE is a specific string parameter with a maximum length of 10 characters that specifies what you intend to do with the information. <!-. Enclosure Name too long. MOD_BLADE_RACK runtime errors The possible MOD_BLADE_RACK error messages include: • • • • • Rack information is open for read-only access. Only commands that are SERVER_INFO type commands are valid inside the SERVER_INFO command block.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <SERVER_INFO MODE="write"> <!-.operating systems configured to support graceful shutdown.SNMP_RACK_ALERTS determines if alerts from the rack infrastructure should be forwarded to user-defined SNMP trap destinations. Example: <SERVER_INFO MODE="read"> ……… SERVER_INFO commands ……… </SERVER_INFO> Reset server example: <RIBCL VERSION="2. A value of "Yes" enables rack alerts to be forwarded. A value of "No" disables the logging of rack alerts in the IML log. CONFIG_ILO_PRIV required. Read mode prevents modification of the iLO 2 information.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <SERVER_INFO MODE="write"> <RESET_SERVER/> </SERVER_INFO> </LOGIN> </RIBCL> Set host power example: <RIBCL VERSION="2. SERVER_INFO The SERVER_INFO command can only appear within a LOGIN command block. A value of "Yes" enables rack alerts to be logged in the IML log. User does not have correct privilege for action. A value of "No" disables rack alerts from being forwarded. Write access is required for this operation.HOST_POWER="No" (Turns host server power off) --> --> --> <!-.Modify the HOST_POWER attribute to toggle power on the host server --> <!-.

Example: <RIBCL VERSION="2.21"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <SERVER_INFO MODE="read"> <GET_EMBEDDED_HEALTH /> </SERVER_INFO> </LOGIN> </RIBCL> GET_EMBEDDED_HEALTH parameters None GET_EMBEDDED_HEALTH return messages A possible GET_EMBEDDED_HEALTH_DATA return message is: IP Address is: 16. and SEVER_INFO MODE can be set to read or write.0"?> <RIBCL VERSION="2.exe: Receiving (116): <?xml version="1.100.22"> <RESPONSE STATUS="0x0000" MESSAGE='No error' /> <GET_EMBEDDED_HEALTH_DATA> <FANS> <FAN> <LABEL VALUE = "Fan Block 1"/> <ZONE VALUE = "Power Supply"/> <STATUS VALUE = "Ok"/> <SPEED VALUE = "25" UNIT="Percentage"/> </FAN> <FAN> Remote Insight command language 113 .0"?> <RIBCL VERSION="2.exe: Receiving (116): <?xml version="1.000. the GET_EMBEDDED_HEALTH command must appear within a SERVER_INFO command block. For this command to parse correctly.<SET_HOST_POWER HOST_POWER="No"/> </SERVER_INFO> </LOGIN> </RIBCL> GET_EMBEDDED_HEALTH GET_EMBEDDED_HEALTH command is used to retrieve health information of the server.192 cpqlocfg.22"> <RESPONSE STATUS="0x0000" MESSAGE='No error' /> </RIBCL> cpqlocfg.

<LABEL VALUE = "Fan Block 2"/> <ZONE VALUE = "CPU 2"/> <STATUS VALUE = "Ok"/> <SPEED VALUE = "37" UNIT="Percentage"/> </FAN> </FANS> <TEMPERATURE> <TEMP> <LABEL VALUE = "Temp 1"/> <LOCATION VALUE = "I/O Board"/> <STATUS VALUE = "Ok"/> <CURRENTREADING VALUE = "29" UNIT="Celsius"/> <CAUTION VALUE = "65" UNIT="Celsius"/> <CRITICAL VALUE = "70" UNIT="Celsius"/> </TEMP> <TEMP> <LABEL VALUE = "Temp 2"/> <LOCATION VALUE = "Ambient"/> <STATUS VALUE = "Failed"/> <CURRENTREADING VALUE = "66" UNIT="Celsius"/> <CAUTION VALUE = "40" UNIT="Celsius"/> <CRITICAL VALUE = "45" UNIT="Celsius"/> </TEMP> <TEMP> <LABEL VALUE = "Temp 3"/> <LOCATION VALUE = "CPU 1"/> <STATUS VALUE = "Ok"/> <CURRENTREADING VALUE = "36" UNIT="Celsius"/> <CAUTION VALUE = "90" UNIT="Celsius"/> <CRITICAL VALUE = "95" UNIT="Celsius"/> </TEMP> <TEMP> <LABEL VALUE = "Temp 4"/> <LOCATION VALUE = "CPU 1"/> <STATUS VALUE = "Ok"/> <CURRENTREADING VALUE = "32" UNIT="Celsius"/> <CAUTION VALUE = "90" UNIT="Celsius"/> <CRITICAL VALUE = "95" UNIT="Celsius"/> </TEMP> <TEMP> <LABEL VALUE = "Temp 5"/> <LOCATION VALUE = "Power Supply"/> <STATUS VALUE = "Ok"/> <CURRENTREADING VALUE = "32" UNIT="Celsius"/> Remote Insight command language 114 .

exe: Script succeeded on "16.100:100" If an advanced license is applied.192:000" GET_POWER_READINGS The GET_POWER_READINGS command is used to get the power readings from the server power supply.0"?> <RIBCL VERSION="2. a typical response is: <?xml version="1.22"> <RESPONSE STATUS="0x0000" MESSAGE='No error' /> <GET_POWER_READINGS> <PRESENT_POWER_READING VALUE="275" UNIT="Watts"/> <!-Additional information is available with iLO 2 Advanced and iLO 2 Select licenses. If an advanced license is not applied.exe: Script succeeded on "16.100.0"?> <RIBCL VERSION="2. depending on whether or not an advanced license is applied.000. --> </GET_POWER_READINGS> </RIBCL> cpqlocfg. then a typical response is: <?xml version="1.22"> <RESPONSE Remote Insight command language 115 . GET_POWER_READINGS parameters None GET_POWER_READINGS return messages Two types of responses are available from the GET_POWER_READINGS command.100.100.<CAUTION VALUE = "51" UNIT="Celsius"/> <CRITICAL VALUE = "56" UNIT="Celsius"/> </TEMP> </TEMPERATURE> <VRM> </VRM> <POWER_SUPPLIES> </POWER_SUPPLIES> <HEALTH_AT_A_GLANCE> <FANS STATUS= "Ok"/> <FANS REDUNDANCY= "Fully Redundant"/> <TEMPERATURE STATUS= "FAILED"/> <VRM STATUS= "Ok"/> <POWER_SUPPLIES STATUS= "Ok"/> <POWER_SUPPLIES REDUNDANCY= "unknown"/> </HEALTH_AT_A_GLANCE> </GET_EMBEDDED_HEALTH_DATA> </RIBCL> cpqlocfg.

and SEVER_INFO MODE can be set to read or write. Example: <RIBCL VERSION="2.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <SERVER_INFO MODE="write"> <GET_HOST_POWER_SAVER_STATUS/> </SERVER_INFO> </LOGIN> </RIBCL> GET_HOST_POWER_SAVER_STATUS parameters None GET_HOST_POWER_SAVER_STATUS runtime errors The possible GET_HOST_POWER_SAVER_STATUS error messages include: • Feature not supported GET_HOST_POWER_SAVER_STATUS return messages The following information is returned within one of the following responses: • <GET_HOST_POWER_SAVER HOST POWER_SAVER="OFF" /> <GET_HOST_POWER_SAVER HOST POWER_SAVER="MIN" /> <GET_HOST_POWER_SAVER HOST POWER_SAVER="AUTO" /> • • Remote Insight command language 116 . For this command to parse correctly.STATUS="0x0000" MESSAGE='No error' /> <GET_POWER_READINGS> <PRESENT_POWER_READING <AVERAGE_POWER_READING <MAXIMUM_POWER_READING <MINIMUM_POWER_READING </GET_POWER_READINGS> </RIBCL> VALUE="275" VALUE="278" VALUE="283" VALUE="270" UNIT="Watts"/> UNIT="Watts"/> UNIT="Watts"/> UNIT="Watts"/> GET_HOST_POWER_SAVER_STATUS The GET_HOST_POWER_SAVER_STATUS command requests the state of the processor power regulator feature of the server. the GET_HOST_POWER_SAVER_STATUS command must appear within a SERVER_INFO command block.

GET_HOST_POWER_REG_INFO The GET_HOST_POWER_REG_INFO command requests iLO 2 power regulator information. The user must have the virtual power and reset privilege to execute this command. Write access is required for this operation. Power Regulator feature is not supported on this server.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <SERVER_INFO MODE="read"> <GET_HOST_POWER_REG_INFO/> </SERVER_INFO> </LOGIN> </RIBCL> GET_HOST_POWER_REG_INFO parameters None Remote Insight command language 117 . Example: <RIBCL VERSION="2. the SET_HOST_POWER_SAVER command must appear within a SERVER_INFO command block. and SERVER_INFO_MODE must be set to read. Example: <RIBCL VERSION="2. User does not have correct privilege for action.SET_HOST_POWER_SAVER The SET_HOST_POWER_SAVER command is used to set the Power Regulator Setting for the server processor. The possible values are: • • • 1 for Max (Off) 2 for Min 3 for Auto SET_HOST_POWER_SAVER runtime errors The possible SET_HOST_POWER error messages include: • • • Server information is open for read-only access. For this command to parse correctly. For this command to parse correctly. the GET_HOST_POWER_REG_INFO command must appear within a SERVER_INFO command block. RESET_SERVER_PRIV required.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <SERVER_INFO MODE="write"> <SET_HOST_POWER_SAVER HOST_POWER_SAVER="1"/> </SERVER_INFO> </LOGIN> </RIBCL> SET_HOST_POWER_SAVER parameters HOST_POWER_SAVER controls the Dynamic Power Saver feature of the server processor if the feature is supported. and SERVER_INFO MODE must be set to write.

For example: <RIBCL VERSION="2..3</TotalAverage> </Pstate0> <Pstate1> <TotalAverage>0</TotalAverage> </Pstate1> <Pstate2> <TotalAverage>65..GET_HOST_POWER_REG_INFO runtime errors GET_HOST_POWER_REG_INFO returns a runtime error if an iLO 2 Advanced License is not found.7</TotalAverage> Remote Insight command language 118 .22"> <RESPONSE STATUS="0x0043" MESSAGE='This feature requires an advanced license' /> </RIBCL> GET_HOST_POWER_REG_INFO return messages The GET_HOST_POWER_REG_INFO command returns all data available at the time of the request..7</TotalAverage> </Pstate2> <Pstate3> <TotalAverage>0</TotalAverage> </Pstate3> .. If the request occurs within the first five minutes of a system or iLO 2 reset or power cycle. A possible GET_HOST_POWER_REG_INFO return message within the five minutes of a system or iLO 2 reset or power cycle is: <GET_HOST_POWER_REG_INFO> <NumberProcessors>0</NumberProcessors> <NumberPstates>0</NumberPstates> </GET_HOST_POWER_REG_INFO> A possible GET_HOST_POWER_REG_INFO return message when all data is available is: <GET_HOST_POWER_REG_INFO> <NumberProcessors>2</NumberProcessors> <NumberPstates>3</NumberPstates> <Processor0> <CurrentPstate>2</CurrentPstate> <Pstate0> <TotalAverage>34.3</TotalAverage> </Pstate0> <Pstate1> <TotalAverage>0</TotalAverage> </Pstate1> <Pstate2> <TotalAverage>65. <Pstate7> <TotalAverage>0</TotalAverage> </Pstate7> </Processor0> <Processor1> <CurrentPstate>2</CurrentPstate> <Pstate0> <TotalAverage>34.. only a limited amount of data is available.

. the GET_HOST_POWER_STATUS command must appear within a SERVER_INFO command block. Example: <RIBCL VERSION="2. and SEVER_INFO MODE can be set to read or write. and SERVER_INFO MODE must be set to write. The user must have the virtual power and reset privilege to execute this command. GET_HOST_POWER_STATUS Return Messages The following information is returned within the response: <GET_HOST_POWER /> HOST POWER="OFF" SET_HOST_POWER The SET_HOST_POWER command is used to toggle the power button of server. For this command to parse correctly.. For this command to parse correctly. the SET_HOST_POWER command must appear within a SERVER_INFO command block.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <SERVER_INFO MODE="write"> <GET_HOST_POWER_STATUS/> </SERVER_INFO> </LOGIN> </RIBCL> GET_HOST_POWER_STATUS Parameters None GET_HOST_POWER_STATUS Runtime Errors The possible GET_HOST_POWER_STATUS error messages include: • • Host power is OFF. <Pstate7> <TotalAverage>0</TotalAverage> </Pstate7> </Processor1> </GET_HOST_POWER_REG_INFO> GET_HOST_POWER_STATUS The GET_HOST_POWER_STATUS command requests the power state of the server. Example: <RIBCL VERSION="2..</Pstate2> <Pstate3> . Host power is ON.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <SERVER_INFO MODE="write"> <SET_HOST_POWER HOST_POWER="Yes"/> Remote Insight command language 119 ..

RESET_SERVER_PRIV required. Example: Remote Insight command language 120 . Host power is already ON. Server is currently powered off. For this command to parse correctly. if the server is currently on. Write access is required for this operation. the RESET_SERVER command must appear within a SERVER_INFO command block.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <SERVER_INFO MODE="write"> <RESET_SERVER/> </SERVER_INFO> </LOGIN> </RIBCL> RESET_SERVER errors The possible RESET_SERVER error messages include: • • • Server information is open for read-only access. Host power is already OFF. The user must have the virtual power and reset privilege to execute this command. RESET_SERVER The RESET_SERVER command will force a warm boot of the server. Write access is required for this operation. The user must have the virtual power and reset privilege to execute this command." SET_HOST_POWER Runtime Errors The possible SET_HOST_POWER error messages include: • • • • • Server information is open for read-only access. and SERVER_INFO MODE must be set to write. RESET_SERVER_PRIV required. the PRESS_PWR_BTN command must appear within a SERVER_INFO command block. Virtual Power Button feature is not supported on this server. The possible values are "Yes" or "No.</SERVER_INFO> </LOGIN> </RIBCL> SET_HOST_POWER Parameters HOST_POWER enables or disables the Virtual Power Button. User does not have correct privilege for action. RESET_SERVER parameters None PRESS_PWR_BTN This PRESS_PWR_BTN command is used to simulate a physical press of the server power button. Example: <RIBCL VERSION="2. User does NOT have correct privilege for action. and SERVER_INFO MODE must be set to write. For this command to parse correctly.

<RIBCL VERSION="2.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <SERVER_INFO MODE="write"> <PRESS_PWR_BTN/> </SERVER_INFO> </LOGIN> </RIBCL>

PRESS_PWR_BTN parameters
There are no parameters for this command.

PRESS_PWR_BTN runtime errors
The possible error messages include:
• •

Server information is open for read-only access. Write access is required for this operation. User does not have correct privilege for action. RESET_SERVER_PRIV required.

HOLD_PWR_BTN
This HOLD_PWR_BTN command is used to simulate a physical press and hold of the server power button. For this command to parse correctly, the HOLD_PWR_BTN command must appear within a SERVER_INFO command block, and SERVER_INFO MODE must be set to write. The user must have the virtual power and reset privilege to execute this command. Example: <RIBCL VERSION="2.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <SERVER_INFO MODE="write"> <HOLD_PWR_BTN/> </SERVER_INFO> </LOGIN> </RIBCL>

HOLD_PWR_BTN parameters
There are no parameters for this command.

HOLD_PWR_BTN runtime errors
The possible error messages include:
• •

Server information is open for read-only access. Write access is required for this operation. User does not have correct privilege for action. RESET_SERVER_PRIV required.

COLD_BOOT_SERVER
This COLD_BOOT_SERVER command will force a cold boot of the server, if the server is currently on. For this command to parse correctly, the COLD_BOOT_SERVER command must appear within a SERVER_INFO command block, and SERVER_INFO MODE must be set to write. The user must have the virtual power and reset privilege to execute this command. Example: <RIBCL VERSION="2.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password">

Remote Insight command language 121

<SERVER_INFO MODE="write"> <COLD_BOOT_SERVER/> </SERVER_INFO> </LOGIN> </RIBCL>

COLD_BOOT_SERVER parameters
There are no parameters for this command.

COLD_BOOT_SERVER runtime errors
The possible error messages include:
• • •

Server information is open for read-only access. Write access is required for this operation. Host power is already OFF. User does not have correct privilege for action. RESET_SERVER_PRIV required.

WARM_BOOT_SERVER
This WARM_BOOT_SERVER command will force a warm boot of the server, if the server is currently on. For this command to parse correctly, the WARM_BOOT_SERVER command must appear within a SERVER_INFO command block, and SERVER_INFO MODE must be set to write. The user must have the virtual power and reset privilege to execute this command. Example: <RIBCL VERSION="2.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <SERVER_INFO MODE="write"> <WARM_BOOT_SERVER/> </SERVER_INFO> </LOGIN> </RIBCL>

WARM_BOOT_SERVER parameters
There are no parameters for this command.

WARM_BOOT_SERVER runtime errors
The possible error messages include:
• • •

Server information is open for read-only access. Write access is required for this operation. Host power is already OFF. User does not have correct privilege for action. RESET_SERVER_PRIV required.

SERVER_AUTO_PWR
The SERVER_AUTO_PWR command is used to set the automatic power on and power on delay settings of the server. This command is supported by iLO 2 firmware version 1.20 or later. It is not supported by iLO firmware or RILOE II. Example: <RIBCL VERSION="2.0">

Remote Insight command language 122

<LOGIN USER_LOGIN="Administrator" PASSWORD="password"> <SERVER_INFO MODE="write"> <!-- Enable automatic power on with 30 seconds delay --> <SERVER_AUTO_PWR VALUE="30" /> </SERVER_INFO> </LOGIN> </RIBCL>

SERVER_AUTO_PWR parameters
The possible values are:
• • • • • • •

Yes enables automatic power on with a minimum delay. No disables automatic power on. 15 enables automatic power on with 15-second delay. 30 enables automatic power on with 30-second delay. 45 enables automatic power on with 45-second delay. 60 enables automatic power on with 60-second delay. Random enables automatic power on with random delay up to 60-second.

SERVER_AUTO_PWR runtime errors
The possible error messages include:
• •

User does not have correct privilege for action. RESET_SERVER_PRIV required. The value specified for SERVER_AUTO_PWR is invalid.

GET_SERVER_AUTO_PWR
The GET_SERVER_AUTO_PWR command is used to get the automatic power on and power on delay settings of the server. Example: <RIBCL VERSION="2.0"> <LOGIN USER_LOGIN="Administrator" PASSWORD="password"> <SERVER_INFO MODE="read"> <GET_SERVER_AUTO_PWR /> </SERVER_INFO> </LOGIN> </RIBCL>

GET_SERVER_AUTO_PWR parameters
None

GET_SERVER_AUTO_PWR return message
A possible GET_SERVER_AUTO_PWR return is: <?xml version="1.0"?> <RIBCL VERSION="2.22"> <RESPONSE STATUS="0x0000" MESSAGE='No error'

Remote Insight command language 123

--> <SERVER_AUTO_PWR VALUE="30" /> </GET_SERVER_AUTO_PWR> </RIBCL> GET_UID_STATUS The UID_STATUS command requests the state of the server UID. the UID_CONTROL command must appear within a SERVER_INFO command block. the UID_STATUS command must appear within a SERVER_INFO command block. Example: <RIBCL VERSION="2. Example: <RIBCL VERSION="2.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <SERVER_INFO MODE="write"> <UID_CONTROL UID="Yes"/> </SERVER_INFO> </LOGIN> </RIBCL> Remote Insight command language 124 . For this command to parse correctly.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <SERVER_INFO MODE="write"> <GET UID_STATUS /> </SERVER_INFO> </LOGIN> </RIBCL> GET_UID_STATUS parameters None GET_UID_STATUS response The following information is returned within the response: <GET_UID_STATUS /> UID="OFF" UID_CONTROL The UID_CONTROL command toggles the server UID. For this command to parse correctly. and SEVER_INFO MODE can be set to read or write. and SEVER_INFO MODE must be set to write./> <GET_SERVER_AUTO_PWR> <!-Automatically Power On Server is enabled with 30 seconds power on delay.

and a value of "No" turns the UID light off. <RIBCL VERSION="2. GET_VPB_CABLE_STATUS return messages A possible GET_VPB_CABLE_STATUS return message is: <RIBCL VERSION="2. A value of "Yes" turns the UID light on. UID_CONTROL errors The possible UID_CONTROL error messages include: • • UID is already ON. GET_VPB_CABLE_STATUS (RILOE II only) The GET_VPB_CABLE_STATUS to return the status of the Virtual Power Button cable that may be connected to a RILOE II board. For this command to parse correctly. Virtual Power Button cable is not attached.UID_CONTROL parameters UID determines the state of the UID.0"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <SERVER_INFO MODE="read"> <GET_VPB_CABLE_STATUS/> </SERVER_INFO> </LOGIN> </RIBCL> GET_VPB_CABLE_STATUS parameters None GET_VPB_CABLE_STATUS Runtime Errors The possible GET_VPB_CABLE_STATUS error messages include: • • Virtual Power Button cable is attached. the GET_VPB_CABLE_STATUS command must appear within a SERVER_INFO command block.22"> <RESPONSE STATUS="0x0000" MESSAGE='No error' /> <GET_VPB_CABLE> <VIRTUAL POWER BUTTON CABLE="ATTACHED"/> </GET_VPB_CABLE> </RIBCL> Remote Insight command language 125 . UID is already OFF. and SEVER_INFO MODE can be set to read or write.

.............hp...................CN=Users............CN=Users..............DC=HP" /> <DIR_LOGIN_NAME value="RILOEGRP2\Adminl" /> <DIR_LOGIN_PASSWORD value="aurora" /> </MOD_DIR_CONFIG> </DIR_INFO> </LOGIN> </RIBCL> HPQLOMGC command language 126 ........ HPQLOMGC does not operate on iLO 2 devices.................... The following is an example of an XML file: <RIBCL VERSION="2........................................................0"> <LOGIN USER_LOGIN="user" PASSWORD="password"> <DIR_INFO MODE="write"> <ILO_CONFIG> <UPDATE_RIB_FIRMWARE IMAGE_LOCATION="C:\fw\ilo140..DC=RILOEGRP2.......... 126 ILO_CONFIG .......brk" /> </RILOE2_CONFIG> <MOD_DIR_CONFIG> <DIR_AUTHENTICATION_ENABLED value="YES" /> <DIR_LOCAL_USER_ACCT value="YES" /> <DIR_SERVER_ADDRESS value="administration................... The script used is a subset of the RIBCL and has been extended to support multiple management processor firmware images................com" /> <DIR_SERVER_PORT value="636" /> <DIR_OBJECT_DN value="CN=RILOP5....................wins...DC=RILOEGRP2....brk" /> </RILOE_CONFIG> <RILOE2_CONFIG> <UPDATE_RIB_FIRMWARE IMAGE_LOCATION="C:\fw\riloeii..................DC=HP" /> <DIR_OBJECT_PASSWORD value="aurora" /> <DIR_USER_CONTEXT_1 value="CN=Users.......HPQLOMGC command language In this section Using HPQLOMGC ........ 127 Using HPQLOMGC HPQLOMGC reads directory settings for the management processor from an XML file...brk" /> </ILO_CONFIG> <RILOE_CONFIG> <UPDATE_RIB_FIRMWARE IMAGE_LOCATION="C:\fw\riloe.........DC=RILOEGRP2..........DC=HP" /> <DIR_USER_CONTEXT_2 value="" /> <DIR_USER_CONTEXT_3 value="" /> <DIR_ROLE value="CN=RILOEROLE.

These commands must be displayed within a DIR_INFO block. To update the firmware. The management processor is reset after the firmware upgrade is complete. The command language for HPQLOMGC has been modified to allow for each management processor to have a specified firmware image within a single XML file.ILO_CONFIG RIBCL allows for only one firmware image per XML file. the user must be logged in with the appropriate privilege. and DIR_INFO must be in write mode. This command line uses the following parameters: • • UPDATE_RIB_FIRMWARE IMAGE_LOCATION ("UPDATE_RIB_FIRMWARE parameters" on page 90) MOD_DIR_CONFIG HPQLOMGC command language 127 .

.. the iLO 2 dedicated management NIC port is active. 5. Select File>Exit and press the Enter key.. iLO 2 ports 128 .. and press the Enter key.............. the iLO 2 RBSU (described in the user guide) or XML scripting must be used............iLO 2 ports In this section Enabling the iLO 2 Shared Network Port feature through XML scripting ......... toggle the Network Interface Adapter Field to ON by pressing the space bar......... Select Network>NIC>TCP/IP....... 3... When prompted during POST... Using this script on platforms that do not support the Shared Network Port will cause an error.. To re-enable the dedicated management port using RBSU: 1......... 128 Enabling the iLO 2 Shared Network Port feature through XML scripting For information on how to use the SHARED_NETWORK_PORT command to enable the iLO 2 Shared Network Port through XML scripting.. Reboot the server................. press the F8 key to enter iLO 2 RBSU... After the iLO 2 resets........21"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <RIB_INFO MODE="WRITE"> <MOD_NETWORK_SETTINGS> <SHARED_NETWORK_PORT VALUE="Y" /> </MOD_NETWORK_SETTINGS> </RIB_INFO> </LOGIN> </RIBCL> Re-enabling the dedicated NIC management port To re-enable the iLO 2 dedicated NIC management port. For information on how to use the SHARED_NETWORK_PORT command to re-enable the iLO 2 dedicated management port see the "Remote Insight command language (on page 65)" section...... You can customize this script to your needs. <RIBCL version="2..... Connect the iLO 2 dedicated NIC management port to a LAN from which the server is managed...... 2.... 128 Re-enabling the dedicated NIC management port .. Press the F10 key to save the configuration. 4.................. In the Network Configuration menu.... The following sample script configures the iLO 2 to select the Shared Network Port. 6....... see the “Remote Insight command language (on page 65)” section... 7..

Using this script on platforms that do not support the Shared Network Port will cause an error. <RIBCL version="2. use the following sample RIBCL script. The sample script configures the iLO 2 to select the iLO 2 Network Port.21"> <LOGIN USER_LOGIN="adminname" PASSWORD="password"> <RIB_INFO MODE="WRITE"> <MOD_NETWORK_SETTINGS> <SHARED_NETWORK_PORT VALUE="N" /> </MOD_NETWORK_SETTINGS> </RIB_INFO> </LOGIN> </RIBCL> iLO 2 ports 129 .To re-enable the dedicated iLO 2 using XML. You can modify this script for your specific needs.

............................................................................................................ 137 Directory settings parameters .................................................................................................... Displays whether the pass-through software to support Microsoft® Terminal Services is present......................... 131 User Administration parameters .................................................... The iLO 2 internal calendar is synchronized with the host system at POST and when the Insight Agents run........................... 132 Network Settings parameters ................................................................................ 130 Server Status parameters..................................................................................................... 131 Global Settings parameters .......................................... Displays the time as indicated by the iLO 2 subsystem internal clock.................................. derived from the host serial number...................XX iLO 2XXXXXXXXXXXX Displays the firmware revision level of the iLO 2 subsystem......................................................... 135 SNMP/Insight Manager settings parameters ... Displays the iLO 2 product functionality currently licensed....................... 139 iLO Advanced Pack License Key......... 140 iLO 2 Status parameters Parameter Current user Remote console Terminal services Disabled Default value Definition Displays the user currently logged into the iLO 2 through this browser..... Displays the serial number..................... 138 BL p-Class parameters......................................iLO 2 parameters In this section iLO 2 Status parameters......................... Displays the date (MM/DD/YYYY) as indicated by the iLO 2 subsystem internal calendar... Displays whether the remote console is available to the current user.................. XX.............. iLO 2 time iLO 2 date iLO 2 firmware version iLO 2 serial number Product version License expires iLO 2 parameters 130 ........................................................................ associated with this iLO 2........................... The iLO 2 internal clock is synchronized with the host system at POST and when the Insight Agents run............................................................................................................... Displays the remaining time in the iLO 2 advanced feature evaluation period and is displayed only when evaluation licenses are installed.............

iLO 2 can also be reconfigured if iLO 2 RBSU is enabled. revoking this privilege from all users prevents reconfiguration. and mouse controls. It is not the name used to log in. they will provide the iLO 2 with the server name. A user with the Administer User Accounts privilege can enable or disable this privilege. Displays if the host is powered ON. It does not include user account administration. Server ID Server power status User Administration parameters Parameter User name Default value Administrator Definition This parameter is the user's real name as it is displayed in the user list and event log. eightcharacter alphanumeric string that is factory assigned Administer user accounts Yes Remote console access Yes Virtual power and reset Virtual media Configure iLO 2 settings Yes Yes Yes iLO 2 parameters 131 . the minimum password length can be assigned.Server Status parameters Parameter Server name Default value Definition Displays the server name if the Insight Management Agents are being used with the host server operating system. or in STANDBY (OFF) mode. This privilege enables a user to configure most iLO 2 settings. including video. Login name Password Administrator A random. Displays the serial number of the server. You must enter the password twice for verification. After iLO 2 is correctly configured. This is a case-sensitive name that the user must provide to log in to iLO 2. modify. This privilege allows a user to add. This is a case-sensitive password that the user must provide to log in to iLO 2. and delete user accounts. The default minimum password length is eight characters. This privilege allows a user to power-cycle or reset the host platform. keyboard. The minimum password can be from 0 to 39 characters. including granting all permissions to a user. including security settings. This privilege allows a user to use virtual media on the host platform. In Security Options. It also allows the user to alter privileges for all users. This privilege allows a user to remotely manage the Remote Console of a managed system. The maximum length of the user name is 39 characters.

Yes • • Enable Pass-Through configuration No This controls the ability to support a connection through the iLO 2 between a Microsoft® Terminal Services client and Terminal Services server running on the host. No disables the High Performance Mouse and instructs the iLO 2 to emulate a conventional USB mouse. all connections to iLO 2 are prevented. There are two options: • Yes means the pass-through feature is enabled but will not launch automatically. The iLO 2 10/100 network and communications with operating system drivers will be turned off if Lights-Out functionality is disabled. RBSU is invoked when the host system reboots and performs POST.Global Settings parameters Parameter Idle connection timeout (minutes) Enable Lights-Out functionality Default value 30 minutes Description This setting specifies the interval of user inactivity. before the web server and Remote Console session are automatically terminated. Show iLO 2 during POST No This setting specifies if the iLO 2 is displayed during POST. The iLO 2 Diagnostic Port for an HP ProLiant BL p-Class server is disabled as well. If iLO 2 functionality. Click the Terminal Svcs button in Remote Console to start the client. You can restrict RBSU access to authorized users by selecting Require Login for iLO 2 RBSU. iLO 2 parameters 132 . Power on the server and use the iLO 2 RBSU to set Enable Lights-Out Functionality. High Performance Mouse is only supported on operating systems that support USB tablet mouse. If the physical security jumper is set. including the iLO 2 Diagnostic Port. • Yes means that the pass-through feature is enabled and can connect the Terminal Services client directly to the iLO 2 without logging in to the iLO 2. This option enables connection to the iLO 2. If disabled. in minutes. • Automatic mode instructs the iLO 2 driver to tell the management processor to enable or disable High Performance based on the operating system that is preset. Yes enables the High Performance Mouse. • Enable iLO 2 RBSU Yes This setting enables a user with access (physical or virtual) to the host to configure the iLO 2 for that system using the iLO 2 RBSU. Enable High Performance Mouse Automatic This option enables iLO 2 to use the High Performance Mouse feature. • Require login for iLO 2 RBSU No This setting controls the ability of iLO 2 to pass through a connection between a Microsoft® Terminal Services client and Terminal Services server running on the server that has the iLO 2 installed. you must use the Security Override Switch in the server to enable iLO 2 functionality. Follow the server documentation of the server to locate the Security Override Switch and set it to the override position. the RBSU prompt displays during reboot. No means that the pass-through feature is disabled. is disabled. No means that the pass-through feature is off.

providing access to the iLO 2 CLP. This port setting is configurable in the Global Settings option of the Administration tab. If the Terminal Services pass-through port is configured to anything other than the default. The embedded web server in iLO 2 is configured by default to use port 80 for unencrypted communications. The virtual media support in the iLO 2 uses a configurable port for its communications. The iLO 2 SSH port is configured by default to use port 22 for SSH communications. This port setting is configurable in the Global Settings option of the Administration tab. This port setting is configurable in the Global Settings option of the Administration tab. Network port scanners can detect that iLO 2 is listening on this port. The embedded web server in iLO 2 is configured by default to use port 443 for encrypted communications. Valid settings are: • Yes—iLO 2 will enable telnet clients to connect to the Remote Console/Telnet port. the port number in Windows® 2000 must be manually changed to match it. but telnet connections will not be accepted. • Communication between the iLO 2 and Remote Consoles is always encrypted. The iLO 2 Terminal Services pass-through is configured by default to use port 3389 for encrypted communications. Valid values are from 1 to 65535. The Terminal Services port is the port that the iLO 2 uses to communicate with Terminal Services pass-through software on the server. Unencrypted communication is allowed between the iLO 2 CLP and telnet clients. The most secure is 128-bit (High). iLO 2 will listen on this port for a few seconds when the Remote Console is opened. This port setting is configurable in the Global Settings option of the Administration tab.Parameter Enable Telnet Default value No Description This setting enables you to connect a telnet client to the Remote Console/Telnet port. No— iLO 2 will not enable telnet clients to connect to the Remote Console/Telnet port. Network port scanners will not normally detect if this port is open on iLO 2. This port can be set in the Global Settings option of the Administration tab. Web server Non-SSL port Web server SSL port 443 Virtual media port 17988 Remote console port 23 Terminal services port 3389 Secure shell(SSH) port 22 Enable Secure Shell (SSH) Access Enabled iLO 2 parameters 133 . This port setting is configurable in the Global Settings option of the Administration tab. The iLO 2 Remote Console is configured by default to use port 23 for Remote Console communications. SSL encryption strength Current cipher 128-bit Negotiated by the iLO 2 and the browser 80 This setting displays the current cipher strength setting. This setting displays the encryption algorithm currently being used to protect data during transmission between the browser and the iLO 2. This setting enables you to specify if the SSH feature on the iLO 2 is enabled or disabled.

This value is assigned when using the HP ProLiant Management Agents. This setting enables you to specify the language model of the keyboard during a Remote Console session. The character length can be set at a value from zero to 39. This setting specifies the minimum number of characters allowed when a user password is set or changed. 8 data bits. This setting enables you to specify which port the embedded web server in iLO 2 uses for unencrypted communications. and 115200. Minimum password length Remote keyboard model Server Name 8 US — Parameter Secure Shell (SSH) Access Secure shell (SSH) port Telnet Access Default value Enabled 22 Disabled Description This setting enables you to specify whether the SSH feature on the iLO 2 is enabled or disabled. The following settings are valid: • Enabled—iLO 2 will allow telnet clients to connect to the Remote Console/Telnet port. providing access to the iLO 2 CLP. If the agents are running. 19200. Unencrypted communication is allowed between the iLO 2 CLP and telnet clients. Network port scanners can detect that iLO 2 is listening on this port. but if you do not use the agents and host unnamed is displayed. you can change it here. the value you assign can be overwritten. This setting enables you to specify the host server name. 57600. Valid settings are: • • • Enabled (authentication required) Enabled (no authentication) Disabled Serial command line interface speed (bits/second) 9600 This setting enables you to change the speed of the serial port for the CLI feature through the serial port. The serial port speed set by this parameter must match the speed of the serial port set in the System ROM RBSU setup. iLO 2 parameters 134 . but telnet connections will not be accepted. Network port scanners will not normally detect if this port is open on iLO 2. Disabled— iLO 2 will not allow telnet clients to connect to the Remote Console/Telnet port. This setting enables you to connect a telnet client to the Remote Console/Telnet port. 38400.Parameter Serial command line interface status Default value Enabled (authentication required) Description This setting enables you to change the status of the CLI feature through the serial port. To force the browser to refresh use the F5 key after saving this setting. and 1 stop bit (N/8/1) for proper operation. Remote Console/Telnet Port Web Server Non-SSL Port 23 80 This setting enables you to specify which port the iLO 2 Remote Console uses for Remote Console communications. The serial port configuration must be set to No parity. iLO 2 will listen on this port for a few seconds when the Remote Console is opened. This setting enables you to configure the iLO 2 SSH port to be used for SSH communications. • Communication between the iLO 2 and Remote Console is always encrypted. Valid speeds are (in bits/s) 9600.

Shared network port No Transceiver speed autoselect Yes Speed Duplex N/A (autoselect) Use this setting to assign 10-Mb/s or 100-Mb/s connect speeds if Transceiver Speed Autoselect is not enabled. This setting enables you to specify the port for virtual media support in iLO 2 communications. • Terminal Services Port 3389 This setting enables you to specify the Terminal Services port that the iLO 2 uses for encrypted communications with Terminal Services pass-through software on the server. the Terminal Services client will be launched. you must assign a static IP address to the iLO 2. Assign the IP address using the iLO 2 IP address parameter. iLO 2 parameters 135 . If the option is available. Refer to your server documentation for additional information. Enabled—Tthe pass-through feature is enabled and can connect the Terminal Services client directly to the iLO 2 without logging-in to the iLO 2. If DHCP is disabled. The following settings are valid: • • Automatic—When remote console is started. This option only displays on servers that support the iLO 2 Shared Network Port. N/A (autoselect) Use this setting to assign half or full duplex to the NIC if Transceiver Speed Autoselect is not enabled.Parameter Web Server SSL Port Terminal Services Passthrough Default value 443 Disabled Description This setting enables you to specify which port the embedded web server in iLO 2 uses for encrypted communications. This setting enables you to control the ability to support a connection through the iLO 2 between a Microsoft® Terminal Services client and Terminal Services server running on the host. If the Terminal Services port is configured to anything other than the default. Disabled—The pass-through feature is off. the help content for the iLO 2 Shared Network Port is also displayed. which is enabled. Selecting Yes will disable the iLO 2 NIC and directs the iLO 2 network traffic over the designated host NIC. Autoselect detects the interface speed and sets the interface to operate at 10 Mb/s or 100 Mb/s and at half or full duplex. The default setting for the NIC is Yes. Virtual Media Port 17988 Network Settings parameters Parameter Enable NIC Default value Yes Definition This parameter enables the NIC to reflect the state of the iLO 2. If necessary. you must manually change the port number in Windows® 2000 to match it. this parameter can be set to manual to allow manual adjustment of speed and duplex settings.

This option causes the iLO 2 to send four ICMP echo request packets to the gateway when iLO 2 initializes. the subnet mask is assigned by DHCP. If not. By default. Yes Yes Yes Yes Yes No IP address Subnet mask Gateway IP address N/A (DHCP) N/A (DHCP) N/A (DHCP) iLO 2 subsystem name iLO 2XXXXXXXXXXX X. If not. If not. enter one in the Gateway IP Address box. Use the gateway parameter to assign the IP address of the network router that connects the iLO 2 subnet to another subnet where the management console resides. Enabling DHCP allows you to configure the following DHCP options: • • • • • Use DHCP Supplied Gateway Use DHCP Supplied DNS Servers Use DHCP Supplied WINS Servers Use DHCP Supplied Static Routes Use DHCP Supplied Domain Name Use DHCP supplied gateway Use DHCP supplied DNS servers Use DHCP supplied WINS servers Use DHCP supplied static routes Use DHCP supplied domain name Register with WINS server Register with DDNS server Ping gateway on startup Yes Yes Toggles whether the iLO 2 will use the DHCP server-supplied gateway. iLO 2 parameters 136 . Toggles whether the iLO 2 will use the DHCP server-supplied DNS server list. By default. #3 boxes. By default. enter one in the Primary/Secondary/Tertiary DNS Server boxes. enter one in the Static Route #1. WINS server addresses are assigned by DHCP. Toggles whether iLO 2 will use the DHCP server-supplied static route. By default. enter one in the Primary/Secondary WINS Server boxes. the domain name is assigned by DHCP. By default. where the 12 Xs are the server serial number (assigned at the factory) N/A (DHCP) Domain name Enter the name of the domain in which the iLO 2 will participate. The iLO 2 automatically registers with a WINS server. #2. the gateway is assigned by DHCP. You cannot set the iLO 2 IP address and subnet mask if DHCP is enabled. The iLO 2 automatically registers with a DNS server. Use the subnet mask parameter to assign the subnet mask for the default gateway. the IP address is assigned by DHCP. Toggles whether the iLO 2 will use the DHCP server-supplied domain name. enter one in the Domain Name box. Use this parameter to assign a static IP address to the iLO 2 on your network. DNS server addresses are assigned by DHCP. The iLO 2 comes preset with a DNS/WINS name. You can change this value.Parameter Enable DHCP Default value Yes Definition Enables you to select static IP (disabled) or Enables the use of a DHCP server to obtain an IP address for the iLO 2 subsystem. The DNS/WINS name is "iLO 2" plus the serial number of the server. Toggles whether the iLO 2 will use the DHCP server-supplied WINS server list. If not. This name also is displayed on the tag attached to the bracket of iLO 2. If not. This option ensures that the ARP cache entry for iLO 2 is current on the router responsible for routing packets to and from iLO 2. By default.

Use this parameter to assign a unique static route destination and gateway IP address pair on the network. Use this parameter to assign a unique DNS server IP address on the network.255. Use this parameter to assign a unique WINS server IP address on the network. the primary and secondary WINS servers are assigned by DHCP. the Diagnostic Port IP address is automatically supplied. If not.0 The subnet mask for the Diagnostic Port IP network.1. and tertiary DNS server Primary and secondary WINS server Static routes #1. and tertiary DNS servers are assigned by DHCP. If the Autoselect option is set to Yes. These alerts can be Insight Manager SNMP traps. You cannot change this setting. They also include the iLO 2 events. The iLO 2 forwards the alerts to an HP SIMconsole using the destinations provided. Primary. the primary. enter a static IP address here. This speed must match the speed of the Diagnostic Port network. Enable iLO 2 SNMP alerts No iLO 2 parameters 137 . If the Autoselect option is set to Yes. secondary. The duplex should match the duplex of the Diagnostic Port network. Duplex IP address Subnet mask 255.1 The Diagnostic Port IP address. By default.168. N/A (autoselect) Configures the duplex of the Diagnostic Port. the speed will be automatically configured by the iLO 2. the static routes are assigned by DHCP. Up to three static route pairs can be assigned. If not. 192. If DHCP is being used. enter the subnet mask for the network. SNMP/Insight Manager settings parameters Parameter SNMP alert destination(s) Default Value No Definition Enter the IP address of the remote management PC that will receive SNMP trap alerts from the iLO 2.Parameter DHCP server Default value N/A (DHCP) Definition This setting is automatically detected if DHCP is set to Yes. the Subnet Mask is automatically supplied. By default. N/A (autoselect) Configures the speed of the Diagnostic Port. Up to three IP addresses can be designated to receive SNMP alerts.255. such as remote server power outages or server resets. The iLO 2 alert conditions are detected by the iLO 2 and are independent of the host server operating system. Speed and Duplex are disabled if Autoselect is set to Yes. #2. N/A (DHCP) secondary. If DHCP is being used. By default. such as security disabled or failed login attempt. the duplex will be automatically configured by the iLO 2. These alerts include major events. #3 N/A (DHCP) N/A for both the destination and gateway address (DHCP) Blade server parameters Diagnostic port configuration parameters Transceiver speed autoselect Speed Yes Toggles the ability of the Transceiver to auto-detect the speed and duplex of the network on the Diagnostic Port.

HP recommends using a DNS name or multi-host DNS name. When set to No.0. Directory settings parameters Parameter Disable directory authentication Default value No Definition This parameter enables or disables directory authentication. These alerts are sent to HP SIM clients on the network and are forwarded asynchronously by the iLO 2 to the IP addresses that have been configured to receive them. The None Data Level prevents the iLO 2 from responding to the HP SIM requests. The Enable SNMP pass-through option enables the system to pass SNMP packets from the Insight Management Agent. This parameter enables or disables the use of schema-free directories. This parameter specifies the Directory Server DNS name or IP address. this enables user login to iLO 2 using directory credentials. provide sufficient data to allow integration with HP SIM. All settings.0 Directory server LDAP port 636 iLO 2 parameters 138 . The Insight Manager Web Agent URL option enables you to enter the IP address or the DNS name of the host server on which the Insight Manager Web Agents are running. The Medium and High settings enable HP SIM and Systems Insight Manager to associate the management processor with the host server. except the None Data Level. This option sets the port number used to connect to the directory server. This option enables a user to log in using a local user account instead of a directory account. The agents must be installed on the host server to receive these alerts. If directory support is properly configured. Entering this data in the field provided enables iLO 2 to create a link from the iLO 2 Web pages to the pages of the Web Agent. By default. the directory will not be available if that server is down. The SSL-secured LDAP port number is 636. which are provided for each supported network operating system. these alerts are generated by the Insight Management agents. This parameter enables or disables the use of extended schema directories. this setting is Enabled. Enable SNMP pass-thru Yes Insight Manager Web Agent URL Level of data returned Medium The Level of Data Returned option regulates how much data is returned to an anonymous request for the iLO 2 information from HP SIM. If an IP address is used.0. Schema-free directory Use HP extended schema Enable local user accounts Directory server address Yes No Yes 0.Parameter Forward Insight Manager Agent SNMP alerts Default Value No Definition When set to Yes. all SNMP traffic is stopped and will not pass-through the iLO 2.

The bay name is used when logging and alerting to assist in identifying a component or its function. This parameter specifies the password for the iLO 2 object to access the directory. the rack name is communicated to all other components connected in a rack. This field is to provide forward compatibility with future firmware releases.ou=lights out devices. If you change the LOM Object Password. This eliminates the requirement of entering a fully distinguished user name at the login screen. The bays are numbered from left to right starting with 1 and finishing with 8. the LOM Object Password field is not used.o=corp" would allow the user "cn=manager. The name is used when logging and alerting to assist in identifying the component." BL p-Class parameters Parameter Rack name Default value Provided by rack Definition The rack name is used to logically group together the components that compose a single rack. Directory User Contexts are limited to 128 characters each. the search context. Enclosure name Provided by rack Bay name Bay iLO 2 parameters 139 . When changed. directory user context 3 Prevents mistyped passwords. also enter the new password in this field.corp.Parameter LOM object distinguished name LOM object password Default value Definition This option specifies the unique name for the iLO 2 in the directory. LOM Object Passwords are limited to 39 characters. NOTE: At this time. The name is used when logging and alerting to assist in identifying the component. the enclosure name is communicated to all other server blades connected in the same enclosure. For example. This parameter enables you to specify up to three searchable contexts used to locate the user when the user is trying to authenticate using the directory. "@directory. This information is for viewing only. Directory User Contexts enable you to specify directory user containers that are automatically searched when an iLO 2 login is attempted." Active Directory allows an additional search context format. The enclosure name is used to logically group together the server blades that compose a single enclosure. The bay number is used to assist in physically identifying the faulty server blade or other error conditions. LOM object password confirm Directory user context 1. directory user context 2. Provided by rack The ProLiant BL p-Class enclosure can support one to eight server blades. "@hostname" for example. When changed.o=corp" to login to iLO 2 using just "manager. "ou=lights out devices. LOM Object Distinguished Names are limited to 256 characters.

The blade serial number identifies the serial number for the server blade product. these events can be logged to the IML. then select Facility Provides 48V. As the server blade receives alerts. If the facility can provide 48 V DC power directly. virtual media (floppy and CD-ROM). then the server blade automatically powers on and begins the normal server booting process. The server blade enclosure can be installed in a rack by using one of two configurations: • The server blade power supplies can be used to convert normal AC facility power to 48 V DC to power the rack. iLO 2 parameters 140 . If the power is available. select the power source as Rack Provides Power. NOTE: It is essential that proper power sizing requirements be performed to ensure sufficient power for all the server blades and other components of the rack. without the need for the provided power supplies. enclosure. and power supply to communicate power requirements to ensure proper power consumption without risking power failures. Enclosure serial number Blade serial number Power source Provided by rack Provided by blade server Rack provides power • Enable automatic power on On Each server blade can be configured to automatically power on when inserted into the enclosure. This setting enables each server blade. Enable rack alert logging (IML) On iLO Advanced Pack License Key The iLO 2 Advanced Pack License Key option is used to enable the iLO 2 Advanced Features including Graphical Remote Console. Enter the 25character key in this field to enable the features.Parameter Rack serial number Default value Provided by rack Definition The rack serial number identifies the components in the rack as a logical grouping. Depending on the Power Source setting. and directory support . Switching components (server blade enclosure or power supplies) alters the rack serial number. the server blade communicates with the rack to determine if enough power is available to power on. Additional IML viewing tools are available to allow viewing from the installed operating system on the server blade. You can view these events by using the iLO 2 System Status—IML tab. Each server blade will not be required to communicate with the infrastructure for power when powering on or off. The serial number is determined during power-up of the various components to create a unique rack serial number. The enclosure serial number identifies the particular server blade enclosure in which a server blade resides. In this configuration.

..hp.. calls may be recorded or monitored............. refer to the HP website (http://www................hp......Technical support In this section HP contact information...... 141 Before you contact HP...........hp...html). For more information about Care Packs.... To contact HP by phone: • • For HP technical support: • Call 1-800-HP-INVENT (1-800-474-6836). call 1-800-633-3600................ see the Contact HP worldwide (in English) webpage (http://welcome........html)..........html). 7 days a week.hp................ for contact options see the Contact HP United States webpage (http://welcome.... 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 Applicable error messages Add-on boards or hardware Third-party hardware or software Operating system type and revision level Technical support 141 .... If you have purchased a Care Pack (service upgrade).............. In the United States....... In other locations............ For continuous quality improvement....... This service is available 24 hours a day........................ • In other locations....com).com/country/us/en/contact_us...com/country/us/en/wwcontact...................................hp................. 141 HP contact information For the name of the nearest HP authorized reseller: • • In the United States. see the Contact HP worldwide (in English) webpage (http://welcome...com/country/us/en/wwcontact.................. see the HP US service locator webpage (http://www..com/service_locator)...

Acronyms and abbreviations ACPI Advanced Configuration and Power Interface ARP Address Resolution Protocol ASCII American Standard Code for Information Interchange ASM Advanced Server Management ASR Automatic Server Recovery BMC base management controller CA certificate authority CGI Common Gateway Interface CLI Command Line Interface CLP command line protocol CR Certificate Request DAV Distributed Authoring and Versioning Acronyms and abbreviations 142 .

DDNS Dynamic Domain Name System DHCP Dynamic Host Configuration Protocol DLL dynamic link library DNS domain name system DSA Digital Signature Algorithm EMS Emergency Management Services EULA end user license agreement FEH fatal exception handler FSMO Flexible Single-Master Operation GUI graphical user interface HB heartbeat HPONCFG HP Lights-Out Online Configuration utility HPQLOMGC HP Lights-Out Migration Command Line ICMP Internet Control Message Protocol Acronyms and abbreviations 143 .

IIS Internet Information Services iLO Integrated Lights-Out IML Integrated Management Log IP Internet Protocol IPMI Intelligent Platform Management Interface ISIP Enclosure Bay Static IP JVM Java Virtual Machine KCS Keyboard Controller Style LAN local-area network LDAP Lightweight Directory Access Protocol LED light-emitting diode LOM Lights-Out Management LSB least significant bit MAC medium access control Acronyms and abbreviations 144 .

MLA Master License Agreement MMC Microsoft® Management Console MP Multilink Point-to-Point Protocol MTU maximum transmission unit NIC network interface controller NMI non-maskable interrupt NVRAM non-volatile memory PERL Practical Extraction and Report Language PKCS Public-Key Cryptography Standards POST Power-On Self Test PSP ProLiant Support Pack RAS remote access service RBSU ROM-Based Setup Utility RDP Remote Desktop Protocol Acronyms and abbreviations 145 .

and Adelman public encryption key RSM Remote Server Management SLES SUSE LINUX Enterprise Server SMASH System Management Architecture for Server Hardware SMS System Management Server SNMP Simple Network Management Protocol SSH Secure Shell SSL Secure Sockets Layer TCP Transmission Control Protocol UART universal asynchronous receiver-transmitter Acronyms and abbreviations 146 . Shamir.RIB Remote Insight Board RIBCL Remote Insight Board Command Language RILOE Remote Insight Lights-Out Edition RILOE II Remote Insight Lights-Out Edition II RSA Rivest.

UID unit identification USB universal serial bus VM Virtual Machine VPN virtual private networking WINS Windows® Internet Naming Service XML extensible markup language Acronyms and abbreviations 147 .

iLO 2 commands 15 CLP. eventlog commands 25 CLP. CLP 25 eventlog commands. 68. 60. license commands 18 CLP. boot commands 26 CLP. 143 dynamic link library (DLL) 56. RIBCL 66 dedicated NIC. settings 97 CERTIFICATE_SIGNING_REQUEST 97 CGI helper scripts 52 CGI. CLP 16 embedded health settings. miscellaneous commands 29 CLP. 79. escape commands 11 CLP. using 9 CLP. base commands 11 CLP. 47. capturing 61 configuration. 57. parameters 138 directory settings. specific commands 12 CLP. RIBCL 105 blade information 25 boot commands 26 boot commands. 80. RIBCL 101. RIBCL 121. SNMP settings 18 CLP. 131 authorized reseller 141 Automatic Server Recovery (ASR) 142 CLP. 122 configuration procedures 59. start and reset commands 23 CLP. setting a configuration 61 contacting HP 141 CPQLOCFG. network commands 13 CLP. batch processing 44 CPQLOCFG. blade commands 25 CLP. directory settings 19 CLP.EXE. 109 eventlog commands. obtaining complete configuration 59 configuration. 143 E EJECT_VIRTUAL_MEDIA 94 embedded health settings. virtual media commands 20 COLD_BOOT_SERVER 121. 103 domain name system (DNS) 44. RIBCL 113 enclosure. 104 Dynamic Host Configuration Protocol (DHCP) 59. IP settings 108.EXE. 71 DELETE_USER 70 DIR_INFO command block 101 Directory Services 138 directory settings 138 directory settings. CLP 19 directory settings. syntax errors 40 B BL p-Class blade parameters 139 blade commands. user commands 12 CLP. obtaining specific information 60 configuration. firmware updates 24 CLP. 80. software components 52 CLEAR_EVENTLOG 79 CLI. 61 configuration utilities 56 configuration. re-enabling 128 DELETE_CURRENT_USER 70. 79. 79 examples. 59. RIBCL 65 Index 148 . parameters 44 CPQLOCFG. multi-user support 9 CLP. CLP 26 boot commands.EXE. 59.Index A ADD_USER 58. CLP 25 blade commands. LED commands 27 CLP. connetion options 9 CLP. embbed health settings 16 CLP. commands 9 CLP. system target and properties settings 27 D data types 65 data types. 69 administration 41. 122 C certificate. RIBCL 77.EXE. restoring 62 configuration. runtime errors 40 CPQLOCFG.

92 HP Lights-Out Migration Command Line (HPQLOMGC) 126. 60. application launch 43 HP SIM. 34 G GET_ALL_USERS 74 GET_ALL_USERS_INFO 75 GET_DIAGPORT_SETTINGS 106. 102 GET_EMBEDDED_HEALTH 113 GET_ENCLOSURE_IP_SETTINGS 108 GET_EVENT_LOG 77. 125 GET_USER 71 GET_VM_STATUS 94.0 8 features. task creation 42 M management port 128 MOD_BLADE_RACK 111. F-key codes 34 LOGIN command block 67 H HOLD_PWR_BTN 121 HOTKEY_CONFIG 91. RIBCL 76 iLO 2 status parameters 130 iLO ports 128 iLO settings 15. using 41 HP Technical Support 141 HPONCFG (HP Lights-Out Online Configuration) 56 HPONCFG. custom command 42 HP SIM. 112 MOD_DIAGPORT_SETTINGS 107. CLP 24 firmware update. 85 GET_HOST_POWER_REG_INFO 117. 61.F features. using 126 I IIS. 118 GET_HOST_POWER_SAVER_STATUS 116 GET_HOST_POWER_STATUS 116. 91 GET_GLOBAL_SETTINGS 84. IPMI 2. customized list 41 HP SIM. CLP 15 iLO 2 settings. 108 Index 149 . 59 HPONCFG. scripted media 53 iLO 2 port. integration 36 HP SIM. VT100 31 L LED commands. 95 GET_VPB_CABLE_STATUS 125 global settings 132 global settings parameters 132 guidelines. RIBCL 65 HP SIM. RIBCL 92 license parameters 140 Lights-Out Configuration Utility (CPQLOCFG. enclosure 108. SSH 35 firmware update. 78 GET_FIRMWARE_VERSION 90. PuTTY 37 INSERT_VIRTUAL_MEDIA 93. 93 license commands.EXE) 41 Linux. 62 HPONCFG. requirements 56 HPONCFG. 119 GET_NETWORK_SETTINGS 79 GET_POWER_READINGS 115 GET_RACK_SETTINGS 106 GET_SERVER_AUTO_PWR 123 GET_SNMP_IM_SETTINGS 88 GET_TOPOLOGY 110 GET_TWOFACTOR_SETTINGS 98 GET_UID_STATUS 124. CLP 27 LICENSE 92. new 7 features. CLP 18 license commands. iLO 2 configuration examples 59. 127 ILO_CONFIG 127 IMPORT_CERTIFICATE 97. parameters 58 HPONCFG. grouping LOM devices 42 HP SIM. Linux 57. installation 57 HPONCFG. using 57. 143 HP ProLiant Essentials Rapid Deployment Pack 7 HP SIM parameters 137 HP SIM. 107 GET_DIR_CONFIG 101. commands 58 HPONCFG. re-enabling 128 iLO 2 settings. 98 importing SSH keys. variable substitution 61 HPQLOMGC. RIBCL 90 F-keys 33. 59 HPONCFG. 94 Intelligent Platform Management Interface (IPMI) 8 Internet Information Services Manager 53 introduction 7 IP settings. 109 K key map.

59. 65 Secure Shell (SSH) 35 Secure Sockets Layer (SSL) 47. 89 SSH key authorization 36 SSH key authorization. XML enhancements 46 phone numbers 141 PuTTY. RIBCL. 90 MOD_TWOFACTOR_SETTINGS 99. CLP 18 SNMP settings. 101 MOD_USER 68. 120. perl 46 scripting. 121 response definition. 48. CLP 9 overview. HPONCFG 56 overview. SSH 35 overview.EXE 40 overview. RIBCL 66 support 141 supported key sequences 31 supported operating systems 56 system status 130 system target information. Perl scripting 46 overview. RIBCL 76. 77 RESET_SERVER 120. features 35 SSH. CLP 27 system target information. CPQLOCFG. RIBCL 65 overview. RIBCL 79. sending XML scripts 48 Perl. RIBCL 88. importing 37 SSH. virtual media scripting 50 P Perl. 105 MOD_ENCLOSURE_IP_SETTINGS 109. 122 string. RIBCL. guide 7 overview. telnet 30 overview. RIBCL. RIBCL. 110 MOD_GLOBAL_SETTINGS 85. XML 46 scripting interface. scripted 46 shared network port. 123 SERVER_INFO command block 112 SET_HOST_POWER 117.MOD_DIR_CONFIG 103. 97 setup. using 36 R RACK_INFO command block 105 Remote Insight Board Command Language (RIBCL) 65 RESET_RIB 76. RIBCL. connection 36 SSH. overview 35 SSH. RIBCL 66 RIB_INFO command block 76 RIBCL command block 67 Index 150 . 86. 57. enabling 128 shared network port. RIBCL. 104. Lights-Out Configuration Utility 40 overview. tool definition files 37 SSH keys. 120 SET_VM_STATUS 95. 84 MOD_SNMP_IM_SETTINGS 89. 82. RIBCL. features 128 shared ports 128 SNMP parameters 137 SNMP settings. 48. 56. IPMI 8 overview. opening 47 start and reset commands. RIBCL. data types 66 DIR_INFO commands 101 examples 65 LOGIN command 67 RACK_INFO commands 105 response definitions 66 RIB_INFO commands 76 SERVER_INFO commands 112 string 66 USER_INFO commands 68 S script body. 100. RIBCL 112 O online configuration untility 56 OpenSSH. using 46 Perl. CLP 23 start and reset commands. 121. RIBCL. using 36 operating systems supported 56 operational overview 65 overview. 88 MOD_NETWORK_SETTINGS 59. using 36 SSL connection. SSL connection 47 Perl. 80. 96. 58. virtual media 50 scripts 46. 146 server identification 131 server status 131 server status parameters 131 SERVER_AUTO_PWR 122. CLP 13 network settings. 72. 80 RIBCL. importing SSH keys 37 PuTTY. 73 Mxagentoconfig 37 N network settings parameters 135 network settings. 47.

94. 34 W WARM_BOOT_SERVER 122 X XML (Extensible Markup Language) 46. 147 XML header 48. CGI helper 52 virtual media scripting. security 31 telnet. key sequences 31 telnet. F-key codes 33. web server requirements 50 VT100 key map 31 VT100. adding 65 user administration parameters 131 user settings. using 30 topology. HPONCFG 61 virtual media commands. 65 Index 151 . 95 virtual media image files 52 virtual media scripting. CLP 12 user settings. unauthenticated 40 XML. using 50 virtual media scripting. IIS requirements 53 virtual media scripting. 99 U UID_CONTROL 124 UPDATE_RIB_FIRMWARE 90 user account. Linux 51 virtual media scripting. 66. RIBCL 93.Systems Insight Manager 42 T technical support 141 telephone numbers 141 telnet 30 telnet. 66 XML query. RIBCL 68 USER_INFO command block 68 V variable substitution. CLP 20 virtual media commands. command set 30 telnet. settings 98. RIBCL commands 110 two-factor authentication. general guidelines 46.

Sign up to vote on this title
UsefulNot useful