3. Network Bandwidth
demand in SP’s
Network 1 1.66 2.76 4.57 7.59 12.60 20.92 34.73 57.66 95.71
Compute 1 1.50 2.25 3.38 5.06 7.59 1.139 1.709 2.563 38.44
Year 1 Year 2 Year 3 Year 4 Year 5 Year 6 Year 7 Year 8 Year 9 Year 10
http://www.ieee802.org/3/ad_hoc/bwa/BWA_Report.pdf
Compute demand
double every 24
months
Network demand
double every 18
months
4. • Bigger routers:
• 100G
• Multi-Chassis
• Hardware bandwidth double every 3-4 years
• More routers:
• Limited amount of router per domain
• Resulting in insertion of additional domain’s
• Example: MAN between WAN, DC and
Access
• Seamless services: DC, WAN,
MAN, Aggregation, Access
Impact on network design
Access
Access
DC
DC
MAN WAN
NY region
5. METRO architecture changes
P P
PE PE
P P
Leaf
CDN
PE PEAccess
WAN WAN
Man Fabric
DC
DCI DCI
Leaf Leaf Leaf
NfV
DC
Access
Access Access
6. MAN fabric & traffic flows
• CLOS architecture (2, 3 or 4 layers)
• 100G
• Large ECMP
• Heavy use of CDN
To reduce North-South traffic (between
Access domain’s and WAN domains)
Increasing East/Weast traffic (between DC’s
and Access’s domains)
• Still need for end-end reachability.
• Still need to engineer traffic end-end.
P P
Leaf
CDN
PE PE
WAN
DC
DCI DCI
Leaf Leaf Leaf
NfV
DC
Access Access
East-West
North-South
7. Why Traffic Engineering ?
• High bandwidth paths
• Low Latency paths
• Disjoint paths
• Avoid resources
o avoid low bandwidth links
o avoid high utilized links
• Optimize Network Capacity
• Ad-hoc
o Calendaring
8. Distributed or Centralized computing ?
Policy Single-Domain Multi-Domain
Reachability IGP’s Centralized
Low Latency Distributed or Centralized Centralized
Disjoint from same node Distributed or Centralized Centralized
Disjoint from different node Centralized Centralized
Avoiding resources Distributed or Centralized Centralized
Capacity optimization Centralized Low Priority
Others… TBD Centralized
9. • On Demand Next Hop
• BGP SR-TE dynamic
• HA with IOS-XR PCE SR controller
Segment Routing Traffic Engineering:
Keep it simple via innovation…
10. DC WAN Access
Unicast-SID 17001
Anycast-SID 18001 Unicast-SID 16001
BGP Route Reflector
Tail-f NSO controller
Unicast-SID 17002
Anycast-SID 18001
Unicast-SID 17003
Anycast-SID 18002
Unicast-SID 17004
Anycast-SID 18002
ToR1
ToR2
ABR1
ABR2
ABR3
ABR4
AC1
Unicast-SID 16002
Unicast-SID 16001
Unicast-SID 16002
PCE controller
AC2
BGP Link State
Hint:
1. PCE collect topology and SID via BGP LS
On demand SR Next Hop
11. XML YANG:
- PW-123 from ToR1 to AC1
Hint:
1. PCE collect topology and SID via BGP LS
2. NSO to configure service
DC WAN Access
Unicast SID 17001
Anycast SID 18001 Unicast-SID 16001
BGP Route Reflector
Tail-f NSO controller
Unicast SID 17002
Anycast SID 18001
Unicast SID 17003
Anycast SID 18002
Unicast SID 17004
Anycast SID 18002
ToR1
ToR2
ABR1
ABR2
ABR3
ABR4
AC1
Unicast-SID 16002
Unicast-SID 16001
Unicast-SID 16002
PCE controller
AC2
XML YANG:
- PW-123 from AC1 to ToR1
On demand SR Next Hop
12. DC WAN Access
Unicast SID 17001
Anycast SID 18001 Unicast-SID 16001
BGP Route Reflector
Tail-f NSO controller
Unicast SID 17002
Anycast SID 18001
Unicast SID 17003
Anycast SID 18002
Unicast SID 17004
Anycast SID 18002
ToR1
ToR2
ABR1
ABR2
ABR3
ABR4
AC1
Unicast-SID 16002
Unicast-SID 16001
Unicast-SID 16002
PCE controller
AC2
Hint:
1. PCE collect topology and SID via BGP LS
2. NSO to configure service
3. ToR1 check if he has LSP to AC1
Yes -> use it
No -> next slide
Do I have LSP
to AC1 ?
On demand SR Next Hop
13. DC WAN Access
Unicast SID 17001
Anycast SID 18001 Unicast-SID 16001
BGP Route Reflector
Tail-f NSO controller
Unicast SID 17002
Anycast SID 18001
Unicast SID 17003
Anycast SID 18002
Unicast SID 17004
Anycast SID 18002
ToR1
ToR2
ABR1
ABR2
ABR3
ABR4
AC1
Unicast-SID 16002
Unicast-SID 16001
Unicast-SID 16002
PCE controller
AC2
Hint:
1. PCE collect topology and SID via BGP LS
2. NSO to configure service
3. ToR1 check if he has LSP to AC1
4. ToR1 request LSP to PCEPCEP request
- Could you provide me the
ERO to reach AC1 ?
PCEP reply
- ERO is: 18001,18002,16001
1 2
3
On demand SR Next Hop
14. Hint:
1. PCE collect topology and SID via BGP LS
2. NSO to configure service
3. ToR1 check if he has LSP to AC1
4. ToR1 request LSP to PCE
5. ToR1 report service state to NSO
DC WAN Access
Unicast-SID 17001
Anycast-SID 18001 Unicast-SID 16001
BGP Route Reflector
Tail-f NSO controller
Unicast-SID 17002
Anycast-SID 18001
Unicast-SID 17003
Anycast-SID 18002
Unicast-SID 17004
Anycast-SID 18002
ToR1
ToR2
ABR1
ABR2
ABR3
ABR4
AC1
Unicast-SID 16002
Unicast-SID 16001
Unicast-SID 16002
PCE controller
AC2
XML YANG notification:
- PW-123 is UP
On demand SR Next Hop
Ethernet PW 16001 18002 18001 Ethernet PW 16001 18002 Ethernet PW 16001
Ethernet
Etherne
15. XML YANG:
- PW-123 from ToR1 to AC1
- Policy: Low Latency
Hint:
1. PCE collect topology and SID via BGP LS
2. NSO to configure service
DC WAN Access
Unicast SID 17001
Anycast SID 18001 Unicast-SID 16001
BGP Route Reflector
Tail-f NSO controller
Unicast SID 17002
Anycast SID 18001
Unicast SID 17003
Anycast SID 18002
Unicast SID 17004
Anycast SID 18002
ToR1
ToR2
ABR1
ABR2
ABR3
ABR4
AC1
Unicast-SID 16002
Unicast-SID 16001
Unicast-SID 16002
PCE controller
AC2
XML YANG:
- PW-123 from AC1 to ToR1
- Policy: Low Latency
ODN with policy
16. DC WAN Access
Unicast SID 17001
Anycast SID 18001 Unicast-SID 16001
BGP Route Reflector
Tail-f NSO controller
Unicast SID 17002
Anycast SID 18001
Unicast SID 17003
Anycast SID 18002
Unicast SID 17004
Anycast SID 18002
ToR1
ToR2
ABR1
ABR2
ABR3
ABR4
AC1
Unicast-SID 16002
Unicast-SID 16001
Unicast-SID 16002
PCE controller
AC2
Hint:
1. PCE collect topology and SID via BGP LS
2. NSO to configure service
3. ToR1 check if he has LSP to AC1
4. ToR1 request LSP to PCE
PCEP request
- Could you provide me the ERO
to reach AC1 ?
- Policies are Low Latency
PCEP reply
- ERO is: 17001,17003,16001
1 2
3
ODN with policy
17. Hint:
1. CPE send BGP update for prefix X and
add LL community ex: 100:333
NLRI: X
Community: LL
Technical name: BGP SR-TE dynamic
DC WAN Access
Unicast SID 17001
Anycast SID 18001 Unicast-SID 16001
Tail-f NSO controller
Unicast SID 17002
Anycast SID 18001
Unicast SID 17003
Anycast SID 18002
Unicast SID 17004
Anycast SID 18002
ToR1
ToR2
ABR1
ABR2
ABR3
ABR4
AC1
Unicast-SID 16002
Unicast-SID 16001
Unicast-SID 16002
PCE controller
AC2
CPE2
BGP Route Reflector
CPE1
On demand steering for BGP services
L3VPN
18. L3VPN
Hint:
1. CPE send BGP update for prefix X and
add LL community
2. AC1 PE announce VPN prefix X with LL
community
Technical name: BGP SR-TE dynamic
DC WAN Access
Unicast SID 17001
Anycast SID 18001 Unicast-SID 16001
Tail-f NSO controller
Unicast SID 17002
Anycast SID 18001
Unicast SID 17003
Anycast SID 18002
Unicast SID 17004
Anycast SID 18002
ToR1
ToR2
ABR1
ABR2
ABR3
ABR4
AC1
Unicast-SID 16002
Unicast-SID 16001
Unicast-SID 16002
PCE controller
AC2
CPE2
BGP Route Reflector
NLRI: VPN_X
Community: LL
CPE1
On demand steering for BGP services
19. L3VPN
Hint:
1. CPE send BGP update for prefix X and
add LL community
2. AC1 PE announce VPN prefix X with LL
community
3. On demand Next Hop LL to PCE controller
4. Install explicit path for prefix X in VRF
green
Technical name: BGP SR-TE dynamic
DC WAN Access
Unicast SID 17001
Anycast SID 18001 Unicast-SID 16001
Tail-f NSO controller
Unicast SID 17002
Anycast SID 18001
Unicast SID 17003
Anycast SID 18002
Unicast SID 17004
Anycast SID 18002
ToR1
ToR2
ABR1
ABR2
ABR3
ABR4
AC1
Unicast-SID 16002
Unicast-SID 16001
Unicast-SID 16002
PCE controller
AC2
CPE2
BGP Route Reflector
CPE1
PCEP request
- Could you provide me the ERO
to reach AC1 ?
- Policy is Low Latency
PCEP reply
- ERO is: 17001,17003,16001
1
2
3
On demand steering for BGP services
20. ODN HA model
Hint:
1. Collect topology and SID via BGP LS
Hint:
• NSO and provisioning centralized and part
of NMS/OSS
• PCE and RR function could be distributed
• Scale sessions
• Full HA
• BGP and PCE are Statefull: Client and
Controller states are always synchronized.
DC WAN Access
Unicast SID 17001
Anycast SID 18001 Unicast-SID 16001
Unicast SID 17002
Anycast SID 18001
Unicast SID 17003
Anycast SID 18002
Unicast SID 17004
Anycast SID 18002
ToR1
ToR2
ABR1
ABR2
ABR3
ABR4
AC1
Unicast-SID 16002
Unicast-SID 16001
Unicast-SID 16002
AC2
CPE2CPE1
Tail-f NSO controller
PCE
RR
PCE
RR
PCE
RR
PCE
RR
Tail-f NSO controller
PCE
BGP LS
21. Application Engineered Routing
Definition
Applications express
requirements –
bandwidth, latency,
SLAs
SDN controllers are capable
of collecting data from the
network – topology, link
states, link utilization, …
Applications are mapped to a
path defined by a list of
segments
The network only maintains segments
No application state
Segment
Routing
(SW upgrade)
SDN
Controller
Applications
1
2
3
22. VF
App
App
ToR Leaf Spine P
PE
PE
DC WAN
PE
Cloud
Orchestrator
PCE controller
Service Provisioing
Classify
Application flow
and push SR
segment list
1
Top segment
provides ECMP-
path to selected
DCI
2
Next segments implement
WAN Policy:
• Capacity
• Latency
• Avoidance
• Disjointness
And select Egress BR’s
3
DCI
Last segment
selects egress
peer
5
Provide automated 50ms
protection in case of failure
4
Step by Step
deployment
Lower OPEX
One system, Simple,
Scalable
Focus on main value:
The application
End-end cross domain
solution
Application Engineered Routing
23. Label-Switching control points
ToR
NIC
VM VM
VM VM
Match flow
Set Labels
ToR
S-NIC
VM VM
VM VM
Match flow
Set Labels
ToR
NIC
VM VM
VM VM
Match flow
Set Labels
ToR
NIC
VM VM
VM VM
Match flow
Set Labels
VF
XRv
Network Smart-NIC Virtual Forwarder,
Kernel or Container
NfV, vR