BRKRST 1014

Introduction to Software-Defined
Networking (SDN) and Network

Programmability
Nathan Holland – Systems Engineer (Cisco)

BRKRST-1014
Agenda
• Software Defined Networking (SDN) - Defined

• SDN Use Cases
• Key Concepts & Technologies
• API’s and Data Models
• SDN Controllers
• Where to Learn More and Questions
About me…
ICT Industry 10+ Years

CISSP
CCNP (R/S)
Meraki CMNA
BRKRST-1014
© 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 4
Software Defined Networking (SDN)
Defined….
• Dynamically apply state and control to network
infrastructure using globally aware software controls
• An approach and architecture in networking where control and data planes are decoupled and
intelligence and state are logically centralised
• Enablement where underlying network infrastructure is abstracted from the applications [network
virtualisation]
• A concept that leverages programmatic interfaces to enable external systems to influence network
provisioning, control and operations
BRKRST-1014 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 6
What does your day to day look like?
7% Other
14% Traffic Optimisation

43% Other 36%
14% Equipment Upgrade More Time Available for
Business Innovation
18% Configuration 10% Traffic Optimisation
19% Security 14% Equipment Upgrade

8% Configuration
36%
10% Security Total Network Operations
28% Troubleshooting Time Savings
14% Troubleshooting
Current IT* Fast IT

* Source Forrester Commissioned Study BRKRST-1014 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 7
SDN is..
…a new approach at network transformation
…impacting the networking industry
…providing new methods to interact with equipment/services via controllers, APIs
…enabling high-scale, rapid network and service provisioning/management
…generating a LOT of ‘buzz’ and attention
…providing a catalyst for traditional Route/Switch engineers to branch-out
SDN is not..
…an easy button
…a end-state
…narrowly defined
…meaning the death of network engineers
…a mandate for all network engineers to become C and Java programmers
…a new attempt at network evolution
Evolution of Network Configuration
1990s Today
hq>enable
hq# config terminal
hq(config)# interface fastethernet 1/1
NEXUS>enable NEXUS(config)# feature eigrp
hq(config-if)# ip address
NEXUS# config terminal NEXUS(config)# router eigrp Test1
1.1.1.1 255.255.255.0
NEXUS(config)# interface NEXUS(config)# interface
hq(config-if)# no shutdown
ethernet 1/1 ethernet 1/1
hq(config-if)# exit
NEXUS(config-if)# no switchport NEXUS(config-if)# ip router
hq(config)# router eigrp
NEXUS(config-if)# ip address eigrp Test1
hq(config-router)# network 1.1.1.0
1.1.1.1 255.255.255.0 NEXUS(config-if)# no shutdown
hq(config-router)# exit
NEXUS(config-if)# no shutdown NEXUS(config-if)# end
hq(config)# exit
NEXUS(config-if)# exit NEXUS# copy run start
hq# copy run start
Drivers for change
• Familiar Manual, CLI-driven, device-by-device approach is inefficient
• Increased need for programmatic interfaces which allow faster and
automated execution of processes and workflows with reduced errors
• Need for a ‘central source of truth’ and touch-point
BRKRST-1014 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Challenges
• Complexity
• Pace of Change – Technology & Competition
• Consistent Pressure for Improved Operational Efficiency
• IT Budgets, Staffing and Resources
• Accelerated Pace of Cloud, Virtualisation and XaaS Options
• Consumption Economics
Microsegementation + Scale {^^} Brain
“If you dislike change, you’ll dislike
irrelevance even more”
Gen. Eric Shineski
Chief of Staff, US Army
Use Cases
SDN Use Cases
Network Function Network Traffic Service

Virtualization Abstraction Engineering Deployment
Traffic Engineering
An Intelligent WAN
WAN Transport
MPLS
$$$ Private
Cloud Virtual
Private
Cloud
Branch Internet
Low Cost Circuit, backhaul
Direct Cisco Internet, 4G
Cloud
Internet Web Security
Access $ Public
Cloud
ü Secure WAN transport across MPLS and/or ü Leverage Low Cost path for public cloud and
Internet for private cloud / DC access Internet access
Increase WAN Capacity Improve App Performance Scale Security at the Branch
© 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Traffic Engineering
Dynamic QoS
Session
Collaboration Policy
Application
QoS Changes Pre-QOS change – Default Classification

