routing within geant

EUMEDCONNECT GEANT routing policy -- Agnès Pouélé ([email protected])1

Routing within GEANT

EUMEDCONNECT APM meeting

Paris 19th of March 2002

EUMEDCONNECT GEANT routing policy -- Agnès Pouélé ([email protected])

Agenda

• Introduction to GEANT

• GEANT’s peerings

• Access to GEANT

• Internal routing Policy

• GEANT external routing policy

• Questions ?

2


Introduction to GEANT

• 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.

3

EUMEDCONNECT GEANT routing policy -- Agnès Pouélé ([email protected]) 4

Estonia

Latvia

Lithuania

Slovak Rep.

Romania

Bulgaria



• 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.

5


PoP

PoPPoP

PoP

PoP


GEANTAS 20965

DFN

Rediris

Garr

JANET

IUCC

Surfnet

M-BGPv4

Primary and Backup access

AS680

AS1103

AS786

AS378

AS137

AS766

•Currently 19 PoPs across Europe•2 New PoPs under construction: Israel and Croatia

6


GEANT’s peeringsNREN ACCESS MCAST Type

Austria POS STM-4 NO Mcast

Slovenia POS STM-4* NATIVE

Belgium POS STM-16 NATIVE

Croatia ATM E3 NATIVE

Czech Rep. POS STM-16 NATIVE

Cyprus E3 TBA

Germany POS STM-16 NATIVE

ESTONIA POS STM-1 NATIVE

Portugal POS STM-4 NATIVE

Greece POS STM-16* NATIVE

Ireland POS STM-1 NATIVE

Hungary POS STM-16 NATIVE

Italy POS STM-16 NATIVE

Israel T3 NATIVE

United Kingdom POS STM-16 NATIVE

Latvia E3 NATIVE

Lithuania T3NATIVE

Norway, Sweden, Finland,Island

POS STM-16 NATIVE

Poland POS STM-16 NATIVE

Spain POS STM-16 NATIVE

France POS STM-16 NATIVE

Luxembourg POS STM-1 NATIVE

Roumania E3 NATIVE

Slovak Rep. POS STM-1 NATIVE

Netherlands POS STM-16 NATIVE

Switzerland POS STM-16 NATIVE/TBA

Bulgaria E3 TBA

7

•27 NRENs peering •12 peerings at STM16 POS capacity•10 peerings <= to STM1 capacity


GEANT’s Research Peerings

GÉANTAS20965

CAnet

DFN

NREN2JANET

NREN4

GTRENSTM-16

UKDE

Esnet

... ...

Abilene

8

STM-4

www.dante.net/nep/gtren.html

GTREN stands for Global Terabit Research and Education NetworkInitiative of DANTE and UCAID to establish an intercontinentalnetwork connecting the various regional networks.

8


ACCESS to GEANT

• 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

traffic9


GEANT Internal routing Policy

• 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.

10


uk

fr

at

ch

cz

pl

hu

sk

gr

ie

10

10

9

7 640

20

40

20

40

10

35

40

160

159

77

7

40

35

630

10si

160

170

be

nl

40

40

40

lu

640

640

5

it

es

de

se

IUCCJanet NY4-1 Nordunet

Eenet

Latnet

Litnet

Posnan

DFNNY4-2

InfonetCesnet

Sanet

HungarnetRoEduNet

Arnes

Grnet

Switch&Cern

Renater

Rediris

FCCN

Surfnet

Belnet

Restena

Heanet

Carnet

INFN

Aconet

Unicom-bCynet

11

STM64 circuitsSTM16 circuitsSTM4 circuitsSTM1 circuits

GÉANT TE: OSPF Metric


GEANT external routing policy

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

12


• 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


13



• 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.

14


GEANT community set-upEU Peerings

Community

BT Nacsis (AS6683)

20965:6683

NRN routes

20965:0155

Infonet (AS3300)

20965:3300

Abilene (AS11537)

20965:11537US Peerings

Via GTREN

Esnet (AS 293)

21320:293

Abilene (AS 11537)

21320:11537

Canarie (AS6509)

21320:6509

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 Actionhttp://www.dante.net/nep/NEP-2001-137-GTREN-ROUTING-ISSUES-v4.doc

15


Questions ?

•www.dante.net/nep•www.dante.net/nep/GEANT-MULTICAST•www.dante.net/operations

16

routing within geant

Documents