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]
38
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
3001 100.1.1.1 /237.1.0.1
Eth101/1/130.1.1.1 00:08:33 00:00:03 00:04:16
3001 100.1.1.1 /237.1.0.1
Eth111/1/130.1.1.1 00:08:22 00:00:02 00:04:17
3001 100.1.1.1 /237.1.0.2
Eth101/1/130.1.1.1 00:08:32 00:00:02 00:04:17
3001 100.1.1.1 /237.1.0.2
Eth111/1/130.1.1.1 00:08:21 00:00:01 00:04:18
3001 100.1.1.1 /237.1.0.3
Eth101/1/130.1.1.1 00:08:31 00:00:01 00:04:18
3001 100.1.1.1 /237.1.0.3
Eth111/1/130.1.1.1 00:08:20 0.158710 00:04:19
3001 100.1.1.1 /237.1.0.4
Eth101/1/130.1.1.1 00:08:30 0.743343 00:04:19
3001 100.1.1.1 /237.1.0.4
Eth111/1/130.1.1.1 00:08:19 00:00:09 00:04:10
3001 100.1.1.1 /237.1.0.5
Eth101/1/130.1.1.1 00:08:29 00:00:09 00:04:10
3001 100.1.1.1 /237.1.0.5
Switch# sh ip igmp snooping explicit-tracking vlan 3001 <<<<<<<<<<<<<<< No info
when specific VLAN is used
IGMPv3 Snooping Explicit-tracking information
Vlan Source/Group
Intf Reporter Uptime Last-Join Expires
Switch#
This occurs when the command is issued for a specific VLAN.
Workaround: None
• CSCti87650
Symptom:On a Cisco Nexus 5000, the output of the command "show interface fc<x/y> capabilities"
may indicate that "Class 2 sequential delivery" and "BB state change notification" are supported
when in fact they are not supported. The command "show interface fc<x/y> capabilities" has to be
executed
Workaround: This issue is resolved..
Workaround: No workaround is available. It's just a display issue which should be ignored.
• CSCti91712
Symptom: Nexus 5000 implementation of igmp snooping needs to be consistent with Nexus 7000
Workaround: None
• CSCtj10418
Symptom:
When peer Cisco Nexus 5000 Series switches are configured with switch-profile for
configuration sync functionality, and merge for the first time, merge fails if the switch-profile
configuration between the peer switches do not match.
Workaround: After a merge failure, correct the offending configuration before issuing a commit.
• CSCtj24599
Symptom: Deleting a switch-profile using 'no switch-profile local-config | all-config' doesn't
removes the configuration applied under switch-profile. The issue has been sporadically seen on
5548 which has dual core CPU.
Workaround:The leftover configuration needs to be manually removed.
• CSCtj27351