Skip to main content
NetApp Knowledge Base

What IKE and IPsec lifetimes are recommended with ONTAP

Views:
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

  • ONTAP 9.8 and later

Answer

  • Use an IPsec Security Association (SA) lifetime of 8 hours.
  • Use an Internet Key Exchange (IKE) SA lifetime of 24 hours.
  • In large environments with many IPsec Security Associations (SAs), short rekey times add load to the ONTAP process responsible for IPsec administrative work. This can:
    • Slow down IKE operations
    • Delay connection processing on failover
  • The specific configuration to set SA lifetimes depends on the client software in use.
  • After adjusting the lifetime values, restart the IKE daemon or reconnect the IPsec tunnel to apply the change.

Additional Information

  • If rekeying based on bytes, either select 0 to allow ONTAP to rekey based on its timers or select a sufficient amount of bytes based on the workload to avoid frequent rekeying.
  • Configuration examples
  • strongSwan (ipsec.conf)
    • In the relevant `conn` block, set:
      ikelifetime=24h
      lifetime=8h
  • strongSwan (swanctl.conf)
    • Set rekey_time on the IKE connection and on the child SA:
      connections {
          <name> {
              rekey_time = 24h
              children {
                  <name> {
                      rekey_time = 8h
                  }
              }
          }
      }
  • Libreswan
    • In the relevant connection definition in `/etc/ipsec.conf` or a file under `/etc/ipsec.d/`:
      ikelifetime=24h
      lifetime=8h
NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.