Static, RIP, EIGRP, OSPF, BGP, IBGP, IS-IS and any other routing.
!interface Tunnel1211 ip unnumbered Loopback0 load-interval 30 tunnel destination 18.104.22.168 tunnel mode mpls traffic-eng tunnel mpls traffic-eng autoroute announce tunnel mpls traffic-eng priority 1 1 tunnel mpls traffic-eng bandwidth 1000 tunnel mpls traffic-eng path-option 1 explicit name hj tunnel mpls traffic-eng path-option 2 dynamic tunnel mpls traffic-eng fast-reroute!mpls traffic-eng reoptimize timers frequency 5mpls traffic-eng reoptimize timers delay installation 5mpls traffic-eng reoptimize timers delay cleanup 5mpls traffic-eng reoptimize events link-upOur mpls configuration is like above log.We configured the path option1, path option2 in the tunnel interface.when the explicit path failed, the path option2 comes up.Our plan is that when the path option 1 is failed, and the core running the FRRWe do not want to switch over th path option2 dynamicallyHow can I do that? Any thought?and next...there is mpls traffic-eng reoptimize in our configuration. If I remove that, Can I make it like above?
I think the best way is to have 2 TE GRE Tunnels configured. Both with explicit paths with one the direct path and the other one having the backup path. See below:interface Tunnel100 description DIRECT LSP ip unnumbered Loopback0 tunnel destination 22.214.171.124 tunnel mode mpls traffic-eng tunnel mpls traffic-eng autoroute announce tunnel mpls traffic-eng path-option 1 explicit name TE_PRIMARY tunnel mpls traffic-eng priority 1 1 tunnel mpls traffic-eng bandwidth 1000 tunnel mpls traffic-eng fast-rerouteinterface Tunnel200 description BACKUP LSP ip unnumbered Loopback0 tunnel destination 126.96.36.199 tunnel mode mpls traffic-eng tunnel mpls traffic-eng autoroute announce tunnel mpls traffic-eng path-option 1 explicit name TE_SECONDARY tunnel mpls traffic-eng priority 1 1 tunnel mpls traffic-eng bandwidth 1000interface X mpls traffic-eng backup-path Tunnel200-----Also, depending on your IGP (IS-IS is faster for FRR convergence) you could tweak the spf timers and if you are running BFD then tie RSVP to BFD for even better convergence (but this depends on hardware platforms used).
Thank a lot..I understood your comment.but I have a question within your config.the interface X...When We are config explcit path, we point hop-by-hop. I think that your interface x is Physical interface. Right?if so. if the interface x didn't goes to down, the backup-path tunnel 200 didn't activate..Right? the reason is the physical link still up.if I can configure to make backup tunnel in the the interface tunnel 100, It's make sense. but real didn't do that.
Yeah interface X is the physical interface where your LSP begins. Remember, in the routing table you'll see the tunnels and not the physical interface. I have implemented this for a customer and it works pretty really well (sub 2ms failover).Another note, if you remove "autoroute announce" from the backup tunnel it will work only as a backup, if you have "autoroute announce" there it will load-share between the 2 tunnels.I recommend doing this in a lab environment so you can break the direct link and see the routing change. An MPLS traceroute or a normal IP traceroute will show you which LSP its taking (ie, which Tunnel is in use).HTH.- Joe.
Thans a lot! Be always happy :)I would like to know when the below,The Tunnel 100 is configured with Explicit Path. and It's working well in normal . but Tunnel 100 is down due to its explicit path failed. but Tunnel 200 didn't working due to tunnel 100 indirect link failed.AS I know. the physcal link still comes up. and the indirect explicit failed . so the traffic can't use the tunnel 200just thing I would like to know that If I want to activate the tunnel 200, the physical link must be down ? Right?