ServerNet Cluster Manual
Troubleshooting and Replacement Procedures
ServerNet Cluster Manual—520575-003
7-37
Replacing a Fiber-Optic Cable in a Multilane Link
Replacing a Fiber-Optic Cable in a Multilane Link
Use this procedure to replace a fiber-optic cable in a multilane link between two cluster
switches. Before starting, read this procedure all the way through, especially if your
cluster switches are in different sites.
1. Make sure that interprocessor communication (IPC) connectivity is up between all
nodes on the peer fabric of the suspected bad cable by doing one of the following:
•
If one of the nodes is running SNETMON/MSGMON version T0294AAG (or a
superseding SPR), use the SCF STATUS SUBNET $ZZSCL, PROBLEMS
command to check connectivity on the peer fabric. This command reports
connectivity problems on all nodes. To determine your SNETMON/MSMGMON
version, see Table 2-9, Checking SPR Levels.
•
If none of the nodes are running T0294AAG (or a superseding SPR), use the
SCF STATUS SUBNET $ZZSCL command on all nodes to check the peer
fabric.
If connectivity is down on the peer fabric, repair the problem, if possible, before
attempting to replace a multilane link. If necessary, refer to the Troubleshooting
Procedures on page 7-1.
2. Label the connectors of the replacement cable with the cluster switch names and
port numbers to which the suspected bad cable is connected (such as X1, port 8 at
one end and X2, port 10 at the other end). If necessary, refer to Figure 1-17 for
connections in a four-lane link and Figure 1-18 for connections in a two-lane link.
3. Physically route the replacement cable along the same path as the suspected bad
cable.
4. Disconnect the suspected bad cable at both ends.
5. If the connectors on the replacement cable have dust caps, remove the dust caps
and install them on the connectors of the suspected bad cable.
6. Connect the replacement cable as labeled in Step 2.
7. Confirm that the link-alive LED lights at both ends. The link-alive LEDs should light
within a few seconds. If the link-alive LEDs do not light:
•
Try reconnecting the cable, using care to align the key on the cable plug with
the PIC connector.
•
If possible, try connecting a different cable.
Note. You can determine the ServerNet nodes that are affected by the loss of a specific
multilane link by referring to Connections Between Cluster Switches on page 1-30. Figure 1-17
shows the routing of ServerNet packets across four-lane links, and Figure 1-18 shows the
routing of ServerNet packets across two-lane links.