Sun Remote System Control (RSC) 2.2.2 Release Notes

This document describes some Sun Remote System Control (RSC) 2.2.2 hardware and software issues. For complete information about using RSC, see the Sun Remote System Control (RSC) 2.2 User's Guide.

##

What's New in RSC 2.2.2

Several new features are available in RSC 2.2.2 hardware and software:

- RSC 2.2.2 software supports the Sun Fire V490 and Sun Fire V890 servers with the system controller (SC) card installed. For more information about how RSC 2.2.2 works with the system controller card, refer to "RSC 2.2.2 Support on Sun Fire V490 and Sun Fire V890 Servers" on page 4.

- The RSC graphical user interface (GUI) requires an updated version of the Java Runtime Environment: Java 2 Standard Edition (J2SE) Runtime Environment Version 1.3.0_02 or greater. You can download the appropriate version from one of these web sites:

- Solaris -- `http://www.sun.com/solaris/java`

- Windows -- `http://java.sun.com/j2se/1.3/`

The following features are new in RSC 2.2.2 software. These features are not reflected in the Sun Remote System Control (RSC) 2.2 User's Guide.

- Client support has been added for the Microsoft Windows 2000 operating system.

- Sun Fire V480 and Sun Fire V490 servers include a hardware feature, a Locator LED on the system's front and rear panels. RSC software allows you to toggle the state of these LEDs to help identify a particular system that might be located in a rack with other servers.

- Support for a maximum of 16 RSC user accounts has been added with RSC 2.2.2 software. A maximum of 10 users can be logged in at one time. However, the increased number of user accounts does not affect the limitation of five concurrent `telnet` or GUI login sessions per server.

##

Before Installing Sun Remote System Control Software

RSC software is included as part of the default installation set on the Solaris Software Supplement CD that came with your operating system. You must install RSC server components only on a compatible server running the Solaris Operating System. You can install the client software on any computer that meets the Solaris or Windows operating system requirement. You must install and configure the RSC software before you can use RSC.

IMPORTANT: Before upgrading from a previous version of RSC server software or reinstalling the software, log in to the server as root and back up your configuration data using the following commands:

    # rscadm show > remote_filename
    # rscadm usershow >> remote_filename

Use a meaningful file name that includes the name of the server that RSC controls. After installation, you can refer to this file to restore your configuration settings, if necessary. Reverting to a previous version of RSC server software after installing Version 2.2.2 is not recommended. However, if you do so, you will need to restore your configuration information and also power cycle the server.

You can install the RSC 2.2.2 server software package, `SUNWrsc`, on the following Sun servers:

- A Sun Fire V890 server running the Solaris 8 2/04 Operating System or the Solaris 9 8/04 Operating System, or compatible release

- A Sun Fire V490 server running the Solaris 8 2/04 Operating System or the Solaris 9 8/04 Operating System, or compatible release

- A Sun Fire V480 server running the Solaris 8 10/01 Operating System, or compatible release

- A Sun Fire V880 server running the Solaris 8 7/01 Operating System, or compatible release

- A Sun Fire 280R server running the Solaris 8 1/01 Operating System, or compatible release

- A Sun Enterprise 250 server running one of the following Operating Systems:

- Solaris 2.6

- Solaris 7

- Solaris 8

You can install the RSC 2.2.2 client software packages on:

- Any other computer running the Solaris 2.6, Solaris 7, Solaris 8, or Solaris 9 Operating Systems. The packages are `SUNWrscj` (GUI) and `SUNWrscd` (documentation).

- Any computer running one of the following Microsoft Windows operating systems:

- Windows 98

- Windows 2000

- Windows NT 4.0

The file used to install the RSC GUI and documentation for Microsoft Windows operating systems is `SunRsc.exe`.

- Client computers require Java 2 Standard Edition (J2SE) Runtime Environment Version 1.3.0_02 or a subsequent 1.3.x version to run RSC 2.2.2 software. RSC 2.2.2 software will not run using J2SE Runtime Environment Version 1.2.x. You can download the appropriate version from one of these web sites:

- Solaris -- `http://www.sun.com/solaris/java`

- Windows -- `http://java.sun.com/j2se/1.3/`

##

RSC Documentation Location

After you install the Solaris Operating System and the software from the Solaris Software Supplement CD, you have access to the online version of Sun Remote System Control (RSC) documentation. You can find the PDF version of the Sun Remote System Control (RSC) 2.2 User's Guide in the following location within the Solaris Operating System:

`/opt/rsc/doc/`<locale>`/pdf/user_guide.pdf`

After you install RSC software on a Microsoft Windows-based PC, you can find the appropriate User's Guide in the following location within the Microsoft Windows environment:

`C:\Program Files\Sun Microsystems\ Remote System Control\doc\
`<locale>`\pdf\user_guide.pdf`

