mpls te forwarding adjacency

[sachin30720041]

Hello,

I have the following setup.

csr1----csr2----csr3---csr4----csr5

I created two tunnels.

1) csr2 to csr4

2) csr4 to csr2.

I configured 'tunnel mpls traffic-eng forwarding-adj' and 'isis metric 1' commands under both the tunnels.  I expect metric of 5.5.5.5/32 to be 21 on R1. But 5.5.5.5/32's metric on R1 is 40. That means tunnel is not distributed in igp. What could be the reason? Below is the configuration of all the routers. 

csr1
--------------------
mpls traffic-eng tunnels

int gi1
ip address 100.10.20.1 255.255.255.0
no sh
ip router isis 1
ip rsvp bandwidth
mpls traffic-eng tunnels

int gi2
ip address 100.10.60.1 255.255.255.0
no sh
ip router isis 1
ip rsvp bandwidth
mpls traffic-eng tunnels

int lo0
ip address 1.1.1.1 255.255.255.255
ip router isis 1

router isis 1
net 49.0000.0000.0000.0001.00
metric-style wide
mpls traffic-eng router-id lo0
mpls traffic-eng level-1

csr2
-----------------------
mpls traffic-eng tunnels

int gi1
ip address 100.10.20.2 255.255.255.0
no sh
ip router isis 1
ip rsvp bandwidth
mpls traffic-eng tunnels

int gi2
ip address 100.20.30.2 255.255.255.0
no sh
ip router isis 1
ip rsvp bandwidth
mpls traffic-eng tunnels

int lo0
ip address 2.2.2.2 255.255.255.255
ip router isis 1

router isis 1
net 49.0000.0000.0000.0002.00
metric-style wide
mpls traffic-eng router-id lo0
mpls traffic-eng level-1


int tunnel1
ip unnumbered lo0
tunnel destination 4.4.4.4
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng path-option 1 dynamic
tunnel mpls traffic-eng forwarding-adj
isis metric 1 level-1

csr3
-----------------------
mpls traffic-eng tunnels

int gi1
ip address 100.30.40.3 255.255.255.0
no sh
ip router isis 1
ip rsvp bandwidth
mpls traffic-eng tunnels


int gi2
ip address 100.20.30.3 255.255.255.0
no sh
ip router isis 1
ip rsvp bandwidth
mpls traffic-eng tunnels


int lo0
ip address 3.3.3.3 255.255.255.255
ip router isis 1

router isis 1
net 49.0000.0000.0000.0003.00
metric-style wide
mpls traffic-eng router-id lo0
mpls traffic-eng level-1

csr4
-----------------------
mpls traffic-eng tunnels

int gi1
ip address 100.30.40.4 255.255.255.0
no sh
ip router isis 1
ip rsvp bandwidth
mpls traffic-eng tunnels

int gi2
ip address 100.40.50.4 255.255.255.0
no sh
ip router isis 1
ip rsvp bandwidth
mpls traffic-eng tunnels

int lo0
ip address 4.4.4.4 255.255.255.255
ip router isis 1


router isis 1
net 49.0000.0000.0000.0004.00
metric-style wide
mpls traffic-eng router-id lo0
mpls traffic-eng level-1

int tunnel1
ip unnumbered lo0
tunnel destination 2.2.2.2
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng path-option 1 dynamic
tunnel mpls traffic-eng forwarding-adj
isis metric 1

csr5
-----------------------
mpls traffic-eng tunnels

int gi1
ip address 100.50.80.5 255.255.255.0
no sh
ip router isis 1
ip rsvp bandwidth
mpls traffic-eng tunnels


int gi2
ip address 100.40.50.5 255.255.255.0
no sh
ip router isis 1
ip rsvp bandwidth
mpls traffic-eng tunnels


int lo0
ip address 5.5.5.5 255.255.255.255
ip router isis 1

router isis 1
net 49.0000.0000.0000.0005.00
metric-style wide
mpls traffic-eng router-id lo0
mpls traffic-eng level-1

Thanks,

Sachin

[MHM Cisco World]

follow

[Harold Ritter · Accepted solution]

Hi @sachin30720041 ,

If you shutdown the tunnel interface on CSR2, your metric from CSR1 to 5.5.5.5/32 should be 50 (10 for each hop + 10 for CSR5 lo0). The fact that the metric for 5.5.5.5/32 on CSR1 is 40 (10 to CSR2 + 10 to CSR4 over the tunnel + 10 to CSR5 + 10 for lo0) tells me that the forwarding adjacency (FA) is actually working. You can do a "show isis data CSR2.00-00 detail" to see whether the FA is included in CSR2 LSP.

Note: I don't think changing the isis metric for the FA (isis metric 1 on the tunnel interface) is actually supported. The default metric 10 is applied. You can also see that in the "show isis data detail" output.

Regards,