Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes, for Cisco NX-OS Release 5.0(2)N1(1) and NX-OS Release 5.0(2)N2(1) OL-22747-02, December 2010)

Send documentation comments to [e-mail]
17
Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes, for Cisco NX-OS Release 5.0(2)N1(1) and NX-OS Release 5.0(2)N2(1)
OL-22747-02
Caveats
• 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 cannot be configured as a SPAN destination. Only a switch port can be configured and
used as a SPAN destination.
Checkpoint and Configuration Rollback Limitation
When FCoE is enabled, the checkpoint and configuration rollback functionality is disabled.
Caveats
This section includes the following topics:
• Open Caveats, page 17
• Resolved Caveats—Cisco NX-OS Release 5.0(2)N2(1), page 36
• Resolved CaveatsCisco NX-OS Release 5.0(2)N1(1), page 42
Open Caveats
This section lists the open caveats for the Cisco NX-OS 5.0(2)N2(1) release.
• CSCtj13786
Symptom: On upgrade from the Cisco NX-OS Release 5.0(2)N1(1) to the Cisco NX-OS
Release 5.0(2)N2(1), igmp v3-groups might age out and the groups are flushed. Any data destined
to these removed groups might be dropped during an ISSU. They resume when the ISSU is
completed.
Workaround: There is no workaround in when you upgrade from NX-OS Release 5.0(2)N1(1) to
NX-OS Release 5.0(2)N2(1). This is fixed in NX-OS Release 5.0(2)N2(1) and is not seen on
upgrade from NX-OS Release 5.0(2)N2(1).
• CSCtk33187
Symptom: A Cisco Nexus 5500 may crash when an expansion module is removed from the switch
and the expansion module has some fabric ports that are used for control traffic.
Workaround: Shut the fabric ports on the expansion module before removing the expansion module
from the switch. Because expansion module itself is being removed, doing a "shut" on the fabric
ports should not have any functional impact.
• CSCtj66020
Symptom: After downgrade from 5.0(2)N2(1) to 5.0(2)N1(1), channel-group config may be lost
due to priority-flow-control config on a few ports.
Workaround: Although PFC mode auto is default, you need to config PFC mode 'auto' to Port
channel members and then add it to the Port channel.