ServerNet Cluster Manual

Upgrading a ServerNet Cluster
ServerNet Cluster Manual—520575-003
4-52
Fallback for Upgrading Software to Obtain G06.14
Functionality
10. If you need to fall back to earlier firmware, use the TSM Service Application to
download the T0569AAB (or T0569AAA) M6770CL configuration to the nearest X-
fabric cluster switch. For detailed steps, refer to Using the TSM Service Application
to Download the ServerNet II Switch Firmware or Configuration on page 4-99.
Otherwise, skip this step.
11. If you fell back to earlier switch firmware from T0569AAE in Step 10, power cycle
the ServerNet II Switch subcomponent of the nearest Y-fabric cluster switch:
a. On the ServerNet II Switch front panel, press the Power On button to remove
power. (You must fully depress the button until it clicks.)
b. Wait at least one minute.
c. Press the Power On button again to reapply power to the ServerNet II Switch.
12. Use the TSM Service Application to verify the operation of the Y-fabric cluster
switch.
13. If the cluster is connected in a split-star topology, repeat Step 2 through Step 6 on
the external ServerNet Y fabric of the other star group of the split-star topology.
14. On all nodes, use SCF to make sure that direct ServerNet communication is
possible on both fabrics between all nodes connected to the cluster switches:
>SCF STATUS SUBNET $ZZSCL
15. 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.
Note. Using the SCF STATUS SUBNET $ZZSCL command 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) on the local node
as follows:
SCF STATUS SUBNET \REMOTE.$ZZSCL
This command eliminates the need to establish a logon window on each node. If
T0294AAG (or a superseding SPR) is applied, use the following command:
SCF STATUS SUBNET $ZZSCL, PROBLEMS