No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Configuration Guide - IP Multicast

CloudEngine 8800, 7800, 6800, and 5800 V200R005C10

This document describes the configurations of IP multicast, including IP multicast basics, IGMP, MLD, PIM (IPv4), PIM (IPv6), MSDP, multicast VPN, multicast route management (IPv4), multicast route management (IPv6), IGMP snooping, MLD snooping, static multicast MAC address, multicast VLAN, multicast network management.
Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Changes in IGMPv2

Changes in IGMPv2

IGMPv2 works similarly to IGMPv1. The most significant difference between the two versions lies in the leave mechanism. When an IGMPv2 host leaves a group, it sends a Leave message to the IGMP querier. When the IGMP querier receives the Leave message, it sends a Group-Specific Query message to check whether the group has other members. If the IGMP querier does not receive any Report messages for the group within a specified period, it no longer maintains membership of the group. IGMPv2 enables an IGMP querier to know the groups that have no members on a local network segment and update group membership quickly. This leave mechanism reduces redundant multicast traffic on the network.

IGMPv2 Messages

IGMPv2 differs from IGMPv1 in the following ways:
  • In addition to General Query and Report messages IGMPv2 defines two new message types:
    • Leave message: sent by a host to notify the querier on the local network segment that it has left a group.
    • Group-Specific Query message: sent by a querier to a specified group on the local network segment to check whether the group has members.
  • IGMPv2 adds a new field to General Query messages: Max Response Time. This field can be configured to control hosts' response speed to Query messages.

Figure 2-6 shows the IGMPv2 message format, and Table 2-3 describes the message fields.

Figure 2-6 IGMPv2 message format
Table 2-3 Fields in an IGMPv2 message
Field Description
Type The four message type options are:
  • 0x11: Query message. IGMPv2 Query messages include General Query and Group-Specific Query messages.
  • 0x12: IGMPv1 Report message
  • 0x16: IGMPv2 Report message
  • 0x17: Leave message
Max Response Time After receiving a General Query message, hosts must respond with a Report message within the maximum response time. This field is valid only in IGMP Query messages.
Checksum The checksum is 16 bits long. It is the one's complement of the one's complement sum of the whole IGMP message (the entire IP payload). When computing the checksum, a device initially sets the checksum field to 0. The sender computes the checksum and inserts it into this field. The receiver verifies the checksum before processing the message.
Group Address The group address is set differently in different types of messages:
  • In a General Query message, this field is set to 0.
  • In a Group-Specific Query message, this field is set to the address of the queried group.
  • In a Report or Leave message, this field is set to the address of the group that the host wants to join or leave.

How IGMPv2 Works

IGMPv2 introduces the querier election and leave mechanisms.

Figure 2-7 shows a multicast network running IGMPv2. RouterA and RouterB connect to a network segment with three receivers: HostA, HostB, and HostC. HostA and HostB want to receive data sent to group G1, and HostC wants to receive data sent to group G2.
Figure 2-7 Multicast network

The following describes the querier election and leave processes on the network in Figure 2-7.

Querier election mechanism

IGMPv2 defines an independent querier election mechanism. When multiple multicast routers are present on a local network segment, the router with the smallest IP address is elected as the querier.

Figure 2-8 IGMPv2 querier election process

Figure 2-8 shows how an IGMPv2 querier is elected:

  1. All IGMPv2 routers (RouterA and RouterB in this example) consider themselves queriers and send General Query messages to all hosts and routers on the shared network segment.

    When the routers receive a General Query message, they compare the source IP address of the message with their own interface IP addresses. The router with the smallest IP address becomes the querier, and the other routers are considered non-queriers. In this example, RouterA has a smaller interface IP address than RouterB. Therefore, RouterA becomes a querier, and RouterB becomes a non-querier.

  2. The IGMP querier (RouterA) sends General Query messages to all hosts and other multicast routers on the local network segment. The non-querier (RouterB) no longer sends General Query messages.

    RouterB starts the other querier present timer. If RouterB receive a Query message from the querier before the timer expires, it resets the timer. Otherwise, it triggers a querier election.

Leave mechanism

Figure 2-9 IGMPv2 leave process

Figure 2-9 shows message exchanges when HostA leaves group G1:

  1. HostA sends a Leave message for G1 to all multicast routers on the local network segment. The destination address of the Leave message is 224.0.0.2.
  2. When the querier receives the Leave message, it sends Group-Specific Query messages for G1 at intervals to check whether G1 has other members on the network segment. The query interval and count are configurable. By default, the querier sends Group-Specific Query messages twice, at an interval of 1 second. In addition, the querier starts the group membership timer. The timer length is the product of the group-specific query interval and count.
  3. There is another member of G1 on the network segment, HostB, which sends a Report message for G1 immediately after receiving a Group-Specific Query message. The querier therefore continues maintaining the membership of G1.

    If G1 has no members on the network segment, the querier will not receive a Report message for G1. When the group membership timer times out, the querier deletes the (*, G1) entry. Thereafter, if the querier receives multicast data sent to G1, it does not forward the data downstream.

Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100075361

Views: 20219

Downloads: 21

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next