C H A P T E R  9

Remote Host Management Options

Topics

Description

Links

Identify the remote management options

Learn about controlling the power state of a remote server

Learn about redirecting storage media from the CLI on your local system to a remote host server

Learn about redirecting devices (keyboard, video display, mouse, storage) from the web interface on your local system to a remote host server

Learn about securing the ILOM Remote Console

Learn how to control the host boot device on an x86 system SP

Learn about Logical Domain (LDom) configurations on SPARC servers



Related Topics

For ILOM

Chapter or Section

Guide

  • CLI
  • Managing Remote Hosts’ Power States and Storage Redirection

Oracle Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide (820-6412)

  • Web interface
  • Managing Remote Hosts’ Power States and Redirection

Oracle Integrated Lights Out Manager (ILOM) 3.0 Web Interface Procedures Guide (820-6411)

The ILOM 3.0 Documentation Collection is available at: http://docs.sun.com/app/docs/prod/int.lights.mgr30#hic



Server SP Remote Management Options

As of ILOM 3.0, the remote management options in ILOM include:

Information about each of these remote management options follows.


Remote Power Control

The remote power states in ILOM are available for all Oracle Sun servers from the ILOM CLI or web interface. These options enable you to control the power state of a remote host server or chassis.

For information about remotely managing the power states on a managed device, see the section about Managing Host Remote Power States in one of the following guides:


Storage Redirection CLI

The Storage Redirection CLI in ILOM is supported on all Oracle Sun x86 processor-based servers. This CLI is also supported on some SPARC processor-based servers. However, the Storage Redirection CLI is not supported on Sun server SPs or chassis monitoring modules (CMMs) running ILOM 2.0. It is also not supported on CMMs running ILOM 3.0; although, the CMM web interface still provides the download links to the Storage Redirection service and client CLI tools. Once the service and client tools are downloaded and running on your machine, they can be used for Storage redirection to a server module running ILOM 3.0.

The Storage Redirection CLI enables the storage devices (CD/DVD or ISO images) on your local client to behave as if they were directly attached to the remote host server. For instance, the redirection functionality enables you to locally perform these actions:



Note - The Storage Redirection CLI is limited to remote media control. If you need to remotely manage other devices on a remote host server (such as the keyboard, video display, or mouse), you should use the Oracle ILOM Remote Console. For more information about the Oracle ILOM Remote Console, see Oracle ILOM Remote Console.


For instructions about how to launch and use the Storage Redirection CLI, see the section about “Managing Remote Host Storage Redirections” in the Oracle Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide.

First Time Access

When you access the Storage Redirection CLI for the first time, you must sign in to the ILOM web interface to install the service and the client. After the service and client are installed on your system, you can subsequently start the service and launch the Storage Redirection CLI directly from a command window or terminal.



Note - You can, alternatively, choose to start the service directly from the ILOM web interface. If you choose to start the service from the ILOM web interface without installing it, you will need to subsequently access the ILOM web interface to start the service prior to launching the Storage Redirection CLI from a command window or terminal. For more information about how to install or start the service, see the section about “Managing Remote Hosts” in the Oracle Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide.


Storage Redirection CLI Architecture

The Storage Redirection CLI consists of a Java Web Start service and a scriptable, Java command-line client. You must start the service and initially install the client from the ILOM web interface. The Storage Redirection service runs in the background of your local client and establishes the connection between your local client and the remote host server. After a connection is established, you can locally launch the Storage Redirection CLI from a command window or terminal. The Storage Redirection CLI enables you to issue commands to the service for starting and stopping storage redirection.


FIGURE 9-1 Storage Redirection Service and Client

Storage Redirection Service and Client


Figure Legend

1

Local client running Storage Redirection command-line client

2

Storage Redirection service running on local client

3

Remote host server




Note - You can only run one instance of the Storage Redirection service on your local system at one time. However, you can launch multiple Storage Redirection CLIs by issuing the Storage Redirection command (-jar StorageRedir.jar) from a local command window or terminal.


For instructions about how to launch and use the Storage Redirection feature in ILOM, see the section about Managing Remote Host Storage Redirections in the Oracle Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide

Default Network Communication Port

The default network communication port provided for Storage Redirection CLI is 2121. This default socket port enables the Storage Redirection CLI to communicate over the network with a remote host server SP. If you need to change the default network port, you must edit the Jnlpgenerator-cli file to manually override the default port number (2121).

For more information about how to edit the network port number that is referenced in the Jnlpgenerator-cli file, see “Change the Default Storage Redirect Port: 2121” in the Oracle Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide.


Oracle ILOM Remote Console

