Shared Remote Console - HP AB500A - Integrated Lights-Out Advanced Technology Brief

The iLO 2 processor stores captured video data in an internal buffer area for boot sequences and for
ASR-2 and OS faults. With additional configuration, iLO 2 can export the captured data to an
external file after the buffer fills. The external file is stored on a web server on the network. The iLO 2
processor continues to export captured files to the specified web server every time there is a reboot or
an OS failure, as long as space is available. These files, each typically 2- to 3-MB, include a time
stamp and an indicator of which type of data they contain. If administrators manually run the capture
function, the data is stored on the client machine. Files created in this manner can be of any size.
Administrators can view the exported video capture files using the Integrated Remote Console
application as well as a stand-alone tool for Windows called the HP iLO Video Player available for
download from www.hp.com/support/ilo2.

Shared remote console

iLO 2 supports sharing a remote console session with up to four users, including the session leader.
The administrator who initiates a remote console session connects to the host server normally and is
designated the session leader. When another administrator tries to connect to the iLO 2 processor in
a second remote console session, the iLO 2 processor transmits the IP address of the session leader
computer back to the new client session. Thus, subsequent shared remote consoles become satellite
clients in a peer-to-peer configuration, as illustrated in Figure 4.
Figure 4. This diagram represents a host server and a remote server console session. The first user in a shared
remote console session becomes the session leader, while up to three others are satellite clients in a peer-to-peer
configuration.
For each satellite client request, a pop-up window appears on the session leader's desktop,
identifying the requester's user name and DNS name (if available) or IP address. All console sessions
are encrypted through client authentication first, and then the session leader decides whether or not to
allow the new connection to the remote console session. The session leader controls the remote
console session. All satellite client sessions terminate when the session leader terminates the session.
The shared remote console allows administrators at multiple locations to collaborate on
troubleshooting or maintaining the remote server for greater IT efficiency and system availability.
10