In this post we will quickly discuss the use of most commonly needed IGMP timers. First, as we know, multicast routers periodically query hosts on a segment. If there are two or more routers sharing the same segment, the one with the lowest IP address is the IGMP querier (per IGMPv2 election procedure – as you remember, IGMPv1 let the multicast routing protocol define the querier).

The periodic interval is defined using the command:

ip igmp query-interval [interval in secs]

The hosts on the segment are supposed to report their group membership in response to the queries. Note that IGMPv2 defines special report suppression procedure, which allows host to suppress its own report, if it saw some other host reporting the same group. The query-interval timer is also used to define the amount of time a router will store particular IGMP state if it does not hear any reports on the group. This interval is 3xquery-time and it was the only mechanism available in IGMPv1 to expire a non-needed group. By default the interval is 60 seconds.

From what we said above follows that hosts must respond to a query during some time-window interval. This time window is specified in IGMPv2 packets using special field that defines the maximum response time. You set the value of this field using the command:

ip igmp query-max-response-time [time-in-seconds]

When a host receives the query packet, it starts counting to a random value, less that the maximum response time. When this timer expires, host replies with a report, provided that no other host has responded yet. This accomplishes two purposes:

a) Allows controlling the amount of IGMP reports sent during a time window.
b) Engages the report suppression feature, which permits a host to suppress its own report and conserve bandwidth.

Naturally, the maximum response timer could not be less than the query-interval. Note that IGMPv1 does not support the maximum response time field in its packets, and this timer is fixed to 10 seconds with version 1.

The next important timer, pertaining to IGMPv2, is last member query interval. This interval is configured using the following command:

ip igmp last-member-query-interval [interval in ms]

IGMP uses this value when router hears IGMPv2 Leave report. This means that at least one host wants to leave the group. After router receives the Leave report, it checks that the interface is not configured for IGMP Immediate Leave (single-host on the segment) and if not, it sends out an out-of-sequence query. The maximum-response-time in this query is set to last-member-query-interval which is 1000ms by default. The router sends out maximum of

ip igmp last-member-query-count [number]

messages and if no one responds during this time, the router removes the IGMP state for the group. The whole procedure controls if there are any more members left on the interface. After the last query send router waits some additional time, approximately 0,5 second to finally remove the group. So by default, after a reception of the Leave message the router waits for 2x1000ms+0,5seconds before stopping the multicast traffic flow.

If the interface is configured for immediate leave for a specific group list using the command:

ip igmp immediate-leave group-list [list]

Then the router will treat these groups as having single host member. After the reception of a Leave message, the router immediately removes the multicast forwarding state.
The last interesting timer is

ip igmp query-timeout [timeout]

This timer is used by “silent” routers, i.e. the routers that lost the IGMP querier election process. If the inactive routers did not hear any query for the 2 * [timeout] interval, they start election process again.

And in the end, a quick command to learn all default IGMP timer values:

Rack21R5#show ip igmp interface fastEthernet 0/1
FastEthernet0/1 is up, line protocol is up
  Internet address is
  IGMP is enabled on interface
  Current IGMP host version is 2
  Current IGMP router version is 2
 IGMP query interval is 60 seconds
  IGMP querier timeout is 120 seconds
  IGMP max query response time is 10 seconds
  Last member query count is 2
  Last member query response interval is 1000 ms
  Inbound IGMP access group is not set
About Petr Lapukhov, 4xCCIE/CCDE:

Petr Lapukhov's career in IT begain in 1988 with a focus on computer programming, and progressed into networking with his first exposure to Novell NetWare in 1991. Initially involved with Kazan State University's campus network support and UNIX system administration, he went through the path of becoming a networking consultant, taking part in many network deployment projects. Petr currently has over 12 years of experience working in the Cisco networking field, and is the only person in the world to have obtained four CCIEs in under two years, passing each on his first attempt. Petr is an exceptional case in that he has been working with all of the technologies covered in his four CCIE tracks (R&S, Security, SP, and Voice) on a daily basis for many years. When not actively teaching classes, developing self-paced products, studying for the CCDE Practical & the CCIE Storage Lab Exam, and completing his PhD in Applied Mathematics.

Find all posts by Petr Lapukhov, 4xCCIE/CCDE | Visit Website

You can leave a response, or trackback from your own site.

8 Responses to “A quick overview of basic IGMP timers”

  1. John Penrod says:

    Thanks for this article! It was helpful.

  2. Khurram Noor says:

    Thanks this was a vital peace of information.

  3. Mukarram says:

    default query interval on cisco routers is 60 secs, while the RFC recommends 125 secs.
    As per 12.4T command reference cisco thinks 60 secs are good enough for fast detection of multicast hosts..

    will it not cause an issue with non-cisco devices???

  4. Cert says:

    The delay mentioned for the leave process is wrong. The 0.5s delay does happen per interval not once for the whole process. So you have to change your formula to (0.5 x Interval) + (0.5 x count).


  5. [...] http://blog.ine.com/2008/10/31/a-quick-overview-of-basic-igmp-timers/ Default query-interval = 60 seconds (3×20=60). Default querier-timeout = 120 seconds (2x [...]

  6. Yahoo tech support says:

    I appreciate your opinion your article really helps to me I always visit your site regularly so keep posting the valuable information.

  7. john says:

    Thanks for the sharing this I appreciate your opinion your article really helps to me I always visit your site regularly so keep posting the valuable information.

  8. Radek says:

    Quick question on IGMPv3 backward compatibility. Will an IGMPv3 group in an IGMPv2 backward compatibility mode ever return to an IGMPv3 if an IGMPv2 speaker, that was accidentally introduced, is removed? Even if all other hosts requesting same group are IGMPv3?


Leave a Reply to Mukarram

Click here to cancel reply.


CCIE Bloggers