Best Current Practices for IPv4 Multicast Deployment.ppt

1、Best Current Practices for IPv4 Multicast Deployment,Bill Nickless nicklessmcs.anl.gov http:/www.mcs.anl.gov/home/nickless,What is Multicast?,A multicast sender simply sends its data, and intervening routers “conspire“ to get the data to all interested listeners. (S. Deering) Destination of IP multi

2、cast packets is a “Group” address, within 224.0.0.0/4.,Notation,Specific source address(es): S Specific group address(es): G Specific source traffic for a group: (S,G) All sources traffic for a group: (*,G) Rendezvous Point RP,Any Source Multicast,Senders send multicast group-addressed packets. Rece

3、ivers register their interest in groups by way of IGMPv2 (*,G) Joins Network keeps track of all senders for each group, and delivers packets from all senders to each interested Receiver.,Source Specific Multicast,Senders send multicast group-addressed packets. Receivers register their interest in sp

4、ecific sources sending to specific groups by way of IGMPv3 (S,G) Joins (well, group membership reports.) Receivers are responsible for specifying which Senders traffic they want to receive.,Reachability,NOT DEFINED BY INTERNET STANDARDS,Reachability (Where To?),NOT DEFINED BY INTERNET STANDARDS Unic

5、ast reachability is interpreted by implementation and practice as: Send me IP packets with destination addresses that match this advertisement. Think show ip route,Reachability (Whence?),NOT DEFINED BY INTERNET STANDARDS Multicast reachability is interpreted by implementation and practice as: Heres

6、where to get IP packets from sources that match this advertisement. Think show ip rpf,Reachability Examples,terra% netstat rn Kernel IP routing table Destination Gateway Genmask Flags Iface 140.221.11.103 0.0.0.0 255.255.255.255 UH eth0 140.221.8.0 0.0.0.0 255.255.252.0 U eth0 127.0.0.0 0.0.0.0 255.

7、0.0.0 U lo 224.0.0.0 0.0.0.0 240.0.0.0 U eth0 0.0.0.0 140.221.11.253 0.0.0.0 UG eth0,Reachability Examples,Kiwi#show ip route 140.221.11.103 Routing entry for 140.221.8.0/22Known via “ospf 683“, distance 110, metric 1117, type intra areaLast update from 140.221.20.124 on GigabitEthernet5/0, 03:35:56

8、 agoRouting Descriptor Blocks:* 140.221.20.124, from 140.221.47.6, 03:35:56 ago, via GigabitEthernet5/0Route metric is 1117, traffic share count is 1,Reachability Examples,Kiwi#show ip rpf 140.221.11.103 RPF information for terra.mcs.anl.gov (140.221.11.103)RPF interface: GigabitEthernet5/0RPF neigh

9、bor: stardust-msfc-20.mcs.anl.gov (140.221.20.124)RPF route/mask: 140.221.8.0/22RPF type: unicast (ospf 683)RPF recursion count: 0Doing distance-preferred lookups across tables,The Old MBONE,Excellent first approximation. Used tunnels to encapsulate multicast traffic over unicast paths. Routing done

10、 by user-space daemons running on general purpose Unix boxes. Internet Group Management Protocol (IGMP) (Think Multicast ARP) Pre-dates the World Wide Web (hence SDR),Lessons Learned from MBONE,Distance Vector Metric Routing Protocol (DVMRP) does not scale Easy to create IP Multicast “amplifiers”. S

11、eparate tunneled routing infrastructure not aligned with modern BGP Internetworking. Flood & Prune does not scale Examples: PIM-Dense Mode, DVMRP. Not sensitive to available bandwidth. Requires downstream routers that are smart and powerful enough to send prune messages.,Applying Those Lessons,Multi

12、cast Border Gateway Protocol. Provides reachability and policy control for multicast routing, just as BGP does for unicast. Protocol Independent Multicast (Sparse Mode) Listeners receive traffic only when requested. Forms multicast distribution trees. Multicast Source Discovery Protocol Finding acti

13、ve sources in other PIM Sparse Mode domains (usually other ASes).,Setting Reachability Policy: Multicast Border Gateway Protocol,RFC 2283 adds the MP_REACH_NLRI attribute to BGP-4. Identifies a BGP route as unicast, multicast, or both When implemented in a router, all the standard BGP machinery is a

