CNaaS Extending the NREN through Campusnetwork as a Service David Heed Project Manager / Product coordinator

Quick facts about Sunet 3 optical fiber routes to all regions Connecting customers at ~25 locations 100 Gbps 8000+ km optical fibre

Challenges of today NRENs need to diverse itself for more than connectivity to stay relevant, more service driven and supporting the customers. Our goal with Campusnetwork as a Service (CNaaS) “Share staff and expertise for campus network and security operations by standardizing network architecture, tools and processes.”

Competence shift - Retaining staff & no one gets fired! Hardware and connections more software defined Network engineer → programmer Central templates control, but local staff is needed for fixes and user support. Aging staff, Retention,,Schooling, Few with exposure to complex networking,Not filling the ranks

Architecture scalability and automation In order to achieve scalability we need to be able to repeat processes and orchestrate changes through automation. This is DevOps for the networks. Built for fault tolerance and expansion Redundant design on all levels except access ports Repeatable Best practise leaf/spine Common NOC

Collaborative activities - Automation and Monitoring Fully automate provisioning of network switches at Campuses Sunet CNaaS NMS automation + production at local site Uninett NAV used for integration with OC and tickets GN4-3 WP6 making the CNaaS service model available for other NRENs

Summary and more information By extending the NREN core network to the institutions on both equipment monitoring and change management Sunet is supporting new services including Security operations New services Extending NREN physically https://wiki.sunet.se/display/CNaaS