Post QoS change - Video
Enterprise Network
AP
Single policy request produces automated change across all network elements enabling
high quality user experience
Service Deployment
Network Plug ’n’ Play
Today’s Process Network PnP
Central Staging Facility

Ships
equipment 1 Pre Provision
Projects/Sites
• Install OS
• Install base
Network
config Network Admin
Reseller/Partner Admin
2 Install & Power-on 3 Monitor device

devices installation
Installer
Installer
Network Admin
Site-1 Site-2 Site-3 Site(s)
Low Cost Physical Consistent for devices and Greenfield &

GUI Based Secure
Installation PIN (Campus/Branch) Brownfield
ITSM Integration
Accelerate Trouble-Ticket Processing
User Problem:
Application is responding slow
1. User uses cloud service to open a ticket on the web

1. User calls helpdesk 2. User picks the problematic application form the list
2. Opens a ticket 3. servicenow -> API -> APIC-EM (open)
3. Ticket get’s routed 4. APIC-EM has user, application, location and network information
4. Case owner calls user 5. APIC-EM configures the ERSPAN and Wireshark Capture session
5. Tries to figure out the problem 6. APIC-EM -> servicenow -> User (action)
6. OK, we need a packet capture 7. User works until issue shows up again
7. Calls Networking team 8. User confirms the issue and the steps to re-create in servicenow
8. Need to find a Wireshark Analyzer 9. servicenow -> API -> APIC-EM (close)
9. Need login credentials to the closest network device 10.APIC-EM removes SPAN and Capture session
10. Need to configure a SPAN port 11.PCAP file get’s attached and the service request ticket get’s routed
11. Need to get there 12.Ticket owner has all information needed to immediately start
12. Need user to re-create the problem working on a solution
13. WTF, problem went magically away Overall all happened nearly in real-time information and it’s all
Overall this took a week and a lot of experts user driven
Key Concepts & Technologies
SDN Origins
The Traditional Network…
Control Plane (CP)
Control and Data
Plane resides within CP DP CP DP
Physical Device
Data Plane (DP)
CP DP CP DP
CP DP CP DP CP DP CP DP
Control plane learns/computes forwarding decisions

Data plane acts on the forwarding decisions
The Network As It Could Be…to an SDN ‘Purist’
CP DP CP DP
CP
CP DP CP DP
Control plane becomes centralised

Physical device retains Data plane functions only
The Network As It Could Be…In a ‘Hybrid SDN’
CP DP CP DP
CP CP DP CP DP
Controller
A Controller is centralised and separated from the Physical Device,

but devices still retain a localised Control plane intelligence
APIs and Data Models
Application Programming Interface
RESTful API’s
Well Understood HTTP or HTTPS

GET, PUT, POST, and DELETE
Easy to Develop Against
Client Server
Versioned Response in HTML, JSON / XML
NETCONF (RFC 6241)
Informational RFC 3535, SNMP has failed
CLI scripting was being extensively used for configuration
The Network Configuration Protocol (NETCONF) is a network management

protocol developed and standardized by the IETF …
NETCONF provides mechanisms to install, manipulate, and delete the

configuration of network devices. Its operations are realized on top of a simple
remote procedure call (RPC) layer. The NETCONF protocol uses an Extensible
Markup Language (XML) based data encoding for the configuration data as well
as the protocol messages. The protocol messages are exchanged on top of a
secure transport protocol.
NETCONF Layers
Content Config
Operation <edit>
Messages <rpc>
Transport SSH
YANG (RFC 7950)
YANG [1] is a data modeling language for the NETCONF network configuration
protocol…
YANG is a modular language representing data structures in an XML tree format.

