IP addressing, BGP, OSPF, and LDP are already pre-configured. Note: the route-policy called PASS applied to the CE peering sesssion does not appear when booting up PE6 for some reason. You’ll need to add this after booting PE6.
Create a TE tunnel so that a tracert from CE1 to CE2 follows the path PE1-P2-P4-PE6, and likewise a tracert from CE2 to CE1 follows the path PE6-P4-P2-PE1.
CE1#traceroute 10.2.2.2 sou lo0 probe 1
Type escape sequence to abort.
Tracing the route to 10.2.2.2
VRF info: (vrf in name/id, vrf out name/id)
1 100.64.0.1 8 msec
2 10.1.2.2 [MPLS: Labels 25/24010 Exp 0] 13 msec
3 10.2.4.4 [MPLS: Labels 24009/24010 Exp 0] 21 msec
4 10.4.6.6 [MPLS: Label 24010 Exp 0] 9 msec
5 100.64.0.2 6 msec
CE2#traceroute 10.1.1.1 source lo0 probe 1
Type escape sequence to abort.
Tracing the route to 10.1.1.1
VRF info: (vrf in name/id, vrf out name/id)
1 100.64.0.1 5 msec
2 10.4.6.4 [MPLS: Labels 24010/16 Exp 0] 6 msec
3 10.2.4.2 [MPLS: Labels 26/16 Exp 0] 10 msec
4 100.64.0.1 [MPLS: Label 16 Exp 0] 5 msec
5 100.64.0.2 63 msec
Configure FRR with link-protection for the P2-P4 link. Verify that both MPLS-TE tunnels have FRR enabled.
Answers
This is a simple lab which I’d encourage you to repeat until you can preform the steps without hesitation. I timed myself at just under 7 minutes after configuring it a few times. The first time you preform the lab, it will likely take you significantly longer because you’ll inevitably get tripped up on a configuration parameter here and there.
First you must enable RSVP and MPLS-TE on all routers.
! IOS-XE
mpls traffic-eng tunnels
!
int GiX
mpls traffic-eng tunnels
ip rsvp bandwidth
!
router ospf 100
mpls traffic-eng area 0
mpls traffic-eng router-id lo0
! IOS-XR
router ospf 100
mpls traffic-eng router-id lo0
area 0
mpls traffic-eng
!
mpls traffic-eng
int Gi0/0/0/X
!
rsvp
int Gi0/0/0/X
bandwidth
You will need to decide on a method to make the path through P5 less prefered. You can create an explicit path avoiding the node, require the LSP to need more bandwidth than is available on P5’s interfaces, use TE metrics, or link-affinity colors. I decided to use TE metrics on Gi1 and Gi2 with a metric of 100 so that I could use a dynamic path-option.
Next you will need to configure a tunnel interface on each PE.
To configure FRR, you must configure the tunnel interfaces to request FRR, then configure the backup tunnel interfaces on P2 and P4 which will avoid the P2-P4 link.
! Add fast-reroute to each tunnel interface on PE1 and PE6
! On P2 and PE6 configure tunnel interfaces with an explicit path which avoids the P2-P4 link
! IOS-XE shown below:
ip explicit-path name name
index 1 exclude-address 10.2.4.X
!
int tunnel1
tunnel mpls traffic-eng path-option 1 explicit name name
! IOS-XR shown below:
epxlicit-path name name
index 1 exlucde-address ipv4 unicast 10.2.4.X
!
int tunnel-te1
path-option 1 explicit name name
! Add the tunnel as a backup option under the interface
! IOS-XE
int Gi2
mpls traffic-eng backup-path tun1
! IOS-XR
mpls traffic-eng
int Gi0/0/0/1
backup-path tunnel-te1
On P2 and P4, verify that the FRR tunnel is ready to protect the PE1-PE6 LSPs.
P2#show mpls traffic-eng fast-reroute database
P2P Headend FRR information:
Protected tunnel In-label Out intf/label FRR intf/label Status
--------------------------- -------- -------------- -------------- ------
P2P LSP midpoint frr information:
LSP identifier In-label Out intf/label FRR intf/label Status
--------------------------- -------- -------------- -------------- ------
1.1.1.1 1 [3] 27 Gi2:24011 Tu1:24011 ready
RP/0/RP0/CPU0:P4#show mpls traffic-eng fast-reroute database
Tue Nov 8 02:38:34.776 UTC
LSP midpoint FRR information:
LSP Identifier Local Label Out Intf : Label FRR Intf : Label Status
----------------------------- ----------- ------------------ ------------------ -------
6.6.6.6 1 [2] 24010 Gi0/0/0/1:26 tt1:26 Ready
