Segment Routing-Cisco Live

Introduction to
Segment Routing
Dan Hutchins, Principal Architect
danhut@cisco.com
BRKRST-1124
Cisco Spark
Questions?
Use Cisco Spark to communicate
with the speaker after the session
How
1. Find this session in the Cisco Live Mobile App
2. Click “Join the Discussion”
3. Install Spark or go directly to the space
4. Enter messages/questions in the space
© 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public
Abstract
Introduction to Segment Routing
This session provides an overview of the segment routing technology and its use
cases. This new routing paradigm provides high operational simplicity and
maximum network scalability and flexibility. You will get an understanding of the
basic concepts behind the technology and its wide applicability ranging from
simple transport for MPLS services, disjoint routing, traffic engineering and its
benefits in the context of software defined networking.
Previous knowledge of IP routing and MPLS is required.
BRKRST-1124 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 4
Opinions on
Source Routing
Agenda
• Why Should I Care?

• Technology Overview
• Use Cases
• A Closer Look at the Control
and Data Planes
• Traffic Protection
• Traffic Engineering
Why Should I care?
• Existing Core Protocol Stack is Complex
• IGP
• BGP
• RSVP
• LDP
• Network Hand-Offs are Complex and Costly

• Emerging Requirements from Mobility such as slicing
• Application enablement
What Does SR Do?
• Protocol Removal / Simplification
• Built-in Fast Re-Route (near zero config)
• Scalable & Simple Traffic Engineering
• Inter-domain routing
• Service Chaining
• NOT THE SERVICE LAYER – EVPN FOR THAT
Agile Carrier Ethernet
Unified IP/MPLS ACE

Apps Applications Applications Apps
APIs
CLIs
Path Computation/
BGP Provisioning WAN optimization Crosswork Controller/
NSO XTC/WAE Automation Orchestration
T-LDP
BGP-LU APIs
Router RSVP-TE BGP
MPLS LDP IGP/SR
Router
IGP IP
IP
Simplified control plane (distributed on router)

Centralized management and policy control
© 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 9
Where Can I Use It?
Metro & Access
Data Centre
BRKRST-1124 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public
Segment Routing Standardisation
• IETF standardisation in SPRING Sample IETF Documents
working group Problem Statement and Requirements
(RFC 7855)
• Protocol extensions progressing in Segment Routing Architecture
(draft-ietf-spring-segment-routing)
multiple groups
IPv6 SPRING Use Cases
• IS-IS (draft-ietf-spring-ipv6-use-cases)
• OSPF Segment Routing with MPLS data plane
(draft-ietf-spring-segment-routing-mpls)
• PCE
Topology Independent Fast Reroute using Segment Routing
• IDR (draft-bashandy-rtgwg-segment-routing-ti-lfa)
• 6MAN IS-IS Extensions for Segment Routing

