User's Manual
Table Of Contents
- HP Remote Insight Lights-Out Edition II User Guide
- Notice
- Contents
- Operational overview
- Installing the RILOE II
- Configuring the RILOE II
- Using the RILOE II
- Accessing RILOE II for the first time
- Features of the RILOE II
- Managing the user and configuration settings of the RILOE II
- Using the Remote Console
- Terminal Services pass-through option
- Using virtual devices
- Resetting the RILOE II to the factory default settings
- Getting help
- Pocket PC access with RILOE II
- RILOE II security
- Systems Insight Manager integration
- Directory services
- Overview of directory integration
- Benefits of directory integration
- How directory integration works
- Advantages and disadvantages of schema-free and HP Extended
- Setup for Schema-free directory integration
- Setting up HP schema directory integration
- Features supported by HP schema directory integration
- Setting up directory services
- Directory services support
- Schema required software
- Schema installer
- Management snap-in installer
- Directory services for Active Directory
- Active Directory Lights-Out management
- Directory services for eDirectory
- User login using directory services
- Directory settings
- Directory-enabled remote management
- Scripting, command line, and utility options
- Overview of the Lights-Out DOS utility
- Lights-Out directories migration utilities
- Compatibility
- Pre-migration checklist
- HP Lights-Out directory package
- HPQLOMIG operation
- Finding management processors
- Upgrading firmware on management processors
- Selecting a directory access method
- Naming management processors
- Configuring directories when HP Extended schema is selected
- Configuring directories when schema-free integration is sele
- Setting up management processors for directories
- HPQLOMGC operation
- Lights-Out Configuration Utility
- Using Perl with the XML scripting interface
- HPONCFG
- Remote Insight command language
- RIBCL sample scripts
- RIBCL general guidelines
- XML header
- Data types
- Response definitions
- RIBCL
- LOGIN
- USER_INFO
- ADD_USER
- DELETE_USER
- GET_USER
- MOD_USER
- GET_ALL_USERS
- GET_ALL_USER_INFO
- RIB_INFO
- RESET_RIB
- GET_NETWORK_SETTINGS
- MOD_NETWORK_SETTINGS
- GET_GLOBAL_SETTINGS
- MOD_GLOBAL_SETTINGS
- CLEAR_EVENTLOG
- UPDATE_RIB_FIRMWARE
- GET_FW_VERSION
- HOTKEY_CONFIG
- DIR_INFO
- GET_DIR_CONFIG
- MOD_DIR_CONFIG
- SERVER_INFO
- RESET_SERVER
- INSERT_VIRTUAL_FLOPPY
- EJECT_VIRTUAL_FLOPPY
- COPY_VIRTUAL_FLOPPY
- GET_VF_STATUS
- SET_VF_STATUS
- GET_HOST_POWER_STATUS
- SET_HOST_POWER
- GET_VPB_CABLE_STATUS
- GET_ALL_CABLES_STATUS
- GET_TWOFACTOR_SETTINGS
- MOD_TWOFACTOR_SETTINGS
- Troubleshooting the RILOE II
- Supported client operating systems and browsers
- Supported hardware and software
- Server PCI Slot and Cable Matrix
- Network connection problems
- Alert and trap problems
- NetWare initialization errors
- Miscellaneous problems
- Accessing System Partition Utilities
- Inability to reboot the server
- Inability to upgrade the RILOE II firmware
- Incorrect time or date of entries in the event log
- Interpreting LED indicators
- Invalid Source IP address
- Login name and password problems
- Remote Console mouse control issue
- Resetting the RILOE II to Factory Default Settings
- Virtual Floppy media applet is unresponsive
- Video Problems
- Troubleshooting the host server
- Directory Services errors
- Directory Services schema
- Technical support
- Regulatory compliance notices
- Acronyms and abbreviations
- Index

Scripting, command line, and utility options 129
Do not use this switch if launching from Systems Insight Manager.
NOTE: The output values might need to be modified to match the RIBCL syntax.
NOTE: The -L parameter cannot designate an output log file. A default log file named with the DNS name
or the IP address is created in the same directory where CPQLOCFG is launched.
• -V is the optional switch that turns on the verbose message return. The resulting log file contains all
commands sent to the Remote Insight board, all responses from the Remote Insight board, and any
errors. By default, only errors and responses from GET commands are logged without this switch.
See the "Remote Insight Command Language (on page 138)" section for information on the syntax of the
XML data files. Sample XML scripts are available on the HP website (http://www.hp.com/servers/lights-
out) in the Best Practices section.
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. Primarily, administrators use tools like the cpqlocfg.exe to assist deployment
efforts. Administrators using a non-Windows® client can use Perl scripts to send XML scripts to the Lights-
Out devices. Administrators can also use Perl to perform more complex tasks than cpqlocfg.exe can
perform.
This section discusses how to use Perl scripting in conjunction with the Lights-Out XML scripting language.
Perl scripts require a valid user ID and password with appropriate privileges. Sample XML scripts for
Lights-Out devices and a sample Perl script are available on the HP website
(http://www.hp.com/servers/lights-out
) in the Best Practices section.
XML enhancements
Previous versions of RILOE II firmware do not return properly formatted XML syntax. If the RILOE II
firmware determines the client utility being used does not support the return of properly formatted XML
syntax, the following message appears:
<INFORM>Scripting utility should be updated to the latest
version.</INFORM>
This message informs the customer to update to a later version of the cpqlocfg scripting utility. The latest
version of cpqlocfg.exe is currently 2.21.
For customers using a utility other than cpqlocfg.exe, such as Perl scripts, the following steps can help
ensure the RILOE II firmware returns properly formatted XML. Assuming the version of firmware is 1.20,
<LOCFG version="2.21"> should be incorporated into the script sent to RILOE II. This tag can be
placed in either the Perl script or the XML script. Placement of this tag is important. If placing this tag in
the Perl script, the tag should be sent after <?xml version="1.0"?> and before the XML script is
sent. If placing the tag in the XML script, the tag should be placed before <RIBCL version="2.0">. If
you are using the Perl script provided by HP, then the bold line in the following example can be added to
return properly formatted XML syntax.
• Perl script modification
…
# Open the SSL connection and the input file
my $client = new IO::Socket::SSL->new(PeerAddr => $host);
open(F, "<$file") || die "Can't open $file\n";
# Send the XML header and begin processing the file
print $client '<?xml version="1.0"?>' . "\r\n";
#Send tag to RILOE II firmware to insure properly formatted XML is
returned.










