Thread Info
  • State Suggested Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 28 subscribers
  • Views 6260 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Email alerts after MR3 update

ZaneDonaldson

All,

 

after updating to V17 MR3, I am getting alert emails from the appliance every hour alerting me that my IPsec vpn tunnel is up.  I never get a down notice, just up notices.  Over 80 emails over the weekend.

 

any insight on how to fix this?  Like any network monitoring tool, its worthless if it continue to give false results.



This thread was automatically locked due to age.
Parents
  • 0

    Hi  

    Are you experiencing any issues with your IPsec tunnels? These notifications are configured from System > Administration > Notification Settings.

    From the help page:
    An email is sent only when Host-to-Host and Site-to-Site tunnel connections are disconnected for one of the following reasons:
    ◦ A peer is found dead (DPD)
    ◦ Failed to re-establish connection after Dead Peer Detection (DPD)
    ◦ IPsec Security Association (SA) is expired and is required to be re-established.
    ◦ IPsec tunnel comes up without administrator intervention after losing the connectivity.
    ◦ An email is sent for each subnet pair in case of Site-to-Site connections with multiple local/remote networks.
    ◦ Description of IPsec tunnel connection is included in the email only if the administrator has provided the information.

    Regards,

    FloSupport | Community Support Engineer

Reply
  • 0

    Hi  

    Are you experiencing any issues with your IPsec tunnels? These notifications are configured from System > Administration > Notification Settings.

    From the help page:
    An email is sent only when Host-to-Host and Site-to-Site tunnel connections are disconnected for one of the following reasons:
    ◦ A peer is found dead (DPD)
    ◦ Failed to re-establish connection after Dead Peer Detection (DPD)
    ◦ IPsec Security Association (SA) is expired and is required to be re-established.
    ◦ IPsec tunnel comes up without administrator intervention after losing the connectivity.
    ◦ An email is sent for each subnet pair in case of Site-to-Site connections with multiple local/remote networks.
    ◦ Description of IPsec tunnel connection is included in the email only if the administrator has provided the information.

    Regards,

    FloSupport | Community Support Engineer

Children
  • 0 in reply to FloSupport

    FloSupport said:

    Hi  

    Are you experiencing any issues with your IPsec tunnels? These notifications are configured from System > Administration > Notification Settings.

    From the help page:
    An email is sent only when Host-to-Host and Site-to-Site tunnel connections are disconnected for one of the following reasons:
    ◦ A peer is found dead (DPD)
    ◦ Failed to re-establish connection after Dead Peer Detection (DPD)
    ◦ IPsec Security Association (SA) is expired and is required to be re-established.
    ◦ IPsec tunnel comes up without administrator intervention after losing the connectivity.
    ◦ An email is sent for each subnet pair in case of Site-to-Site connections with multiple local/remote networks.
    ◦ Description of IPsec tunnel connection is included in the email only if the administrator has provided the information.

    Regards,

    FloSupport | Community Support Engineer

     

     

    The log viewer is not showing any tunnel renegotiation.

     

    Also, as I noted above, the email notifications I'm receiving are only UP messages.  I'm not getting any DOWN notifications at all.

     

    I am also running an independent network monitoring software tool, it has not alerted that the various servers/printers/etc at the remote site have gone away, which would be the case if the tunnel was actually going down.

  • 0 in reply to ZaneDonaldson

    Hi  

    After further investigation, I have found a known bug ID NC-26354 that describes the issue that you are experiencing. This should be included in the next MR-5 update. Apologies for the inconvenience caused by this.

    Regards,

    FloSupport | Community Support Engineer