The Oracle ILOM Remote Console is supported on all Sun x86 processor-based servers. It is also supported on some SPARC processor-based servers. The Oracle ILOM Remote Console is a Java application that you can launch from the ILOM web interface. When you use the Oracle ILOM Remote Console, you can remotely redirect and control the following devices on a remote host server:

The Oracle ILOM Remote Console enables the devices on your local client to behave as if they were directly attached to the remote host server. For instance, the redirection functionality enables you to perform any of the following tasks:

The Oracle ILOM Remote Console supports two methods of redirection: video and serial console. Video redirection is supported on all Sun x86 processor-based servers and some Sun SPARC processor-based servers. Serial console redirection is supported on all SPARC processor-based servers. Serial console redirection is not currently supported on x86 processor-based servers.

For instructions for redirecting host devices using the Oracle ILOM Remote Console, see “Managing Remote Hosts’ Power States and Redirection” in the Oracle Integrated Lights Out Manager (ILOM) 3.0 Web Interface Procedures Guide.

International Keyboard Support for ILOM Remote Console

As of ILOM 3.0.9, the ILOM Remote Console fully supports the use of all characters on the following international keyboards.



Note - Prior to ILOM 3.0.9, the ILOM Remote Console did not support the use of all the international characters on these keyboards.


Single or Multiple Remote Host Server Management Views

The Oracle ILOM Remote Console supports both single and multiple remote server management views.

Single and multiple server management views are currently supported on all x86 processor-based servers and some SPARC processor-based servers.

Single remote server management views are supported when you connect to the IP address of any server SP.

FIGURE 9-2 Single Server Management View


Single Server Management View

Multiple remote server management views are supported when you either: (1) add a new Oracle ILOM Remote Control session to manage another remote host server; or (2) connect to the IP addresses that are associated with an x86 chassis monitoring module (CMM).

FIGURE 9-3 Multiple Server Management Views


Multiple Server Management View

Installation Requirements

The Oracle ILOM Remote Console does not require you to install any additional hardware or software. It is built into the ILOM software. However, to run the Oracle ILOM Remote Console, you must have the JRE 1.5 or higher (Java 5.0 or higher) software installed on your local client. To download the Java 1.5 runtime environment, go to: http://java.com

In addition, the Oracle ILOM Remote Console is supported on your local client with the operating systems, web browsers, and JVM listed in the following table.


TABLE 9-1 Supported Operating Systems, Web Browsers, and JVM

Operating System

Web Browser

Java Virtual Machine (JVM)

Oracle Solaris (9 and 10)

  • Mozilla 1.7.5 and above
  • Firefox 1.0 and above
  • 32-bit JDK

Linux (Red Hat, SuSE, Ubuntu, Oracle)

  • Mozilla 1.7.5 and above
  • Firefox 1.0 and above
  • Opera 6.x and above
  • 32-bit JDK

Microsoft Windows (98, 2000, XP, Vista)

  • Internet Explorer 6.0 and above
  • Mozilla 1.7.5 and above
  • Firefox 1.0 and above
  • Opera 6.x and above
  • 32-bit JDK

Network Communication Ports and Protocols

The Oracle ILOM Remote Console communicates to a remote host server SP using the following network ports and protocols.


TABLE 9-2 SP ILOM Remote Console Network Ports and Protocols

Port

Protocol

SP - ILOM Remote Console

5120

TCP

CD

5123

TCP

Diskette

5121

TCP

Keyboard and mouse

5556

TCP

Redirection authentication

7578

TCP

Video

7579

TCP

SPARC servers only


Sign In Authentication Required

When you launch the Oracle ILOM Remote Console from the ILOM web interface, you must sign in using an Admin (a) or Console (c) role account. The system will subsequently prompt you to reenter the Admin or Console role account each time you perform one of the following: start a redirection, stop a redirection, or restart a redirection.



Note - If the Single Sign On feature is disabled in ILOM, users with Admin (a) or Console (c) role privileges will be prompted to sign in to ILOM again using the Login dialog. For additional information about the Single Sign On feature, see Single Sign On.


CD and Diskette Redirection Operation Scenarios

Use the information in TABLE 9-3 to help identify different case scenarios in which the CD drive or diskette drive redirection functionality might behave during a Remote Console session.


TABLE 9-3 Remote Console Operation With DVD Drive and Diskette Drive

Case

Status

DVD as Seen by Remote Host

Diskette as Seen by Remote 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 ILOM when the hosts asks.

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

2

Remote Console application started with no medium present in the drive

DVD device present. When 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. When 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. When 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. When 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 case 3.

Same as case 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 case 3.

