INE Multicast   Alp ISIK  13.11.2011
Topology
PIM Dense Mode• Flooding için  1 – SPT shortest path tree oluşturulur.  2- Reverse path forwarding kullanılarak multicast ...
• PIM DM konuşturmak istediğimiz router’da  oncelikle• ip multicast routing // açılır.• İnterface duzeyinde // “ip pim den...
• Show ip pim neigh• Show ip pim int• Show ip mroute---------------Rack1R4#show ip mroute(*, 224.10.10.10), 00:01:35/stopp...
8.2 RPF• Config altında // “ip multicast rpf ?” komutları ile rpf timerlarla oynanabilir.• ****İnterface altında no ip mro...
8.3 PIM Sparse mode• PIM SM konuşturmak istediğimiz router’da oncelikle• ip multicast routing // açılır.• Receiver ve sour...
PIM Sparse-Dense Mode• Hybrid combination of sparse nad dense  mode.• Configure edildiği interface’de both spase and  dens...
RP for specific groupsip pim rp-address 150.1.5.5 <access-list>
8.5 PIM Assert• Eger aynı multicast route iki farklı yerden  ogreniliyorsa, ilk AD, metric sonra buyuk ip’li  olan yol ter...
8.6 PIM Accept RP• As a security feature in order to routers only  accept (*,G) from a specific RP.ip pim accept-rp 150.1....
PIM DR Election• DR multiple-access segmentte multicast  source registration’dan sorumludur.• İnterface altında // ip pim ...
PIM Accept register• Tek bir source’a izin verilmesinde kullanılır.• Konfigurasyon RP’ de yapılır.• Filtreleme için RP ve ...
Multicast tunneling• Tunelde pim enable edilmeli,---------------------------interface Tunnel0   ip unnumbered Loopback0   ...
8.10 PIM NBMA mode• Broadcast queue’sunda gonderilir.• Full mesh olmadığı durumda kullanılır.• PIM-SM’de calısır. Sparse-d...
8.11 Auto RP                                    M source• İki consept içerir candidate RP (cRP) ve Mapping            R6 E...
8.12 Auto-rp multiple candidate RP• Primary-backup olarak calıstırabiliriz. //highest  IP will be selected.• Aynı grup içi...
8.13 auto-rp – filtering candidate RPsip pim rp-announce-filter rp-list RP_LIST group-  list GROUP_LIST // rp-list ile RP’...
8.14 auto-rp listener• Auto-RP listener, auto-rp kullanılırken  224.0.1.39 ve 224.0.1.40’ın automatik  dinlenilmesini sağl...
8.15 Auto-RP and RP/MA Placement                                             M source• Hub & Spoke da hub ve spoke u RP   ...
8.16 Filtering Auto RP Messages• AutoRP mesajlarını filtrelemek için scope ile  TTL ayarlanabilir ya da //ip multicast bou...
8.17 multicast boundry• Multicast boundry ile multicast trafige (control  plane and data plane)sınır koyabiliriz.• Unicast...
8.18 PIM Bootstrap Router• It’s the stadards-based protocol, autorp ile aynı işi  yaparlar.• Rp candidate’te priority’de d...
8.19 BSR – Multiple RP Candidates• SW2, SW4 RP candidate; R5 is BSR-------------------• Aynı grup için yüksek ip li router...
8.20 Filtering BSR Messages• Not to learn any RP information via BSR• İnterface level //ip pim bsr-border
8.21 stub multicast routing & IGMP Helper             e0/0                             FR         S2/0                    ...
IGMP Filtering• İnterface altında // ip igmp access-group <IGMP_FILTER>                     //ip igmp limit 10
IGMP Timers• İnterface altında//ip igmp querry-interval 20//ip igmp querry-max-response-time 4//ip igmp immediate-leave gr...
8.24 Multicast Helper Map•   R1    ip forward-protocol UDP 5000    inte0/0            ip multicast helper-map broadcast 23...
8.25 Multicast Rate limiting• İnterface altında //  ip multicast rate-limit out group-list <access-list> 128  ip multicast...
8.26 Bidirectional PIM• Global configte //İp pim bidir-enable//ip pim rp-candidate lo0 group-list <access-list>   bidir
PIM SSM Source Specific Multicast• IGMPv3 ile yalnızca SPT oluşturur. RP yok.  (shared tree yok)Global configte//ip pim ss...
8.28 DVMRP Interoperability• Tunelling DVMRPint tunn 0   ip unnumbered lo0   İp pim dense-mode // komsuluk kurulmasada mca...
8.29 Multicast BGP Extention• In general PIM-SM is used, her bir domainin kendi RP si  olmalı, bsr ve auto-rp bilgisinin d...
• R4  route-map PREPEND       set as-path prepend 200 200 200  router bgp 200       address-family ipv4 multicast       ne...
• R5  router bgp 200       address-family ipv4 multicast       neighbor 155.1.0.3 activate       redistribute eigrp 100   ...
• R6  route-map PREPEND       set as-path prepend 100 100 100  router bgp 100       address-family ipv4 multicast       ne...
•   SW1    router bgp 100          address-family ipv4 multicast          neighbor IBGP route-reflector-client          ne...
MSDP   Msdp peerMsdp peer
8.30 MSDP multicast source discovery protocol• Interdomain multicastta her bir domainin kendi RP si vardır, farklı  domain...
8.31 Anycast RP• Her iki RP yi aynı IP ile gosterip yedeklilik sağlar.• RP için yeni bir lo100 yarattık.• PIM join’ler en ...
• At SW2   interface Loopback100         ip address 150.1.100.100 255.255.255.255         ip pim sparse-mode   router erig...
IGMP Snooping• Global configte //İp igmp snooping vlan 146  immediate-leave• Check etmek için //show ip igmp snooping mrou...
Multicast VLAN Registrationmvrmvr vlan 146mvr group 146mvr group 239.1.1.100mvr mode dynamicint ether 0/1    mvr type sour...
IGMP Profilesip igmp profile 1  permit  range 232.0.0.0 232.255.255.255  range 239.0.0.0 239.255.255.255int e0/4  ip igmp ...
kısaltmalar• OIL : outgoing interface list.• Multicast spt switchover : (*,G) to (S,G)
Ine Multicast
Upcoming SlideShare
Loading in …5
×

