HP Cisco Nexus 5000 Cisco Nexus 5000 Series Release Notes Release 4.0(1a)N1(1a - Page 6

Release 4.0(1a)N1(1a) Upgrade and Downgrade Issues Send documentation comments to [email protected] The following table describes the changes to the interface level QoS service policy, 4.0(0)-based releases 4.0(1a)N1(1a) Upgrade Downgrade 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. No configuration is allowed on member ports. All member ports follow the configuration on the EtherChannel. 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. This capability needs to be reconfigured after the downgrade. Otherwise, egress queue scheduling configuration on the EtherChannel will be lost after the downgrade. The following table describes the changes to the priority flow control configuration. 4.0(0)-based releases 4.0(1a)N1(1a) Upgrade Downgrade 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. No configuration allowed on member ports. All member ports follow the configuration on the EtherChannel. 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. This capability needs to be reconfigured after the downgrade. Otherwise, the priority flow control configuration on the EtherChannel will be lost. The following table describes the changes to the syntax of the Ethernet load-balancing commands. 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 4.0(1a)N1(1a) Note The keyword source-destination is used in this release. 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 Upgrade Downgrade Note The keyword source-dest is used in this release. The load-balancing configuration is lost. This capability needs to be reconfigured after the downgrade. Otherwise, the load-balancing configuration on the EtherChannel will be lost. Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1a) 6 OL-16601-01