14、vailable for prefix filtering, preference setting, MEDs, AS length comparisons, etc. M-BGP routes can be independent of BGP, allowing for different inter-AS unicast/multicast reachability.,Cisco M-BGP Configuration,router bgp 683 network 130.202.0.0 nlri unicast multicast network 140.221.0.0 nlri un

15、icast multicast neighbor 192.5.170.130 remote-as 145 nlri unicast multicast neighbor 192.5.170.130 description vBNS neighbor 192.5.170.130 soft-reconfiguration inbound neighbor 192.5.170.130 route-map from-vbns-lp-400 in neighbor 192.5.170.130 route-map to-vbns-med-10 out,Cisco M-BGP Configuration,r

16、oute-map from-vbns-lp-400 permit 10 match nlri unicast set local-preference 400 ! route-map from-vbns-lp-400 permit 15 match as-path 145 match nlri multicast set local-preference 400 ! route-map to-vbns-med-10 permit 10 match ip address 50 set metric 10,Cisco M-BGP Configuration,access-list 50 permi

17、t 140.221.0.0 access-list 50 permit 130.202.0.0 ! ip as-path access-list 145 deny _24_ ip as-path access-list 145 deny _293_ ip as-path access-list 145 deny _11537_ ip as-path access-list 145 permit .*,Juniper M-BGP Configuration,routing-options rib inet.2 static route 141.142.0.0/16 reject;route 14

18、1.142.109.0/25 next-hop 141.142.11.74;route 141.142.109.128/25 next-hop 141.142.11.74;route 141.142.104.0/24 next-hop 141.142.11.74;route 141.142.105.0/24 next-hop 141.142.11.74;route 141.142.108.0/24 next-hop 141.142.11.74; ,Juniper M-BGP Configuration,routing-options rib-groups ifrg import-rib ine

19、t.0 inet.2 ; mcrg export-rib inet.2; import-rib inet.2; igp-rg export-rib inet.0; import-rib inet.0 inet.2 ; ,Juniper M-BGP Configuration,protocols bgp group anl import bgp-anl-accept reject-all ;family inet any; export bgp-announce-ncsa reject-all ;peer-as 683;neighbor 206.220.243.21; ,Monitoring M

20、-BGP (Cisco),Kiwi#show ip mbgp sum BGP router identifier 192.5.170.2, local AS number 683 MBGP table version is 324285 4121 network entries and 12621 paths using 862335 bytes of memory Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ 192.5.170.130 4 145 53420 20497 324285 0 0 Up/Down State/PfxRcd 5d14h

21、 346,Kiwi#show ip mbgp 128.163.3.214 MBGP routing table entry for 128.163.0.0/16, version 323761 Paths: (3 available, best #2)24 145 10490 10437, (aggregated by 10437 128.163.55.253), (received-only)192.12.123.10 from 192.12.123.10 (198.10.80.66)Origin IGP, localpref 100, valid, external, atomic-agg

22、regate145 10490 10437, (aggregated by 10437 128.163.55.253)192.5.170.130 from 192.5.170.130 (204.147.135.241)Origin IGP, localpref 400, valid, external, atomic-aggregate, best145 10490 10437, (aggregated by 10437 128.163.55.253), (received-only)192.5.170.130 from 192.5.170.130 (204.147.135.241)Origi

23、n IGP, localpref 100, valid, external, atomic-aggregate,Monitoring M-BGP (Juniper),nicklesscharlie show bgp neighbor 206.220.243.21 Peer: 206.220.243.21+179 AS 683 Local: 206.220.243.160+1969 AS 1224 . . .NLRI advertised by peer: inet-unicast inet-multicastNLRI for this session: inet-unicast inet-mu

24、lticastPeer supports Refresh capability (2)Table inet.0 Bit: 10006Active Prefixes: 13Received Prefixes: 13Suppressed due to damping: 0Table inet.2 Bit: 20006Active Prefixes: 9Received Prefixes: 9Suppressed due to damping: 0,nicklesscharlie show route table inet.2 140.221.34.1 inet.2: 5046 destinatio

25、ns, 5046 routes (5045 active, 0 holddown, 1 hidden) + = Active Route, - = Last Active, * = Both140.221.0.0/16 *BGP/170 2w5d 19:24:04, MED 0, localpref 1000AS path: 683 I to 206.220.243.21 via at-1/0/0.683BGP/170 3d 04:38:22, MED 0, localpref 60AS path: 11537 683 I to 141.142.11.246 via so-2/2/0.0BGP

