Skip to main content
MotorOil
MotorOil
New Member
December 5, 2014
Question

Progress IPsec Phase 2 Failure

  • December 5, 2014
  • 4 replies
  • 53878 views

We are running a 800C and are getting a IPsec Phase 2 error every hour (Key Lifetime set to 3600 on both ends).  Build v5.2.1,build618

 

Our connection is in-house to Amazon's data center (VPC connection for those familiar).  We have been able to duplicate the error on a test connection and have tried several settings to make it go away.  Turning off DPD, extending key lifetime (not adjustable on Amazon's end). 

    4 replies

    emnoc
    emnoc
    New Member
    December 5, 2014

    That's probably okay, is the VPN staying up? or during the rekey are you having to do anything manual?

    MotorOil
    MotorOilAuthor
    New Member
    December 5, 2014

    drops for 15 to 30 seconds and reconnects on its own.

    MotorOil
    MotorOilAuthor
    New Member
    December 5, 2014

    Phase 1 is fine, only the phase 2 is failing every hour.  Causes a disconnect of our key systems and staff needing to reconnect every hour....

    emnoc
    emnoc
    New Member
    December 5, 2014

    That's not good. So is this a phase2 re-key or a phase1 re-key? ( monitor you phase1  SA SPI at the 1 hr mark )

     

    emnoc
    emnoc
    New Member
    December 7, 2014

    So how do you have the phase2 set in the cfg and mainly for the below items?

     

     

    set auto-negotiate disable set keepalive enable set keylife-type seconds

    set keylifeseconds 3600

     

     

     

    This sounds like a phase2-keylife not matched or being honored.

     

     

    Alex_K
    Alex_K
    New Member
    May 2, 2016

    Hi!

     

    Sorry for resurrecting this old thread but it looks like I'm having similar symptoms between Fortigate 100D and Amazon VPC.

     

    In Log & Report->VPN Events every now and then I see negotiate failure messages "progress IPsec phase 2", Direction=inbound, Role=responder, RemotePort=500. It looks like the tunnel is always up and I have no problems pinging hosts from both ends, but since this new setup is not rolled out to users yet, I can't really say if it will be stable.

    What I also noticed was that I could RDP into servers in Amazon without any issues. However, when I try to RDP from Amazon back to premises, it works, but every 2-3-4th time, meaning that in first several attempts I get a standard RDP connection error. During RDP failures, I can ping hosts fine.

     

     

    linfante
    linfante
    New Member
    September 20, 2017

    Bump.

     

    Was there ever a solution to this? We are having the exact same issue. Pretty sure it's key lifetime as the VPN error messages happen every hour at the same time. FG800 and FG100 IPSec VPN to AWS as well.

    Terms & ConditionsAccessibility statement