How to Test Cluster Interconnects

1. Disconnect one of the cluster transport cables from a node that masters a device group.

   Messages appear on the consoles of each node, and error messages appear in the /var/adm/messages file. If you run the scstat(1M) command, the Sun Cluster software assigns the cluster transport path you disconnected a faulted status. This fault does not result in a failover.

2. Disconnect the remaining cluster transport cable from the primary node you identified in Step 1.

   Messages appear on the consoles of each node, and error messages appear in the /var/adm/messages file. If you run the scstat command, the Sun Cluster software assigns the cluster transport path you disconnected a faulted status. This action causes the primary node to go down, resulting in a partitioned cluster.

   For conceptual information on failure fencing or split brain, see Sun Cluster 3.0 Concepts.

3. On another node, run the scstat command to verify that the secondary node took ownership of the device group mastered by the primary.

   # scstat

4. Reconnect all cluster transport cables.

5. Boot the initial primary, which you identified in Step 1, into cluster mode.

   {0} ok boot

   If you have the device group failback option enabled, skip Step 7 because the system boot process moves ownership of the device group back to the initial primary. Otherwise, proceed to Step 7 to move ownership of the device group back to the initial primary. Use the scconf -p command to determine if your device group has the device group failback option enabled.

6. Verify that the Sun Cluster software assigned each cluster transport path you reconnected in Step 4 a path online status.

   # scstat

7. If you do not have the device group failback option enabled, move ownership of the device group back to the initial primary.

   # scswitch -S -h nodename