1 / 45

A new national network

A new national network. Andrew Mackarel Andrea Tognola Dave Wilson. Agenda. Evolution of the network Procurement process The new hardware and layout Transition and timeline. Evolution of the network. 1994-1999 First IP network - star topology Single core router in UCD

aerona
Download Presentation

A new national network

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. A new national network Andrew Mackarel Andrea Tognola Dave Wilson

  2. Agenda • Evolution of the network • Procurement process • The new hardware and layout • Transition and timeline

  3. Evolution of the network

  4. 1994-1999 First IP network - star topology Single core router in UCD Typical speeds: 64k-2M, clients and peers Star topology DIT MCI Forbairt UCC UCD (then a second for BGP) HEA NCIR VCIL Ebone TCD

  5. 2000-2007 Bring the networkout of Dublin Avoid duplication & cost Add resilience Tendered for PoP sites Won by client sites Typical speeds clients up to ~10M, upstreams N*2M National Backbone External peers and upstreams Clients

  6. Multi-pop backbone • This model has scaled to 1Gbit/s • Overlaid on National Backbone Extension • Dark fibre network providing ethernet point-to-point • Bring networkto the client • Avoid duplication • Reduce cost • Increase flexibility • Add resilience • These goals now addressed by NBE!

  7. Scaling limit >1Gbit/s requires newhardware Software upgrades long and intensive Feature upgrades require new hardware… National Backbone External peers and upstreams Clients

  8. Collapsed backbone 2008 onward • New Best Current Practice:Concentrate, then duplicate • Concentrating reduces the hardware,and with it failure incidence andscaling cost • Duplicating providesresilience, and keepsnetwork consistent • Model now being followed by many NRENs

  9. Procurement

  10. Procurement • Chose procedure • Competitive dialogue, open, restricted • PIN notice followed by open procedure • PIN notice sought input on type of equipment and architecture, and set expectations • Proceeded to open RfT based in part onthe input received in response to PIN • RfT issued December 2006

  11. Procurement • Responses arrived February 2007 • Thorough evaluation includingon-site testing of candidate equipment • Single vendor solution chosen • Biggest single contract in HEAnet • Extensive environmental requirements checked with colo sites • Contract signed August 2007 • Delivery October 2007 • Implementation ongoing as we speak

  12. To implementation • Detailed transition plan being developed • HEAnet • Lan Communications & Cisco • Being customised with each client's input • Starting with HEAnet internal infrastructure • Identification of project to clients now • Contact taking place to agree individual transition plans over the coming weeks

  13. The hardwareand new architecture

  14. Hardware Scalablity • Chosen equipment: Cisco CRS-1 • Scalablity • up to 100Gbit/s interfaces • 1.5+ Terabits per second total • Full support for current andfuture services • New operating system platform: IOS-XR

  15. Features • Support for critical new features • IPv6 multicast, 4byte ASN, … • Excellent high availability • Software is modular • Possibility of hitless upgrades! • Top of the field for future growth • 10Gbit/s connections a matter of course • Scale to 100Gbit/s peer, multi-10Gbit/s client

  16. Network Architecture • Two routers, both performingcore and access functions • One in Citywest, one in Kilcarbery Park • Where possible, client gets connectivity via NBE to both routers • Primary/backup connections • Resilience a function of the underlying NBE • Ethernet only, burst up to 10Gbit/sper interface

  17. Bandwidth scaling Today Effective limit of old equipment 10Gig connections to INEX, GÉANT andGeneral Internet now being commissioned

  18. The transitionand timelines

  19. Transition • Careful consultation with each client • Minimise disturbance to connections • Where possible, bring up new connections before deleting old • BGP policy will assist in this (thank you!) • Preferentially route traffic over new network for a test period • Can revert by shutting down new links • Transition plan customised for each client's needs

  20. Transition

  21. Transition • NBE resilience rollout in parallel • Clients not directly connected to NBE should still peer with both routers • BGP preferred, to protect from fibre cutor reboot of one or other router • All clients now transitioning to Ethernet • Extra flexibility of design & speed overATM and serial links • Connect directly with NBE • Use VLANs to provide second peering session

  22. Transition • Testing during November 2007 • 4Gbit/s interconnect with current network • Slow start with handpicked connections • HEAnet internal infrastructure first(MNS - ftp.heanet.ie, videoconf, streaming) • INEX and backup GÉANT connections • One client of each technical category,by agreement, full support from all partners • Plan: production traffic by Christmas • Transition in earnest starts in January 2008 • Majority March 2008, decommission June

  23. Impact • Most transitions should be hitless or near-hitless • Will discuss each connection in detail • If HEAnet manages your CPE • We will contact you for scheduling • We will manage the transition • If you manage your own CPE • We will contact you for schedulingand planning of the changes

  24. Thank you! Questions?

  25. Bonus slides

  26. Timelines • NOW - Installation • Late Nov - Acceptance tests • End Nov - HEAnet services • Early Dec - First clients and peers • Mid Dec - Acceptance and freeze for Christmas period • Jan-Feb - Next 10 clients • Feb-Mar - Remaining clients and completion

  27. Tasks for transition • Inform customer of new network design • Identify local liaison at site • Determine Local requirements, software changes, patching • Agree time schedule for parallel running/test • Implement switchover to new connection • Confirm new connection confirms to requirements • Terminate old connection

  28. New IP Backbone Rollout phase Nov 2007 – June 2008

  29. Current topology “Rednet” ar1-cwt ar2-cwt ar1-dcu ar1-tcd cr1-cwt cr1-kp cr1-gal cr1-lim cr1-cork

  30. 1 1 1) Interconnection with the core (Nov 07) CR1-CWT CR2-CWT CWT-PE1 NTL ESBT KP-PE1 CR1-KP CR2-KP

  31. 2 2 2 1 1 2) Interconnection with Bluenet (Nov) CR1-CWT CR2-CWT CWT-PE1 IP link via Bluenet NTL ESBT KP-PE1 CR1-KP CR2-KP

  32. 2 2 3 1 1 3)Rehome ESBT dark fibre (Dec) CR1-CWT CR2-CWT CWT-PE1 X NTL ESBT ESBT KP-PE1 CR1-KP CR2-KP

  33. 4 3 2 4 2 1 1 4)Peer with Route Reflectors (Jan 08) RR1 CR1-CWT CR2-CWT CWT-PE1 X NTL ESBT ESBT KP-PE1 RR2 CR1-KP CR2-KP

  34. 4 4 4)Peer with Route Reflectors (w/o Bluenet) RR1 CR1-CWT CR2-CWT RR2 CR1-KP CR2-KP

  35. 5 5 5) Dealing with ATM and commodity (Feb 08) RR1 X CR1-CWT CR2-CWT AR3-CWT AR2-CWT RR2 X CR1-KP AR1-KP CR2-KP

  36. Transition phase 2008 AR3-CWT CR1-CWT CR2-CWT CWT-PE1 INEX GEANT New IPTr Clients via Bluenet ESBT GBLX KP-PE1 CR1-KP CR2-KP AR1-KP

  37. New IP Backbone Client’s access setup overview

  38. Client with telco connection to a central PoP-> NUI Maynooth X Port-Channel1 AR1-DCU G6/2.28 G1/0/1 Eircom DWDM BLUENET cpe2-nuim North nuim-sw1 kp-sw1 dcu-sw1 CR2-KP IP link & BGP IP link & BGP BLUENET CWT-PE1 cwt-sw1 CR2-CWT Port-Channel1 NEW! X BT HEAN103306 HEAN105011 X G7/5 nuim2 South nuim-sw2 AR1-CWT AT 200711 Slide 39

  39. Client access via Bluenet and cancelled Telco-> DIT Aungier St (planned) X G6/2.22 AR1-TCD IP link & BGP G1/0/1 DCC fiber A1/0.28 G0/2 G1/0/1 G2/0/10 cpe1-dit aungier-sw1 tcd-sw1 BLUENET KP-PE1 CR2-KP ? IP link & BGP BLUENET CWT-PE1 cwt-sw1 CR2-CWT X X Eircom AVC502353 A3/1.8 AR1-CWT atmsw1-cwt AT 200711 Slide 40

  40. Client with leased line to Citywest, singlehomed-> EPA, Wexford ? IP link & BGP F0/0 cpe1-epa BLUENET KP-PE1 kp-sw1 CR2-KP ? IP link & BGP BLUENET CWT-PE1 cwt-sw1 CR2-CWT X static X HEAN101018 10Mb/s BLI F9/2 AR1-CWT AT 200711 Slide 41

  41. BGP client with full resilience. Will use Bluenet-> UL (not resilient though) IP link & BGP BLUENET KP-PE1 CR2-KP IP link & BGP trunk BLUENET CWT-PE1 X lim-sw1 ul.lim.client LIM-PE1 CR2-CWT G0/2 REDNET CR1-LIM AR1-LIM AT 200711 Slide 42

  42. IoT: Limerick IT IP link & BGP AR1-GAL BLUENET KP-PE1 X CR2-KP IP link & BGP trunk BLUENET CWT-PE1 X lit-sw1 lim-sw1 cpe1-lit LIM-PE1 CR2-CWT G0/2 AR1-LIM AT 200711 Slide 43

  43. IoT: Tipperary Institute X HEAN0111 2Mb/s S3/2 AR1-GAL converted leased line BLUENET KP-PE1 gal-sw1 TippInst Clonmel CR2-KP IP link & BGP BLUENET CWT-PE1 converted leased line cwt-sw1 TippInst Thurles CR2-CWT IP link & BGP X HEAN0109 STM-1 A3/1.44 AR1-CWT AT 200711 Slide 44

  44. IP link & BGP BLUENET KP-PE1 CR2-KP IP link & BGP trunk BLUENET CWT-PE1 lim-sw1 LIM-PE1 CR2-CWT IoT: Limerick IT AR1-GAL X X lit-sw1 cpe1-lit G0/2 AR1-LIM AT 200711 Slide 45

More Related