Software Defined Networks
By: Thierry Couture, Consulting Systems Architect
There is currently a lot of buzz around OpenFlow and Software Defined Networks (SDN) in the industry. It would be a mistake to think that these are one and the same. The reality is that the current market conversation has loose semantics mixed in with hyperbole and hearsay that hide the simplicity of SDN behind terms like Openstack, Virtual Overlays, Network Function Virtualization, Orchestration, etc. This session will explain the origins of SDN, establish a basic terminology for SDN concepts, and offer a framework to both understand these trends and distill the applicability of SDN through a use case lens.
Ensuring Technical Readiness For Copilot in Microsoft 365
Software Defined Networks
1. Introduction to
Cisco SDN & Open Network Environment"
Thierry Couture
Consulting Systems Architect
dax@cisco.com
GTEC 2013 Government Technology Show
31. Example: Monetize / Simplify / Optimize
S
Client
Site A Site B
$$$
1ms
$
10ms
$
10ms
Daytime = Transactions = Optimize for Latency and Responsiveness = $9@3ms
Nighttime = Inventory Updates = Optimize for high BW and lower cost = $4@40ms
A
P
WAN
57. Cisco ONE Business Drivers
Cloud Video Mobility Data Deluge
How to
Harness
Network
Value?
How to Drive
Business
Agility?
How to Drive
Operational
Simplicity?
But is the Network Ready?
58. Cisco Open Network Environment
Bringing the Network to Applications
Software
Defined
Networks
Open
Flow
59. Where we started a while ago…
Network
Applications
Services
Orchestration
Analytics
Network Intelligence,
GuidancePolicy & Intent
Programmability Statistics, States,
Events
Program for Optimized Experience
Harvest Network Intelligence
60. Cisco ONE
A Comprehensive Approach
SDN
Open APIs
Open Cloud
Virtualization (NFV)
Industry-Defined
Bidirectional Interaction
Real-time Analytics
Orchestration
Automation
Cisco Innovative Extensions
+
61. Cisco Approach: Flexibility to Choose
• Match the model with the use case
• Deploy hybrid for optimal business results
Multiple Approaches to SDN
Cisco ONE Enables All of Them
Controller
OpenFlow
Device
Device with
OpenFlow
Device
Other
Agents
Apps
APIs
Network
Apps
Virtual Overlays
Network
Physical
and
Virtual
Apps
62. Control Plane and Data Plane Separation Strategy
Open Daylight ONE Controller
Open Flow ONE PK
Open Source Cisco
63. Data and Control Plane Abstraction Build on
Known Mechanisms and Features
RPNetFlow
QoS
PBR
EVC
ABF
IP
MPLS
TE
Route
Science
PfR
Segment
Routing
CBTS
PBTS
64. Network Function Virtualization (NFV)
Many familiar network functions are already virtualized on UCS!
LAN Switch
(VEM/
Nexus1K)
Security
Gateway
(VSG)
Identity
Services
(vISE)
Adaptive
Security
(vASA)
WAN
Acceleration
(vWAAS)
Mobility
Services
(vMSE)
Wireless LAN
Control
(vWLC)
Route
Reflector
(VRR)
Video
Cache
Network
Analytics
(vDNA)
Network
Analysis
(vNAM)
Network
Management
(PRIME NCS)
CSR
(vCE/vPE)
Load
Balancers
vEPC
(M2M)
Cisco Unified Computing System (UCS)
72. Network Monitoring – Existing Challenges
• Problem
– SPAN sessions have limited scalability and are currently not ‘sharable’
– Many teams require insight into DC flows for analytics
• Solution
– Multi-SPAN / Packet Capture solution that uses centralized flow control
– Single Pane of Glass into Data Center traffic
– Packet capturing as a service
– Scalability: many source to many destinations
– Adjustable to changing DC Network Architectures
72
73. Solution Architecture – Overview
• A Software Defined Networking (SDN) solution
• SPAN sessions are aggregated on Nexus 6000 & 3000
switches, via a combination of network taps and SPAN
sessions
• Nexus switches are managed by an Cisco ONE Openflow
Controller
• Controller directs the flow of SPAN traffic from ingress ports to
egress ports to reach their target traffic analysis collectors
• End result is a consolidation of traffic analysis collectors,
freeing up space in the data center pods, and a centralized
management of SPAN sessions
73