ServerNet Cluster Manual

Upgrading a ServerNet Cluster
ServerNet Cluster Manual—520575-003
4-29
Fallback for Upgrading ServerNet Cluster Software
Without a System Load to Obtain G06.12
12. On all nodes, use SCF to make sure direct ServerNet communication is possible
on both fabrics between all nodes connected to the cluster switches:
>SCF STATUS SUBNET $ZZSCL
13. On all nodes connected to the cluster switch, use SCF to ensure that the
ServerNet node numbers used by the MSEB port and ServerNet II Switch port are
consistent:
>SCF STATUS CONN $ZZSMN
In the SCF display, check that the “SvNet Node Number” values for the MSEB port
and switch port are the same. If the values are not the same, use one of the
following recovery measures:
•
Use the SCF PRIMARY PROCESS $ZZSMN command to force a takeover of
the SANMAN process in the problem node.
•
Disconnect and reconnect the MSEB-to-switch fiber-optic cable on the affected
fabric.
14. If the requisite SPRs are to be removed, make sure T0569AAA has been
downloaded to all cluster switches prior to removing the requisite SPRs. G06.12
contains T0502AAE and T0569AAB. If necessary, you can use T0569AAA with
G06.12 instead of T0569AAB, but only in a star topology, which supports up to
eight ServerNet nodes.
15. If falling back to an earlier version of the operating system (G06.09, for example),
perform the following optional step:
a. Shut down any nodes for which a fallback to an earlier version of the operating
system is desired.
b. On the nodes that were shut down, load the system using the down-rev
operating system.
Note. Using SCF STATUS SUBNET $ZZSCL requires T0294AAA or a superseding SPR.
If remote passwords are configured, you can issue the SCF STATUS SUBNET $ZZSCL
command for a remote node (for example, \REMOTE) from the local node as follows:
SCF STATUS SUBNET \REMOTE.$ZZSCL
This command eliminates the need to establish a logon window for each node.