Segment Routing

Segment Routing
Traffic Engineering
Diptanshu Singh
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
Distributed or Centralized computing ?
Policy Single-Domain Multi-Domain
Reachability IGP’s Centralized
Low Latency Distributed or Centralized Centralized
Disjoin from same node Distributed or Centralized Centralized
Disjoin from different node Centralized Centralized
Avoiding resources Distributed or Centralized Centralized
Capacity optimization Centralized Low Priority
Others… TBD Centralized

High level Architecture
• SR PCE have multi-domain topology view
--feed via BGP-LS from multiple domains
• Stateful PCE with native SRTE algorithms.
PCE controller • PCEP Messages:
• PCEP Request (PCC -> PCE)
LSP-DB TED • PCEP Reply (PCE -> PCC)
• PCC Report (PCC -> PCE)
• PCE Update (PCE -> PCC)
• PCE Initiate (PCE -> PCC)
PCEP
BGP-LS
BGP-LS
Router
PCC Area Y Router Area X Router Area Z Router
SR Basics: Binding Segment
• Binding Segment represents a tunnel at SR
• The Binding Segment is a local segment
– Has local significance
• A Binding-Segment ID identifies a SRTE Policy
– Each SRTE Policy is associated 1-for-1 with a Binding-SID
• Packets received with Binding-SID as top label are steered
into the SRTE Policy associated with the Binding-SID
– Binding-SID label is popped, SRTE Policy’s SID list is pushed
SR Basics: Binding Segment
• Binding-SID use-case examples:
– Label stack “compression”: nesting and stitching SRTE Policies
– BGP SRTE Dynamic: use local Binding-SID(later)
PCEP Request
Could you provide me the ERO 2 PCE controller
for AC1?
3
PCC Report
PCEP Reply - 17002,17003,17004
- 17001,4001 1 - Binding SID 4001
- Instead of 17001,17002,17003,17004
WAN
DC
TOR WAN
AC1
Headend
IP 4001
IP 17004
Unicast-SID 17002 17003 Unicast-SID 17003 IP
Unicast-SID 17001 IP 17004 Unicast-SID 17004
IP 4001 17001
IP 17004 17003 17002
Segment Routing Traffic Engineering:
• On Demand Next Hop
• BGP SR-TE dynamic
• HA with PCE SR controller
On demand SR Next Hop
Service Orchestrator Hint:
1. PCE collect topology and SID via BGP
LS
PCE controller 2. Including ip address and SID
BGP Route Reflector
BGP Link State
Unicast-SID 17001 Unicast-SID 17003

Unicast-SID 16001 Anycast-SID 18001 Anycast-SID 18002 Unicast-SID 16001
ToR1 ABR1 ABR3 AC1
DC WAN Access
ISIS SR2 ISIS SR1
ISIS SR3
ToR2 SRGB 16000-16999 ABR2 SRGB 17k-18k ABR4 AC2
SRGB 16000-16999
Unicast-SID 16002 Unicast-SID 17002 Unicast-SID 17004 Unicast-SID 16002

Anycast-SID 18001 Anycast-SID 18002
1. PCE collect topology and SID via BGP LS
2. Service Orchestrator to configure service
PCE controller
XML YANG:
BGP Route Reflector XML YANG:
- PW-123 from ToR1 to AC1 - PW-123 from AC1 to ToR1
Unicast SID 17001 Unicast SID 17003

Unicast-SID 16001 Anycast SID 18001 Anycast SID 18002 Unicast-SID 16001
ToR1 ABR1 ABR3 AC1
DC WAN Access
ToR2 ABR2 ABR4 AC2
Unicast-SID 16002 Unicast SID 17002 Unicast SID 17004 Unicast-SID 16002
Anycast SID 18001 Anycast SID 18002
2. NMS/OSS to configure service
PCE controller 3. ToR1 check if he has LSP to AC1
Do I have LSP Yes -> use it
No -> next slide
to AC1 ?
BGP Route Reflector

ToR1 ABR1 ABR3 AC1
DC WAN Access
ToR2 ABR2 ABR4 AC2
PCEP request 4. ToR1 request LSP to PCE
- Could you provide me the
ERO to reach AC1 ? BGP Route Reflector
1 2 PCEP reply
- ERO is: 18001,18002,16001
3
ToR1 ABR1 ABR3 AC1
DC WAN Access
ToR2 ABR2 ABR4 AC2
4. ToR1 request LSP to PCE
5. ToR1 report service state to orchestrator
XML YANG notification:
BGP Route Reflector
- PW-123 is UP
Unicast-SID 17001 Unicast-SID 17003

