Digging Out IGMPv2 Querier process

There's a wonderful quantity of bafflement surrounding this IGMP querier selection process- most specially in what conditions can be used to decide on this specified querier for just a part. To demonstrate this kind of, we’ll make use of the using topology:

IGMP Querier

In this particular topology, many of us have about three routers on a discussed part (connected to an ethernet change, almost all routers on a single VLAN), along with we now have made it possible for PIM sparse method about every single fastethernet0/0 interface involving R1, R2, along with R3, respectively. Ahead of all of us end up in this animal meat in this article, what on earth is the purpose of this querier?

“Out on the box” so to speak, let’s examine how are you affected. 1st we’ll check out your IGMP reputation about R1:

Be aware: We’re currently running IGMPv2.

R1#show ip igmp int f0/0
FastEthernet0/0 is usually upwards, brand method is usually upwards
World wide web deal with is usually 10. twenty five. 1. 1/24
IGMP is usually made it possible for about interface
Existing IGMP router model is usually only two
IGMP query time period is usually 62 seconds
IGMP querier timeout is usually 120 seconds
IGMP activity: 1 ties, 0 leaves
Multicast specified router (DR) is usually 10. twenty five. 1. 3
IGMP querying router is usually 10. twenty five. 1. 1 (this system)

Since you discover, R1 evolved into this IGMP querying router, whilst R3 evolved into this PIM DOCTOR for that part, because doing so has the maximum IP deal with. Remember that we could affect this DOCTOR selection when using the interface demand “ip pim dr-priority x” – this default price for that DOCTOR priority is usually no, and so almost any price earlier mentioned this could result in that system to become this PIM DOCTOR instead of while using the maximum IP deal with to be a tiebreaker.

At this point let’s test a similar course of action but rather I’ll help IGMP model 1 about almost all routers:

R1, R2, R3
ip igmp model 1

At this point let’s discover what exactly IGMP does. Once again, we’ll check out from R1′s point of view:

R1#show ip igmp int f0/0
FastEthernet0/0 is usually upwards, brand method is usually upwards
World wide web deal with is usually 10. twenty five. 1. 1/24
---output disregarded for brevity-----
Multicast specified router (DR) is usually 10. twenty five. 1. 3
IGMP querying router is usually 10. twenty five. 1. 3 (this system)

Observe everything odd? R3 is becoming selected this PIM DOCTOR, however it displays this IGMP querying router as R3 in addition, along with states “this system” – let’s research additional. We’ll ut upon R2 to see what exactly the item states:

R2#show ip igmp int f0/0
FastEthernet0/0 is usually upwards, brand method is usually upwards
World wide web deal with is usually 10. twenty five. 1. 2/24
---output disregarded for brevity-----
Multicast specified router (DR) is usually 10. twenty five. 1. 3
IGMP querying router is usually 10. twenty five. 1. 3 (this system)

Hmm.. it also displays R3 because IGMP querying router, although the reason why? Well, IGMPv1 certainly not identified some sort of query mechanism. The idea rather relies on this PIM DOCTOR to handle this characteristics on the querier. So, in theory, even though our gadgets present this IGMP querying router as “this system” your questions MUST originate from this DOCTOR, which is R3. Let’s examination.

R1#debug ip igmp
---output omitted---
*May twenty five 00: twenty-seven: 03. 651: IGMP(0): Received v1 Problem about FastEthernet0/0 from 10. twenty five. 1. 3

So, all of us discover ‘officially’ that R3 is being applied as your querier because of this part.

The limited model here, is usually this kind of:

IGMPv2/3:

-Highest IP AS WELL AS DOCTOR priority = PIM DOCTOR
-Lowest IP = IGMP Chosen Querier

IGMPv1

-Highest IP or even DOCTOR priority = PIM DOCTOR
-Highest IP = IGMP Chosen Querier

I’ll get yet another article fairly shortly that relates to a couple of unique eccentricities regarding IGMPv3.