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 162
NOTE: When using schema-free directories, the following tags must not be used:
• DIR_OBJECT_DN
• DIR_OBJECT_PASSWORD
MOD_DIR_CONFIG parameters
All of the following parameters are optional. If a parameter is not specified, then the parameter value for
the specified setting is preserved.
DIR_AUTHENTICATION_ENABLED enables or disables directory authentication. The possible values are
"Yes" and "No."
DIR_ENABLE_GRP_ACCT causes RILOE II to use schama-less directory integration. The possible values are
"Yes" and "No."
When using schema-free directory integration, RILOE II supports variable privileges associated with
different directory groups. These groups are contained in the directory, and the corresponding member
RILOE II privileges are stored in RILOE II.
• DIR_GRPACCT1_NAME identifies a group container in the directory, such as Administrators, Users,
or Power Users.
• DIR_GRPACCT1_PRIV numerically identify RILOE II privileges for members of the group. You can mix
and match privileges by including more than one value. These privileges are expressed as a comma
separated list of numbers (1,2,3,4,5) which correlate to:
1. Administer Group Accounts
2. Remote Console Access
3. Virtual Power and Reset
4. Virtual Media
5. Configure RILOE II Settings
NOTE: When using directory integration with schema extension, the following tags must not be used:
• DIR_ENABLE_GRP_ACCT
• DIR_GRPACCT1_NAME
• DIR_GRPACCT1_PRIV
NOTE: When using schema-free directories, the following tags must not be used:
• DIR_OBJECT_DN
• DIR_OBJECT_PASSWORD
DIR_LOCAL_USER_ACCT enables or disables local user accounts. The possible values are "Yes" and
"No."
DIR_SERVER_ADDRESS specifies the location of the directory server. The directory server location is
specified as an IP address or DNS name.
DIR_SERVER_PORT specifies the port number used to connect to the directory server. This value is
obtained from the directory administrator. The secure LDAP port is 636, but the directory server can be
configured for a different port number.
DIR_OBJECT_DN specifies the unique name of RILOE II in the directory server. This value is obtained from
the directory administrator. Distinguished names are limited to 256 characters.
DIR_OBJECT_PASSWORD specifies the password associated with the RILOE II object in the directory
server. Passwords are limited to 39 characters.
DIR_USER_CONTEXT_1, DIR_USER_CONTEXT_2, and DIR_USER_CONTEXT_3 specify searchable
contexts used to locate the user when the user is trying to authenticate using directories. If the user could
not be located using the first path, then the parameters specified in the second and third paths are used.