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
Troubleshooting the RILOE II 186
•
Unauthorized, couldn't find RIB object
• Unauthorized, no readable roles
• Unable to read restrictions on object
• Time Restriction Not Satisfied
• IP Restriction Not Satisfied
• Unauthorized
Directory Server connect failed
The RILOE II was not able to connect to the LDAP server. Be sure that the Directory Server Address on the
RILOE II Directory Settings Screen is correct, and that the port number corresponds to the LDAP SSL port
number used by that directory server, usually port 636. If the directory server address is a DNS name, be
sure that the DNS server is properly configured on the RILOE II Network Setting Screen, and that the DNS
name of the directory server resolves to the appropriate address using "nslookup" or a similar tool.
Many SSL problems are reported with this error; be sure your directory server is properly configured for
LDAP SSL connections. Refer to the installation prerequisites for Active Directory ("Active Directory
installation prerequisites" on page 83) or eDirectory for more information on testing LDAP SSL
configurations.
Invalid credentials
The directory server has denied the authentication request. If configured, check the searchable contexts to
be sure the user exists in one of those contexts, or try specifying a fully distinguished name. Directory
servers will deny the authentication request if the user account has been disabled, locked out, or is
otherwise prevented from authenticating due to network address or time restrictions placed on the
account.
This error is common on eDirectory when periods are used to separate the name components, or the
components are partially specified. LDAP distinguished name components are separated by commas, not
periods, and must be preceded by cn=, or appropriate naming attribute name.
NOTE: The short form of the login name by itself does not tell the directory which domain you are trying to
access. You must provide the domain name or use the LDAP distinguished name of your account.
Invalid Directory Server address or port
The specified Directory Server address was empty, or the port number was set to 0. Specify the correct
server address or port.
Directory Server timeout
The server did not acknowledge the bind request within a reasonable amount of time, normally 20
seconds. The server may be under heavy load or otherwise unwilling to process the request. Try again
later.
This error can also occur if the Directory Server address and port correspond to a service other than LDAP
SSL.
Unauthorized, couldn't find RILOE II object
An error occurred while trying to read the RILOE II object. Be sure that the distinguished name specified in
the Directory Settings screen matches the location of the object within the directory. The distinguished
name must be a fully distinguished LDAP name.