User Guide
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 140
This tag name indicates that the RILOE II 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 RILOE
II.
• STATUS
This parameter contains an error number. The number 0x0000 indicates that there is no error.
• MSG
This element contains a message describing the error that happened. If no error occurred, the
message No error appears.
RIBCL
This command is used to start and end an RIBCL session. You can use it only once to start an RIBCL
session, and it must be the first command to display in the script. The RIBCL tags are required to mark the
beginning and the end of the RIBCL document.
Example:
<RIBCL VERSION="2.0">
</RIBCL>
RIBCL parameters
VERSION is a string that indicates the version of the RIBCL that the client application is expecting to use.
The VERSION string is compared to the version of the RIBCL that is expected, and an error is returned if
the string and the version do not match. The preferred value for the VERSION parameter is "2.0." The
VERSION parameter is no longer checked for an exact match; however, this parameter can never be
blank.
RIBCL runtime errors
The possible RIBCL error messages include:
Version must not be blank.
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 specified user must have a valid account on the
respective RILOE II to execute RIBCL commands. The user's privileges are checked against the required
privilege for a particular command, and an error is returned if the privilege level does not match.
Example:
<LOGIN USER_LOGIN="username" PASSWORD="password">
</LOGIN>
Alternatively, the CPQLOCFG utility can specify the login information as parameters on its command line:
cpqlocfg -u <username> -p <password>
When using this format, the utility returns an Overriding credentials warning message but still
shows the error log message entry as Login name must not be blank.
LOGIN parameters
USER_LOGIN is the login name of the user account. This parameter is case sensitive and must never be
blank.
PASSWORD is the password associated with the user. This parameter is case sensitive and can be a
combination of any printable characters.