WIXLIB

SDN and NFV:Why ODL ticks all theright boxes?Sridhar K. N. Rao (Ph.D)NEC Technologies India Limited.sridhar@linux.comwww.theraos.in

Acknowledgement Image Sources. NEC America. ETSI-NfV Framework ETSI-NFV PoCs– From slides distributed during SDN-NFV Conferenceheld at Dusseldorf, Germany, in October 2014. ONF Stefan Schnitter Jim Machi Justin Dustzadeh THANKS A LOT.

Agenda

6 Questions What is NFV? Role of SDN in NfV? SDN-Elements (Controller, NEs and Apps) inNfV Architecture? What are expectations from SDN controllersfor NFV? Why ODL ticks all the right boxes? What are the related trends to look out for?

What is NfV?

Traditional ApproachMessageRouterCDNSession BorderControllerDPIPHYSICALFirewallCarrierGrade NATNETWORKFUNCTIONSPE RouterEPCWANAccelerationBRASDNSTester/QoEmonitor Fragmented non-commodity HW Physical install per appliance per site Low asset utilization HW development is time consuming and can’t becontinuously deployed / upgraded HW development is challenging for new vendors Limits modularity, vendor choice

Flexibility / ExtensibilityHigh asset utilizationContinuously deployed / upgradedAchieve ModularityGain Software benefitsOpens the competitive landscape upInnovative EcosystemVirtualized Network plianceApplianceNFVCommodity/Off theShelf Servers andNetwork ElementsOrchestrators(OpenStack)and otherControllers

What is NfV Cloudifying** the Network Network Functions Virtualization (NFV) replaces theneed for physical appliances with virtualized networkfunctions running on standard server platforms Moving the functions usually embedded in networkhardware into software that can run in a VM on thestandard servers. Functions: Routers, DPI, EPC, Firewalls. Separation of HW and SW NO Vertical Integration Hw Vendor, Sw Vendor, Management Soln. Vendor Once Network elements are software-based hardwareelements are managed as a ‘pool of resources’.** Alcatel-Lucent

Examples: vCPE and vEPC

vCPE(1) IP service edge function as VNF on COTSserver(2) CPE functionalities integrated into telecomcarrier facilitySource : www.nec.com

vEPCSource: www.nec.comSource: 3gpp.org

NfV Architecture

NFV ArchitectureOs-MaOSS/BSSOrchestratorSe-MaService, VNF and InfrastructureDescriptionEMS 1EMS 2EMS 3Or-VnfmVe-VnfmVNFManager(s)VNF 1VNF 3VNF tualNetworkNf-ViVirtualisation n reference ware resourcesNetworkHardwareOther reference pointsSource: ETSI NFV Architectural FrameworkMain NFV reference points

A Layered ViewSource: Andy Reid, British Telecom

Examples: Proof of Concepts

CloudNFV Open NFV Framework – PoC#1Source: ETSI PoCs

E2E vEPC Orchestration in an multivendor open NFVI environment – PoC#5Source: ETSI PoCs

