2014 Engineering Roadmap. Derek Cobb/Richard Petrie IXScotland Meeting: 9 January 2014

Transcription

1 2014 Engineering Roadmap Derek Cobb/Richard Petrie IXScotland Meeting: 9 January 2014

2 Contents 2013 LINX review IXScotland 2014 Outsource NOC Route server New PoP policy Introducing Richard Petrie, our new CTO

3 London Juniper LAN 100Gb/s in the core North/south plane split 2013 Network Developments 100Gb/s access now available on JunOS 12.3 London Extreme LAN VPLS and Connexions POCs complete UK IX IXScotland launches IXManchester expansion approved US IX LINX NoVA launched and first Open IX accreditation

4 2013 Internal Developments IT platform refresh 2 new data centres, HP Generation 8 Blades, 3PAR SAN, remote backup Virtualised (VMWare) LINX Internal networks AS5459 rebuilt Secure VPN remote access Out of band site access replaced with added WiFi! Systems New stats system now under extended internal test OSS Inventory in service replaces old database Alarm and ticketing systems in final development BSS Migration to new IT platform to complete by end 2013

5 2013 Service Developments Fractional ports service launched on Juniper and Extreme Service availability metric launched Available on all LANs

6 q 493 members q 80 new applications in 2013 q 1222 connected member ports q 707 member-facing 10GigE ports q 2 member-facing 100GigE port q 2 Tb/sec of peak LAN traffic q Tb of connected capacity q 60 member countries 2013 LINX Exchange Facts

7 IXScotland Facts Launched 28 October 2013 Powered by Extreme Networks x460 technology Hosted by Pulsant South Gyle Current port speeds offered: 100Mb/s, 250Mb/s, 500Mb/s, 1Gb/s, 10Gb/s Route server, NTP time service Exchange stats, member port stats Free ports in 2014 (up to 10Gb/s) Currently 8 connected members Prospect list stands at 35 Peak traffic 25Mb/s

8 IXScotland 2014 Budget provision for 2 nd site and diverse fibre connections More information in new POP slides Ability to add x670 to provide 10Gb/s port capacity No plan for 100Gb/s deployment in 2014, but technology options available if demand arises Current roadmap assumes 2015 earliest deployment Connexions reseller services to be available in Q Dependent on Extreme XoS

9 Outsource NOC Partnership with Allegro as the NOC provider to establish a consistent 24x7 first line NOC Extended cover meets continued LINX growth and extended hours for NoVA Partnership allows LINX to set up NOC at lower cost than establishing in house and with right skill levels RFQ process over 3 stages: 1) RFQ document and formal response 2) Presentation 3) NOC visit NOC launch target is February

10 Route Servers Introduction Peering requires social interaction, and sometimes legal documents That doesn't scale very well at the high end And lots of members at IXPs are open to all peering requests So what have we got to address that? Multi-lateral peering (MLP)! Essentially a device (called a route server) to connect to Used by networks with open peering policies Connect to the route server and you have multi-lateral peering!

11 MLP and 'communities' Route Servers - Communities You don't have to advertise all of your routes Community policies allow large and smaller networks to use route servers There are 4 community policies Block announcement of a route to a certain peer Announcement of a route to a certain peer Block announcement of a route to all peers Announcement of a route to all peers

12 IXScotalnd route server rs1-pue.sco1.linx.net Sources of further advice? Route Server Resources Or raise a ticket support@linx.net Or speak to LINX staff Some useful slides? Nick Hilliard s route server presentation

13 New PoP policy detail (1) Six key elements: 1. Support from members 2. Business case must make sense 3. Colo partner must risk share 4. Diverse dark fibre back to LINX core 5. Must support dual LANs (in London) 6. Fair/favourable terms

14 New PoP policy detail (2) 1. There must be support from members for the idea of a new LINX PoP. 2. A business case must be established for any new PoP, showing that it makes sense over no greater than a three year period that any financial investment made by LINX can be fully recovered over that period. 3. Risk sharing with the colocation provider must be a prerequisite of any new PoP proposal, such that any risk associated with the business case in item #2 can be appropriately mitigated.

15 New PoP policy detail (3) 4. Any new PoP proposal shall incorporate diverse dark fibre links to at least two other LINX PoPs, and furthermore any linkage to other LINX PoPs should ideally be done at core sites (where this 'core' designation is applied and appropriate) 5. Where LINX operates dual LANs in a metro area (e.g. as in London at present), and new PoP must contain provision for connection to both LANs 6. Taking into account clause (2), the colocation provider must offer terms that include (as a minimum) an undertaking: to provide LINX with most favoured IXP customer status (i.e. must not offer better terms to any other IXP that they choose to host) that any charges that apply may be varied by mutual consent, but no new charges can be introduced for services already/customarily provided