| Sun Remote System Control(RSC) 2.2.3 Release Notes |     |
| Sun Remote System Control(RSC) 2.2.3 Release Notes | |
|
Sun Remote System Control (RSC) 2.2.3 Release Notes |
This document describes some Sun
Remote System Control (RSC) 2.2.3 hardware and software issues. For complete information about using RSC, see the Sun Remote System Control (RSC) 2.2 User's Guide.
Several new features are available in RSC 2.2.3 hardware and software:
V480, V880, V490, and V890 servers with an updated system controller (SC) card installed. For more information about how RSC 2.2.3 works with the system controller card, refer to RSC 2.2.3 Support on Sun Fire V480, V880, V490 and V890 Servers.
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:
The following features are new in RSC 2.2 software. These features are not reflected in the RSC 2.2 User's Guide.
RSC software is included as part of the default installation set for the Solaris 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:
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.3 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.3 server software package, SUNWrsc, on the following Sun servers:
250 server running one of the following operating systems:
You can install the RSC 2.2.3 client software packages on:
The file used to install the RSC GUI and documentation for Microsoft Windows operating systems is SunRsc.exe.
Installation on the Solaris Operating System places the Sun Remote System Control (RSC) 2.2 User's Guide in the location /opt/rsc/doc/locale/pdf/user_guide.pdf. Installation on the Windows operating system places the User's Guide in the location C:\Program Files\Sun Microsystems\Remote System Control\doc\locale\pdf\user_guide.pdf.
The Remote System Controller (RSC) card has been replaced with a new system controller (SC) card on the Sun Fire V490 and V890 servers as well as some V480 and V880 servers. Both cards run the same RSC 2.2.3 software; however, there some important feature differences:
To update your RSC software to a version that supports these hardware changes, go to the following Web site:
http://www.sun.com/servers/rsc.html
For more information about using RSC 2.2.3 software with SC hardware, refer to your server's administration guide or owner's guide. This manual is included on the documentation CD that came with your server.
The Sun Fire V490 and V890 servers 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 Sun Fire V490 or V890 Documentation CD that came with your server.
This section describes issues that affect RSC 2.2.3 software running on Sun Enterprise 250, Sun Fire 280R, Sun Fire V480, Sun Fire V880, Sun Fire V490, and Sun Fire V890 servers.
Before you follow the procedures in the Service Manual for your server to remove or install the 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 procedure you require in your Service Manual.
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.
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.
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.
This intermittent problem has been observed on Sun Fire V880 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.
If you run obdiag on the console while it is set to rsc-console mode, the following behaviors might occur:
To avoid these behaviors, run obdiag when the system console is not set to RSC.
When you are running the maximum allowed number of telnet sessions on RSC, you might see messages similar to the following:
Connection to myserver closed by foreign host.
If this message appears, try running fewer telnet sessions on RSC.
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. RSC reports each state change as a disk error. These messages do not appear when SunVTS is not running tests.
This section describes issues that affect RSC 2.2.3 software running on Sun Fire V480, V880, V490, and V890 servers.
When the OpenBoot PROM enhanced diagnostics are enabled (as they are by default), rsc-console gets sent to the system console without warning. The RSC console might appear to be unresponsive to RSC commands. This behavior can also happen when you are using RSC software and the keyswitch of the system is set to the Diagnostics position.
(Sun Fire V490 and Sun Fire V890 servers only)
In the Sun Fire V490 and V890 servers, during startup, the Power LED does not blink. This LED blinks in other Sun server products. The LED in the Sun Fire V490 and V890 servers remains on during the startup process.
This section describes issues that affect RSC 2.2.3 software running only on Sun Fire 280R servers. See the Sun Fire 280R Server Product Notes for other Sun Fire 280R server issues.
RSC software generates the following alert on a Sun Fire 280R 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.
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.
This section describes issues that affect RSC 2.2.3 software running on Sun Enterprise 250 servers. See the Sun Enterprise 250 Server Product Notes for other Sun Enterprise 250 server issues.
Support for a maximum of 16 RSC user accounts is available in RSC 2.2.3 software. However, Sun Enterprise 250 servers continue to be limited to four RSC user accounts because of hardware limitations.
Reset the system's input-device and output-device settings to ttya. Then reboot the system and access the system through its local console or terminal and execute the boot -s command directly.
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.
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.
The Sun Remote System Control 2.2 User's Guide currently states that supports Sun Fire 480R and Sun Fire 880 servers. These model numbers are described incorrectly. The terminology should instead say that Sun Fire V480 and Sun Fire V880 servers are supported.
| Sun Remote System Control(RSC) 2.2.3 Release Notes | 819-2022-10 | |
Copyright © 2004, Sun Microsystems, Inc. All Rights Reserved.
