gÉant ip and geant plus network convergence · 2013-11-19 · gÉant ip and geant plus network...
Post on 23-Apr-2020
1 Views
Preview:
TRANSCRIPT
connect • communicate • collaborate
GÉANT IP and GEANT Plus Network
Convergence
Mian Usman, DANTE
13th Feb – TERENA Network Architect Workshop
Prague
connect • communicate • collaborate
2
Network Convergence
Pre-Procurement Architecture
Post-Procurement/Deployment Architecture
Convergence Motivation & Goals
Convergence Advantages & Challenges
Post Convergence Architecture
connect • communicate • collaborate
3
Pre-Procurement Architecture
Three main services on three different platforms
GÉANT IP – Juniper T-Series
GÉANT+ - Alcatel MCC
GÉANT Lambda – Alcatel LM 1626
connect • communicate • collaborate
4
Pre-Procurement Topology
connect • communicate • collaborate
5
Post-Procurement Architecture
Three services on three different platforms
GÉANT IP – Juniper T-Series and MX
GÉANT+ - Juniper MX
GÉANT Lambda – Infinera DTNx
SwitchingIP/MPLS
DWDM
Fibre Leased Circuits
IP
FR ES IT AT CZ SK SI
IE CHUK BE NL DK DE
HR HU
LV LT BG
EEGR PL PT
RO
LU RU
CY RS MT
MKTR IL ME
Fully Featured PoPs IP/Switching Only NREN PoPs
Lease
d
Circuits
connect • communicate • collaborate
6
Originally two separate networks
GÉANT IP network
connect • communicate • collaborate
7
Originally two separate networks
GÉANTPlus network
CZ
DKUK
HUCH
GR2
PL
IT
DE
GÉANT Plus Topology8/11/2012 AK
AT
NL
20 GE
30 GE
40 GE
10 GE
FR
ES
IE
Rt1.lon.uk
Rt1.mad.es
Rt1.fra.de
Rt1.vie.at Rt1.bud.hu
Rt1.poz.pl
Mx1.dub.ie
Rt1.ams.nl
100 ISIS cost
Only GÉANTPlus
MX are shown.
connect • communicate • collaborate
8
Convergence Motivation
Enable NRENs to connect at 100GE for GEANT IP access
Provide multiple services on a single interface as VLANs
Utilise the 100GE trunks between Juniper MXes for IP traffic
Avoid upgrading GEANT IP backbone
connect • communicate • collaborate
9
Convergence Goals
Merging of the existing GÉANT IP (T series) and GÉANTPlus (MX)
platforms
All the devices exist in a common IGP (IS-IS)
All the devices are in same Autonomous System
All services available everywhere
connect • communicate • collaborate
10
Convergence Challenges/Principles
Initially keep the GÉANTPlus and GÉANT IP traffic on dedicated trunks
Start using the 100GE trunks for production GÉANT IP and GÉANTPlus
traffic as soon as possible
Keep both backbone networks operational during the convergence
process
Minimize or preferably eliminate any site outages
Converge both IPv4/IPv6 and avoid partitioning either network or
blackholing any traffic
Avoid buying any extra hardware for Juniper T-series for convergence
purposes
connect • communicate • collaborate
11
Post Convergence Architecture
DWDM
Fibre Leased Circuits
IP & Switching
FR ES IT AT CZ SK SI
IE CHUK BE NL DK DE
HR HU
LV LT BG
EEGR PL PT
RO
LU RU
CY RS MT
MKTR IL ME
Fully Featured PoPs IP/Switching Only NREN PoPs
Lease
d
Circuits
connect • communicate • collaborate
12
Post Convergence Topology
connect • communicate • collaborate
13
Convergence Advantages
Easier to maintain and manage the network
Same monitoring and provisioning tools
Easier approach to migrate or upgrade NREN IP connection on MX
Can support both IP and GEANT+ connection on either platform
No upgrade of GEANT IP backbone required, no need to buy expensive
T-Series hardware
connect • communicate • collaborate
14
Convergence Status
Majority of the connections migrated from T-Series to MX in all PoPs
Nine out of 15 T-Series switched off, three M series switched off
Four PoPs AT, CH, DE and NL running both boxes
connect • communicate • collaborate
15
Working draft
POP with secondary access point (e.g. Milan)
1 MX deployed and backup via transport to adjacent POP
POP on fiber cloud without SAP
1 MX deployed and backup via transport to adjacent POP
POP off fiber cloud
2 MX deployed for primary and backup connections
Large POPs with international connectivity
1 MX and 1 T-series
connect • communicate • collaborate
16
Questions?
Questions?
top related