Igmpv2 Enhancements - HP FlexNetwork 7500 Series Configuration Manual

The hosts send unsolicited IGMP reports to the multicast groups they want to join without
1.
having to wait for the IGMP queries from the IGMP querier.
The IGMP querier periodically multicasts IGMP queries (with the destination address of
2.
224.0.0.1) to all hosts and routers on the local subnet.
After receiving a query message, the host whose delay timer expires first sends an IGMP report
to the multicast group G1 to announce its membership for G1. In this example, Host B sends the
report message. Host C suppresses its own report for G1 after receiving the report from Host B.
Because IGMP routers already know that G1 has at least one member, other members do not
need to report their memberships. This host IGMP report suppression mechanism helps reduce
traffic on the local subnet.
At the same time, Host A sends a report to the multicast group G2 after receiving a query.
3.
Through the query and response process, the IGMP routers (Router A and Router B) determine
4.
that the local subnet has members of G1 and G2. The multicast routing protocol (PIM, for
example) on the routers generates (*, G1) and (*, G2) multicast forwarding entries, where
asterisk (*) represents any multicast source. These entries are the basis for subsequent
multicast forwarding.
When the multicast data addressed to G1 or G2 reaches an IGMP router, the router looks up
5.
the multicast forwarding table. Based on the (*, G1) or (*, G2) entries, the router forwards the
multicast data to the local subnet. Then, the receivers on the subnet can receive the data.
IGMPv1 does not define a leave group message (often called a leave message). When an IGMPv1
host is leaving a multicast group, it stops sending reports to that multicast group. If the subnet has no
members for a multicast group, the IGMP routers will not receive any report addressed to that
multicast group. In this case, the routers clear the information for that multicast group after a period
of time.

IGMPv2 enhancements

Backwards-compatible with IGMPv1, IGMPv2 has introduced a querier election mechanism and a
leave-group mechanism.
Querier election mechanism
In IGMPv1, the DR elected by the Layer 3 multicast routing protocol (such as PIM) acts as the
querier.
IGMPv2 introduced an independent querier election mechanism. The querier election process is as
follows:
Initially, every IGMPv2 router assumes itself to be the querier. Each router sends IGMP general
1.
query messages (often called general queries) to all hosts and routers on the local subnet. The
destination address of general queries is 224.0.0.1.
After receiving a general query, every IGMPv2 router compares the source IP address of the
2.
query message with its own interface address. The router with the lowest IP address becomes
the querier. All the other IGMPv2 routers become non-queriers.
All the non-queriers start the other querier present timer. If a router receives an IGMP query
3.
from the querier before the timer expires, it resets this timer. Otherwise, the router considers
that the querier has timed out. In this case, the router initiates a new querier election process.
"Leave group" mechanism
In IGMPv1, when a host leaves a multicast group, it does not send any notification to the multicast
routers. The multicast routers determine whether a group has members by using the maximum
response time. This adds to the leave latency.
In IGMPv2, when a host is leaving a multicast group, the following process occurs:
The host sends a leave message to all routers on the local subnet. The destination address of
1.
leave messages is 224.0.0.2.
76