ServerNet Cluster Manual

Troubleshooting and Replacement Procedures
ServerNet Cluster Manual—520575-003
7-23
Checking Communications With a Remote Node
Checking Communications With a Remote Node
Use the Node Responsive Test action in the TSM Service Application to test
communications with a remote node. This action pings the remote node, verifying
whether or not the node is connected and responding.
To ping a remote node:
1. In the tree pane, right-click the X or Y fabric-to-node resource for the node that you
want to ping, and select Actions. The Actions dialog box appears.
2. From the Actions list, click Node Responsive Test.
3. Click Perform action. The Action Status window shows the progress of the action.
If the action status shows Completed, the action passed. If the action status shows
Failed, the action failed.
4. If the action failed, click Show detail for more information
Methods for Repairing ServerNet Connectivity Problems
ServerNet connectivity problems refer to the inability of one or more processors to
communicate with one or more other processors over a ServerNet path.
Clusters using the split-star or tri-star topologies with G06.14 software (or G06.13 and
the release 3 SPRs that provide G06.14 functionality) support automatic fail-over of
ServerNet traffic on the two-lane or four-lane links. For more information, refer to
Automatic Fail-Over for Two-Lane and Four-Lane Links on page 7-25.
You can use several methods to repair ServerNet connectivity problems. The following
subsections describe these methods:
Switching the SANMAN Primary and Backup Processes to
Repair Connectivity Problems
The SCF PRIMARY PROCESS $ZZSMN command forces a takeover of the SANMAN
primary process. The backup process, upon becoming the new primary, queries all
processors in the node to find the state of ServerNet connections to all other nodes. If
it finds any connections that are down, it initiates a sequence to bring the connections
to an online state.
Procedure Page
Switching the SANMAN Primary and Backup Processes to Repair Connectivity
Problems
7-23
Using the SCF START SERVERNET Command to Repair Connectivity Problems 7-24
Stopping and Starting the ServerNet Cluster Subsystem to Repair Connectivity
Problems
7-24
Aborting and Restarting SNETMON to Repair Connectivity Problems 7-25