test

Solaris 7 3/99 Release Notes Supplement for Sun Hardware

Sun Remote System Control (RSC) Release Notes

Hardware and Software Configurations Supported for RSC

These release notes are applicable to Sun Remote System Control (RSC) Version 1.0, Firmware Version 1.12.

Supported Server

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.

Supported GUI Clients

Supported CLI Clients

Uninterruptible Power Supply (UPS)

An American Power Conversion SmartUPS 1000 with PowerChute plus 4.2.2 software was used for testing.

SunVTS

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.

Paging Support

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.

Testing RSC Paging

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:

  1. It failed to communicate with the modem.

  2. It failed to contact the paging service specified by the page_info1 or page_info2 variable.

  3. A failure occurred while RSC was communicating with the paging service TAP server.

When a page fails, check the following:

  1. That your modem dip switch and software configuration variables are set correctly.

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

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

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

Troubleshooting

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.

Known Issues