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

Send documentation comments to [e-mail]
6
Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1a)
OL-16601-01
Release 4.0(1a)N1(1a) Upgrade and Downgrade Issues
The following table describes the changes to the interface level QoS service policy,
The following table describes the changes to the priority flow control configuration.
The following table describes the changes to the syntax of the Ethernet load-balancing commands.
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(1a) 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.
4.0(0)-based
releases
Priority flow control is an interface level configuration. This CLI option is used to
override results of DCBX negotiation. Priority flow control function is not aware of
the EtherChannel. It strictly follows a per-member port configuration.
4.0(1a)N1(1a) No configuration allowed on member ports. All member ports follow the
configuration on the EtherChannel.
Upgrade If a member port has modified priority flow control configuration and the
EtherChannel is explicitly configured, then port configuration is lost. The
EtherChannel has default priority flow control configuration.
Downgrade This capability needs to be reconfigured after the downgrade. Otherwise, the priority
flow control configuration on the EtherChannel will be lost.
4.0(0)-based
releases
The following command is used to set the load-balancing method in a channel-group
bundle:
switch(config)# port-channel load-balance ethernet source-destination-?
source-destination-ip Source & Destination IP address
source-destination-mac Source & Destination MAC address
source-destination-port Source & Destination TCP/UDP port
Note The keyword source-destination is used in this release.
4.0(1a)N1(1a) The following command is used to set the load-balancing method in a channel-group
bundle:
switch(config)# port-channel load-balance ethernet source-dest-?
source-dest-ip Source & Destination IP address
source-dest-mac Source & Destination MAC address
source-dest-port Source & Destination TCP/UDP port
Note The keyword source-dest is used in this release.
Upgrade The load-balancing configuration is lost.
Downgrade This capability needs to be reconfigured after the downgrade. Otherwise, the
load-balancing configuration on the EtherChannel will be lost.