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
Using the RILOE II 41
The Windows® EMS Console, if enabled, provides the ability to perform EMS in cases where video,
device drivers, or other operating system features have prevented normal operation and normal corrective
actions from being performed.
The Windows® EMS serial port must be enabled through the host system RBSU. The configuration allows
for the enabling or disabling of the EMS port, and the selection of the COM port. The RILOE II system will
automatically detect whether the EMS port is enabled or disabled, and the selection of the COM port.
To obtain the SAC> prompt, typing Enter might be required after connecting through the Virtual Serial
Port console.
For more information on using the EMS features, refer to the Windows® Server 2003 Server
documentation.
Terminal Services pass-through option
Terminal Services is provided by the Microsoft® Windows® operating systems. The RILOE II Terminal
Services pass-through option provides a connection between the Terminal Services server on the host
system and the Terminal Services client on the client system. When the Terminal Services pass-through
option is enabled, RILOE II firmware sets up a socket, listening by default on port 3389. All data received
from the Terminal Services on this port is forwarded to the server and all data it receives from the server is
forwarded back to the socket. The firmware assumes anything received on this port is in an RDP packet.
RDP packets are exchanged between the RILOE II firmware and the server's Terminal Services (RDP) server
through the localhost address on the server. A service is provided to facilitate communications between
the RILOE II firmware and the RDP server, such that the RDP server believes that an external RDP
connection has been established. For more information on RDP service, refer to the "Windows® RDP Pass-
Through service (on page 42)" section.
A Terminal Services session provides a performance-enhanced view of the host system console. When the
operating system is unavailable (or the Terminal Services server or client is unavailable), the traditional
RILOE II remote console provides the view of the host system console. For more information on Remote
Console and Terminal Services, refer to the "Remote Console and Terminal Services clients (on page 44)"
section.
To configure the Terminal Services pass-through option, refer to "Terminal Services Client requirements (on
page 41)" and "Terminal Services Pass Through installation ("Terminal Services pass-through installation"
on page 42)."
Terminal Services Client requirements
The Terminal Services client is available on Microsoft® Windows® client machines running:
• Windows® 2000
Microsoft® Windows® 2000 servers require the installation of Microsoft® .NET Framework to
support the use of Terminal Services. After .NET Framework is installed, the Terminal Services client
must be installed from diskettes created by the Terminal Services server. Consult your Windows®
operating guides or help files for instructions. When installing the Terminal Services client on
Windows® 2000, use the default installation location. The Terminal Services client in Windows®
2000 generates a dialog box asking for which target Terminal Services server to use.
• Windows® Server 2003
On Windows® Server 2003 servers, the Terminal Services client and RDP connection is built in. The
client is an integral part of the operating system and is activated using Remote Desktop sharing. To
activate desktop sharing allow, select My Computer>Properties>Remote>Remote Desktop.
The Terminal Services client in Windows® Server 2003 provides command line options and
seamless launches from the Remote Console applet.
• Windows® XP










