GÉANT IP and GEANT Plus Network Convergence Mian Usman, DANTE 13 th Feb – TERENA Network Architect Workshop Prague connect • communicate • collaborate
Network Convergence Pre-Procurement Architecture Post-Procurement/Deployment Architecture Convergence Motivation & Goals Convergence Advantages & Challenges Post Convergence Architecture connect • communicate • collaborate 2
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 3
Pre-Procurement Topology connect • communicate • collaborate 4
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 Fully Featured PoPs IP/Switching Only NREN PoPs GR PL EE PT IE UK BE NL DK DE CH TR IL MK ME LV LT BG RO FR ES IT AT CZ SK SI CY RS MT HR HU LU RU Leased Circuits IP Switching IP/MPLS DWDM Fibre Leased Circuits connect • communicate • collaborate 5
Originally two separate networks GÉANT IP network connect • communicate • collaborate 6
Originally two separate networks GÉANTPlus network GÉANT Plus Topology 8/11/2012 AK Only GÉANTPlus 40 GE 30 GE MX are shown. Rt1.ams.nl 20 GE IE Mx1.dub.ie 10 GE DK 100 ISIS cost NL UK Rt1.lon.uk PL Rt1.poz.pl DE CZ Rt1.fra.de FR IT AT CH HU GR2 Rt1.vie.at Rt1.bud.hu ES connect • communicate • collaborate Rt1.mad.es 7
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 8
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 9
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 10
Post Convergence Architecture Fully Featured PoPs IP/Switching Only NREN PoPs GR PL EE PT IE UK BE NL DK DE CH TR IL MK ME FR ES IT AT LV LT BG RO CZ SK SI CY RS MT HR HU LU RU d e s s a t e i u L IP & Switching c r i C DWDM Fibre Leased Circuits connect • communicate • collaborate 11
Post Convergence Topology connect • communicate • collaborate 12
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 13
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 14
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 15
Questions? Questions? connect • communicate • collaborate 16
Recommend
More recommend