The data modeling language comes with a number of built-in data types.
Additional application specific data types can be derived from the built-in data
types. More complex reusable data structures can be represented as groupings.
OpenFlow
What is OpenFlow?
API
Application
OF
OF Controller AGENT
…a Layer 2 communications protocol that gives access to the

forwarding plane of a network device,
…a specification for building switches conforming to the protocol
AT&T : Google : NEC : Princeton University
OPEN NETWORK FOUNDATION NTT Communications : SK Telecom : Verizon : Stanford University ONF Board
ONF Members
Accton China Telecom Globe Business Neptune Swisscom
ADVA Optical Networking China Academy of Google Netberg Tsmc
Alibaba Group Holding Ltd Telecommunications H3C Technologies Netscount Tata Communications
Allied Telesis Ciena HCL Netronome Telecom Italia
Argela Cisco Systems HPE Nokia TTA
Aricent Group Citrix Systems Huawei North Bound Telefonica
ARM Corsa Technology Infinera Noviflow Telus
AT&T Criterion Networks (I) Pvt Institute for Information NTT Communications Tenceni
ATTO Research Korea Ltd Industry (III) NXP TreQ Labs
Barefoot Networks Cyretix Intel xNet Uberflow
Beijing Internet Institute Dell/Force10 Networks Inventec Oracle Vello Cloud
(BII) Deutsche Telekom ITRI (Industrial Technology PCCW Global Verizon
BISDN ECI Research Institute) Plantia Systems Vodafone
Blue Coat Ecode Ixia Ricoh Whitestack
Brain 4 Net Ericsson Juniper Networks Samsung Wipro
Broadcom ETRI (Electronics and KulKloud Sanctum Networks Ltd XILINX
Brocade Communication Telecommunications Lenovo SDN Essentials Yahoo
Systems Research Institute) Lumen Networks SDN Lab ZTE
Cavium Extreme Networks Luxoft Sedona Systems
Cengn Facebook Mellanox Technologies SIA
CenX Fiberhome Technologies Microsoft Sify
Ceragon Fujitsu NAIM Networks SK Telecom
China Mobile Research Goldman Sachs NEC Smoptics
Center Gigamon Nephos Spirent
http://opennetworking.org
What Makes OpenFlow Different?
Flow Table
Ingres Source Dest Ether VLAN VLAN IP IP IP IP TCP/U TCP/U Action Priority Counter
s Port MAC Protoco
MAC Type ID Priorit SRC DEST TOS DP DP
l
y SRC DEST
Fwd Port 100

* * * *
Switching * * * * * * * 10
3c:07:54:*
Fwd Port 100
* * *Routing* * * * * * * * 12
192.168.1.*
Port 1 Fwd Port 100
* * * *
Replication/SPAN * * * * * * * 14…24
25 Drop 100
* * Firewall/Security
* * * * * * * * *
0x0800 Controller 100
* * * * *
Inspection * * * * * *
Vlan10 80 Fwd Port 8 200
* 00:01:E7:* * * * * *
Combinations * * *
80 Rewrite 200
* * *
Multi-action *
; NAT * * * 192.168.1.*
* * * 10.1.2.3;
Fwd port 9
10.* Local 200

*Local handling
* * * * * * * * * *
What Makes OpenFlow Different?
Actions
OPENFLOW CONTROLLER
Required Actions
Forward out all ports
1
except input port
2 2
Redirect to OpenFlow
Controller
FLOW
CPU Forward to local
TABLE 3
Forwarding Stack (CPU)
Perform action in flow

4
table
4 3
7
5 Forward to input port
SWITCH FORWARDING
5 ENGINE 6
Forward to destination
port
7 Drop Packet
1 6
OpenFlow Introduced Notable Features Flow-spec
Version Tuple
1.0 2009-12 Initial Specification [Still very prevalent in the market] 12
1.1 2011-02 Support for multiple flow tables; Added support for MPLS 15
Defined two operating modes – Hybrid | Pure OpenFlow
1.2 2011-12 Support for IPv6 34
Multiple Controller support
1.3 2012-06 Support for Rate Limiting; IPv6 Extensions, GRE 38
Version increasingly targeted by customers/manufacturers
1.3.1 2012-09 Support for Negotiation TLVs 38
1.3.2 2013-04 Support for controller-initiated connections 38
1.4 2013-10 Support for Rule change ‘transactions’ (1.4.1 April 2015) 40
1.3.3 2013-12 Update with IANA registered TCP port : 6653 40

Clarify multipart segmentation rules, clarify use of empty multipart messages
Specify the normal fragment handling is mandatory, drop/reasm optional
1.3.4 2014-03 Clarify table feature wildcard list should not include fields that are mandatory in some context 40
Only
Add section about control channel maintenance
Push MPLS should add a MPLS header before the IP header and before MPLS tags, not
before
VLAN which is not valid
1.5 2014-12 Egress Tables; Packet aware pipeline (IP, PPP); flexible encoding - OpenFlow 44
eXtensible Statistics (OXS); set-field action wildcard; Controller connection status
(1.5.1 April 2015)
OpenFlow is one Fish in the Sea of SDN
SDN Protocols in Internet
Application Frameworks, Management Systems, Controllers, ...
“Protocols” OpenFlow I2RS PCEP BGP-LS/FS Neutron OMI Puppet NETCONF
Management OMI Puppet NETCONF

Agent Agent Agent
Orchestration OpenStack
Agent
Network Services BGP PCEP BGP-LS/FS
Agent Agent
Radius
Control SNMP I2RS
Agent
…
Forwarding OpenFlow
Agent
Device Operating Systems – Cisco IOS / NX-OS / IOS-XR
Industry Communities, Projects and
Standards Bodies
Cisco Innovations:
FEX Architecture
Technical Advisory
802.1 Overlay
Board seat Open Network Research
Networking Project
Center at Stanford
University
Puppet Agent
Modules
Puppet Labs
Initiatives:
investor
Contributor - Neutron API
Technical Advisory Group Technical Committee Donabe
Chair, Management Area Cisco Innovations:
Working Groups: Projects OpenStack API for Nexus
Config, Hybrid, Extensibility, OpenStack Extensions
Futures/FPMOD/OF2.0
Founding Platinum member

Catalyzed initial Open Source
offering
Overlay Working Groups:

NVO3, L2VPN, TRILL, L3VPN, LISP, PWE3
Working Groups:
NETCONF, ALTO, CDNI, XMPP, SDNP,
Open Source Cloud I2AEX
Computing project PCE, FORCES
I2RS – Interface to Routing System
Silicon isn’t fixed anymore…
Unified Access Data Plane (UADP) ASIC
$100M+ R&D Investment 300+ Person-Years
SDN Controllers
SDN Controllers
• Open Daylight
• Cisco Open SDN Controller
• Cisco APIC (Application Policy Infrastructure Controller)
• Cisco APIC-EM (Enterprise Module)
• ….
SDN Controller – Overview
• Four Wheels All Cars

• Steering Wheel
• Accelerator Pedal Different Use Cases
• Brake Pedal
Open Daylight
OpenDaylight
• The biggest networking OSS project by any measure (www.openhub.net):
Floodlight: 93,198 Floodlight: 86 Floodlight: 2,722
RYU:95 RYU:2,783
FD.io: 276,133
FD.io: 90 FD.io: 1,418

OVS:306,888
§ 150+ known deployments by 20+ companies

