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

Send documentation comments to [email protected], source-destination, source-dest

Page 5 highlights

Release 4.0(1a)N1(1) Upgrade and Downgrade Issues Send documentation comments to [email protected] The following table describes the changes to the priority flow control configuration. 4.0(0)-based releases 4.0(1a)N1(1) 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(1) 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. When an Ethernet interface joins a EtherChannel, the following interface level parameters are disabled: bandwidth delay duplex flowcontrol ip ipv6 mac priority-flow-control service-policy spanning-tree speed storm-control Set bandwidth informational parameter Specify interface throughput delay Enter the port duplex mode Configure interface flowcontrol Configure IP features Configure IPv6 features MAC configuration commands Configure interface priority-flowcontrol Configure QoS service policy Spanning Tree Subsystem Enter the port speed Configure Interface storm control OL-16601-01 Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1) 5

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24

Send documentation comments to [email protected]
5
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
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.
When an Ethernet interface joins a EtherChannel, the following interface level parameters are disabled:
bandwidth
Set bandwidth informational parameter
delay
Specify interface throughput delay
duplex
Enter the port duplex mode
flowcontrol
Configure interface flowcontrol
ip
Configure IP features
ipv6
Configure IPv6 features
mac
MAC configuration commands
priority-flow-control
Configure interface priority-flowcontrol
service-policy
Configure QoS service policy
spanning-tree
Spanning Tree Subsystem
speed
Enter the port speed
storm-control
Configure Interface storm control
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(1)
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(1)
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.