SOFTWARE DEFINED NETWORK 
Ravi
Agenda 
• What? Why? 
• Architecture 
• SDN Controllers 
• Open Flow 
• Daylight Control 
• Cisco 
• Cisco ONE 
• Cisco onePK 
• Google B4 
• Demo
What is SDN? 
The physical separation of the network control plane 
from the forwarding plane, and where a control plane 
controls several devices 
• Directly programmable 
• Agile: Abstracting control from forwarding 
• Centrally managed 
• Programmatically configured 
• Open standards-based vendor neutral
SDN Operation - Control/Data Plan 
• Control plan :Logic for controlling forwarding behavior. 
Examples: routing protocols, network middle box configuration 
• Data plane : Forward traffic according to control plane logic 
— Examples: IP forwarding, Layer 2 switching
Why? So Many Uses/Use cases 
1. Virtualization: Use network resource without worrying about 
where it is physically located, how much it is, how it is 
organized, etc. 
2. Orchestration: Should be able to control and manage 
thousands of devices with one command. 
3. Programmable: Should be able to change behavior on the fly. 
4. Dynamic Scaling: Should be able to change size, quantity 
5. Automation: To lower OpEx minimize manual involvement 
 Troubleshooting 
 Reduce downtime 
 Policy enforcement 
 Provisioning/Re-provisioning/Segmentation of resources 
 Add new workloads, sites, devices, and resources.
Why? So Many Uses/Use cases 
6. Visibility: Monitor resources, connectivity 
7. Performance: Optimize network device utilization 
 Traffic engineering/Bandwidth management 
 Capacity optimization 
 Load balancing 
 High utilization 
 Fast failure handling 
8. Multi-tenancy: Tenants need complete control over their 
addresses, topology, and routing, security 
9. Service Integration: Load balancers, firewalls, Intrusion 
Detection Systems (IDS), provisioned on demand and placed 
appropriately on the traffic path
SDN Architecture
SDN Controllers 
Many Different SDN Controllers 
• NOX/POX 
• Ryu 
• Floodlight 
• OpenDaylight 
• Pyretic 
• Frenetic 
• Procera 
• RouteFlow 
• Trema 
! NOX/POX 
! Ryu 
! Floodlight 
! OpenDaylight 
! Pyretic 
! Frenetic 
! Procera 
! RouteFlow 
! Trema 
3
Open Flow 
OpenFlow Protocol Specification 
! OpenFlow controller communicates with 
switch over a secure channel 
" OpenFlow protocol defines message format 
" Purpose of control channel: update flow table 
" Logic is executed at controller
Matching (OpenFlow v. 1.0) 
! Packet header fields matched against one of N 
tables 
! If no match, packet is sent to controller 
! Otherwise, switch performs action 
5
Open Day Light
Cisco ONE
Cisco onePK
Cisco Controller
Cisco Application Centric Infrastructure
Google B4 Architecture 
-Software-defined WAN 
• Logically centralized traffic-engineering controller, which allows applications to manipulate bandwidth 
across data centers through WAN networks. 
• Automation - separate monitoring, management and operation from individual boxes
Amazon VP Cloud 
Dynamic Scaling of Resources: 
Amazon Virtual Private Cloud 
! Connect logically 
isolated VM 
instances to existing 
network 
! Connection to 
existing 
infrastructure via 
VPN 
hDp://aws.typepad.com/aws/2009/08/introducingHamazonHvirtualHprivateH 
cloudHvpc.html)
ADDITIONAL SLIDES
Network Function Virtualization
Cisco ONE
Network Programmability Models
Active Networks 
• Networks where switches perform custom 
computations on packets 
• ž Examples (and motivation) 
• —Trace program running at each router 
• —Middleboxes: firewalls, proxies, application services
Network Virtualization 
• What is Network Virtualization? 
• ž Representation of one or more logical network 
topologies on the same infrastructure. 
• ž Many different instantiations 
—Virtual LANs (VLANs) 
—Various technologies and network testbeds —Today: 
VMWare, Nicira, etc.