Application Engineered

Routing with Segment

Routing
Pedro Sanchez, Solutions Integration Architect
BRKRST-2789
Agenda
• Application Engineered Routing
• Segment Routing Overview
• Use Cases
• A Closer Look to Control and Data Plane
• Traffic Protection
• Traffic Engineering
• Conclusion
Application Engineered
Routing
The Problem
The Network is facing new challenges
Cloud
services
Mobility IoE

4K Others
Increasingly diverse
applications

Dynamic and changing New constraints on the Application-specific

traffic patterns Network transport requirements

E2E control required

IPv6

NETWORK FABRIC
Networks need to be rethought
Applications and Network interaction is key

IP APPLICATIONS
Core

Edge

EVOLVED SERVICES PLATFORM

Acce
ss/
Agg

IPv6

EVOLVED PROGRAMMABLE NETWORK

IP NGN Era

Designed to support a set of services Designed to support any kind of services

Static traffic patterns Dynamic traffic patterns

Manual configuration (CLI) Automation (APIs, Controllers, …)

Apps Independent of Network App & Network Interaction

Specific approaches to the problem
A continuum of enhanced solutions

Hosts DC Core Agg Hosts DC Core Agg Hosts DC Core Agg

One device, single domain Many devices, single domain Many devices, across domains

IP NGN Era EPN Era

Policy-Based routing MPLS TE

Evolution  Scalable
required to
Effective solutions with some caveats: address the  Stateless
new paradigm
 Little or no application / network interaction
 Scalability  Programmable
 Configuration & troubleshooting complexity
 States to be maintained in each network node  Ease of configuration &
troubleshooting
 Applications & Network Interaction
Implications for the Network Fabric
Many applications with
dynamic and changing traffic patterns

IP Networks IP Networks & Traffic Engineering

Limitations
 Limited to a single network  Impediment to service
domain creation
 Scalability
 Configuration &  Major scalability issues
troubleshooting complexity
 States to be maintained in  Operational challenges
Shortest path with QoS Traffic-engineered tunneling each network node

IP Networks Evolution
 The solution
Application Engineered Routing

Applications express Applications are mapped to a path

requirements – Applications defined by a list of segments
1
bandwidth, latency, SLAs

3
SDN
Controller

2 Segment
The network only maintains segments
SDN controllers are capable of Routing
No application state
collecting data from the network – (SW upgrade)

topology, link states, link

utilization, …
Application Engineered Routing – Phase 1
Evolve MPLS with Segment Routing

No control over the path –

Mission – Route the Luggage is routed over the shortest path
luggage to Berlin

London
Toronto
Seattle Berlin

IP/LDP
New-York Madrid

Mexico
TLX

A luggage tag is
TLX
attached with the
final destination Luggage identified
and routed to next
destination

draft-ietf-spring
Application Engineered Routing – Phase 1
Evolve MPLS with Segment Routing
Path can be controlled
Complexity and scalability
Mission – Route the
issues
luggage to Berlin via
Mexico and Madrid

London
Toronto
Seattle Berlin

RSVP-TE New-York Madrid

Mexico
20000
20000

20000
A specific luggage tag, Tunnel ID 20000,
At each stop, the luggage is is created to identify the path Seattle-
identified and routed to next Mexico-Madrid-Berlin
hop
A list of all the paths has to be
maintained
Application Engineered Routing – Phase 1
Evolve MPLS with Segment Routing

Path can be controlled

Mission – Route the It is simple and scalable
luggage to Berlin via
Mexico and Madrid

London
Toronto
Seattle Berlin

Segment
Routing New-York Madrid

MEX Mexico

MAD
MEX
TXL
MAD
MEX
TXL
A unique and global luggage
MAD
tag is attached to the luggage
with the list of stops to the final TXL
destination
At each stop, the luggage is
simply routed to the next hop
listed on the luggage tag
Application Engineered Routing Phase 1
Segment Routing – Technical view

Data Plane
Path expressed in the packet Data
MPLS IPv6
Dynamic path (segment labels) (+SR header)

Control Plane

Routing protocols with

extensions SDN controller
(IS-IS,OSPF, BGP)

Explicit path

Paths options

