<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic IPsec Redundancy  to the Same Endpoint in Cloud Firewall</title>
    <link>https://community.checkpoint.com/t5/Cloud-Firewall/IPsec-Redundancy-to-the-Same-Endpoint/m-p/183944#M91</link>
    <description>&lt;P&gt;The following shows what we need to establish: The Azure VPN gateway is on the UK South domain.&lt;/P&gt;&lt;P&gt;What has been identified is that traffic loss is seen when the specific link to Azure domain is in maintenance, traffic is lost fro approx 20 mins.&lt;/P&gt;&lt;P&gt;What the requirement is that the secon IPSec is established as a standby.&lt;/P&gt;&lt;P&gt;It is assumed that multiple access links for the Azure are available and that may be set up as the standby (cold)&lt;/P&gt;&lt;P&gt;The two CP gateways are a HA pair.&lt;/P&gt;&lt;P&gt;Currently the BGP is showing only as being available and active from the Active :&lt;/P&gt;&lt;P&gt;169.254.22.69&amp;nbsp;&amp;nbsp;&amp;nbsp; 65xxx&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 17&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 16&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Established&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 21&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 4d7h&lt;/P&gt;&lt;P&gt;We know that in HA redundancy that the BGP re-forms on the HA partner when there is a failure.&lt;/P&gt;&lt;P&gt;When we need to do is enable the platform to have two possible IPsec to the remote Azure VPN gateway , having the same Target remote AS number.&lt;/P&gt;&lt;P&gt;So in essence a Primary&amp;nbsp; and a secondary : now not having experimented and not having any lab facility the behaviour and the configuration is unknown, this is where I post this article/ info request.&lt;/P&gt;&lt;P&gt;Also in the event of the switch between Active Ip sec and the Secondary Ipsec ( when the AZ provider does the maintenance ) one would assume that the traffic will be interrupted due to the re-formation of the BGP on the secondary IPsec.&lt;/P&gt;&lt;P&gt;There is no requirement for any load sharing : One Ipsec is up or the other.&lt;/P&gt;&lt;P&gt;Expressing here the design requirements that have been presented for any valid input or design ideas or even sample configurations that may have been developed or deployed in the past.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="jed1_0-1686730798275.png" style="width: 400px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/21415iDC1B0C3D55B1CFB8/image-size/medium?v=v2&amp;amp;px=400" role="button" title="jed1_0-1686730798275.png" alt="jed1_0-1686730798275.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 14 Jun 2023 08:21:14 GMT</pubDate>
    <dc:creator>jed1</dc:creator>
    <dc:date>2023-06-14T08:21:14Z</dc:date>
    <item>
      <title>IPsec Redundancy  to the Same Endpoint</title>
      <link>https://community.checkpoint.com/t5/Cloud-Firewall/IPsec-Redundancy-to-the-Same-Endpoint/m-p/183944#M91</link>
      <description>&lt;P&gt;The following shows what we need to establish: The Azure VPN gateway is on the UK South domain.&lt;/P&gt;&lt;P&gt;What has been identified is that traffic loss is seen when the specific link to Azure domain is in maintenance, traffic is lost fro approx 20 mins.&lt;/P&gt;&lt;P&gt;What the requirement is that the secon IPSec is established as a standby.&lt;/P&gt;&lt;P&gt;It is assumed that multiple access links for the Azure are available and that may be set up as the standby (cold)&lt;/P&gt;&lt;P&gt;The two CP gateways are a HA pair.&lt;/P&gt;&lt;P&gt;Currently the BGP is showing only as being available and active from the Active :&lt;/P&gt;&lt;P&gt;169.254.22.69&amp;nbsp;&amp;nbsp;&amp;nbsp; 65xxx&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 17&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 16&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Established&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 21&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 4d7h&lt;/P&gt;&lt;P&gt;We know that in HA redundancy that the BGP re-forms on the HA partner when there is a failure.&lt;/P&gt;&lt;P&gt;When we need to do is enable the platform to have two possible IPsec to the remote Azure VPN gateway , having the same Target remote AS number.&lt;/P&gt;&lt;P&gt;So in essence a Primary&amp;nbsp; and a secondary : now not having experimented and not having any lab facility the behaviour and the configuration is unknown, this is where I post this article/ info request.&lt;/P&gt;&lt;P&gt;Also in the event of the switch between Active Ip sec and the Secondary Ipsec ( when the AZ provider does the maintenance ) one would assume that the traffic will be interrupted due to the re-formation of the BGP on the secondary IPsec.&lt;/P&gt;&lt;P&gt;There is no requirement for any load sharing : One Ipsec is up or the other.&lt;/P&gt;&lt;P&gt;Expressing here the design requirements that have been presented for any valid input or design ideas or even sample configurations that may have been developed or deployed in the past.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="jed1_0-1686730798275.png" style="width: 400px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/21415iDC1B0C3D55B1CFB8/image-size/medium?v=v2&amp;amp;px=400" role="button" title="jed1_0-1686730798275.png" alt="jed1_0-1686730798275.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 14 Jun 2023 08:21:14 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Cloud-Firewall/IPsec-Redundancy-to-the-Same-Endpoint/m-p/183944#M91</guid>
      <dc:creator>jed1</dc:creator>
      <dc:date>2023-06-14T08:21:14Z</dc:date>
    </item>
    <item>
      <title>Re: IPsec Redundancy  to the Same Endpoint</title>
      <link>https://community.checkpoint.com/t5/Cloud-Firewall/IPsec-Redundancy-to-the-Same-Endpoint/m-p/184206#M92</link>
      <description>&lt;P&gt;Where are you intending to initiate the second tunnel from?&lt;BR /&gt;The same active device or the other (standby) device?&lt;/P&gt;
&lt;P&gt;Note in an HA configuration, only one of the gateways should initiate an IPsec tunnel.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 16 Jun 2023 19:13:51 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Cloud-Firewall/IPsec-Redundancy-to-the-Same-Endpoint/m-p/184206#M92</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2023-06-16T19:13:51Z</dc:date>
    </item>
  </channel>
</rss>