Ine Multicast

966 views

Published on

multicast

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
966
On SlideShare
0
From Embeds
0
Number of Embeds
7
Actions
Shares
0
Downloads
14
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Last updated 07.03.2012
  • Rack1R5#shippimrpmappPIM Group-to-RP MappingsThis system is an RP (Auto-RP)Group(s) 224.0.0.0/4 RP 150.1.5.5 (?), v2v1 Info source: 150.1.8.8 (?), elected via Auto-RP Uptime: 00:59:51, expires: 00:02:34----------------------------------------------------------------
  • Rack1R5#sh ip pim rp mappPIM Group-to-RP MappingsGroup(s) 224.0.0.0/5 RP 150.1.8.8 (?), v2v1 Info source: 150.1.8.8 (?), elected via Auto-RP Uptime: 00:09:07, expires: 00:02:00Group(s) 224.0.0.0/4 RP 150.1.10.10 (?), v2v1 Info source: 150.1.8.8 (?), elected via Auto-RP Uptime: 00:06:54, expires: 00:02:02Group(s) (-)224.110.110.110/32 RP 150.1.10.10 (?), v2v1 Info source: 150.1.8.8 (?), elected via Auto-RP Uptime: 00:05:54, expires: 00:02:02Group(s) 232.0.0.0/5 RP 150.1.10.10 (?), v2v1 Info source: 150.1.8.8 (?), elected via Auto-RP Uptime: 00:05:54, expires: 00:02:00Rack1R5#sh ip pim rp mappPIM Group-to-RP MappingsGroup(s) 224.0.0.0/5 RP 150.1.8.8 (?), v2v1 Info source: 150.1.8.8 (?), elected via Auto-RP Uptime: 00:09:07, expires: 00:02:00Group(s) 224.0.0.0/4 RP 150.1.10.10 (?), v2v1 Info source: 150.1.8.8 (?), elected via Auto-RP Uptime: 00:06:54, expires: 00:02:02Group(s) (-)224.110.110.110/32 RP 150.1.10.10 (?), v2v1 Info source: 150.1.8.8 (?), elected via Auto-RP Uptime: 00:05:54, expires: 00:02:02Group(s) 232.0.0.0/5 RP 150.1.10.10 (?), v2v1 Info source: 150.1.8.8 (?), elected via Auto-RP Uptime: 00:05:54, expires: 00:02:00
  • Rack1R5(config)#do sh ip pim interfAddress Interface Ver/ Nbr Query DR DR Mode Count Intvl Prior155.1.45.5 Serial2/1 v2/S 1 30 1 0.0.0.0155.1.58.5 Ethernet0/0 v2/S 1 30 1 155.1.58.8150.1.5.5 Loopback0 v2/SD 0 30 1 150.1.5.5Rack1R5(config)#do sh ip mrouteIP Multicast Routing TableFlags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected, L - Local, P - Pruned, R - RP-bit set, F - Register flag, T - SPT-bit set, J - Join SPT, M - MSDP created entry, X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement, U - URD, I - Received Source Specific Host Report, Z - Multicast Tunnel, z - MDT-data group sender, Y - Joined MDT-data group, y - Sending to MDT-data group, V - RD &amp; Vector, v - VectorOutgoing interface flags: H - Hardware switched, A - Assert winner Timers: Uptime/Expires Interface state: Interface, Next-Hop or VCD, State/Mode(*, 224.0.1.39), 00:03:36/stopped, RP 0.0.0.0, flags: DC Incoming interface: Null, RPF nbr 0.0.0.0 Outgoing interface list: Serial2/1, Forward/Sparse, 00:03:36/00:00:00 Ethernet0/0, Forward/Sparse, 00:03:36/00:00:00(150.1.10.10, 224.0.1.39), 00:03:13/00:02:53, flags: T Incoming interface: Ethernet0/0, RPF nbr 155.1.58.8 Outgoing interface list: Serial2/1, Forward/Sparse, 00:00:13/00:00:00(150.1.8.8, 224.0.1.39), 00:03:25/00:02:43, flags: T Incoming interface: Ethernet0/0, RPF nbr 155.1.58.8 Outgoing interface list: Serial2/1, Forward/Sparse, 00:00:25/00:00:00(*, 224.0.1.40), 00:03:36/stopped, RP 0.0.0.0, flags: DCL Incoming interface: Null, RPF nbr 0.0.0.0 Outgoing interface list: Serial2/1, Forward/Sparse, 00:03:38/00:00:00 Ethernet0/0, Forward/Sparse, 00:03:38/00:00:00(150.1.8.8, 224.0.1.40), 00:03:35/00:02:31, flags: LT Incoming interface: Ethernet0/0, RPF nbr 155.1.58.8 Outgoing interface list: Serial2/1, Forward/Sparse, 00:03:35/00:00:00Rack1R6(config)#do sh ip pim rp mappPIM Group-to-RP MappingsGroup(s) 224.0.0.0/5 RP 150.1.8.8 (?), v2v1 Info source: 150.1.8.8 (?), elected via Auto-RP Uptime: 00:43:34, expires: 00:02:23Group(s) 224.0.0.0/4 RP 150.1.10.10 (?), v2v1 Info source: 150.1.8.8 (?), elected via Auto-RP Uptime: 00:41:21, expires: 00:02:24Group(s) (-)224.110.110.110/32 RP 150.1.10.10 (?), v2v1 Info source: 150.1.8.8 (?), elected via Auto-RP Uptime: 00:40:21, expires: 00:02:23Group(s) 232.0.0.0/5 RP 150.1.10.10 (?), v2v1 Info source: 150.1.8.8 (?), elected via Auto-RP Uptime: 00:40:21, expires: 00:02:24
  • NOT : RP’de tunnel 0 pim registering için ayrılır.Rack1R1#sh ip mroute 224.0.1.39IP Multicast Routing TableFlags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected, L - Local, P - Pruned, R - RP-bit set, F - Register flag, T - SPT-bit set, J - Join SPT, M - MSDP created entry, X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement, U - URD, I - Received Source Specific Host Report, Z - Multicast Tunnel, z - MDT-data group sender, Y - Joined MDT-data group, y - Sending to MDT-data group, V - RD &amp; Vector, v - VectorOutgoing interface flags: H - Hardware switched, A - Assert winner Timers: Uptime/Expires Interface state: Interface, Next-Hop or VCD, State/Mode(*, 224.0.1.39), 01:00:27/stopped, RP 0.0.0.0, flags: DCL Incoming interface: Null, RPF nbr 0.0.0.0 Outgoing interface list: Loopback0, Forward/Sparse, 00:36:30/00:02:42 Serial2/0.1, Forward/Sparse, 00:36:30/00:02:43 Tunnel1, Forward/Sparse, 00:35:16/00:00:00(150.1.10.10, 224.0.1.39), 00:33:06/00:02:07, flags: LT Incoming interface: Serial2/0.1, RPF nbr 155.1.0.5 Outgoing interface list: Loopback0, Forward/Sparse, 00:33:06/00:02:42 Tunnel1, Forward/Sparse, 00:33:06/00:00:00(150.1.8.8, 224.0.1.39), 00:33:17/00:02:57, flags: LT Incoming interface: Serial2/0.1, RPF nbr 155.1.0.5 Outgoing interface list: Loopback0, Forward/Sparse, 00:33:17/00:02:42 Tunnel1, Forward/Sparse, 00:33:17/00:00:00 Rack1R3(config-if)#do sh ip mroute 224.0.1.40IP Multicast Routing TableFlags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected, L - Local, P - Pruned, R - RP-bit set, F - Register flag, T - SPT-bit set, J - Join SPT, M - MSDP created entry, X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement, U - URD, I - Received Source Specific Host Report, Z - Multicast Tunnel, z - MDT-data group sender, Y - Joined MDT-data group, y - Sending to MDT-data group, V - RD &amp; Vector, v - VectorOutgoing interface flags: H - Hardware switched, A - Assert winner Timers: Uptime/Expires Interface state: Interface, Next-Hop or VCD, State/Mode(*, 224.0.1.40), 01:17:19/stopped, RP 0.0.0.0, flags: DCL Incoming interface: Null, RPF nbr 0.0.0.0 Outgoing interface list: Serial2/0.1, Forward/Sparse, 01:17:20/00:02:16(150.1.8.8, 224.0.1.40), 00:01:40/00:01:19, flags: L Incoming interface: Null, RPF nbr 155.1.37.7 Outgoing interface list: Serial2/0.1, Forward/Sparse, 00:01:40/00:02:16(150.1.1.1, 224.0.1.40), 00:39:41/00:02:08, flags: LT Incoming interface: Tunnel1, RPF nbr 150.1.1.1, Mroute Outgoing interface list: Serial2/0.1, Forward/Sparse, 00:39:41/00:02:16
  • Rack1R1(config)#do sh ip pim rp mappPIM Group-to-RP MappingsGroup(s) 224.0.0.0/4 RP 150.1.5.5 (?), v2 Info source: 150.1.5.5 (?), via bootstrap, priority 0, holdtime 150 Uptime: 00:00:20, expires: 00:02:13Rack1R1(config)#do sh ip pim bsr-routerPIMv2 Bootstrap information BSR address: 150.1.5.5 (?) Uptime: 00:02:12, BSR Priority: 0, Hash mask length: 0 Expires: 00:01:58
  • Rack1R4(config)#do sh ip pim rp-hash 239.1.1.1 RP 150.1.10.10 (?), v2 Info source: 150.1.10.10 (?), via bootstrap, priority 0, holdtime 150 Uptime: 00:06:59, expires: 00:01:41 PIMv2 Hash Value (mask 255.255.255.254) RP 150.1.10.10, via bootstrap, priority 0, hash value 989207280 RP 150.1.8.8, via bootstrap, priority 0, hash value 718054422Rack1R4(config)#do sh ip pim rp-hash 239.1.1.2 RP 150.1.8.8 (?), v2 Info source: 150.1.10.10 (?), via bootstrap, priority 0, holdtime 150 Uptime: 00:07:27, expires: 00:02:24 PIMv2 Hash Value (mask 255.255.255.254) RP 150.1.10.10, via bootstrap, priority 0, hash value 1093093598 RP 150.1.8.8, via bootstrap, priority 0, hash value 1364246456
  • Rack1R5(config)#do shipigmp groupsIGMP Connected Group MembershipGroup Address Interface Uptime Expires Last Reporter Group Accounted239.1.1.7 Serial2/0 00:01:33 00:02:44 155.1.0.3 224.0.1.40 Serial2/0 00:01:25 00:02:43 155.1.0.3 224.0.1.40 Serial2/1 06:30:47 stopped 155.1.45.5 Rack1SW2(config)#do ping 239.1.1.7Type escape sequence to abort.Sending 1, 100-byte ICMPEchos to 239.1.1.7, timeout is 2 seconds:Reply to request 0 from 155.1.37.7, 72 msRack1R3(config-subif)#do sh ip mroute 239.1.1.7IP Multicast Routing TableFlags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected, L - Local, P - Pruned, R - RP-bit set, F - Register flag, T - SPT-bit set, J - Join SPT, M - MSDP created entry, X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement, U - URD, I - Received Source Specific Host Report, Z - Multicast Tunnel, z - MDT-data group sender, Y - Joined MDT-data group, y - Sending to MDT-data group, V - RD &amp; Vector, v - VectorOutgoing interface flags: H - Hardware switched, A - Assert winner Timers: Uptime/Expires Interface state: Interface, Next-Hop or VCD, State/Mode(*, 239.1.1.7), 00:04:07/stopped, RP 0.0.0.0, flags: DC Incoming interface: Null, RPF nbr 0.0.0.0 Outgoing interface list: Ethernet0/0, Forward/Dense, 00:04:07/00:00:00 Serial2/0.1, Forward/Dense, 00:04:07/00:00:00
  • Rack1R3#shipigmp interface e0/0Ethernet0/0 is up, line protocol is up Internet address is 155.1.37.3/24IGMP is enabled on interface Current IGMP host version is 2 Current IGMP router version is 2IGMP query interval is 60 secondsIGMPquerier timeout is 120 secondsIGMP max query response time is 10 seconds Last member query count is 2 Last member query response interval is 1000 ms Inbound IGMP access group is IGMP_FILTERIGMP activity: 3 joins, 2 leaves Interface IGMP State Limit : 1 active out of 10 max Multicast routing is enabled on interface Multicast TTL threshold is 0 Multicast designated router (DR) is 155.1.37.7 IGMP querying router is 155.1.37.3 (this system)IGMP helper address is 155.1.0.5 No multicast groups joined by this system
  • Ip helper address : broadcast to unicastIp multicast helper map : broadcast to multicast
  • Rack1R6(config-subif)#do sh ip pim rp mappPIM Group-to-RP MappingsRack1R6(config-subif)#
  • Her bir autonom sistemde farklı RP’lerin yedekli calısmasını sağlar. Receiverlar, diğer autonom sistemdeki source’dan yayın alır.Mtrace 150.1.10.10 239.1.1.1Rack1R4(config-router)#do sh ip pim rp-hash 239.1.1.1 RP 150.1.5.5 (?), v2 Info source: 150.1.10.10 (?), via bootstrap, priority 0, holdtime 150 Uptime: 00:05:45, expires: 00:02:04 PIMv2 Hash Value (mask 255.255.255.254) RP 150.1.5.5, via bootstrap, priority 0, hash value 1362971077 RP 150.1.8.8, via bootstrap, priority 0, hash value 718054422Rack1R4(config-router)#do sh ip pim rp-hash 239.1.1.2 RP 150.1.8.8 (?), v2 Info source: 150.1.10.10 (?), via bootstrap, priority 0, holdtime 150 Uptime: 00:05:45, expires: 00:01:47 PIMv2 Hash Value (mask 255.255.255.254) RP 150.1.5.5, via bootstrap, priority 0, hash value 443334807 RP 150.1.8.8, via bootstrap, priority 0, hash value 1364246456Rack1SW3#sh ip mroute 239.1.1.1IP Multicast Routing TableFlags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected, L - Local, P - Pruned, R - RP-bit set, F - Register flag, T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet, X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement, U - URD, I - Received Source Specific Host Report, Z - Multicast Tunnel, z - MDT-data group sender, Y - Joined MDT-data group, y - Sending to MDT-data group V - RD &amp; Vector, v - VectorOutgoing interface flags: H - Hardware switched, A - Assert winner Timers: Uptime/Expires Interface state: Interface, Next-Hop or VCD, State/Mode(*, 239.1.1.1), 00:00:23/stopped, RP 150.1.7.7, flags: SJCL Incoming interface: Vlan79, RPF nbr 155.1.79.7 Outgoing interface list: Loopback0, Forward/Sparse, 00:00:23/00:02:43(155.1.67.6, 239.1.1.1), 00:00:06/00:02:53, flags: LJT Incoming interface: Vlan79, RPF nbr 155.1.79.7 Outgoing interface list: Loopback0, Forward/Sparse, 00:00:06/00:02:53Rack1R4#sh ip mroute 239.1.1.1IP Multicast Routing TableFlags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected, L - Local, P - Pruned, R - RP-bit set, F - Register flag, T - SPT-bit set, J - Join SPT, M - MSDP created entry, X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement, U - URD, I - Received Source Specific Host Report, Z - Multicast Tunnel, z - MDT-data group sender, Y - Joined MDT-data group, y - Sending to MDT-data group, V - RD &amp; Vector, v - VectorOutgoing interface flags: H - Hardware switched, A - Assert winner Timers: Uptime/Expires Interface state: Interface, Next-Hop or VCD, State/Mode(*, 239.1.1.1), 00:15:53/00:01:32, RP 150.1.5.5, flags: SJCL Incoming interface: Serial2/1, RPF nbr 155.1.45.5 Outgoing interface list: Loopback0, Forward/Sparse, 00:15:53/00:02:07(155.1.146.6, 239.1.1.1), 00:03:31/00:01:34, flags: LJT Incoming interface: Ethernet0/1, RPF nbr 155.1.146.6 Outgoing interface list: Loopback0, Forward/Sparse, 00:03:31/00:02:07Rack1SW3#sh ip mroute 239.1.1.1IP Multicast Routing TableFlags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected, L - Local, P - Pruned, R - RP-bit set, F - Register flag, T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet, X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement, U - URD, I - Received Source Specific Host Report, Z - Multicast Tunnel, z - MDT-data group sender, Y - Joined MDT-data group, y - Sending to MDT-data group V - RD &amp; Vector, v - VectorOutgoing interface flags: H - Hardware switched, A - Assert winner Timers: Uptime/Expires Interface state: Interface, Next-Hop or VCD, State/Mode(*, 239.1.1.1), 00:06:57/stopped, RP 150.1.7.7, flags: SJCL Incoming interface: Vlan79, RPF nbr 155.1.79.7 Outgoing interface list: Loopback0, Forward/Sparse, 00:06:57/00:02:12(150.1.4.4, 239.1.1.1), 00:00:07/00:02:52, flags: LJT Incoming interface: Vlan79, RPF nbr 155.1.79.7, Mbgp Outgoing interface list: Loopback0, Forward/Sparse, 00:00:07/00:02:52(155.1.45.4, 239.1.1.1), 00:00:07/00:02:52, flags: LJT Incoming interface: Vlan79, RPF nbr 155.1.79.7, Mbgp Outgoing interface list: Loopback0, Forward/Sparse, 00:00:07/00:02:52(155.1.67.6, 239.1.1.1), 00:01:44/00:01:15, flags: LJT Incoming interface: Vlan79, RPF nbr 155.1.79.7 Outgoing interface list: Loopback0, Forward/Sparse, 00:01:44/00:02:12
  • Ine Multicast

    1. 1. INE Multicast Alp ISIK 13.11.2011
    2. 2. Topology
    3. 3. PIM Dense Mode• Flooding için 1 – SPT shortest path tree oluşturulur. 2- Reverse path forwarding kullanılarak multicast paketleri SPT boyunca flood edilir.• PIM, RPF kontrolunu unicast routing table uzerinden yapar.• Downstream router’da herhangi bir kullanıcı yada router multicast paketini istemez ise PIM prune mesajı upstreame gonderilir.• PIM Dense mode’da periodic prune ve flood mekanizması var.
    4. 4. • PIM DM konuşturmak istediğimiz router’da oncelikle• ip multicast routing // açılır.• İnterface duzeyinde // “ip pim dense-mode” konfigure edilir.• Subscriber tarafında // “ip pim dense-mode” ve ip igmp join-group 224.10.10.10 konfigure edilir.
    5. 5. • Show ip pim neigh• Show ip pim int• Show ip mroute---------------Rack1R4#show ip mroute(*, 224.10.10.10), 00:01:35/stopped, RP 0.0.0.0, flags: D Incoming interface: Null, RPF nbr 0.0.0.0 Outgoing interface list: Serial2/1, Forward/Dense, 00:01:35/00:00:00 Ethernet0/1, Forward/Dense, 00:01:35/00:00:00(155.1.146.6, 224.10.10.10), 00:01:35/00:02:06, flags: T Incoming interface: Ethernet0/1, RPF nbr 155.1.146.6 Outgoing interface list: Serial2/1, Forward/Dense, 00:01:35/00:00:00(*, 224.0.1.40), 00:09:26/00:02:24, RP 0.0.0.0, flags: DCL Incoming interface: Null, RPF nbr 0.0.0.0 Outgoing interface list: Serial2/1, Forward/Dense, 00:07:40/00:00:00 Ethernet0/1, Forward/Dense, 00:09:26/00:00:00-----------------------• RPF neighbor 0.0.0.0 means it’s connected to the source
    6. 6. 8.2 RPF• Config altında // “ip multicast rpf ?” komutları ile rpf timerlarla oynanabilir.• ****İnterface altında no ip mroute-cache• ****Debug ip mpacket• RPF hatası gorulen durumlarda (S,G) için incoming interface goremiyorsak. Static mroute yazabiliriz.ip mroute 0.0.0.0 0.0.0.0 155.1.0.4-----------------------------Rack1R5#show ip mroute(*, 224.10.10.10), 00:06:26/stopped, RP 0.0.0.0, flags: D Incoming interface: Null, RPF nbr 0.0.0.0 Outgoing interface list: Ethernet0/0, Forward/Dense, 00:06:26/00:00:00 Serial2/0, Forward/Dense, 00:06:26/00:00:00(155.1.146.6, 224.10.10.10), 00:00:05/00:02:54, flags: T Incoming interface: Serial2/0, RPF nbr 155.1.0.4, Mroute Outgoing interface list: Ethernet0/0, Forward/Dense, 00:00:05/00:00:00(*, 224.0.1.40), 01:17:42/00:02:44, RP 0.0.0.0, flags: DCL Incoming interface: Null, RPF nbr 0.0.0.0 Outgoing interface list: Ethernet0/0, Forward/Dense, 01:16:17/00:00:00 Serial2/0, Forward/Dense, 00:19:18/00:00:00
    7. 7. 8.3 PIM Sparse mode• PIM SM konuşturmak istediğimiz router’da oncelikle• ip multicast routing // açılır.• Receiver ve source’ların bildiği bir randevu point “RP” belirlenir.• Receiver oncelikle ilgilendigi group için RP’ye multicast distribution tree oluşturur. Source belirdiğinde PIM register mesajları en kısa unicast yol ile RP’ye gonderilir. Bu yolda PIM SM açık olmalıdır.• Registration bittiğinde RP source’a doğru SPT oluşturur (*,G) ile. Receiverlar (*,G)li trafigi aldıklarında sourca dogru (S,G)li SPT oluştururlar. Buna spt switchover denilir, receiving router RP’ye multicast trafigin iki noktadan gelmemesi için prune mesajı gonderir. SPT switchovera threshold koyabiliriz. //ip pim spt-threshold 128• RP configurasyonu PIM SM domainindeki her routerda yapılmalı. Global configte//ip pim rp-address 150.1.5.5
    8. 8. PIM Sparse-Dense Mode• Hybrid combination of sparse nad dense mode.• Configure edildiği interface’de both spase and dense multicast group.• RP’si olan grouplar sparse; olmayan grouplar dense ile gonderilir.• Sadece sparse olarak calısması için “no ip dm- fallback”.
    9. 9. RP for specific groupsip pim rp-address 150.1.5.5 <access-list>
    10. 10. 8.5 PIM Assert• Eger aynı multicast route iki farklı yerden ogreniliyorsa, ilk AD, metric sonra buyuk ip’li olan yol tercih edilir.
    11. 11. 8.6 PIM Accept RP• As a security feature in order to routers only accept (*,G) from a specific RP.ip pim accept-rp 150.1.5.5 ALLOWED_GROUPSip access-list standard ALLOWED_GROUPS permit 224.110.110.110 permit 224.10.10.10
    12. 12. PIM DR Election• DR multiple-access segmentte multicast source registration’dan sorumludur.• İnterface altında // ip pim dr-priority 100
    13. 13. PIM Accept register• Tek bir source’a izin verilmesinde kullanılır.• Konfigurasyon RP’ de yapılır.• Filtreleme için RP ve DR ayrı olmalıdır.Rack1R5(config)#ip pim accept-register ? list Access list route-map Route-map
    14. 14. Multicast tunneling• Tunelde pim enable edilmeli,---------------------------interface Tunnel0 ip unnumbered Loopback0 ip pim sparse-dense-mode tunnel source Loopback0 tunnel destination 150.1.1.1--------------------------• Tunnel içinde igp mümkünse konuşulmamalı, konuşulması gerektiği durumda loop olmamasına dikkat edilmeli (metric ayarlanır.)• Static mroute ile multicast trafiği tunele gönderilir.
    15. 15. 8.10 PIM NBMA mode• Broadcast queue’sunda gonderilir.• Full mesh olmadığı durumda kullanılır.• PIM-SM’de calısır. Sparse-dense mode’ta tavsiye edilmez.• Interface altında // ip pim nbma-mode• Spoke-to-spoke multicast trafiğinin gönderilmesini sağlarız.
    16. 16. 8.11 Auto RP M source• İki consept içerir candidate RP (cRP) ve Mapping R6 E0/0.146 sm-dm Pim Agent (MA), bir ya da daha çok router cRP olabilir. cRP E1/0 paketi 224.0.1.39 ile gonderir, MA bu adresi R4 dinleyerek cRP bilgilerine sahip olur. Birden fazla MA varsa yuksek IP’li kazanır. MA auto-RP bilgisini S2/1 224.0.1.40 a atar, butun dinleyiciler, auto-RP’yi Pim sm-dm öğrenmiş olur. 224.0.1.39• Global config’te // ip pim send-rp-announce lo0 scope 10 (cRP için) S2/1 ip pim send-rp-discovery lo0 scope 10 (MA için) cRP R5 burada scope TTL ‘i belirler.• Auto-RP için 4 yol mevcut. E0/0 1- pim sparse-dense mode // RP’si olmayan butun Pim sm-dm gruplar için dense mode çalışır 2- pim sparse-mode (static RP for 224.0.1.39-40) 224.0.1.40 vl58 3- pim sparse-dense mode with no ip dm-fallback (sadece 224.0.1.39 ve 40 için dense-mode çalışır.) E0/1 SW2 SW4 E0/1 4- pimsparse-mode + autorp listener (loopback’lerde MA sparse-dense-mode [cRP ve MA için Lo0 kullandık]). Pim sm-dm vl10 receiver
    17. 17. 8.12 Auto-rp multiple candidate RP• Primary-backup olarak calıstırabiliriz. //highest IP will be selected.• Aynı grup için yedeklilik saglayabiliriz. //access-listt’e wildcard maskin longest matchine dayalı olarak.• Belli bir grubu exclude edebiliriz.• ip pim send-rp-announce lo0 scope 10 group- list SW2_GROUPS• Show ip pim rp mapping // ile check edilir.
    18. 18. 8.13 auto-rp – filtering candidate RPsip pim rp-announce-filter rp-list RP_LIST group- list GROUP_LIST // rp-list ile RP’leri group-list ile groupları filtreleriz.debug ip pim auto-rp
    19. 19. 8.14 auto-rp listener• Auto-RP listener, auto-rp kullanılırken 224.0.1.39 ve 224.0.1.40’ın automatik dinlenilmesini sağlar.• Global configte //ip pim autorp listener
    20. 20. 8.15 Auto-RP and RP/MA Placement M source• Hub & Spoke da hub ve spoke u RP yapmak için. R6 R4• Spokelar arasında tunnel kurduk.-------------- R1 rpinterface Tunnel1 tunnel1 ip unnumbered Loopback0 ip pim sparse-mode R3 tunnel source Loopback0 receiver R5 tunnel destination 150.1.3.3----------------R3 tarafına static mroute koyduk ki autorp discovery’leri R1den alabilsin ma SW2ip mroute 150.1.1.1 255.255.255.255 SW4 tunnel1 ma receiver
    21. 21. 8.16 Filtering Auto RP Messages• AutoRP mesajlarını filtrelemek için scope ile TTL ayarlanabilir ya da //ip multicast boundry configure edilebilir.• ip pim send-rp-discovery lo0 scope 2
    22. 22. 8.17 multicast boundry• Multicast boundry ile multicast trafige (control plane and data plane)sınır koyabiliriz.• Unicast pim register mesajları etkilenmez.• Interface altında //ip multicast boundary <acl (PERMITTED_GROUPS) > filter-autorp
    23. 23. 8.18 PIM Bootstrap Router• It’s the stadards-based protocol, autorp ile aynı işi yaparlar.• Rp candidate’te priority’de düşük değerler tercih edilir.• Autorp-MA ile BSR router aynı gorevi gorur.• Bsr candidate’te priority si yuksek olan tercih edilir. ip pim bsr-candidate Loopback0 0 //hash mask length ip pim rp-candidate Loopback0• NOT : BSR mesajlarının ulaşması için RPF check sağlanmalıdır.• Debug ip pim bsr
    24. 24. 8.19 BSR – Multiple RP Candidates• SW2, SW4 RP candidate; R5 is BSR-------------------• Aynı grup için yüksek ip li router secilir.• RP’lerden biri düşerse BSR bootstrap mesajlarına dayalı olarak automatik failoverı gercekleştirir. sh ip pim rp-hash 239.1.1.1
    25. 25. 8.20 Filtering BSR Messages• Not to learn any RP information via BSR• İnterface level //ip pim bsr-border
    26. 26. 8.21 stub multicast routing & IGMP Helper e0/0 FR S2/0 S2/0.1 R5İp igmp join –group R3 155.1.0.5 239.1.1.7 • Dusuk kapasiteli cihazda ya da bandwith’teki cihazda PIM-DM flooding ya da PIM-SM RP announcement’tan etkilenmemesi için “ip igmp helper- address” konfigurasyonu yapılır. Boylece cihaz bütün igmp mesajlarını receivera forward eder ve grupları oluşturmaz. • R3 int e0/0 ip igmp helper-address 155.1.0.5 ip pim dense-mode int s2/0.1 ip pim dense-mode • R5 access-list 33 deny 155.1.0.3 access-list 33 permit any int s2/0 ip pim sparse-mode ip pim neighbor-filter 33
    27. 27. IGMP Filtering• İnterface altında // ip igmp access-group <IGMP_FILTER> //ip igmp limit 10
    28. 28. IGMP Timers• İnterface altında//ip igmp querry-interval 20//ip igmp querry-max-response-time 4//ip igmp immediate-leave group-list IMMEDIATE_LEAVE//ip igmp querrier-timeout 60
    29. 29. 8.24 Multicast Helper Map• R1 ip forward-protocol UDP 5000 inte0/0 ip multicast helper-map broadcast 239.1.1.100 <access-list> // access-list ile port 5000 ve dns’i yakala• R3 ip forward-protocol UDP 5000 ip multicast multipath // eşit rpf’lerde multicast trafiği paylaştırır. // access-list ile port 5000 ve dns’i yakala int e0/0 ip directed-broadcast ip broadcast-address 155.1.37.255 int s2/0.1 ip multicast helper-map 239.1.1.100 155.1.37.255 <acl for port 5000-dns>• R5 R6 E0/0 ip mroute 155.1.146.0 255.255.255.0 155.1.0.1 R1 DR• SW1 SW1 int e3/1 e3/1 ip igmp join-group 239.1.1.100 E0/0 R3 FR R5 hub
    30. 30. 8.25 Multicast Rate limiting• İnterface altında // ip multicast rate-limit out group-list <access-list> 128 ip multicast rate-limit out 1024
    31. 31. 8.26 Bidirectional PIM• Global configte //İp pim bidir-enable//ip pim rp-candidate lo0 group-list <access-list> bidir
    32. 32. PIM SSM Source Specific Multicast• IGMPv3 ile yalnızca SPT oluşturur. RP yok. (shared tree yok)Global configte//ip pim ssm default|range <acl>İnterface altında //ip igmp ver 3İnterface altında //ip igmp join 232.6.6.6 source 150.1.10.10
    33. 33. 8.28 DVMRP Interoperability• Tunelling DVMRPint tunn 0 ip unnumbered lo0 İp pim dense-mode // komsuluk kurulmasada mcast feedin MBONEda akmasını saglartunnel source lo0 tunnel destination <IP in Mbone> Tunnel mode dvmrp-----------------------ip dvmrp interoperability(config-if)#ip dvmrp metric 1 list 40 eigrp 100
    34. 34. 8.29 Multicast BGP Extention• In general PIM-SM is used, her bir domainin kendi RP si olmalı, bsr ve auto-rp bilgisinin domainler arası gecişi engellenmeli. “pim bsr border” komutu kullanılabilir.• R3 router bgp 100 address-family ipv4 multicast neighbor 155.1.0.5 activate redistribute ospf 1 neighbor 150.1.7.7 activate neighbor 150.1.7.7 next-hop-self int s2/0.1 ip pim sparse-mode
    35. 35. • R4 route-map PREPEND set as-path prepend 200 200 200 router bgp 200 address-family ipv4 multicast neighbor 155.1.146.6 activate redistribute eigrp 100 neighbor 155.1.146.6 route-map PREPEND out neighbor 150.1.5.5 activate int e0/1 ip pim sparse-mod ip pim bsr-border
    36. 36. • R5 router bgp 200 address-family ipv4 multicast neighbor 155.1.0.3 activate redistribute eigrp 100 neighbor IBGP route-reflector-client neighbor 150.1.4.4 peer-group IBGP neighbor 150.1.8.8 peer-group IBGP neighbor 150.1.10.10 peer-group IBGP neighbor IBGP next-hop-self int s2/0 ip pim sparse-mode ip pim bsr-border
    37. 37. • R6 route-map PREPEND set as-path prepend 100 100 100 router bgp 100 address-family ipv4 multicast neighbor 155.1.146.4 activate redistribute ospf 1 neighbor 155.1.146.4 route-map PREPEND out neighbor 150.1.7.7 activate neighbor 150.1.7.7 next-hop-self int e0/0.146 ip pim sparse-mode
    38. 38. • SW1 router bgp 100 address-family ipv4 multicast neighbor IBGP route-reflector-client neighbor 150.1.3.3 peer-group IBGP neighbor 150.1.6.6 peer-group IBGP neighbor 150.1.9.9 peer-group IBGP• SW2 router bgp 200 address-family ipv4 multicast neighbor 150.1.5.5 activate• SW3 router bgp 100 address-family ipv4 multicast neighbor 150.1.7.7 activate• SW4 router bgp 200 address-family ipv4 multicast neighbor 150.1.5.5 activate
    39. 39. MSDP Msdp peerMsdp peer
    40. 40. 8.30 MSDP multicast source discovery protocol• Interdomain multicastta her bir domainin kendi RP si vardır, farklı domaindeki sourse-receiverların birbiri ile gorusmesi için RP’ler bilgi değişimi yaparlar.• SW2 ve R5 AS200’un RP’leri, SW1 AS100’un RP’si• At R5 ip msdp peer 150.1.7.7 connect-source lo0 remote-as 100• At SW 2 ip msdp peer 150.1.7.7 connect-source lo0 remote-as 100• At SW1 ip msdp peer 150.1.5.5 connect-source lo0 remote-as 200 ip msdp peer 150.1.8.8 connect-source lo0 remote-as 200• At SW4 ip pim bsr-candidate lo0 31 // iki grup için iki RPDebug ip msdp de
    41. 41. 8.31 Anycast RP• Her iki RP yi aynı IP ile gosterip yedeklilik sağlar.• RP için yeni bir lo100 yarattık.• PIM join’ler en yakın RP den gelir, Unicast routing table’a gore.• At R5 ip msdp peer 150.1.8.8 connect-source Loopback0 ip msdp originator-id Loopback0 ip pim rp-candidate lo100 no ip pim rp-candidate lo0 interface Loopback100 ip address 150.1.100.100 255.255.255.255 ip pim sparse-mode router erigrp 100 network 150.1.100.100 0.0.0.0
    42. 42. • At SW2 interface Loopback100 ip address 150.1.100.100 255.255.255.255 ip pim sparse-mode router erigrp 100 network 150.1.100.100 0.0.0.0 no ip pim rp-candidate lo0 ip pim rp-candidate Loopback100 ip msdp peer 150.1.5.5 connect-source Loopback0 ip msdp originator-id Loopback0-------------Check etmek için//show ip msdp sa-cache
    43. 43. IGMP Snooping• Global configte //İp igmp snooping vlan 146 immediate-leave• Check etmek için //show ip igmp snooping mrouter vlan 146show ip igmp groups
    44. 44. Multicast VLAN Registrationmvrmvr vlan 146mvr group 146mvr group 239.1.1.100mvr mode dynamicint ether 0/1 mvr type sourceint type ether 0/5 mvr type receiver//show mvr//show mvr interface//show mvr members//show ip igmp groups
    45. 45. IGMP Profilesip igmp profile 1 permit range 232.0.0.0 232.255.255.255 range 239.0.0.0 239.255.255.255int e0/4 ip igmp filter 1• It filters igmp messages according to profile.
    46. 46. kısaltmalar• OIL : outgoing interface list.• Multicast spt switchover : (*,G) to (S,G)

    ×