IKEv2 renegotiation on acceptor gateway reboot

Reply
Highlighted
L0 Member

IKEv2 renegotiation on acceptor gateway reboot

Hi community,

 

I have a site-to-site IPSec connectivity with Palo Alto gateway (PA-VM 8.0.5 on kvm hypervisor - CentOS 7 host) on one end as initiator and Vyatta OS based gateway on the other end as acceptor.

 

When IKEv2 and IPSec (and BGP) are in established state, and the Vyatta OS reboots, it takes about 6 minutes for PA-VM to detect outage and renegotiate IKEv2.


The IKE Crypto has "Key Lifetime" set to 8 hours.

 

My question:

1. What configuration needs to be done (or can be done) in PA-VM for IKE to negotiate sooner ? (Is it a good idea to set Key Lifetime param in IKE Crypto to 3 minutes ?)

 

2. What is the industry best practice for setting up site-to-site VPNs in order to minimize outages due to peer firewall going down ?

 

Regards


Thanks in advance.

Highlighted
Cyber Elite

@rameshgi,

I imagine that you are not doing any tunnel monitoring? 

Highlighted
L0 Member

Hi @BPry,

 

I did use tunnel-monitoring with the following params, and associated it with the IPSec tunnel:

1. Action - Wait-Recover

2. Interval - 2 secs

3. Threshold - 2 secs

 

Regards

 

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!