DEVELOPMENTS IN GÉANT2: END-TO-END … · DEVELOPMENTS IN GÉANT2: END-TO-END SERVICES ... Alcatel...

Connect. Communicate. Collaborate

The Italian Research& Education Network

DEVELOPMENTS IN GÉANT2:END-TO-END SERVICESMauro Campanella - GARR([email protected])

6th Annual Global LambdaGrid Workshop,11-13 September 2006, Tokyo, Japan


The Italian Researchand Education Network 2

Agenda

• GÉANT2 briefing and developments• End to end services and the hybrid

infrastructure• Monitoring• GÉANT2 activity JRA3 (BoD) introduction



GÉANT2• Interconnects 34 National Research & Education

Networks (NRENs) of the extended European ResearchArea (ERA)

• Interconnects more than 3500 Research & Education(R&E) Institutions

• Serves millions of end-users and e-Science Projects (e.g.GRIDs) under Accepted Usage Policy (AUP) rules

• The model: A 3-tier Federal Architecture:– Campus Network (LAN/MAN)– NREN (MAN/WAN)– Pan-European Interconnection: GÉANT2 (GN2 in FP6):

now a Hybrid Optical Backbone (+ Cross BorderFibers)



The 7 Generations ofEuropean R&E Networks

0.01 0.1 1 10 100 1000 10000 100000

GEANT 2 (2006-??)

GEANT (2001-05)

TEN-155 (1998-2001)

TEN-34 (1997-98)

EuropaNET 2 (1996-97)

EuropaNET (1993-96)

IXI (1991-93)

Link Speed Mbps

UnderlyingTechnology

Services

Datagram&

IPv4

IPv4&

ATM

IP4,6 only

Hybrid

PDHcircuits

ATMoverSDH

Waves

Fibre



GÉANT1 Services

• Best effort (unicast) IPv4 and IPv6 transit– Between European NRENs– To/from R&E backbones in other world regions

• Multicast IPv4• Premium IP (destination-aware QoS, based on Expedited

Forwarding PHB of DiffServ)• Less-than-Best-Effort IPv4 (scavenger service of I2)• Multicast IPv6 (almost there)• L2VPN (Point-to-Point EoMPLS)• Distributed (routed) testbed



GÉANT(1) ⇒ GÉANT2 Connect. Communicate. CollaborateSome New Facts & Figures…

• 25 POPs (+4) serve >30 NRENs• 11600 km of fibre + 140 ILA sites• 50+ x (own) 10G lambdas• 9 x (leased) 10G lambda• 8 x 2.5G (leased) “lambda” +

some lower speed links• Juniper T640, M160, M40 routers• NREN accesses at up to 10Gbps

(+ backup) + P2P• 4 x 10G to North America• POP in NY• connections to other R&E

networks as before : Abilene,ESnet, CA*net4, SINET, TENET,RedCLARA, EUMEDCONNECT,TEIN2 (coming)



The GÉANT2 fibre topology

Core fibretopology

Figures incirclesrepresentsthe number offibers

Valid atJune 2006



Provision of end-to-end (e2e)Services to e-Science• Up to now: Packet Switched IP (Layer 3) & MPLS Managed

Bandwidth Services – VPNs• From now on the hybrid NREN - GÉANT2 service model

also enables:– Layer 2 Switched e2e circuits (e.g.1 GigE) involving

GÉANT2 facilities ( + local circuits provided by NRENsand Campuses)

– 10 Gig Optical Private Networks (OPNs) configured forlarge e-Science projects using GÉANT2 DWDM &NREN - Campus lightpaths

• Pricing of additional e2e lightpaths: Incremental costing ofGÉANT2 Dark Fibre, charged to projects via hostingNRENs, Global extensions (if possible) under similar terms



GÉANT2 (GN2) is not just anetwork, but also …

Networking Activities (NAs)(Human networks)

• Management• Dissemination and outreach• User support (NRENs)

SERVICE ACTIVITIES (SAs)(focus on services, not

infrastructure)

• Network Service Provisioning

• Network Operation and Support

JOINT RESEARCH ACTIVITIES (JRAs)

Focus on academic, technological research

… an Integrated Infrastructure Initiative - I3 of EC, with allNRENs as partners and DANTE as coordinator



JRA1 (perfSONAR) – Advanced Network Monitoring

• Versatile web services based framework for theexchange of network monitoring information

• MP and MA services• Started at L3, now adding lower layers

Joint Research Activitiesand Service

JRA2 – Security

• Of the network• Developing & promoting best practices for CSIRTs• Develop toolkit• Looking at using netflow data

JRA3 – Bandwidth Allocation & Reservation

• Develop a connection-oriented, E2E, non-contended,guaranteed capacity P2P service (Ethernet, SDH)

• Multi-domain (hence multi-technology)• With advance reservation• More on this later…

JRA4 – Technology & Service Testing

• Build distributed testbed for use by NRENs and otherJRAs

• Undertake technology testing programme• Also mopped up technical aspects surrounding use of

so-called Cross-Border Fibre (CBF)

