C H A P T E R  5

Using the Remote Console Application

This chapter describes how to use the remote console application. It includes the following sections:


Accessing the Remote Console From the Web GUI

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

Installation Requirements

A compatible browser and a minimum of JREtrademark 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.



TABLE 5-1 Client Installation Requirements

Client OS

Java Runtime Environment Including Java Web Start

Browsers

Microsoft Windows XP Pro

JRE 1.6 (Java 6.0 or later)

Internet Explorer 6.0 and later

Mozilla 1.7.5 or later

Mozilla Firefox 1.0

Red Hat Linux 4.0 or later Desktop and Workstation Editions

JRE 1.6 (Java 6.0 or later)

Mozilla 1.7.5 or later

Mozilla Firefox 1.0

Solaris 9

JRE 1.6 (Java 6.0 or later)

Mozilla 1.7.5

Solaris 10

JRE 1.6 (Java 6.0 or later)

Mozilla 1.7.5

SUSE Linux 9.2

JRE 1.6 (Java 6.0 or later)

Mozilla 1.7.5




Note - You can download the JRE 1.6 at http://java.com.


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:

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 CD Drive and Diskette Drive

Case

Status

CD As Seen by Host

Diskette As Seen by Host

1

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

CD device present. No medium indication is sent to the host from the ELOM whenever the hosts asks.

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

2

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

CD 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.

CD 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 CD redirection stopped so it sends a medium absent status on the next host query.

Driver knows CD 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 keepalive 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.



Starting the Remote Console Application

Use this procedure to start the remote console application from the web GUI. You may 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 will default to the IP address 192.168.1.2 to allow instant web access.



procedure icon  To Start the Remote Console Application

1. Open your browser.

2. In the address bar, enter the IP address of the SP that you obtained in: To Set Up the Service Processor with the WebGUI.

The login screen appears.

3. Type user name and password for an account with administrator privileges.

4. Click Login.

The ELOM main menu appears.

5. Click the Remote Control tab.

6. Select Redirection.

The screen displays a Launch Redirection button.

7. Click Launch Redirection.

A screen identifies your current host name, IP address, and user name. The Launch button opens the remote console.

8. Click Launch.



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


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



Note - If the remote console does not display, it might be blocked by browser security controls (pop-up blocker). Reduce security configuration to allow the remote console to display.



Redirecting Keyboard, Video, Mouse, or Storage Devices

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


procedure icon  To Redirect Keyboard and Mouse Devices

Use the following procedure to redirect your local workstation or laptop keyboard and mouse to a remote Sun Blade X6250 server module.

1. Start the remote console application as described in Starting the Remote Console Application.

2. From the system management software opening screen select the Remote Control tab.

3. Select the Hotkey Setup tab.

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

4. 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


A screenshot of teh Remote Control, Hotkey Setup screen.Graphic showing keyboard, video and mouse selections[ D ]

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.


procedure icon  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 module. 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.

1. Start the remote console application as described in Starting the Remote Console Application.

The Remote Console screen is displayed.

2. Select Storage from the drop-down list and click Mount Device.

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.

3. Select a source device from the drop-down list.



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 browser to navigate to the corresponding file, then click Submit.


After successfully mounting a storage device a green check mark is displayed in the lower left corner of the Remote Console window.



Note - Use the web GUI to disable the session time out, or to set the session timeout to a long enough period of time to allow you to work without the system automatically logging you out.



Installing an OS on a Remote Server

This method includes using a CD or DVD drive or image of the operating system on a remote networked system to install the operating system, for example, onto the Sun Blade X6250 server module.

Requirements for Remote KMVS Over IP installation include:


procedure icon  To Install an OS on a Remote Server Using a Virtual CD-ROM



Note - Disable the timeout function when installing remotely from the virtual CD-ROM.


1. On your laptop or local terminal, open a browser, and enter the IP address of the Sun Blade X6250 server module service processor for the target system.

This is the Sun Blade X6250 server module on which you want to install the operating system.

2. Enter the user name and password in the login screen.

3. In the main ELOM screen, click the Remote Control tab, then click Launch Redirect to open a remote console screen.

4. Insert the operating system CD/DVD to be installed on the Sun Blade X6250 server module into your laptop or local CD/DVD drive.

5. In the remote console screen, choose Storage ->Mount devices.

The Device Configuration screens appears.

6. Under Storage 1, in the drop-down list, select the local CD/DVD that you will be using for the installation.

7. Click Submit.

8. Reboot the server.


Other Remote Options

Command-line options that are available to address many of these tasks include IPMI tools (Chapter 7), CLI (Chapter 6), and SSH (Secure Shell).