Accessing the Remote Console

The remote console application, which you access via a web browser, enables you to control your server’s operating system remotely using the screen, mouse, and keyboard, and to redirect local CD and diskette drives as if they were connected directly to the server.

Requirements

A compatible web browser and a minimum of JRE 1.6.0 are required to operate the remote console application. See TABLE 5-1.

Note - You do not need to install any OS-specific drivers or helper applications on client systems to run the remote console application.

Note - To start the remote console successfully, pop-ups must be allowed on the browser. With some browsers you can do this by pressing and holding the Control key when launching the remote console session.

CD and Diskette Redirection Operational Model

When you redirect the local client CD drive or diskette drive to a remote host server, the following rules apply:

In all cases, the CD drive and diskette drive appear to be plugged in to the host.

If you do not redirect them, the host acts as if there is no medium unless there is a CD in the host CD drive. If there is a CD in the host CD drive, the host accesses it normally.

The information in TABLE 5-2 describes different case scenarios in which the remote console application and CD drive and diskette drive redirection operate.

TABLE 5-2 Remote Console Operation With DVD Drive and Diskette Drive

Case

Status

DVD Seen by Host

Diskette Seen by Host

1

Remote console application not started or remote console started but DVD/diskette redirection not started.

DVD device present. No medium indication is sent to the host from the ELOM when the hosts asks.

Diskette device present. No medium indication is sent to the host from the ELOM when the host asks.

2

Remote console application started with no medium present in the drive.

DVD device present. Whenever the host asks, which may be automatic or when you access the device on the host, the remote client sends a status message. In this case since there is no medium, the status is no medium.

Diskette device present. Whenever the host asks (for example, you double-click a drive), the remote client sends a status message. In this case since there is no medium, the status is no medium.

3

Remote console application started with no medium, then medium is inserted.

DVD device present. Whenever the hosts asks (automatic or manual), the remote client sends a status message as medium present and also indicates the medium change.

Remote console application started with medium present, then medium is removed.

Next command from the host gets a status message indicating medium not present.

Next command from the host gets a status message indicating medium not present.

6

Remote console application started with image redirection.

Same as 3.

Same as 3.

7

Remote console application started with image, but redirection is stopped (which is the only way to stop ISO redirection).

Driver knows DVD redirection stopped so it sends a medium absent status on the next host query.

Driver knows DVD redirection stopped so it sends a medium absent status on the next diskette query.

8

Network failure.

The software has a keep alive mechanism. The software detects keep alive failure since there is no communication and closes the socket, assuming the client is unresponsive. Driver sends a no medium status to the host.

The software has a keep alive mechanism. The software detects and unresponsive client, closes the socket, and indicates to the driver that the remote connection went away. Driver sends a no medium status to the host.

9

Client crashes.

Same as 8.

Same as 8.

Starting the Remote Console Application

Use this procedure to start the remote console application from a web browser. You might be presented with a series of questions. In each case, select Run.

Note - Each new ELOM system is delivered with DHCP set as the default. If an IP address is not found within 5 seconds, the system retries three times to find a DHCP server. If it is still unsuccessful, the SP will allow instant web access by defaulting to the IP address 192.168.xxx.xxx. Where xxx.xxx is based upon the last two fields of the SP MAC address.

Note - For systems using Firefox and Mozilla web browsers, the required version of JRE must be at least version 1.6 or later.

The web browser downloads the embedded remote control application automatically, and the Remote Console screen appears.

If the remote console does not appear, it might be blocked by web browser security controls. Reduce security configuration to allow the remote console to appear.

Note - To start the remote console successfully, pop-ups must be allowed on the browser. With some browsers you can do this by pressing and holding the Control key when launching the remote console session.

Setting Parameters for the Remote Console

This section explains how to define the quality of video, the size of the screen, and set hot keys for the remote console application.

To Set Parameters for the Remote Console

1. From the Remote Control submenu, select Hotkey Setup.

The User Profile screen appears. The User Profile screen allows you to set up separate video, KVM, and hot key settings for each user. The subsequent window displays a version of the screen output. This requires a Java Webstart application to be launched.

a. The first time this application is launched you must respond to accept various security questions before the application is installed and operates correctly.

b. Right-click to display the remote console as a full screen.

By default, the remote console will synchronize both mouse cursors, and display only one mouse cursor within the remote console screen.

When the mouse cursor leaves the screen, the local cursor takes over and the other mouse cursor remains in the remote console screen.

You can enable user modes in the setup of the web GUI or in the remote console screen.

2. When the login is successful, the remote console screen appears.

The remote console application starts with the video and keyboard enabled by default. In most cases, you need only enable the mouse redirection. You can now use the remote console application to start your server’s operating system.

The Control Mode section of the Hotkey Setup screen enables mouse redirection.

3. Select Hardware Cursor to enable a variety of cursor movements.

Note - For the mouse to work correctly, you might have to change the mouse mode. Click the double mouse cursor on the navigation bar to toggle between local and remote mouse cursor movement. Keyboard redirection is selected by default.

FIGURE 5-1 Keyboard, Video, and Mouse Selections

4. You can click Submit to enable your options after each choice to observe the consequences, or continue directly to Step 5.

5. When you have completed your selections, click Submit to enable your options.

To Redirect Storage Devices

Use the following procedure to enable a storage device attached to your local workstation or laptop to serve as a storage device for a server. You can use this option to install software from a local CD/DVD drive to multiple remote servers.

You can also redirect a CD image file or a diskette image file stored on your hard drive.

Note - You cannot select two CD-ROM devices or two diskette devices. For example, you cannot select CD-ROM and CD-ROM image. Use the web browser to navigate to the corresponding file, then click Submit.

Redirection and Mount Workarounds for RHEL

The procedures in this section describe redirection and mount workarounds for some versions of RHEL. The procedures included here are: