We have a PA with two VPNs configured. VPN-Main is the active one and if this vpn falls, the traffic must go through the other VPN-backup. The fact is that when the active VPN falls, the route that has the Palo Alto continues going through the previous VPN, it does not refresh the route and adds it through the new tunnel.
This configuration worked when this deployment was done but suddenly stop working.
We have configured a tunnel monitor with destination IP and profile fail-over.
In VPN Main (active):
In VPN (backup):
And this is the route table:
tunnel.29 is the main (active). The metric is 2.
tunnel.27 is the backup. Metric is 5.
Why PA is not deleting the "active" route if the monitor ip is down through the vpn down.
Its because they are static routes. For this type of config I would recommend one of the following.
For VPN tunnel A
Use Policy based forwarding with the monitoring and "Disable this rule if nexthop/monitor ip is unreachable" checked.
Then use a static route for tunnel B
The PAN will enforce PBF policies prior to the routing table so when the PBF disables its self the routing table takes affect.
The second option is to use PBF for both tunnels and tunnel B lower on the list. The firewall reads these from top down so it will always prefer tunnel A unless it goes down then switch to tunnel B.
Hope that makes sense.
Yes, but its not necesary PBF. It should be work only with tunnel monitoring
Whats the problem with static routes??? static route should dissapear when monitor ip is down.
The static route will be removed from the FIB not the RIB - if you go to the VR and click "More runtime stats" -> "Forwarding Table" it shouldn't be there.
In the static route, was the Route monitoring configured? Sorry if I missed it somewhere in the thread?
I may be completely wrong here, but the way that I thought it worked was that if you had tunnel monitoring configured with action of 'fail-over' the actual failover mechanism works by removing any static routes associated with that tunnel interface from the FIB - effectively making it so you can start using another IPSec tunnel via routes in your RIB.
Reading the documentation - when failover option is selected, tunnel interface is disabled so all routes with that tunnel interface are indeed removed from the FIB. So yes @jesuscano this setup is valid and the traffic would start using the backup tunnel so long as your primary tunnel has tunnel monitoring with failover option set.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!
The Live Community thanks you for your participation!