Specifications

6-4 Sun StorEdge A1000 and A3x00/A3500FC Best Practices Guide November 2002
Upon receiving the mode select, the controller will:
Attempt to quiesce itself and its pair.
New commands to either of the controllers will terminate with a check condition
indicating that quiescence is in progress.
Write the new controller information to DacStore.
Hold the alternate controller in reset.
Reset the drive buses.
Reconfigure to become the active controller in active/passive mode.
Return status to the host for the mode select command.
The alternate controller is held in a hardware reset state, and is inaccessible to and
from the host.
6.1.3 Replacing a Failed Controller
Note A controller that “owns” logical units should not be hot swapped. You
should either fail the controller prior to removal (preferable), or switch the controller
to active/passive mode.
Refer to FIN I0709 and Section 5.2.6, “Controller Card Guidelines” on page 5-12 for
more information on NVSRAM in the controllers.
A controller held in a hardware reset state for example failed, will have all of its
LEDs on. A passive controller in the active/passive mode flashed a pattern of 0xEE
or 0x6E/0xEE (module profile will indicate if it in passive mode).
When a failed controller is replaced, the new controller will not be automatically be
made operational. It will remain in the hardware reset state (failed) until the good
alternate controller is directed to release it from this state.
A failed controller is unfailed when it is released from the hardware reset state. This
is done to allow the host to perform diagnostics on a previously failed controller, or
to release a newly replaced controller from reset.
If you have a controller failure and you are using the Recovery Guru, it is very
important to follow every single step as displayed through the popup windows
during the recovery process. Failure to do so can cause further problems with your
RAID module. Refer to Section 2.6.1, “Cluster Information” on page 2-10 for
guidelines when replacing a controller within a cluster environment.
After you have brought your controller back online, do a module profile and make
sure that the failed controller is in active mode and not in passive mode. If it is in
passive mode, go through the maintenance application and bring that controller