RSC documentation is also included on the documentation CD that is shipped with the server.

##

RSC 2.2.2 Support on Sun Fire V490 and Sun Fire V890 Servers

The Sun Fire V490 and Sun Fire V890 servers come with the system controller (SC) card installed.

The following list summarizes how the RSC 2.2.2 software and the system controller hardware work.

- The SC card does not have an on-board modem. The modem/pager commands in the RSC 2.2.2 software do not work with the SC card. Likewise, the modem/pager configuration variables do not work with the SC card.

- The SC card does not have a system backup battery. It receives its power directly from the server power, and it runs even when the server is powered down or on standby, as long as the server is plugged in to an AC outlet.

For more information about using RSC 2.2.2 software with SC hardware, refer to the Sun Fire V490 Server Administration Guide or the Sun Fire V890 Server Owner's Guide. These guides are on the corresponding Documentation CDs shipped with the Sun Fire V490 and Sun Fire V890 servers.

### OpenBoot PROM Enhancements

The Sun Fire V490 server and the Sun Fire V890 server ship with OpenBoot PROM Version 4.15. This version of OpenBoot PROM has a new standard (default) configuration that includes enhanced diagnostics. These enhanced diagnostics change some behaviors in RSC. For more information about these diagnostics, refer to OpenBoot PROM Enhancements for Diagnostic Operation, which is on the Documentation CD that came with your server.

##

RSC General Issues

This section describes issues that affect RSC 2.2.2 software running on Sun Enterprise 250, Sun Fire 280R, Sun Fire V880, Sun Fire V480, Sun Fire V890, and Sun Fire V490 servers. The battery, pager, and modem related issues do not apply to the Sun Fire V490 or Sun Fire V890 servers, since they use the system controller (SC) card instead of the RSC card.

### Removing and Installing the RSC or SC Card

| Caution - Removing or installing the RSC or SC card while the system has the AC power cord connected could damage your system or your RSC or SC card. Only qualified service personnel should remove or replace the RSC or SC card. Contact your qualified service representative to perform this service operation.

Before you follow the procedures in the Service Manual or Parts Installation and Removal Guide for your server to remove or install the RSC or SC card, perform this procedure to ensure that there is no AC power present in the system.

1. Shut down and halt the system.

2. With the system at the `ok` prompt, turn the keyswitch to the Off position.

Standby power is still present in the system at this point.

3. Disconnect all AC power cords from their back panel receptacles.

This ensures that there is no standby power voltage present in the system.

4. Follow the removal procedure in your Service Manual or Parts Installation and Removal Guide.

### Alert Messages Might Be Delayed

If the RSC variables `page_enabled` and `mail_enabled` are set to `true` and multiple alert messages are generated within a short interval, the first message is delivered in a timely fashion, but each subsequent message issued during the interval is delayed by three to four minutes.

### Wrong Information Provided on `alerts.html`

When configuring the `page_info1` or `page_info2` fields, you can use any digit or the alphanumeric characters `#`, `@`, and`,` (comma) when specifying a pager phone number, but the PIN area can contain only digits (0 to 9). In the RSC GUI, the online help for this function is incorrect. For more information about how to configure RSC to work with a pager, refer to the Sun Remote System Control (RSC) 2.2 User's Guide.

### `rsc-console` Switches to `tip` Connection During Boot When `diag-switch?` Is Set to `true`

When `diag-switch?` is set to `true` and you use the `bootmode -u` command to reboot your server, `rsc-console` reverts to the serial (`tip`) connection after the Solaris software restarts, even if you have previously redirected the console to RSC.

If this occurs, manually redirect the console output to RSC again after the reboot operation has completed. Refer to the Sun Remote System Control (RSC) 2.2 User's Guide for more information.

### RSC `bootmode -u` Command Fails to Toggle the Console

This intermittent problem has been observed on servers running OpenBoot PROM Version 4.4.6. Occasionally, the `bootmode -u` command fails to redirect the console to RSC. If this happens, use the `resetrsc` command.

### Running `obdiag` in `rsc-console` Mode Can Cause Unexpected Behaviors

If you run `obdiag` on the console while it is set to `rsc-console` mode, the following behaviors might occur:

- Running the `rsc-control` test in `obdiag` logs you out of RSC.

- Running the serial test in `obdiag` sends unexpected characters to the server's serial connection.

To avoid these behaviors, run `obdiag` when the system console is not set to RSC.

### `SetSockOpt: Invalid argument` Message Received When Maximum Number of Telnet Sessions Is Reached

When you are running the maximum allowed number of telnet sessions on RSC, you might see messages similar to the following:

`telnet myserver`

`Trying 123.234.245.256...`

`Connected to myserver.`

`Escape character is `^]'.`

`SetSockOpt: Invalid argument`

`Connection to myserver closed by foreign host.`

