Sun Fire 3800/4800/4810/6800 System Controller May Experience a Deadlock During Execution of the "setfailover off" Command |
|
| Category : | Availability |
| Release Phase : | Resolved |
| Product : | Sun Fire 3800 Server Sun Fire 4800 Server Sun Fire 4810 Server Sun Fire 6800 Server
|
| Bug Id : | 4805222
|
| Date of Workaround Release : | 31-JUL-2003
|
| Date of Resolved Release : | 25-NOV-2003
|
Impact
A deadlock in the System Controller Application (ScApp) may occur when the "setfailover off" command is issued. The System Controller (SC) failover can hang the command line interface and eventually the SC which may require a system reboot.
Contributing Factors
This issue can occur in the following releases:
SPARC Platform
-
Sun Fire 3800/4800/4810/6800 with firmware (ScApp) 5.13.x
-
Sun Fire 3800/4800/4810/6800 with firmware (ScApp) 5.14.x
-
Sun Fire 3800/4800/4810/6800 with firmware (ScApp) 5.15.1 and 5.15.2
Use the "showsc -v" command to display the firmware version of the System Controller.
This issue is most likely to occur when the "setfailover off" command is used while the SC private link is down. The "private link" is the serial port communication between the two SC's.
Note: Systems with firmware 5.11.x and 5.12.x are not affected by this issue.
Symptoms
Should the described issue occur, the SC will not respond.
Workaround
There is no workaround. To recover from this issue, reboot the SC by pressing the reset button on the SC board.
If the spare SC is not responsive, press the reset button on the spare SC.
If the master SC is not responsive, do the following:
-
Schedule a maintenance window
-
Bring down all domains in the platform
-
Press the reset button on the master SC
-
When the master SC returns, recover the domains
Resetting the SC may cause the system to reboot.
Resolution
This issue is addressed in the following releases:
-
Sun Fire 3800/4800/4810/6800 with firmware (ScApp) 5.15.3 (as delivered in patch 112884-04) or later
Modification HistoryDate: 25-NOV-2003
-
Updated Resolution section
-
State: Resolved
AttachmentsThis solution has no attachment