Network TransformationHow to Get Started with Automation

Fredrik Lundberg, Sr. Director, Tail-f NFV Business UnitMarch 9, 2017

Broadband Growth vs. Revenue Growth

2010 2015 2020

Year over Year Broadband Growth

50%

Keys to SP TransformationSP Outcomes

Reduce TCO

Transform operations

Accelerate speed to market

Generate new revenue

Improve customer experience

Mitigate risk

Application-led, not infrastructure

Network as platform

Virtualize

Simplify

Automate

Program

Cisco

Bandwidth is growing; revenue is not

Web-scale breaks current cost & design models

Grow compelling services

Subscriber retention and relationship

SP Drivers

Executing on the new strategy will require hard work and cooperation from all

CEOHead of Strategy

Product Management

“Let’s implement a strategy based on speed, customer centricity and agility”

“Competitor X is doing this. Customer Y wants this. We need to have a new offer in 30 days”

Head of IT“Next release is in 4 months. Come back then, but most likely it will a 3-6 month project since the NW integration is very cumbersome”

Head of NW“Huh, Crazy ideas, but if it weren’t for IT’s rigid procedures I could create a script that should work”

Network Automation

Physical Networks Virtual Networks

• Automated Service Lifecycle ManagementFor example: Service Activation, Service Modifications and Deletions

• Enabling the BSS and OSS systems to programically use the network resources

• Make the Network Programmable replacing• Customized Integrations• Manual Work

• Super-important to make use of evolving SDN and NFV concepts

BSS

OSS

Characteristics of IT and Networking

Physical Networks Virtual Networks

BSS

OSS

IT driven with software peopleComputer science principles applyEvolved over decadesComplex (partly due to NW)Need very controlled change

“IT”

“NW”

CCIE drivenCLI!Bandwidth, throughputScripts, yes sometimesJava?Magic OK button – Don’t think so!

Promise of Network Automation

Speed & Agility

Generate New Revenue

Lower Operating Costs

Network Automation– NSO Scope

Well-defined API

Physical Networks Virtual Networks

OSS

Resource Facing Services (RFS)

NetworkServiceLifecycle

• Unlocks agility and flexibility at the Resource Facing Services layer (RFS)

• Enables DevOps at the network/RFS layer

• Network changes and new features can be rolled-out continuously during run-time, i.e. DevOps Network Service Orchestration System

BSS

Product/ Service Systems Lifecycle

Infrastructure

Cisco Orchestration ArchitectureHigh Level View

• Model-driven end-to-end service lifecycle and customer experience in focus

• Seamless integration with existing and future OSS/BSS environment

• Loosely-coupled and modular architecture leveraging open APIs and standard protocols

• Orchestration across multi-domain and multi-layer for centralized policy and services across entire network

RFS

DC & NFV ControllerMulti-layerWAN SDN

CFSOrder Managers

OSS

Metro and Access WAN Data CenterCPE

Configuration-basedProvisioning

Network Service Orchestrator (NSO)

Service Orchestrator System Overview

NSO

Service Manager PackageManager

ESC (VNFM)

VNF Lifecycle Manager

Multi-domain Networks

Device Abstraction

NED NEDNED VNF Service Monitoring

Device ManagerCDB

Network Engineer DevelopersIT/OSS/BSS Extensible Generic Platform

Minimum Programming

Model-drivenFAST-MAP Algorithm

Transaction FrameworkPackage Manager

DeviceModels

ServiceModels

