Some history: Lightpaths and OPNs - network users and uses

1. Lightpaths: why, what (and how!)Bram Peeters, SURFnet Network ServicesSNE College, 21st of March, Utrecht

2. # u s e r s SB ≈ 40 Gb/s SC ≈ 100 Gb/s A SA ≈ 20 Gb/s B C ADSL GigE BW requirements Some history: Lightpaths and OPNs -network users and uses Required capacity per user category: • A: End users: web, e-mail • B: Institutions: applications, VPNs, shared service center • C: Researchers: computing, data grids, virtual-presence This slide courtesy of Cees de Laat

3. The Basic Light Path A definition (one of many) • “reliable, point-to-point connection, with guaranteed bandwidth and fixed delay” • SURFnet standard: GE port at the client side • L2 connection => building stone OPN, direct connection projects • OPN = Optical Private Network GE GE

4. Make the network ready -SURFnet6: DWDM on dark fiber Muenster Network Fiber

5. End-to-End Light Path A network for lightpaths GLORIAD AMS2 AMS1 Nortel HDXc European Light Paths Nortel transport box Nortel transport box Intercontinental Light Paths .. SURFnet6 Common Photonic Layer Nortel transport box Nortel transport box Customer equipment Customer equipment End user SURFnet infrastructure End user Non-SURFnet

6. Lightpaths: implementation • Standard LAN interface (GE, 10GE) • Uses the qualities of the transport network to achieve • Performance: capacity, availability • Security: OSI L1 • Flexibility: locations, topologies • Simplicity: ‘transparent’, predictable/fixed latency • Costs of usage GE GE

7. packet IP Ethernet HDLC 10 G LAN PHY 10 G WAN PHY 1 G PHY optical GFP (G.7041) SDH (G.707) Optical Fibre Hybrid Optical/Packet Networks – from a GE to wavelengths Courtesy of John Graham

8. A B C D E Time Division Multiplexing A 8 7 6 5 4 3 2 1 B MUX / DEMUX MUX / DEMUX C Z Z D E A  Z:1 E  Z:1 STM-64: 10 Gbit/s – 64 x 150 Mbit/s STM-16: 2.5 Gbit/s – 16 x 150 Mbits/s Courtesy of John Graham

9. … … … … X X X Basic Node Architecture – A bit on next-gen SDH / SONET 10G GE X 10G GE GE 10G GE 10G crossconnect Client side X network side - SDH

10. Model 2: “path protected” • GE kinterface • 1 client port • 1+1 protected! • Fiber breuk => switch to protecting path < 60 ms • Good, clear guarantees OME OME GE GE working protecting Making Lightpaths reliable Model 1: Single • GE interface • 1 client port • Fiber cut or failing equipment => service gone • Poor guarantees! OME OME GE GE

11. Model 4: let’s have it even more reliable • 2 client ports • redundant, protected • Node is final single point of failure • 0 to 1G each path • Failure always covered (for 1G) • THESE ARE TWO PROTECTED LPs!!! OME OME GE working 1 GE protecting 2 GE GE protecting 1 working 2 More models Model 3: redundant – not protected • 2 client ports • redundant, not protected • Node is single point of failure • 0 to 1G each path • Failure always impacts client experience OME OME GE working GE GE GE working

12. A network with lightpaths? • Designing a network to work with lightpaths demands some attention • Simple solution: direct point to point between two ‘boxes’ --> not really a network… • Complex solution: real L2 network??? • Routed solution, but a single admin domain

13. Example Optical Private Network: Artez Logical Physical

14. Firewall to Internet - uplink 1 Gb/s SURFnet LP 1Gb SURFnet LP 1Gb Managed Dark fiber Managed Dark fiber Artez OPN Nieuwe situatie internet Arnhem Oude Kraan Zwolle Stadsmuur Zwolle Sophia Arnhem Onderlangs Enschede AKI

15. Layer 3 architecture with Layer 2 applications

16. Application specific OPNs University dept High Energy Physics Network CERN Healthcare OPN Research Network University University Institute Optical Private Network eVLBI Network Telescope site

17. Large Hadron Collider:high-level network architecture

18. “USI” – User to Service Interface (web GUI, API) Control plane Admin The (near!) future: Dynamic, user schedulable LPs public DRAC private User Nortel OME 6500 Nortel OME 6500 Nortel OME 6500 CPE Nortel OME 6500 1 GE Customer equipment CPE 1 GE Customer equipment resource SURFnet infrastructure Non-SURFnet

19. End-user GUI snapshot

20. Group manager • Add users to group • Manage user rights • Get accounting of service usage • Request more ports! Service manager • Add network resources to DRAC • Create groups • Assign port resources and policy to group • Allocate to group manager Network operators • Know about the service • Don’t want to care about provisioning alarms • Manage network incidents • Don’t provision on DRAC resource! A manageable serviceFinding the right place for management functions Service users • Get registered with group(s) • Log on • Schedule services within group • Use service • Verify service USER COMMUNITY SURFNET

21. Klaar!

22. Verder: 09:30 uur: Ontvangst met koffie 10:00 uur: Inleiding SURFnet en GigaPort – Roy van Schaik 10:20 uur: Fotonica in SURFnet6 - Wouter Huisman 10:50 uur: Bio-break 11:05 uur: Lightpaths, hoe, wat en waarom - Bram Peeters 11:35 uur: SURFnet6 Reporting and monitoring - Hans Trompert 12:00 uur: Lunch 12:30 uur: Einde