ServerNet Cluster Manual
Adding or Removing a Node
ServerNet Cluster Manual—520575-003
6-6
Moving ServerNet Cables to Different Ports on the
ServerNet II Switches
To move the fiber-optic cables at the ServerNet II Switches:
1. Make sure an unused port in the range 0 through 7 is available on the X-fabric and 
Y-fabric ServerNet II Switches. You must use the same port number on both 
switches.
2. Complete the Planning Form for Moving ServerNet Cables. See the Sample 
Planning Form for Moving ServerNet Cables on page 6-9. A blank copy of this form 
is included in Appendix B, Blank Planning Forms. To complete the form:
a. Record the system name and Expand node number of the node whose 
ServerNet cables will be moved. You can use the TSM Service Application to 
collect this information.
b. Record the old and new ServerNet II Switch port connections.
c. For the node whose ServerNet cables will be moved, list the Expand-over-
ServerNet lines that must be aborted before removing the node from the 
cluster. You can use the Expand subsystem SCF LISTDEV command to 
identify the currently configured Expand-over-ServerNet lines:
-> LISTDEV TYPE 63, 4
d. For all other nodes in the cluster, list the Expand-over-ServerNet line that must 
be aborted for the node being removed. You can use the SCF INFO 
PROCESS $NCP, LINESET command to identify the line configured for a 
specific node:
-> INFO PROCESS $NCP, LINESET
3. If your applications might be affected and an adequate alternate Expand line is not 
available, shut down all applications that depend on the Expand-over-ServerNet 
line-handler processes.
4. Identify and label the cables you want to move to the unused ports. Labeling the 
cables reduces the likelihood of moving the wrong cables.
5. Use the following commands to remove the ServerNet node (the node whose 
cables will change ports) temporarily from the ServerNet cluster:
a. On the node being removed, use the Expand subsystem SCF ABORT LINE 
command to abort the Expand-over-ServerNet lines to all other nodes in the 
cluster. For example:
-> ABORT LINE $SC012
-> ABORT LINE $SC013
-> ABORT LINE $SC014
-> ABORT LINE $SC015
-> ABORT LINE $SC016
-> ABORT LINE $SC017
Note. You do not have to stop or delete the line-handler processes (devices).










