Transcript Open SDN in Metro P-OTS Networks

Open SDN in Metro P-OTS Networks
Sten Nordell
CTO
Metro Business Group
2015-10-15
1 | © 2015 Infinera
The New Network for a Software-driven World
Old Model
Firewall
SBC
B-RAS
Layered
MPLS PE
Network
L2/3 Packet
Layer 1 OTN
Layer 0 WDM
2 | © 2015 Infinera
New Simplified Model
Network Functions
Services
Virtualized into Cloud
API – SDN Control
Intelligent
Transport
Transport Functions
Scale, Convergence,
Software-Controlled
Dynamic Intelligent BW
Network Efficiency
Intelligent Automation
App-Driven Performance
The evolution of Native Packet Optical in the Metro
Native Packet
Optical 1.0
Layer 2
Layer 1
3 | © 2015 Infinera
Native Packet
Optical 2.0
MPLS-TP
CE2.0
Ethernet
OTN
Native Packet
Optical 3.0
Metro P-OTS SDN 2.0 key characteristics
 Open SDN architecture
• Open Source Software
• Open platform with added value
• Feature velocity driven
• OpenFlow based
 Open APIs providing interoperability between
transport layers
 Built for Metro P-OTS networks
• Each switch instance controlled individually
• Node level for infrastructure
 Scalable and distributed SDN controller
architecture
4 | © 2015 Infinera
SDN
What applications are we focusing on?
 Service oriented transport SDN apps
• Bandwidth
• On demand
• Flexible
• Calendaring
• Instant
 Service chaining
 Multi-layer coordination
 L0 to L3 applications and services
 Open APIs for network programmability
5 | © 2015 Infinera
Metro P-OTS SDN 2.0 Overview
UI
TNM
SDN Web app
Control Layer
REST APIs
vRouter
Bandwidth
Calendaring
Network
Tap
Statistics
MEF
Connectivity
Host Discovery
Simple
DHCP Server
Policers
Controller
Hardware
OpenFlow 1.3 (+Extensions)
EMXP
EMXP
EMXP
EMXP
6 | © 2015 Infinera
EMXP
Application examples
7 | © 2015 Infinera
Flexible bandwidth
What:
 Adjust services’ bandwidth
levels freely and live
Why:
 Allows the operator to
dynamically adjust
bandwidth based on
customers requests
8 | © 2015 Infinera
CE A
E-LINE
CE B
EMXP
EMXP
Video
Display
Video
Source
EMXP
Bandwidth Calendaring
What:
Bandwidth
Calendar for
Customer X
Network wide
Utilization
 Define bandwidth limits
based on date and time
100%
100%
50%
50%
Threshold
0%
0%
Time
00:00
Why:
 Define services providing
more bandwidth when
utilization is low (off-hours)
 Define services only used at
scheduled intervals
9 | © 2015 Infinera
CE A
06:00
12:00
18:00
Time
23:00
00:00
06:00
E-LINE
12:00
18:00
CE B
EMXP
EMXP
EMXP
23:00
Optimize services
What:
Why:
 Possibility to optimize the route of
 Provides freed-up resources and
existing services
improved services
 Avoid sub-optimal routing as a
result of changed network
topology
Better path
CE
EDU
EMXP
EMXP
EMXP
Existing path
10 | © 2015 Infinera
EDU
CE
Instant services scenario
What:
 Operator provides a number of
ports for connectivity between
sites
Why:
 Customer can choose to connect
or disconnect network ports
 Customer get automated service
realization by connecting endpoint devices
11 | © 2015 Infinera
E-LINE
CE A
CE B
EMXP
EMXP
EMXP
EDU / Host mobility
Why:
What:
 Improving operational efficiency
 Services follow the customer –
 Enables services definitions to be
bound up with a customer rather
than to a physical network location
CE
e.g. when moving its offices 
increases customer satisfaction
EDU
EMXP
EMXP
EMXP
EDU
CE
12 | © 2015 Infinera
EDU
CE
Automatic Restoration
What:
Why:
 Basic level of protection provided
 Automated service restoration in
without additional configuration
of rings or linear protection
CE
case of faults/fiber break
EDU
EMXP
EMXP
EMXP
13 | © 2015 Infinera
EDU
CE
Redirect / Reroute services
Why
What:
 Tell network to re-route services
 Allows operator to remove traffic
away from a network element
using a ”make-before-break”
approach
• Reduces network impact of a
planned upgrade or replacement
from a given element using a
hitless approach
Alternative path
CE
EDU
EMXP
EMXP
EMXP
Upgrade target
14 | © 2015 Infinera
EDU
CE
Virtualization
SDN based vRouter in Metro P-OTS
15 | © 2015 Infinera
Goal
Physical topology
EMXP
EMXP
EMXP
Router topology
IP Traffic
IP Traffic
vRouter
16 | © 2015 Infinera
vRouter – How
OSPF
 Picks up control plane traffic:
ISIS
• From each router neighbor
• For example OSPF packets
Routing
Table
vRouter
 Passes the control packet to routing
engine:
• And sends back packets to edges
Controller
Forwarding Entries
OSPF PDUs
OSPF PDUs
EMXP
EMXP
17 | © 2015 Infinera
Data flow
EMXP
 Routing engine computes routing
table
• Which is turned into forwarding
rules
vRouter – Why – Mobile backhaul
 Without vRouter:
• All traffic goes to the core router
• Traffic between edge routers
• Even traffic that could go between ports
in the switch
 With vRouter:
EMXP
Link
for protection
EMXP
18 | © 2015 Infinera
EMXP
• Enables effective routing between routers
• Traffic is no longer routed via core
router
• Limited configuration needed for the
vRouter.
• IS-IS would require no configuration
• Any change in router configuration
reflected in vRouter
vRouter – Why – Smart aggregation
 Without vRouter:
• Each client interface adds a port specific vlan
• Router has one vlan interface per client interface on
port aggregation device
• All traffic goes to router
• Even traffic that could go between ports in switch
• Event traffic that could go between aggregation
switches
VLAN
Flows
1
CE
EMXP
2
CE
19 | © 2015 Infinera
 With vRouter:
3
CE
CE
CE
CE
• One vRouter is created over the aggregation switches
in the network
• All metro flows are handled efficiently
• Port to port flows
• Flows between aggregation switches
• Same operational model for vRouter as in routers
• L2 service can still be provided in parallel
vRouter for Metro P-OTS SDN 2.0 on existing EMXPs
Supported on existing EMXP
family and PT-Fabric
MPLS-TP over Ethernet
Native Ethernet
Packet over OTU
L2 services
 E-Line
 E-LAN
 E-Tree
 E-Access
MPLS
(LSRs LERs)
IP Router
Ethernet
L3 services
 VPN
 Provider Edge
 Service chaining
(SVLAN, ERPS, …)
Mobile SGW
OTN
(switching grooming)
Core network
agnostic
λ
ROADM
20 | © 2015 Infinera
WDM foundation
- Flexible Optical
Networks
L3 Services
 Internet
 L3VPN
 IPTV
Mobile services
 3G
 LTE
Summary Open SDN in Metro P-OTS Networks
 Open SDN architecture
• OpenFlow based Native Packet Optical
• Open APIs for network programmability
 Applications oriented for metro transport services
•
•
•
•
Bandwidth on demand
Service chaining
Multi-layer coordination
Supporting Layer 0 to Layer 3 services
21 | © 2015 Infinera
Thank you
22 | © 2015 Infinera