500
E
ES4710BD 10 Slots L2/L3/L4 Chassis Switch
command disables this debug function.
Parameters:
N/A.
Default:
Disabled
Command mode:
Admin Mode
Usage Guide:
If detailed information about IGMP events is required, this debugging command can
be used.
Example:
Switch# debug ip igmp event
igmp event debug is on
Switch#
01:04:30:56: IGMP: Group 224.1.1.1 on interface vlan1 timed out
19.6.4.1.4 debug ip igmp packet
Command: debug ip igmp packet
Function:
Enables the IGMP packet debug function; the “
no debug ip ospf packet
” command
disables this debug function.
Parameters:
N/A.
Default:
Disabled.
Command mode:
Admin Mode
Usage Guide:
If information about IGMP packets is required, this debugging command can be
used.
Example:
Switch# debug ip igmp packet
igmp packet debug is on
Switch #02:17:38:58: IGMP: Send membership query on dvmrp2 for 0.0.0.0
02:17:38:58: IGMP: Received membership query on dvmrp2 from 192.168.1.11 for 0.0.0.0
02:17:39:26: IGMP: Send membership query on vlan1 for 0.0.0.0
02:17:39:26: IGMP: Received membership query on dvmrp2 from 192.168.1.11 for 0.0.0.0
19.6.4.2 IGMP
Troubleshooting
In configuring and using IGMP protocol, the IGMP protocol may fail to run properly due to reasons
such as physical connection failure or wrong configurations. The user should ensure the following:
Good condition of the physical connection.
All interface and link protocols are in the UP state (use “show interface” command).
Ensure at least one multicast protocol is enabled on the interface.
Multicast protocols use unicast routes to perform RPF check, for this reason, the unicast
route correctness must be ensured.
If IGMP problems persist after the abovementioned procedures, please run debug commands like
“debug ip igmp event/packet”, and copy the debug information in 3 minute and send the information
to Edge-Core technical service center.