Dynamic Explicit
(STP computation) (expressed in the packet)
Segment Routing
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 without any further
per-flow state
• Segment: an identifier for any type of instruction
• forwarding or service
IGP Prefix Segment

• Shortest-path to the IGP prefix

• Global
12
• 16000 + Index
10
2 4
• Signaled by ISIS/OSPF
1
7
13 16005

3 6 5

11
14
DC (BGP-SR) WAN (IGP-SR) PEER
IGP Adjacency Segment

• Forward on the IGP adjacency

• Local
12 124
• 1XY
10
• X is the “from” 2 4
• Y is the “to”
1
7
• Signaled by ISIS/OSPF 13

3 6 5

11
14
DC (BGP-SR) WAN (IGP-SR) PEER
BGP Prefix Segment

• Shortest-path to the BGP prefix

• Global 16001
12
• 16000 + Index
10
2 4
• Signaled by BGP
1
7
13

3 6 5

11
14
DC (BGP-SR) WAN (IGP-SR) PEER
BGP Peering Segment

• Forward to the BGP

peer
• Local 12 147 Low Lat,
10 Low BW
• 1XY 2 4
• X is the “from”
1
• Y is the “to” 7
13
• Signaled by BGP-LS
3 6 5
(topology information) High Lat, High BW

to the controller 11
14
DC (BGP-SR) WAN (IGP-SR) PEER
WAN Controller
BGP-LS
• WAE collects via BGP-LS BGP-LS
• IGP segments
BGP-LS
• BGP segments
• Topology 12
10
2 4 Low Lat, Low BW

1
7
13

3 6 5

11
14
DC (BGP-SR) WAN (IGP-SR) PEER
An end-to-end path as a list of segments
PCEP, Netconf,
BGP
• WAE computes that
the green path can be
encoded as
• 16001 12
{16001,
16002, 10
• 16002
124, 2 50
4 Low Lat, Low BW

• 124 147}
1
• 147 7
13
• WAE programs a
single per-flow state 3 6 5
to create an
11
application-
engineered end-to- 14
Default ISIS cost metric: 10
end policy DC (BGP-SR) WAN (IGP-SR) PEER
Segment Routing Standardization
• IETF standardization in SPRING
working group
• Protocol extensions progressing in
multiple groups
• IS-IS
Sample IETF Documents
Segment Routing Architecture
(draft-ietf-spring-segment-routing)
Problem Statement and Requirements
(draft-ietf-spring-problem-statement)
IPv6 SPRING Use Cases
(draft-ietf-spring-ipv6-use-cases)
Segment Routing Use Cases
(draft-filsfils-spring-segment-routing-use-cases)

• OSPF Topology Independent Fast Reroute using Segment Routing

(draft-francois-spring-segment-routing-ti-lfa)
• PCE IS-IS Extensions for Segment Routing
(draft-ietf-isis-segment-routing-extensions)
• IDR
OSPF Extensions for Segment Routing
• 6MAN (draft-ietf-ospf-segment-routing-extensions)
PCEP Extensions for Segment Routing
• Broad vendor and customer support (draft-ietf-pce-segment-routing)

Close to 30 IETF drafts in progress

Segment Routing Product Support

• Platforms: ASR9000, CRS-1/CRS-3 (shipping)

• IS-IS IPv4 / IPv6 (shipping)
• Node/Adjacency SID advertisement
• LDP interworking (mapping server/client)
• Traffic protection (topology independent LFA link protection)

• OSPFv2 (shipping)
• Node SID advertisement
• Traffic protection (LFA)

• Upcoming
• SR Traffic Engineering (manual provisioning and PCEP)
• OAM (Ping/Trace)
• IOS XE Support (ASR1000, ASR902, ASR903, ISR4400)
Use Cases
IPv4/6 VPN/Service transport 16007
vpn
pkt
• IGP only
2 3 vpn
• No LDP, no RSVP-TE
pkt
• ECMP
1 4 7
pkt
pkt
6 5
Site1 Site2
16007
vpn
pkt
Seamless interworking with LDP
16007
vpn
• Seamless deployment
pkt LDP(7)

vpn
2 3 vpn
pkt
pkt

1 4 7
pkt
pkt
6 5
Site1 Site2
16007
vpn
pkt
Topology-Independent LFA (TI-LFA FRR)

