ServerNet Cluster Web

DELAY 5
START PROCESS $ZZKRN.#ZZSMN
Aborting and restarting SANMAN causes the nodes to correctly
pick up the high node numbers (9 through 16) and configure the
X and Y NNAs with these new numbers.
Workaround: To avoid this problem, use the G06.13 version of
the ServerNet Cluster Manual (520440-001). The procedure has
been corrected in the G06.13 manual.
If you do not have access to the G06.13 manual, perform the
"Steps for Merging Two ServerNet Clusters" in Section 4 of the
ServerNet Cluster Manual. However, before running the guided
procedure for adding a cluster switch on the cluster that will use
the high (9 through 16) ServerNet node numbers (step 5 of the
documented procedure), perform the following steps on all nodes
of the cluster to be configured as the X2/Y2 cluster. These steps
ensure an orderly shutdown of ServerNet communications on the
cluster. The shutdown is recommended because the ServerNet
node numbers will change from the 1-8 range to the 9-16 range
when the cluster is configured as the X2/Y2 cluster.
1. On all nodes of the X2/Y2 cluster, stop any applications that
depend on ServerNet cluster connectivity.
2. On all nodes of the X2/Y2 cluster, abort all
Expand-over-ServerNet lines.
3. On all nodes of the X2/Y2 cluster, use the SCF STOP SUBSYS
$ZZSCL command to ensure an orderly shutdown of ServerNet
communications.
From any node on the X2/Y2 cluster, run the guided procedure
for adding a cluster switch, as documented in the G06.12
ServerNet Cluster Manual. After running the guided procedure,
perform the following steps on all nodes of the X2/Y2 cluster:
1. On all nodes of the X2/Y2 cluster, use the SCF START SUBSYS
$ZZSCL command to bring up direct ServerNet connectivity
between the nodes.
2. On all nodes of the X2/Y2 cluster, start the
Expand-over-ServerNet lines to all other nodes.
3. If desired, start any applications that utilize ServerNet
connectivity to nodes within the X2/Y2 cluster.