ServerNet Cluster Manual

Troubleshooting and Replacement Procedures
ServerNet Cluster Manual—520575-003
7-5
Software Problem Areas
The TSM Service
Application shows
the remote node
name as
\Remote_Node_\n
nn, where nnn is
the Expand node
number.
Verify that the Expand-over-ServerNet line-
handler processes between the local node and
the remote node are up. See Troubleshooting
Expand-Over-ServerNet Line-Handler
Processes and Lines on page 7-21.
ServerNet
Communication
The TSM Service
Application shows
the remote node
name as
\UNKNOWN_Re
mote_\Node_n,
where n is the
ServerNet node
number.
Verify that SNETMON is operating properly on
the remote node. See Troubleshooting
SNETMON on page 7-17.
The TSM Service
Application shows
the Switch-to-
Node link as X | Y
Fabric_to_\nnn,
where nnn is the
Expand node
number.
Verify that the Expand-over-ServerNet line-
handler processes between the local node and
the remote node are up. See Troubleshooting
Expand-Over-ServerNet Line-Handler
Processes and Lines on page 7-21.
The TSM Service
Application shows
the Switch-to-
Node link as X | Y
Fabric_to_\Node_
n, where n is the
ServerNet node
number.
Verify that SNETMON is operating properly on
the remote node. See Troubleshooting
SNETMON on page 7-17.
Communication
between a cluster
switch and a local
or remote node is
disrupted.
Use TSM to check for alarms and repair actions
for the Switch-to-Node link. See Using TSM
Alarms on page 7-12.
Expand-Over-
ServerNet Line-
Handler Processes
and Lines
Communication
between the local
node and a
remote node is
disrupted.
See Troubleshooting Expand-Over-ServerNet
Line-Handler Processes and Lines on
page 7-21.
Table 7-1. Software Problem Areas (page 3 of 3)
Problem Area Symptom Recovery