Before attempting to downgrade to an earlier software release, follow these guidelines:
-
The only supported method of downgrading a Nexus 9000 Series switch is to utilize the install all command. Changing the boot
variables, saving the configuration, and reloading the switch is not a supported method to downgrade the switch.
Disable the Guest Shell if you need to downgrade from NX-OS Release 9.3(x) to an earlier release.
-
Performing an ISSU downgrade from NX-OS Release 9.3(x) to Release 7.0(3)I4(1) with an FCoE (Fiber Channel over Ethernet) NPV
(N-port Virtualization) configuration causes the port channel to crash with a core file:
[################ ] 38%2016 Apr 18 20:52:35 n93-ns1 %$ VDC-1 %$ %SYSMGR-2-
SERVICE_CRASHED: Service "port-channel" (PID 14976) hasn't caught signal 11 (core will
be saved)
-
ISSU (non-disruptive) downgrade is not supported
-
On Nexus 9500 switches with N9508-E2 Fabric module, downgrade from any 9.x or 10.x supported releases to any unsupported releases
of 7.x is not supported.
-
When downgrading from the NX-OS Release 9.3(x) to earlier releases, any ACL with the statistics per-entry command enabled
and applied as RACL needs the statistics per-entry command removed from the running configuration before downgrading. Otherwise,
the interfaces on which this ACL is applied as a RACL will be error disabled after the downgrade.
-
Prior to downgrading a Nexus 9500-series switch, with -FX or -FX+EX line cards, from NX-OS Release 10.1(x) to earlier releases
(9.2(x) or 7.x), the TCAM region that applies to NetFlow (ing-netflow) should be carved to zero (0) using the following command:
hardware access-list tcam region ing-netflow 0
The configuration change is required because the default ing-netflow TCAM region in 9.3(1) and onwards is 512 while the default
in 9.2(x) and earlier is 0.
-
When downgrading from the NX-OS Release 10.1(x) to a release prior to 9.3(x), make sure that the ACL TCAM usage for ingress
features does exceed the allocated TCAM space in the absence of the label sharing feature. Label sharing is a new feature
in NX-OS Release 9.3(x). Otherwise, interfaces with RACLs that could not fit in the TCAM will be disabled after the downgrade.
-
Software downgrades should be performed using the
install all
command. Changing the boot variables, saving the configuration, and reloading the switch is not a supported method to downgrade
the switch.
-
The following limitation applies to Nexus platform switches that support Trust Anchor Module (TAM):
The TACACS global key cannot be restored when downgrading from NX-OS Release 9.3(3) and higher to any earlier version. TAM
was updated to version-7 in 9.3(3), but earlier NX-OS versions used TAM version-3.
-
iCAM must be disabled before downgrading from Release 9.2(x) or Release 9.3(x) → 7.0(3)I7(1). Only Release 9.3(1) → Release
9.2(4) can be performed if iCAM is enabled.
-
Beginning with NX-OS Release 9.3(3), new configuration commands exist for SRAPP (with sub-mode options for MPLS and SRTE).
The SRAPP configuration on the switch running release 9.3(3) (or later) will not be present if the switch is downgraded to
an earlier release.
-
On devices with dual supervisor modules, both supervisor modules must have connections on the console ports to maintain connectivity
when switchovers occur during a software downgrade. See the Hardware Installation Guide for your specific chassis.
-
Cisco NX-OS automatically installs and enables the guest shell by default. However, if the device is reloaded with a NX-OS
image that does not provide guest shell support, the existing guest shell is automatically removed and a %VMAN-2-INVALID_PACKAGE
message is issued. As a best practice, remove the guest shell with the guestshell destroy
command before downgrading to an earlier NX-OS image.
-
You must delete the switch profile (if configured) when downgrading from a NX-OS release that supports switch profiles to
a release that does not. For more information, see the Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 10.1(x).
-
Software downgrades are disruptive. In-service software downgrades (ISSDs), also known as non-disruptive downgrades, are not
supported.
-
When downgrading from NX-OS Release 9.3(3) or later to 7.0(3)I7(7), disable BFD for the BGP neighbor prefix peer using the
no bfd command.
-
While downgrading from the NX-OS Release 10.2(1)F or higher to an earlier release, the install all command is blocked when the delay config is present in track list Boolean/weight.
-
While performing ISSD from NX-OS Release 10.2(3)F to NX-OS Release 10.2(2)F with epbr L2 applied on interfaces, remove the policies from interfaces before performing ISSD to avoid the duplicate tracks issue.
-
Beginning with NX-OS Release 10.2(3)F, if you have configured the lldp chassis-id switch command, then you must disable the command before performing ISSD.
-
Beginning with 10.2(3)F, although application of ePBR policy to access ports is supported, downgrading with this configuration
is not recommended.
-
When feature ngmvpn is enabled and a disruptive downgrade is performed from NX-OS Release 10.3(2)F to NX-OS Release 10.3(1)F,
although a few VRFs are missing from the show run output, this is only a display issue, and has no functional impact.
-
When a switch is downgraded from NX-OS Release 10.3(3)F or 10.4(1)F to a version that supports both Native and LXC modes, the switch always goes to Native mode even if the upgrade was done from
LXC mode. To keep the mode persistent after a downgrade, ensure that you perform the downgrade in the following sequence:
Note
|
-
The following sections are applicable only to Nexus 9300-FX3 and 9300-GX platform switches.
-
When system comes up in native mode on downgrade, boot mode lxc is removed from configuration.
|
-
When you downgrade from NX-OS Release 10.4(2)F to any earlier releases until 10.3(2)F (included), N9K-C9400-SW-GX2A Sup card
ports 2xSFP Eth10/1-2 are not supported.
-
The N9K-C92348GC-FX3 switch does not support downgrade from NX-OS Release 10.4(4)M to any lower releases as 10.4(4)M is the
first supported release for this switch.
-
During downgrade, where both source and target images support Type-6 encryption, while performing device reload, if ASCII
replay is triggered without binary restore, primary key gets lost. The primary key must be reconfigured after device reload.
Use the key config-key ascii command to reconfigure the primary key and avoid encryption issues. However, downgrade with binary restore retains the primary
key after the reboot, provided both source and target images support Type-6 encryption.
If you downgrade the system from an image that supports Type-6 encryption to an image that does not support Type-6 encryption,
compatibility check fails.
Feedback