Sun Cluster 3.1 - 3.2 Hardware Administration Manual for Solaris OS

Testing Cluster Interconnect Redundancy

This section provides the procedure for testing cluster interconnect redundancy.

ProcedureHow to Test Cluster Interconnects

Before You Begin

This procedure provides the long forms of the Sun Cluster commands. Most commands also have short forms. Except for the forms of the command names, the commands are identical. For a list of the commands and their short forms, see Appendix A, Sun Cluster Geographic Edition Object-Oriented Commands.

To perform this procedure, become superuser or assume a role that provides solaris.cluster.read and solaris.cluster.modify RBAC authorization.

  1. Disconnect one of the cluster transport cables from a node in the cluster.

    Messages similar to the following appear on the consoles of each node and are logged in the /var/adm/messages file.


    Nov  4 08:27:21 node1 genunix: WARNING: ce1: fault detected external to device; service degraded
    Nov  4 08:27:21 node1 genunix: WARNING: ce1: xcvr addr:0x01 - link down
    Nov  4 08:27:31 node1 genunix: NOTICE: clcomm: Path node1:ce1 - node1:ce0 being cleaned up
    Nov  4 08:27:31 node1 genunix: NOTICE: clcomm: Path node1:ce1 - node1:ce0 being drained
    Nov  4 08:27:31 node1 genunix: NOTICE: clcomm: Path node1:ce1 - node1:ce0 being constructed
    Nov  4 08:28:31 node1 genunix: NOTICE: clcomm: Path node1:ce1 - node1:ce0 errors during initiation
    Nov  4 08:28:31 node1 genunix: WARNING: Path node1:ce1 - node1:ce0 initiation 
    encountered errors, errno = 62.
      Remote node may be down or unreachable through this path.
  2. Verify that Sun Cluster has registered that the interconnect is down.

    Enter one of the following commands and verify that the interconnect path displays as Faulted.

    • If you are using Sun Cluster 3.2, use the following command:


      # clinterconnect status
      
    • If you are using Sun Cluster 3.1, use the following command:


      # scstat -W
      
  3. Reconnect the cluster transport cable

    Messages similar to the following appear on the consoles of each node and are logged in the /var/adm/messages file.


    Nov  4 08:30:26 node1 genunix: NOTICE: ce1: fault cleared external to device; service available
    Nov  4 08:30:26 node1 genunix: NOTICE: ce1: xcvr addr:0x01 - link up 1000 Mbps full duplex
    Nov  4 08:30:26 node1 genunix: NOTICE: clcomm: Path node1:ce1 - node1:ce0 being initiated
    Nov  4 08:30:26 node1 genunix: NOTICE: clcomm: Path node1:ce1 - node1:ce0 online
  4. Verify that Sun Cluster has registered that the interconnect is up.

    Enter one of the following commands and verify that the interconnect path displays as Online.

    • If you are using Sun Cluster 3.2, use the following command:


      # clinterconnect status
      
    • If you are using Sun Cluster 3.1, use the following command:


      # scstat -W
      
  5. Repeat Step 1 through Step 4 on each cluster transport cable in the node.

  6. Repeat Step 1 through Step 5 on each node in the cluster.