BRKRST-2124-Introduction To Segment Routing PDF

#CLUS
Introduction to
Segment Routing
Vinit Jain
+ Technical Leader, Services
++ { CCIE# 22854 }
++ { Twitter - @vinugenie }
BRKRST-2124
#CLUS
Agenda
• Introduction
• Technology Overview
• SRGB
• LDP to SR Migration
• Control Plane & Data Plane
• Traffic Protection
• Traffic Engineering
#CLUS BRKRST-2124 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 3
Cisco Webex Teams
Questions?
Use Cisco Webex Teams (formerly Cisco Spark)
to chat with the speaker after the session
How
1 Find this session in the Cisco Events App
2 Click “Join the Discussion”
3 Install Webex Teams or go directly to the team space
4 Enter messages/questions in the team space
Webex Teams will be moderated cs.co/ciscolivebot#BRKRST-2124

by the speaker until June 18, 2018.
SP Disruption: Complexity vs. Value
Application / Service /
Customization
OSI Reference Revenues, Stickiness
Model Traditional SP Cloud Scale SP

Application Complexity
Presentation
Value
Session
Transport
Network
Data-Link The complexity should
Physical Complexity be where the ROI is best
Complex Network
Infrastructure Simplification
and Convergence Areas
Delayering Unified Infrastructure Horizontal Integration

IP Data Access
ATM/Ethernet SDH replacement Aggregation
SDH/OTN Video Edge
WDM Fixed Mobile Core and DC
Transformation
SDN Driven Automation and Virtualization

IP Fixed Mobile End to End IP
WDM Data Video Circuit Segment Routing
Challenges of Todays Service Creation
Limited Cross-domain Automation
Legacy Central Office
Metro Network Domain Core Network Domain Data Center Domain
L2VPN L3VPN VXLAN VNF VNF
Aggregation
Ethernet MPLS IP
Access
Centralized Delivery
of Services
HW Appliances
E2E service provisioning is lengthy and complex:

 Multiple network domains under different management teams
 Manual operations
 Heterogeneous Underlay and Overlay networks
Unified “Stateless Fabric” for Service Creation
Controller
Cloud Scale Networking
Central Office
Access
Metro Network Core and Peering Network Network Data Center
EVPN VNF VNF
VNF
Segment Routing
VNF
Compute Leaf Spine
Unified underlay and overlay E2E Cross-domain automation Transform the CO into a data center
networks with segment with model-driven programmability to enable distributed service delivery
routing and EVPN and streaming telemetry and speed up service creation
Simplify Automate Virtualize
Network Transport Evolution
Simplify - Optimize - Enable
Unified MPLS SR
Service Enabled Transport
Protocol
s
BGP-EVPN
Transpor IGP/SR
t
Protocol IP
s
Do more with less !!

Segment Routing Standardization
• IETF standardization in SPRING working group Sample IETF Documents
Problem Statement and Requirements
• First RFC document - RFC 7855 (May (RFC 7855)
2016)
Segment Routing Architecture
• Protocol extensions progressing in multiple (draft-ietf-spring-segment-routing)
groups IPv6 SPRING Use Cases
• IS-IS (draft-ietf-spring-ipv6-use-cases)
• OSPF Segment Routing with MPLS data plane
• PCE (draft-ietf-spring-segment-routing-mpls)
• IDR Topology Independent Fast Reroute using Segment Routing
(draft-bashandy-rtgwg-segment-routing-ti-lfa)
• 6MAN
• BESS IS-IS Extensions for Segment Routing
(draft-ietf-isis-segment-routing-extensions)
• Broad vendor support OSPF Extensions for Segment Routing
(draft-ietf-ospf-segment-routing-extensions)
• Strong customer adoption and support
PCEP Extensions for Segment Routing
• WEB, SP, Enterprise (draft-ietf-pce-segment-routing)
Close to 40 IETF drafts in progress

Technology Overview
Segment Routing
An IP and MPLS source-routing architecture that seeks the right
balance between distributed intelligence and centralized
optimization
Path expressed in the packet Data
Dynamic path Paths options
Dynamic Explicit
(Headend computation) (Operator / Controller)
Control Plane
Routing protocols with
Explicit path extensions SDN controller
(IS-IS,OSPF, BGP)
Data Plane
MPLS IPv6
(segment labels) (+SR header)
Segment Routing
• Source Routing
• the source chooses a path and encodes it in the packet header as an ordered list of segments
• the rest of the network executes the encoded instructions
• Segment: an identifier for any type of instruction
• forwarding or service
• This presentation: IGP-based forwarding construct
Segment Routing
• Source Routing: the source chooses a path and encodes it in the packet header as
an ordered list of segments
• Segment: an identifier for any type of instruction
• Service
• Context
• Locator
• IGP-based forwarding construct
• BGP-based forwarding construct
Segment = Instructions such as
"go to node N using the shortest path"
• Local value or Global Index
Segment Routing
Evolve MPLS with Segment Routing
Mission – Route the luggage to Berlin
via Mexico and Madrid
Segment Routing
London
Toronto 1. A unique and global luggage tag
Seattle Berlin is attached to the luggage with
the list of stops to the final
New-York Madrid destination
Mexico
MEX 2. At each stop, the luggage is simply
routed to the next hop listed on the
MAD luggage tag
BER
Path can be controlled

MAD BER RESULT:
Simple and scalable
BER
Segment Routing – Forwarding Plane
• MPLS: an ordered list of segments is represented as a stack of
labels
• IPv6: an ordered list of segments is encoded in a routing extension
header
• This presentation: MPLS data plane
• Segment → Label
• Basic building blocks distributed by the IGP or BGP
IGP segments
• Two basic building blocks distributed by IGP
• Prefix Segments
• Adjacency Segments
IGP Prefix Segment
16005
• Shortest-path to the IGP prefix 1.1.1.5/32
• Equal Cost MultiPath (ECMP)-aware 1 2 16005
• Global Segment 16005

16005
• Label = 16000 + Index 5
• Advertised as index 16005
16005
• Distributed by ISIS/OSPF
3 4
16005
All nodes use default SRGB

16,000 – 23,999
IGP Prefix Segment
16004
• Shortest-path to the IGP prefix

• Equal Cost MultiPath (ECMP)-aware 1 2
• Global Segment 16004
16004 16004
• Label = 16000 + Index
16004
5
• Advertised as index
16004
• Distributed by ISIS/OSPF
3 4
1.1.1.4/32
16004
16,000 – 23,999
IGP Adjacency Segment
• Forward on the IGP adjacency
• Local Segment 1 2
• Advertised as label value
• Distributed by ISIS/OSPF Adj to 2
5
24042
Adj to 5
3 4 24045
24043
Adj to 3
16,000 – 23,999
Combining IGP Segments 16004
24045
Packet to 5
• Steer traffic on any path through
the network 1 2
• Path is specified by a stack of
labels
5
• No path is signaled 24045
• No per-flow state is created Packet to 5
• Single protocol: IS-IS or OSPF 3 4

16004 24045
Segment Routing – 3 Segments Example
PHP
• Source routing – ordered list of segments
3000 • Stack of MPLS labels
1900 1900 • IPv6 Routing Extension
1700 1700 • MPLS labels are advertised by the IGP
Global label • Simplicity
3000
A B C D
1700
segment 1 Global label
segment 2 I
1700
E F G H
Adjacency
1700 segment 3
label 1900
Segment Routing Global Block (SRGB)
• SRGB allocation based on Segment Routing Configuration
• Default Range SRGB is 16000-23999
• Dynamic Range starts at 16
• If some labels are in use in the requested range SR_APP will periodically keep retrying
to reserve the range
• SR is disabled until range is reserved successfully
• A non-default SRGB can be configured

• All protocols use the same SRGB
• SRGB is allocated as a block of labels under control of SR-APP
• Modifying a SRGB configuration is disruptive for traffic

• Recommended to have same SRGB on all nodes
IOS-XE
ONE(config)#segment-routing mpls Configure a non-default SRGB
ONE(config-srmpls)#global-block 18000 19999 18,000 – 19,999
ONE(config-srmpls)#
Note “mpls” keyword. All config related to MPLS encap (for V4 or V6). In the
future “ipv6 encap” may be available.
IOS-XR
RP/0/0/CPU0:XR-1(config)#segment-routing
RP/0/0/CPU0:XR-1(config-sr)#global-block 18000 19999
Show commands for segment routing
nevada#show segment-routing mpls gb
LABEL-MIN LABEL_MAX STATE DEFAULT
20000 20799 ENABLED No
nevada(config-srmpls)#do show seg mpls gb

LABEL-MIN LABEL_MAX STATE DEFAULT
16000 23999 ENABLED Yes
nevada(config-srmpls)#
segment-routing mpls
global-block 1000 2000
!
connected-prefix-sid-map
address-family ipv4
10.100.1.3/32 index 3 range 1
10.100.1.99/32 index 500 range 1
10.100.100.0/32 index 600 range 100
exit-address-family
R3#show segment-routing mpls connected-prefix-sid-map ipv4

Prefix/masklen SID Type Range Flags SRGB
10.100.1.3/32 3 Indx 1 Y
10.100.1.99/32 500 Indx 1 Y
10.100.100.0/32 600 Indx 100 Y
Segment Routing Global Block (SRGB) – Example
R3#show mpls label range
Downstream Generic label region: Min/Max label: 16/100000 Same SRGB label
Range for Reserved labels:
block allocation for
1. Range ID: 0 Owner: SR-APP OSPF and ISIS
Min/Max label: 1000/2000 ISIS and OSPF
Clients Permitted: ISIS OSPF
Clients In Use: ISIS
Checkpoint Labels Unclaimed: FALSE
Start_label = 1,000 Last_label = 2,000
R3#show mpls infrastructure lsd apps detail service internal

Application Registration Status:
Index Name Client Index Recovery(ms) Cutover(ms) Timer
1 INTERNAL 65 0 0 INACTIVE
10 SNMP 74 10000 10000 INACTIVE
20 LABEL BR 84 0 0 INACTIVE
22 MPLS OAM 86 0 0 INACTIVE
35 ISIS 99 30000 30000 INACTIVE
37 SR-APP 101 0 0 INACTIVE
Modifying SRGB
 If SRGB allocation fails, no SR labels will be installed incl.
• IGP re-downloads all prefixes with new label values based on the
new SRGB
• Disruptive !!
• All labeled traffic will be dropped until IGP routes are re-
downloaded with new labels
4 3 2 1
16,000 16,000 16,000

… … …
Available label space
… … …
1,048,575 1,048,575 1,048,575
Recommended SRGB allocation
1.1.1.1/32, Prefix Segment index 1
4 3 2 1
16001 16001 16001 16001

Payload Payload Payload Payload
16,000 Idx 0 16,000 Idx 0 16,000 Idx 0
SRGB
SRGB
SRGB
…
16,001 Idx 1 …
16,001 Idx 1 16,001
… Idx 1
… … … … … …
23,999 Idx 7,999 23,999 Idx 7,999 23,999 Idx 7,999
24,000 24,000 24,000
… … …
Recommended SRGB allocation:

“same SRGB for all”
 Prefix-SID has global label value
… … …
1,048,575 1,048,575 1,048,575
Recommended SRGB allocation
4 3 2 1
16001 16001 16001 16001

16,000 Idx 0 16,000 Idx 0 16,000 Idx 0
SRGB
SRGB
SRGB
…
16,001 Idx 1 …
16,001 Idx 1 16,001
… Idx 1
… … … … … …
23,999 Idx 7,999 23,999 Idx 7,999 23,999 Idx 7,999
24,000 24,000 24,000
… … …
Same SRGB  prefix-SID has Global label value:

Simple, predictable
Much easier to troubleshoot
Simplifies …SDN programming … …
1,048,575 1,048,575 1,048,575
Not recommended, but possible SRGB allocation
4 3 2 1
16,000 Idx 0 16,000 16,000 Idx 0
SRGB
SRGB
… … … … …
… … … …
23,999 Idx 7,999 23,999 Idx 7,999
24,000 … 24,000
… 533,334 …
533,335 Idx 0
Non-recommended SRGB … …
SRGB allocation: … …
541,334 Idx 7,999
Different SRGBs 541,335
… … …
1,048,575 1,048,575 1,048,575
Not recommended, but possible SRGB allocation
4 3 2 1
16001 533336 16001 16001

16,000 Idx 0 16,000 16,000 Idx 0
SRGB
SRGB
…
16,001 Idx 1 … 16,001
… Idx 1
… … … …
23,999 Idx 7,999 23,999 Idx 7,999
24,000 … 24,000
… 533,334 …
533,335 Idx 0
SRGB 533,336 Idx 1
… …
541,334 Idx 7,999
541,335
… … …
1,048,575 1,048,575 1,048,575
LDP-SR Migration
Assumptions:
• all the nodes can be upgraded to SR
Simplest migration LDP to SR • all the services can be upgraded to SR
• Initial state: All nodes run LDP, not SR

LDP LDP
3 4
LDP LDP
1 LDP 2
5 6
LDP LDP
LDP Domain
Assumptions:

SR+LDP SR+LDP
• Step1: All nodes are upgraded to SR
• In no particular order 3 4
SR+LDP SR+LDP
• leave default LDP label imposition preference
1 LDP 2
5 6
SR+LDP SR+LDP
SR+LDP Domain
Assumptions:

SR+LDP SR+LDP
SR+LDP SR+LDP
1 SR 2
• Step2: All PEs are configured to
prefer SR label imposition sr-prefer
5 6
• In no particular order
SR+LDP SR+LDP
SR+LDP Domain
Assumptions:

SR SR
SR SR
1 SR 2
• Step2: All PEs are configured to prefer SR
label imposition
5 6
SR SR
• Step3: LDP is removed from the nodes in
the network SR Domain
• Final state: All nodes run SR, not LDP
Node X
SR Topology Lo0 – 1.1.1.x/32
Link XY – 99.X.Y.0/24; X < Y
Prefix SID – 16000 + X
SRGB: 16000-23999
Prefix SID Prefix SID
16001 16003 16005 16007

XR-1 XR-3 XR-5 XE-7
1.1.1.1 3.3.3.3 24010 24012 5.5.5.5 7.7.7.7
16008 16009
XE-8 XR-9
PeerAdj SID* 8.8.8.8 9.9.9.9
16002 16004 16006 16010
24011 24008
XE-2 XR-4 XR-6 XR-10
4.4.4.4 6.6.6.6 10.10.10.10
2.2.2.2
ISIS SR ISIS SR ISIS SR

ISIS Level-2 ISIS Level-2 AS64002 ISIS Level-1
AS 64001
Note (*) = PeerAdj SID values are dynamically allocated
Enabling Segment Routing – XR and XE
IOS-XR
segment-routing
!
router isis SR-AS-1
address-family ipv4 unicast
!
interface Loopback0
prefix-sid absolute 16001
!
commit
IOS-XE
XE-2(config)#segment-routing mpls
XE-2(config-srmpls)#connected-prefix-sid-map
XE-2(config-srmpls-conn)#address-family ipv4
XE-2(config-srmpls-conn-af)#2.2.2.2/32 absolute 16002 range 1
XE-2(config-srmpls-conn-af)#exit
XE-2(config-srmpls-conn)#exit
XE-2(config-srmpls)#exit
XE-2(config)#router isis SR-AS-1
XE-2(config-router)#segment-routing mpls
Segment Routing - Control Plane & Data
Plane
MPLS Control and Forwarding Operation with Segment
Routing
Services
MP-BGP
No changes to
IPv4 IPv6
IPv4 IPv6 VPWS VPLS control or
PE1 PE2 VPN VPN
forwarding plane
Packet
Transport LDP RSVP Static BGP IS-IS OSPF IGP or BGP label
distribution for
PE1 IGP PE2
IPv4 and IPv6.
MPLS Forwarding
Forwarding plane
remains the same
SR enabled node
SID Encoding
SRGB = [ 16,000 – 23,999 ] – Advertised as base = 16,000, range = 8,000
Prefix SID = 16,001 – Advertised as Prefix SID Index = 1
Adjacency SID = 24000 – Advertised as Adjacency SID = 24000
• Prefix SID
• Label form SR Global Block (SRGB)
• SRGB advertised within IGP via TLV
• In the configuration, Prefix-SID can be configured as an absolute value or an index
• In the protocol advertisement, Prefix-SID is always encoded as a globally unique index
Index represents an offset from SRGB base, zero-based numbering, i.e. 0 is 1st index
E.g. index 1  SID is 16,000 + 1 = 16,001
• Adjacency SID
• Locally significant
• Automatically allocated by the IGP for each adjacency
• Always encoded as an absolute (i.e. not indexed) value
SR IS-IS Control Plane Summary
• IPv4 and IPv6 control plane
• Level 1, level 2 and multi-level routing
• Prefix Segment ID (Prefix-SID) for host prefixes on loopback
interfaces
• Adjacency Segment IDs (Adj-SIDs) for adjacencies
• Prefix-to-SID mapping advertisements (mapping server)
• MPLS penultimate hop popping (PHP) and explicit-null signaling
SID index 1
1.1.1.2 1.1.1.1
IS-IS Configuration – Example

1.1.1.4 1.1.1.6
router isis 1 DIS
address-family ipv4 unicast Wide metrics
metric-style wide
enable SR IPv4 control plane and
SR MPLS data plane on all ipv4
! interfaces in this IS-IS instance
metric-style wide Wide metrics
! enable SR IPv6 control plane and
interface Loopback0 SR MPLS data plane on all ipv6
passive interfaces in this IS-IS instance
Ipv4 Prefix-SID value for loopback0
!
Ipv6 Prefix-SID value for loopback0
!
!
SR OSPF Control Plane Summary
• OSPFv2 control plane
• Multi-area
• IPv4 Prefix Segment ID (Prefix-SID) for host prefixes on loopback
interfaces
• Adjacency Segment ID (Adj-SIDs) for adjacencies
• Prefix-to-SID mapping advertisements (mapping server)
• MPLS penultimate hop popping (PHP) and explicit-null signaling
SID index 1
1.1.1.2 1.1.1.1 1.1.1.4
OSPF Configuration Example

router ospf 1 1.1.1.5 1.1.1.3
DR
router-id 1.1.1.1 Enable SR on all areas
area 0
interface Loopback0
passive enable
prefix-sid absolute 16001 Prefix-SID for loopback0
!
!
!
MPLS Data Plane Operation (labeled)
Prefix SID Adjacency SID
SRGB [16,000 – 23,999 ] SRGB [16,000 – 23,999 ]
Adjacency
SID = X
Swap Pop
X
X X Y Y
• Packet forwarded along IGP shortest path (ECMP)  Packet forwarded along IGP adjacency
• Swap operation performed on input label  Pop operation performed on input label
• Same top label if same/similar SRGB
 Top labels will likely differ
• PHP if signaled by egress LSR
 Penultimate hop always pops last adjacency SID
MPLS Data Plane Operation (Prefix SID)
SRGB [16,000 – 23,999 ] SRGB [16,000 – 23,999 ] SRGB [16,000 – 23,999 ] SRGB [16,000 – 23,999 ]
A B C D Loopback X.X.X.X
Prefix SID Index = 41
Push Swap Pop Pop

Push
16041 16041
VPN Label VPN Label VPN Label
Payload Payload Payload Payload Payload
MPLS Data Plane Operation (Adjacency SIDs)
SRGB [16,000 – 23,999 ] SRGB [16,000 – 23,999 ] SRGB [16,000 – 23,999 ] SRGB [16,000 – 23,999 ]
A B X D Loopback X.X.X.X
Adjacency Prefix SID Index = 41
SID = 30206
Push Pop Pop Pop
Push
Push
30206
16041 16041
VPN Label VPN Label VPN Label
Payload Payload Payload Payload Payload
Traffic Protection
Topology Independent LFA (TI-LFA) – Benefits
• 100%-coverage 50-msec link, node, and SRLG protection
• Simple to operate and understand
• automatically computed by the IGP
• Prevents transient congestion and suboptimal routing

• leverages the post-convergence path, planned to carry the traffic
TI-LFA – Zero-Segment Example
• TI-LFA for link R1R2 on R1 prefix-SID(Z) A Z
Packet to Z
• Calculate post-convergence SPT
• SPT with link R1R2 removed from 1 2
topology
1000
• Derive SID-list to steer traffic on Packet to Z
post-convergence path prefix-SID(Z) 5
Packet to Z
• R1 will steer the traffic towards
LFA R5 4 3
Default metric: 10
TI-LFA – Single-Segment Example
• TI-LFA for link R1R2 on R1 prefix-SID(Z) A Z
Packet to Z
• Calculate post-convergence Packet to Z
SPT 1 2
• Derive SID-list to steer traffic
on post-convergence path  prefix-SID(R4)
<Prefix-SID(R4)> prefix-SID(Z) 5
prefix-SID(Z)
• Also known as “PQ-node” Packet to Z
Packet to Z
• R1 will push the prefix-SID 4 3
of R4 on the backup path
Default metric:10
TI-LFA – Double-Segment Example
A Z
prefix-SID(Z)
• TI-LFA for link R1R2 on R1 Packet to Z Packet to Z
• Calculate post-convergence SPT 1 2
• Derive SID-list to steer traffic on prefix-SID(R4)

post-convergence path  adj-SID(R4-R3)
5
<Prefix-SID(R4), Adj-SID(R4-R3) prefix-SID(Z) prefix-SID(Z)
• Also known as “P- and Q-node” Packet to Z Packet to Z
• R1 will push the prefix-SID of R4 4

R4 3
R3
and the adj-SID of R4-R3 link on 1000
the backup path

adj-SID(R4-R3) Default metric: 10
prefix-SID(Z)
Packet to Z
Enabling TI-LFA
IOS-XR
router isis SR-AS-1
interface GigabitEthernet0/0/0/0
fast-reroute per-prefix ti-lfa level 2
!
!
!
!
!
IOS-XE
router isis SR-AS-1
fast-reroute ti-lfa level-2
TI-LFA Backup Coverage
IOS-XR
RP/0/0/CPU0:XR-1#show isis fast-reroute summary
IS-IS SR-AS-1 IPv4 Unicast FRR summary
Critical High Medium Low Total
Priority Priority Priority Priority
Prefixes reachable in L2
All paths protected 0 0 4 8 12
Some paths protected 0 0 0 0 0
Unprotected 0 0 0 0 0
Protection coverage 0.00% 0.00% 100.00% 100.00% 100.00%
IOS-XE
XE-2#show isis fast-reroute summary
Tag SR-AS-1:
Microloop Avoidance State: Enabled for protected
Segment-Routing Microloop Avoidance State: Disabled
IPv4 Fast-Reroute Protection Summary:
Prefix Counts: Total Protected Coverage

High priority: 0 0 0%
Normal priority: 12 12 100%
Total: 12 12 100%
SRTE
Traffic Engineering with Segment Routing
• Source-Based routing – State only at
ingress PE Segment
Routing
• Supports constraint-based routing
• Supports centralized admission control
• Uses existing ISIS / OSPF extensions to
advertise link attributes
• No RSVP-TE to establish LSPs
• Supports ECMP
TE LSP
MPLS LFIB with Segment Routing
• LFIB populated by IGP (ISIS / PE PE
OSPF) PE PE
• Forwarding table remains constant PE

P
PE
(Nodes + Adjacencies) regardless PE PE
of number of paths
In Out Out
Label Label Interface
L1 L1 Intf1
Network
Node L2 L2 Intf1 Forwarding
Segment Ids … … … table remains
L8 L8 Intf4 constant
L9 L9 Intf2
Node L10 Pop Intf2
Adjacency … … …
Segment Ids
Ln Pop Intf5
Binding SID
• Binding Segment is a fundamental building block of
SRTE
24008 • The Binding Segment is a local segment

1
3 • Has local significance
pkt
• A Binding-Segment ID identifies a SRTE Policy
• Each SRTE Policy is associated 1-for-1 with a
Binding-SID
• Packet received with Binding-SID as top label is
steered into the SRTE Policy associated with the
Binding-SID
• Binding-SID label is popped, SRTE Policy’s SID
list is pushed
• Binding SID can be automatically assigned or
statically configured as part of the SRTE policy
Binding SID
2 • Binding Segment is a fundamental building block of
SRTE
24008 • The Binding Segment is a local segment

1 3
pkt 5 • Has local significance
160074 pkt
7 • A Binding-Segment ID identifies a SRTE Policy
16003 16003
6 • Each SRTE Policy is associated 1-for-1 with a
pkt pkt Binding-SID
• Packets received with Binding-SID as top label are
8 9 steered into the SRTE Policy associated with the
Binding-SID
• Binding-SID label is popped, SRTE Policy’s SID
list is pushed
• Binding SID can be automatically assigned or
statically configured as part of the SRTE policy
SR-TE Use Cases
segment-routing
Node1
Low- Delay path
traffic-eng
policy POLICY1
color 20 end-point ipv4 1.1.1.3
Use-Case D:1500
I:10
D:1500
I:10 candidate-paths
1 2 3 preference 100
D:800 dynamic mpls
SID-list: <16005, 16004, 16003> I:10 metric
D:800 D:800 type delay
I:10 I:10
5 4
D:2200
I:10
D:2000
I:10
6
• Head-end computes a SID-list that expresses the shortest-path according to the selected
metric delay
Link Delay Measurement Protocol
(phase1) One Way Delay = (T2 – T1)
PTP
(future) Two-Way Delay
•
• Accurate time-stamp
TX Timestamp T1 RX Timestamp T2
• MPLS PM Local-end Remote-end
• using GAL/Gach defined in RFC 6374 PM Query Packet 99.2.1.2
• IGP and BGP support:

99.1.2.1 PM Response Packet
• Extended TE Link Delay Metrics will be
supported in ISIS (RFC 7810) and OSPF (RFC
XTC (PCE) view
7471)
Link[0]: local address 99.1.2.1, remote address 99.2.1.2
• BGP-LS (draft-ietf-idr-te-pm-bgp) Extended Local node:
ISIS system ID: 0000.0000.6666 level-2 ASN: 64002
TE Link Delay Metrics Remote node:
TE router ID: 5.5.5.5
Host name: Napoli-5
ISIS system ID: 0000.0000.5555 level-2 ASN: 64002
• No additional configuration in ISIS/OSPF/BGP-IS Metric: IGP 1, TE 1,Delay 6000
: Latency automatically flooded Bandwidth: Total 125000000, Reservable 0
Adj SID: 24005 (protected) 24004 (unprotected)
Excluded from CSPF: no
Reverse link exists: yes
Different VPNs need different underlay SLA
I: 50
2 4
1 CE Basic VPN should
D: 15
use lowest cost
6 5 underlay path
IGP cost 30
Default IGP cost: I:10 Objective:
Default Delay cost: D:10
operationalize this
service for
TE cost 20
I: 50
simplicity, scale
2 4 and performance
Premium VPN
1 CE should use lowest
D: 15 delay path
6 5
Default IGP cost: I:10

On-Demand SR Policy work-flow
Automatic LSP setup and steering
➎
➌ BGP: 20/8 via PE4
router bgp 1
neighbor 1.1.1.10 VPN-LABEL: 99999
Low-Delay (color 20) ➋ BGP: 20/8 via PE4
address-family vpnv4 unicast RR VPN-LABEL: 99999
! Low-Delay (color 20)
segment-routing
traffic-eng
on-demand color 20 ➍ PE4 with Low-
I: 50 ➊ BGP: 20/8 via
preference 100
metric
SR Policy template Delay (color 20)?
2 4 CE
Low-Delay (color 20) ➎ use template
type delay
color 20 1 CE 20/8
➏  SID-list D: 15
<16002, 30204> 6 5
Default IGP cost: I:10

Automated performant steering
➐➑ ➌ BGP: 20/8 via PE4
FIB table at PE1 VPN-LABEL: 99999
Low-latency (color 20) ➋ BGP: 20/8 via PE4
BGP: 20/8 via 4001 RR VPN-LABEL: 99999
SRTE: 4001: Push <16002, 30204> Low-latency (color 20)
Low Latency to PE4

➍ PE4 with Low-
➐ I: 50 ➊ BGP: 20/8 via
latency (color 20)?
2 4 CE
Automatically, the service route ➎ use template
resolves on the Binding SID (4001) of color 20 1 CE 20/8
the SR Policy it requires ➏  SID-list L: 15
<16002, 30204>
6 5
Simplicity and Performance
➐ instantiate
SR Policy Default IGP cost: I:10
No route-policy required. No complex BSID 4001 Default Latency cost: L:10
PBR to configure, no PBR ➑ Install in FIB 20/8
performance tax via BSID label 4001
SR-TE Use Cases
Inter domain
connectivity with SLA
Crossing the AS border: BGP Peering Segment
AS1 30024 AS6
2 4 6.1.1.6/32
30024 18006
18006
1 10 11 pkt 6
pkt
16002 pkt
30024 3 5
18006
pkt
• “Pop and Forward to the BGP peer”

What is missing?
• Local Segment – like an adjacency SID external to the IGP
• DynamicallyHow dobut
allocated I get topology
persistent info of external domains?
Inter Area Path Computation with SLA
Ask: Provide latency optimized path across multiple AS’s from a source to a destination
Service Y
Service
w/ SLA
Configuration PCE
Latency
Request PCE to compute path to A9
with SLA X Get back SID-list Real Time
Topology feed via
Configuration of SR Policy Delegation to the BGP-LS
to Node 1 with SLA Latency PCE for reopt.
segment-routing
traffic-eng 1 2 3 4 5 6 7 8 9
policy POL1
end-point 9.9.9.9 color 20 T1’
path 21 22 23
preference 100
dynamic mpls pce 11 12 13 14 15 16 17 18 19
metric
type latency
Region1 CORE Region2
XR Transport Controller
• XTC is an IOS XR multi-domain stateful SR Path Computation Element (PCE)
• Fundamentally Distributed (RR-like Deployment)
• Supports RSVP-TE
On XTC:
pce
address ipv4 1.1.1.3
XTC !
Domain1 Domain2 BGP-LS Domain3
A BR1 BR3 BR5
Peering
On PE:
links
pcc
pce
!
address ipv4 1.1.1.3 BR2 BR4 BR6 Z
XTC Receives & Consolidates Multiple Topologies
Each domain feeds its
Domain1 Domain2 Domain3
•
topology to XTC via BGP-LS
A BR1 BR1 BR3 BR3 BR5 BR5
BR2 BR2 BR4 BR4 BR6 BR6 Z

• XTC combines the different
topologies to compute
paths across entire topology XTC
Domain1 Domain2 Domain3
A BR1 BR3 BR5
Peering
links
BR2 BR4 BR6 Z
BGP-LS
Service Disjointness segment-routing
Node1
traffic-eng
policy POLICY1
Intra and inter domain color 20 end-point ipv4 1.1.1.3
candidate-paths
preference 100
XTC XTC dynamic mpls pce
metric
type igp
SID-list:
1 I:100
2 I:100
3 association group 1 type node
{30102, 30203} segment-routing
Node6
traffic-eng
5 4
7 policy POLICY2
color 20 end-point ipv4 1.1.1.8
candidate-paths
preference 100
SID-list:
6 I:100
7 I:100
8 dynamic mpls pce
metric
{16007, 16008} type igp
Default IGP link metric: I:10 association group 1 type node
• Two dynamic paths between two different pairs of (head-end, end-point) must be disjoint
from each other
Path Computation
Distributed or Centralized ?
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 Centralized
Multi Layer Centralized Centralized
SR-TE
• Simple, Automated and Scalable
• No state in the network: state in the packet header
• No tunnel interface: “SR Policy”
• No head-end a-priori configuration: on-demand policy instantiation
• No head-end a-priori steering: automated steering
• Multi-Domain
• XR Traffic Controller (XTC) for compute
• Lots of Functionality and flexibility
• Designed with lead operators along their use-cases
Stay Up-To-Date
amzn.com/B01I58LSUO
segment-routing.net
linkedin.com/groups/8266623
twitter.com/SegmentRouting
facebook.com/SegmentRouting/
Complete your online session evaluation
Give us your feedback to be entered

into a Daily Survey Drawing.
Complete your session surveys through
the Cisco Live mobile app or on
www.CiscoLive.com/us.
Don’t forget: Cisco Live sessions will be available for viewing
on demand after the event at www.CiscoLive.com/Online.
Continue
your Demos in
the Cisco
Walk-in
self-paced
Meet the
engineer
Related
sessions
education campus labs 1:1
meetings
Thank you
#CLUS
#CLUS
Reference Slides
ODN
XTC Building Blocks
WAE Custom app
REST API
Native SR
Multi-Domain algorithms
Topology
Topo
Compute
DB
XTC runs on
virtual or physical
IOS-XR node
Collect Deploy
IGP PCEP
BGP-LS
BGP
Dynamic BGP Traffic Engineering (BGP-TE)
 Headend must have global auto tunnel configuration
 Headend must have an attribute-list for TE specific configurations
Step 1:
Step 2: Setting Community Attribute:
Matching community Attribute: Route-map matches Route-map matches customer prefix
community attribute and sets attribute-list for the and sets unique community
NLRI
L3VPN
Headend Tailend
Customer traffic in VRF
Midpoint
Step 3:
Attribute-list Configuration- Has the tunnel
related configurations
ODN Workflow
BGP VPNv4
BGP RR BGP RR
BGP VPNv4
• Routes tagged with a user-defined COLOR to BGP VPNv4
BGP color comm.
“gold”
convey SLA requirements
• VPN routes propagated via BGP
BGP color comm.
BGP “gold” Y/24
XR-1 XR-3 XR-5 XE-7
1.1.1.1 3.3.3.3 5.5.5.5 7.7.7.7
XE-8 XR-9
8.8.8.8 9.9.9.9

2.2.2.2 4.4.4.4 BGP 6.6.6.6 10.10.10.10

AS 64001
ODN Workflow
• Ingress PE matches on user-specified BGP “color” community
XTC-A
SRTE • Ingress PE enforces a “template” associated with the color community
SR PCE
On-demand color “gold”
contact PCE
request path to BGP NH
minimize TE metric
Need a path to node (9)?
Minimizing TE metric
PCReq
BGP XE-7
XR-1 XR-3 XR-5
1.1.1.1 3.3.3.3 5.5.5.5 7.7.7.7
XE-8 XR-9
8.8.8.8 9.9.9.9

2.2.2.2 4.4.4.4 BGP 6.6.6.6 10.10.10.10

AS 64001
PCEP
XTC-A XTC-B
SR PCE SR PCE
PCEP
PCEP
BGP XE-7
XR-1 XR-3 XR-5
1.1.1.1 3.3.3.3 5.5.5.5 7.7.7.7
XE-8 XR-9
8.8.8.8 9.9.9.9

2.2.2.2 4.4.4.4 BGP 6.6.6.6 10.10.10.10

AS 64001
PCE
XTC
RP/0/0/CPU0:XTC-A(config)# pce
RP/0/0/CPU0:XTC-A(config-pce)# address ipv4 11.11.11.11
XR-1
RP/0/0/CPU0:XR-1(config)#segment-routing
RP/0/0/CPU0:XR-1(config-sr)# traffic-eng
RP/0/0/CPU0:XR-1(config-sr-te)# pcc
RP/0/0/CPU0:XR-1(config-sr-te-pcc)# source-address ipv4 1.1.1.1
RP/0/0/CPU0:XR-1(config-sr-te-pcc)# pce address ipv4 11.11.11.11
RP/0/0/CPU0:XR-1(config-pcc-pce)# !
RP/0/0/CPU0:XR-1(config-pcc-pce)# report-all
RP/0/0/CPU0:XR-1(config-sr-te-pcc)# maximum-sid-depth 5
PCE
XR-1
RP/0/0/CPU0:XR-1#show segment-routing traffic-eng pcc ipv4 peer brief
Address Precedence State Learned From
-------------------- ------------ ------------ ---------------
11.11.11.11 255 up config
RP/0/0/CPU0:XR-1#show segment-routing traffic-eng pcc ipv4 peer detail

PCC's peer database:
--------------------
Peer address: 11.11.11.11 (best PCE)
State up
Capabilities: Stateful, Update, Segment-Routing, Instantiation
PCEP has been up for: 05:41:32
Local keepalive timer is 30 seconds
Remote keepalive timer is 30 seconds
Local dead timer is 120 seconds
Remote dead timer is 120 seconds
Statistics:
Open messages: rx 1 | tx 1
Close messages: rx 0 | tx 0
Keepalive messages: rx 683 | tx 683
Error messages: rx 0 | tx 0
Report messages: rx 0 | tx 0
Update messages: rx 0 | tx 0
PCE
XTC
RP/0/0/CPU0:XTC-A#show pce ipv4 topology summary
PCE's topology database summary:
--------------------------------
Topology nodes: 13
Prefixes: 10
Prefix SIDs:
Total: 10
Regular: 10
Strict: 0
Links:
Total: 74
EPE: 4
Adjacency SIDs:
Total: 120
Unprotected: 58
Protected: 58
EPE: 4
Private Information:
Lookup Nodes 21
Consistent yes
Update Stats (from IGP and/or BGP):
Noded added: 17
Noded deleted: 0
Links added: 74
Links deleted: 0
Prefix added: 93
Prefix deleted: 0
Coloring
XR-9 XR-1
router bgp 64002 segment-routing
bgp router-id 9.9.9.9 traffic-eng
vrf VPN_FOO on-demand color 10
rd auto dynamic mpls
address-family ipv4 unicast pce
redistribute connected !
! metric
neighbor 172.16.2.2 type te
remote-as 2 !
address-family ipv4 unicast !
route-policy SET_COLOR_HI_BW in !
route-policy pass-all out on-demand color 20
! dynamic mpls
route-policy SET_COLOR_HI_BW pce
set extcommunity color color20-hi-bw !
pass metric
end-policy type igp
! !
extcommunity-set opaque color20-hi-bw !
20 !
end-set !
! !
SR Policy
RP/0/0/CPU0:XR-1#show segment-routing traffic-eng policy color 20
SR-TE policy database
---------------------
Name: bgp_AP_1 (Color: 20, End-point: 2.2.2.2)

<snip>
Name: bgp_AP_2 (Color: 20, End-point: 9.9.9.9)
Status:
Admin: up Operational: up for 00:06:37 (since Apr 11 09:43:54.630)
Candidate-paths:
Preference 100:
Dynamic (pce 11.11.11.11) (active)
Weight: 13, Metric Type: IGP
16003 [Prefix-SID, 3.3.3.3]
24013 [Adjacency-SID, 99.3.5.3 - 99.3.5.5]
16010 [Prefix-SID, 10.10.10.10]
16009 [Prefix-SID, 9.9.9.9]
Attributes:
Binding SID: 24014
Allocation mode: dynamic
State: Programmed
Policy selected: yes
Forward Class: 0
Distinguisher: 0
Auto-policy info:
Creator: BGP
IPv6 caps enable: no
PCC
RP/0/0/CPU0:XTC-A#show pce lsp pcc ipv4 1.1.1.1 detail
Tunnel Name: bgp_AP_2
LSPs:
LSP[0]:
source 1.1.1.1, destination 9.9.9.9, tunnel ID 2, LSP ID 2
State: Admin up, Operation active
Binding SID: 24014
PCEP information:
PLSP-ID 0x80002, flags: D:1 S:0 R:0 A:1 O:2 C:0
LSP Role: Single LSP
State-sync PCE: None
PCC: 1.1.1.1
LSP is subdelegated to: None
Reported path:
Metric type: IGP, Accumulated Metric 13
SID[0]: Node, Label 16003, Address 3.3.3.3
SID[1]: Adj, Label 24013, Address: local 99.3.5.3 remote 99.3.5.5
Computed path: (Local PCE)
Computed Time: Wed Apr 11 09:43:34 2018 (00:09:00 ago)
Metric type: IGP, Accumulated Metric 13
SID[1]: Adj, Label 24013, Address: local 99.3.5.3 remote 99.3.5.5
<snip>

BRKRST-2124-Introduction To Segment Routing PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

BRKRST-2124-Introduction To Segment Routing PDF

Hochgeladen von

Copyright:

Verfügbare Formate

#CLUS

Webex Teams will be moderated cs.co/ciscolivebot#BRKRST-2124

Model Traditional SP Cloud Scale SP

Delayering Unified Infrastructure Horizontal Integration

SDN Driven Automation and Virtualization

Legacy Central Office

Metro Network Domain Core Network Domain Data Center Domain

L2VPN L3VPN VXLAN VNF VNF

E2E service provisioning is lengthy and complex:

EVPN VNF VNF

Compute Leaf Spine

Do more with less !!

Close to 40 IETF drafts in progress

Path can be controlled

• Shortest-path to the IGP prefix 1.1.1.5/32

• Equal Cost MultiPath (ECMP)-aware 1 2 16005

• Global Segment 16005

All nodes use default SRGB

• Shortest-path to the IGP prefix

• No per-flow state is created Packet to 5

• Single protocol: IS-IS or OSPF 3 4

• A non-default SRGB can be configured

• Modifying a SRGB configuration is disruptive for traffic

nevada(config-srmpls)#do show seg mpls gb

R3#show segment-routing mpls connected-prefix-sid-map ipv4

Start_label = 1,000 Last_label = 2,000

R3#show mpls infrastructure lsd apps detail service internal

16,000 16,000 16,000

16001 16001 16001 16001

16,000 Idx 0 16,000 Idx 0 16,000 Idx 0

Recommended SRGB allocation:

16001 16001 16001 16001

16,000 Idx 0 16,000 Idx 0 16,000 Idx 0

Same SRGB  prefix-SID has Global label value:

16,000 Idx 0 16,000 16,000 Idx 0

16001 533336 16001 16001

16,000 Idx 0 16,000 16,000 Idx 0

Simplest migration LDP to SR • all the services can be upgraded to SR

• Initial state: All nodes run LDP, not SR

Simplest migration LDP to SR • all the services can be upgraded to SR

• Initial state: All nodes run LDP, not SR

Simplest migration LDP to SR • all the services can be upgraded to SR

• Initial state: All nodes run LDP, not SR

Simplest migration LDP to SR • all the services can be upgraded to SR

• Initial state: All nodes run LDP, not SR

Prefix SID Prefix SID

16001 16003 16005 16007

ISIS SR ISIS SR ISIS SR

IS-IS Configuration – Example

OSPF Configuration Example

SRGB [16,000 – 23,999 ] SRGB [16,000 – 23,999 ]

Payload Payload Payload Payload

Push Swap Pop Pop

Payload Payload Payload Payload Payload

Payload Payload Payload Payload Payload

• Prevents transient congestion and suboptimal routing

• Calculate post-convergence SPT 1 2

• Derive SID-list to steer traffic on prefix-SID(R4)

• R1 will push the prefix-SID of R4 4

the backup path

Prefix Counts: Total Protected Coverage

• Forwarding table remains constant PE

(Nodes + Adjacencies) regardless PE PE