Sun(TM) Remote System Control (RSC) Release Notes
=================================================
Version 1.0
Firmware Version 1.12
November 16, 1998
Part Number 805-5681-12
Hardware and Software Configurations Supported for RSC
======================================================
Supported Server:
Sun(tm) Enterprise(tm) 250 server only, running the Solaris(tm) 7
or Solaris 2.6 5/98 operating environment.
The Sun Enterprise 250 flash PROM must be updated to version 3.7.7
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 systems running the Solaris 7 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
Sun JDK 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. The required version for the Solaris 2.6
operating environment is available at http://www.sun.com/solaris/java.
Sun JDK is included in the install package for Windows clients.
Supported CLI Clients:
- ASCII character terminals
- Systems running ASCII terminal emulation software
- Systems with telnet client software
Uninterruptible Power Supply (UPS):
An American Power Conversion SmartUPS 1000 with PowerChute plus 4.2.2
software was used for testing.
SunVTS:
To run the SunVTS test for RSC on systems running the Solaris 2.6 5/98
operating environment, you must install the unbundled rsctest package.
This package is available for download from the RSC Web page at
http://sunsolve2.sun.com/sunsolve/E250_RSC/, and is also provided
on the Sun Enterprise 250 Supplement CD. The rsctest package is already
included in the Solaris 7 operating environment.
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
============
1) 4151918: The RSC subtests do not provide adequate failure information.
2) 4168110: The RSC GUI "OK" button in dialog boxes cannot be translated.
3) 4171924: The RSC GUI occasionally reports invalid exceptions when you
Logout or Exit.
4) 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.
5) 4167862: A loghistory error is reported when the "index -n" value
you specify is greater than the number of lines in the buffer.
6) 4171929: RSC sometimes reports a fan failure erroneously after a
thermal shutdown.
7) 4172574: The CLI reports a DC Power Failure when the host is powered off.
8) 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.
9) 4167651: RSC default configuration settings for pagers do not match
modem configuration settings suggested in documentation.
10) 4152840: RSC shell commands do not issue a confirmation query before
resetting the host system.
11) 4171431: The GUI event log output differs from the CLI loghistory output.
12) 4170988: The RSC GUI Back button for the first instance of Help does not
return you to the previous view.
13) 4172337: The error message displayed for an attempted third telnet or
fifth user session needs improvement.
14) 4162419: In the Windows operating environment, the RSC GUI goes to the
background when you cancel an operation after an error message.
15) 4158400: The message "[Loaded DTD html32 in 142ms]" appears when the
RSC Help file is displayed.
16) 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 " title.
17) 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.
18) 4159618: A GUI reset request and the resulting reset event are recorded
in the incorrect order in the RSC event log.
19) 4159562: The telnet connection resets intermittently when you try to
connect to the RSC console from the GUI.
20) 4159564: The Java Runtime Environment (JRE) may crash in the Windows 95
operating environment when you modify an RSC user account.
21) 4172331: In the RSC GUI Serial Port settings, there is a typo in the error
message for Invalid IP Address.
22) 4159135: The RSC GUI has no option which shows the information returned
by the CLI shownetwork command.
23) 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.
24) 4173022: The escape sequence for exiting from the RSC console does not
work if the escape_char variable is set to "^?".
25) 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.
|
Select pages from WAGONEERS.COM:
Buy this FSJ decal... ...use PayPal to pay for it! |
AMSOIL synthetic lubricants and filters (please use customer #283461)
Shop AMAZON.com from wagoneers.com!
| |||||||