RSC Issues for Sun Fire 280R Servers Only

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

Soft Reset With xir Does Not Work Correctly (BugID 4361396, 4411330)

The xir command does not bring the server to the ok prompt as expected. This issue may have been resolved for your server type; see your hardware platform release notes.

Boot Sequence Sometimes Bypasses RSC (BugID 4387587)

In rare instances, the system may bypass the RSC card during startup. To check whether the system booted and is online, use the ping command to see if the card is alive, or log in using telnet or rlogin. If the system is not connected to the network, establish a tip connection to the system. (Be sure that console I/O is not directed to the RSC card.) Use the tip connection to view boot messages on the troubled system, or reboot the system. For help in diagnosing the problem, see your hardware Owner's Guide.

False Drive Fault Reported at Power On (BugID 4343998, 4316483)

When you power on the system, it may report a false internal drive fault that is recorded in the Sun Remote System Control (RSC) log history.

If the error is reported by RSC, you should disregard the report if the system boots successfully to the Solaris operating environment. In most cases the erroneous fault does not reappear. You can verify the disk after the boot process by using the fsck utility.

Any disk drive error message reported by the Solaris operating environment is a real disk drive error.

If a disk fault is reported at the ok prompt and the system fails to boot to the Solaris operating environment, there may be a problem with the disk drive. Test the disk drive with the OpenBoot Diagnostics tests documented in the “Diagnostics, Monitoring, and Troubleshooting” chapter in the Sun Fire 280R Server Service Manual.

Command rscadm resetrsc Fails (BugID 4374090)

After a cold restart or after powering on the system, the RSC command rscadm resetrsc fails; this is a known condition. You need to reset the host system for the command to function correctly.

There are three ways you can reset the host. Use one of the following commands:

• At the ok prompt, execute the reset-all command.

• At the RSC command-line interface (CLI) prompt, issue the reset command.

• At the Solaris CLI prompt, issue the reboot command.

The RSC rscadm resetrsc command will now function correctly.