ServerNet Cluster 6780 Operations Guide (G06.24+, H06.03+)

Troubleshooting and Replacement Procedures
ServerNet Cluster 6780 Operations Guide—525606-002
3-3
Software Problem Areas
ServerNet
communication
Communication
on an external
fabric is disrupted.
Use OSM to check for alarms and repair actions
for the External Fabric resource. See Using
OSM Alarms on page 3-11.
Use the Node Connectivity ServerNet Path Test.
See Checking the External ServerNet X and Y
Fabrics on page 3-23.
Communication
on an external
fabric is disrupted
by:
•
BTE timeouts
•
CRC
checksum
errors
•
TPB errors
These symptoms
appear in event
messages or
statistics.
One of the fiber-optic cable connections might
be faulty. Reseat or replace the fiber-optic cable
connecting the MSEB with the switch port. See
Replacing a Fiber-Optic Cable Between an
MSEB and a Switch-to-Node Port on page 3-31.
ServerNet
Communication
Communication
with a remote
node is disrupted.
Use OSM to check for alarms and repair actions
for the Remote Node resource. See Using OSM
Alarms on page 3-11.
Verify that SNETMON is operating properly. See
Troubleshooting SNETMON
on page 3-13.
Verify that SANMAN is operating properly. See
Troubleshooting SANMAN
on page 3-15.
Perform the Node Responsive Test. Checking
Communications With a Remote Node on
page 3-18.
The OSM Service
Connection 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 3-16.
Table 3-1. Software Problem Areas (page 2 of 3)
Problem Area Symptom Recovery