Virtualized Mobile Network withIntegrated DPI – (PoC#6)Source: ETSI PoCs

Biggest Challenge How to achieve Carrier Grade? Uptimes: Five-9s at the services level and Six-9s forthe Infrastructure (including networking).* Enterprise software : Three-9s Ensuring a highly stateful and secure end-to-endservice is always available. StatefulnessHigh AvailabilityUltra-low Latency.Security & ReliabilityRapid Provisioning and Resource Optimization

Carrier Grade Vs COTS –Hardware* Carrier Grade Strong fault detection and fault isolation capabilities athardware level Well established traditions on software upgrade,patching, and maintenance Reliably Central Office assumed COTS May have smaller “mean time between failure” (MTBF) Relative smaller “mean time to repair” (MTTR) COTS procedures for software upgrade, patching, andaintenance contribute more to “scheduled down time” Different grade of reliability for data centers*Dr. Li Mo, CTO Group

SDN in NFV

SDN is Necessary to Exploit the NFV Potential .Prodip Sen, HPSDN and NFV: Twins or Distant Cousins ?.Arpit Joshipura (Dell)SDN and NFV are independent.But, SDN has a significant role toplay in NfV Carrier SDN SDN NFV , is getting mature andcommercially ready brings significant benefit toTelecom Industry .Hashimoto (NEC)

SDN is already been well explored by Telcos for(multi-layer) WAN.We can come across many solutions where SDN isused for Transport Networks (SDN-Transport)SDN has played a Significant role in such MultiLayer/Multi-Domain environments.SDN in Telco Clouds with NFV

SDN and NfV: Similarity * Both owe their existence to similar marketforces, Better processor capability significant improvement in the processor technology Simplification in connectivity - scope forseparation of planes. Virtualization maturity. Both technologies are designed to increase flexibility,decrease costs,support scalability,and speed the introduction of new services.Source: Stefan Schnitter – Detecon International*Source: Jim Machi

Why Do we need SDN inNfV? It is not mandatory to have SDN for NfV. But NFV is a complementary initiative to SDN. SDN makes realization of NfV much easierand better - improve performance andsimplify operations As long as NFV addresses the general caseof ’policy-managed’ forwarding, and needdynamic service orchestration SDN can play a major role.

Why do we need SDN inNfV ? Use of Dynamic Virtual Overlays and needfor Multitenancy in NfV also drives the needfor SDN. Currently, the widely acknowledged role ofSDN in NfV: Supporting Service ChainManagement. Traffic Steering. Offload, Bypass, Selection, etc. Dynamic Scale-up and Scale-out Service chain with Virtual-Networks. Load Balancing.

Service chaining On-demand network service composition bydynamically chaining virtual networkfunctions, such as router, firewall, DPI, uter

ETSI : SDN for NfV Classification of user-traffic Adding labels to the packet. L3-L4 or L7 traffic steering. L2-Transparent network service chaining with traffic steering. Automation of mapping in Multi-layer bandwidth on Demand Automation of the process to map the service request requirements intoavailable network resources Dynamic manage of these resources can map the service into the appropriatenetwork layer for the most efficient use of network resources Interconnecting VNFCs Interconnecting VNFs – connecting traffic sources and sinks, provideprocessing of traffic in transit. To provide a specified service of network design. Chained based on customer policy/service or on VNF Processing. Load balancing across VNFs - VNF elasticity.

Summary: SDN in NfVFlexible erlays.Policy EnforcingTraffic Engineering

Real-World SDN & NFV DevelopmentsSource: Justin Dustzadeh, Huawei

ETSI NFV Proof of ConceptsSource: ETSI-NFVService Description(Infrastructure ntVirtualizationmanagementNOVA APISWIFT APIQuantum APIVirtualized Infrastructure Manger - OpenStackNOVASWIFTSDN pluginRest API /Network serviceNf-ViSDN AgentL2 SwVM-1VM-2SDN pervisorOpenFlowHypervisorNeutronSDN daemon SwitchStandard L2PhysicalLayerSwitchFabricServer HWDC GWIP CoreNetwork SDN is used to implement the MAC forwarding required to TheQOSMOSDPI VNFsVNFCexpectspackets routedconnectthe clusteredcomponentswithinthroughthe VNF andand/orcopiedits toportsthat it can analyse the traffic.to connectthe toVNFthe sonetwork.

SDN Elements in NFVarchitecture

SDN ComponentsBusiness Apps PlaneSDN ApplicationsControl PlaneMANAGEMENTPLANESDN ControllerData PlaneOSS/BSSNETWORK ELEMENTSSource: ONF

Source: ETSI GS NFV-SWA 001 V1.1.1-NFV ArchitectureOs-MaOSS/BSSOrchestratorSe-MaService, VNF and InfrastructureDescriptionEMS 1EMS 2Or-VnfmVe-VnfmEMS 3VNFManager(s)VNF21VNF 3VNF irtualNetworkVirtualisation Layer1ComputingHardwareExecution reference rdware resourcesNetworkHardware0Other reference pointsDataVirtualisedInfrastructureManager(s)4Main NFV reference pointsControl

SDN in NFV Architecture DATA: SDN-enabled Network Elements Virtual and Physical CONTROL: SDN Controller. APPLICATION: SDN Applications. SDN enabled Virtual Network Function? Should there be any overlap with VNFM andSDN Controllers? VNFs are providing networking services - virtualrouters – They may be configured by SDNControllers?

SDN Controllers and Nfv

NfV framework enhances andredefines the role of SDNcontrollers.

Expectations from an SDNController for NfV Multi-Deployment Support Fully Programmable, Open Interfaces Virtualized Infrastructure connectivity Management. Support Multiple Southbound/Data-Plane Elements Interoperability with other controllers/orchestrator/managers. Rich Feature Set. Routing, SFC, etc. Transport Networks: Multi-Layer Multi-Domain Non-Functional: Scalability Low-Latency

SDN Controller Deployment OptionsOptionsDescriptionSingle/Redundant Single (or with redundancy) controller for the networkHierarchicalA hierarchy of controllers with, possibly, client/serverrelationships between them.OptionsNon DescriptionComplete controller instance running on single system (aphysical machine)Controller instance running in virtualized environment (as aVM)DescriptionAll the SDN controller functions running under singleinstance.SDN controller functions are distributed.

Deployment SDN Controller should supportmultiple deployment models. Support different Control planeoptions in NfV Architecture. VIM, NFVI, VNFM, etc. In either case - Supportappropriate interfaces in eachmodel and option.

Virtualized Infrastructureconnectivity*** Responsible for the following aspects relatedto NFVI connectivity services: Interconnecting VNFs Waypoint * support. Resource management and tracking of networkresources and attributes such as bandwidth,jitter, delay etc. Connectivity services to create overlay tunnels(e.g., VXLAN, NVGRE, MPLS over GRE) ornetwork partitions.

Support MultipleSouthbound/Data-PlaneElements Southbound support of multiple protocols OpenFlow, NetConf, SNMP, BGP-LS etc Support IETF protocols to control physicaland virtual routers and switches Border Gateway Protocol – Link State (BGP-LS) – Path Computation Element Protocol (PCEP) –

Fully Programmable, OpenInterfaces Fully programmatic open interfaces forservice and Resource Orchestration withinand across NFVIs (Data-Centers). Support different deployment options too. Minimize Manual/Proprietary interfacing.

Interoperability Interoperability with other controllers andOrchestrators. Non-SDN Network Controllers VIMs Support different scenarios Multiple Orchestration (VIMs)? Single VIM and multiple SDN Controllers. Within Single and Across Multiple Data Centers.

Transport Networks Support:Interconnecting Data CentersController/OrchestratorVIMVIMSDN Controller(s)SDN Controller(s)SDN Controller(s)NEsNEsNEsDC-1WANDC-2

Rich and Relevant FeatureSet Features : Multi-layer Topology Management.Real-Time Monitoring.Policy Driven Load Balancing.Policy Driven Traffic Steering.Service Function Chaining Management.

Service Insertion and Chaining Ability to manage network service chains. Ability to manage network functions within the chain – Service Insertion/Deletion No disruption to existing traffic when new service is inserted in the chain. Traffic Steering Ability to define traffic rules to bypass network functions in thechain. Ability to define traffic rules for selecting the chain out ofmultiple chains. Multi-tenancy and Service Chaining Management of network service chain with virtual networks. Ability to associate multiple network service chains to a network.

Why ODL ticks all the rightboxes?

ODL is the best OpenSourcesolution we have for NfV, at leastfor now, and the competition isheating up!

ODL for NfV: FeaturesExpectationsODLMultiple Deployment Model Support – Including the modularity,Clustering and Virtualization of the ControllerYESMultiple Southbound Protocols including IETF ProtocolsYESService Function Chaining and InsertionYES and PARTIALMultiple Network Virtualization supportYES [VTNs, Dove, etc]Multiple Network Configuration ProtocolsYES (NETCONF andSNMP)Multi-Layer Network Optimization for transport networks.YESSupport for Integration with VIM (Openstack) and VNFM (Proprietary). YES and PARTIALDeeper Integration with Openstack.InteroperabilityYES