Hi Jon, First off, I apologize that the 'qualified-next-hop' parameter is missing from the Command Reference, I'll notify our tech writer so she can add it in ASAP.
From my testing and from speaking with XORP, the 'qualified-next-hop' is triggered by the <NO CARRIER> flag on the interface that is associated with the static route's next-hop value. So, if your next-hop is reachable via interface eth0 and eth0 goes down: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> Then the qualified-next-hop would be automatically installed in the routing table as long is it's reachable (it's associated interface is up). As soon as the primary next-hop's associated interface is restored (NO-CARRIER flag disappears) the primary next-hop is once again installed in the routing table and the qualified-next-hop becomes the back up: eth0: <BROADCAST,MULTICAST,UP,10000> Thank you, Robyn Jon wrote: > Hi, > > In the last available command reference on the Wiki, there is no > mentioning of "protocols static routes qualified-next-hop". > > I believe this has been available for quite a while now? > > I also have a question about the use of qualified-next-hop: > > According to the XORP user manual, it states: > <Quote> > Qualified-next-hop: this speciļ¬es an alternative nexthop router for the > route, but with a > different metric. Typically it is used to install a backup static route > that will be used in case the > original next hop becomes unreachable. > </Quote> > > What is the definition of "becomes unreachable"? Does this imply there is > no route to it anymore, or does it take into account "not-reachable" > messages? > > Thanks, > > Jon > _______________________________________________ > Vyatta-users mailing list > [email protected] > http://mailman.vyatta.com/mailman/listinfo/vyatta-users > _______________________________________________ Vyatta-users mailing list [email protected] http://mailman.vyatta.com/mailman/listinfo/vyatta-users
