These release notes are applicable to Sun Remote System Control (RSC) Version 1.0, Firmware Version 1.12.
The only supported server is the Sun Enterprise 250 server, running the Solaris 2.6 5/98, Solaris 7, or Solaris 7 3/99 operating environments.
The Sun Enterprise 250 flash PROM must be updated to version 3.7.7 or later before installing the RSC software. Failing to do so may cause server and RSC malfunctions. For update instructions and a downloadable image, see the Sun Enterprise 250 Supplement Web page at http://sunsolve2.Sun.COM/sunsolve/E250/flash.html. If you install RSC from the Solaris 7 3/99 Sun Computer Systems Supplement CD, you can update the flash PROM as part of the installation process.
Sun systems running the Solaris 7 3/99 operating environment
Sun systems running the Solaris 2.6 5/98 operating environment
Systems running the Microsoft Windows 95 operating environment
Systems running the Microsoft Windows 98 operating environment
Systems running the Windows NT Workstation operating environment
ASCII character terminals
Systems running ASCII terminal emulation software
Systems with telnet client software
An American Power Conversion SmartUPS 1000 with PowerChute plus 4.2.2 software was used for testing.
As of Solaris 7 3/99, SunVTS 3.1 supports the diagnostic testing of the RSC with a test called rsctest. The rsctest is automatically installed when SunVTS is installed. For more information on the SunVTS diagnostic, refer to the SunVTS 3.1 User's Guide which is part of the Solaris 7 on Sun Hardware AnswerBook collection. It is also available at http://docs.sun.com.
RSC paging requires that the customer's paging service adhere to the TAP protocol. Paging services in the Americas and Europe generally are TAP-compliant, but this is not necessarily so in other locales.
Due to the many variables associated with paging, Sun strongly recommends that you test the RSC paging mechanism to insure that your configuration options are set correctly.
The easiest way to test that all the components associated with RSC paging are functioning properly is to use the rscadm send_event -c command. This command can be invoked from a UNIX shell and will initiate an RSC alert. If the RSC page_enabled flag is set to true, this alert will send a page to the recipients specified by the page_info1 and page_info2 environment variables.
If RSC fails to send a page, a message similar to the following will be added to the event log:
THU AUG 27 22:31:09 1998 sst4828: 00060006: "Failed to send page alert for recent event"
If RSC successfully transmits a page, no error message is added to the event log.
RSC can fail to send a page notification for the following reasons:
It failed to communicate with the modem.
It failed to contact the paging service specified by the page_info1 or page_info2 variable.
A failure occurred while RSC was communicating with the paging service TAP server.
When a page fails, check the following:
That your modem dip switch and software configuration variables are set correctly.
That all the RSC page_variables (page_info1 and 2, page_init1 and 2, and page_baud1 and 2) are set correctly and match the settings for your paging service.
Insure that your paging service supports the TAP protocol. Check with the paging service to insure that you have the proper phone number and modem configuration parameters.
Attempt to connect with the paging service manually. Refer to the "Troubleshooting Modem Problems" section in Appendix B of the RSC User's Guide for instructions on manually connecting to a TAP paging service.
In some cases, it might be desirable to extend the pause period to allow the modem to recognize the dial tone of the phone line. This can be accomplished on most modems by increasing the value in the S8 register. See documentation that came with your modem for more details.
4151918: The SunVTS rsctest subtest does not provide adequate failure information.
4168110: The RSC GUI "OK" button in dialog boxes cannot be translated.
4171924: The RSC GUI occasionally reports invalid exceptions when you Logout or Exit.
4168266: Heavy use of UNIX tcsh shell commands in an RSC console session may stop RSC from responding to requests. Killing the tcsh shell restores RSC to normal behavior.
4167862: A loghistory error is reported when the "index -n" value you specify is greater than the number of lines in the buffer.
4171929: RSC sometimes reports a fan failure erroneously after a thermal shutdown.
4172574: The CLI reports a DC Power Failure when the host is powered off.
4145761: An RSC reset is required for changes to the serial_hw_handshake variable (or "Enable Hardware Handshaking" setting in the GUI) to take effect, but should not be required.
4167651: RSC default configuration settings for pagers do not match modem configuration settings suggested in documentation.
4152840: RSC shell commands do not issue a confirmation query before resetting the host system.
4171431: The GUI event log output differs from the CLI loghistory output.
4170988: The RSC GUI Back button for the first instance of Help does not return you to the previous view.
4172337: The error message displayed for an attempted third telnet or fifth user session needs improvement.
4162419: In the Windows operating environment, the RSC GUI goes to the background when you cancel an operation after an error message.
4158400: The message "[Loaded DTD html32 in 142ms]" appears when the RSC Help file is displayed.
4151674: Clicking on "Set RSC Date and Time" sometimes displays a duplicate image of the "Set RSC Date and Time" option just above the option list, and below the "RSC for <hostname>" title.
4170986: The GUI "Set Date/Time" dialog box displays 0:00:00 when time changes to noon and midnight. This is an invalid time format.
4159618: A GUI reset request and the resulting reset event are recorded in the incorrect order in the RSC event log.
4159562: The telnet connection resets intermittently when you try to connect to the RSC console from the GUI.
4159564: The Java Runtime Environment (JRE) may crash in the Windows 95 operating environment when you modify an RSC user account.
4172331: In the RSC GUI Serial Port settings, there is a typo in the error message for Invalid IP Address.
4159135: The RSC GUI has no option which shows the information returned by the CLI shownetwork command.
4157854: Sometimes when a thermistor displays a warning in the Environmental Status window and you refresh the screen, the warning is mistakenly displayed for a different thermistor. Another refresh corrects this problem.
4173022: The escape sequence for exiting from the RSC console does not work if the escape_char variable is set to "^?".
4175561: When connected to the server's console through RSC, a paste operation of over 336 characters into the window connected to RSC may hang the console connection. A reset of RSC is required to recover. The operation of the server is not affected.