• 50msec FRR in any topology

7
• IGP Automated
2 3
• No LDP, no RSVP-TE 16007
• Optimum pkt
1 4
• Post-convergence path

• No midpoint backup state 16007

6 5
• Detailed operator report pkt
• S. Litkowski, B. Decraene, Orange
16005
• Mate Design
16007
• How many backup segments
• Capacity analysis
pkt
Automated Traffic Matrix Collection
1 2 3 4

• Traffic Matrix is fundamental for 2

• capacity planning 3

• centralized traffic engineering 4

• IP/Optical optimization
2
• Most operators do not have an
accurate traffic matrix
• With SR, the traffic matrix 1 3
collection is automated

4
Optimized Content Delivery
7
AS7
• On a per-content, per-user basis,
the content delivery application
can engineer 16003 5 6
• the path within the AS 16002 AS5 AS6
• the selected border router 126
• the selected peer pkt
1 2
• Also applicable for engineering
egress traffic from DC to peer
• BGP Prefix and Peering Segments
4 3
AS1
Application Engineered Routing
Low-Latency to 7
for application A12
PeerSID: 147, Low Lat, Low BW

• Per-application PeerSID: 147, High Lat, High BW

flow engineering Low-Lat to 4

BSID: 200

• End-to-End
12
• DC, WAN, AGG, PEER
10 ISIS: 35
Push
{16001,
2 4 Low Lat, Low BW

• Millions of flows 200, 147}

• No signaling 1
200: pop 7
and push
• No midpoint state 13 {16002,
16004}
• No reclassification at
boundaries 3 6 5

11
Default ISIS cost metric: 10
14 Default Latency metric: 10
DC (or AGG) WAN PEER
Application Engineered Routing
Low-Latency to 7,
DC Plane 0 only,
for application A12 PeerSID: 147, Low Lat, Low BW

• Per-application PeerSID: 147, High Lat, High BW

flow engineering Low-Lat to 4

BSID: 200

• End-to-End
12
• DC, WAN, AGG, PEER
10 ISIS: 35
Push
{16010,
2 4 Low Lat, Low BW

• Millions of flows 16001,

• No signaling 200, 147} 1
200: pop 7
and push
• No midpoint state 13 {16002,
16004}
• No reclassification at
boundaries 3 6 5

11
Default ISIS cost metric: 10
14 Default Latency metric: 10
DC (or AGG) WAN PEER
A Closer Look to Control
and Data Plane
MPLS Control and Forwarding Operation with Segment
Routing
Services
BGP / LDP
No changes to
IPv4 IPv6
IPv4 IPv6 VPWS VPLS control or
PE1 PE2 VPN VPN
forwarding plane

Packet
Transport LDP RSVP BGP Static IS-IS OSPF IGP label
distribution for IPv4
PE1 IGP PE2
and IPv6, same
MPLS Forwarding
forwarding plane
SID Encoding

• Prefix SID
• SID encoded as an index SR-enabled Node
• Index represents an offset from SRGB base
• Index globally unique
• SRGB may vary across LSRs
• SRGB (base and range) advertised with
router capabilities SRGB = [ 16000 - 23999 ]. Advertised as base = 16,000, range = 7,999
Prefix SID = 16041. Advertised as Prefix SID Index = 41
• Adjacency SID Adjacency SID = 24000. Advertised as Adjacency SID = 24000

• SID encoded as absolute (i.e. not indexed)

value
• Locally significant
• Automatically allocated for each adjacency
SR IS-IS Control Plane Overview

• Level 1, level 2 and multi-level routing

• Prefix Segment ID (Prefix-SID) for host prefixes on loopback interfaces
• Adjacency SIDs for adjacencies
• Prefix-to-SID mapping advertisements (mapping server)
• MPLS penultimate hop popping (PHP) signaling
• MPLS explicit-null label signaling
IS-IS Configuration

• Required
• Wide metrics
• SR enabled under unicast address family

• Optional
• Prefix-SID configured under loopback(s) AF IPv4
• MPLS forwarding enabled automatically on all (non-passive) IS-IS
interfaces
• Adjacency-SIDs are automatically allocated for each adjacency
SR OSPF Control Plane Overview

