Repairing a Lost SPARCstorage Array Connection

When a connection from a SPARCstorage Array to one of the hosts fails, the failure is probably due to a fiber optic cable, an SBus FC/S card, or an FC/OM module.

The host on which the failure occurred will begin generating errors when the failure is discovered. Later accesses to the SPARCstorage Array will generate additional errors. The host behaves as though power had been lost to the SPARCstorage Array.

I/O operations from the other nodes in the cluster are unaffected by this type of failure.

To diagnose the failure, inspect the SPARCstorage Array's display. The display will show whether the A or B connection has been lost. Use the procedures for testing the FC/S card and FC/OM modules in the service manual for your Sun Cluster node to determine which component failed. For hardware debugging, free up one Sun Cluster node and the SPARCstorage Array that appears to be down.

How to Repair a Lost SPARCstorage Array Connection

1. Prepare the Sun Cluster system for component replacement.

   Depending on the cause of the connection loss, prepare the Sun Cluster system with one of the following procedures.

   • If the failed component is an FC/S card or the FC/OM module for an FC/S card, see Chapter 7, Administering Server Components, to prepare the Sun Cluster node for power down.

   • If the problem is a bad fiber optic cable, the volume management software will have detected the problem and prepared the system for cable replacement.

   • If the SPARCstorage Array FC/OM module has failed, use either the procedure "How to Take a SPARCstorage Array Tray Out of Service (Solstice DiskSuite)" or "How to Take a SPARCstorage Array Tray Out of Service (VxVM)", on each SPARCstorage Array tray to prepare the entire SPARCstorage Array.

2. Replace the failed component.

   If the fiber optic cable, SBus FC/S card, or an FC/OM module fails, refer to the service manual for your Sun Cluster node for detailed instructions on replacing them.

3. Recover from volume management software errors.

   Use the procedures described in "Recovering From Power Loss".