6. To
analyze the reason for Invalid Pkts counter, enable appropriate debugs to verify
the packets, timers and event notifications on IGMP Snooping module using the
debug
igmp-snooping
<all
|
packet
|
event
|
timer>
command. Useno debug
igmp-snooping
<all |
packet |
event |
timer>
to disablethe debug trace.
One possible reason for packet being considered INVALID is the IGMP message
can be of IGMPv3 type, which is not supported. For successful operation ensure
only IGMP v1/v2 messages are sent by the host or mrouter.
Enabling packet dump should dump the details of IGMP messages received on
host/mrouter interfaces on console. If none of the IGMP messages are seen, then
it means that IGMP Snooping module is not getting any messages from the ports.
7. Recover from the issue. If the multicast group association with host interface is not
seen, try the following options:
a. Ensure the host interface receives IGMP v1/v2 messages of valid range
of multicast groups.
b. Execute command clear ip igmp snooping groups.
c. Disable IGMP Snooping globally and on VLAN.
d. Administratively DOWN the host port, mrouter port, and port connected
to traffic source using the shutdown command.
e. Administratively UP the host port, mrouter port, and port connected to
traffic source using the no shutdown command.
f. Enable IGMP Snooping globally and on VLAN.
g. Repeat steps 1 to 4.
Mrouter ports are not getting cleared properly
• Check whether the mrouter ports are Dynamic (Learned) or Static (Configured) using the
show ip igmp snooping mrouter command.
Troubleshooting IGMP Snooping
Troubleshooting August 2013 105
To Next Page
Loading...
