Cluster Upgrade Guidelines; Performing The Cluster Upgrade - Cisco MDS 9216 Configuration Manual

Chapter 8 Upgrading CSM Software

Cluster Upgrade Guidelines

Be aware of the following guidelines when upgrading clusters:
•
•
•
•
•
•

Performing the Cluster Upgrade

Issue the cluster name cluster-name upgrade svc-system command at the configuration node of the
Step 1
cluster.
If the cluster contains an I/O group with a single node, use the optional force keyword at the end of this
Tip
command.
switch(svc)# cluster name SampleCluster upgrade svc-system
scp://userc@171.69.16.22/auto/andusr/userc/hkrel/VegasSW/build/gdb.sb-avanti/isan/targetfs
/m9000-ek9-csm-svc-mzg.1.3.x.bin
userc@171.69.16.22's password:
m9000-ek9-csm-svc-mz 100% |***************************************|
This process may take few minutes as the config node performs the following checks:
•
•
•
78-16119-01, Cisco MDS SAN-OS Release 1.3
Nodes are updated one at a time. One node from each I/O group is updated before the second node
in any I/O group is updated.
During the update of a node it does not participate in I/O activity in the I/O group. Thus all I/O
activity for the VDisks in the I/O group is directed to the other node in the I/O group by the host
multipathing software. During a node upgrade, the other node in the I/O group will attempt to flush
the cache and change operations to write-through mode. This flush is not guaranteed to be successful
or complete. Should the remaining node in an I/O group experience a failure when its' partner is
being upgraded, then the only valid copy of the modified data in the cache could be lost. If this risk
is unacceptable, then the customer must take steps to ensure that no I/O activity takes place during
the software upgrade.
A 30 minute delay is inserted into the procedure between updating the first and second nodes in each
I/O group. This allows time for the host multipathing software to rediscover paths to the nodes that
were updated first so that when the second set of nodes are updated loss of access does not result.
The update is not committed until all nodes in the cluster have been successfully updated to the new
code level.
When code upgrade starts an entry is made in the event log and another entry is made when the
upgrade completes or fails.
The config node goes down to upgrade to the new software level. This will cause a different node to
become the new config node. At this point, you need to reconnect to the cluster IP address.
If the new SVC software image is compatible with the config node's running switch software and
running SVC software. If any compatibility checks fail, cluster upgrade fails and an appropriate
error message is issued.
If the SVC software image is compatible with the software running on each of the switches where
the other nodes in the cluster reside.
The config node collects the compatibility check result from each node in the cluster and makes sure
that all of them have succeeded. If any of nodes report a check failure, then an error message is
issued with a table displaying all the check failures across all the nodes in the cluster.
Cisco MDS 9000 Family SAN Volume Controller Configuration Guide
Upgrading Clusters
108 MB 01:23
8-3