JRA5 – Mobility & AAI

• Develop and promote roaming access infrastructure -eduGAIN

• Develop all-in-one AAI for use by new services (suchas monitoring, PIP provisioning, BoD, etc)

SA3 – End-to-end QoS

• Make “quality” more ubiquitous• Develop PIP provisioning system (AMPS) and

(encourage) roll-out across many NREN domains• Operate enhanced monitoring infrastructure as

“production” service• Develop and operate PERT• create a Common Network Information System



GÉANT2 vs GÉANT (1)Services Enhancements• Improved e2e L3 performance monitoring (JRA1 & SA3)

via perfSONAR architecture• more automated QoS Premium IP provisioning (SA3) via

AMPS• new L1 and L2 Point-to-Point services

– cost-effective support for high-capacity [“lightpath”]services

– up to 10G (for now)– emphasis placed on support for Ethernet framing– try to provide translational Point- toPoint service

support• e.g. native GbE to GFP VC-4-7v over SDH

– explore various protection/restoration modes



Agenda

• GEANT2 status and developments• End to end services and the hybrid

infrastructure• Monitoring• JRA3 introduction



GÉANT2:Hybrid infrastructure

GÉANT2POP A

IP Router DWDM andSDH Switch

n × lambdato neighbouring

POP

GÉANT2POP B

To NREN

n × 10 Gbps10 Gbps

n × lambdato neighbouring

POP

Primary IPPeering

Backup IPPeering

To NREN




Connect. Communicate. CollaborateTransport Equipment

Alcatel 1626 LM (Light Manager)

Alcatel 1678 MCC (Metro & Core Connect)



Services over GÉANT2 Connect. Communicate. Collaborate

GÉANT2

More resilient IP service

POP A

POP B

POP C

POP D

Features:• Ethernet• Ethernet VLAN• SDH

Primary IP access

Backup IP access




GÉANT2

Point-to-point GE (GE access)

POP A

POP B

POP C

POP D

Features:• uses GFP/VCAT • GE port per instance• more dynamic• sub 1G possible

Essentially animplementation ofITU-T G.8011.1

EPL serviceType 1




GÉANT2

Point-to-point GE (10GE access)

POP A

POP B

POP C

POP D

Features:• uses GFP/VCAT• 10GE port (supporting multiple instances)

• use 802.1Q VLAN tags as IDs• sub (or >) 1G possible

VLAN X

VLAN Y

Essentially animplementation ofITU-T G.8011.2EVPL service

Type 1




GÉANT2

Point-to-point GE (10G SDH access)

POP A

POP B

POP C

POP D

Features:• uses GFP/VCAT • 10G SDH port• GFP done in NREN• sub 1G possible

VCG X

VCG Y




Managed wavelength service

POP A

POP B

POP C

POP D

Features:• 10G only• SONET/SDH or 10GE LAN PHY• static• 10GE is “full-rate”

GÉANT2



CERN T0

IN2P3

PICCNAF

RAL

GRIDKa

Nordugrid

TRIUMF ASCC

SARA

BNL FNAL

DKUK

NL

DE

ITES

FR

GEANT2

LCG TIER0 – TIER1 Optical Private Network - OPN,scenario based on work by Roberto Sabatino DANTE

CW



Agenda





Problem space

Point A

PointB

Domain A

Domain B

Domain C

Goal: (near) real-time monitoring (link status) of constituent DomainLinks(and links between domains) and whole end-to-end Link A-B.The following applies to the GÉANT2+ service and the cross border fibres.

E2ELink A-B



Divide & conquer(JRA4 E2Emon info model) Connect. Communicate. Collaborate

JRA4 view of world:note WDM systems,& static lambdas



Approach

Point A

PointB

Domain A

Domain B

Domain C

E2ELink A-B

perfSONARMP or MA

perfSONARMP or MA

E2Emoncorrelator

perfSONARMeasurement Point (MP)

or Measurement Archive (MA)

DomainLink and(partial) ID_Link info

“Weathermap”view for users

E2ECUoperators



The physical topology

GARR GÉANT2

Milano

XX

ALCATELInterdomain Link

CNAFCERN

CNAF - CERNexample monitoring

Bologna

The logical topology built for the e2e monitoring system abstracts theinternal topology of each domain an produces a simpler topology.



GARR GEANT2end point end point

demarcation points

CERNCNAF

Interdomain Link

Domain Link

CNAF - CERNLOGICAL TOPOLOGY

Logical topology as seen from the monitoring system

GARR must supply the local edge-to-edge path status in its monitoring domain tothe centralised E2E monitoring system (E2EMS). The E2EMS aggregates theinformations from each domain to provide the e2e path status.The status of a link can, for now assume the operational states of : Up, Degraded,Down, Unknown, and the administrative values of : NormalOperation,Maintenance,TroubleShooting, UnderRepair, Unknown.

Milano



GEANT2

GINS (the GARR network monitoring system) checks the status of the logicalcircuits in the GARR domain and provides the result to the GARR MP.The central e2e measurement system queries each domain and provides the globale2e status.This shows the domain independency, the possibility to easily aggregate theinformation and its scalability.

