Converged SDN Transport For CCIE SPv5 v202104
Converged SDN Transport For CCIE SPv5 v202104
© 2021
Joël François, IT Network Architect (CCIE R&S #55635)
https://www.linkedin.com/in/joël-françois-4293b937
Converged SDN Transport (CST) architecture is also presented in next chapter. In April
2021, CST is the latest Cisco operational model that provides simplicity, programmability
and automation for Service Providers. Interestingly, that model fully align with the CCIE
SP exam blueprint. Labs and tasks were written with that model in mind.
The workbook contains 5 labs (Lab 1 to Lab 5) composed of many tasks. All the labs must
be completed sequentially.
Chapter 10 is presenting the key takeaways of all the labs, with a synthesis of the Cisco
network simplification journey we experienced as we go through the implementations.
CML and EVE-NG topology files with initial configuration, software images, diagrams,
tables and figures are provided to follow the labs.
Value proposition
Service Providers are facing the challenge to provide next generation services that can
quickly adapt to market needs. New paradigms such as 5G introduction, video traffic
continuous growth, IoT proliferation and cloud services model require unprecedented
flexibility, elasticity and scale from the network. Increasing bandwidth demands and
decreasing *ARPU put pressure on reducing network cost. At the same time, services need
to be deployed faster and more cost effectively to stay competitive.
Metro Access and Aggregation solutions have evolved from native Ethernet/Layer 2
based, to Unified MPLS to address the above challenges. The Unified MPLS architecture
provides a single converged network infrastructure with a common operational model. It
has great advantages in terms of network convergence, high scalability, high availability,
and optimized forwarding. However, that architectural model is still quite challenging to
manage, especially on large-scale networks, because of the large number of distributed
network protocols involved which increases operational complexity.
The Converged SDN Transport design brings tremendous value to Service Providers:
• Fast service deployment and rapid time to market through fully automated service
provisioning and end-to-end network programmability
The Converged SDN Transport design is targeted at Service Provider customers who:
Summary
The Converged SDN Transport design satisfies the following criteria for scalable next-
generation networks:
• Simple: based on Segment Routing as unified forwarding plane and EVPN and
L3VPN as a common BGP based services control plane
• Automated : Service provisioning is fully automated using NSO and YANG models;
Analytics with model driven telemetry in conjunction with Crosswork Network
Insights to enhance operations and network visibility
https://xrdocs.io/design/
Topology overview
Below is the main topology we will use as reference throughout the workbook.
The Service Provider’s network consists of 3 IGP domains, including 2 access domains
running OSPF and a dual-plane Core domain running ISIS.
There are 4 customers spread over 8 sites in West and East regions. We will implement
Carrier Ethernet services for customer 1 and 4, and L3VPN services for customer 2 and 3.
Lab topology has 30 NFV platforms in total, including 28 routers and 2 switches. This
represents 48 links and 185 interfaces. NFV platforms are described in upcoming section.
Lab is setup and validated using Cisco CML (Personal 2.1 40 Node) and EVE-NG Pro
installed as a VM on a ESXI 6.7.0 hypervisor and hosted on a Dell PowerEdge T430.
Once fully loaded, the lab consumes around 8 vCPU and 80GB RAM.
For most of the XR devices, choice was to go with IOS XRv rather than XR9000v in the
objective to save overall resources (IOS XRv are able to return IDLE CPU to hypervisor).
There are 2 Access PE running XR9000v. Unlike XRv, XR9000v allows some technologies
to work in dataplane like L2VPN or BFD, etc.
Choice was made to use only physical interfaces to interconnect the routers for scalability
and performance reasons.
Zone Node IP
Core 10.X.Y.Z/24
Access 1 20.X.Y.Z/24
Access 2 30.X.Y.Z/24
Customer West 40.X.Y.Z/24
Customer East 50.X.Y.Z/24
X=Lower Node ID
Y=Higher Node ID
Z=Node ID
2.4 L3VPN
2.4.a. Design, deploy, and optimize L3VPN
2.4.d. Design, deploy, and optimize L3VPN service auto steering into segment routing
policy
* In this version of the workbook, we will only test the Carrier Ethernet technologies that
are supported in both control-plane and data-plane.
Objective
This Unified MPLS design mimics a large scale SP network. We will configure IGP and
LDP along with LFA in each domain, and enable BGP label exchange using RFC-3107 for
BGP peerings between each IGP domain. ASBR are inline-RR reflecting routes to access
PE and set themsleves as the next-hop for routes being reflected. This design is using a
transport-RR located in core domain, which peers and reflects routes to all ASBR routers.
We will first start by using default metric in all domains. Then, we will use different metric
in ISIS Core domain with the goal to test multiple BGP-TE and MPLS-TE scenarios.
Target topology
Access
A1-XR22:
!
router ospf 10
router-id 22.22.22.22
area 0
prefix-suppression
interface Loopback0
passive enable
!
interface GigabitEthernet0/0/0/0
network point-to-point
!
interface GigabitEthernet0/0/0/1
network point-to-point
!
interface GigabitEthernet0/0/0/2
network point-to-point
A1-R23:
!
router ospf 10
router-id 23.23.23.23
prefix-suppression
passive-interface lo0
!
interface lo0
ip ospf 10 area 0
!
interface range Gi1-3
ip ospf 10 area 0
ip ospf network point-to-point
ASBR
C-XR1, C-XR11:
!
router ospf 10
router-id X.X.X.X <<< Replace ‘X’ by Node ID
area 0
prefix-suppression
interface Loopback0
passive enable
!
interface GigabitEthernet0/0/0/2
network point-to-point
!
interface GigabitEthernet0/0/0/3
network point-to-point
!
interface GigabitEthernet0/0/0/4
network point-to-point
Access
A2-XR32:
!
router ospf 20
router-id 32.32.32.32
area 0
prefix-suppression
interface Loopback0
passive enable
!
interface GigabitEthernet0/0/0/0
network point-to-point
!
interface GigabitEthernet0/0/0/1
network point-to-point
!
interface GigabitEthernet0/0/0/2
network point-to-point
A2-R33:
!
router ospf 20
router-id 33.33.33.33
prefix-suppression
passive-interface lo0
!
interface lo0
ip ospf 20 area 0
!
interface range Gi1-3
ip ospf 20 area 0
ip ospf network point-to-point
ASBR
C-XR6, C-XR16:
!
router ospf 20
router-id X.X.X.X <<< Replace ‘X’ by Node ID
area 0
prefix-suppression
interface Loopback0
passive enable
!
interface GigabitEthernet0/0/0/2
network point-to-point
!
interface GigabitEthernet0/0/0/3
network point-to-point
!
interface GigabitEthernet0/0/0/4
network point-to-point
Transport RR
C-XR10:
!
router isis 1
net 49.0100.0000.0000.0010.00
is-type level-2-only
log adjacency changes
address-family ipv4 unicast
metric-style wide
advertise passive-only
!
int lo0
passive
address-family ipv4 unicast
!
int Gi0/0/0/0
point-to-point
address-family ipv4
Service RR
C-R110:
!
router isis 1
net 49.0100.0000.0000.0110.00
is-type level-2-only
metric-style wide
log-adjacency-changes
passive-interface Lo0
advertise passive-only
!
int Gi1
ip router isis 1
isis network point-to-point
C-XR1, C-XR6:
!
router isis 1
net 49.0100.0000.0000.000X.00 <<< Replace ‘X’ by Node ID
is-type level-2-only
log adjacency changes
address-family ipv4 unicast
metric-style wide
advertise passive-only
!
int lo0
passive
address-family ipv4 unicast
!
int Gi0/0/0/0
point-to-point
address-family ipv4
metric 50
!
int Gi0/0/0/1
point-to-point
address-family ipv4
metric 100
C-XR3, C-XR5:
!
router isis 1
net 49.0100.0000.0000.000X.00 <<< Replace ‘X’ by Node ID
is-type level-2-only
log adjacency changes
address-family ipv4 unicast
metric-style wide
advertise passive-only
!
int lo0
passive
address-family ipv4 unicast
!
int Gi0/0/0/0
point-to-point
address-family ipv4
metric 100
!
int Gi0/0/0/1
point-to-point
address-family ipv4
!
int Gi0/0/0/2
point-to-point
address-family ipv4
metric 100
!
int Gi0/0/0/4
point-to-point
address-family ipv4
C-XR2, C-XR4:
!
router isis 1
net 49.0100.0000.0000.000X.00 <<< Replace ‘X’ by Node ID
is-type level-2-only
log adjacency changes
address-family ipv4 unicast
metric-style wide
advertise passive-only
!
int lo0
passive
address-family ipv4 unicast
!
int Gi0/0/0/0
point-to-point
address-family ipv4
metric 50
!
int Gi0/0/0/1
point-to-point
address-family ipv4
!
int Gi0/0/0/2
point-to-point
address-family ipv4
metric 50
!
int Gi0/0/0/3
point-to-point
address-family ipv4
!
int Gi0/0/0/4
point-to-point
address-family ipv4
IS-IS 1 neighbors:
System Id Interface SNPA State Holdtime Type IETF-NSF
C-XR1 Gi0/0/0/0 *PtoP* Up 24 L2 Capable
C-XR4 Gi0/0/0/2 *PtoP* Up 20 L2 Capable
C-XR3 Gi0/0/0/1 *PtoP* Up 23 L2 Capable
C-XR10 Gi0/0/0/3 *PtoP* Up 28 L2 Capable
C-XR12 Gi0/0/0/4 *PtoP* Up 27 L2 Capable
IS-IS 1 Interfaces
Interface All Adjs Adj Topos Adv Topos CLNS MTU Prio
OK L1 L2 Run/Cfg Run/Cfg L1 L2
----------------- --- --------- --------- --------- ---- ---- --------
Lo0 Yes - - 0/0 1/1 No - - -
Gi0/0/0/0 No - 1 1/1 0/0 Up 1497 - -
Gi0/0/0/1 No - 1 1/1 0/0 Up 1497 - -
Gi0/0/0/2 No - 1 1/1 0/0 Up 1497 - -
Gi0/0/0/3 No - 1 1/1 0/0 Up 1497 - -
Gi0/0/0/4 No - 1 1/1 0/0 Up 1497 - -
Access
A1-XR22:
!
mpls ldp address-family ipv4 discovery targeted-hello accept
!
router ospf 10
fast-reroute per-prefix
fast-reroute per-prefix remote-lfa tunnel mpls-ldp
area 0
mpls ldp auto-config
mpls ldp sync
!
mpls ldp router-id 22.22.22.22
mpls label range 202200 202299
mpls ldp session protection
mpls oam
!
! >>> Restart the router for label range to take effect on XR9000v
A1-R23:
!
mpls ldp router-id lo0
mpls ldp session protection
mpls label range 202300 202399
!
mpls ldp discovery targeted-hello accept
!
router ospf 10
fast-reroute per-prefix enable prefix-priority low
fast-reroute per-prefix remote-lfa area 0 tunnel mpls
mpls ldp autoconfig
mpls ldp sync
A1-XR1:
!
mpls ldp address-family ipv4 discovery targeted-hello accept
!
router ospf 10
fast-reroute per-prefix
fast-reroute per-prefix remote-lfa tunnel mpls-ldp
area 0
mpls ldp auto-config
mpls ldp sync
!
mpls ldp router-id 1.1.1.1
mpls label range 200100 200199
mpls ldp session protection
mpls oam
A1-XR11:
!
mpls ldp address-family ipv4 discovery targeted-hello accept
!
router ospf 10
fast-reroute per-prefix
fast-reroute per-prefix remote-lfa tunnel mpls-ldp
area 0
mpls ldp auto-config
mpls ldp sync
!
mpls ldp router-id 11.11.11.11
mpls label range 201100 201199
mpls ldp session protection
mpls oam
GigabitEthernet0/0/0/0:
VRF: 'default' (0x60000000)
Sync delay: Disabled
Sync status: Ready
Peers:
1.1.1.1:0
GigabitEthernet0/0/0/1:
VRF: 'default' (0x60000000)
Sync delay: Disabled
Sync status: Ready
Peers:
11.11.11.11:0
GigabitEthernet0/0/0/2:
VRF: 'default' (0x60000000)
Sync delay: Disabled
Sync status: Ready
Peers:
22.22.22.22:0
GigabitEthernet0/0/0/3:
VRF: 'default' (0x60000000)
Sync delay: Disabled
Sync status: Ready
Peers:
23.23.23.23:0
1.1.1.1/32, version 67, internal 0x1000001 0x30 (ptr 0xdcf60d8) [1], 0x0 (0xe4ebd50), 0xa28
(0xf41b378)
remote adjacency to GigabitEthernet0/0/0/2
Prefix Len 32, traffic index 0, precedence n/a, priority 3
via 20.1.22.1/32, GigabitEthernet0/0/0/2, 2 dependencies, weight 0, class 0, protected [flags
0x400]
path-idx 0 bkup-idx 1 NHID 0x0 [0xf69d280 0xf69d620]
next hop 20.1.22.1/32
local label 202200 labels imposed {ImplNull}
via 20.21.22.21/32, GigabitEthernet0/0/0/1, 7 dependencies, weight 0, class 0, backup (Local-
LFA) [flags 0x300]
path-idx 1 NHID 0x0 [0xf25b440 0x0]
next hop 20.21.22.21/32
remote adjacency
local label 202200 labels imposed {202100}
11.11.11.11/32, version 68, internal 0x1000001 0x30 (ptr 0xdcf6000) [1], 0x0 (0xe4ebba0), 0xa28
(0xf39d0a8)
remote adjacency to GigabitEthernet0/0/0/0
Prefix Len 32, traffic index 0, precedence n/a, priority 3
via 20.22.23.23/32, GigabitEthernet0/0/0/0, 4 dependencies, weight 0, class 0, protected,
ECMP-backup (Local-LFA) [flags 0x600]
path-idx 0 bkup-idx 2 NHID 0x0 [0xf69d198 0x0]
next hop 20.22.23.23/32
local label 202201 labels imposed {202303}
via 20.1.22.1/32, GigabitEthernet0/0/0/2, 2 dependencies, weight 0, class 0, protected [flags
0x400]
path-idx 1 bkup-idx 0 NHID 0x0 [0xf69d368 0x0]
next hop 20.1.22.1/32
local label 202201 labels imposed {200112}
via 20.21.22.21/32, GigabitEthernet0/0/0/1, 4 dependencies, weight 0, class 0, protected,
ECMP-backup (Local-LFA) [flags 0x600]
path-idx 2 bkup-idx 0 NHID 0x0 [0xf69d538 0x0]
next hop 20.21.22.21/32
local label 202201 labels imposed {202101}
23.23.23.23/32, version 70, internal 0x1000001 0x30 (ptr 0xdcf5e50) [1], 0x0 (0xe4eb9a8), 0xa28
(0xf41b2d8)
remote adjacency to GigabitEthernet0/0/0/0
Prefix Len 32, traffic index 0, precedence n/a, priority 3
via 20.22.23.23/32, GigabitEthernet0/0/0/0, 2 dependencies, weight 0, class 0, protected [flags
0x400]
path-idx 0 bkup-idx 1 NHID 0x0 [0xf69d8d8 0xf69d198]
next hop 20.22.23.23/32
local label 202203 labels imposed {ImplNull}
via 20.21.22.21/32, GigabitEthernet0/0/0/1, 7 dependencies, weight 0, class 0, backup (Local-
LFA) [flags 0x300]
path-idx 1 NHID 0x0 [0xf25b440 0x0]
next hop 20.21.22.21/32
remote adjacency
local label 202203 labels imposed {202103}
XR21:
!
interface Gi0/0/0/0
shut
interface Gi0/0/0/1
shut
interface Gi0/0/0/2
shut
interface Gi0/0/0/3
shut
Access
A2-XR32:
!
mpls ldp address-family ipv4 discovery targeted-hello accept
!
router ospf 20
fast-reroute per-prefix
fast-reroute per-prefix remote-lfa tunnel mpls-ldp
area 0
mpls ldp auto-config
mpls ldp sync
!
mpls ldp router-id 32.32.32.32
mpls label range 303200 303299
mpls ldp session protection
mpls oam
!
! >>> Restart the router for label range to take effect on XR9000v
A2-R33:
!
mpls ldp router-id lo0
mpls ldp session protection
mpls label range 303300 303399
!
mpls ldp discovery targeted-hello accept
!
router ospf 20
mpls ldp autoconfig
mpls ldp sync
fast-reroute per-prefix enable prefix-priority low
fast-reroute per-prefix remote-lfa area 0 tunnel mpls
A2-XR6:
!
mpls ldp address-family ipv4 discovery targeted-hello accept
!
router ospf 20
fast-reroute per-prefix
fast-reroute per-prefix remote-lfa tunnel mpls-ldp
area 0
mpls ldp auto-config
mpls ldp sync
!
mpls ldp router-id 6.6.6.6
mpls label range 300600 300699
mpls ldp session protection
mpls oam
A2-XR16:
!
mpls ldp address-family ipv4 discovery targeted-hello accept
!
router ospf 20
fast-reroute per-prefix
fast-reroute per-prefix remote-lfa tunnel mpls-ldp
area 0
mpls ldp auto-config
mpls ldp sync
!
mpls ldp router-id 16.16.16.16
mpls label range 301600 301699
mpls ldp session protection
mpls oam
6.6.6.6/32, version 22, internal 0x1000001 0x30 (ptr 0xd903040) [1], 0x0 (0xe249a80), 0xa28
(0xf5b20a8)
remote adjacency to GigabitEthernet0/0/0/2
Prefix Len 32, traffic index 0, precedence n/a, priority 3
via 30.31.32.31/32, GigabitEthernet0/0/0/0, 7 dependencies, weight 0, class 0, backup (Local-
LFA) [flags 0x300]
path-idx 0 NHID 0x0 [0xf25b440 0x0]
next hop 30.31.32.31/32
remote adjacency
local label 303200 labels imposed {303100}
via 30.6.32.6/32, GigabitEthernet0/0/0/2, 2 dependencies, weight 0, class 0, protected [flags
0x400]
path-idx 1 bkup-idx 0 NHID 0x0 [0xf6a1198 0xf6a10b0]
next hop 30.6.32.6/32
local label 303200 labels imposed {ImplNull}
16.16.16.16/32, version 23, internal 0x1000001 0x30 (ptr 0xd902f68) [1], 0x0 (0xe249b10), 0xa28
(0xf352100)
remote adjacency to GigabitEthernet0/0/0/0
Prefix Len 32, traffic index 0, precedence n/a, priority 3
via 30.31.32.31/32, GigabitEthernet0/0/0/0, 4 dependencies, weight 0, class 0, protected,
ECMP-backup (Local-LFA) [flags 0x600]
path-idx 0 bkup-idx 2 NHID 0x0 [0xf6a1280 0x0]
next hop 30.31.32.31/32
local label 303201 labels imposed {303101}
via 30.6.32.6/32, GigabitEthernet0/0/0/2, 4 dependencies, weight 0, class 0, protected [flags
0x400]
path-idx 1 bkup-idx 0 NHID 0x0 [0xf6a10b0 0x0]
next hop 30.6.32.6/32
local label 303201 labels imposed {300612}
via 30.32.33.33/32, GigabitEthernet0/0/0/1, 4 dependencies, weight 0, class 0, protected,
ECMP-backup (Local-LFA) [flags 0x600]
path-idx 2 bkup-idx 0 NHID 0x0 [0xf6a1368 0x0]
next hop 30.32.33.33/32
local label 303201 labels imposed {303301}
33.33.33.33/32, version 25, internal 0x1000001 0x30 (ptr 0xd902db8) [1], 0x0 (0xe2499a8), 0xa28
(0xf5b2148)
remote adjacency to GigabitEthernet0/0/0/1
Prefix Len 32, traffic index 0, precedence n/a, priority 3
via 30.31.32.31/32, GigabitEthernet0/0/0/0, 7 dependencies, weight 0, class 0, backup (Local-
LFA) [flags 0x300]
path-idx 0 NHID 0x0 [0xf25b440 0x0]
next hop 30.31.32.31/32
remote adjacency
local label 303203 labels imposed {303102}
via 30.32.33.33/32, GigabitEthernet0/0/0/1, 2 dependencies, weight 0, class 0, protected [flags
0x400]
path-idx 1 bkup-idx 0 NHID 0x0 [0xf6a1538 0xf6a1368]
next hop 30.32.33.33/32
local label 303203 labels imposed {ImplNull}
A2-R31:
!
int range Gi1-4
shut
A2-R31:
!
int range Gi1-4
no shut
Configuration on ASBR:
▪ Don’t configure label range on ASBR (done in previous tasks)
▪ Don’t configure LDP router-id on ASBR (done in previous tasks)
▪ Don’t configure LDP Session Protection on ASBR (done in previous tasks)
▪ Don’t configure MPLS OAM on ASBR (done in previous tasks)
Transport RR
C-XR10:
!
mpls ldp router-id 10.10.10.10
mpls label range 101000 101099
mpls ldp session protection
mpls oam
!
router isis 1
address-family ipv4 unicast
mpls ldp auto-config
!
interface Gi0/0/0/0
address-family ipv4 unicast
mpls ldp sync
Service RR
C-R110:
!
mpls ldp router-id lo0
mpls ldp session protection
mpls label range 110100 110199 <<< Label range adjusted for Node ID 110
!
router isis 1
mpls ldp autoconfig
mpls ldp sync
GigabitEthernet0/0/0/0:
VRF: 'default' (0x60000000)
Sync delay: Disabled
Sync status: Ready
Peers:
1.1.1.1:0
GigabitEthernet0/0/0/1:
VRF: 'default' (0x60000000)
Sync delay: Disabled
Sync status: Ready
Peers:
3.3.3.3:0
GigabitEthernet0/0/0/2:
VRF: 'default' (0x60000000)
Sync delay: Disabled
Sync status: Ready
Peers:
4.4.4.4:0
GigabitEthernet0/0/0/3:
VRF: 'default' (0x60000000)
Sync delay: Disabled
Sync status: Ready
Peers:
10.10.10.10:0
GigabitEthernet0/0/0/4:
VRF: 'default' (0x60000000)
Sync delay: Disabled
Sync status: Ready
Peers:
12.12.12.12:0
L2 1.1.1.1/32 [50/115]
via 10.1.2.1, GigabitEthernet0/0/0/0, C-XR1, Weight: 0
No FRR backup
L2 3.3.3.3/32 [10/115]
via 10.2.3.3, GigabitEthernet0/0/0/1, C-XR3, Weight: 0
Backup path: R-LFA, via C-XR13 [13.13.13.13], via 10.2.12.12, GigabitEthernet0/0/0/4 C-
XR12, Weight: 0, Metric: 20
L2 4.4.4.4/32 [50/115]
via 10.2.4.4, GigabitEthernet0/0/0/2, C-XR4, Weight: 0
No FRR backup
L2 5.5.5.5/32 [60/115]
via 10.2.4.4, GigabitEthernet0/0/0/2, C-XR4, Weight: 0
No FRR backup
L2 6.6.6.6/32 [100/115]
via 10.2.4.4, GigabitEthernet0/0/0/2, C-XR4, Weight: 0
No FRR backup
If we were using OSPF as Core IGP, meaning a single Loopback on ASBR for
both OSPF+LDP and BGP+Label LSPs, we would need to redistribute ASBR
Loopback into OSPF Core domain. This is because Loopback cannot belong
to multiple OSPF processes at the same time.
Network we built so far is using ISIS as Core IGP domain so we don’t need to redistribute
any ASBR Loopback. In this task, we are using OSPF in Core domain configured as Process
100, just as an example.
C-XR1:
!
route-policy C-XR1
if destination in (1.1.1.1/32) then
pass
endif
end-policy
!
router ospf 100
redistribute connected route-policy C-XR1
C-XR11:
!
route-policy C-XR11
if destination in (11.11.11.11/32) then
pass
endif
end-policy
!
router ospf 100
redistribute connected route-policy C-XR11
C-XR16:
!
route-policy C-XR16
if destination in (16.16.16.16/32) then
pass
endif
end-policy
!
router ospf 100
redistribute connected route-policy C-XR16
ASBR are reflecting routes to Access PE and they set themselves as the
next-hop for routes being reflected. Because of this, they are considered as
“inline-RR” as they are in the forwarding path.
ASBR
C-XR1,C-XR11:
!
router bgp 100
bgp router-id X.X.X.X <<< Node ID
ibgp policy out enforce-modifications
address-family ipv4 unicast
network 22.22.22.22/32
network 23.23.23.23/32
allocate-label all
!
neighbor-group BGP-LU
remote-as 100
update-source lo0
address-family ipv4 labeled-unicast
route-reflector-client
next-hop-self
!
neighbor 22.22.22.22
use neighbor-group BGP-LU
!
neighbor 23.23.23.23
use neighbor-group BGP-LU
A1-XR22:
!
router bgp 100
bgp router-id 22.22.22.22
address-family ipv4 unicast
allocate-label all
!
neighbor 1.1.1.1
remote-as 100
update-source lo0
address-family ipv4 labeled-unicast
!
neighbor 11.11.11.11
remote-as 100
update-source lo0
address-family ipv4 labeled-unicast
A1-R23:
!
router bgp 100
bgp router-id 23.23.23.23
neighbor 1.1.1.1 remote-as 100
neighbor 1.1.1.1 update-source lo0
neighbor 11.11.11.11 remote-as 100
neighbor 11.11.11.11 update-source lo0
!
address-family ipv4
neighbor 1.1.1.1 activate
neighbor 1.1.1.1 send-label
neighbor 11.11.11.11 activate
neighbor 11.11.11.11 send-label
A2-XR32:
!
router bgp 100
bgp router-id 32.32.32.32
address-family ipv4 unicast
allocate-label all
!
neighbor 6.6.6.6
remote-as 100
update-source lo0
address-family ipv4 labeled-unicast
!
neighbor 16.16.16.16
remote-as 100
update-source lo0
address-family ipv4 labeled-unicast
A2-R33:
!
router bgp 100
bgp router-id 33.33.33.33
neighbor 6.6.6.6 remote-as 100
neighbor 6.6.6.6 update-source lo0
neighbor 16.16.16.16 remote-as 100
neighbor 16.16.16.16 update-source lo0
!
address-family ipv4
neighbor 6.6.6.6 activate
neighbor 6.6.6.6 send-label
neighbor 16.16.16.16 activate
neighbor 16.16.16.16 send-label
ASBR
Transport-RR
C-XR10:
!
router bgp 100
bgp router-id 10.10.10.10
address-family ipv4 unicast
allocate-label all
network 10.10.10.10/32
!
neighbor-group BGP-LU
remote-as 100
update-source Loopback0
address-family ipv4 labeled-unicast
route-reflector-client
!
neighbor 1.1.1.1
use neighbor-group BGP-LU
!
neighbor 11.11.11.11
use neighbor-group BGP-LU
!
neighbor 6.6.6.6
use neighbor-group BGP-LU
!
neighbor 16.16.16.16
use neighbor-group BGP-LU
Transport-RR
C-XR10:
!
router bgp 100
address-family ipv4 unicast
network 110.110.110.110/32
!
neighbor 110.110.110.110
use neighbor-group BGP-LU
Service-RR
C-R110:
!
router bgp 100
bgp router-id 110.110.110.110
no bgp default ipv4-unicast
neighbor 10.10.10.10 remote-as 100
neighbor 10.10.10.10 update-source Loopback0
!
address-family ipv4
neighbor 10.10.10.10 activate
neighbor 10.10.10.10 send-label
With actual Metric in place, traffic sent from A1-XR22 to A2-XR32 take the
expected path as shown in below figure. Notice traffic may also be ECMP in
access domains where we are using default metric everywhere.
C-XR11, C-XR16:
!
router isis 1
interface GigabitEthernet0/0/0/0
address-family ipv4 unicast
metric 1
C-XR12, C-XR14:
!
router isis 1
interface GigabitEthernet0/0/0/0
address-family ipv4 unicast
metric 1
!
interface GigabitEthernet0/0/0/2
address-family ipv4 unicast
metric 1
With new Metric in place in Core domain, traffic is now using another path
as shown in below figure. However this path is sub-optimal as it is not
using C-XR11_C-XR12 and C-XR14_C-XR16 links, which both have a
better cost. Notice traffic may also be ECMP in Access domains where we
are using default metric everywhere.
▪ BGP best path to A2-XR32 is still via C-XR1 and is still originated by C-XR6.
▪ Best path is via C-XR1 because it has a lowest IGP metric to BGP next-hop (2)
compared to path via C-XR11 (3).
C-XR1,C-XR11:
!
prefix-set PE_ACC_1_PSET
22.22.22.22/32,
23.23.23.23/32
end-set
!
route-policy PE_ACC_1_RPL
if destination in PE_ACC_1_PSET then
set aigp-metric igp-cost
endif
end-policy
!
router bgp 100
address-family ipv4 unicast
no network 22.22.22.22/32
no network 23.23.23.23/32
redistribute ospf 10 route-policy PE_ACC_1_RPL
C-XR6,C-XR16:
!
prefix-set PE_ACC_2_PSET
32.32.32.32/32,
33.33.33.33/32
end-set
!
route-policy PE_ACC_2_RPL
if destination in PE_ACC_2_PSET then
set aigp-metric igp-cost
endif
end-policy
!
router bgp 100
address-family ipv4 unicast
no network 32.32.32.32/32
no network 33.33.33.33/32
redistribute ospf 20 route-policy PE_ACC_2_RPL
With new Metric in place in Core domain and with AIGP enabled for all PE
Loopbacks, traffic is now using a new optimized path as shown in below
diagram. Now the path is optimal as it is using C-XR11_C-XR12 and C-
XR14_C-XR16 links, which both have a very low cost. Notice traffic may
also be ECMP in Access domains where we are using default metric
everywhere.
➢ IGP metric to BGP next-hop is still compared between Path #1 (2) and Path #2 (3).
➢ Path via C-XR1 still has the lowest IGP metric. Now that AIGP is used, it comes before
IGP metric in BGP best path process, hence Path #2 via C-XR11 is preferred.
1. Weight
2. Highest Local-Pref
3. Lowest AIGP Cost
4. Shortest AS-PATH
5. Lowest origin code (IGP/EGP/incomplete)
6. Lowest MED
7. Prefer eBGP over iBGP
8. Lowest IGP metric to the BGP next-hop
ASBR (inline-RR)
Transport-RR
C-XR10:
!
route-policy ADD-PATH_RPL
set path-selection all advertise
end-policy
!
router bgp 100
address-family ipv4 unicast
additional-paths receive
additional-paths send
additional-paths selection route-policy ADD-PATH_RPL
A1-XR22, A2-XR32:
!
route-policy ADD-PATH_RPL
set path-selection backup 1 install
end-policy
!
router bgp 100
address-family ipv4 unicast
additional-paths receive
additional-paths selection route-policy ADD-PATH_RPL
➢ After the changes are done on XR, we need to flap BGP sessions (clear bgp *).
➢ This is needed to negotiate the additional capabilities on the session.
A1-R23:
!
router bgp 100
address-family ipv4
bgp additional-paths receive
bgp additional-paths select all
bgp additional-paths install
neighbor 1.1.1.1 additional-paths receive
neighbor 11.11.11.11 additional-paths receive
A1-R33:
!
router bgp 100
address-family ipv4
bgp additional-paths receive
bgp additional-paths select all
bgp additional-paths install
neighbor 6.6.6.6 additional-paths receive
neighbor 16.16.16.16 additional-paths receive
➢ As we reach Access 2 domain, BGP is no more relevant. LFA (and ECMP if applicable)
takeover to provide FRR mechanism to targeted prefix.
ASBR
Access 1
A1-XR22:
!
vrf cust-2
address-family ipv4 unicast
import route-target
100:2232
!
export route-target
100:2232
!
interface Gi0/0/0/3
no ipv4 address
vrf cust-2
ipv4 address 40.22.42.22/24
A1-R23:
!
vrf definition cust-3
rd 100:23
route-target both 100:2333
address-family ipv4
!
interface Gi4
vrf forwarding cust-3
ip address 40.23.43.23 255.255.255.0
A2-XR32:
!
vrf cust-2
address-family ipv4 unicast
import route-target
100:2232
!
export route-target
100:2232
!
interface Gi0/0/0/3
no ipv4 address
vrf cust-2
ipv4 address 50.32.52.32/24
A2-R33:
!
vrf definition cust-3
rd 100:33
route-target both 100:2333
address-family ipv4
!
interface Gi4
vrf forwarding cust-3
ip address 50.33.53.33 255.255.255.0
Access 1
A1-XR22:
!
route-policy PASS
pass
end-policy
!
router bgp 100
address-family ipv4 unicast
address-family vpnv4 unicast
!
vrf cust-2
rd 100:22
address-family ipv4 unicast
!
neighbor 40.22.42.42
remote-as 45
address-family ipv4 unicast
route-policy PASS in
route-policy PASS out
as-override
A2-XR32:
!
route-policy PASS
pass
end-policy
!
router bgp 100
address-family ipv4 unicast
address-family vpnv4 unicast
!
vrf cust-2
rd 100:32
address-family ipv4 unicast
!
neighbor 50.32.52.52
remote-as 45
address-family ipv4 unicast
route-policy PASS in
route-policy PASS out
as-override
CE-XR52:
!
router bgp 45
bgp router-id 52.52.52.52
neighbor 50.32.52.32 remote-as 100
network 52.52.52.52 mask 255.255.255.255
Access 1
A1-R23:
!
router ospf 23 vrf cust-3
network 40.23.43.43 0.0.0.0 area 0
redistribute bgp 100 subnets
!
int Gi4
ip ospf 23 area 0
!
ip prefix-list LOOPBACK_PLIST seq 5 permit 0.0.0.0/0 ge 32
!
route-map LOOPBACK_RMAP permit 10
match ip address prefix-list LOOPBACK_PLIST
!
router bgp 100
address-family ipv4 vrf cust-3
redistribute ospf 23 match internal external nssa route-map LOOPBACK_RMAP
CE-XR43:
!
router ospf 1
router-id 43.43.43.43
area 0
interface Loopback0
passive enable
!
interface GigabitEthernet0/0/0/1
A1-R33:
!
router ospf 33 vrf cust-3
network 50.33.53.53 0.0.0.0 area 0
redistribute bgp 100 subnets
!
int Gi4
ip ospf 33 area 0
!
ip prefix-list LOOPBACK_PLIST seq 5 permit 0.0.0.0/0 ge 32
!
route-map LOOPBACK_RMAP permit 10
match ip address prefix-list LOOPBACK_PLIST
!
router bgp 100
address-family ipv4 vrf cust-3
redistribute ospf 33 match internal external nssa route-map LOOPBACK_RMAP
CE-R53:
!
router ospf 1
router-id 53.53.53.53
network 50.33.53.33 0.0.0.0 area 0
network 53.53.53.53 0.0.0.0 area 0
passive-interface lo0
!
int Gi0/1
ip ospf 1 area 0
Service RR
C-R110:
!
router bgp 100
!
neighbor iBGP peer-group
neighbor iBGP remote-as 100
neighbor iBGP update-source lo0
!
neighbor 22.22.22.22 peer-group iBGP
neighbor 23.23.23.23 peer-group iBGP
neighbor 32.32.32.32 peer-group iBGP
neighbor 33.33.33.33 peer-group iBGP
!
address-family vpnv4
neighbor iBGP send-community extended
neighbor iBGP route-reflector-client
neighbor 22.22.22.22 activate
neighbor 23.23.23.23 activate
neighbor 32.32.32.32 activate
neighbor 33.33.33.33 activate
A1-XR22, A2-XR32:
!
router bgp 100
address-family vpnv4 unicast
!
neighbor 110.110.110.110
remote-as 100
update-source lo0
address-family vpnv4 unicast
A1-R23, A2-R33:
!
router bgp 100
no bgp default ipv4-unicast
neighbor 110.110.110.110 remote-as 100
neighbor 110.110.110.110 update-source lo0
!
address-family vpnv4 unicast
neighbor 110.110.110.110 activate
neighbor 110.110.110.110 send-community extended
CE-XR43:
!
prefix-set ONLY_LOOPBACK_PSET
0.0.0.0/0 ge 32
end-set
!
prefix-set DENY_ALL_PSET
0.0.0.0/0 le 32
end-set
!
route-policy ONLY_LOOPBACK_RPL
if destination in ONLY_LOOPBACK_PSET then
pass
else
if destination in DENY_ALL_PSET then
drop
endif
endif
end-policy
!
!
router ospf 1
area 0
distribute-list route-policy ONLY_LOOPBACK_RPL in
CE-R53:
!
ip prefix-list ONLY_LOOPBACK_PLIST permit 0.0.0.0/0 ge 32
ip prefix-list ONLY_LOOPBACK_PLIST deny 0.0.0.0/0 le 32
!
router ospf 1
distribute-list prefix ONLY_LOOPBACK_PLIST in
A1-R23:
!
interface Lo123
vrf forwarding cust-3
ip address 123.123.123.123 255.255.255.255
!
access-list 2 permit 123.123.123.123
access-list 2 permit 133.133.133.133
!
route-map TO_CUST-3_RMAP deny 10
match ip address 2
route-map TO_CUST-3_RMAP permit 20
!
router ospf 23 vrf cust-3
area 0 sham-link 123.123.123.123 133.133.133.133
redistribute bgp 100 route-map TO_CUST-3_RMAP
!
ip prefix-list LOOPBACK_PLIST seq 5 permit 0.0.0.0/0 ge 32
!
route-map LOOPBACK_RMAP permit 10
match ip address prefix-list LOOPBACK_PLIST
!
router bgp 100
address-family ipv4 vrf cust-3
network 123.123.123.123 mask 255.255.255.255
redistribute ospf 23 match internal external nssa-external route-map LOOPBACK_RMAP
EVPN BGP
C-R110:
!
router bgp 100
address-family l2vpn evpn
neighbor iBGP send-community both
neighbor iBGP route-reflector-client
neighbor 22.22.22.22 activate
neighbor 32.32.32.32 activate
exit-address-family
A1-XR22, A2-XR32:
!
router bgp 100
address-family l2vpn evpn
!
neighbor 110.110.110.110
address-family l2vpn evpn
A1-XR22:
!
interface GigabitEthernet0/0/0/4.10 l2transport
encapsulation dot1q 50
rewrite ingress tag pop 1 symmetric <<< Pop Customer vlan 50 before send traffic in PW
!
l2vpn
xconnect group evpn_vpws
p2p evpn1
interface Gi0/0/0/4.10
neighbor evpn evi 2 target 10 source 5 <<< Ethernet Tag (AC ID) is 5
A2-XR32:
!
interface GigabitEthernet0/0/0/4.10 l2transport
encapsulation dot1q 50
rewrite ingress tag pop 1 symmetric <<< Pop Customer vlan 50 before send traffic in PW
!
l2vpn
xconnect group evpn_vpws
p2p evpn1
interface Gi0/0/0/4.10
neighbor evpn evi 2 target 5 source 10 <<< Ethernet Tag (AC ID) is 10
CE-XR41:
!
interface GigabitEthernet0/0/0/0.50
encapsulation dot1q 50
ipv4 address 192.168.50.41 255.255.255.0
CE-R51:
!
interface Gi0/0.50
encapsulation dot1q 50
ip address 192.168.50.51 255.255.255.0
➢ EVPN routes show the Ethernet segments with their associated Ethernet Tag.
➢ Customer 1 sites in our design are Single-homed. This is why Ethernet Segment is
identified by a unique zero Ethernet Segment Identifier (ESI). If customer were Multi-
homed sites, Ethernet Segment would be identified by a unique non-zero ESI.
RP/0/0/CPU0:CE-XR41#ping 192.168.50.51
RP/0/0/CPU0:CE-XR41#sh arp
-------------------------------------------------------------------------------
0/0/CPU0
-------------------------------------------------------------------------------
Address Age Hardware Addr State Type Interface
192.168.50.41 - 5254.0012.f76e Interface ARPA GigabitEthernet0/0/0/0.50
192.168.50.51 02:01:19 5254.001b.9a50 Dynamic ARPA GigabitEthernet0/0/0/0.50
EoMPLS vlan-based
A2-R23, A2-R33:
!
pseudowire-class VC_2333_VLAN
encapsulation mpls
interworking vlan
!
int Gi5
service instance 10 ethernet
encapsulation dot1q 10 second-dot1q 100,120 <<< QinQ traffic going to CE
xconnect X.X.X.X 10 pw-class VC_2333_VLAN <<< X.X.X.X is the remote PE
CE-R44, CE-R54:
!
int Gi1
no shut
service instance 10 ethernet
encapsulation dot1q 10 second-dot1q 100,120 <<< QinQ traffic going to PE
rewrite ingress tag pop 1 symmetric <<< Pop Outer vlan 10 before send traffic to switch
bridge-domain 10
!
int Gi2
no shut
service instance 10 ethernet
encapsulation dot1q 100,120
bridge-domain 10
!
bridge-domain 10
SW1, SW2:
!
vtp mode transparent
vtp domain CST
!
vlan 100, 120, 140
!
Int gi0/0
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface Vlan100
ip address 192.168.100.x 255.255.255.0 <<< X is the Switch ID
!
interface Vlan120
ip address 192.168.120.x 255.255.255.0 <<< X is the Switch ID
!
interface Vlan100
ip address 192.168.140.x 255.255.255.0 <<< X is the Switch ID
➢ Alternatively, this output shows VC status with MPLS labels with interworking mode.
➢ Test pseudowire VC 10
Tracing MS-PW segments within range [1-1] peer address 33.33.33.33 and timeout 2 seconds
sw1#debug ip icmp
ICMP packet debugging is on
sw1#ping 192.168.100.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.100.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 21/29/37 ms
sw1#
*May 1 12:14:56.582: ICMP: echo reply rcvd, src 192.168.100.2, dst 192.168.100.1, topology
BASE, dscp 0 topoid 0
*May 1 12:14:56.604: ICMP: echo reply rcvd, src 192.168.100.2, dst 192.168.100.1, topology
BASE, dscp 0 topoid 0
*May 1 12:14:56.643: ICMP: echo reply rcvd, src 192.168.100.2, dst 192.168.100.1, topology
BASE, dscp 0 topoid 0
*May 1 12:14:56.682: ICMP: echo reply rcvd, src 192.168.100.2, dst 192.168.100.1, topology
BASE, dscp 0 topoid 0
sw1#ping 192.168.120.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.120.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 20/26/37 ms
sw1#
*May 1 12:16:09.498: ICMP: echo reply rcvd, src 192.168.120.2, dst 192.168.120.1, topology
BASE, dscp 0 topoid 0
*May 1 12:16:09.529: ICMP: echo reply rcvd, src 192.168.120.2, dst 192.168.120.1, topology
BASE, dscp 0 topoid 0
*May 1 12:16:09.550: ICMP: echo reply rcvd, src 192.168.120.2, dst 192.168.120.1, topology
BASE, dscp 0 topoid 0
*May 1 12:16:09.574: ICMP: echo reply rcvd, src 192.168.120.2, dst 192.168.120.1, topology
BASE, dscp 0 topoid 0
sw1#ping 192.168.140.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.140.2, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
CE-R44#show bridge-domain 10
• SW-1 and SW-2 MAC in vlan 100 and 120 are learned in the bridge-domain.
• SW-1 MAC in vlan 140 is learned, but SW-2 MAC in vlan 140 is not learned.
CE-R44, CE-R54:
!
interface GigabitEthernet1
service instance 10 ethernet
encapsulation dot1q 10 second-dot1q 100,120,140
A1-R23, A2-R33:
!
interface GigabitEthernet5
service instance 10 ethernet
encapsulation dot1q 10 second-dot1q 100,120,140
SW1#ping 192.168.140.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.140.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 25/29/36 ms
SW1#
*May 1 13:56:43.787: ICMP: echo reply rcvd, src 192.168.140.2, dst 192.168.140.1, topology
BASE, dscp 0 topoid 0
*May 1 13:56:43.814: ICMP: echo reply rcvd, src 192.168.140.2, dst 192.168.140.1, topology
BASE, dscp 0 topoid 0
*May 1 13:56:43.841: ICMP: echo reply rcvd, src 192.168.140.2, dst 192.168.140.1, topology
BASE, dscp 0 topoid 0
*May 1 13:56:43.876: ICMP: echo reply rcvd, src 192.168.140.2, dst 192.168.140.1, topology
BASE, dscp 0 topoid 0
CE-R44#show bridge-domain 10
In earlier BGP-LU tasks, we implement AIGP in the objective to optimize the end-to-end
path computation to account the accumulated IGP metrics of each domain. To verify that,
we configured low metrics in Core domain, where BGP-LU next-hop changed from C-XR1
and C-XR6 to C-XR11 and C-XR16.
RED traffic must transit via C-XR6 and then via C-XR1. This means that prior to setup
MPLS TE tunnels, we first have to make C-XR6 and C-XR1 the preferred BGP next-hop to
reach our final destination A1-XR22. As a solution, we will configure Local-Preference
which is a better BGP attribute than AIGP in regards to the BGP bestpath selection.
The figure shows 3 MPLS TE tunnels in total. With the Unified MPLS network actually in
place, transport labels are allocated by LDP and BGP-LU. As the domains do not have IGP
knowledge of the other domains, this is not possible to configure a single MPLS-TE LSP
from East PE to West PE.
MPLS-TE tunnel are unidirectional. In real case scenarios, it would makes sense to
configure 2 tunnels, 1 in each direction. In this task, we are using only one unidirectional
path from East to West. This is enough for our tests.
BGP Traffic-Engineering
➢ Makes C-XR6 the preferred exit point for A1-XR32 to reach A1-XR22.
A2-XR32:
!
route-policy LP
if destination in (22.22.22.22/32) then
set local-preference 200
else
pass
endif
end-policy
!
router bgp 100
neighbor 6.6.6.6
remote-as 100
update-source Loopback0
address-family ipv4 labeled-unicast
route-policy LP in
C-XR6:
!
route-policy LP
if destination in (22.22.22.22/32) and next-hop in (1.1.1.1) then
set local-preference 200
else
pass
endif
end-policy
!
router bgp 100
neighbor 10.10.10.10
address-family ipv4 labeled-unicast
route-policy LP in
➢ Access 2 - ASBR
C-XR6, C-XR16:
!
router ospf 20
mpls traffic-eng router-id Lo0
area 0
mpls traffic-eng
!
mpls traffic-eng
int Gi0/0/0/2
int Gi0/0/0/3
int Gi0/0/0/4
!
rsvp
int Gi0/0/0/2
bandwidth percentage 75 <<< No Bandwidth reserved on XR, by default
int Gi0/0/0/3
bandwidth percentage 75 <<< No Bandwidth reserved on XR, by default
int Gi0/0/0/4
bandwidth percentage 75 <<< No Bandwidth reserved on XR, by default
A2-XR32:
!
router ospf 20
mpls traffic-eng router-id Lo0
area 0
mpls traffic-eng
!
mpls traffic-eng
reoptimize 30
int Gi0/0/0/0
int Gi0/0/0/1
int Gi0/0/0/2
!
rsvp
int Gi0/0/0/0
bandwidth percentage 75 <<< No Bandwidth reserved on XR, by default
int Gi0/0/0/1
bandwidth percentage 75 <<< No Bandwidth reserved on XR, by default
int Gi0/0/0/2
bandwidth percentage 75 <<< No Bandwidth reserved on XR, by default
!
explicit-path name A2-XR32_To_C-XR6
index 1 next-address ipv4 unicast 33.33.33.33
index 2 next-address ipv4 unicast 31.31.31.31
index 3 next-address ipv4 unicast 6.6.6.6
!
interface Tunnel-te1
ipv4 unnumbered lo0
destination 6.6.6.6
path-option 1 explicit name A2-XR32_To_C-XR6
path-option 2 dynamic
signalled-bandwidth 50000
fast-reroute
autoroute announce
C-XR6:
!
router isis 1
address-family ipv4 unicast
metric-style wide
mpls traffic-eng router-id Lo0
mpls traffic-eng level-2-only
!
mpls traffic-eng
reoptimize 30
int Gi0/0/0/0
int Gi0/0/0/1
!
rsvp
int Gi0/0/0/0
bandwidth percentage 75 <<< No Bandwidth reserved on XR, by default
int Gi0/0/0/1
bandwidth percentage 75 <<< No Bandwidth reserved on XR, by default
!
explicit-path name C-XR6_To_C-XR1
index 1 next-address strict ipv4 unicast 4.4.4.4
index 2 next-address strict ipv4 unicast 5.5.5.5
index 3 next-address strict ipv4 unicast 3.3.3.3
index 4 next-address strict ipv4 unicast 2.2.2.2
index 5 next-address strict ipv4 unicast 1.1.1.1
!
interface Tunnel-te1
ipv4 unnumbered lo0
destination 1.1.1.1
path-option 1 explicit name C-XR6_To_C-XR1
path-option 2 dynamic
signalled-bandwidth 50000
autoroute announce
C-XR2/3/4/5, C-XR12/13/14/15:
!
router isis 1
address-family ipv4 unicast
metric-style wide
mpls traffic-eng router-id Lo0
mpls traffic-eng level-2-only
!
mpls traffic-eng
int Gi0/0/0/0
int Gi0/0/0/1
int Gi0/0/0/2
int Gi0/0/0/4
!
rsvp
int Gi0/0/0/0
bandwidth percentage 75 <<< No Bandwidth reserved on XR, by default
int Gi0/0/0/1
bandwidth percentage 75 <<< No Bandwidth reserved on XR, by default
int Gi0/0/0/2
bandwidth percentage 75 <<< No Bandwidth reserved on XR, by default
int Gi0/0/0/4
bandwidth percentage 75 <<< No Bandwidth reserved on XR, by default
C-XR1:
!
router ospf 10
mpls traffic-eng router-id Lo0
area 0
mpls traffic-eng
!
mpls traffic-eng
reoptimize 30
int Gi0/0/0/2
int Gi0/0/0/3
int Gi0/0/0/4
!
rsvp
int Gi0/0/0/2
bandwidth percentage 75 <<< No Bandwidth reserved on XR, by default
int Gi0/0/0/3
bandwidth percentage 75 <<< No Bandwidth reserved on XR, by default
int Gi0/0/0/4
bandwidth percentage 75 <<< No Bandwidth reserved on XR, by default
!
explicit-path name C-XR1_To_A1-XR22
index 1 next-address strict ipv4 unicast 21.21.21.21
index 2 next-address strict ipv4 unicast 22.22.22.22
!
interface Tunnel-te1
ipv4 unnumbered lo0
destination 22.22.22.22
path-option 1 explicit name C-XR1_To_A1-XR22
path-option 2 dynamic
signalled-bandwidth 50000
autoroute announce
C-XR21:
!
router ospf 10
mpls traffic-eng router-id Lo0
area 0
mpls traffic-eng
!
mpls traffic-eng
int Gi0/0/0/0
int Gi0/0/0/1
int Gi0/0/0/2
int Gi0/0/0/3
!
rsvp
int Gi0/0/0/0
bandwidth percentage 75 <<< No Bandwidth reserved on XR, by default
int Gi0/0/0/1
bandwidth percentage 75 <<< No Bandwidth reserved on XR, by default
int Gi0/0/0/2
bandwidth percentage 75 <<< No Bandwidth reserved on XR, by default
int Gi0/0/0/3
bandwidth percentage 75 <<< No Bandwidth reserved on XR, by default
A2-R23:
!
mpls traffic-eng tunnels
!
router ospf 10
mpls traffic-eng area 0
mpls traffic-eng router-id lo0
!
int range Gi1-3
mpls traffic-eng tunnels
ip rsvp bandwidth
MPLS-TE Topologies
path option 1, type explicit A2-XR32_To_C-XR6 (Basis for Setup, path weight 3)
Accumulative metrics: TE 3 IGP 3 Delay 900000
path option 2, type dynamic
G-PID: 0x0800 (derived from egress interface properties)
Bandwidth Requested: 50000 kbps CT0
Creation Time: Tue May 4 12:23:33 2021 (2d03h ago)
Config Parameters:
Bandwidth: 50000 kbps (CT0) Priority: 7 7 Affinity: 0x0/0xffff
Metric Type: TE (global)
Path Selection:
Tiebreaker: Min-fill (default)
Hop-limit: disabled
Cost-limit: disabled
Delay-limit: disabled
Delay-measurement: disabled
Path-invalidation timeout: 10000 msec (default), Action: Tear (default)
AutoRoute: enabled LockDown: disabled Policy class: not set
Forward class: 0 (not enabled)
Forwarding-Adjacency: disabled
Autoroute Destinations: 0
Loadshare: 0 equal loadshares
Auto-bw: disabled
Auto-Capacity: Disabled:
Fast Reroute: Enabled, Protection Desired: Any
Path Protection: Not Enabled
BFD Fast Detection: Disabled
Reoptimization after affinity failure: Enabled
Soft Preemption: Disabled
SNMP Index: 18
Binding SID: None
History:
Tunnel has been up for: 00:48:58 (since Thu May 06 14:50:52 UTC 2021)
Current LSP:
Uptime: 00:37:47 (since Thu May 06 15:02:03 UTC 2021)
Reopt. LSP:
Last Failure:
LSP not signalled, identical to the [CURRENT] LSP
Converged SDN Transport for CCIE Service Provider v5 | v202104
© 2021 Joël François
Page 187 out of 326
Date/Time: Thu May 06 15:25:36 UTC 2021 [00:14:14 ago]
Prior LSP:
ID: 30 Path Option: 2
Removal Trigger: reoptimization completed
Current LSP Info:
Instance: 31, Signaling Area: OSPF 20 area 0
Uptime: 00:37:47 (since Thu May 06 15:02:03 UTC 2021)
Outgoing Interface: GigabitEthernet0/0/0/1, Outgoing Label: 303304
Router-IDs: local 32.32.32.32
downstream 33.33.33.33
Soft Preemption: None
SRLGs: not collected
Path Info:
Outgoing:
Explicit Route:
Strict, 30.32.33.33
Strict, 30.31.33.31
Strict, 30.6.31.6
Strict, 6.6.6.6
path option 1, type explicit C-XR6_To_C-XR1 (Basis for Setup, path weight 220)
Accumulative metrics: TE 220 IGP 220 Delay 1500000
path option 2, type dynamic
G-PID: 0x0800 (derived from egress interface properties)
Bandwidth Requested: 50000 kbps CT0
Creation Time: Wed May 5 09:11:03 2021 (11:51:27 ago)
Config Parameters:
Bandwidth: 50000 kbps (CT0) Priority: 7 7 Affinity: 0x0/0xffff
Metric Type: TE (global)
Path Selection:
Tiebreaker: Min-fill (default)
Hop-limit: disabled
Cost-limit: disabled
Delay-limit: disabled
Path-invalidation timeout: 10000 msec (default), Action: Tear (default)
AutoRoute: enabled LockDown: disabled Policy class: not set
Forward class: 0 (not enabled)
Forwarding-Adjacency: disabled
Autoroute Destinations: 0
Loadshare: 0 equal loadshares
Auto-bw: disabled
Auto-Capacity: Disabled:
Fast Reroute: Disabled, Protection Desired: None
Path Protection: Not Enabled
BFD Fast Detection: Disabled
Reoptimization after affinity failure: Enabled
Soft Preemption: Disabled
SNMP Index: 10
Binding SID: None
History:
Tunnel has been up for: 11:51:27 (since Wed May 05 09:11:03 UTC 2021)
Current LSP:
Uptime: 11:51:27 (since Wed May 05 09:11:03 UTC 2021)
Reopt. LSP:
Last Failure:
LSP not signalled, identical to the [CURRENT] LSP
Date/Time: Wed May 05 20:36:17 UTC 2021 [00:26:13 ago]
path option 1, type explicit C-XR1_To_A1-XR22 (Basis for Setup, path weight 2)
Accumulative metrics: TE 2 IGP 2 Delay 600000
path option 2, type dynamic
G-PID: 0x0800 (derived from egress interface properties)
Bandwidth Requested: 50000 kbps CT0
Creation Time: Wed May 5 09:15:03 2021 (11:56:23 ago)
Config Parameters:
Bandwidth: 50000 kbps (CT0) Priority: 7 7 Affinity: 0x0/0xffff
Metric Type: TE (global)
Path Selection:
Tiebreaker: Min-fill (default)
Hop-limit: disabled
Cost-limit: disabled
Delay-limit: disabled
Path-invalidation timeout: 10000 msec (default), Action: Tear (default)
AutoRoute: enabled LockDown: disabled Policy class: not set
Forward class: 0 (not enabled)
Forwarding-Adjacency: disabled
Autoroute Destinations: 0
Loadshare: 0 equal loadshares
Auto-bw: disabled
Auto-Capacity: Disabled:
Fast Reroute: Disabled, Protection Desired: None
Path Protection: Not Enabled
BFD Fast Detection: Disabled
Reoptimization after affinity failure: Enabled
Soft Preemption: Disabled
SNMP Index: 10
Binding SID: None
History:
Tunnel has been up for: 11:56:23 (since Wed May 05 09:15:03 UTC 2021)
Current LSP:
Uptime: 11:56:23 (since Wed May 05 09:15:03 UTC 2021)
Reopt. LSP:
Last Failure:
LSP not signalled, identical to the [CURRENT] LSP
Date/Time: Wed May 05 09:17:28 UTC 2021 [11:53:58 ago]
Prior LSP:
ID: 2 Path Option: 1
Removal Trigger: path tear
Converged SDN Transport for CCIE Service Provider v5 | v202104
© 2021 Joël François
Page 191 out of 326
Current LSP Info:
Instance: 3, Signaling Area: OSPF 10 area 0
Uptime: 11:56:23 (since Wed May 05 09:15:03 UTC 2021)
Outgoing Interface: GigabitEthernet0/0/0/2, Outgoing Label: 202104
Router-IDs: local 1.1.1.1
downstream 21.21.21.21
Soft Preemption: None
SRLGs: not collected
Path Info:
Outgoing:
Explicit Route:
Strict, 20.1.21.21
Strict, 20.21.22.22
Strict, 22.22.22.22
➢ A2-R33 and A2-R31 are BFD neighbors, and the client protocol of BFD is FRR
A2-R33#show ip rsvp hello bfd nbr detail
Hello Client Neighbors
▪ Now, let’s disable A2-R33--A2-R41 link and see what is the new backup path
A2-R31:
!
interface Gi4
shutdown
▪ For a very short time, we see the new backup path is via A2-R33 :
➢ This is because we are also using a dynamic fallback path option, and the headend is
configured to reoptimize automatically the TE LSP for a better path after 30 seconds.
A2-XR32:
!
interface Tunnel-te1
no path-option 2 dynamic
A2-R31:
!
interface Gi4
shutdown
▪ The backup path changes via A2-R33, but after a short time, it changes again via C-
XR6. The reason is that the hops in the explicit-path on A2-XR32 are configured as
“strict”, and hence the tunnel signaling is broken.
Strict means that the next address in the explicit path belongs to an
adjacent router to the router in the sequence.
Loose means that the next address can belong to a router that is not
necesserly adjacent.
A2-XR32:
!
explicit-path name A2-XR32_To_C-XR6
index 1 next-address loose ipv4 unicast 33.33.33.33
index 2 next-address loose ipv4 unicast 31.31.31.31
index 3 next-address loose ipv4 unicast 6.6.6.6
▪ Finally the backup path via A2-R33 and does not change.
A2-R31:
!
interface Gi4
no shut
Note: After that action, we need to let a little time for the Tunnel to reoptimize its best
path using the configured explicit-path.
CE-R51#debug ip icmp
ICMP packet debugging is on
!
CE-R51#ping 192.168.50.41
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.50.41, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
➢ To make it works, I had to clear the bgp table and restart the bgp process on both A1-
XR22 and X2-XR32.
Clear bgp *
Process bgp restart
CE-R51#ping 192.168.50.41
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.50.41, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 31/34/37 ms
CE-R51#
*May 6 18:57:49.181: ICMP: echo reply rcvd, src 192.168.50.41, dst 192.168.50.51, topology
BASE, dscp 0 topoid 0
*May 6 18:57:49.212: ICMP: echo reply rcvd, src 192.168.50.41, dst 192.168.50.51, topology
BASE, dscp 0 topoid 0
*May 6 18:57:49.250: ICMP: echo reply rcvd, src 192.168.50.41, dst 192.168.50.51, topology
BASE, dscp 0 topoid 0
*May 6 18:57:49.286: ICMP: echo reply rcvd, src 192.168.50.41, dst 192.168.50.51, topology
BASE, dscp 0 topoid 0
*May 6 18:57:49.318: ICMP: echo reply rcvd, src 192.168.50.41, dst 192.168.50.51, topology
BASE, dscp 0 topoid 0
Objective
First we will configure Segment-Routing and TI-LFA in all IGP domains and prefer LDP as
MPLS control-plane. Then we will prefer SR and ensure an equivalent BGP Prefix-SID is
allocated for inter-domain communication, and it remains the same end-to-end. Finally we
will entirely remove LDP from all IGP domains. This change will also require to reconfigure
the RED TE path with SRTE.
Target topology
Access 1 - ASBR
C-XR1, C-XR11:
!
segment-routing
global-block 16000 23999
!
router ospf 10
segment-routing mpls
fast-reroute per-prefix ti-lfa enable
!
area 0
interface lo0
prefix-sid index X <<< X is Router Node ID
Access 1 - P and PE
A1-XR21, A1-XR22:
!
segment-routing
global-block 16000 23999
!
router ospf 10
segment-routing mpls
fast-reroute per-prefix ti-lfa enable
!
area 0
interface lo0
prefix-sid index X <<< X is Router Node ID
<snip>
SID Prefix/Mask
-------- ------------------
1 1.1.1.1/32
11 11.11.11.11/32
21 21.21.21.21/32
22 22.22.22.22/32 (L)
23 23.23.23.23/32
A1-XR21:
!
interface Gi0/0/0/0-1-2-3
shutdown
A1-XR21:
!
rollback config last 1
RP/0/0/CPU0:CE-XR41#ping 192.168.50.51
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.50.51, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 29/33/39 ms
SW1#ping 192.168.100.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.100.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 21/28/39 ms
SW1#ping 192.168.120.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.120.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 20/21/25 ms
SW1#ping 192.168.140.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.140.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 20/24/30 ms
Access 2 - ASBR
C-XR6, C-XR16:
!
segment-routing
global-block 16000 23999
!
router ospf 20
segment-routing mpls
fast-reroute per-prefix ti-lfa enable
!
area 0
interface lo0
prefix-sid index X <<< X is Router Node ID
Access 2 - P and PE
A2-R31, A2-R33:
!
segment-routing mpls
global-block 16000 23999
!
connected-prefix-sid-map
address-family ipv4
X.X.X.X/32 index X <<< X is Router Node ID
!
router ospf 20
segment-routing mpls
segment-routing area 0 mpls
fast-reroute per-prefix ti-lfa
fast-reroute per-prefix ti-lfa area 0
<snip>
SID Prefix/Mask
-------- ------------------
6 6.6.6.6/32
16 16.16.16.16/32
31 31.31.31.31/32
32 32.32.32.32/32 (L)
33 33.33.33.33/32
A2-R31:
!
interface range Gi1-4
shutdown
A2-R31:
!
interface range Gi1-4
no shut
RP/0/0/CPU0:CE-XR41#ping 192.168.50.51
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.50.51, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 29/33/39 ms
SW1#ping 192.168.100.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.100.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 21/28/39 ms
SW1#ping 192.168.120.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.120.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 20/21/25 ms
SW1#ping 192.168.140.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.140.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 20/24/30 ms
Core - ASBR
C-XR10:
!
segment-routing
global-block 16000 23999
!
router isis 1
address-family ipv4 unicast
metric-style wide
segment-routing mpls
!
interface lo0
address-family ipv4 unicast
prefix-sid index 10
Service RR
C-R110:
!
segment-routing mpls
global-block 16000 23999
!
connected-prefix-sid-map
address-family ipv4
110.110.110.110/32 index 110
!
router isis 1
metric-style wide
segment-routing mpls
<snip>
▪ Segment-Routing labels
L2 1.1.1.1/32 [50/115]
via 10.1.2.1, GigabitEthernet0/0/0/0, C-XR1, SRGB Base: 16000, Weight: 0
Backup path: TI-LFA (link), via 10.2.3.3, GigabitEthernet0/0/0/1 C-XR3, SRGB Base: 16000,
Weight: 0, Metric: 110
P node: C-XR3.00 [3.3.3.3], Label: ImpNull
Q node: C-XR1.00 [1.1.1.1], Label: 100315
Prefix label: ImpNull
Backup-src: C-XR1.00
L2 3.3.3.3/32 [10/115]
via 10.2.3.3, GigabitEthernet0/0/0/1, C-XR3, SRGB Base: 16000, Weight: 0
Backup path: TI-LFA (link), via 10.2.12.12, GigabitEthernet0/0/0/4 C-XR12, SRGB Base:
16000, Weight: 0, Metric: 30
P node: C-XR13.00 [13.13.13.13], Label: 16013
Prefix label: 16003
Backup-src: C-XR3.00
L2 4.4.4.4/32 [21/115]
via 10.2.12.12, GigabitEthernet0/0/0/4, C-XR12, SRGB Base: 16000, Weight: 0
Backup path: TI-LFA (link), via 10.2.3.3, GigabitEthernet0/0/0/1 C-XR3, SRGB Base: 16000,
Weight: 0, Metric: 41
P node: C-XR13.00 [13.13.13.13], Label: 16013
Prefix label: 16004
Backup-src: C-XR4.00
L2 5.5.5.5/32 [31/115]
via 10.2.12.12, GigabitEthernet0/0/0/4, C-XR12, SRGB Base: 16000, Weight: 0
Backup path: TI-LFA (link), via 10.2.3.3, GigabitEthernet0/0/0/1 C-XR3, SRGB Base: 16000,
Weight: 0, Metric: 51
P node: C-XR13.00 [13.13.13.13], Label: 16013
Prefix label: 16005
Backup-src: C-XR5.00
L2 6.6.6.6/32 [71/115]
via 10.2.12.12, GigabitEthernet0/0/0/4, C-XR12, SRGB Base: 16000, Weight: 0
Backup path: TI-LFA (link), via 10.2.3.3, GigabitEthernet0/0/0/1 C-XR3, SRGB Base: 16000,
Weight: 0, Metric: 91
P node: C-XR13.00 [13.13.13.13], Label: 16013
Prefix label: 16006
Backup-src: C-XR6.00
L2 10.10.10.10/32 [10/115]
via 10.2.10.10, GigabitEthernet0/0/0/3, C-XR10, SRGB Base: 16000, Weight: 0
No FRR backup
L2 11.11.11.11/32 [11/115]
Converged SDN Transport for CCIE Service Provider v5 | v202104
© 2021 Joël François
Page 229 out of 326
via 10.2.12.12, GigabitEthernet0/0/0/4, C-XR12, SRGB Base: 16000, Weight: 0
Backup path: TI-LFA (link), via 10.2.3.3, GigabitEthernet0/0/0/1 C-XR3, SRGB Base: 16000,
Weight: 0, Metric: 31
P node: C-XR13.00 [13.13.13.13], Label: 16013
Prefix label: 16011
Backup-src: C-XR11.00
L2 12.12.12.12/32 [10/115]
via 10.2.12.12, GigabitEthernet0/0/0/4, C-XR12, SRGB Base: 16000, Weight: 0
Backup path: TI-LFA (link), via 10.2.3.3, GigabitEthernet0/0/0/1 C-XR3, SRGB Base: 16000,
Weight: 0, Metric: 30
P node: C-XR13.00 [13.13.13.13], Label: 16013
Prefix label: 16012
Backup-src: C-XR12.00
L2 13.13.13.13/32 [20/115]
via 10.2.3.3, GigabitEthernet0/0/0/1, C-XR3, SRGB Base: 16000, Weight: 0
Backup path: LFA, via 10.2.12.12, GigabitEthernet0/0/0/4, C-XR12, SRGB Base: 16000,
Weight: 0, Metric: 20
via 10.2.12.12, GigabitEthernet0/0/0/4, C-XR12, SRGB Base: 16000, Weight: 0
Backup path: LFA, via 10.2.3.3, GigabitEthernet0/0/0/1, C-XR3, SRGB Base: 16000,
Weight: 0, Metric: 20
L2 14.14.14.14/32 [11/115]
via 10.2.12.12, GigabitEthernet0/0/0/4, C-XR12, SRGB Base: 16000, Weight: 0
Backup path: TI-LFA (link), via 10.2.3.3, GigabitEthernet0/0/0/1 C-XR3, SRGB Base: 16000,
Weight: 0, Metric: 31
P node: C-XR13.00 [13.13.13.13], Label: 16013
Prefix label: 16014
Backup-src: C-XR14.00
L2 15.15.15.15/32 [21/115]
via 10.2.12.12, GigabitEthernet0/0/0/4, C-XR12, SRGB Base: 16000, Weight: 0
Backup path: TI-LFA (link), via 10.2.3.3, GigabitEthernet0/0/0/1 C-XR3, SRGB Base: 16000,
Weight: 0, Metric: 41
P node: C-XR13.00 [13.13.13.13], Label: 16013
Prefix label: 16015
Backup-src: C-XR15.00
L2 16.16.16.16/32 [12/115]
via 10.2.12.12, GigabitEthernet0/0/0/4, C-XR12, SRGB Base: 16000, Weight: 0
Backup path: TI-LFA (link), via 10.2.3.3, GigabitEthernet0/0/0/1 C-XR3, SRGB Base: 16000,
Weight: 0, Metric: 32
P node: C-XR13.00 [13.13.13.13], Label: 16013
Prefix label: 16016
Backup-src: C-XR16.00
L2 110.110.110.110/32 [31/115]
via 10.2.12.12, GigabitEthernet0/0/0/4, C-XR12, SRGB Base: 16000, Weight: 0
Backup path: TI-LFA (link), via 10.2.3.3, GigabitEthernet0/0/0/1 C-XR3, SRGB Base: 16000,
Weight: 0, Metric: 51
P node: C-XR13.00 [13.13.13.13], Label: 16013
Prefix label: 16110
Backup-src: C-R110.00
Converged SDN Transport for CCIE Service Provider v5 | v202104
© 2021 Joël François
Page 230 out of 326
▪ Verify L2VPN services for Customer 1
RP/0/0/CPU0:CE-XR41#ping 192.168.50.51
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.50.51, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 29/33/39 ms
SW1#ping 192.168.120.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.120.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 20/21/25 ms
SW1#ping 192.168.140.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.140.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 20/24/30 ms
Access 1
A1-R23
!
segment-routing mpls
set-attributes
address-family ipv4
sr-label-preferred
Access 2
A2-R31, A2-R33:
!
segment-routing mpls
set-attributes
address-family ipv4
sr-label-preferred
C-R110:
!
segment-routing mpls
set-attributes
address-family ipv4
sr-label-preferred
▪ Below trace from A1-XR22 to reach remote PE A2-XR32 shows a 2 labels stack.
First label is the IGP SR label to reach the ASBR which is the next-hop of the BGP-LU
Prefix-SID label that comes second. BGP-LU Prefix-SID 16032 remains unchanged
end-to-end, whereas the IGP label changes in every IGP domain in case it needs to be
resolved.
▪ BGP Prefix-SID label 16022 is received on C-XR6 from C-XR1 and C-XR11 to reach
A1-XR22’s loopback. That label is derived from IGP Prefix-SID from Access 1.
➢ From BGP viewpoint, the best path to reach A1-XR22 is via C-XR11.
This is due to the calculated AIGP path which is better via C-XR11.
➢ But on C-XR6, remember that we have also an active MPLS-TE tunnel for the RED path
that overrides BGP best path calculation because that tunnel is configured to transit via C-
XR1 to reach A1-XR22.
RP/0/0/CPU0:CE-XR41#ping 192.168.50.51
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.50.51, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 29/33/39 ms
SW1#ping 192.168.120.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.120.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 20/21/25 ms
SW1#ping 192.168.140.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.140.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 20/24/30 ms
Access 1
A1-R23:
!
no mpls ldp session protection
no mpls ldp discovery targeted-hello accept
!
router ospf 10
no fast-reroute per-prefix remote-lfa area 0 tunnel mpls-ldp
no mpls ldp sync
no mpls ldp autoconfig
!
no mpls ldp router-id Loopback0
A2-R31, A2-R33:
!
no mpls ldp session protection
no mpls ldp discovery targeted-hello accept
!
router ospf 20
no fast-reroute per-prefix remote-lfa area 0 tunnel mpls-ldp
no mpls ldp sync
no mpls ldp autoconfig
!
no mpls ldp router-id Loopback0
C-XR3/5, C-XR12/13/14/15:
!
router isis 1
address-family ipv4 unicast
no mpls ldp auto-config
!
interface Gi0/0/0/0
address-family ipv4 unicast
no fast-reroute per-prefix remote-lfa tunnel mpls-ldp level 2
no mpls ldp sync
!
interface Gi0/0/0/1
address-family ipv4 unicast
no fast-reroute per-prefix remote-lfa tunnel mpls-ldp level 2
no mpls ldp sync
!
interface Gi0/0/0/2
address-family ipv4 unicast
no fast-reroute per-prefix remote-lfa tunnel mpls-ldp level 2
no mpls ldp sync
!
interface Gi0/0/0/4
address-family ipv4 unicast
no fast-reroute per-prefix remote-lfa tunnel mpls-ldp level 2
no mpls ldp sync
!
no mpls ldp
C-XR10:
!
router isis 1
address-family ipv4 unicast
no mpls ldp auto-config
!
interface Gi0/0/0/0
address-family ipv4 unicast
no mpls ldp sync
!
no mpls ldp
C-XR2, C-XR4:
!
router isis 1
address-family ipv4 unicast
no mpls ldp auto-config
!
interface Gi0/0/0/0
address-family ipv4 unicast
no fast-reroute per-prefix remote-lfa tunnel mpls-ldp level 2
no mpls ldp sync
!
interface Gi0/0/0/1
address-family ipv4 unicast
no fast-reroute per-prefix remote-lfa tunnel mpls-ldp level 2
no mpls ldp sync
!
interface Gi0/0/0/2
address-family ipv4 unicast
no fast-reroute per-prefix remote-lfa tunnel mpls-ldp level 2
no mpls ldp sync
!
interface Gi0/0/0/3
address-family ipv4 unicast
no mpls ldp sync
!
interface Gi0/0/0/4
address-family ipv4 unicast
no fast-reroute per-prefix remote-lfa tunnel mpls-ldp level 2
no mpls ldp sync
!
no mpls ldp
On all XE routers:
!
interface GiX
no mpls traffic-eng tunnels
no ip rsvp bandwidth
On all XR routers:
!
no mpls traffic-eng
no rsvp
A2-R33:
!
no interface Tunnel1
A2-XR32:
!
segment-routing
traffic-eng
segment-list SIDLIST_TO_C-XR6
index 1 mpls label 16033
index 2 mpls label 16031
index 3 mpls label 16006
index 4 mpls label 15900 <<< Binding-SID of C-XR6
!
policy SRTE_TO_C-XR6
color 777 end-point ipv4 6.6.6.6
autoroute
metric relative -1
include all
!
candidate-paths
preference 200
explicit segment-list SIDLIST_TO_C-XR6
▪ RED path trace is correct. As expected, it takes the configured explicit-paths to final
destination.
➢ That trace shows the 2 configured Binding-SID used to stitch the 3 SRTE policies
together which forms that end-to-end LSP.
➢ All labels before the Binding-SID are the ones configured in the explicit-paths.
➢ Label after the Binding-ID is the BGP Prefix-SID which is derived from the IGP Prefix-
SID used in OSPF domain 1 to reach A1-XR22.
➢ It looks like the pseudowire between the 2 PE is operational, but CE-to-CE connectivity
is broken.
RP/0/0/CPU0:CE-XR41#ping 192.168.50.51
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.50.51, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
RP/0/0/CPU0:CE-XR41#ping 192.168.50.51
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.50.51, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
RP/0/0/CPU0:CE-XR41#sh arp
-------------------------------------------------------------------------------
0/0/CPU0
-------------------------------------------------------------------------------
Address Age Hardware Addr State Type Interface
192.168.50.41 - 5254.0012.f76e Interface ARPA GigabitEthernet0/0/0/0.50
192.168.50.51 - 0000.0000.0000 Deleted ARPA GigabitEthernet0/0/0/0.50
▪ If we disable the SRTE tunnel, then CE-to-CE traffic sent through the EVPN-VPWS
pseudowire is working instantly.
RP/0/RP0/CPU0:A2-XR32(config)#segment-routing
RP/0/RP0/CPU0:A2-XR32(config-sr)#no traffic-eng
RP/0/RP0/CPU0:A2-XR32(config-sr)#commit label SRTE
RP/0/0/CPU0:CE-XR41#ping 192.168.50.51
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.50.51, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 19/27/59 ms
A2-XR32:
!
l2vpn
pw-class 3222
encapsulation mpls
preferred-path sr-te policy srte_c_777_ep_6.6.6.6 fallback disable
!
!
xconnect group evpn_vpws
p2p evpn1
interface GigabitEthernet0/0/0/4.10
neighbor evpn evi 2 target 5 source 10
pw-class 3222
RP/0/0/CPU0:CE-XR41#ping 192.168.50.51
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.50.51, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 29/29/29 ms
SW1#ping 192.168.100.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.100.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 21/28/39 ms
SW1#ping 192.168.120.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.120.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 20/21/25 ms
SW1#ping 192.168.140.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.140.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 20/24/30 ms
Eg: on A1-XR22
RP/0/RP0/CPU0:A1-XR22#sh mpls label table
Table Label Owner State Rewrite
----- ------- ------------------------------- ------ -------
0 0 LSD(A) InUse Yes
0 1 LSD(A) InUse Yes
0 2 LSD(A) InUse Yes
0 13 LSD(A) InUse Yes
0 15000 LSD(A) InUse No
0 16000 OSPF(A):ospf-10 InUse No
BGP-VPNv4(A):bgp-default InUse No
0 202205 BGP-VPNv4(A):bgp-default InUse No
0 202209 BGP-VPNv4(A):bgp-default InUse No
0 202210 OSPF(A):ospf-10 InUse Yes
0 202211 L2VPN(A) InUse Yes
0 202212 OSPF(A):ospf-10 InUse Yes
0 202213 OSPF(A):ospf-10 InUse Yes
0 202214 OSPF(A):ospf-10 InUse Yes
0 202215 OSPF(A):ospf-10 InUse Yes
0 202216 OSPF(A):ospf-10 InUse Yes
Objective
In the previous lab, we configured SR in each domain and we migrated from LDP to SR.
Then, we removed LDP in all domains to have MPLS labels for IGP and BGP allocated
only by Segment-routing. Consequently, we confirmed we got a BGP Prefix-SID label that
remains unchanged end-to-end. Now the tasks of this lab consist to ease the transition to
the converged SDN transport network. To achieve that we will pre-configure specific SDN
features, but without enable them. Thoses features will be enabled only in the next lab,
where the ultimate goal will be to remove BGP-LU and rely only on Segment-routing/SDN
to establish an end-to-end transport LSP.
Target topology
▪ Advertisement of OSPF and ISIS link-state database from ASBR to PCE via BGP-LS
C-XR10:
!
router bgp 100
address-family link-state link-state
!
neighbor 1.1.1.1
remote-as 100
update-source Loopback0
address-family link-state link-state
route-reflector-client
!
neighbor 11.11.11.11
remote-as 100
update-source Loopback0
address-family link-state link-state
route-reflector-client
!
neighbor 6.6.6.6
remote-as 100
update-source Loopback0
address-family link-state link-state
route-reflector-client
!
neighbor 16.16.16.16
remote-as 100
update-source Loopback0
address-family link-state link-state
route-reflector-client
▪ We need to feed the IGP link-state database in BGP-LS from the ASBR, so that PCE
can receive all IGP link-state topologies.
C-XR1, C-XR11:
!
router ospf 10
distribute link-state instance-id 1020
!
router isis 1
distribute link-state instance-id 1010
C-XR6, C-XR16:
!
router ospf 20
distribute link-state instance-id 1030
!
router isis 1
distribute link-state instance-id 1010
▪ Now PCE router is receiving IGP link-state prefixes from the ASBR
Versions:
Process bRIB/RIB SendTblVer
Speaker 5898 5898
Flags: 0x00000001+0x00010000;
Last Modified: May 16 07:08:17.434 for 00:40:13
Paths: (4 available, best #3)
Advertised to update-groups (with more than one peer):
0.1
Path #1: Received by speaker 0
Flags: 0x4000000000020205, import: 0x20
Not advertised to any peer
Local, (Received from a RR-client)
1.1.1.1 (metric 60) from 1.1.1.1 (1.1.1.1)
Origin IGP, localpref 100, valid, internal
Received Path ID 0, Local Path ID 0, version 0
Link-state: MSD: Type 1 Value 10, Node-name: C-XR14, ISIS area: 49.01.00
Local TE Router-ID: 14.14.14.14, SRGB: 16000:8000 ,
SR-ALG: 0 SR-ALG: 1 SRLB: 15000:1000
Path #2: Received by speaker 0
Flags: 0x4000000000020205, import: 0x20
Not advertised to any peer
Local, (Received from a RR-client)
6.6.6.6 (metric 81) from 6.6.6.6 (6.6.6.6)
Origin IGP, localpref 100, valid, internal
Received Path ID 0, Local Path ID 0, version 0
Link-state: MSD: Type 1 Value 10, Node-name: C-XR14, ISIS area: 49.01.00
Local TE Router-ID: 14.14.14.14, SRGB: 16000:8000 ,
SR-ALG: 0 SR-ALG: 1 SRLB: 15000:1000
Topology nodes: 20
Prefixes: 24
Prefix SIDs: 24
Links: 76
Adjacency SIDs: 148
Node 20
TE router ID: 32.32.32.32
OSPF router ID: 32.32.32.32 area ID: 0 domain ID: 1030
Prefix SID:
Prefix 32.32.32.32, label 16032 (regular)
C-XR10:
!
pce
address ipv4 10.10.10.10
segment-routing
traffic-eng
A1-XR22:
!
segment-routing
traffic-eng
pcc
source-address ipv4 22.22.22.22
pce address ipv4 10.10.10.10
A2-XR32:
!
segment-routing
traffic-eng
pcc
source-address ipv4 32.32.32.32
pce address ipv4 10.10.10.10
A1-R23:
!
mpls traffic-eng tunnels
mpls traffic-eng pcc peer 10.10.10.10 source 23.23.23.23
A2-R33:
!
mpls traffic-eng tunnels
mpls traffic-eng pcc peer 10.10.10.10 source 33.33.33.33
C-XR1, C-XR11:
!
route-policy PCE_S-RR
if destination in (10.10.10.10/32,110.110.110.110/32) then
pass
endif
end-policy
!
router ospf 10
redistribute isis 1 route-policy PCE_S-RR
C-XR6, C-XR16:
!
route-policy PCE_S-RR
if destination in (10.10.10.10/32,110.110.110.110/32) then
pass
endif
end-policy
!
router ospf 20
redistribute isis 1 route-policy PCE_S-RR
C-XR1, C-XR11:
!
route-policy PE
if destination in (22.22.22.22/32,23.23.23.23/32) then
pass
endif
end-policy
!
router isis 1
address-family ipv4 unicast
redistribute ospf 10 route-policy PE
C-XR6, C-XR16:
!
route-policy PE
if destination in (32.32.32.32/32,33.33.33.33/32) then
pass
endif
end-policy
!
router isis 1
address-family ipv4 unicast
redistribute ospf 20 route-policy PE
➢ Router loopbacks are advertised via BGP and also via OSPF/ISIS. OSPF/ISIS have a
better AD than BGP, so the preferred path to reach those routers is now via IGP; this is
what we want.
▪ Confirmation that PCE, PCC and Service-RR are learned via IGP
▪ All PCEP sessions between PCE and PCC routers are established
Objective
In the first place, we will enable SDN by configuring the SRTE policies to rely on SR-PCE
to calculate an LSP path, by specifying the tailends. Then, we will not specify the tailends,
and use On-demand Next-hop
Target topology
RED Path
A1-XR22:
!
extcommunity-set opaque RED
777
end-set
!
route-policy COLOR_777
if destination in (42.42.42.42/32) then
set extcommunity color RED
endif
end-policy
!
router bgp 100
neighbor 110.110.110.110
address-family vpnv4 unicast
route-policy COLOR_777 out
A2-XR32:
!
segment-routing
traffic-eng
maximum-sid-depth 8
segment-list SIDLIST_To_A1-XR22
index 1 mpls label 16033
index 2 mpls label 16031
index 3 mpls label 16006
index 4 mpls label 16004
index 5 mpls label 16005
index 6 mpls label 100517 <<< Adjacency SID is used to reach C-XR3 directly
index 7 mpls label 16002
index 8 mpls label 16001
index 9 mpls label 16021
index 10 mpls label 16022
!
policy SRTE_To_A1-XR22
binding-sid mpls 50000
color 777 end-point ipv4 22.22.22.22
candidate-paths
preference 200
explicit segment-list SIDLIST_To_A2-XR22
!
router static
address-family ipv4 unicast
22.22.22.22/32 Null0
The static route to Null0 creates a CEF entry for remote PE.
This is required for A2-XR32 prefix to be recognized as best (>) in BGP table,
and hence to have a functionnal SRTE policy. Additionally, that static routes
is preempting the existing BGP-LU route.
Note: SRTE tunnel is down because the configured Maximum SID depth (MSD) value is
too small to account the configured SID-list requiring an MSD value of 9.
A2-XR32:
!
segment-routing
traffic-eng
maximum-sid-depth 9
Note: With that new MSD value configured the tunnel is now operational. In that output,
the MSD value is not shown because the SRTE policy is not delegating the path
computation to PCE.
A1-XR52:
!
interface Loopback152
ipv4 address 152.152.152.152 255.255.255.255
!
router bgp 45
address-family ipv4 unicast
network 152.152.152.152/32
A2-XR32:
!
extcommunity-set opaque BLUE
666
end-set
!
extcommunity-set opaque GREEN
152
end-set
!
route-policy CUST-2
if rd in (100:32) and destination in (52.52.52.52/32) then
set extcommunity color BLUE
endif
if rd in (100:32) and destination in (152.152.152.152/32) then
set extcommunity color GREEN
endif
end-policy
!
router bgp 100
neighbor 110.110.110.110
address-family vpnv4 unicast
route-policy CUST-2 out
A1-XR22:
!
segment-routing
global-block 16000 23999
traffic-eng
on-demand color 152
dynamic
pcep
!
metric
type hopcount
!
!
maximum-sid-depth 8
!
on-demand color 666
dynamic
pcep
!
metric
type igp
!
!
!
pcc
source-address ipv4 22.22.22.22
pce address ipv4 10.10.10.10
!
router static
address-family ipv4 unicast
32.32.32.32/32 Null0
Note: In that output, the default Maximum SID depth value (10) is shown because the
SRTE policy is delegating the path computation to PCE.
Note: In that output, the Maximum SID depth value is shown because that SRTE policy is
delegating the path computation to PCE.
Note: RED traffic takes the expected path using the configured SID-list.
Note: BLUE traffic takes the shortest path using IGP metric type.
Note: GREEN traffic takes the shortest path using hopcount metric type.
A1-XR22:
!
segment-routing
traffic-eng
no on-demand color 152
no on-demand color 666
A2-XR32:
!
segment-routing
traffic-eng
no segment-list SIDLIST_To_A2-XR22
no maximum-sid-depth 9
no policy SRTE_To_A1-XR22
C-XR10:
!
pce
address ipv4 10.10.10.10
segment-routing
traffic-eng
segment-list name SIDLIST_To_A1-XR22
index 1 mpls label 16033
index 2 mpls label 16031
index 3 mpls label 16006
index 4 mpls label 16004
index 5 mpls label 16005
index 6 mpls label 100517
index 7 mpls label 16002
index 8 mpls label 16001
index 9 mpls label 16021
index 10 mpls label 16022
!
peer ipv4 22.22.22.22
policy P1_A1-XR22_C152
color 152 end-point ipv4 32.32.32.32
candidate-paths
preference 200
dynamic mpls
metric
type hopcount
!
policy P2_A1-XR22_C666
color 666 end-point ipv4 32.32.32.32
candidate-paths
preference 200
dynamic mpls
metric
type igp
!
peer ipv4 32.32.32.32
policy P1_A2-XR32_C777
binding-sid mpls 50000
color 777 end-point ipv4 22.22.22.22
candidate-paths
preference 200
explicit segment-list SIDLIST_To_A1-XR22
Note: RED traffic takes the expected path with explicit metric type and SID-list.
Note: BLUE traffic takes the shortest path using IGP metric type.
Note: GREEN traffic takes the shortest path using hopcount metric type.
Conclusion
A2-XR32:
!
segment-routing
global-block 16000 23999
traffic-eng
segment-list SIDLIST_To_A1-XR22
index 1 mpls label 16033
index 2 mpls label 16031
index 3 mpls label 16006
index 4 mpls label 16004
index 5 mpls label 16005
index 6 mpls label 100517
index 7 mpls label 16002
index 8 mpls label 16001
index 9 mpls label 16021
index 10 mpls label 16022
!
maximum-sid-depth 9
policy SRTE_To_A1-XR22
binding-sid mpls 50000
color 777 end-point ipv4 22.22.22.22
candidate-paths
preference 200
explicit segment-list SIDLIST_To_A2-XR22
A1-XR22:
!
segment-routing
traffic-eng
policy P1_A1-XR22_C152
color 152 end-point ipv4 32.32.32.32
candidate-paths
preference 100
dynamic
pcep
!
metric
type igp
!
policy P2_A1-XR22_C666
color 666 end-point ipv4 32.32.32.32
candidate-paths
preference 100
dynamic
pcep
!
metric
type igp
!
pcc
source-address ipv4 22.22.22.22
pce address ipv4 10.10.10.10
CE-XR42:
!
RP/0/0/CPU0:CE-XR42#tra 52.52.52.52 source lo0
Note: Both BLUE and GREEN traffic is using exactly the same path to reach BLUE and
GREEN customer networks.
A1-XR22:
!
segment-routing
traffic-eng
policy P1_A1-XR22_C152
candidate-paths
preference 100
constraints
disjoint-path group-id 1 type node
!
policy P2_A1-XR22_C666
candidate-paths
preference 100
constraints
disjoint-path group-id 1 type node
Note: The 2 node-disjoint paths configured between the same pair of nodes do not share
any network resources.
Configuration
C-R110:
!
ip bgp new-format
!
router bgp 100
address-family vpnv4
neighbor iBGP send-community both
A1-R23, A2-R33:
Converged SDN Transport for CCIE Service Provider v5 | v202104
© 2021 Joël François
Page 311 out of 326
!
ip bgp new-format
!
router bgp 100
address-family vpnv4
neighbor 110.110.110.110 send-community both
A1-R23:
!
route-map COLOR_43_RMAP permit 10
match ip address WEST_TRAFFIC
set community 43
!
router bgp 100
address-family vpnv4
neighbor 110.110.110.110 route-map COLOR_43_RMAP out
A1-R33:
!
route-map COLOR_53_RMAP permit 10
match ip address EAST_TRAFFIC
set community 53
!
router bgp 100
address-family vpnv4
neighbor 110.110.110.110 route-map COLOR_53_RMAP out
A1-R23:
!
! SRTE ODN policy used for both L2VPN & L3VPN
mpls traffic-eng lsp attributes L2VPN-L3VPN-ODN
priority 7 7
path-selection metric igp
pce
!
ip community-list 1 permit 53
!
route-map BGP_TE_MAP permit 10
A2-R33:
!
! SRTE ODN policy used for both L2VPN & L3VPN
mpls traffic-eng lsp attributes L2VPN-L3VPN-ODN
priority 7 7
path-selection metric igp
pce
bandwidth 50000
!
ip community-list 1 permit 43
!
route-map BGP_TE_MAP permit 10
match community 1
set attribute-set L2VPN-L3VPN-ODN
!
router bgp 100
address-family vpnv4
neighbor 110.110.110.110 route-map BGP_TE_MAP in
▪ Enable auto-tunnel
A1-R23:
!
mpls traffic-eng tunnels
mpls traffic-eng auto-tunnel p2p tunnel-num min 2000 max 5000
mpls traffic-eng auto-tunnel p2p config unnumbered-interface lo0
A1-R33:
!
mpls traffic-eng tunnels
mpls traffic-eng auto-tunnel p2p tunnel-num min 2000 max 5000
Converged SDN Transport for CCIE Service Provider v5 | v202104
© 2021 Joël François
Page 313 out of 326
mpls traffic-eng auto-tunnel p2p config unnumbered-interface lo0
A1-R23, A2-R33:
!
int range Gi1-3
mpls traffic-eng tunnels
▪ The mpls TE tunnel policy automatically creates a directly connected route entry at
destination to PE with its associated CEF entry.
➢ Verify BGP route coloring and binding SID with the VRF prefix
Config Parameters:
Bandwidth: 50000 kbps (Global) Priority: 7 7 Affinity: 0x0/0xFFFF
Metric Type: IGP (interface)
Path Selection:
Protection: any (default)
Path-selection Tiebreaker:
Global: not set Tunnel Specific: not set Effective: min-fill (default)
Hop Limit: disabled
Cost Limit: disabled
Path-invalidation timeout: 10000 msec (default), Action: Tear
AutoRoute: disabled LockDown: disabled Loadshare: 50000 [40000] bw-based
auto-bw: disabled
Attribute-set: L2VPN-L3VPN-ODN
Fault-OAM: disabled, Wrap-Protection: disabled, Wrap-Capable: No
Active Path Option Parameters:
State: dynamic path option 1 is active
BandwidthOverride: disabled LockDown: disabled Verbatim: disabled
PCEP Info:
Delegation state: Working: yes Protect: no
Delegation peer: 10.10.10.10
Working Path Info:
Request status: processed
Created via PCUpd message from PCE server: 10.10.10.10
PCE metric: 5, type: IGP
Reported paths:
Tunnel Name: A1-R23_t2001
LSPs:
LSP[0]:
source 23.23.23.23, destination 33.33.33.33, tunnel ID 2001, LSP ID 12
State: Admin up, Operation active
Binding SID: 202318
Setup type: SR
Bandwidth: requested 0, used 0
LSP object:
PLSP-ID 0x807D1, flags: D:0 S:0 R:0 A:1 O:2
Converged SDN Transport for CCIE Service Provider v5 | v202104
© 2021 Joël François
Page 317 out of 326
Metric type: IGP, Accumulated Metric 5
ERO:
SID[0]: Node, Label 16011, NAI: 11.11.11.11
SID[1]: Node, Label 16016, NAI: 16.16.16.16
SID[2]: Node, Label 16033, NAI: 33.33.33.33
<snip>
History:
Tunnel:
Time since created: 39 days, 22 hours, 46 minutes
Time since path change: 39 days, 22 hours, 45 minutes
Number of LSP IDs (Tun_Instances) used: 12
Current LSP: [ID: 12]
Uptime: 39 days, 22 hours, 45 minutes
Tun_Instance: 12
Segment-Routing Path Info (IGP information is not used)
Segment0[Node]: 11.11.11.11, Label: 16011
Segment1[Node]: 16.16.16.16, Label: 16016
Segment2[Node]: 33.33.33.33, Label: 16033
Config Parameters:
Bandwidth: 50000 kbps (Global) Priority: 7 7 Affinity: 0x0/0xFFFF
Metric Type: IGP (interface)
Path Selection:
Protection: any (default)
Path-selection Tiebreaker:
Global: not set Tunnel Specific: not set Effective: min-fill (default)
Hop Limit: disabled
Cost Limit: disabled
Path-invalidation timeout: 10000 msec (default), Action: Tear
AutoRoute: disabled LockDown: disabled Loadshare: 50000 [40000] bw-based
auto-bw: disabled
Attribute-set: L2VPN-L3VPN-ODN
Fault-OAM: disabled, Wrap-Protection: disabled, Wrap-Capable: No
Active Path Option Parameters:
State: dynamic path option 1 is active
BandwidthOverride: disabled LockDown: disabled Verbatim: disabled
PCEP Info:
Converged SDN Transport for CCIE Service Provider v5 | v202104
© 2021 Joël François
Page 318 out of 326
Delegation state: Working: yes Protect: no
Delegation peer: 10.10.10.10
Working Path Info:
Request status: processed
Created via PCUpd message from PCE server: 10.10.10.10
PCE metric: 5, type: IGP
Reported paths:
Tunnel Name: A2-R33_t2001
LSPs:
LSP[0]:
source 33.33.33.33, destination 23.23.23.23, tunnel ID 2001, LSP ID 24
State: Admin up, Operation active
Binding SID: 303314
Setup type: SR
Bandwidth: requested 0, used 0
LSP object:
PLSP-ID 0x807D1, flags: D:0 S:0 R:0 A:1 O:2
Metric type: IGP, Accumulated Metric 5
ERO:
SID[0]: Node, Label 16016, NAI: 16.16.16.16
SID[1]: Node, Label 16011, NAI: 11.11.11.11
SID[2]: Node, Label 16023, NAI: 23.23.23.23
<snip>
Tun_Instance: 24
Segment-Routing Path Info (IGP information is not used)
Segment0[Node]: 16.16.16.16, Label: 16016
Segment1[Node]: 11.11.11.11, Label: 16011
Segment2[Node]: 23.23.23.23, Label: 16023
Access domains are connected to Core domain using two borders routers
which are inline RR and get the same Anycast SID and the same IP address
for high availability any may use load-balancing.
C-XR1, C-XR11:
!
int lo111
ip address 111.111.111.111/32
!
router ospf 10
area 0
interface lo111
passive enable
prefix-sid index 111
C-XR6, C-XR16:
!
int lo166
ip address 166.166.166.166/32
!
router ospf 20
area 0
interface lo166
Chapter 9:
Lab 5 - Network Slicing
Objective
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Target topology