C H A P T E R 10 - Using The Remote Console Application

C H A P T E R 10

Using The Remote Console Application

This chapter describes how to use the remote console application.

It includes the following sections:

Section 10.1, About the Remote Console Application

Section 10.2, Starting the Remote Console Application From the WebGUI

Section 10.3, Redirecting Keyboard, Video, Mouse, or Storage Devices

10.1 About the Remote Console Application

The remote console application, which is started using the WebGUI, allows 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.

The screen, mouse, and keyboard functionality allows you to use the operating system and other GUI-based programs, instead of restricting you to the command-line-based utilities provided by terminals and emulators.

The ability to redirect CD and diskette drives allows you to download and upload software to and from the server as if you were accessing its own CD and diskette drives.

10.1.1 Installation Requirements

You do not need to install software on the host system (server). The ILOM ships with the remote console application installed.

A compatible web browser and JRE 1.5 are required to operate the remote console application. See TABLE 10-1.

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

TABLE 10-1 Client Installation Requirements
Client OS	Java Runtime Environment Including Java Web Start	Browser(s)
Microsoft Windows XP Pro	JRE 1.5 (Java 5.0)	Internet Explorer 6.0 and later Mozilla 1.7.5 or later Mozilla Firefox 1.0
Red Hat Linux 3.0 and 4.0 Desktop and Workstation Editions	JRE 1.5 (Java 5.0)	Mozilla 1.7.5 or later Mozilla Firefox 1.0
Solaris 9	JRE 1.5 (Java 5.0)	Mozilla 1.7.5
Solaris 10	JRE 1.5 (Java 5.0)	Mozilla 1.7.5
SUSE Linux 9.2	JRE 1.5 (Java 5.0)	Mozilla 1.7.5

Note - To download the Java 1.5 runtime environment, go to http://java.com.

The remote console application uses the following TCP ports:

TABLE 10-2 Remote Console Ports and Interfaces
Port	Interface	Application
443	TCP	HTTPS
5120	TCP	Remote CD
5121	TCP	Remote keyboard and mouse
5123	TCP	Remote diskette
6577	TCP	CURI (API) - TCP and SSL
7578	TCP	Video Data
161	UDP	SNMP V3 Access
3072	UDP	Trap Out (outgoing only)

Note - If the ILOM is configured to use HTTP, it uses TCP port 80.

10.1.2 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 don't redirect them, the host will act 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.

Information in TABLE 10-3 describes different case scenarios in which the remote console application and CD drive and diskette drive redirection operate.

TABLE 10-3 Remote Console Operation With DVD Drive and Diskette Drive
Case	Status	DVD As Seen by Host	Diskette As 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 ILOM whenever the hosts asks.	Diskette device present. No medium indication is sent to the host from the ILOM whenever 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 on 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.	Diskette device present. Whenever the host asks (manual), the remote client sends a status message as medium present and also indicates the medium change.
4	Remote console application started with medium inserted	Same as 3.	Same as 3.
5	Remote console application started with medium present, then medium is removed	Next command from the host will get a status message indicating medium not present.	Next command from the host will get 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 keepalive mechanism. The software will detect keep-alive failure since there is no communication and will close the socket, assuming the client is unresponsive. Driver will send a no medium status to the host.	The software has a keepalive mechanism. The software will detect unresponsive client and close the socket, as well as indicate to the driver that the remote connection went away. Driver will send a no medium status to the host.
9	Client crashes	Same as 8.	Same as 8.

10.1.3 Remote Console Security

Only users with administrator privilege can use the remote console application.

When users with operator privilege select Remote Console => Redirection, a login window prompts them for a user name and password. They must enter the user name and password for an account with administrator privilege to proceed.

Normally, when users with administrator privilege click Remote Console => Redirection, the Launch Redirection page appears.

However, this can be configured. If /SP/services/sso is set to disabled, even users with administrator privilege are prompted to login again. They can log in using the same user name and password, or a different user name and password, as long as it accesses a valid user account with administrator privilege.

To change the /SP/services/sso:

1. Log in to the CLI using an account with administrator privileges.

2. Navigate to /SP/services.

3. Enter the command:

sso state = enabled

to allow users with administrator privileges to start the remote console operation without a login prompt.

sso state = disabled

to require users with administrator privileges to log in again when starting the remote console application

10.2 Starting the Remote Console Application From the WebGUI

Use this procedure to start the remote console application from the WebGUI.

1. Log in to the ILOM as administrator.

2. Select Remote Control => Redirection.

The Launch Redirection page appears.

3. If a login screen appears, enter the user name and password of an account that has administrator privileges. See Section 10.1.3, Remote Console Security for details.

FIGURE 10-1 Launch Redirection Page

Graphic showing a launch redirection screen.

4. If necessary, set the mouse mode.

If you are not changing the mouse mode, skip to Step 5.

Absolute mouse mode - Select this setting for best performance when you are using a Solaris or Microsoft Windows operating system.

Relative mouse mode - Select this setting for best performance when you are using a Linux operating system. Linux currently does not support Absolute mode.

a. Select Remote Control => Mouse Mode Settings.

The Mouse Mode Settings page appears.

Caution - Do not change the mouse mode unless it is necessary, as it causes the ILOM to reset itself.

FIGURE 10-2 Mouse Mode Settings Page

Graphic showing mouse mode settings.

b. Check to see if the mouse mode is set correctly and, if it is, proceed to Step 5.

c. If the mouse mode is set incorrectly, select either Absolute or Relative mouse mode from the drop-down menu.

A confirmation dialog box appears.

d. Click OK in the dialog box.

The ILOM is reset. This process takes about two or three minutes, during which time the ILOM is unavailable.

Note - Do not reboot the host while the ILOM is resetting itself, or the host might become confused about the mouse mode. For best results, change the mouse mode to the desired state prior to booting the host.

e. After the ILOM resets itself, repeat Step 1 and Step 2, then proceed to Step 5.

The new mouse mode is now in effect. The mouse mode setting is stored on the ILOM. Therefore, subsequent connections to the WebGUI will use the new mode.

Note - If you use Relative mouse mode, you might have difficulty getting a redirected mouse out of the remote console window. To regain control of the cursor, type ALT+m

5. Select the 8-bit or 16-bit color option.

Note - For faster performance, select 8-bit color.

6. Click Launch Redirection.

The Redirection page appears.

During this procedure, you might see security warnings. When you are prompted, select Accept, Allow, Yes, or whatever else will tell your security software to enable the connection.

The JavaRConsole message appears.

FIGURE 10-3 JavaRConsole Page

Graphic showing the Java Web start screen.

7. When you see the Login dialog box, type the user name and password.

The default user name is root and the default password is changeme.

FIGURE 10-4 Login Dialog Box

Graphic showing the remote console login screen.

8. Select a bandwidth from the drop-down menu (optional).

Select bandwidth that matches your actual bandwidth.

Note - Setting the bandwidth higher than what is actually available can degrade performance. Sometimes you can improve performance by setting the bandwidth lower.

9. Click OK to launch the remote console application.

When the login is successful, the Remote Console screen appears.

FIGURE 10-5 Remote Console Screen

Graphic showing the remote console login screen.

The Remote Console application starts with the video and keyboard enabled.

Note - You can open multiple Remote Console sessions and use the tabs to switch between them.

10. Choose Devices => Mouse to enable mouse redirection (Optional).

FIGURE 10-6 Mouse and Keyboard Redirection Selected

Graphic showing mouse selected.

You should now be able to use the Remote Console application to start your server's operating system.

Video and keyboard are enabled by default. In most cases, all you need to do is enable the mouse redirection.

For detailed instructions on how to enable and disable I/O and storage devices (CD-ROM and Diskette drives), see Section 10.3, Redirecting Keyboard, Video, Mouse, or Storage Devices.

10.3 Redirecting Keyboard, Video, Mouse, or Storage Devices

The remote console application supports the redirection of the following types of devices:

Video display - the server's video output is automatically displayed on the remote console window.

Keyboard and mouse devices - Standard keyboards, mouse, and other pointing devices.

Keyboard redirection is enabled by default.

Mouse redirection must be enabled manually.

Storage devices - CD/DVD drives or diskette drives.

10.3.1 Redirecting Keyboard and Mouse Devices

Use the following procedure to redirect a server keyboard and mouse device to your local workstation or laptop.

Note - For the mouse to work correctly, you might have to change the mouse mode as well. This is described in Step 4 of the procedure Section 10.2, Starting the Remote Console Application From the WebGUI.

1. Start the remote console application as described in Section 10.2, Starting the Remote Console Application From the WebGUI.

The Remote Console screen appears.

2. Choose Devices => Mouse to enable mouse redirection.

3. If keyboard redirection is disabled, choose Devices => Keyboard to enable it.

Note - Keyboard redirection is selected by default.

FIGURE 10-7 Keyboard and Mouse Selected

Graphic showing mouse selected.

4. Use the Keyboard menu to control keyboard attributes and to send special characters that might not be available on the keyboard in remote console mode.

FIGURE 10-8 Keyboard Menu Options

Graphic showing keyboard options.

Selecting Auto-Keybreak Mode causes the SP to send a key release event automatically. Use this mode when network latency causes the host to act as if keys are being held down.

To simulate a Ctrl+Alt key sequence:

a. Choose Left Alt Key (or Right Alt Key).

b. Hold down the Ctrl key.

c. Release the Ctrl key.

d. Deselect Left Alt Key (or Right Alt Key).

To send F10 (used in BIOS), click F10.

To send a break, click Control Alt Delete.

10.3.2 Redirecting Storage Devices

This section describes how 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.

Note - You can also use this procedure to redirect a CD image file or a diskette image file stored on your hard drive.

1. Start the remote console application as described in Section 10.2, Starting the Remote Console Application From the WebGUI.

The Remote Console screen appears.

2. Choose Devices => CD-ROM or Devices => Floppy.

This enables the corresponding local storage device to connect to the remote server as though it were a storage device attached directly to that remote server.

FIGURE 10-9 CD-ROM Selected

Graphic showing CD-ROM selected.

3. To start a CD image file or a diskette image file from your hard drive, select CD-ROM Image or Floppy Image.

A browser appears.

Note - You cannot select two CD-ROM devices or two diskette devices. For example, you cannot select CD-ROM and CD-ROM image.

4. Use the browser to navigate to the corresponding image file, then click OK.

5. To disconnect a device from the server, deselect the corresponding menu item.