
•
To enable filtering, routers must keep track of more state information, that is, the list of sources that must be filtered. An
additional query type, the Group-and-Source-Specific Query, keeps track of state changes, while the Group-Specific and General
queries still refresh the existing state.
•
Reporting is more efficient and robust: hosts do not suppress query responses (non-suppression helps track state and enables
the immediate-leave and IGMP snooping features), state-change reports are retransmitted to insure delivery, and a single
membership report bundles multiple statements from a single host, rather than sending an individual packet for each statement.
The version 3 packet structure is different from version 2 to accommodate these protocol enhancements. Queries are still sent to
the all-systems address 224.0.0.1, as shown in the following illustration, but reports are sent to the all IGMP version 3-capable
multicast routers address 244.0.0.22, as shown in the second illustration.
Figure 48. IGMP Version 3 Packet Structure
Figure 49. IGMP Version 3–Capable Multicast Routers Address Structure
Joining and Filtering Groups and Sources
The following illustration shows how multicast routers maintain the group and source information from unsolicited reports.
1.
The first unsolicited report from the host indicates that it wants to receive traffic for group 224.1.1.1.
2.
The host’s second report indicates that it is only interested in traffic from group 224.1.1.1, source 10.11.1.1. Include messages
prevents traffic from all other sources in the group from reaching the subnet. Before recording this request, the querier sends a
group-and-source query to verify that there are no hosts interested in any other sources. The multicast router must satisfy all
hosts if they have conflicting requests. For example, if another host on the subnet is interested in traffic from 10.11.1.3, the
router cannot record the include request. There are no other interested hosts, so the request is recorded. At this point, the
multicast routing protocol prunes the tree to all but the specified sources.
348
Internet Group Management Protocol (IGMP)
Содержание S4048-ON
Страница 1: ...Dell Configuration Guide for the S4048 ON System 9 9 0 0 ...
Страница 146: ...Figure 14 BFD Three Way Handshake State Changes 146 Bidirectional Forwarding Detection BFD ...
Страница 477: ...Figure 68 Inspecting Configuration of LAG 10 on ALPHA Link Aggregation Control Protocol LACP 477 ...
Страница 480: ...Figure 70 Inspecting a LAG Port on BRAVO Using the show interface Command 480 Link Aggregation Control Protocol LACP ...
Страница 481: ...Figure 71 Inspecting LAG 10 Using the show interfaces port channel Command Link Aggregation Control Protocol LACP 481 ...
Страница 522: ...Figure 87 Configuring Interfaces for MSDP 522 Multicast Source Discovery Protocol MSDP ...
Страница 523: ...Figure 88 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 523 ...
Страница 524: ...Figure 89 Configuring PIM in Multiple Routing Domains 524 Multicast Source Discovery Protocol MSDP ...
Страница 528: ...Figure 91 MSDP Default Peer Scenario 1 528 Multicast Source Discovery Protocol MSDP ...
Страница 529: ...Figure 92 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 529 ...
Страница 530: ...Figure 93 MSDP Default Peer Scenario 3 530 Multicast Source Discovery Protocol MSDP ...
Страница 633: ...Policy based Routing PBR 633 ...
Страница 777: ...Figure 119 Single and Double Tag TPID Match Service Provider Bridging 777 ...
Страница 778: ...Figure 120 Single and Double Tag First byte TPID Match 778 Service Provider Bridging ...