ServerNet Cluster 6780 Operations Guide (G06.28+, H06.05+)

Troubleshooting and Replacement Procedures
ServerNet Cluster 6780 Operations Guide—525606-003
3-18
Checking Communications With a Remote Node
Checking Communications With a Remote Node
Use the Node Responsive Test action in the OSM Service Connection 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 Switch Port for the node that you want to
ping, and select Actions. The Actions dialog box appears.
2. From the Actions drop-down 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.
You can use several methods to repair ServerNet connectivity problems. These
subsections describe these methods:
Switching the SANMAN Primary and Backup Processes
The SCF PRIMARY PROCESS $ZZSMN command forces a takeover of the SANMAN
primary process. The backup process, upon becoming the new primary, queries the
switches connected to the node and attempts to program any NNA PICs that are not
programmed.
The SCF PRIMARY PROCESS $ZZSMN command is a noninvasive command. It
does not cause the SANMAN process to stop running, and it does not cause any
ServerNet connectivity that is already up to go down.
Procedure Page
Switching the SANMAN Primary and Backup Processes
3-18
Switching the SNETMON Primary and Backup Processes 3-19
Using the SCF START SERVERNET Command 3-19
Stopping and Starting the ServerNet Cluster Subsystem 3-19
Aborting and Restarting SNETMON 3-20