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 145
MOD_USER
The MOD_USER command is used to modify an existing local user’s information. You are not required to
enter any of the fields except for the first one, which specifies which user to modify. If any parameter does
not need to be modified, you should omit it. MOD_USER must be displayed within a USER_INFO
parameter, and USER_INFO must be in write mode. The user login name used to gain access cannot be
modified.
Example:
<RIBCL VERSION="2.0">
<LOGIN USER_LOGIN="adminname" PASSWORD="password">
<USER_INFO MODE="write">
<MOD_USER USER_LOGIN="loginname">
<USER_NAME value="username"/>
<PASSWORD value="password"/>
<ADMIN_PRIV value="No"/>
<LOGIN_PRIV value="Yes"/>
<REMOTE_CONS_PRIV value="Yes"/>
<RESET_SERVER_PRIV value="No"/>
<CONFIG_RILO_PRIV value="Yes"/>
<VIRTUAL_MEDIA_PRIV value="No"/>
<CLIENT_IP value="255.255.255.255"/>
</MOD_USER>
</USER_INFO>
</LOGIN>
</RIBCL>
MOD_USER Parameters
USER_LOGIN is the name that the user types to log in to the RILOE II. The USER_LOGIN parameter has a
maximum length of 40 characters, can be an ASCII string containing any combination of printable
characters, and is case sensitive. The USER_LOGIN parameter must never be blank.
NOTE: If the following parameters are not specified, then the parameter value for the specified user is not
changed.
USER_NAME is the actual name of the user. The USER_NAME parameter has a maximum length of 40
characters and can be any ASCII string containing printable characters, including white spaces. This
string is used for display only and must never be blank.
PASSWORD is the password that will be associated with the user. This parameter has a minimum length
of 8 characters, a maximum length of 40 characters, and is an ASCII string that may contain any
combination of printable characters. The PASSWORD parameter cannot contain both single and double
quote characters. This parameter is case sensitive and must never be blank.
ADMIN_PRIV is a Boolean parameter that allows the user to administer user accounts. The user can
modify their account settings, modify other user account settings, add users, and delete users. Leaving out
this parameter prevents the user from adding, deleting, or configuring accounts.
LOGIN_PRIV is a Boolean parameter that allows the user to log in to the RILOE II and use resources such
as Web pages. Marking this parameter with a "No" value or leaving out this parameter effectively
disables the account without deleting it.