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 151
MOD_NETWORK_SETTINGS
The MOD_NETWORK_SETTINGS command modifies certain network settings. This command is only valid
inside a RIB_INFO block. The logged-in user must have the configure RILOE privilege, and the mode of
the containing RIB_INFO block must be "write." All of these elements are optional and may be left out. If
an element is left out, then the current setting is preserved.
Example:
<RIBCL VERSION="2.0">
<LOGIN USER_LOGIN="adminname" PASSWORD="password">
<RIB_INFO MODE="write">
<MOD_NETWORK_SETTINGS>
<SPEED_AUTOSELECT value="No"/>
<FULL_DUPLEX value="Yes"/>
<NIC_SPEED value="100"/>
<DHCP_ENABLE value="Yes"/>
<IP_ADDRESS value="255.255.255.255"/>
<SUBNET_MASK value="255.255.0.0"/>
<GATEWAY_IP_ADDRESS value="255.255.255.255"/>
<DNS_NAME value="demorib.internal.net"/>
<DOMAIN_NAME value="internal.net"/>
<DHCP_GATEWAY value="No"/>
<DHCP_DNS_SERVER value="No"/>
<DHCP_STATIC_ROUTE value="No"/>
<REG_WINS_SERVER value="No"/>
<PRIM_DNS_SERVER value="255.255.255.255"/>
<SEC_DNS_SERVER value="255.255.255.255"/>
<STATIC_ROUTE_1 DEST="255.255.0.0" GATEWAY="255.0.0.0"/>
<STATIC_ROUTE_2 DEST="255.255.0.0" GATEWAY="255.0.0.0"/>
<WEB_AGENT_IP_ADDRESS value="255.255.255.255"/>
</MOD_NETWORK_SETTINGS>
</RIB_INFO>
</LOGIN>
</RIBCL>
MOD_NETWORK_SETTINGS Parameters
SPEED_AUTOSELECT is used to automatically select the transceiver speed. The possible values are "Yes"
or "No." It is case insensitive.
FULL_DUPLEX is used to decide if the RILOE II is to support full-duplex or half-duplex mode. It is only
applicable if SPEED_AUTOSELECT was set to "No." The possible values are "Yes" or "No." It is case
insensitive.
NIC_SPEED is used to set the transceiver speed if SPEED_AUTOSELECT was set to "No." The possible
values are "10" or "100." Any other values will result in a syntax error.
DHCP_ENABLE is used to enable DHCP. The possible values are "Yes" or "No." It is case insensitive.