Troubleshooting Guide

Table Of Contents
1 125 100 2 2 10 false false false false
2 125 100 2 2 10 false false false false
3 125 100 2 2 10 false false false false
4 125 100 2 2 10 false false false false
5 125 100 2 2 10 false false false false
10 125 100 2 2 10 false false false false
100 125 100 2 2 10 false false false false
200 125 100 2 2 10 false false false false
300 125 100 2 2 10 false false false false
444 125 100 2 2 10 false false false false
All 10 out of 10 Total Num of Igmp entries displayed
VLAN SNOOP SNOOP DYNAMIC COMPATIBILITY EXPLICIT
ID QUERIER QUERIER DOWNGRADE MODE HOST
ENABLE ADDRESS VERSION TRACKING
--------------------------------------------------------------------------------
1 false 0.0.0.0 enable disable disable
2 false 0.0.0.0 enable disable disable
3 false 0.0.0.0 enable disable disable
4 false 0.0.0.0 enable disable disable
5 false 0.0.0.0 enable disable disable
10 false 0.0.0.0 enable disable disable
100 false 0.0.0.0 enable disable disable
200 false 0.0.0.0 enable disable disable
300 false 0.0.0.0 enable disable disable
444 false 0.0.0.0 enable disable disable
All 10 out of 10 Total Num of Igmp entries displayed
Job aid
The following table describes the fields in the output for the show ip igmp interface vlan
command.
Note:
The following table shows the field descriptions for this command if you use the optional
parameter vlan. If you do not the output is different.
Field Description
VLAN ID Identifies the VLAN or port where IGMP is
configured.
QUERY INTVL Indicates the frequency at which IGMP host query
packets transmit on this interface.
QUERY MAX RESP Indicates the maximum query response time (in
tenths of a second) advertised in IGMPv2 queries on
this interface.
ROBUST Indicates the robustness variable, which you can
configure for the expected packet loss on a subnet. If
you expect packet loss on a subnet, increase the
robustness variable.
VERSION Indicates the version of IGMP that runs on this
interface. This object configures a router capable of
Table continues…
Multicast troubleshooting
January 2017 Troubleshooting 262
Comments on this document? infodev@avaya.com