26、/170 1w0d 11:18:35, localpref 60AS path: 145 683 I to 141.142.11.1 via at-1/0/0.145BGP/170 2w5d 19:23:42, localpref 60AS path: 38 683 I to 192.17.8.32 via at-1/0/0.38BGP/170 4d 05:55:21, MED 5, localpref 20AS path: 2914 683 I to 192.17.8.34 via at-1/0/0.2914,PIM Sparse Mode,RFC 2362 defines PIM Spar

27、se Mode. No PIM-SM activity until: A host starts transmitting traffic (or) A host subscribes to a group. A Rendezvous Point (RP) is the root of the shared distribution tree for multicast traffic within a PIM Domain. Given enough traffic, a source-based distribution tree is created. (Enough is typica

28、lly anything greater than zero). Inter-PIM Domain distribution trees are all source-based.,PIM Sparse Mode,Multicast Session Discovery Protocol (MSDP),Not yet an RFC (in Last Call stage). See http:/www.ietf.org/html.charters/msdp-charter.html and ftp:/ftp.ietf.org/internet-drafts/ draft-ietf-msdp-sp

29、ec-09.txt Currently only covers IPv4. PIM-SM RPs communicate through MSDP to find active multicast sources. If “interested”, the RP initiates a PIM-SM Join towards each active source.,Reachability Redux,A BGP NLRI=Multicast route is a statement of reachability. Inter-domain PIM-Sparse Mode Joins fol

30、low the BGP reachability topology. MSDP forwarding between RPs follows the BGP reachability topology. Not doing MSDP where you do M-BGP means that youve formed an MSDP “black hole”.,Cisco PIM-SM w/ MSDP Configuration,interface ATM3/0.145 point-to-point description vBNS MBGP+PIM-SM+MSDP ip address 19

31、2.5.170.129 255.255.255.252 ip pim border ip pim sparse-mode ip multicast ttl-threshold 32 ip multicast boundary 10 ip msdp peer 204.147.128.141 ip msdp description 204.147.128.141 vBNS ip msdp sa-filter in 204.147.128.141 list 111 ip msdp sa-filter out 204.147.128.141 list 111 ip msdp sa-request 20

32、4.147.128.141 ip msdp ttl-threshold 204.147.128.141 32 ip msdp cache-sa-state,access-list 10 deny 224.0.1.39 ! CISCO-RP-ANNOUNCE.MCAST.NET access-list 10 deny 224.0.1.40 ! CISCO-RP-DISCOVERY.MCAST.NET access-list 10 deny 239.0.0.0 0.255.255.255 access-list 10 permit 224.0.0.0 15.255.255.255 access-l

33、ist 111 deny ip any host 224.0.2.2 ! SUN-RPC.MCAST.NET access-list 111 deny ip any host 224.0.1.3 ! RWHOD.MCAST.NET access-list 111 deny ip any host 224.0.1.24 ! MICROSOFT-DS.MCAST.NET access-list 111 deny ip any host 224.0.1.22 ! SVRLOC.MCAST.NET access-list 111 deny ip any host 224.0.1.2 ! SGI-DOG

34、.MCAST.NET access-list 111 deny ip any host 224.0.1.35 ! SVRLOC-DA.MCAST.NET access-list 111 deny ip any host 224.0.1.60 ! HP-DEVICE-DISC.MCAST.NET access-list 111 deny ip any host 224.0.1.39 ! CISCO-RP-ANNOUNCE.MCAST.NET access-list 111 deny ip any host 224.0.1.40 ! CISCO-RP-DISCOVERY.MCAST.NET acc

35、ess-list 111 deny ip any 239.0.0.0 0.255.255.255 access-list 111 deny ip 10.0.0.0 0.255.255.255 any access-list 111 deny ip 127.0.0.0 0.255.255.255 any access-list 111 deny ip 172.16.0.0 0.15.255.255 any access-list 111 deny ip 192.168.0.0 0.0.255.255 any access-list 111 permit ip any,Juniper PIM-SM

36、 w/ MSDP Config,protocols pim rib-group mcrg;rp local address 141.142.12.1; interface all mode sparse;version 2; ,Juniper PIM-SM w/ MSDP Config,protocols msdp rib-group mcrg; group anl /* kiwi-loop.anchor.anl.gov */peer 192.5.170.2 local-address 141.142.12.1; ,Monitoring MSDP and PIM-Sparse,Verify t

