<?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 Re: ISP Redundancy and VPN site-to-site in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/ISP-Redundancy-and-VPN-site-to-site/m-p/207952#M39400</link>
    <description>&lt;P&gt;Keep in mind, its NOT supported to use same interoperable object in more than 1 vpn community. As a a matter of fact, if you do that, policy install will fail, 100%. The only way it would work is if you clone existing int. object, give it another name, but then there is no way to differ which community will take presedence and probably only 1 tunnel may show as up, you would not even see the other ones.&lt;/P&gt;
&lt;P&gt;Best,&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
    <pubDate>Wed, 06 Mar 2024 12:09:16 GMT</pubDate>
    <dc:creator>the_rock</dc:creator>
    <dc:date>2024-03-06T12:09:16Z</dc:date>
    <item>
      <title>ISP Redundancy and VPN site-to-site</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/ISP-Redundancy-and-VPN-site-to-site/m-p/207898#M39386</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I need your help. I have this scenarious:&lt;/P&gt;&lt;P&gt;Site1: Managment server with cluster( 2x gateways, and 2 ISP ( A.A.A.A + B.B.B.B)&amp;nbsp;&lt;/P&gt;&lt;P&gt;Site2: Managment server with cluster( 2x gateways, and 2 ISP ( C.C.C.C + D.D.D.D)&amp;nbsp;&lt;/P&gt;&lt;P&gt;My questions is: When i make site-to-site VPN with site 1 and 2, i need garanted redundancy of ISP. What is a best pratices for this scenarious?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 05 Mar 2024 20:19:35 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/ISP-Redundancy-and-VPN-site-to-site/m-p/207898#M39386</guid>
      <dc:creator>paulocosta</dc:creator>
      <dc:date>2024-03-05T20:19:35Z</dc:date>
    </item>
    <item>
      <title>Re: ISP Redundancy and VPN site-to-site</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/ISP-Redundancy-and-VPN-site-to-site/m-p/207901#M39387</link>
      <description>&lt;P&gt;Please &lt;A href="https://sc1.checkpoint.com/documents/R81.10/WebAdminGuides/EN/CP_R81.10_ClusterXL_AdminGuide/Topics-CXLG/ISP-Redundancy-and-VPN.htm" target="_self"&gt;read the documentation&lt;/A&gt;, I believe it covers what you need. If not, let me know.&lt;/P&gt;</description>
      <pubDate>Tue, 05 Mar 2024 22:14:29 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/ISP-Redundancy-and-VPN-site-to-site/m-p/207901#M39387</guid>
      <dc:creator>_Val_</dc:creator>
      <dc:date>2024-03-05T22:14:29Z</dc:date>
    </item>
    <item>
      <title>Re: ISP Redundancy and VPN site-to-site</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/ISP-Redundancy-and-VPN-site-to-site/m-p/207911#M39391</link>
      <description>&lt;P&gt;See...key here is that even with ISPR configured, other side needs to be aware of say site's 1 both links (same the other way around) and since its NOT supported to have same interoperable object, or in your case externally managed gateways (as its CP) in the same community, personally, I would approach TAC with an official answer as far as best approach.&lt;/P&gt;
&lt;P&gt;Maybe simple network diagram may also help us,&lt;/P&gt;
&lt;P&gt;Best,&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2024 00:12:58 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/ISP-Redundancy-and-VPN-site-to-site/m-p/207911#M39391</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2024-03-06T00:12:58Z</dc:date>
    </item>
    <item>
      <title>Re: ISP Redundancy and VPN site-to-site</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/ISP-Redundancy-and-VPN-site-to-site/m-p/207933#M39395</link>
      <description>&lt;P&gt;Hi _Val_&lt;/P&gt;&lt;P&gt;Thanks for your reply.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yes, already read this documentation. Maybe my first post not is a very complete.&amp;nbsp;&lt;/P&gt;&lt;P&gt;When i create a site-to-site vpn i need create interoperable device (one for a ISP) and put it all in VPN Communitie, because i have two managments servers&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2024 09:16:56 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/ISP-Redundancy-and-VPN-site-to-site/m-p/207933#M39395</guid>
      <dc:creator>paulocosta</dc:creator>
      <dc:date>2024-03-06T09:16:56Z</dc:date>
    </item>
    <item>
      <title>Re: ISP Redundancy and VPN site-to-site</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/ISP-Redundancy-and-VPN-site-to-site/m-p/207952#M39400</link>
      <description>&lt;P&gt;Keep in mind, its NOT supported to use same interoperable object in more than 1 vpn community. As a a matter of fact, if you do that, policy install will fail, 100%. The only way it would work is if you clone existing int. object, give it another name, but then there is no way to differ which community will take presedence and probably only 1 tunnel may show as up, you would not even see the other ones.&lt;/P&gt;
&lt;P&gt;Best,&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2024 12:09:16 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/ISP-Redundancy-and-VPN-site-to-site/m-p/207952#M39400</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2024-03-06T12:09:16Z</dc:date>
    </item>
    <item>
      <title>Re: ISP Redundancy and VPN site-to-site</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/ISP-Redundancy-and-VPN-site-to-site/m-p/207997#M39408</link>
      <description>&lt;P&gt;Why Interoperable? Do Externally Managed GWs. What's the issue, then?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2024 17:27:06 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/ISP-Redundancy-and-VPN-site-to-site/m-p/207997#M39408</guid>
      <dc:creator>_Val_</dc:creator>
      <dc:date>2024-03-06T17:27:06Z</dc:date>
    </item>
    <item>
      <title>Re: ISP Redundancy and VPN site-to-site</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/ISP-Redundancy-and-VPN-site-to-site/m-p/207999#M39409</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;This is scenarios:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ISP_Redundancy.png" style="width: 400px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/24761i9D1B8D8EAC146646/image-size/medium?v=v2&amp;amp;px=400" role="button" title="ISP_Redundancy.png" alt="ISP_Redundancy.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;I need to create a site-to-site VPN to connect sites 1 and 2. One requirement is: if ISP A.A.A.A has a problem, I need ISP B.B.B.B to maintain a VPN connection.&lt;/P&gt;&lt;P&gt;My question is: When I create a VPN community for connecting site 1 to site 2, as this site has a different management server, how can I tell the Sattelite Gateways that I have 2 possible ISP connections? I need to create 2 written interoperable devices right?&lt;/P&gt;&lt;P&gt;How do you suggest?&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2024 17:53:13 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/ISP-Redundancy-and-VPN-site-to-site/m-p/207999#M39409</guid>
      <dc:creator>paulocosta</dc:creator>
      <dc:date>2024-03-06T17:53:13Z</dc:date>
    </item>
  </channel>
</rss>

