All i had to do was define the backup paths for each interface under the ISIS process. Note this is L2 ISIS only.
I removed it before putting this into production as my customer couldn't decide which paths they wanted as backup!
I did some convergence time measurements whilst the kit was still in the lab, so its not real world as the routers were all directly cabled together, but without LFA it took typically 50ms for ISIS to reconverge following a p2p cable disconnect, with LFA on this time reduced to less than 1ms!
The only show command output I recorded was a show route, a snippit of which is here:
i L2 10.250.250.96/30 [115/20000] via 10.250.250.2, 00:10:23, TenGigE0/0/0/0
[115/0] via 10.250.250.6, 00:10:23, TenGigE0/0/0/3
i L2 10.250.250.100/30 [115/0] via 10.250.250.2, 00:10:23, TenGigE0/0/0/0
[115/20000] via 10.250.250.6, 00:10:23, TenGigE0/0/0/3
You can see the backup paths are already in the route table, but with a higher metric.
Introduction: The "external-out enable" command is available for
configuration under the "router ospf process" in case of the IOS-XR
operating system. This command basically enables advertisement of
intra-area routes on the device as external routes in th...
IntroductionIn this article we'll discuss how to troubleshoot packet
loss in the asr9000 and specifically understanding the NP drop counters,
what they mean and what you can do to mitigate them. This document will
be an ongoing effort to improve troublesh...