If these messages appear, try running fewer telnet sessions on RSC.

### Disk Errors Are Reported in `loghistory` While Running SunVTS, But No Errors Are Reported in SunVTS or Solaris

If you run SunVTS software and RSC software simultaneously, you may see disk errors reported using the `loghistory` command that do not appear in SunVTS tests. This occurs because SunVTS cannot suspend RSC monitoring while tests are running. Because SunVTS tests mimic conditions used to report disk errors, RSC reports these conditions as disk errors. These messages do not appear when SunVTS is not running tests.

##

RSC Issues for Sun Fire V490 and
Sun Fire V890 Servers

This section describes issues that affect RSC 2.2.2 software running on Sun Fire V490 and Sun Fire V890 servers.

### The RSC Console Switches to the Server Console Without Warning When OpenBoot PROM Enhanced Diagnostics Are On or the Control Switch Is in the Diagnostics Position

When service-mode? is set to true, the `rsc-console` connection gets sent to the server console without warning. When this occurs, the RSC console may appear not to respond to RSC commands. This behavior can also happen when you are using RSC while the front panel keyswitch of the Sun Fire V490 or Sun Fire V890 server is set to the Diagnostics position.

### LED Behavior During Startup

In the Sun Fire V490 and Sun Fire V890 servers, during startup, the power LED does not blink, unlike other Sun server products. The LED remains on during startup.

##

RSC Issues for Sun Fire 280R, Sun Fire V880, and Sun Fire V480 Servers

This section describes issues that affect RSC 2.2.2 software running on Sun Fire 280R, Sun Fire V880, and Sun Fire V480 servers. See the Product Notes for the respective servers for other server issues.

### Additional RSC Alerts

RSC software generates the following alert on a Sun Fire 280R or Sun Fire V880 server when the RSC card begins battery use after a power interruption:

`00060012: "RSC operating on battery power."`

RSC software generates the following alerts when the host system has shut down from RSC. The messages appear in the log history.

`00040000: "RSC Request to power off host."`

`00040029: "Host system has shut down."`

If you shut down the system using the keyswitch, or by using the OpenBoot PROM `poweroff` command, the alert 00040029 is the only alert displayed.

These alerts are not documented in the Sun Remote System Control (RSC) 2.2 User's Guide.

### False Drive Fault Reported at Power-On

On Sun Fire 280R servers only, when you power on the system, it might report a false internal drive fault that is recorded in the RSC log history.

If the error is reported by RSC, you should disregard it if the system boots successfully to the Solaris Operating System. In most cases the erroneous fault will not reappear. You can verify the disk after the boot process by using the `fsck` utility.

Note - Any disk drive error message reported by the Solaris Operating System is a real disk drive error.

If a disk fault is reported at the `ok` prompt and the system fails to boot to the Solaris Operating System, there may be a problem with the disk drive. Test the disk drive with the OpenBoot Diagnostics tests documented in the "Diagnostics, Monitoring, and Troubleshooting" chapter in the Sun Fire 280R Server Service Manual.

### Going From Battery to Standby, the Locator LED Will Turn On in the GUI

On Sun Fire V480 servers only, when the RSC hardware changes state from battery power to standby power, the Locator LED on the Sun Fire V480 server appears illuminated in the GUI only. It does not illuminate on the system.

If this happens, use the `resetrsc` command.

##

RSC Issues for Sun Enterprise 250 Servers

This section describes issues that affect RSC 2.2.2 software running on Sun Enterprise 250 servers. See the Sun Enterprise 250 Server Product Notes for other Sun Enterprise 250 server issues.

### Increased Number of RSC User Accounts Not Supported

Support for a maximum of 16 RSC user accounts has been added for RSC 2.2.2 software. However, Sun Enterprise 250 servers continue to be limited to four RSC user accounts because of hardware limitations.

### Change to the `serial_hw_handshake` Variable Requires a System Reboot

[4145761]

In order for changes to the RSC configuration variable `serial_hw_handshake` to take effect, the server must be rebooted. This also affects the Enable Hardware Handshaking check box in the RSC graphical user interface. This limitation is not stated in the documentation.

### Power Supply Alerts Display Incorrect Index in the GUI

[4521932]

In the Sun Enterprise 250, the power supplies are numbered 0 and 1, but the RSC graphical user interface (GUI) refers to them as Power Supply 1 and Power Supply 2 in the event log and in alerts.

##

Documentation Issue

### Sun Remote System Control (RSC) 2.2 User's Guide Update

The Sun Remote System Control (RSC) 2.2 User's Guide currently states that it supports Sun Fire 480R and Sun Fire 880 servers. These model numbers are described incorrectly. The terminology should say that Sun Fire V480 and Sun Fire V880 servers are supported instead.

####

Copyright © 2004, Sun Microsystems, Inc. All rights reserved.