05-24-2013 08:07 AM - edited 03-07-2019 01:32 PM
I notice when working on my PBRs that it will let you set multiple next-hop IPs. Are these for redundancy I assume? For example, if I have it setup like this:
set ip next-hop 4.2.2.1 4.2.2.2
will it try the 4.2.2.1 and if the interface that is connected to doesn't work it will try 4.2.2.2?
Solved! Go to Solution.
05-24-2013 08:17 AM
Hi Chris,
"If the interface associated with the first next hop specified with the set ip next-hop command is down, the optionally specified IP addresses are tried in turn"
From this document:
http://www.cisco.com/en/US/docs/ios/12_2/iproute/command/reference/1rfindp2.html#wp1020776
05-24-2013 08:17 AM
Hi Chris,
"If the interface associated with the first next hop specified with the set ip next-hop command is down, the optionally specified IP addresses are tried in turn"
From this document:
http://www.cisco.com/en/US/docs/ios/12_2/iproute/command/reference/1rfindp2.html#wp1020776
05-24-2013 10:10 AM
Thanks for the info! I might also think about using an SLA type configuration like in this document:
http://www.cisco.com/en/US/tech/tk364/technologies_configuration_example09186a0080211f5c.shtml
05-24-2013 04:46 PM
Hello chris,
FYI - for resiliency with PBR, if the next hop interfaces are unreachable the policy will still try to forward traffic based on the match statements and start arping for the next hop address.
Applying the set ip next-hp verify-availability command into the polciy will make the router do a cdp lookup for the next-hop address before policy routing and if its not found the router will route normal instead
.
res
Paul
Please don't forget to rate any posts that have been helpful.
Thanks.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide