RSC Issues for Sun Enterprise 250 Servers Only

This section describes issues that affect RSC running on Sun Enterprise 250 servers only. See the Sun Enterprise 250 Server Product Notes for other Sun Enterprise 250 server issues.

Increased Number of RSC User Accounts Not Supported

Support for a maximum of 16 RSC user accounts has been added for RSC 2.2. However, Sun Enterprise 250 servers continue to be limited to four RSC user accounts because of hardware limitations.

Do Not Run OpenBoot PROM fsck Command From the RSC Console (BugID 4409169)

Do not issue the fsck command from the redirected RSC console.

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 OpenBoot PROM fsck command directly.

Do Not Run OpenBoot PROM boot -s Command From the RSC Console (BugID 4409169)

The command boot -s does not work from the RSC console.

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.

Change to the serial_hw_handshake Variable Requires a System Reboot (BugID 4145761)

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.

Power Supply Alerts Display Incorrect Index in the GUI (BugID 4521932)

In the Sun Enterprise 250, the power supplies are numbered 0 and 1, but the RSC GUI refers to them as Power Supply 1 and Power Supply 2 in the event log and in alerts.