25.02.2013 Views

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

2. Subset A is currently included. However, only subset B is desired. To do this,<br />

first an ALLOW_NEW_SOURCES message is issued to add all of subset B<br />

except for those addresses already included in A. This is followed by a<br />

BLOCK_OLD_SOURCES message to exclude all of subset A except for<br />

those addresses which also belong to B.<br />

3. Now only subset B is included. However, we want to change the filter to<br />

EXCLUDE, <strong>and</strong> to specify only subset A. This is done with one<br />

CHANGE_TO_EXCLUDE_MODE specifying subset A.<br />

4. After step 3, only subset A is excluded. Now, we want to exclude only<br />

subset B. First issue an ALLOW_NEW_SOURCES message to remove all of<br />

subset A from the excluded list except those addresses also in subset B.<br />

Then add all of the addresses in subset B to the exclude list except for those<br />

also in subset A.<br />

5. Now only subset B is excluded. We want to change the filter to INCLUDE <strong>and</strong><br />

add A to the list. Use the CHANGE_TO_INCLUDE_MODE specifying<br />

subset A.<br />

Multicast router operations<br />

When a host attempts to join a group, multicast routers on the subnet receive the<br />

membership report packet <strong>and</strong> create an entry in their local group database. This<br />

database tracks the group membership of the router’s directly attached networks.<br />

Each entry in the database is of the format [group, attached network]. This<br />

indicates that the attached network has at least one <strong>IP</strong> host belonging to the<br />

group. Multicast routers listen to all multicast addresses to detect these reports.<br />

The information in the local group database is used to forward multicast<br />

datagrams. When the router receives a datagram, it is forwarded out each<br />

interface containing hosts belonging to the group.<br />

To verify group membership, multicast routers regularly send an IGMP query<br />

message to the all hosts’ multicast address. Each host that still wants to be a<br />

member of a group sends a reply. RFC 3376 specifies this verification should by<br />

default occur every 125 seconds. To avoid bursts of traffic on the subnet, replies<br />

to query messages are sent using a r<strong>and</strong>om delay. Because routers do not track<br />

the number of hosts in each group, any host that hears another device claim<br />

membership cancels any pending membership replies. If no hosts claim<br />

membership within the specified interval, the multicast router assumes no hosts<br />

on that network are members of the group.<br />

IGMP snooping switches<br />

One potential problem when implementing IGMP is the flooding of a network<br />

segment with multicast packets, even though there might not be any nodes on<br />

that segment that have any interest in receiving the packets. Although the<br />

Chapter 6. <strong>IP</strong> multicast 249

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

Saved successfully!

Ooh no, something went wrong!