Unicast-SID 16001 Anycast-SID 18001 Anycast-SID 18002 Unicast-SID 16001
Ethernet Etherne
ToR1 ABR1 ABR3 AC1
Ethernet PW
DC
16001 18002 18001 Ethernet
WAN
PW 16001 18002 Ethernet PW 16001
Access
ToR2 ABR2 ABR4 AC2
Unicast-SID 16002 Unicast-SID 17002 Unicast-SID 17004 Unicast-SID 16002

Anycast-SID 18001 Anycast-SID 18002
ODN with policy
PCE controller
XML YANG: BGP Route Reflector XML YANG:

- Policy: Disjoin GID 123 - Policy: Disjoin GID 123

ToR1 ABR1 ABR3 AC1
DC WAN Access
ToR2 ABR2 ABR4 AC2
ODN with policy
PCE controller 3. ToR1 and ToR2 check if they has LSP to
PCEP request
AC1 and AC2 respectively.
- Could you provide me the ERO
4. ToR1 and ToR2 request LSP to PCE
to reach AC1 ?
- Policies are G-ID 123 BGP Route Reflector
PCEP request
- Could you provide me the ERO
to reach AC2 ?
1
- Policies are G-ID 123
2 Unicast SID 17001 Unicast SID 17003

ToR1 ABR1 ABR3 AC1
DC WAN Access
ToR2 ABR2 ABR4 AC2
ODN with policy (Cont)
PCE controller 3. ToR1 and ToR2 check if they has LSP to
AC1 and AC2 respectively.
4. ToR1 and ToR2 request LSP to PCE
3
BGP Route Reflector 5. PCE sees the same Disjoint ID and
4 computes two Disjoint paths
PCEP reply
- ERO is: 17001,17003,16001
PCEP reply
- ERO is: 17002,17004,16002
ToR1 ABR1 ABR3 AC1

Ethernet PW 16001 17003 17001 Ethernet PW 16001 17003 Ethernet PW 16001
DC WAN Access
ToR2 ABR2 ABR4 AC2
Ethernet PW 16002 17004 17002 Ethernet PW 16002 17004 Ethernet PW 16002
On demand steering for BGP services
Technical name: BGP SR-TE dynamic Hint:
1. Isolated domains with no redistribution.
2. CPE send BGP update for prefix X and
PCE controller add LL community ex: 100:777
BGP Route Reflector

BGP-LS
BGP-LS

Unicast-SID 16001 Anycast SID 18001 BGP-LS Anycast SID 18002 Unicast-SID 16001
CPE1 ToR1 ABR1 ABR3 AC1 CPE2
DC WAN Access
ToR2 ABR2 ABR4 AC2
1. Isolated domains with no redistribution.
PCE controller add LL community ex: 100:777
BGP Route Reflector
NLRI: 1.1.1.1/32
Unicast SID 17001 Unicast SID 17003 Community:
Unicast-SID 16001 Anycast SID 18001 Anycast SID 18002 Unicast-SID 16001 100:777
DC WAN Access
ToR2 ABR2 ABR4 AC2
add LL community
PCE controller 2. AC1 PE announce VPN prefix X with LL
community
BGP Route Reflector
NLRI: 1.1.1.1/32
Community: 100:777

DC WAN Access
ToR2 ABR2 ABR4 AC2
add LL community
PCEP request PCE controller 2. AC1 PE announce VPN prefix X with LL
- Could you provide me the ERO community
to reach AC1 ? 3. On demand Next Hop LL to PCE controller
- Policy is LL BGP Route Reflector 4. Install explicit path for prefix X in VRF
1
PCEP reply
- ERO is: 17001,17003,16001
2
CPE1 ToR1 3 ABR1 ABR3 AC1 CPE2
DC WAN Access
ToR2 ABR2 ABR4 AC2
• TE installs SRTE Policy in 1.1.1.1/32; NH: AC1
BGP
FIB: Received VPN label: L_VPN
Community 100:777
– Binding-SID (e.g. 24006): push Binding Label: 24006
{Label 17001, Label
17003,Label 16001} SRTE Policy to AC1:
TE
SID List {17001,17003,16001},OIF 3
• TE provides the Binding-SID Binding Label: 24006
of the SRTE Policy to BGP
Local label: 24006 out label: POP

