Q1 ) Tunnel monitor is Palo Alto proprietary and as far as I know it should be use between Palo Alto peers to work optimally, am I right? Yes , tunnel monitor is Palo Alto Networks proprietary protocol. Please see this link for more details. https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClFaCAK#:~:text= Q2 ) Considering this if having a VPN between Palo Alto device and another vendor device, would path monitoring for a static route work similar than tunnel monitor? In essence , the goal of path monitoring and tunnel monitoring are the same , but there are some differences. In Path Monitoring , If “all” or “any” of the monitored destinations for the static route are unreachable by ICMP, the firewall removes the static route from the RIB and FIB and adds the dynamic or static route that has the next lowest metric going to the same destination to the FIB. There are two possible actions that can be taken if a monitored destination fails with tunnel monitoring. 1) Wait recover. Wait for the tunnel to recover; do not take additional action. 2) Failover.Traffic will fail over to a backup path, if one is available. The firewall uses routing table lookup to determine routing for the duration of this session. Q) My idea is that sourcing the path-monitoring pings from the tunnel IP to remote peer´s IP could keep the tunnel up like tunnel monitoring does. (Not having the firewall in passive mode of course) The function of Path monitoring and Tunnel monitoring is not to keep the “tunnel up” . It is used to just monitor if a destination is reachable or not. If you still have any questions, please open a support ticket and one of us will help you. Kavi
... View more