MPLS FRR

Static, RIP, EIGRP, OSPF, BGP, IBGP, IS-IS and any other routing.
Guest

Re:MPLS FRR

Post by Guest » Thu Mar 03, 2005 5:16 pm


Barada,It will happen after the re-optimize timer times out, which one hour (3600 seconds) by default.Regards

Guest

Re:MPLS FRR

Post by Guest » Thu Mar 03, 2005 6:45 pm


could you not also solve your problem by usingmpls traffic-eng reoptimize events link-up??

Guest

Re:MPLS FRR

Post by Guest » Thu Mar 03, 2005 8:07 pm


Matthew,This would certainly work. It boils down to how quickly you want your path to be reoptimized vs. network stability.Regards

Guest

Re:MPLS FRR

Post by Guest » Thu Mar 03, 2005 8:53 pm


Hi Mike,   Instead of dynamic path option, configure an explicit path with "192.168.3.1" as strict hop and try the scenario.   In this case, when pos interface on primary path goes down the traffic will be rerouted via backup tunnel and the primary path will be retried for every 30 seconds. When the interface is back up, primary path signaling will succeed and tunnel will no longer use the backup path.When tunnel uses the backup tunnel, "show mpls traffic-eng fast database" will display it's status as "active".With dynamic path option, the tunnel will calculate a path which will be same as the backup tunnel path and it'll look like it's using the backup tunnel. To use the best path you've to trigger reoptimization (manual/periodic/event-linkUp).Thanks,Vijay

Post Reply