Cisco AP776A - Nexus Converged Network Switch 5020 Catatan Rilis - Halaman 6

Jelajahi secara online atau unduh pdf Catatan Rilis untuk Beralih Cisco AP776A - Nexus Converged Network Switch 5020. Cisco AP776A - Nexus Converged Network Switch 5020 26 halaman. Cisco nexus 5000 series release notes release 4.1(3)n1(1) (ol-16601-01 h0, july 2009)
Juga untuk Cisco AP776A - Nexus Converged Network Switch 5020: Catatan Rilis (48 halaman), Catatan Rilis (44 halaman), Catatan Rilis (22 halaman), Panduan Referensi Cepat (14 halaman), Catatan Rilis (3 halaman), Catatan Rilis (26 halaman)

Halaman Cetak
Cisco AP776A - Nexus Converged Network Switch 5020 Catatan Rilis
Release 4.0(1a)N1(1a) Upgrade and Downgrade Issues
S e n d d o c u m e n t a t i o n c o m m e n t s t o n e x u s 5 k d o c s @ c i s c o . c o m
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
The following table describes the changes to the priority flow control configuration.
4.0(0)-based
releases
4.0(1a)N1(1a)
Upgrade
Downgrade
The following table describes the changes to the syntax of the Ethernet load-balancing commands.
4.0(0)-based
releases
4.0(1a)N1(1a)
Upgrade
Downgrade
Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1a)
6
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.
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 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-mac
source-destination-port
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
The keyword source-dest is used in this release.
Note
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.
Source & Destination IP address
Source & Destination MAC address
Source & Destination TCP/UDP port
OL-16601-01