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 47
•
If the Virtual Floppy capability is enabled, the floppy drive normally cannot be accessed from the
client operating system.
• If the Virtual CD-ROM capability is enabled, the CD-ROM drive cannot be accessed from the client
operating system.
Under certain conditions, you can access the Virtual Floppy drive from the client operating system while it
is connected. However, it is important that access to the Virtual Floppy drive from the client operating
system not be attempted while it is connected as a virtual media device. Doing so could cause data loss
on the floppy drive. Always disconnect virtual media before trying to access it from the client operating
system.
You can access virtual media on a host server from a client through a graphical interface using a Java™
applet and through a script interface using an XML engine.
To access RILOE II Virtual Media devices using the graphical interface, select Virtual Media on the Virtual
Devices tab. An applet loads in support of the Virtual Floppy or Virtual CD-ROM device.
RILOE II Virtual Floppy
RILOE II Virtual Floppy disk is available at server boot time for all operating systems. Booting from RILOE II
Virtual Floppy enables you to upgrade the host system ROM, deploy an operating system from network
drives, and perform disaster recovery of failed operating systems, among other tasks.
If the host server operating system supports USB mass storage devices, then RILOE II Virtual Floppy is also
available after the host server operating system loads. You can use RILOE II Virtual Floppy when the host
server operating system is running to upgrade device drivers, create an emergency repair diskette, and
perform other tasks. Having the Virtual Floppy available when the server is running can be especially
useful if you must diagnose and repair a problem with the NIC driver.
The Virtual Floppy can be the physical floppy drive on which you are running the web browser, or an
image file stored on your local hard drive or network drive.
NOTE: For best performance use image files. HP recommends using local image files stored either on the
hard drive of your client PC or on a network drive accessible through a high-speed network link.
To use a physical floppy in your client PC:
1. Select Local Media Drive.
2. Select the drive letter of the desired local floppy or USB key drive on your client PC from the
dropdown menu. To ensure the source diskette or image file is not modified during use, select the
Force read-only access option.
3. Click Connect.