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 48
The connected drive icon and LED changes state to reflect the current status of the Virtual Floppy Drive.
To use an image file:
1. Select Local Image File within the Virtual Floppy section of the Virtual Media applet.
2. Enter the path or file name of the image in the text box, or click Browse to locate the image file
using the Choose Disk Image File dialog. To ensure the source diskette or image file is not modified
during use, select the Force read-only access option.
3. Click Connect.
The connected drive icon and LED changes state to reflect the current status of the Virtual Floppy drive.
When connected, the virtual devices are available to the host server until you close the Virtual Media
applet. When you are finished using the Virtual Floppy, you can either select to disconnect the device
from the host server or close the applet.
NOTE: The Virtual Media applet must remain open in your browser as long as you continue to use a Virtual
Media Device.
RILOE II Virtual Floppy is available to the host server at run time if the operating system on the host server
supports USB floppy drives. See "Operating System USB Support (on page 57)" for information on which
operating systems support USB mass storage at the time of the publication of this manual.
RILOE II Virtual Floppy appears to your operating system just like any other drive. When using RILOE II for
the first time, the host operating system might prompt you to complete a New Hardware Found wizard.
When you are finished using RILOE II Virtual Media and disconnect it, you might receive a warning
message from the host operating system regarding unsafe removal of a device. This warning can be
avoided by using the operating system-provided feature to stop the device before disconnecting it from the
Virtual Media.
Virtual Floppy operating systems notes
• MS-DOS
During boot and during an MS-DOS session, the Virtual Floppy device displays as a standard BIOS
floppy drive. This device will display as drive A. An existing physically attached floppy drive is
obscured and unavailable during this time. You cannot use a physical local floppy drive and the
Virtual Floppy simultaneously.
• Windows® 2000 SP3 or later and Windows® Server 2003
Virtual Floppy drives display automatically after Microsoft® Windows® has recognized the
mounting of the USB device. Use it as you would a locally attached device.
To use Virtual Floppy during a Windows® installation to provide a driver diskette, disable the
integrated diskette drive in the host RBSU which forces the Virtual Floppy to appear as drive A.