Cisco IOS XR MPLS TE Fast Reroute Example
In this example we will show Cisco IOS XR MPLS Traffic Engineering Fast Reroute configuration briefly.Here is our basic topology for this configuration:
We have configured MPLS TE tunnel between R5 and R1.
Configuration on head end router:
router ospf 1
router-id 5.5.5.5
area 0
mpls traffic-eng
interface GigabitEthernet0/1/0/0
mpls traffic-eng
interface GigabitEthernet0/1/0/0
rsvp
interface GigabitEthernet0/1/0/0
explicit-path name to-router5
index 1 next-address strict ipv4 unicast 4.4.4.4
index 2 next-address strict ipv4 unicast 3.3.3.3
index 3 next-address strict ipv4 unicast 5.5.5.5
interface tunnel-te5
ipv4 unnumbered Loopback0
load-interval 30
autoroute announce
destination 5.5.5.5
fast-reroute
path-option 1 explicit name to-router5
path-option 2 dynamic
We will protect the link between R4(4.4.4.4) and R3(3.3.3.3).When the link between R3 and R4 fails, all MPLS TE traffic will pass through Router2(2.2.2.2) until the new path converges(because we have secondary dynamic path option).
Configuration on Point of Local Repair router(router4):
router ospf 1
router-id 4.4.4.4
area 0
mpls traffic-eng
interface GigabitEthernet0/1/0/0
interface GigabitEthernet0/1/0/1
interface GigabitEthernet0/1/0/2
mpls traffic-eng
interface GigabitEthernet0/1/0/0
interface GigabitEthernet0/1/0/1
backup-path tunnel-te 23
interface GigabitEthernet0/1/0/2
rsvp
interface GigabitEthernet0/1/0/0
interface GigabitEthernet0/1/0/1
interface GigabitEthernet0/1/0/2
explicit-path name backupto-r3
index 1 next-address strict ipv4 unicast 2.2.2.2
index 2 next-address strict ipv4 unicast 3.3.3.3
interface tunnel-te23
ipv4 unnumbered Loopback0
load-interval 30
destination 3.3.3.3
path-option 1 explicit name backupto-r3
RP/0/RSP1/CPU0:Router4#show mpls traffic-eng fast-reroute database
LSP midpoint FRR information:
LSP Identifier Local Out Intf/ FRR Intf/ Status
Label Label Label
----------------------------- ------ ---------------- ---------------- -------
5.5.5.5 5 143987 Gi0/1/0/1:16014 tt23:16015 Ready
In this example we will show Cisco IOS XR MPLS Traffic Engineering Fast Reroute configuration briefly.Here is our basic topology for this configuration:
We have configured MPLS TE tunnel between R5 and R1.
Configuration on head end router:
router ospf 1
router-id 5.5.5.5
area 0
mpls traffic-eng
interface GigabitEthernet0/1/0/0
mpls traffic-eng
interface GigabitEthernet0/1/0/0
rsvp
interface GigabitEthernet0/1/0/0
explicit-path name to-router5
index 1 next-address strict ipv4 unicast 4.4.4.4
index 2 next-address strict ipv4 unicast 3.3.3.3
index 3 next-address strict ipv4 unicast 5.5.5.5
interface tunnel-te5
ipv4 unnumbered Loopback0
load-interval 30
autoroute announce
destination 5.5.5.5
fast-reroute
path-option 1 explicit name to-router5
path-option 2 dynamic
We will protect the link between R4(4.4.4.4) and R3(3.3.3.3).When the link between R3 and R4 fails, all MPLS TE traffic will pass through Router2(2.2.2.2) until the new path converges(because we have secondary dynamic path option).
Configuration on Point of Local Repair router(router4):
router ospf 1
router-id 4.4.4.4
area 0
mpls traffic-eng
interface GigabitEthernet0/1/0/0
interface GigabitEthernet0/1/0/1
interface GigabitEthernet0/1/0/2
mpls traffic-eng
interface GigabitEthernet0/1/0/0
interface GigabitEthernet0/1/0/1
backup-path tunnel-te 23
interface GigabitEthernet0/1/0/2
rsvp
interface GigabitEthernet0/1/0/0
interface GigabitEthernet0/1/0/1
interface GigabitEthernet0/1/0/2
explicit-path name backupto-r3
index 1 next-address strict ipv4 unicast 2.2.2.2
index 2 next-address strict ipv4 unicast 3.3.3.3
interface tunnel-te23
ipv4 unnumbered Loopback0
load-interval 30
destination 3.3.3.3
path-option 1 explicit name backupto-r3
RP/0/RSP1/CPU0:Router4#show mpls traffic-eng fast-reroute database
LSP midpoint FRR information:
LSP Identifier Local Out Intf/ FRR Intf/ Status
Label Label Label
----------------------------- ------ ---------------- ---------------- -------
5.5.5.5 5 143987 Gi0/1/0/1:16014 tt23:16015 Ready
What the heck is your tunnel head ? your explcit path makes no sense.
ReplyDeleteexplicit-path name to-router5
index 1 next-address strict ipv4 unicast 4.4.4.4
index 2 next-address strict ipv4 unicast 3.3.3.3
index 3 next-address strict ipv4 unicast 5.5.5.5
If either R1 or R5 is your head end
if R1 is your head R3 should be your next hop not R4
if R5 is your head then you named your own loopback as a next hop ?