37、hat MSDP session has come up with your peer: Kiwi#show ip msdp sum MSDP Peer Status Summary Peer Address AS State Uptime/ Reset Peer Name Downtime Count 204.147.128.141 145 Up 1d12h 11 nicklesscharlie show msdp peer 192.5.170.2 Peer address Local address State Last up/down Peer-Group 192.5.170.2 141

38、.142.12.1 Established 2w5d18h anl,Monitoring MSDP and PIM-Sparse,Verify that active sources are being discovered: Kiwi#show ip msdp sa-cache 224.2.177.155 MSDP Source-Active Cache - 4020 entries (128.197.160.27, 224.2.177.155), RP 204.147.128.141, MBGP/AS 145, 03:40:18/00:05:03 etc nicklesscharlie s

39、how msdp source-active group 233.2.171.1 Group address Source address Peer address Originator Flags 233.2.171.1 140.221.34.1 141.142.11.246 192.5.170.2 Accept192.5.170.2 192.5.170.2 Accept192.17.8.32 192.5.170.2 Accept204.147.128.141 192.5.170.2 Accept,Monitoring MSDP and PIM-Sparse,Verify that you

40、are receiving traffic from those active sources, and are forwarding: Kiwi#show ip mroute count 224.2.177.155 128.163.3.214 Forwarding Counts: Pkt Count/Pkts per second/ Avg Pkt Size/Kilobits per second Other counts: Total/RPF failed/ Other drops(OIF-null, rate-limit etc) Group: 224.2.177.155, Source

41、 count: 26, Group pkt count: 31060731 RP-tree: Forwarding: 159/0/429/0, Other: 72/0/0 Source: 128.163.3.214/32, Forwarding: 7089/0/480/0, Other: 6/0/0,Kiwi#show ip mroute 224.2.177.155 128.163.3.214 IP Multicast Routing Table Flags: D - Dense, S - Sparse, C - Connected, L - Local, P - Pruned R - RP-

42、bit set, F - Register flag, T - SPT-bit set, J - Join SPT, M - MSDP created entry, X - Proxy Join Timer Running Timers: Uptime/Expires Interface state: Interface, Next-Hop or VCD, State/Mode (128.163.3.214, 224.2.177.155), 03:55:28/00:03:22, flags: MTIncoming interface: ATM3/0.145, RPF nbr 192.5.170

43、.130, MbgpOutgoing interface list:ATM0/0.216, Forward/Sparse, 03:55:28/00:03:08ATM0/0.200, Forward/Sparse, 03:55:28/00:02:04,nicklesscharlie show multicast route group 233.2.171.1 source-prefix 140.221.34.1 extensive Group Source prefix Act Pru NHid Packets IfMismatch T/O 233.2.171.1 140.221.34.1 /3

44、2 A F 68 1829657 0 355Upstream interface: at-1/0/0.683Session name: Static Allocationsnicklesscharlie show multicast route group 233.2.171.1 source-prefix 140.221.34.1 extensive Group Source prefix Act Pru NHid Packets IfMismatch T/O 233.2.171.1 140.221.34.1 /32 A F 68 1830512 0 355Upstream interfac

45、e: at-1/0/0.683Session name: Static Allocations,nicklesscharlie show pim join 233.2.171.1 extensive Group Source RP Flags. . .233.2.171.1 140.221.34.1 sparse,spt-pending Upstream interface: at-1/0/0.683 Upstream State: Local RP, Join to Source Downstream Neighbors: Interface: ge-1/1/0.103 141.142.0.

46、14 State: Join Flags: S Timeout: 182 Interface: gr-1/2/0.0 141.142.11.74 State: Join Flags: S Timeout: 208,Other Tips,ATM peerings are best done with point-to-point subinterfaces. (Whats a Designated Router in the context of an ATM exchange point, anyway?) MSDP Source Actives are made from PIM Regis

47、ter messages. If youre not sending MSDP SA messages for a source, you may have a problem with the Designated Router for that source.,More Tips,MSDP encapsulates data in its Source Active messages (just like they were encapsulated in the PIM Sparse Mode Register messages). This was done primarily to

48、support SDR. It is possible for MSDP to work while PIM-SM is not working, so you cant always count on SDR to verify multicast routing.,Debugging Multicast,You must have: at least one constantly active source at least one constantly active receiver Start near the receiver Identify the PIM-SM Designated Router Verify IGMP state in the Designated Router Look for (S,G) state in the Designated Router,