HP Cisco Nexus 5000 Cisco Nexus 5000 Series Release Notes Release 4.1(3)N1(1) - Page 6

Upgrading from Cisco NX-OS 4.0(1a)N1-Based Releases to 4.1(3)N1-Based Releases, Downgrading

Page 6 highlights

Cisco NX-OS Release 4.1(3) N1(1) Upgrade/Downgrade Issues Send documentation comments to [email protected] Upgrading from Cisco NX-OS 4.0(1a)N1-Based Releases to 4.1(3)N1-Based Releases When you upgrade your Cisco Nexus 5000 Series switch from Cisco NX-OS 4.0(1a)N1-Based Releases to 4.1(3)N1-Based Releases, the following occurs: • QoS configuration will be automatically converted to the new syntax • If an ACL has more than 549 ACEs then the ACL fails to get applied. This is due to a new limit on the number of ACEs in an ACL • The Interface fcoe mode on command is deprecated. Alternatively, you can contact Cisco Customer Support for help with upgrading and converting your configuration to the new format. Downgrading from Cisco NX-OS 4.1(3)N-Based Releases • Downgrade is only supported for the following releases: - Cisco NX-OS 4.0(1a)N1(1) release - Cisco NX-OS 4.0(1a)N1(1a) release - Cisco NX-OS 4.0(1a)N2(1) release - Cisco NX-OS 4.0(1a)N2(1a) release • Install all will warn of all configurations that need be undone before proceeding. Note Not all QoS configurations will be converted properly on downgrade. It is recommended that the QoS configuration be verified and re-applied after a downgrade. QoS Upgrade and Downgrade During an upgrade from 4.0(1a)N1-Based Releases to 4.1(3)N1-Based Releases, the class-maps, policy-maps, and service-policies with a particular name will be split up into multiple instances, each with a different type and associated match conditions/actions. During a downgrade from 4.1(3)N1-Based Release, to 4.0(1a)N1-Based Release , the following will occur: • Checks will occur during the install all before reboot, alerting you to delete any new CLI in this release. • The class-maps, policy-maps, and service-policies of different types but sharing the same name are combined into a single instance. - For policy-maps, if the resulting entity cannot be attached onto an interface in 4.0(1a)N1-Based Releases, the attachment for the whole policy-map will fail Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes, Release 4.1(3)N1(1) 6 OL-16601-01

  • 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

Send documentation comments to [email protected]
6
Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes, Release 4.1(3)N1(1)
OL-16601-01
Cisco NX-OS Release 4.1(3) N1(1) Upgrade/Downgrade Issues
Upgrading from Cisco NX-OS 4.0(1a)N1-Based Releases to 4.1(3)N1-Based
Releases
When you upgrade your Cisco Nexus 5000 Series switch from Cisco NX-OS 4.0(1a)N1-Based Releases
to 4.1(3)N1-Based Releases, the following occurs:
QoS configuration will be automatically converted to the new syntax
If an ACL has more than 549 ACEs then the ACL fails to get applied. This is due to a new limit on
the number of ACEs in an ACL
The Interface
fcoe mode on
command is deprecated.
Alternatively, you can contact Cisco Customer Support for help with upgrading and converting your
configuration to the new format.
Downgrading from Cisco NX-OS 4.1(3)N-Based Releases
Downgrade is only supported for the following releases:
Cisco NX-OS 4.0(1a)N1(1) release
Cisco NX-OS 4.0(1a)N1(1a) release
Cisco NX-OS 4.0(1a)N2(1) release
Cisco NX-OS 4.0(1a)N2(1a) release
Install all
will warn of all configurations that need be undone before proceeding.
Note
Not all QoS configurations will be converted properly on downgrade. It is recommended that the QoS
configuration be verified and re-applied after a downgrade.
QoS Upgrade and Downgrade
During an upgrade from 4.0(1a)N1-Based Releases to 4.1(3)N1-Based Releases, the class-maps,
policy-maps, and service-policies with a particular name will be split up into multiple instances, each
with a different type and associated match conditions/actions.
During a downgrade from 4.1(3)N1-Based Release, to 4.0(1a)N1-Based Release , the following will
occur:
Checks will occur during the
install all
before reboot, alerting you to delete any new CLI in this
release.
The class-maps, policy-maps, and service-policies of different types but sharing the same name are
combined into a single instance.
For policy-maps, if the resulting entity cannot be attached onto an interface in 4.0(1a)N1-Based
Releases, the attachment for the whole policy-map will fail