Hi there,
I have the exact config as per solution but upon bring down the R9 to R1 link, it's seems to be that the mpls te link produce this kind of error:
Rack1R1#
00:37:07: %MPLS_TE-3-CONSISTENCY: Path lookup returned path that didn't pass verification: Tunnel14
-Traceback= 6076D55C 61333B20 61333E50 61335FA8 6133AAD0 61346BC4 6134708C 61347370 6133F428 6133F764
Rack1R1#
00:37:09: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.9.9 on ATM4/0.19 from FULL to DOWN, Neighbor Down: Dead timer expired
Rack1R1#
00:37:18: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.9.9 on ATM4/0.19 from LOADING to FULL, Loading Done
Rack1R1#sh run
00:37:20: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel14, changed state to up
Once, I bring up the R9 to R1 link, tunnel14 seems to be up.
Here is my configuration on tunel:
Rack1R1#sh run int tun14
Building configuration...
Current configuration : 372 bytes
!
interface Tunnel14
ip unnumbered Loopback0
tunnel destination 192.168.4.4
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng autoroute announce
tunnel mpls traffic-eng priority 7 7
tunnel mpls traffic-eng bandwidth 1000
tunnel mpls traffic-eng path-option 1 explicit name R1-R9-R2-R3-R4
tunnel mpls traffic-eng path-option 2 dynamic
no clns route-cache
end
Since the question dictates if R9 is down, it should be routed as necessary .. I was thinking the route should take path-option 2 dynamically, but it seems to travel on normal OSPF route.
Rack1R1#traceroute 192.168.4.4
Type escape sequence to abort.
Tracing the route to 192.168.4.4
1 129.1.123.3 8 msec 12 msec 20 msec
2 129.1.34.4 32 msec * 28 msec
Any ideas ?
Thank you.