22.10.2013 Views

7.8.1.0 - Force10 Networks

7.8.1.0 - Force10 Networks

7.8.1.0 - Force10 Networks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Figure 196<br />

Leaving a Multicast Group<br />

1. A host sends a membership report of type 0x17 (IGMP Leave message) to the all routers multicast<br />

address 224.0.0.2 when it no longer cares about multicast traffic for a particular group.<br />

2. The querier sends a Group-Specific Query to determine whether there are any remaining hosts in the<br />

group. There must be at least one receiver in a group on a subnet for a router to forward multicast<br />

traffic for that group to the subnet.<br />

3. Any remaining hosts respond to the query according to the delay timer mechanism (see Adjusting<br />

Query and Response Timers on page 338). If no hosts respond (because there are none remaining in<br />

the group) the querier waits a specified period, and sends another query. If it still receives no response,<br />

the querier removes the group from the list associated with forwarding port and stops forwarding<br />

traffic for that group to the subnet.<br />

IGMP version 3<br />

Conceptually, IGMP version 3 behaves the same as version 2. There are differences:<br />

• Version 3 adds the ability to filter by multicast source, which helps multicast routing protocols avoid<br />

forwarding traffic to subnets where there are no interested receivers.<br />

• To enable filtering, routers must keep track of more state information, that is, the list of sources that<br />

must be filtered. An additional query type, the Group-and-Source-Specific Query, keeps track of state<br />

changes, while the Group-Specific and General queries still refresh existing state.<br />

• Reporting is more efficient and robust: hosts do not suppress query responses (non-suppression helps<br />

track state and enables the immediate-leave and IGMP Snooping features), state-change reports are<br />

retransmitted to insure delivery, and a single membership report bundles multiple statements from a<br />

single host, rather than sending an individual packet for each statement.<br />

The version 3 packet structure is different from version 2 to accommodate these protocol enhancements.<br />

Queries (Figure 196) are still sent to the all-systems address 224.0.0.1, but reports (Figure 197) are sent to<br />

the all IGMP version 3-capable multicast routers address 244.0.0.22 .<br />

Type<br />

(0x11)<br />

Code: 0x11: Membership Query<br />

IGMP version 3 Membership Query Packet Format<br />

Max. Response<br />

Code<br />

Maximum Response Time<br />

derived from this value<br />

Checksum<br />

Group Address<br />

Reserved S Querier Robustness<br />

Value<br />

(2)<br />

Bit flag that when set to<br />

1 suppresses router query<br />

response timer updates<br />

Querier's Query<br />

Interval Code<br />

Query Interval derived<br />

from this value<br />

Number of times that a<br />

router or receiver transmits<br />

a query or report to insure<br />

that it is received<br />

FTOS Configuration Guide, version <strong>7.8.1.0</strong> 333<br />

Number of<br />

Sources<br />

Number of source addresses<br />

to be filtered<br />

Source Addresses<br />

Source addresses to be<br />

filtered<br />

fnC0070mp

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!