(draft-ietf-isis-segment-routing-extensions)
• BESS
OSPF Extensions for Segment Routing
(draft-ietf-ospf-segment-routing-extensions)
• Broad vendor support PCEP Extensions for Segment Routing
(draft-ietf-pce-segment-routing)
• Strong customer adoption
• WEB, SP, Enterprise Close to 40 IETF drafts in progress
Technology Overview
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 – 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 Prefix Segment
• Shortest-path to the
IGP prefix
• Equal Cost Multipath
(ECMP)-aware
• Global Segment 12
10
2 4
• Label = 16000 + Index
• Index of NodeX = X is 1
used for illustrative
7
13 16005
purposes
3 6 5
• Distributed by
ISIS/OSPF 11
14
DC (BGP-SR) WAN (IGP-SR) PEER
IGP Adjacency Segment
• “Pop and Forward on
the IGP adjacency”
• Local Segment
• Dynamically allocated 30204
12
• Value “30X0Y” 10
2 4
used for illustration
1
• X is the “from” 7
• Y is the “to”
13
3 6 5
• Advertised as a label
value 11
• Distributed by 14
ISIS/OSPF DC (BGP-SR) WAN (IGP-SR) PEER
BGP Prefix Segment
• Shortest-path to the
BGP prefix
• Global Segment
16001
• 16000 + Index 12
• Index of NodeX = X is 10
2 4
used for illustrative
purposes 1
7
• Signaled by BGP 13
3 6 5
11
14
BGP Peering Segment
• “Pop and Forward to
the BGP peer”
• Local Segment
• Dynamically allocated
12 40407 Low Lat,
• Value 40X0Y (for 10 Low BW
2 4
illustration)
• X is the “from” 1
7
• Y is the “to” 13
• Signaled by BGP-LS 3 6 5 High Lat, High BW
(topology information)
to the controller 11
14
Multi-Domain Topology
• SR Path Computation SR
BGP-LS
Element (PCE) PCE
BGP-LS
• PCE collects via BGP-
LS BGP-LS
• IGP segments
12
• BGP segments
10 Low Lat, Low BW
2 4
• Topology
1
7
13
3 6 5
11
14
End-to-End Policy, Unified Data Plane
• Construct a path by Low-Latency to 7 SR
combining segments for application … PCE
to form an end-to-end PCEP, Netconf, BGP
path: {16001,
16002,
• 16001 (Prefix-SID)
• 16002 (Prefix-SID)
30204, 16001 30204
40407 } 12
• 30204 (Adj-SID)
10 16002 40407
• 40407 (Peer-SID) 2 4
16001 50
• Per-application 1 Low Lat
flow engineering Low BW
7
13
• Millions of flows
• No signalling 3 6 5
• No midpoint state
• No reclassification at 11
boundaries
14 Default ISIS cost metric: 10
Segment Routing Product Support
• Cisco Platforms:
• IOS-XR (ASR9000, CRS-1/CRS-3, NCS5000, NCS5500, NCS6000)
• IOS-XE (ASR1000, CSR1000v, ASR902, ASR903, ASR920, ISR4400)
• NX-OS (N3K, N9K)
• Open Source (FD.io/VPP, Linux Kernel, ODL, ONOS, OpenWRT)
• PCE (WAN Automation Engine, XTC)
Use Cases
Simple and Efficient Transport of MPLS services
16002
• No change to
service vpn
configuration Packet to 8
• MPLS services MP-BGP
ride on the prefix vpn
segments Packet to 8 3 4 Packet to 8
CE PE PE CE
• Simple: IGP-only
• One less protocol 7 1 2 8
to operate
1.1.1.2/32
• No LDP, no Prefix-SID 16002 10.0.0.0/30
2001::a00:0/126
5 6
RSVP-TE
16002
vrf RED SR Domain vrf RED
vpn
Packet to 8
Interworking with LDP
• SR to LDP Interworking
requires Mapping Server 16007
functionality vpn
• E.g. Nodes 6 & 8 can advertise LDP(7)
prefix-SIDs in IGP, on behalf of Packet
non-SR nodes. vpn
• SR nodes install these prefix- 2 3 Packet
vpn
SIDs in their forwarding table. Packet
• Mapping server is a control
plane mechanism and doesn’t 1 4 7
have to be in the data path
Packet
• LDP to SR Interworking is Packet
Automatic and Seamless. 6 5
Site 1 Site 2
16007
8
vpn
Mapping-servers
1.1.1.4/32  SID 16004
Packet
1.1.1.7/32  SID 16007 BRKRST-1124 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 25
Topology-Independent LFA (TI-LFA FRR)
• 50msec FRR in any topology
• Link, Node, or SRLG 7
• IGP Automated 2 3
• No LDP, no RSVP-TE
16007
• Optimum
Packet 1 4
• Post-convergence path
• No midpoint backup state 16007
6 5
Packet
• Detailed operator report
16005
• S. Litkowski, B. Decraene, Orange
16007
Packet
Optimised Content Delivery
• On a per-content, per-user basis, the 7
AS7
content delivery application can
engineer
• The path within the AS 5 6
• The selected border router 16003
• The selected peer
AS5 AS6
16002
• Also applicable for engineering 40206
egress traffic from DC to peer Packet
1 2
• BGP Prefix and Peering Segments
4 3
AS1
A Closer
Look at the
Control and
Data Planes
MPLS Control and Forwarding Operation
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
• Prefix SID Adjacency SID = 24000 – Advertised as Adjacency SID = 24000
• Uses SR Global Block (SRGB)
• SRGB advertised with router capabilities 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 for each adjacency
• Always encoded as an absolute (i.e. not indexed) value
SR IS-IS Control Plane Overview
• IS-IS Segment Routing functionality
• 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 signalling
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
segment-routing mpls
SR MPLS data plane on all ipv4
!
interfaces in this IS-IS instance
address-family ipv6 unicast
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
prefix-sid absolute 16001 Ipv4 Prefix-SID value for
! loopback0
prefix-sid absolute 20001 Ipv6 Prefix-SID value for
! loopback0
!
SR OSPF Control Plane Overview
• OSPF Segment Routing functionality
• 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 signalling
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
Prefix SID Adjacency SID
SRGB [16,000 – 23,999 ] SRGB [16,000 – 23,999 ]
Adjacency
SID = X
Swap Pop
X
X X Y Y
Payload Payload Payload Payload
• Packet forwarded along IGP shortest path • Packet forwarded along IGP adjacency
(ECMP) • Pop operation performed on input label
• Swap operation performed on input label • Top labels will likely differ
• Same top label if same/similar SRGB • Penultimate hop always pops last adjacency SID
• PHP if signaled by egress LSR
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
MPLS LFIB with Segment Routing
PE PE
• LFIB populated by IGP (ISIS / OSPF) PE PE
• Other protocols (LDP, RSVP, BGP) can PE PE

