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]
20
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
Eth1-a# show vpc brief Legend: (*) - local vPC is down, forwarding via vPC
peer-link vPC domain id : 1000 Peer status : peer adjacency formed ok vPC
keep-alive status : peer is alive Eth1-b(config)# show vpc brief Legend: (*) -
local vPC is down, forwarding via vPC peer-link vPC domain id : 1000 Peer status :
peer link is down (vPC peer is not reachable over cfs) vPC keep-alive status :
peer is alive
Workaround: Perform a shut/no shut operation on the peer-link.
• CSCti22294
Symptom: A Cisco Nexus 5000 Series switch may not forward the Mcast traffic on GEM ports after
a reload/OIR of the GEM. The Show ip igmp snooping group cli may not show the GEM ports
against the groups. This issue is observed if IGMP snooping is enabled onthe Cisco Nexus 5000
Series switch.
Workaround: Statically configuring the groups again or apply any trigger (like port flap).
• CSCti26220
Symptom:
By default, on the Cisco Nexus 5500 platforms, there is a mechanism called slow port
pruning that avoids drops for multicast traffic for uncongested ports when one of the receivers is
slow. An example of this is the 1G. Traffic for for slow receivers is dropped in the fabric. However,
there is no CLI command to indicate that such a drop has occurred. The drops occur for slow
receivers of multicast traffic (like1G ports).
Workaround: If needed, slow port pruning can be turned off using the hardware multicast
disable-slow-port-pruning command.
• CSCti31594
Symptom:
There are continuous stp disputes when 12K STP ports are configured with a hello time
value 1.
Workaround: Avoid configuring hello time value as 1 and keep the default value.
• CSCti34155
Symptom:
The show running-config ipqos all command does not display complete default
queuing-policy information.
Switch-1# show run ipqos all
policy-map type queuing default-in-policy
policy-map type queuing default-out-policy
Workaround: Use following command to see the default queuing policy-maps.
show policy-map type queuing default-in-policy
show policy-map type queuing default-out-policy
• CSCti40833
Symptom: Switch-profile session like Verify/Commit take long time before detecting a failure and
returning the cli prompt in certain cases of peer becoming unresponsive while its still reachable over
transport (CFSoIP) or in case of uni-directional failure (i.e. only one side sees peer becoming
unreachable).
Workaround: None.
• CSCti45602
Symptom:
On a Cisco Nexus 5000 Series switch, running a 5.0(2)N1(1) image, if the offline
interface configuration is made ahead of pre-provisioning configuration, commit may fail as the
configuration is not applied on the peer switch. This happens when offline interfaces are configured
ahead of pre-provisioning configuration and such configuration is synced to the peer.
Workaround: Configure pre-provisioning configuration ahead of interface configuration.