Sun Remote System Control (RSC) Release Notes

What's New in This Version

This version of Sun Remote System Control (RSC) includes bug fixes and a new environment variable, tpe_link_test. In addition, the RSC device Internet address has been added to email and pager alert messages.

If you have already installed a previous version of Remote System Control, back up your RSC configuration before installing this version, following the directions in Chapter 2 of the RSC User's Guide, and then restore them after installation when you run the RSC configuration script.

The tpe_link_test variable enables 10BASE-T Ethernet link integrity tests when set to true, the default. If you are using RSC in a hub that does not support Ethernet link integrity tests or that has them disabled, set this variable to false. Changes to this variable take effect after the next RSC reset. The tpe_link_test variable behaves similarly to the tpe-link-test? OBP environment variable, which is available on some SPARC platforms.

RSC and the local hub should have Ethernet link integrity tests enabled or disabled consistently. If this setting is not consistent, communication may not be possible.

Hardware and Software Configurations Supported for RSC

Supported Server

Sun Enterprise 250 server only, running the Solaris 7 or Solaris 2.6 5/98 operating environment.

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 Sun Enterprise 250 Supplement CD, you can update the flash PROM as part of the installation process.

Supported GUI Clients

Sun JDK(TM) version 1.1.6 or a subsequent compatible version is required for GUI support on systems running the Solaris operating environment, and is included in the base Solaris 7 operating environment and the Sun Enterprise 250 Supplement CD.

Supported CLI Clients

• ASCII character terminals

• Systems running ASCII terminal emulation software

• Systems with Telnet client software

Ethernet Support

RSC is designed to function in a 10BASE-T network, and the RSC Ethernet port should be connected to a hub operating at 10 Mbps. If RSC does not respond to an Ethernet request, the first thing to check is that connection is to a 10BASE-T hub.

Uninterruptible Power Supply (UPS)

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

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 Microsystems 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 that the following conditions are met:

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

2. All the RSC page_variables (page_info1, page_info2, page_init1, page_init2, page_baud1, and page_baud2) are set correctly and match the settings for your paging service.

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