GARR

end point

IP Link

X

X

IL MONITORING

GARR monitoring domain

CNAF GINS e2eMonitor

XML Data

GARR MP E2E MSMPLS LSP IP/L2 Link

CNAF - CERNGARR monitoring flow



VISUALIZZAZIONE

http://cnmdev.lrz-muenchen.de/e2e/lhc/G2_E2E_index.html (beta)

CNAF - CERNE2E MS user interface



VISUALIZZAZIONE

https://www.noc.garr.it/GINS/e2e/ms_e2e_view.php (restricted access)(Slides from Marco Marletta , Giovanni Cesaroni GARR)

CNAF - CERNGARR GINS user interface



Measurement SystemFuture work - wish list

• Define & implement “degraded” link status• Add PM statistics• Add scheduled maintenance indication• Add more detail to data model

– Break down DomainLink into constituent parts?(e.g. OCh trails)

– use more info from equipment



Agenda





The JRA3 Activity of GN2• JRA3 is investigating the provision of ‘Bandwidth on Demand’ services

to the NREN community• The goal implies an environment that is:

– Multi-domain– Using multiple transmission technologies

• SDH, GFP over SDH, L2 MPLS VPN, Ethernet• Requirements for:

– end-to-end delivery of a non-contended capacity– a standardized interface for service requests at end-points– service level indication to end-users– advance reservation (scheduled)– modular and technology independent implementation



L2 MPLS VPN

JRA3 architectureKey elements:- Inter-Domain manager

(IDM)- Domain manager (DM)- Resource modeling (aka

Abstract representsation)- Path finder- Technology proxies- Standardized interfacesEach domain participating inthe BoD service provisioningneeds to operate an IDM andhonor the IDM-DM and IDM-IDM interfaces.The local DM can be anytechnology, just a proxy isneeded towards the IDM



JRA3Distributed approach

User interface

Inter-Domain Manager

Domain Manager

Client equipment IP domain

NMS

GE domain

L2 MPLS VPN

SDH domain

Native Ethernet GFP over SDH

GMPLS signalling

Client equipment

User interface


Domain Manager

User interface


Domain Manager

(1)

(2)

(4)

(5)

(6)

(7)(3)

Inter-domainpath-finding

(8)(9)(10)



JRA3Inter Domain Manager

Client equipment

IP domain

NMS

GE domain

L2 MPLS VPN

SDH domain

Native Ethernet GFP over SDH

GMPLS signalling

Technology Proxy

Domain Manager

Inter -Domain Manager

User access module

Request handling logic

DM pathfinding

AAI

Resource modelling

Policy module

Inter-domain pathfinder

User interface

Technology Proxy

Domain Manager


User access module


DM pathfinding

AAI

Resource modelling

Policy module

Inter-domain pathfinder

User interface

Client equipment

JRA

3 B

oD s

yste

mD

ata

pla n

e

Technology Proxy

Domain Manager

Inter -Domain Manager

User access module


DM pathfinding

AAI

Resource modelling

Policy module

Inter -domain pathfinder

User interface



JRA3Why an Inter-Domain Manager

• The effort to provision end-to-end Bandwidth on Demandservices in the European scenario requires specificdevelopments in inter-domain collaboration

• Splitting intra-domain management functionalities frominter-domain ones in separate modules, allows multi-domain R&D to proceed autonomously and focus on thisless standardized area

• At the same time, it allows to leverage existing inter-domain managers through wrappers/proxies and interfaces,exploiting a modular approach

• This effort can provide solid experience for brokeringservices other than Bandwidth on Demand



JRA3Domain independence

• Collaborative and distributed effort through newly definedinterfaces which extend the NNI standards

• No centralised management• Better resilience• A common naming and addressing schema for a large

amount of devices• An abstract network representation to ensure faithful

service description• Possibility to hide domain internals• Clear separation of control and data plane also at the

physical level when needed



JRA3:IDM multi-domain issues

The IDM faces a number of requirements and correspondingchallenges related to its multi-domain scope:

• domain independence for resource usage policies and technologicalchoices

• a service and network abstraction schema to describe implementationover very different networks, with different policies

– a schema to allow a clear specification of the service– a network abstraction which allows inter-domain information

exchange independently of the underlying technologies• stitching of multi technology domains• multi-domain path finding procedure• advance reservation• monitoring• Authentication and Authorization



JRA3:Current status• Framework and Architecture defined• IDM functional specification released• IDM phase 0 (simplified in some modules) implementation

and testing done• Working on Pathfinding module, IDM phase 1 and abstract

representation

Key results/issues to be described and discussed by VictorReijs this afternoon in the control plane working groupmeeting



Thank you !

DEVELOPMENTS IN GÉANT2: END-TO-END … · DEVELOPMENTS IN GÉANT2: END-TO-END SERVICES ... Alcatel...

Documents

Transcript of DEVELOPMENTS IN GÉANT2: END-TO-END … · DEVELOPMENTS IN GÉANT2: END-TO-END SERVICES ... Alcatel...