RMDCN Network Architecture

1. RMDCN Network Architecture Vienna, RMDCN Steering Group 4-6 June 2008 Remy Giraud ECMWF RMDCN Network Architecture

2. Standard Service Elements • Bandwidth for each User Site; • User Site-specific service and traffic management through COS mechanisms • Service Levels depending on the Service Type selected by User Sites; • Secured VPN provided through Multi Protocol Label Switching (“MPLS”) technology; • Access leased line including its provisioning and monitoring; • Regular reporting on the VPN performance (Quality of Service indicators); • Network Management and Fault management for all Service elements, all provided on a 724365 basis. • Router Management (PE and CE) – dedicated VPN Owner RMDCN Network Architecture

3. RMDCN Service Elements • Connection to the Network • In general, doubling of Frame Relay access speed – IP BANDWIDTH • Speed Access Line - nearest available • Direct (Leased Line, Ethernet) CE – PE or Frame Relay PVC between CE and PE • Gold Service Type • Class of Service • Backup • Enhanced Resilience: NAS ISDN Backup • ISDN Speed limitation (OBS support) • Mission Critical Setup RMDCN Network Architecture

4. MPLS – Strengths and Weaknesses RMDCN Network Architecture

5. Access Methods - dedicated Access • Technologies • Native IP – Direct access (LL) • Frame Relay access, Ethernet access type • IP Bandwidth • A unique service on each type of dedicated access • A flexible parameter for the site sizing • From 64 kbps up to 50 Mbps LL Bandwidth IP Bandwidth Flexible parameter up to the LL bandwidth RMDCN Network Architecture

6. What define an access to the MPLS Cloud ? • Access Line • IP Bandwidth • Standards OBS Service Type • GOLD – Data Classes Of Service Standard COS profiles • 60% - D1, 30% - D2, 10% - D3 • 66% - D1, 33% - D2 • 100% - D2 • SILVER – Unique COS • 100% of the IP bandwidth • Approved option for the traffic allocation: • D1: 75% - ECMWF dissemination and GTS • D2: 20% - Aladin/RETIM/LACE/coupling File Transmission • D3: 5% - Other (Default) RMDCN Network Architecture

7. COS Management • Data classes D1, D2 and D3 • CB-WFQ for all classes (relative weight = relative priority in case of congestion) • No layer 3 shaping: Each data class can use up to the IP bandwidth • No more Frame Relay facilities: Traffic always limited to the IP bandwidth CB-WFQ: Class Based – Weighted Fair Queuing RMDCN Network Architecture

8. APPLICATION CLASSIFICATION RULES • From the CE to the Backbone. • OBS has configured the Network’s application classification rules that define how the CE router manages the application traffic classification (ie prioritization) for the outgoing traffic. Application traffic is assigned to the corresponding COS class (D1, D2 or D3). Unclassified application traffic will by default be assigned to the “by default” COS class. • From the Network to the CE. • In this direction, the Network takes precedence over the sender User Site (using COS) and automatically classifies the received data in the same COS. If the COS used is not configured on the access, then the received traffic is classified as “unknown type of traffic” and put in the “by default” COS configured on the access. The per-COS traffic assignment rules correspond to how traffic flow is mapped to a COS, and is similar to specifying an access control list. If any incoming traffic is received that does not match any of the provided rules, this traffic is sent into the lower level class (might be D2 or D3). RMDCN Network Architecture

9. CONTINGENCY SOLUTIONS • Standard Connection • NAS BACKUP – SINGLE CPE • NAS BACKUP – DUAL CPE (Warm Standby) – Enhanced • ON-NET BACKUP – DUAL CPE • Mission Critical Connection • DUAL CONNECTION – SHADOW ACCESS – SINGLE CPE • DUAL CONNECTION – SHADOW ACCESS – DUAL CPE • Mission Critical RMDCN Network Architecture

10. NAS Back-up Resiliency Proxy Radius “Warm standby” router Customer site ISDN PSTN Authentication Equant NAS Customer VPN Equant IP VPN network Warm standby option dual CPE OBS Pop (PE) resiliency CE – LNS router • Hub site: 1 access supporting • Private Dial traffic • Traffic to the VPN ECMWF RMDCN Network Architecture

11. Dual Connection – Mission CriticalResiliency OBS IP VPN Network Customer Site Primary Access Equant Pop level of resiliency Secondary Access CE router Dual CPE CE router RMDCN Network Architecture

12. Traffic Partitioning • MPLS IPVPN: • No PVC – No CIR – No guaranteed throughput between source destination • Any-to-any connectivity • To limit the any-to-any exposure Access Control Lists can be defined on local routers RMDCN Network Architecture

13. Routing issues • Between CE router and NAS router: HSRP • Mission Critical Setup: 2 CE routers - HSRP • LAN Route redistribution • BGP • EIGRP • OSPF • RIP v1, RIP v2 • Static RMDCN Network Architecture

14. Background – The SRF2 Document • Service Request Form 2 • Used by OBS to • Collect the technical information for each RMDCN site • Internally build the CE routers configurations • ECMWF is the entry point • Complete the SRF2 documents on behalf of the RMDCN sites RMDCN Network Architecture

15. Background – The SRF2 Document • The pre-filled OBS SRF2 document • One pre-filled SRF2 by OBS per RMDCN IPVPN site • The focus is on the required technical details pages RMDCN Network Architecture

16. Service Metrics and Help Desk • SLA 99.9% (100% for Mission Critical sites)‏ • Now Site Availability (used to be PVC availability)‏ • Pro-active monitoring • 24 User Sites • Only English language • OBS Help Desk in New Delhi‏ • Re-active monitoring • 18 User Sites • Local Language RMDCN Network Architecture

17. RMDCN Network Architecture

18. RMDCN Network Architecture

19. Questions? RMDCN Network Architecture