§ SW / Equipment vendors, SPs, …
§ Networking, entertainment, energy management, …
* = reported to Linux Foundation
What Is OpenDaylight?
• …an open source project formed by industry leaders and others under the
Linux Foundation with the mutual goal of furthering the adoption and innovation
of Software Defined Networking (SDN) through the creation of a common
vendor supported framework.
• Focus: Customers with some programming resources that desire a free,
community-supported SDN controller, especially if focus is on OpenFlow
Platinum Gold Silver
OpenDaylight Architectural Model Hydrogen
• Released February 2014
Helium
• Released October 2014
• 1.87M+ lines of code
• 28 Projects
• 256 Contributors
Lithium
• June 2015
Beryllium
• Feb 2016
Boron
• September 2016
Open Daylight OF Toplogy
Cisco Open SDN Controller (OSC)
Çisco Open SDN Controller (OSC)
• Based on OpenDaylight
• Includes Cisco value-added functions: installation
helpers, log and metrics aggregation, plug-in clustering
and monitoring
• https://cisco.com/go/opensdn
• Focus : Customers with some programming resources
that desire a commercially supported edition of a free,
community-support SDN controller, especially if focus is
on Open Flow.
Cisco Commercial Distribution of OpenDaylight
Open SDN Controller
Re-bases XNC on OpenDaylight Helium Release
Hydrogen Helium Lithium
XNC 1.x Open SDN Controller
Open SDN Controller vs OpenDaylight
Open SDN Controller

Community Support Cisco Supported
OpenContrail DLUX Log
Plugin Aggregation
LISP Flow AAA MD-SAL Metrics
Mapping Aggregation
Group Policy BGP-LS
OVA Distribution
Defense4all Basic
L2 Switch Controller
Precluded Clustering Incremental
OpenDaylight Common Content Cisco
Content Value
VTN Project OVSDB Yang Tools PCEP One Click Install
Secure Network
SNMP4SDN Openflow Monitoring
Bootstrap Infra
Plugin
PacketCable Central Admin
PCMM Service Function
Plug-in Clustering
AD-SAL Chaining
SDNi Sample Apps To be contributed back
to the “open community”
Native Applications
Inventory
Augmented OpenDaylight “Nodes”

user interface
Device vendor
Platform IDs
Series numbers
Native Applications (cont’d)
OpenFlow Manager
OpenFlow topology
visualization
Advanced flow management
Flow based troubleshooting
JSON body preview
Cisco APIC
Cisco ACI: Full Stack SDN in Data Center
Centralized Automation and Fabric Management
ACI = CONTROLLER + POLICY MODEL+

NEXUS 9k Single Point of Management APIC
Without a Single Point of Failure
• Turnkey integrated solution with
security, centralized management,
compliance and scale
• L4-L7 Service Graph
• Automated application centric-policy
model with embedded security
• Simplify provisioning, operating through
relational object-model
• Fully programmable (REST API, Python
bindings)
• Broad and deep ecosystem
APIC Cluster
Distributed, Synchronized, Replicated
Cisco APIC-EM
(APIC-Enterprise Module)
What Is APIC-EM?
• A purpose-built, easy to use SDN controller
• Does NOT require programming experience [but does have REST NBI]
• Does NOT require HW/SW upgrades to take advantage of controller model
• Has specific applications built-in to address common network needs:
Policy Management, QoS Management, Zero-Touch Deployment and iWAN
• Available to SmartNet customers without charge
• Focus: Enterprise Customers with Few to No Programming Resources
that desires a Commercially-supported solution that preserves existing
investment and doesn’t require HW/SW upgrades
APIC-EM - Platform Architecture
APIC-EM Network PnP IWAN Path Trace Network Inventory APIC-EM
Applications Advanced Topology Visualizer Applications
APIC-EM Controller
Northbound REST APIs
Inventory Policy
RBAC Policy Analysis
APIC-EM Manager Programmer
APIC-EM
Services Topology Data Access
Services
IWAN
Network PnP
Services Service Services
Addresses
Scale Out
Grapevine Elastic Service Infrastructure and HA
Requirements
APIC-EM – Functions and Applications
• Network Plug-n-Play – for Zero Touch Deployment

• Network Information Base – Device Inventory
• Network Information Base - Host Inventory
• Topology Visualizer
• Path Visualization Application
• Intelligent WAN
• EasyQoS GUI
(*) GA1 BRKRST-1014 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 62
Network Information Base – Device Inventory
Single Source of Truth
• Real-time network device inventory

