HP Cisco Nexus 5000 Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS R - Page 22

Performing a Disruptive Upgrade on a Single Supervisor MDS Family Switch

Page 22 highlights

Downgrading Your Cisco MDS SAN-OS Software Image Send documentation comments to [email protected] Performing a Disruptive Upgrade on a Single Supervisor MDS Family Switch Cisco MDS SAN-OS software upgrades are disruptive on the following single supervisor Cisco MDS Family switches: • MDS 9120 switch • MDS 9140 switch • MDS 9216i switch If you are performing an upgrade on one of those switches, you should follow the nondisruptive upgrade path shown in Table 6, even though the upgrade is disruptive. Following the nondisruptive upgrade path ensures that the binary startup configuration remains intact. If you do not follow the upgrade path, (for example, you upgrade directly from SAN-OS Release 2.1(2) or earlier version to SAN-OS Release 3.3(1c)), the binary startup configuration is deleted because it is not compatible with the new image, and the ASCII startup configuration file is applied when the switch comes up with the new upgraded image. When the ASCII startup configuration file is applied, there may be errors. Because of this, we recommend that you follow the nondisruptive upgrade path. Downgrading Your Cisco MDS SAN-OS Software Image This section lists the guidelines recommended for downgrading your Cisco MDS SAN-OS software image and contains the following sections: • General Downgrading Guidelines, page 22 • Downgrading the SSI Image on Your SSM, page 25 General Downgrading Guidelines Use the following guidelines to nondisruptively downgrade your Cisco MDS SAN-OS Release 3.3(1c): • Install and configure dual supervisor modules. • Issue the system no acl-adjacency-sharing execute command to disable acl adjacency usage on Generation 2 and Generation 1 modules. If this command fails, reduce the number of zones, IVR zones, TE ports, or a combination of these in the system and issue the command again. • Disable all features not supported by the downgrade release. Use the show incompatibility system downgrade-image CLI command to determine what you need to disable. • Layer 2 switching traffic is not disrupted when downgrading to Cisco SAN-OS Release 2.1(2) or later. • Use the show install all impact downgrade-image CLI command to determine if your downgrade will be nondisruptive. • Be aware that some features impact whether a downgrade is disruptive or nondisruptive: - Fibre Channel Ports: Traffic on Fibre Channel ports can be nondisruptively downgraded. See Table 8 for the nondisruptive downgrade path for all SAN-OS releases. - SSM: Intelligent services traffic on the SSM, such as SANTap, NASB, and FC write acceleration, is disrupted during a downgrade. SSM Fibre Channel traffic is not. Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(1c) 22 OL-14116-08

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48

Send documentation comments to [email protected]
22
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(1c)
OL-14116-08
Downgrading Your Cisco MDS SAN-OS Software Image
Performing a Disruptive Upgrade on a Single Supervisor MDS Family Switch
Cisco MDS SAN-OS software upgrades are disruptive on the following single supervisor Cisco MDS
Family switches:
MDS 9120 switch
MDS 9140 switch
MDS 9216i switch
If you are performing an upgrade on one of those switches, you should follow the nondisruptive upgrade
path shown in
Table 6
, even though the upgrade is disruptive. Following the nondisruptive upgrade path
ensures that the binary startup configuration remains intact.
If you do not follow the upgrade path, (for example, you upgrade directly from SAN-OS Release 2.1(2)
or earlier version to SAN-OS Release 3.3(1c)), the binary startup configuration is deleted because it is
not compatible with the new image, and the ASCII startup configuration file is applied when the switch
comes up with the new upgraded image. When the ASCII startup configuration file is applied, there may
be errors. Because of this, we recommend that you follow the nondisruptive upgrade path.
Downgrading Your Cisco MDS SAN-OS Software Image
This section lists the guidelines recommended for downgrading your Cisco MDS SAN-OS software
image and contains the following sections:
General Downgrading Guidelines, page 22
Downgrading the SSI Image on Your SSM, page 25
General Downgrading Guidelines
Use the following guidelines to nondisruptively
downgrade your Cisco MDS SAN-OS Release 3.3(1c):
Install and configure dual supervisor modules.
Issue the system
no acl-adjacency-sharing
execute command to disable acl adjacency usage on
Generation 2 and Generation 1 modules. If this command fails, reduce the number of zones, IVR
zones, TE ports, or a combination of these in the system and issue the command again.
Disable all features not supported by the downgrade release. Use the
show incompatibility system
downgrade-image
CLI command to determine what you need to disable.
Layer 2 switching traffic is not disrupted when downgrading to Cisco SAN-OS Release 2.1(2) or
later.
Use the
show install all impact
downgrade-image
CLI command to determine if your downgrade
will be nondisruptive.
Be aware that some features impact whether a downgrade is disruptive or nondisruptive:
Fibre Channel Ports
:
Traffic on Fibre Channel ports
can be nondisruptively downgraded. See
Table 8
for the nondisruptive downgrade path for all SAN-OS releases.
SSM
: Intelligent services traffic on the SSM, such as SANTap, NASB, and FC write
acceleration, is disrupted during a downgrade. SSM Fibre Channel traffic is not.