HP Cisco Nexus 5000 Cisco Nexus 5000 Series Release Notes Release 4.1(3)N1(1) - Page 9

Caveats, Open Caveats

Page 9 highlights

Caveats Send documentation comments to [email protected] 11 and the switch port 1/5 sends multicast traffic on VLAN 11 in a multicast group, and hosts connected to FEX ports 100/1/3-12 are interested in receiving that mutlicast traffic (through IGMP), then that multicast traffic goes out on FEX ports 100/1/3-12, but not on 100/1/1-2. If you configure SPAN Tx on port 100/1/1, although the multicast traffic does not egress out of port 100/1/1, the SPAN destination does receive that multicast traffic. This is due to a design limitation. • When a FEX port is configured as both SPAN rx-source and tx-source, the broadcast, non-IGMP layer-2 multicast, and unknown unicast frames originating from that port may be seen twice on the SPAN destination, once on the ingress and once on the egress path. On the egress path, the frames are filtered by the FEX to prevent them from going out on the same port on which they were received. For example, if FEX Port 100/1/1 is configured on VLAN 11, and is also configured as SPAN rx-source and tx-source and a broadcast frame is received on that port, the SPAN destination recognizes two copies of the frame, even though the frame is not sent back on port 100/1/1. • A FEX port can not be configured as a SPAN destination. Only a switch port can be configured and used as a SPAN destination. Caveats This section includes the following topics: • Open Caveats, page 9 • Resolved Caveats-Cisco NX-OS Release 4.1(3)N1(1), page 17 • Resolved Caveats-Cisco NX-OS Release 4.0(1a)N2(1), page 20 • Resolved Caveats-Cisco NX-OS Release 4.0(1a)N1(1), page 21 • Resolved Caveats-Cisco NX-OS Release 4.0(0)N1(2a), page 22 • Resolved Caveats-Cisco NX-OS Release 4.0(0)N1(2), page 23 • Resolved Caveats-Cisco NX-OS Release 4.0(0)N1(1a), page 25 • Resolved Caveats-Cisco NX-OS Release 4.0(0)N1(1), page 25 Open Caveats This section lists the open caveats for this release. • CSCsz93815 Symptom: After you downgrade from release 4.1(3)N1, the QoS configuration is not restored if the class-map name is dfferent for type qos, network-qos,or queuing policy-maps. Workaround: Make sure the class-names between different policy types are the same before you begin downgrade. • CSCsz82199 Symptom: You cannot enable std.pause on a port-channel interface connected between two Cisco Nexus 5000 Series switches. Enable std.pause between two Cisco Nexus 5000 Series switches and configure std.pause in the hardware. Workaround: None OL-16601-01 Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes, Release 4.1(3)N1(1) 9

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

Send documentation comments to [email protected]
9
Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes, Release 4.1(3)N1(1)
OL-16601-01
Caveats
11 and the switch port 1/5 sends multicast traffic on VLAN 11 in a multicast group, and hosts
connected to FEX ports 100/1/3-12 are interested in receiving that mutlicast traffic (through IGMP),
then that multicast traffic goes out on FEX ports 100/1/3-12, but not on 100/1/1-2.
If you configure SPAN Tx on port 100/1/1, although the multicast traffic does not egress out of port
100/1/1, the SPAN destination does receive that multicast traffic. This is due to a design limitation.
When a FEX port is configured as both SPAN rx-source and tx-source, the broadcast, non-IGMP
layer-2 multicast, and unknown unicast frames originating from that port may be seen twice on the
SPAN destination, once on the ingress and once on the egress path. On the egress path, the frames
are filtered by the FEX to prevent them from going out on the same port on which they were
received. For example, if FEX Port 100/1/1 is configured on VLAN 11, and is also configured as
SPAN rx-source and tx-source and a broadcast frame is received on that port, the SPAN destination
recognizes two copies of the frame, even though the frame is not sent back on port 100/1/1.
A FEX port can not be configured as a SPAN destination. Only a switch port can be configured and
used as a SPAN destination.
Caveats
This section includes the following topics:
Open Caveats, page 9
Resolved Caveats—Cisco NX-OS Release 4.1(3)N1(1), page 17
Resolved Caveats—Cisco NX-OS Release 4.0(1a)N2(1), page 20
Resolved Caveats—Cisco NX-OS Release 4.0(1a)N1(1), page 21
Resolved Caveats—Cisco NX-OS Release 4.0(0)N1(2a), page 22
Resolved Caveats—Cisco NX-OS Release 4.0(0)N1(2), page 23
Resolved Caveats—Cisco NX-OS Release 4.0(0)N1(1a), page 25
Resolved Caveats—Cisco NX-OS Release 4.0(0)N1(1), page 25
Open Caveats
This section lists the open caveats for this release.
CSCsz93815
Symptom
: After you downgrade from release 4.1(3)N1, the QoS configuration is not restored if the
class-map name is dfferent for type qos, network-qos,or queuing policy-maps.
Workaround:
Make sure the class-names between different policy types are the same before you
begin downgrade.
CSCsz82199
Symptom
: You cannot enable std.pause on a port-channel interface connected between two Cisco
Nexus 5000 Series switches. Enable std.pause between two Cisco Nexus 5000 Series switches and
configure std.pause in the hardware.
Workaround:
None