Академический Документы
Профессиональный Документы
Культура Документы
Engineering Workshops
Engineering Workshops
` " 7 " #! % &$ % ( ' @ B) CA 10 &'4 3 56 () D a he b $V 10 4'3 65 WX' 2 w 6 % ( @ )CA B 1 6 ( ' ' 2 a 56 U &3 B tu a qv y u ) '( a h ig sar q p ce t u w x (8 6 () 9( c u 6 6 4 B R2 T CS 52 D BA 63 ' 3 A tu p ( 5 ef a cdb ` ` Y` B G% 6 H I7 H I! PQ 9( % B) @ )@ @ ! ! FE ` $E
Engineering Workshops
IGMP
Internet Group Management Protocol - how hosts tell routers about group membership Routers also solicit group membership from directly connected hosts RFC 1112 specifies version 1 of IGMP Supported on Windows 95 RFC 2236 specifies version 2 of IGMP Supported on latest service pack for Windows, newer Windows releases, and most UNIX systems RFC 3376 specifies version 3 of IGMP Provides source include-list capabilities (SSM!) Included in Linux kernel 2.5 and later See http://videolab.uoregon.edu/projects.html
Engineering Workshops
IGMPv2
Router: sends Membership Query messages to All Hosts (224.0.0.1) query-interval = 125 secs default router with lowest IP address is Querier (rest non-queriers) If lower-IP address query heard, back off to non-querier state Other Querier Present Interval default: (robust-count x query-interval) + (0.5 x query-response-interval) = 255 secs listens for reports (whether querier or not) and adds group to membership list for that interface query-response-interval = 10 secs default timeout (Group member interval) default: (robust-count x query-interval) + (1 x query-responseinterval) = 260 sec robust-count - provides fine-tuning to allow for expected packet loss on a subnet. Default = 2 (tunable from 2-10)
Engineering Workshops
IGMPv2
Host: sends Membership Report messages to groups it is a member of waits 0-10 sec (default) Hosts listen to other host reports Only 1 host responds sends unsolicited Membership Reports (i.e., Join Messages) to group address (e.g. 224.10.8.5) sends Leave messages to All Routers (224.0.0.2) reports group membership ONLY no sources. Only the existence of local group members is reported, not the actual members themselves Engineering Workshops
10
Soft State
Say I set up an active Multicast group, say by issuing a membership report. What happens if my computer goes down and never directly leaves the group ? This is fixed with Soft State Everything has a timer, and if not periodically reinitiated the timer will expire and the state will be removed. So there is no danger of some rogue group lasting forever.
Engineering Workshops
12
IGMPv3 Enhancements
Group-Source Report message is defined. Enables hosts to specify which senders it can receive or not receive data from. Group-Source Leave message is defined. Enables host to specify the specific IP addresses of a (source,group) that it wishes to leave.
Engineering Workshops
13
14
IGMP Snooping
Implemented by several vendors. Support for IGMPv2 is common; support for IGMPv3 is rare, but becoming more common. What happens at the MAC layer:
IGMP snoopers add a bridge table entry for each multicast group destination address (GDA) to each switch port that has the interested member's unicast source address (USA) already on it. (Remember that there are likely to be dumb hubs downstream of switches, so more than one USA can be on a single port.) When an IGMP Leave is received, the GDA entries are pruned.
Engineering Workshops
15
Engineering Workshops
16
17
CGMP
The proprietary Cisco Group Management Protocol puts the bulk of the Layer 3 logic in Layer 3 devices rather than cramming it into Layer 2 devices like IGMP snooping does. The router sends CGMP Joins and Leaves to the switch, specifying the USA and GDA. On receipt of an IGMP Membership Report, the router sends the switch a CGMP Join. On receipt of an IGMP Leave, the router sends the switch a CGMP Leave. IGMP membership reports still have to be suppressed so that hosts don't go into idle-member state. CGMP functioning is not well documented. Interactions with IGMPv3 are unclear. Engineering Workshops
18
19
20
Case Study
A few months ago I converted all our interfaces over to IGMP Version 3. Then I started getting complaints from our lab/classroom support group that Norton Ghost was failing for them. It would hang after about 3 minutes. So far the fix, without understanding why it works, has been to revert the interfaces to IGMP version 2. The switches downstream from these interfaces are running CGMP and CGMP LEAVE (which is actually a form of IGMP snooping/spoofing for IGMP Leaves sent to 224.0.0.2). I suspect that the fact that these switches are actually looking at IGMP packets may have something to do with the problem that reverting to v2 fixed... Alan Crosswell Engineering Workshops
21
Case Study
This author traveled to Los Alamos, New Mexico to help debug a multicast problem that had everyone stumped. Everyone was assuming the only known router on the subnet was also acting as the multicast gateway. Unfortunately, this wasnt the case. A nominally Layer 2 switch on the subnet was accidentally configured with PIM active, and won the PIM Designated Router election. Of course, this Layer 2 switch had no upstream to anywhere. Bill Nickless
Engineering Workshops
22
23
Engineering Workshops
24
Engineering Workshops
25
SSM
Engineering Workshops
26
PIM-SM
SM stands for Sparse Mode.
RFC 2362 and draft-ietf-pim-sm-v2-new-06.txt There is also a Dense Mode, but we dont recommend using it. Cisco has a proprietary Sparse-Dense mode which is used for RP discovery.
Engineering Workshops
27
Engineering Workshops
28
SSM
Source-Specific Multicast (SSM) is a subset of ASM, so SSM concepts apply directly to ASM, but SSM is a lot simpler than ASM. For these reasons, we cover SSM first in this workshop. 232 / 8 is assigned to SSM as an address space. Other address ranges can also be set up for SSM this is primarily a function of the receiving network. Source activity and IP addresses are assumed known. IGMPv3 allows for Include lists of (S,G) pairs.
Engineering Workshops
29
SSM
SSM - draft-ietf-ssm-arch-01.txt
232/8 IANA assigned No RPTs Guarantees ONE source on any delivery tree Content security no unwanted sources Reduced protocol dependence more later... Solves address allocation issues for inter-domain one-to-many tree address is 64 bits S,G Host must learn source address out-of-band (e.g, from a web page) Host-to-router join request specifies source as well as group requires IGMPv3 for include-source list SSM behavior in 232/8 by default Configurable to expand range
Engineering Workshops
30
SSM in Action
Each (S,G) pair listed in the IGMPv3 include list generates a (S,G) Join directly towards the source. Thats it. Its very simple. All you need to implement is : Edge routers need IGMPv3 Interior routers need filters to prevent RP (*,G) Joins & other RP state for the SSM address block
Engineering Workshops
31
Engineering Workshops
34
Lab 2: SSM
Engineering Workshops