Cisco N5K-C5010P-BF Troubleshooting Guide - Page 47

Multicast, Source MAC addresses of IGMP joins are learned, Multicast data traffic not received by host

Page 47 highlights

Chapter 3 Troubleshooting Layer 2 Switching Issues Multicast Send document comments to [email protected]. Solution Check the native VLAN configured at both ends (ports) of the link. Ensure that they have the same native VLAN. Once the native VLANs are synchronized, the port moves out of the inconsistency state. Multicast Source MAC addresses of IGMP joins are learned In this situation, the source MAC addresses of IGMP joins are learned. However, source MAC addresses of IGMP joins are usually not learned by the switch in order to conserve MAC address space. Possible Cause Receiving joins and performing an ISSU simultaneously might cause the situation. Solution The MAC addresses age out (expire) if the join stops. Alternatively, you can clear the MAC addresses specifically by using the clear mac address-table dynamic mac command. Multicast data traffic not received by host Host does not receive multicast data traffic. Possible Cause The join is not registered. Solution • Ensure that the host application is sending the joins. • Check if the switch port is configured for the VLAN on which the joins are being sent using the show vlan id command. • Check if the relevant VLAN is active by using the show vlan id command. • Check if the switch port is in STP forwarding state by using the show spanning-tree vlan command. Multicast data traffic not received when host is registered for group Multicast data traffic is not received when the host is registered for the group. Possible Cause A bug may exist in exist in the communication between the IGMP and FWM processes. Review the output from the following commands: • show ip igmp snooping groups vlan 1001 • show mac address-table multicast vlan 1001 igmp-snooping • show platform fwm info vlan 1001 all_macgs verbose Solution OL-25300-01 Cisco Nexus 5000 Series Troubleshooting Guide 3-5

  • 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
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162

Send document comments to [email protected].
3-5
Cisco Nexus 5000 Series Troubleshooting Guide
OL-25300-01
Chapter 3
Troubleshooting Layer 2 Switching Issues
Multicast
Solution
Check the native VLAN configured at both ends (ports) of the link. Ensure that they have the same native
VLAN. Once the native VLANs are synchronized, the port moves out of the inconsistency state.
Multicast
Source MAC addresses of IGMP joins are learned
In this situation, the source MAC addresses of IGMP joins are learned. However, source MAC addresses
of IGMP joins are usually not learned by the switch in order to conserve MAC address space.
Possible Cause
Receiving joins and performing an ISSU simultaneously might cause the situation.
Solution
The MAC addresses age out (expire) if the join stops. Alternatively, you can clear the MAC addresses
specifically by using the
clear mac address-table dynamic mac
<mac>
command.
Multicast data traffic not received by host
Host does not receive multicast data traffic.
Possible Cause
The join is not registered.
Solution
Ensure that the host application is sending the joins.
Check if the switch port is configured for the VLAN on which the joins are being sent using the
show vlan id
<vlan>
command.
Check if the relevant VLAN is active by using the
show vlan id
<vlan>
command.
Check if the switch port is in STP forwarding state by using the
show spanning-tree vlan
<vlan>
command.
Multicast data traffic not received when host is registered for group
Multicast data traffic is not received when the host is registered for the group.
Possible Cause
A bug may exist in exist in the communication between the IGMP and FWM processes.
Review the output from the following commands:
show ip igmp snooping groups vlan 1001
show mac address-table multicast vlan 1001 igmp-snooping
show platform fwm info vlan 1001 all_macgs verbose
Solution