Networking revolution in last 6-7 years. This document shows the very brief of high level concept in changing Networking technology from legacy networking to future ideas.

1. Networking
Revolution
NAHIAN CHOWDHURY

2. Traditional Networks
ASIC ASIC ASIC
CPU RAM
Control Plane
Data Plane
 Issues:
 Scalability
 Programmability
 Administrative Challenges
 Classifying Data and Routing Traffic.
Traditional Data Center
 Issues:
 Aggregation complexity/failures.
 Expensive Rack.

3. Traditional Protocols
 RIP – Distance vector Routing (Hop Count)
 OSPF – Dijkstra Algorithm- Shortest path first
 Backbone Area, Stub Area, Not-so-Stub Area
 Handle VLSM
 EIGRP - Metric based - 𝑀𝑒𝑡𝑟𝑖𝑐 = 𝐵𝑎𝑛𝑑𝑊𝑖𝑑𝑡ℎ
+ 𝐷𝑒𝑙𝑎𝑦 ∗ 256.
 NAT, ACL, BGP, MPLS
 Constraints :
 Scalability
 Performance – QoS
 Not Programmable
 Not Dynamic
 Expensive
 Solutions:
 Separation of Control Plane and Data Plane

4. Road towards SDN
 First Separation of CP and DP
 In Telephone Network by At&T
 Problems in AS communications
 Each router has limited visibility of
IGP and BGP
 No central point of
control/observation
 Resource limitations on legacy
routers
 Introduced Routing Control Platform (RCP) by At&T –
2004
 RCP Computes BGP on behalf of routers.
 RCP obtain the network view by OSPF / IS-IS

5. 5Road Towards SDN (2)
Route Control
Server (RCS)
BGP Engine IGP Viewer
Routing Control
Platform (RCP)
Available
BGP routes
BGP
updates
…
Selected
BGP routes
BGP
updates
…
Path cost
matrix
IGP link-state
advertisements…
Source: Matthew Caesar, UIUC

6. Revolution with SDN
PKT forwarding
Operating System
PKT forwarding
Operating System
PKT forwarding
Operating System
PKT forwarding
Operating System
PKT forwarding
Operating System
Network Operating System
App. App. App.
Data
Plane
space
Control
Plane
space
1- Network
abstraction
2- Programmability 3- Data-plane & control-
plane separation
4/24/2017 Slide 6

7. OpenFlow
 Why?
 Closed System
 Stuck with interfaces
 Complex functionality inside Hardware
 Service aggregation
 Traffic Engineering
 OpenFlow:
 High Speed
 Scalability
 Flexibility and control of Software
 How?
Data Path (Hardware)
Control Path OpenFlow
OpenFlow Controller
OpenFlow Protocol (SSL/TCP)

8. SDN Controller
 The SDN controller can be a server
running SDN software.
 The Controller communicates with a
physical or virtual switch Data Plane
through OpenFlow protocol.
 OpenFlow conveys the instructions to
the data plane on how to forward
data.
 NOX, POX,
 Floodlight
 OpenDayLight
 Dijkstra Algorithm
 Network Automation
 Controller can implement network
commands to multiple devices

9. Use Cases of SDN-NFV
 NFV – Network Function Virtualization
 NFV and SDN are highly
complementary.
 Use Case 1: Virtualization of Mobile
Core Network Nodes
 Use Case 2: Virtualized Home
Environment
 Use Case 3: Virtualization of CDNs
 Use Case 4: Service Chaining
Virtualized Network Functions (VNFs)
NFV Infrastructure (NFVI)
Physical Infrastructure
Virtual Infrastructure
Compute Storag
e
Networ
k
Virtual
Computing
Virtual
Storage
Virtual
Networkin
g
NFVManagementand
Orchestration(MANO)
VNF VNF VNF VNF
NFV Scope
OSS /
BSS

10. Docker
 Current Docker
 Containernet
 Emulate the Docker container as
Mininet host

11. Future Docker Implementation 11
OpenFlow
Ctrl’er
h1
(host)
h2
(host)
PDN
AP AP
m1
m2
X1
X2
Floodlight
S1 (Docker
Switch)
S2 (Docker
Switch)
S2 (OVS)
Docker container = Enhanced Forwarding
Element (EFE)
S2 (OVS)S1 (OVS)
Current Mininet MobileUpgraded with Docker System
S1 (OVS)
©Huawei Technology,
Munich.
Abteilung: FNT

12. Thank you

13. Road Towards SDN (3) - Extra
 Clean State 4D
 Decision Plane
 Dissemination Plane
 Discovery Plane
 Data Plane
 Decision Plane: All management logic
implemented on centralized servers
making all decisions
 Dissemination Plane: Provides a
robust communication channel to
each router.
 Discovery Plane: Each router
discovers its own resources and its
local environment.
 Data Plane: Spatially distributed
routers/switches
Decision
Dissemination
Discovery
Data
 Issues:
 With the Ethane switch, need to
access the flow table directly from a
controller.