• IPv4 Prefix Segment ID (Prefix-SID) for host prefixes on loopback

interfaces
• MPLS penultimate hop popping (PHP) signaling
• MPLS explicit-null label signaling
OSPF Configuration

• OSPFv2 control plane

• Required
• Enable segment-routing under instance or area(s)
• Command has area scope, usual inheritance applies
• Enable segment-routing forwarding under instance, area(s) or interface(s)
• Command has interface scope, usual inheritance applies

• Optional
• Prefix-SID configured under loopback(s)
• MPLS forwarding enabled on all OSPF interfaces with
segment-routing forwarding configured
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 Y Y Y

Payload Payload Payload Payload

• Packet forwarded along IGP shortest path (ECMP)
• Swap operation performed on input label
• Same top label if same/similar SRGB
• PHP if signaled by egress LSR
 Packet forwarded along IGP adjacency
 Pop operation performed on input label
 Top labels will likely differ
 Penultimate hop always pops last adjacency SID
MPLS Data Plane Operation (Prefix SID)

SRGB [16,000 – 23,999 ] SRGB [16,000 – 23,999 ] SRGB [26,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 26041
VPN Label VPN Label VPN Label

Payload Payload Payload Payload Payload

MPLS Data Plane Operation (Adjacency SIDs)
MPLS Label Range MPLS Label Range MPLS Label Range MPLS Label Range
[ 24000– 265535 ] [ 24000– 265535 ] [ 24000– 265535 ] [ 24000– 265535 ]
A B C D
Adjacency Adjacency Adjacency
SID = 24010 SID = 24000 SID = 24000
Push Pop Pop Pop
Push
Push
24000
24000 24000
VPN Label VPN Label VPN Label

Payload Payload Payload Payload Payload

MPLS LFIB with Segment Routing
PE PE

• LFIB populated by IGP (ISIS / PE PE

OSPF)
PE PE
P

• Forwarding table remains PE PE

constant (Nodes + Adjacencies)

regardless of number of paths In Out Out
Label Label Interface
L1 L1 Intf1
• Other protocols (LDP, RSVP, Network
Node L2 L2 Intf1 Forwarding
BGP) can still program LFIB 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 and node 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 traffic
Topology Independent LFA – Implementation

• Leverages existing and proven LFA technology

• P space: set of nodes reachable from node S (PLR) without using protected link L
• Q space: set of nodes that can reach destination D without using protected link L

• Enforcing loop-freeness on post-convergence path

• Where can I release the packet?
At the intersection between the post-convergence shortest path and the Q space
• How do I reach the release point?
By chaining intermediate segments that are assessed to be loop-free
TI-LFA – Zero-Segment Example
A Z
• TI-LFA for link R1R2 on R1
Packet to Z Packet to Z

• Calculate LFA(s) R1 R2

• Calculate post-convergence SPT 1000

R5
• Find LFA on post-convergence prefix-SID(Z)
SPT Packet to Z
R4 R3

• R1 will steer the traffic towards

LFA R5
Default metric:10
TI-LFA – Single-Segment Example
A Z
• TI-LFA for link R1R2 on R1
Packet to Z Packet to Z

• Calculate P and Q spaces R1 R2

• They overlap in this case P-space

• Calculate post-convergence SPT prefix-SID(R4) R5

prefix-SID(Z)
prefix-SID(Z)
• Find PQ node on post- Packet to Z
Packet to Z

convergence SPT R4 R3

Q-space
• R1 will push the prefix-SID of R4
Default metric:10
on the backup path
TI-LFA – Double-Segment Example
A Z
• TI-LFA for link R1R2 on R1
Packet to Z Packet to Z

• Calculate P and Q spaces R1 R2

• Calculate post-convergence SPT prefix-SID(R4)

adj-SID(R4-R3)
R5
• Find Q and adjacent P node on prefix-SID(Z) prefix-SID(Z)
Packet to Z
post-convergence SPT Packet to Z

R4 R3

• R1 will push the prefix-SID of R4 1000

P-space Q-space
and the adj-SID of R4-R3 link on adj-SID(R4-R3)
Default metric:10
the backup path prefix-SID(Z)
Packet to Z
Traffic Engineering
Traffic Engineering with Segment Routing

• Provides explicit routing Segment

• Supports constraint-based Routing
routing
• Supports centralized admission
control
• No RSVP-TE to establish LSPs
• Uses existing ISIS / OSPF
extensions to advertise link
attributes
• Supports ECMP
TE LSP
How Traffic Engineering Works
Head end
• Link information Distribution
IP/MPLS • ISIS-TE
• OSPF-TE
• Path Calculation
• Path Setup
• Forwarding Traffic down path
• Auto-route (announce / destinations)
• Static route
• PBR
• PBTS / CBTS
Mid-point Tail end • Forwarding Adjacency
• Pseudowire Tunnel select
TE LSP
Stateful PCE
Stateful PCE

• PCE maintains topology and path LSP DB

database (established paths)
TED
• More optimal centralized path
computation
PCEP
• Enables centralized path initiation
and update control
PCC
• Well suited for SDN deployments
Topology Acquisition

• An external PCE requires some form PCE

of topology acquisition TED
• A PCE may learn topology using
BGP-LS, IGP, SNMP, etc.
BGP-LS
• BGP-LS characteristics
• aggregates topology across one or more Domain 0 RR
domains
• provides familiar operational model BGP-LS BGP-LS
• New BGP-LS attribute TLVs for SR
• IGP: links, nodes, prefixes
Domain 1 Domain 2
• BGP: peer node, peer adjacency, peer set
Active Stateful PCE

• PCC or PCE may initiate path Active Stateful PCE

setup PCE has update
LSP DB
control over
• PCC may delegate update delegated paths
TED
control to PCE
• PCC may revoke delegation PCEP

• PCE may return delegation

Stateful
PCC
Active Stateful PCE
PCE-Initiated and PCC-Initiated LSPs
PCE-Initiated (Active Stateful PCE) PCC-Initiated (Active Stateful PCE)

PCE initiates LSP DB LSP DB

LSP and PCC initiates
maintains TED LSP and TED
update control delegates
update
PCEP control PCEP

Stateful Stateful
PCC PCC

• PCE part of controller architecture managing  PCC may initiate path setup based on
full path life cycle distributed network state
• Tighter integration with application demands  Can be used in conjunction with PCE-
initiated paths
PCE Extensions for Segment Routing (SR)
Stateful PCE
• Segment routing enables source routing Application LSP DB
Path
based on segment ids distributed by IGP Request
TED
• PCE specifies path as list of segment ids
PCEP
• PCC forwards traffic by pushing segment id Segment List:: 10,20,30,40
list on packets
• No path signaling required Stateful
PCC
• Minimal forwarding state
• Maximum network forwarding virtualization
• The state is no longer in the network but in In Out Int
the packet L1 L1 Intf1 Forwarding
Node
… … … table remains
• Paths may be PCE- or PCC-initiated SID
L7 L7 Int3 constant
L8 Pop Intf3
Adjacency
… … …
SID
L9 Pop Intf5
Conclusion
Application Engineered Routing
Solution components
Network Bandwidth Low-latency Disjoint
3rd-party applications
Applications calendaring path selection recovery path

Northbound
RESTful APIs
interfaces

3rd-party
ESP WAE NSO VTS
controller

Southbound Netconf/Yan
BGP LS PCEP Configlets
interfaces g

Segment Routing (SR) across Cisco platforms

ASR 9K ASR 1K
NEXUS 3rd-party platforms
VNF
EPN 9000 supporting SR
NCS 6K … … …
Physical Virtual
Application Engineered Routing journey
Adding value at your own pace
Phase 1 - Evolve Phase 2 - Exceed Phase 3 - Expand

Enable Segment Routing on EPN Enable Segment Routing on EPN Enable Segment Routing on EPN
platforms (SW only) platforms (SW only) platforms (SW only)

Insert ESP components – Insert ESP components –

Orchestration, SDN controller Orchestration, SDN controller

Connect with Cisco’s and third

party VNFs

Benefits Benefits Benefits

Network Network Network Network Network Network
simplification resiliency simplification resiliency simplification resiliency

End-User End-User Network End-User Network

experience experience optimization experience optimization

Service E2E application

velocity control

Today 6-12 months 12-18 months

Thank you
Backup Slides
Configuring Segment Routing for IPv4 Using IS-IS
(Cisco IOS XR)
router isis DEFAULT
net 49.0001.1720.1625.5001.00
address-family ipv4 unicast
Enable Segment Routing for IPv4 with
metric-style wide
segment-routing mpls MPLS data plane
!
interface Loopback0
passive Advertise prefix SID 16041 (index 41) for
address-family ipv4 unicast
Loopback0
prefix-sid absolute 16041
!
!
interface GigabitEthernet0/0/0/0
point-to-point
address-family ipv4 unicast
!
!
!
Configuring Segment Routing for IPv6 Using IS-IS
(Cisco IOS XR)
router isis DEFAULT
net 49.0001.1720.1625.5001.00
address-family ipv6 unicast
Enable Segment Routing for IPv6 with
metric-style wide
segment-routing mpls MPLS data plane
!
interface Loopback0
passive Advertise prefix SID 16061 (index 61) for
address-family ipv6 unicast
Loopback0
prefix-sid absolute 16061
!
!
interface GigabitEthernet0/0/0/0
point-to-point
address-family ipv6 unicast
!
!
!
Configuring Segment Routing for IPv4 Using OSPF
(Cisco IOS XR)
router ospf DEFAULT
router-id 172.16.255.1
segment-routing mpls
Enable Segment Routing with MPLS data
segment-routing forwarding mpls
area 0 plane
interface Loopback0
passive
prefix-sid absolute 16041 Advertise prefix SID 16041 (index 41) for
!
Loopback0
interface GigabitEthernet0/0/0/0
network point-to-point
!
!
!
Configuring Topology Independent Fast Reroute for IPv4
using Segment Routing and IS-IS (Cisco IOS XR)
router isis DEFAULT
net 49.0001.1720.1625.5001.00
address-family ipv4 unicast
metric-style wide
segment-routing mpls
!
interface Loopback0
passive
address-family ipv4 unicast
prefix-sid absolute 16041
!
!
interface GigabitEthernet0/0/0/0
address-family ipv4 unicast
fast-reroute per-prefix
fast-reroute per-prefix ti-lfa Enable TI-LFA for IPv4 prefixes on
! interface GigabitEthernet0/0/0/0
!
!
Configuring Topology Independent Fast Reroute for IPv6
using Segment Routing and IS-IS (Cisco IOS XR)
router isis DEFAULT
net 49.0001.1720.1625.5001.00
address-family ipv6 unicast
metric-style wide
segment-routing mpls
!
interface Loopback0
passive
address-family ipv6 unicast
prefix-sid absolute 16061
!
!
interface GigabitEthernet0/0/0/0
address-family ipv6 unicast
fast-reroute per-prefix
fast-reroute per-prefix ti-lfa Enable TI-LFA for IPv6 prefixes on
! interface GigabitEthernet0/0/0/0
!
!
Configuring a Mapping Server for SR and LDP
Interworking for IPv4 Using IS-IS (Cisco IOS XR)
router isis DEFAULT
net 49.0001.1720.1625.5001.00
address-family ipv4 unicast Construct active mapping policy using
metric-style wide
remotely learned and locally configured
segment-routing mpls
segment-routing prefix-sid-map receive mappings (mapping client)
segment-routing prefix-sid-map advertise-local
! Advertise local mapping policy (mapping
server)
...

!
segment-routing Local prefix-to-SID mapping policy
address-family ipv4
prefix-sid-map
172.16.255.1/32 – 4041
172.16.255.1/32 4041 range 8 :
! 172.16.255.8/32 - 4048
!
!
Configuring a Mapping Client for SR and LDP
Interworking for IPv4 Using IS-IS (Cisco IOS XR)
router isis DEFAULT
net 49.0001.1720.1625.5001.00
address-family ipv4 unicast
metric-style wide
segment-routing mpls
segment-routing prefix-sid-map receive Construct active mapping policy using
!
remotely learned and locally configured
interface Loopback0
passive mappings (mapping client)
address-family ipv4 unicast
prefix-sid absolute 16041
!
!
interface GigabitEthernet0/0/0/0
point-to-point
address-family ipv4 unicast
!
!
!