The YANG Service Model container vpn { ! list l3vpn { ! description "Layer3 VPN"; !! key name; ! leaf name { ! type string; ! } !! leaf as-number { ! mandatory true; ! type uint32; ! } !! list endpoint { ! key "id"; ! leaf id{ ! type string; ! } !!

leaf ce-device { ! mandatory true; ! type leafref {} ! } !! leaf ce-interface { ! mandatory true; ! type string; ! } !! leaf ip-network { ! // the private IP network! mandatory true; ! type inet:ip-prefix; ! } ! leaf bandwidth { ! tailf:info "Bandwidth in bps"; ! mandatory true; ! type uint32; ! } !! }

Demo Example

NSO

Service Manager PackageManager

ESC (VNFM)

VNF Lifecycle Manager

Multi-domain Networks

Device Abstraction

NED NEDNED VNF Service Monitoring

Device ManagerCDB

Network Engineer DevelopersIT/OSS/BSS

container vpn { ! list l3vpn { ! description "Layer3 VPN"; !! key name; ! leaf name { ! type string; ! } !! leaf as-number { ! mandatory true; ! type uint32; ! } !! list endpoint { ! key "id"; ! leaf id{ ! type string; ! } !!

leaf ce-device { ! mandatory true; ! type leafref {} ! } !! leaf ce-interface { ! mandatory true; ! type string; ! } !! leaf ip-network { ! // the private IP network! mandatory true; ! type inet:ip-prefix; ! } ! leaf bandwidth { ! tailf:info "Bandwidth in bps"; ! mandatory true; ! type uint32; ! } !! }

L3 VPN YANG Service Model

Mapping Code. Create Only

NEDs / Device Models

1500 lines of Java or Python

XR NED

IOS NED

JuniperNED

Implementation Specific Packages

Vanilla NSO

Market Trends in Light of NW AutomationExecution at the speed

of software

• Agility, DevOps, NFV, SDN, new services platforms

Changing customer behavior and new

expectations

• Everything on demand• New services with a press

of a button

All of this requires successful, flexible automation and an agile E-2-E operation.

Rapidly changing business models

• Cloud services, virtualization, programmable networks

• New ecosystems andvalue chains

• OTT co-opetition

NSO Enables DevOps Network Automation

Development Testing Production

Market Requirements

Network Operations

Operational Requirements

Service Requests

Implement changes in run-time

New process for improving products and processes

Cisco NSO ReferencesMulti-vendor

WAN AutomationVirtual

MS/NFV/vEPCData Center Automation

Cloud Interconnect

Executive Summary—Value of Automation Reduce OpEx, Improve Time to Revenue and Avoid Cost

ROI Savings

88–738% $3–70M*

• 12 Month Payback Savings (based on Customer Interviews)• 61% Improvement in Operational Efficiency

• 5 Year savings• ROI Based on assumption on the network devices to be managed, device and service models that need to be developed• Included additional revenue uplift from improvement in new customer add

Source: Cisco BTA

Three Implementation Ambitions

DevOps Network Service AbstractionRFS Automation ++

Project Based Network Service AbstractionRFS Automation

API

Physical Networks

Virtual Networks

BSSOSS

Resource Facing Services (RFS)

Programmable Network InterfacePowerTool

P1

P2

API

Physical Networks

Virtual Networks

BSSOSS

Resource Facing Services (RFS)

API

Physical Networks

Virtual Networks

Device Abstraction

Three Implementation Models

API

Physical Networks

Virtual Networks

BSSOSS

Resource Facing Services (RFS)

P1

P2

API

Physical Networks

Virtual Networks

BSSOSS

Resource Facing Services (RFS)

API

Physical Networks

Virtual Networks

Device Abstraction

Focus for all NSO implementations

Varying ease of implementation

Still the vision!

Not fully utilizedLow hanging fruit!

DevOps Network Service AbstractionRFS Automation ++

Project Based Network Service AbstractionRFS Automation

Programmable Network InterfacePowerTool

• Let your strategy drive and be clear on scope and requirements

• Involve experts who have done this before – at least for verification

• Cross functional teams with software skillsNSO minimizes programming but it does not eliminate it. This is software development.

• Automated testing – continuous integration, on real devices, from start

• Proper environment strategy and change control tools

• Top management support to invest in new paradigm to get benefits

• Be careful not to force legacy IT processes and tools onto automation team

• Adapt ambition to overall maturity

• Watch out for automating current way of working

Key Success Factors

Avoid the Red Whale!

Experience from NSO Deployments

DON’T

Sales Point of sales Delivery

PoCTS/Tail-F Support

No involvement of non project SMEs. Design challenges

may lie dormant

Lack correct competency, challenges already inherent in

design grow as time pressure rise

Reach out late into build to support and also discover test errors near final delivery date. Difficult to address the situation

Miss requirements, design challenges may occur later

Requirements Verify Competence

Testing

Test

DO

Sales Point of sales Delivery

PoCTS/Tail-F Support

Use expertize in TS/Tail-f early, e.g. find design

challenges prior to build

Has software build competency and solid design

Testing is automatic, LUX, continuous, on hardware. Challenges are found and addressed well ahead

of time

Ensure detailed statement of work and requirements exists

and are reflected in design

RequirementsVerify

Competence Testing

TestTestTestTestTest

Strategy has to be enabled by People, Processes and Technology

STRATEGY

PROCESS

TECHNOLOGYPEOPLE

Realizing full DevOps RFS automation can only happen when all elements support it

NSO

Modern SW processes and supporting tooling

Modern SW skillsNetworking skillsAlignment to strategy

STRATEGY

PROCESS

TECHNOLOGYPEOPLE

Begin with the end in mind but stage the journey

DevOps Network Service AbstractionRFS Automation ++

Project Based Network Service AbstractionRFS Automation

Programmable Network InterfacePowerTool

STRATEGY

PROCESS

PEOPLE

TECHNOLOGY

Step 1 Step 2

STRATEGY

PROCESS

PEOPLE

TECHNOLOGY

Step 3

STRATEGY

PROCESS

PEOPLE

TECHNOLOGY

Step 1—Programmable Network InterfaceFeatures:• Rich set of Northbound APIs rendered from models

• Network-wide CLI and REST

• Transaction-safe operations

• Minimizing manual fallouts

• Device Configuration Management and Accurate network configuration state

• Golden Configs

• Compliance Reporting

PackageManagerCDB

DeviceModel

Operations IT/OSS/BSS Network Engineer

• Lack of automation, Managing device configuration• Quality issues in delivery• Inflexibility to change existing configuration (create

and delete only)• CLI Scripting—inflexible and high fallout

Fixes these chronic issues:

Step 2—Network Service AbstractionAdditional Features with Service Models:

• Full service automation

• Network run-time modifications• Create, Modify, delete

• Service Plan—how far the service has come

• Service Health (Orchestrated Assurance)• SLA Status

• Service KPIs

PackageManagerCDB

DeviceModel

Operations IT/OSS/BSS Network Engineer

• Lack of zero touch automation• No service insight• Lost data in brownfield network • Quality issues in service delivery, inconsistency• Inflexibility to change existing services (create and

delete only)

Fixes these chronic issues:

Service Model

Continuous Integration and Delivery (CI/CD)

SI

Step 3—Developer Tools and SDK Content

NSODesign Instances

NSOTest Instances

NSOProduction Instances

Market Requirements

Operational Requirements

Service Requests

• Dev-local multi-vendor network simulator• Full production-grade installation in dev environments• YANG tools including validator, compiler• Project tooling for managing package sets

CREATE

• Dev-local multi-vendor network simulator• Build- and runtime validation of package content• Offline-tools for validating version migration

VERIFY

• Self-contained and versioned package format• Hitless package installation and version migration• Local or remote project and package locations

PACKAGE

Multi-vendor Support

Change Requirements REQUIRED CHANGES

PeopleCross-functional teams

with software skills

ProcessDevOps

TechnologyNetwork Operating System built for DevOps with modern IT tools

CURRENT SITUATION

PeopleWalled-off departments, lacking software skills

ProcessWaterfall development processes if any development process at all

TechnologyRigid, built for single purpose, inflexible

People Technology

Process

Strategy

Strategy

Process

Tech-nologyPeople

STRATEGY TECHNOLOGY

PEOPLE PROCESS