and asset service management
• Includes all network devices with an
abstraction for the entire network –
• Full knowledge of network
• Awareness of the overall operational
health of the physical network
• Detailed inventory information for • Inventory service runs in the
easier consumption by controller background to maintain the DB
services and applications accurate
• Allows applications to be device • SNMP traps sent by devices
agnostic during link up/down; APIC-EM
runs discovery on that device (*)
APIC-EM – Device Inventory
Network Information Base – Host Inventory
Single Source of Truth
• Real-time host and end-point

inventory (PCs, Wireless devices,
IP Phones, Printers etc.)
• Detailed information about each
host/end-point –
• Network attachment point for the host
to the network device
• Host Name, IP and Mac-Address
information
• Information collected via CDP,
LLDP and IP Device Tracking DB
• Host Inventory service runs in the lookup
background to maintain the
accuracy of the database – • SNMP Traps used to update host
inventory DB (*)
APIC-EM – Host Inventory
Wireless Host Information
Topology Visualizer
• Auto discovers and maps devices

to a physical topology
• Detailed device level data
• Always up-to-date network
topology
• Layer 2 and 3 topologies on top of
Physical provides granular view for
design planning, simplified • Advanced HTML 5 Javascript
troubleshooting etc. based visualizer that utilizes REST
APIs
• Visualize Device TAGs on top of
the Physical network topology • Highly interactive application
experience
Topology Visualizer – Embedded Device Information
Device Information
Path Visualization
APIC EM Returns A Path Based on a 5 Tuple Input
Path Visualization: Enhanced Application Flow Visibility
Link source
CAPWAP tunnel information
visualization
Accuracy note
(in percentage)
Ingress/Egress
Interface
Path Visualization: Topology View
APIC-EM IWAN App - Application Policy
• Application priority policy

settings
• Path preference
• Drag & Drop business buckets
Site summary
from map view
Deploy End-to-End DSCP-Based Queuing Policies
EasyQoS seamlessly interconnect s all types of
hardware and software queuing models to achieve
consistent and compatible end-to-end treatments
aligned with the expressed business-intent
EM
EasyQoS GUI
Change Application Business-Relevance
Other Considerations
Remember This Inflection Point?
Telephony in 1998
• IP Telephony struggled until we got ‘hybrid engineers’ to translate between the

Circuit Switch ‘Tip & Ring’ and Packet Switch ‘Bits & Bytes’ camps
• Likewise, now, we need the next generation of ‘hybrid engineers’ to translate between
traditional network domain engineers and software/application developers
Business outcomes not technical silo’s
What Skills Would Be Helpful for a
Network Engineer Branching Out?
• Basic Programming constructs
(conditionals, loops, functions/procedures)
• Basic Python / Javascript
• REST / Web Services
• Regular Expression
• XML / XSLT
• Basic SQL
• Basic shell scripting - grep
• #1 - Communicating Effectively with Programmers
Job Roles: Cisco Network Programmability Evolution
Business Application Developer

Business Application
— Network Programmability
Developer
Aware
System Engineer/ Network Programmability

Network Designer Developer
Network Engineer
Development Network
Programmability
Curriculum Designer
Network Programmability
Support Engineer
Engineer
Traditional Networking
Open Infrastructure
Infrastructure
http://www.cisco.com/web/learning/certifications/specialist 80
But I don’t have time….
• Book time to yourself in your calendar
• Map out your learning
• Set realistic achievable goals
• Attend an online or physical class
Where to learn more
Devnet Zone @ Cisco Live
Walk-In Self Paced Labs @ Cisco Live
Recommended CLMEL17 Sessions
• TECRST-2010 : Network Engineer v2.1 – Automating the SDN
Enterprise Campus / WAN – Adam Radford, Wednesday (watch the
recording...)
• BRKACI-2503 : Infrastructure as Code and DevOps for Network
Engineers – Chris Gascoigne Wednesday 2:30pm (watch the recording…)
• BRKCRS-2150 : APIC-EM Deployment and Operations – Adam Radford,
Thursday 8:30am
• BRKSPG-2380 : Goodbye to Manual Configuration : Service Centric
SDN, NFV and Orchestration – Bilal Alam – Thursday 12:50pm
• DEVNET-2037 : APIC-EM API – Adam Radford – Thursday 12pm
https://developer.cisco.com
https://dcloud.cisco.com
What does your day to day look like?
7% Other
14% Traffic Optimisation