FIB OIF: SRTE; Label stack {17001 17003
16001}
• RIB installs in FIB: 1.1.1.1/32; NH: AC1
BGP
Received VPN label: L_VPN
– 1.1.1.1/32 via 24006 Community 100:777
– Push VPN label and steer in Binding Label: 24006
SRTE Policy
SRTE Policy to AC1:
• TE installs SRTE in FIB
TE
SID List {17001,17003,16001},OIF 3
Binding Label: 24006
• BGP, RIB and FIB aware of
BSID 1.1.1.1/32; recursion-via-label
label L_VPN, NH via 24006
FIB
Local label: 24006 out label: POP
OIF: SRTE; Label stack {17001 17003
16001}
PCE HA 1. Service Provisioned via Overlay
RR,Orchestrator
2. Request via PCEP to PCE primary with TE
policy
3. PCE replies with ERO 17001,17003,16001
5
4. ToR1 Reports to PCE Primary and
PCE1 Primary PCE2 Secondary Secondary via PCC Report
5. Primary PCE fails
6. ToR1 waits for some time
7. ToR1 Reports PCE2 of becoming master
2 3
4
7
BGP Route Reflector

1

6: wait for
some timer
DC WAN Access
ToR2 ABR2 ABR4 AC2
ODN HA model
• SR-PCE not to be considered as a Single “god” box
• SR-PCE is closer to RR
• Different TOR’s can use different pairs of SR-PCE
• SR PCE preference can be either based on proximity or service
Service Orchestrator

PCEP PCE BGP LS PCE PCEP

RR RR
DC WAN Access
PCE PCE
ToR2 ABR2 ABR4 AC2
RR RR
Thank you.
References
• http://www.segment-routing.net/
• Current IETF Drafts for SR:
• http://www.segment-routing.net/home/ietf
• PCEP Extensions for Segment Routing
• https://tools.ietf.org/html/draft-ietf-pce-segment-routing-06
• Binding SID
• https://tools.ietf.org/html/draft-sivabalan-pce-binding-label-sid-00
• Anycast Segments in MPLS based Segment Routing
• https://tools.ietf.org/html/draft-psarkar-spring-mpls-anycast-segments-01
• BGP Link-State extensions for Segment Routing
https://tools.ietf.org/html/draft-gredler-idr-bgp-ls-segment-routing-ext-01

Segment Routing - Traffic Engineering

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

Segment Routing - Traffic Engineering

Uploaded by

Copyright:

Available Formats

Reachability IGP’s Centralized

Low Latency Distributed or Centralized Centralized

Disjoin from same node Distributed or Centralized Centralized

Disjoin from different node Centralized Centralized

Avoiding resources Distributed or Centralized Centralized

Capacity optimization Centralized Low Priority

Others… TBD Centralized

BGP Route Reflector

BGP Link State

Unicast-SID 17001 Unicast-SID 17003

ToR1 ABR1 ABR3 AC1

Unicast-SID 16002 Unicast-SID 17002 Unicast-SID 17004 Unicast-SID 16002

Unicast SID 17001 Unicast SID 17003

ToR1 ABR1 ABR3 AC1

Unicast SID 17001 Unicast SID 17003

ToR1 ABR1 ABR3 AC1

Unicast-SID 17001 Unicast-SID 17003

Unicast-SID 16002 Unicast-SID 17002 Unicast-SID 17004 Unicast-SID 16002

XML YANG: BGP Route Reflector XML YANG:

Unicast SID 17001 Unicast SID 17003

ToR1 ABR1 ABR3 AC1

2 Unicast SID 17001 Unicast SID 17003

ToR1 ABR1 ABR3 AC1

ToR1 ABR1 ABR3 AC1

BGP Route Reflector

Unicast SID 17001 Unicast SID 17003

CPE1 ToR1 ABR1 ABR3 AC1 CPE2

BGP Route Reflector

CPE1 ToR1 ABR1 ABR3 AC1 CPE2

BGP Route Reflector

Unicast SID 17001 Unicast SID 17003

CPE1 ToR1 ABR1 ABR3 AC1 CPE2

CPE1 ToR1 3 ABR1 ABR3 AC1 CPE2

Local label: 24006 out label: POP

BGP Route Reflector

CPE1 ToR1 ABR1 ABR3 AC1 CPE2

Unicast SID 17001 Unicast SID 17003

PCEP PCE BGP LS PCE PCEP

You might also like