1 / 16

Routing within GEANT

Routing within GEANT. EUMEDCONNECT APM meeting Paris 19th of March 2002. 1. Introduction to GEANT GEANT’s peerings Access to GEANT Internal routing Policy GEANT external routing policy Questions ?. Agenda. 2.

jed
Download Presentation

Routing within GEANT

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Routing within GEANT EUMEDCONNECT APM meeting Paris 19th of March 2002 1

  2. Introduction to GEANT GEANT’s peerings Access to GEANT Internal routing Policy GEANT external routing policy Questions ? Agenda 2

  3. GÉANT is a 10 Gbps Pan-European Network, it supports the development activities of the European National Research & Education Networks (NRENs) GÉANT has been launched in December 2001 and is the successor of TEN-155. Introduction to GEANT 3

  4. Estonia Latvia Lithuania Slovak Rep. Romania Bulgaria 4

  5. GEANT is a IP transit domain where NRENs are peering with M-BGPv4 Ripe assigned to GEANT the Autonomous System* number AS20965 and the address space 62.40.96.0/19 www.ripe.net We are using half of this address space for the European addressing => 62.40.96.0/20 * An Autonomous System (AS) is a set of routers that are under a single technical administration. To other ASs, an AS appears to have a single coherent interior routing plan and presents a consistent picture of what destinations are reachable. Introduction to GEANT 5

  6. PoP PoP PoP PoP PoP Introduction to GEANT DFN JANET M-BGPv4 AS786 AS680 GEANT AS 20965 Surfnet AS1103 AS378 Primary and Backup access IUCC Rediris AS766 Garr AS137 • Currently 19 PoPs across Europe • 2 New PoPs under construction: Israel and Croatia 6

  7. GEANT’s peerings • 27 NRENs peering • 12 peerings at STM16 POS capacity • 10 peerings <= to STM1 capacity 7

  8. GEANT’s Research Peerings CAnet Esnet STM-4 Abilene GTREN www.dante.net/nep/gtren.html DFN STM-16 GÉANT AS20965 JANET DE UK NREN2 NREN4 ... ... GTREN stands for Global Terabit Research and Education Network Initiative of DANTE and UCAID to establish an intercontinental network connecting the various regional networks. 8 8

  9. The type of access is various We have mainly POS access type with Cisco-HDLC framing, two NRENs are peering with ATM and 1 with giga-ethernet. Currently the access capacity varies from E3 to STM16. NRENs can be dual-homed with a main and backup access Note: the backup access doesn’t carry any traffic ACCESS to GEANT 9

  10. GEANT is using OSPF as “IGP” We’ve configured OSPF metrics on the core backbone links to engineer the traffic inside our AS and influence OSPF best path for BGP next-hop. We’ve a full mesh of I-BGP connection which permits us to receive and announce BGP routes from one peer to another peer with BGP attributes. We are not redistributing BGP routes into OSPF or the other way around. GEANT Internal routing Policy 10

  11. Eenet Litnet Janet Nordunet NY4-1 Latnet IUCC Posnan STM64 circuits 9 se pl uk STM16 circuits 40 Heanet 630 STM4 circuits 40 ie Surfnet STM1 circuits 35 7 nl 640 Belnet 5 40 10 DFN be Restena 640 NY4-2 Cesnet 40 lu Infonet Renater 640 10 de 10 cz fr 159 40 40 Rediris 20 Sanet es 7 sk FCCN 7 35 20 Hungarnet 7 hu RoEduNet it ch 40 INFN 170 10 Arnes at si Switch&Cern 160 160 gr Carnet Aconet Grnet Cynet Unicom-b 11 GÉANT TE: OSPF Metric

  12. We are using M-BGPv4 and its attributes to build incoming and outgoing routing policy. GEANT external routing policy 12

  13. Classical BGP incoming routing policy We accept NRENs prefixes based on a prefix list This prefix list is automatically built on Ripe macro database where NRNs are registered. We set the attribute local-pref at “150” for the incoming routes on the main access and 100 for the backup access and tag NRENS routes with the community value 20965:155 We filter out martians routes GEANT external routing policy 13

  14. Classical outgoing policy We announce GEANT routes based on community values. We set MED value to “20” for backup access and keep at “0” for the main access. GEANT external routing policy 14

  15. GEANT community set-up NRENs can tag their routes with specific communities to announce or not announce some networks to some peerings or ask GEANT to do some AS prepending. 20965:PPAA Where PP is the value for the peer and AA is the value for the Action http://www.dante.net/nep/NEP-2001-137-GTREN-ROUTING-ISSUES-v4.doc 15

  16. Questions ? • www.dante.net/nep • www.dante.net/nep/GEANT-MULTICAST • www.dante.net/operations 16

More Related