43% Other 36%
14% Equipment Upgrade More Time Available for
Business Innovation
18% Configuration 10% Traffic Optimisation
19% Security 14% Equipment Upgrade

8% Configuration
36%
10% Security Total Network Operations
28% Troubleshooting Time Savings
14% Troubleshooting
Current IT* Fast IT

* Source Forrester Commissioned Study BRKRST-1014 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 89
Q&A
Complete Your Online Session Evaluation
Give us your feedback and receive a
Cisco Live 2017 Cap by completing the
overall event evaluation and 5 session
evaluations.
All evaluations can be completed via

the Cisco Live Mobile App.
Caps can be collected Friday 10 March Learn online with Cisco Live!
at Registration. Visit us online after the conference
for full access to session videos and
presentations.
www.CiscoLiveAPAC.com

BRKRST 1014

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BRKRST 1014

Uploaded by

Copyright:

Available Formats

Introduction to Software-Defined

Networking (SDN) and Network

Nathan Holland – Systems Engineer (Cisco)

• Software Defined Networking (SDN) - Defined

ICT Industry 10+ Years

14% Traffic Optimisation

19% Security 14% Equipment Upgrade

Current IT* Fast IT

…impacting the networking industry

…providing new methods to interact with equipment/services via controllers, APIs

…enabling high-scale, rapid network and service provisioning/management

…generating a LOT of ‘buzz’ and attention

…providing a catalyst for traditional Route/Switch engineers to branch-out

…meaning the death of network engineers

…a mandate for all network engineers to become C and Java programmers

…a new attempt at network evolution

Network Function Network Traffic Service

QoS Changes Pre-QOS change – Default Classification

Central Staging Facility

2 Install & Power-on 3 Monitor device

Site-1 Site-2 Site-3 Site(s)

Low Cost Physical Consistent for devices and Greenfield &

1. User uses cloud service to open a ticket on the web

Data Plane (DP)

Control plane learns/computes forwarding decisions

Control plane becomes centralised

A Controller is centralised and separated from the Physical Device,

Well Understood HTTP or HTTPS

Easy to Develop Against

Versioned Response in HTML, JSON / XML

CLI scripting was being extensively used for configuration

The Network Configuration Protocol (NETCONF) is a network management

NETCONF provides mechanisms to install, manipulate, and delete the

YANG is a modular language representing data structures in an XML tree format.

…a Layer 2 communications protocol that gives access to the

Fwd Port 100

10.* Local 200

Perform action in flow

1.3.2 2013-04 Support for controller-initiated connections 38

1.3.3 2013-12 Update with IANA registered TCP port : 6653 40

“Protocols” OpenFlow I2RS PCEP BGP-LS/FS Neutron OMI Puppet NETCONF

Management OMI Puppet NETCONF

Device Operating Systems – Cisco IOS / NX-OS / IOS-XR

Founding Platinum member

Overlay Working Groups:

$100M+ R&D Investment 300+ Person-Years

• Four Wheels All Cars

Floodlight: 93,198 Floodlight: 86 Floodlight: 2,722

FD.io: 90 FD.io: 1,418

§ 150+ known deployments by 20+ companies

Platinum Gold Silver

Hydrogen Helium Lithium

XNC 1.x Open SDN Controller

Open SDN Controller

Augmented OpenDaylight “Nodes”

Advanced flow management

Flow based troubleshooting

JSON body preview

ACI = CONTROLLER + POLICY MODEL+

• Network Plug-n-Play – for Zero Touch Deployment

• Real-time network device inventory

• Real-time host and end-point

Wireless Host Information