Same as case 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 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 keep-alive 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 case 8.

Same as case 8.


For instructions about how to launch and use the ILOM Remote Console, see the section about Managing Remote Hosts in one of the following guides:

LDAP/SSL Management pageOptional User Attribute Mapping ParametersMIBs download pageActive Sessions pageActive Directory Management page


ILOM Remote Console Computer Lock

As of ILOM 3.0.4 or later, a Lock feature is available for the ILOM Remote Console that enhances your system security by enabling you to lock your computer when terminating a ILOM Remote Console session. Specifically, the lock behavior takes place either when you terminate an ILOM Remote Console session or when the managed network connection to the server is lost.

If you are running a Windows operating system on your host, you can enable the computer lock feature in ILOM by selecting Windows as your option. The Windows lock mode option works in conjunction with the standard Windows keyboard shortcut for locking the Windows operating system (CRTL+ALT+DEL K).

If you are running a Solaris or Linux operating system on your host, you can execute the computer lock behavior when the ILOM Remote Console terminates by implementing the custom lock mode feature in ILOM.

The custom lock mode feature in ILOM enables you to execute any system behavior that is tied to a predefined keyboard shortcut on your host operating system. To execute a custom keyboard shortcut behavior in ILOM, you must first define the behavior you want to take place on your host operating system with a keyboard shortcut. Then, to execute this behavior when the ILOM Remote Console terminates, you must specify the OS keyboard shortcut parameters in the custom KVMS lock mode feature in ILOM.

Special Considerations When Enabling the ILOM Remote Console Lock Option

Review the following special considerations in TABLE 9-1 prior to enabling the KVMS lock mode option in ILOM.


TABLE 9-1 Special Considerations When Enabling the Remote Console Lock Option

Special Consideration

Description

Console user role is required to set lock option.

To enable the ILOM Remote Console Lock option in ILOM, you must have Console (c) role privileges associated with your user account.

For more information about setting up a user account in ILOM with Console privileges, see the User Management section in the ILOM 3.0 Documentation Collection.

A predefined keyboard shortcut on the OS is required to execute the custom lock mode feature.

Prior to enabling a custom keyboard shortcut in ILOM for when the ILOM Remote Console connection terminates, you must first define the keyboard shortcut behavior on your host operating system.

For instructions for creating a keyboard shortcut on your host operating system, see the documentation supplied with your operating system.

The custom lock mode feature can be defined with up to four modifiers and one key.

When you specify the custom lock mode feature in ILOM, you can specify up to four modifiers and one key. A list of supported modifiers and keys that you can use to match your predefined OS keyboard shortcut appear in both the CLI KVMS help and the web interface KVMS page.

Lock behavior when running multiple ILOM Remote Console Sessions.

If more than one ILOM Remote Console session is opened to the same SP, the Windows lock or custom keyboard shortcut behavior configured in ILOM will only take place when you close the last SP ILOM Remote Console session.


For instructions about how to configure the remote console lock option in ILOM, see section about Managing Remote Hosts in one of the following guides:


Host Control - Boot Device on x86 Systems

As of ILOM 3.0.3, you can use the Host Control features in the CLI and web interface to select the host boot device settings that will override the boot device order in the BIOS. This ability gives the CLI and web interface parity with the existing IPMI interface.

The primary purpose of the boot device override feature is to enable the administrator to perform a one-time manual override of the server’s BIOS boot order settings. This enables the administrator to quickly configure a machine or group of machines to boot from another device, such as the PXE boot environment.

The Host Control boot device settings are available in ILOM for Oracle Sun x86 systems SPs. This feature is not supported on the CMM. For Host Control settings in ILOM specific to SPARC system server SPs, consult the ILOM Supplement guide or platform Administration guide provided for that system.

For procedures on how to use the Host Control boot settings in ILOM on an x86 system SP, see the Remote Management Option procedures in the following ILOM guides:


ILOM Operations for LDom Configurations on SPARC Servers

You can use ILOM to perform the following tasks on SPARC servers that have stored Logical Domain (LDom) configurations.


Task

Supported ILOM Point Release

View ILOM CLI targets and properties for stored LDom configurations from a host SPARC T3 Series server.

  • 3.0.12 (CLI only)
  • 3.0.14 (CLI and web interface)

Specify which stored LDom configuration is used on the host SPARC server when the server is powered-on.

  • 2.0.0 (CLI and web interface)

Enable (default) or disable the control domain boot property values from the host SPARC server.

  • 2.0.0 (CLI and web interface)

For more information and procedures on how to view and configure LDom configurations on SPARC servers, see the following ILOM guides: