SDN and NFV Value in Business Services - A Presentation By Cox Communications
Download as PPTX, PDF4 likes2,509 views
The document discusses the role of Software-Defined Networking (SDN) and Network Function Virtualization (NFV) in modern network architecture, highlighting their benefits such as automation, optimization, and flexibility. It outlines the current challenges faced by network providers, including high costs, inflexibility, and increasing complexity. Furthermore, it presents various use cases for SDN and NFV, illustrating their potential for enhancing network performance and service provision.
SDN and NFV Value in Business Services - A Presentation By Cox Communications
- 1. SDN and NFV value in Business Services. Innovations in Network Monetization and Optimization. * Mazen.Khaddam@cox.com, Loukas@cisco.com Network Architecture Groups M. Khaddam*, L. Paraschis
- 2. SDN & NFV SDN = Control Plane Programmability NFV = Data Plane Programmability Service Plane Programmability?
- 3. Current State of Network Plumbing 3 Cox Packet Layer Network The current state of network technology is: Expensive • Traffic will continue to increase & network will experience failures • All service providers network is 2x – 3x overprovisioned to handle failures • The Backbone experiences on average 3 fiber cuts per month Inflexible • It is hard to change the number of logical paths and their speeds dynamically based on services • It is difficult to delete logical paths when not needed • Lack of programmability Complex • Network complexity is increasing • The maintenance of the network is complicated by using different network operating systems • Lack of coordination between network layers & services
- 4. Layers in an IP/Transport Network 4 IP Traffic Flows Layer-2 Links (Ethernet, DS1/DS3, etc.) Layer-2/3 VPN and Carrier Ethernet Services IP Routing Topology (OSPF,etc.) MPLS/Virtual Link/Tunnel Layer VPN A VPN B VPN A VPN B Transport Layers Digital Channels (SONET/SDH/OTN) Source: Designing Multi-Layer Carrier Networks for Capacity and Survivability, OPNET Technologies, Inc., OPNETWORK 2012. Layer 0 < Data Plane abstractions Only -- where are the control plane abstractions?> Layer 1
- 5. SDN Defined Source: ONF According to ONF SDN is a network in which the control plane is physically separate from forwarding plane. The SDN architecture must open, programmable & standard. SDN Proposition value – Network automation – Optimization – Flexibility & efficiency The Benefits of SDN – Provides more control – Enable programing – Better Guarantees SDN as defined by Open Network Foundation Traditional control control control control control coordination primitivesprotocols Source: Bruce Davie , Principle Engineer VMware , ONS 2013 SDN
- 6. NFV based on ETSI: Separate network function from Hardware : Source ETSI • Move functions from hardware to software • Leverage COTS • Reduced equipment costs and reduced power consumption • Increased speed of Time to Market • Scale up/down dynamically • Purpose hardware to support defined functions • Difficult to scale to handle unscheduled events • Expensive
- 8. Hydrogen Release: OpneDaylightt Source: SDN Hub 8 Base Network Service Functions Management GUI/CLI Controller Platform Southbound Interfaces & Protocol Plugins OpenDaylight APIs (REST) DOVE Mgr Data Plane Elements (Virtual Switches, Physical Device Interfaces) Service Abstraction Layer (SAL) (plug-in mgr., capability abstractions, flow programming, inventory, …) OpenFlow 1.0 1.3 LISP Topology Mgr Stats Mgr Switch Mgr Host Tracker Shortest Path Forwarding VTN Coordinator Affinity Service Network Applications Orchestration & Services OpenStack Neutron OpenFlow Enabled Devices VTN Manager VTN: Virtual Tenant Network DOVE: Distributed Overlay Virtual Ethernet DDoS: Distributed Denial Of Service LISP: Locator/Identifier Separation Protocol OVSDB: Open vSwitch DataBase Protocol BGP: Border Gateway Protocol PCEP: Path Computation Element Communication Protocol SNMP: Simple Network Management Protocol LISP Service NETCONF BGP-LS Additional Virtual & Physical Devices SNMP DDoS Protection Open vSwitches OVSDB PCEP OpenStack Service Network Config Main difference from other OpenFlow-centric controller platforms
- 9. Core Long Haul DWDM Service Provider SDN use cases Data CentreMetro and AccessCPE Metro DWDM Data Centre Virtualized n/w Virtual 2 virtual n/w interconnect Service chaining appliances Analytics collection Core Infrastructure Bandwidth calendaring Demand engineering / PCE Single/multi layer optimization Analytics collection Agg and access Infrastructure Automated set-up Analytics collections Service definition Optimization CPE NFV Services provisioning Analytics Edge Edge NFV Services Provisioning Analytics
- 10. Control Program/ Manager A Control Program/ Manager B Example: Network Virtualization Virtualization Associated SDN/ Network Function Virtualization OF-Agent App App App Example: Open Flow - centric Controller & Agent Flow based SDN Example: Path Computation PCC PCC PCC PCEP Applicability to market segment Metros BBData Centre Applicability to market segmentApplicability to market segment Infrastructure Controller based SDN SDN and NFV Categorizing current SDN/NFV ModelsSDN & NFV Use Cases OF Agent OF Agent
- 11. Network Plumbing: Infrastructure Controller Topology Config BGP v4/v6 Optimization / Analytics Algorithms Infrastructure Controller Utilization Packet Network Traffic Matrix Optical Network Device Level APIs OpenFlow, I2RS, SNMP, Netconf, CLI ,PCEP Application and Sub-Systems Application API
- 12. Google B4, SDN Global WAN
- 13. SDN Optimization & Automation with PCE Google B4, SDN Global WAN
- 14. Microsoft SWAN: Software-defined networking Source: Stanford University networking Seminar – Tested-Based Evolution Hong Kong Seoul Seattle Los Angeles New York Miami Dublin Barcelon a WAN Network Agent Service broker Traffic demand BW allocation Network, Config Topology, traffic Rate limiting
- 15. Cox Case Study: SDN – PCE vs Distributed path Compution 0.00% 10.00% 20.00% 30.00% 40.00% 50.00% 60.00% 70.00% 80.00% 90.00% 100.00% 1 6 11 16 21 26 31 36 41 46 51 56 61 66 71 76 81 86 91 96 101 106 111 116 121 126 131 136 141 146 151 156 161 166 171 176 181 186 191 196 201 206 211 216 221 226 231 236 LinkUtilization Links Path Compuation Model Online PCE
- 16. WAN Controller - Use-Case example Bandwidth Scheduling (On-Demand) Controller NB API WAN R1 R2 R3 1 4 Data Center #1 Data Center #2 ① Network conditions reported to collector ② Cust requests DC #1 – DC #2 bandwidth asap ③ Demand admission request: <R1-R3, B/W, NOW!!> ④ SDN WAN returns option and cust confirms ⑤ R1-R3 LSP Tunnel Programmed via PCEP 2 Web Portal Congested!! 3 PCEP 5 Collector & modelling Programming
- 17. NFV use cases - vPE to VPN mapping SP WAN SP Data Center WAN Controller Collector Program ming Cloud Controller DC WAN Gateway DC Fabric Server Server Tenant 1 VM Tenant 2 VM Tenant 1 VM Tenant 1 VM vPEF VRF1 vPEF VRF2 VRF1 VRF1 VRF2 VRF1 VRF2 VRF3 Server Tenant 2 VM Tenant 3 VM vPEF VRF3 VRF2 VRF3 BGP MPLS VPNs extended into the DC
- 18. SDN “southbound” Automation of Service & Network Programmability – YANG/NETCONF