P
still program LFIB
PE PE
• Forwarding table remains constant
(Nodes + Adjacencies) regardless of In Out Out
number of paths 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
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
• Incremental deployment
• Also protects LDP and unlabeled traffic
TI-LFA – Zero-Segment Example
prefix-SID(Z) A Z
• TI-LFA for link R1R2 on R1
Packet to Z
• Calculate post-convergence SPT
• SPT with link R1R2 removed from 1 2
topology
1000
• Derive SID-list to steer traffic on post- Packet to Z
convergence path  empty SID-list prefix-SID(Z) 5
• R1 will steer the traffic towards LFA Packet to Z

R5
4 3
Default metric: 10
TI-LFA – Single-Segment Example
• TI-LFA for link R1R2 on R1 prefix-SID(Z) A Z
• Calculate post-convergence SPT Packet to Z

Packet to Z
• Derive SID-list to steer traffic on 1 2
post-convergence path  <Prefix-
SID(R4)>
prefix-SID(R4)
• Also known as “PQ-node”
prefix-SID(Z) 5
• R1 will push the prefix-SID of R4 prefix-SID(Z)
Packet to Z
on the backup path Packet to Z
4 3
Default metric:10
TI-LFA – Double-Segment Example
A Z
• TI-LFA for link R1R2 on R1 prefix-SID(Z)
Packet to Z Packet to Z
• Calculate post-convergence SPT
1 2
• Derive SID-list to steer traffic on post-
convergence path  <Prefix-SID(R4), prefix-SID(R4)
Adj-SID(R4-R3) adj-SID(R4-R3)
5
• Also known as “P- and Q-node” prefix-SID(Z) prefix-SID(Z)
Packet to Z Packet to Z
• R1 will push the prefix-SID of R4 and
the adj-SID of R4-R3 link on the 4
R4 3
R3
1000
backup path
adj-SID(R4-R3) Default metric: 10
prefix-SID(Z)
Packet to Z
Traffic Engineering
(SR-TE)
Traffic Engineering with Segment Routing
• Provides explicit routing
Segment
• Supports constraint-based routing Routing
• Supports centralised admission control
• Uses existing ISIS / OSPF extensions to
advertise link attributes
• No RSVP-TE to establish LSPs
• Supports ECMP
TE LSP
segment-routing
Node1
traffic-eng
Low Latency policy POLICY1
color 20 end-point ipv4 1.1.1.3
T:15 T:15
I:10 I:10
candidate-paths
1 2 3 preference 100
T:8 dynamic mpls
SID-list: <16005, 16004, 16003> I:10 metric
T:10 type te
I:30
5 4
Default IGP link metric: I:10

Default TE link metric: T:10 6
• Head-end computes a SID-list that expresses the shortest-path according to the

