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 123
IMPORTANT: Installing directory support for any management processor requires downloading the HP
Smart Component. Refer to the "Pre-migration checklist (on page 113)" and the "HP Lights-Out directory
package" sections for additional information. Extending the schema must be completed by a Schema
Administrator.
To implement directory support on a few management processors.
1. Use Systems Insight Manager to locate all of the management processors in the network.
2. Execute the HPQLOMGC utility.
3. Invoke the XML file to migrate the management processor.
HPQLOMGC goes through three phases to complete the migration of a management processor.
1. The firmware version is validated and updated if necessary.
HPQLOMGC determines the type of management processor and the firmware level. If the firmware
does not meet the minimum requirement ("Upgrading firmware on management processors" on page
116), HPQLOMGC upgrades the firmware and resets the management processor. After the
management processor resets, HPQLOMGC begins the next phase.
2. The management processor directory settings are updated.
HPQLOMGC uses the scripting interface to send the directory settings to the management processor.
3. The directory is updated.
HPQLOMGC creates a device object in the directory at the location specified by the user.
HPQLOMGC uses either the object name specified in the XML file or the network name of the
management processor. After the device object is created, the specified role object is then amended
to include the newly created device object.
Launching HPQLOMGC using application launch
Application Launch can be used to create tasks associated with administration of management
processors. For example, the management processors can be discovered using Application Launch and
could be used to automatically configure new management processors as they are added to the network.
To create an Application Launch task:
1. Click Device in the navigation bar on the top left side of the screen.
2. Click Tasks to open the Tasks screen.
3. Click New Control Task. A dropdown menu is displayed.
4. Click Application Launch from the dropdown menu to open the Create/Edit Task screen.
5. Enter the full path and name for the Lights-Out Migration Command Line Utility in the area provided.
For example, if the HPQLOMGC.exe file is in the root directory of the C drive, then the path is:
C:\HPQLOMGC.exe.
6. Enter the parameters in the area provided.
Command line switches enable you to designate items such as the management processor to be
upgraded, the XML file to be used, and where a log file is generated.
-S <network address>—This switch contains the IP address or DNS name of the management
processor. By default, the IP address of the management processor is automatically provided. The
environment variable <DEVICEIPADDRESS0> can also be used to specify a network address.
Use the -S switch to override the default behavior. If present, this switch has precedence over the IP
address environment variable <DEVICEIPADDRESS0>.
-F <filename>—This switch contains the path of the XML file that has the management processor
directory settings and the location of the firmware images. This switch causes an error if an IP
address is not designated.
-A—This switch uses the network name for the name of the device object created in the directory.










