Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1) (OL-16601-01 G0)

Send documentation comments to [e-mail]
4
Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1)
OL-16601-01
Release 4.0(1a)N1(1) Upgrade and Downgrade Issues
For more information about the features listed, refer to the documentation set listed in the“Related
Documentation” section on page 23.
Release 4.0(1a)N1(1) Upgrade and Downgrade Issues
This section describes issues that you may encounter when you upgrade or downgrade the Cisco NX-OS
software release on the Nexus 5000 Series switch. It provides examples of configuration syntax
differences for some of these changes.
This section includes the following topics:
• EtherChannel® Upgrade/Downgrade Changes, page 4
• Fibre Channel Port Shutdown, page 6
• Switched Port Analyzer (SPAN), page 6
• Example of Virtual Interface Configuration Changes, page 8
• Upgrading to Cisco NX-OS Release 4.0(1a)N1(1), page 9
• Downgrading from Cisco NX-OS Release 4.0(1a)N1(1), page 9
EtherChannel® Upgrade/Downgrade Changes
The following table describes the changes to the security ACLs for EtherChannel members.
The following table describes the changes to the interface level QoS service policy,
4.0(0)-based
releases
Configuration is allowed on member ports (but not used while the port is a member
of the EtherChannel).
4.0(1a)N1(1) No configuration is allowed on member ports. All member ports follow the
configuration on the EtherChannel.
Upgrade Member port ACL configuration, if any, is lost; EtherChannel configuration is
preserved. No impact on the functional behavior while the port is a member of the
EtherChannel.
When the member port leaves the EtherChannel, you have to recreate the ACL
configuration on the physical interface.
Downgrade No issue.
4.0(0)-based
releases
Interface level QoS service policy is not aware of the EtherChannel. QoS strictly
follows a per-member port configuration. The only service policy supported on the
interface level is egress queue scheduling.
4.0(1a)N1(1) No configuration is allowed on member ports. All member ports follow the
configuration on the EtherChannel.
Upgrade If any member port has a modified egress scheduling policy and the EtherChannel is
explicitly configured, then the egress scheduling configuration for the port is lost. A
EtherChannel has a default egress scheduling policy.
Downgrade This capability needs to be reconfigured after the downgrade. Otherwise, egress
queue scheduling configuration on the EtherChannel will be lost after the downgrade.