selected metric
segment-routing
Node1
traffic-eng
policy POLICY1
Service Disjointness color 20 end-point ipv4 1.1.1.3
candidate-paths
preference 100
XTC XTC dynamic mpls pce
metric
type igp
1 2 3 association group 1 type node
SID-list: I:100 I:100
{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
6 7 8 dynamic mpls pce
SID-list: I:100 I:100 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
Per VPN Topology
I: 50
2 4
1 CE Basic VPN should
T: 15
use lowest cost
6 5 underlay path
IGP cost 30
Default IGP cost: I:10 Objective:
Default TE cost: T:10 operationalise this
service for simplicity,
TE cost 20 scale and
I: 50 performance
2 4
Premium VPN
1 CE should use lowest
T: 15 latency path
6 5
Default IGP cost: I:10

Default TE cost: T:10 BRKRST-1124 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 51
On-Demand SR Policy work-flow
➎
➌ BGP: 20/8 via PE4
router bgp 1
neighbor 1.1.1.10 VPN-LABEL: 99999
Low-latency (color 20) ➋ BGP: 20/8 via PE4
address-family vpnv4 unicast RR VPN-LABEL: 99999
!
Low-latency (color 20)
segment-routing
traffic-eng
on-demand color 20 ➍ PE4 with Low-
preference 100 latency (color 20)? I: 50 ➊ BGP: 20/8 via
SR Policy template 2 4
metric CE
type te
Low-latency (color 20) ➎ use template
1 CE 20/8
color 20
➏  SID-list T: 15
6 5
<16002, 30204>
Default IGP cost: I:10

Default TE cost: T: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-
latency (color 20)? ➐ I: 50 ➊ BGP: 20/8 via
Forwarding table on Node1 2 4 CE
➎ use template
In Out Out_intf Fraction 1 CE 20/8
color 20
➏  SID-list T: 15
4001 <16002, 30204> To Node 2 100% 6 5
<16002, 30204>
➐ instantiate
SR Policy Default IGP cost: I:10
BSID 4001 Default TE cost: T:10
➑ forward 20/8
via BSID 4001
SR-TE
• Simple, Automated and Scalable
• No core state: 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
• Binding-SID (BSID) for scale
• Lots of Functionality
• Designed with lead operators along their use-cases
Bits and Bites
Binding SID for Stitching
BSID: BSID:
30410 30710
1 2 3 4 5 6 7 8 9 10
All Nodes SRGB [16,000-23,999]

16003 16006
14 Prefix-SID NodeX: 1600X
16004 16004 16007 16007 16009
Binding-SID XY: 300XY
410 30410 30410 30410 30710 30710 30710 16010 16010
Node 10 Node 10 Node 10 Node 10 Node 10 Node 10 Node 10 Node 10 Node 10
• Assume Node1 can’t push 8 labels to go to Node10

• “Compress” label stack by stitching SRTE Policies:
• Node1 pushes:
• 2 labels to go to Node4
• Binding-SID to go to Node10
• Node4 pops Binding-SID and pushes:
• 2 labels to go to Node7
• Binding-SID to go to Node10
• Node7 pops Binding-SID and pushes 2 labels to go to Node10
Presentation ID © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 57
SRv6 – Segment Routing & IPv6
• Simplicity
• Protocol elimination
• SLA
• FRR and TE
SRv6 for anything else • Overlay
• NFV
IPv6 for reach
• SDN
• SR is de-facto SDN architecture
• 5G Slicing
IPv6 Data Plane
• Segment Routing applies to both IPv6 and MPLS dataplanes
• Difference is in the bits encoded in the packet not in the architecture
• Enabling SR-IPv6, means that ONLY the nodes that have to process the packet
header must have SR-IPv6 dataplane support
• All other nodes in the infrastructure are just plain IPv6 nodes
IPv6 Hdr Label(C)

Label(F)
SR Header
B C D Label(H)
Segments: C,F,H
A H IPv4 or IPv6 hdr
E F G
PAYLOAD PAYLOAD
SR-IPv6 SR-MPLS
Network Instruction
Locator Function(arg)
Function
• 128-bit SRv6 SID

• Locator: routed to the node performing the function
• Function: any possible function (optional argument) either local to NPU or app in
VM/Container
• Flexible bit-length selection
Network Program
Next Segment Locator 1 Function 1
Locator 2 Function 2
SRv6
• 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
• Incremental deployment
• Also protects LDP and unlabeled traffic
Does it Work for Multicast?
• Source Routing a packet is not possible for Multicast!
• Parsing a sequential list of hops does not allow to represent a replication.
Source R1
SD C
A B
X
S D {E,C,B}
S D {C,E,B}
?
?
E
BRKRST-1124
R2
R2
Solutions for Multicast
• There is no exact solution for Multicast that is like Unicast SR.
• Depending on the requirements, we can choose the best fit from the following
options:
1. Deploy traditional Multicast Solutions
• PIM
• mLDP
• RSVP-TE
• Ingress Replication
2. TreeSID – a controller based solution - new
3. Bit Index Explicit replication (BIER)
4. Do I even need it? SR Spray – new
Tree Segment Identifier (TreeSID)
• TreeSID is a SDN controller based approach to building P2MP trees.
• Due to the controller, the tree can be built using any constraint (like P2MP
RSVP-TE).
• A TreeSID identifier can be a:
• IPv4/IPv6 Source and Group (S,G)
• A name string
• A numeric value
TreeSID Labels
Source Static Labels R1

C
Label 14000
A B
R2
R2
E
Source Dynamic Labels R1

C
Label 16
A B
R2
R2
E
Presentation ID © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 67
GW1 WIFI
TV-1
C::1 DD::
SR Spray
Spray Policy 1: <A2::0, A4::0, M1, DD::> CMTS4 WIFI
4 DD::
Spray Policy 2: <A3::0, A5::0, M1, DD::>
Unicasted 2
GW3 WIFI TV-3
Content VPP1 C::3 DD::
Provider B::1
WIFI
Replicate traffic to every CMTS 3 DD::
through TE-Engineered core path CMTS5
then to access mcast tree 5
then to anycast TV GW5 WIFI
TV-5
C::5 DD::
Peering to Content Provider SRv6 domain (Unicast) Multicast domain Anycast
SRv6 node Non SRv6 node Subscribed to M1 channel
Flexible, SLA-enabled and Efficient content injection without multicast core

Conclusion
Conclusion
• Simple routing extensions to implement source routing
• Packet path determined by prepended segment identifiers (one or more)
• Data plane agnostic (MPLS, IPv6)
• Increase network scalability and agility by reducing network state and
simplifying control plane
• Traffic protection with 100% coverage with more optimal routing
• Segment Routing sounds better with an Italian accent
Stay Up-To-Date
http://www.segment-routing.net/
https://www.linkedin.com/groups/8266623
https://twitter.com/SegmentRouting
https://www.facebook.com/SegmentRouting/ amzn.com/B01I58LSUO
Participate in the “My Favorite Speaker” Contest
Promote Your Favorite Speaker and You Could Be a Winner
• Promote your favorite speaker through Twitter and you could win $200 of Cisco
Press products (@CiscoPress)
• Send a tweet and include
• Your favorite speaker’s Twitter handle @wozzit
• Two hashtags: #CLUS #MyFavoriteSpeaker
• You can submit an entry for more than one of your “favorite” speakers
• Don’t forget to follow @CiscoLive and @CiscoPress
• View the official rules at http://bit.ly/CLUSwin
Continue Your Education
• Demos in the Cisco campus
• Walk-in Self-Paced Labs
• Table Topics
• Meet the Engineer 1:1 meetings
• Related sessions
Q&A
Complete Your Online
Session Evaluation
• Give us your feedback and
receive a Cisco Live 2018 Cap
by completing the overall event
evaluation and 5 session
evaluations.
• All evaluations can be completed
via the Cisco Live Mobile App.
Don’t forget: Cisco Live sessions will be
available for viewing on demand after the
event at www.CiscoLive.com/Global.
Thank you
Backup Slides
BRKRST-1124

Segment Routing-Cisco Live

Uploaded by

Copyright:

Available Formats

Segment Routing-Cisco Live

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-Cisco Live

Uploaded by

Copyright:

Available Formats

Introduction to

Previous knowledge of IP routing and MPLS is required.

• Why Should I Care?

• Network Hand-Offs are Complex and Costly

• NOT THE SERVICE LAYER – EVPN FOR THAT

Unified IP/MPLS ACE

Simplified control plane (distributed on router)

Metro & Access

• 6MAN IS-IS Extensions for Segment Routing

• Segment: an identifier for any type of instruction

IS-IS Configuration – Example

OSPF Configuration Example

Payload Payload Payload Payload

Push Swap Pop Pop

Payload Payload Payload Payload Payload

Payload Payload Payload Payload Payload

• LFIB populated by IGP (ISIS / OSPF) PE PE

• Other protocols (LDP, RSVP, BGP) can PE PE

• R1 will steer the traffic towards LFA Packet to Z

• Calculate post-convergence SPT Packet to Z

Default IGP link metric: I:10

• Head-end computes a SID-list that expresses the shortest-path according to the

Default IGP cost: I:10

Default IGP cost: I:10

Low Latency to PE4

All Nodes SRGB [16,000-23,999]

• Assume Node1 can’t push 8 labels to go to Node10

IPv6 Hdr Label(C)

• 128-bit SRv6 SID

Source Static Labels R1

Source Dynamic Labels R1

Peering to Content Provider SRv6 domain (Unicast) Multicast domain Anycast

SRv6 node Non SRv6 node Subscribed to M1 channel

Flexible, SLA-enabled and Efficient content injection without multicast core

You might also like