
But we wanted it to work on the Checkpoint hardware and it just will not. I had to roll back to it Sunday and it's working normally right now. The tunnel settings are EXACTLY the same as they were between the same Palo Alto and the older Checkpoint running R80.10 and on that older combo the tunnel works fine. This happened after an upgrade of the checkpoint from an old CP open server running R80.10 to the new CP appliance cluster (R81). I'm having a problem with an ipsec tunnel between a Palo Alto running PANOS 9 (I think, it could be 10) that will not re-establish the phase 2 with a freshly upgraded Checkpoint 6200 cluster running R81.

It works only between Check Point Security Gateways. Tunnel_test (default) - The permanent tunnel is monitored by a tunnel test (as in earlier versions). There are different possibilities for permanent tunnel mode: After you configure the permanent tunnel, configure Permanent Tunnel mode Based on DPD. To configure DPD for a permanent tunnel, the permanent tunnel must be in the VPN community. All related behavior and configurations of permanent tunnels are supported.

This section (you need DPD value specially if its 3rd party device on the other side) Permanent Tunnel Mode Based on Dead Peer DetectionĭPD can monitor remote peers with the permanent tunnel feature.

You have to do below changes in guidbedit as well per below link: As the guys said, make sure permanent tunnel option inside vpn community is enabled.
