Download presentation
Presentation is loading. Please wait.
PublishMyrtle Hunter Modified over 9 years ago
2
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) Inter-domain Multicast in European Research Networking TEN-155 Operational Experience and Deployment on GÉANT NANOG24 Miami 12th February 2002 Agnes Pouélé, DANTE Network Engineer Jan Novak, Cisco Systems Inc. Network Consulting Engineer 1
3
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) Agenda DANTE TEN-155 Operational Experience –Evolution of the TEN-155 multicast topology from 1998 to 2000 –Operational Experience GÉANT deployment –Overview of GÉANT Network –GÉANT’s Multicast design –GÉANT Multicast and Unicast Coverage –GÉANT Multicast Service and Monitoring Conclusion 2
4
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) DANTE, TEN-155, GÉANT DANTE DANTE is a not-for-profit company set up in 1993 by European National Research Network organizations. TEN-155 was an ATM based network built initially on OC3 links and then upgraded in 2000 GÉANT successors of TEN-155 launched in December 2001 10 Gbps Pan-European Network Is partially funded by the EC 3
5
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) Part I TEN-155 Operational Experience 4
6
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) Typical mess of DVMRP tunnels on Sun WSs with usual tunnel routing problems. 5 Starting point MBONE TUNNELED TOPOLOGY
7
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) 6 OSLO IETF transmitted over both native STM-1 ATM based network and DVMRP tunnelled infrastructure 1999: PIM-SM and DVMRP set-up PIM-SM domain
8
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) Multicast deployment in TEN-155 Based on this first set-up and successful operation, we concluded to enable multicast on all production routers in TEN-155. Multicast code stable, CPU usage ok, M-BGP ok PIM-SM “only” for production service PIM-SM to DVMRP border works, but not possible to operate routinely (NOC) From 1999 to 2000 each country was migrated from the DVMRP cloud to a interconnection with TEN-155 using PIM-SM/MBGP/MSDP 7
9
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) 2000: TEN-155 final topology NL United Kingdom France Italy Greece Belgium Spain CH FR UK SE IT DE Slovenia Czech Rep Germany AT Switzerland Portugal AS8933 OSPF + internal MBGP Poland Israel Netherlands Nordics e x t e r n a l B G P AT & T UUNET Luxembourg Hungary US ABILENE 8 tunnel unicast/mcast line dedicated mcast
10
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) TEN-155 Operational Experience Performance Impact Parameters to be considered for the exploitation of Multicast –CPU - parameters about 1600 forwarding (mroute) entries max 8 outgoing interfaces (average 2-3) max 20 Mbit/s of data forwarded by one router resulting in 5-10% of CPU increase (mainly PIM) 9
11
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) TEN-155 Operational Experience Performance Impact Parameters to be considered for the exploitation of Multicast –Memory about 3000 SA messages in the cache about 1600 forwarding entries (mroute) about 10 000 routes in the MBGP table These parameters didn’t represent a significant memory usage 10
12
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) Usage of MSDP – new component – new storms Default peer in redundant topology “Redundant” mesh-groups MSDP peers default peer Group A Group C Group B Impact of a MSDP storm on the CPU load 11
13
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) Usage of MSDP – early implementation problems Cisco IOS 12.0.6S and lower –ghost SA entries in the MSDP cache SA messages recreated by the incoming (S,G) joins FIXED –Origination of SA messages only when source registered to the originating RP –“ip msdp redistribute” command – without arguments re-originated all known SAs caused huge increase of the SA counts worldwide FIXED 12
14
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) TEN-155 MSDP monitoring MSDP usage monitoring number of RPs, average 90 (40 EU) number of groups number of pairs source, group (S,G) number of SA messages per minute Monitoring set-up WS - DANTE DE.TEN-155 router Software – adapted C++ MSDP implementation of Steve Rubin 13 MSDP peering
15
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) TEN-155 MSDP monitoring Number of RPs originators announced to TEN-155 with and without multicast US connectivity number of RPs 14
16
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) TEN-155 MBGP monitoring MBGP monitoring stability/updates number routes, max about 9000 (760 EU) number of ASNs, average 240 (80 EU) Monitoring set-up WS - DE PoP DE.TEN-155 router Software - Merit’s MRTD - modified SAFI definition for MBGP 15 MBGP peering
17
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) TEN-155 MBGP monitoring In blue, the number of routes originated from one AS In green, the number of updates originated by the same AS stability/updates 16
18
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) TEN-155 Multicast Monitoring tools http://www.dante.net/pubs/dip/40/40.html http://www.dante.net/pubs/dip/41/41.html http://www.dante.net/mbone/ http://sigma.dante.org.uk/stats/mrtg/msdp/data/ http://www.dante.net/mbone/mbgp The graph values from mbgp and msdp monitoring are historical values. 17
19
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) TEN-155 Operational Experience Conclusion The adoption of PIM-SM domain (without DVMRP) encouraged the NRENs to do the same. Unicast and multicast non congruent MSDP peer doesn’t need to be RP. Concept of two BGP tables and “multi-protocol” RPF check often still misunderstood. Inter-domain Multicast debugging –Almost impossible to fix problems in just one week TEN-155 work provided valuable inputs for GEANT multicast services and design 18
20
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) PART II NEXT GENERATION GÉANT DEPLOYMENT 19
21
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) 20 www.dante.net/nep/GEANT-MULTICAST/map.html
22
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) GÉANT Services GÉANT Standard IP Service –IP traffic from NREN to NREN and Research peerings. Multicast Service (rolling out now) Replacement of TEN-155 Managed Bandwidth Service –GÉANT Premium IP Service –Layer-2 VPNs (forthcoming) Upcoming Security and Dos attack detection, IPV6 21
23
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) GÉANT’s Customers and Other Peerings GÉANT Unicast Customers –27 countries in Europe GÉANT Multicast Customers –24 countries in Europe GÉANT Unicast and Multicast research and commercial peerings –Abilene, Canarie and ESnet via GTREN –Infonet, UUNET –KPNQwest, Global Crossing 22
24
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) GÉANT Multicast Customers 23 www.dante.net/nep/GEANT-MULTICAST/map.html
25
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) GÉANT Multicast Implementation Current design built on –The experience gained from TEN-155 –Guidelines from multicast experts –Juniper Laboratory tests –GÉANT Multicast services –Multicast transit domain NRENs to NRENs –Multicast transit domain NRENs to other PEERS –Beacon monitored backbone GÉANT Multicast routing policy at: – http://www.dante.net/nep/GEANT- MULTICAST/routing-policy.html 24
26
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) HostX Mangan ese Iridium HeliumGallium Sulfur HostY Xenon Network 10.2/16 –AS 102 Network 10.0/16 -AS 100 Network 10.1/16 -AS 101 HostZ Tin Network 10.3/16 –AS 103 Group 233.1.10.1 Source 10.1.10.2 Source 10.2.20.2 Group 233.2.20.1Group 233.3.30.1 Source 10.3.30.2 Group 233.0.1.1 Source 10.0.1.2 Group 233.0.3.1 Source 10.3.30.2 TEST-BED LAB 26/27th Nov 2001 M-BGP peering MSDP peering I-MBGP full mesh Junos 5.0R3.3 mesh group 25 I-MSDP full mesh
27
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) PIM SMv2 GÉANT domain GÉANT single PIM-SMv2 –Version 2, enabled on all interfaces. Three Rendez-vous Points with private anycast address. –backup for internal sources and receivers. –Private Anycast address (filtered out) –closest RP based on the OSPF cost All other interconnected administrative domain have to be PIM-SM v2 enabled with their dedicated RP. 26
28
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) PHYSICAL TOPOLOGY: RP uk fr at ch cz pl hu sk gr ie 10 9 7640 20 40 20 40 10 35 40 160 159 7 7 7 40 35 630 10 si 160 170 be nl 40 lu 640 5 it es de se IUCC Janet NY4-1 Nordunet Eenet Latnet Litnet Posnan DFN NY4-2 Infonet Multicast access Rendez-vous Point Cesnet Sanet Hungarnet RoEduNet Arnes Grnet Switch&Cern Renater Rediris FCCN Surfnet Belnet Restena Heanet Carnet INFN Aconet Unicom-bCynet STM64/OC192 STM16/OC48 STM4/OC12 STM1/OC3 27 PoP www.dante.net/nep/GEANT-MULTICAST/map.html
29
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) GÉANT Design: MBGP and MSDP MBGP Separate multicast routing table (inet.2) Currently congruent BGP and MBGP topology in Europe iMSDP MSDP is fully meshed between 19 PoPs Use of mesh group i-MSDP Peering with loopback addresses (Not the anycast address !!) eMSDP NREN GÉANT Access Router 28
30
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) MSDP peering Logical view iMSDP Mesh Group iMBGP Full Mesh uk se de1 cz hu at es fr Iucc JanetNy4-1 Renater Switch&Cern Rediris FCCN INFN Arnes RoEdunet Sanet Posnan Cesnet DFN NY4-2 Infonet GRnet Nordunet Latnet Litnet Eenet Carnet gr Cynet Unicom-b ch lu Restena be Belnet it si Hungarnet sk de2 pl ie Heanet pt Surfnet nl Aconet External MSDP peering NRN ----- GÉANT router 29 RP GTREN Abilene www.dante.net/nep/GEANT-MULTICAST/map.html
31
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) MSDP SA Filtering A list of filtered SA is defined at: –http://www.dante.net/nep/GEANT- MULTICAST/deployment-msdp.html We filter the recommended list. We authorise 239.194.0.0/16 from the IPV4 Organisation Local Scope through GÉANT. 30
32
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) GÉANT AS20965 CAnet Third party provider European Distributed Access Commodity Internet Access DFN NREN2 JANET NREN4 GTREN RESEARCH Peerings STM-16 UKDE Esnet... Abilene 31 STM-4 www.dante.net/nep/gtren.html GÉANT Multicast and Unicast Coverage
33
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) GÉANT Multicast Service Access to the service –Via the primary access to GÉANT –Via a GRE tunnel (currently nobody) –Support of PIM-SM v2 only Operational procedures (rolling out now) –Goal: fully supported service as Unicast. Troubleshooting –Extension of the trouble ticket systems to multicast incidents 32
34
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) GÉANT multicast monitoring Beacon –Tool initially developed by Kai Chen from NLANR dast.nlanr.net/projects/Beacon/ Relies on a number of Agents spread over the network which simultaneously send and receive multicast packets carrying a packet sequence number and a timestamp. Communicates with a central server which displays matrices of Agents via web pages. 33
35
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) GÉANT multicast monitoring Recommended by TF-NGN group –( www.dante.net/tf-ngn) To use from day 1 –monitoring of multicast inside and outside of GÉANT. Server code enhanced with historical functionality http://noc.man.poznan.pl/noc/index/strony ( Menu item “Applications”) romradz@man.poznan.pl romradz@man.poznan.pl Multicast Beacon Agent written in C http://www.cesnet.cz/tf-ngn/multicast/ 34
36
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) GÉANT multicast monitoring Beacon’s matrices –One for the internal sources of GÉANT Each GÉANT POP has a beacon agent installed –One for the external sources of GÉANT http://beaconserver.geant.net:19999/ –We have assigned two multicast groups from GLOP range [RFC2770] for each matrix Parameters monitored Loss Delay Jitter 35
37
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) Beacon internal/external matrix 36 www.dante.net/nep/GÉANT-MULTICAST/deployment-beacon.html
38
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) Other Monitoring Tools Per group monitoring from TEN-155 –Based on the IETF IP-MROUTE MIB –Shows traffic per multicast group per interface –Under installation on ws1.se.geant.net MSDP and MBGP monitoring tools –Not yet available 37
39
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) CONCLUSION Deployment status –beaconserver.geant.net:19999/ Conclusion –From TEN-155 to GÉANT Unicast and multicast moves to a congruent topologyacross Europe and towards research peerings. Links –www.dante.net/nep/GEANT-MULTICAST/ –www.dante.net/mbone/ –www.dante.net/tf-ngn/ 38
40
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) We would like to thank and acknowledge the help of the people who worked and are working with us on these projects, mainly from all EU and US research networks 39 THANKS
41
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) Questions ? 40
42
Agnès Pouélé (agnes.pouele@dante.org.uk), Jan Novak (janovak@cisco.com) SA Filter list 41
Similar presentations
© 2024 SlidePlayer.com. Inc.
All rights reserved.