<?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: Cluster Members IP Address in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Cluster-Members-IP-Address/m-p/151110#M24604</link>
    <description>&lt;P&gt;How else would you connect to a specific gateway member in the cluster for troubleshooting and the like?&lt;BR /&gt;It’s also needed for pushing policy, among other things.&lt;/P&gt;</description>
    <pubDate>Thu, 16 Jun 2022 23:59:21 GMT</pubDate>
    <dc:creator>PhoneBoy</dc:creator>
    <dc:date>2022-06-16T23:59:21Z</dc:date>
    <item>
      <title>Cluster Members IP Address</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Cluster-Members-IP-Address/m-p/150749#M24502</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Why does CP clustering need to have IP address for member 1 and member 2? What's the use of it? Comparing with PA firewall they only need 1 which is VIP.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 14 Jun 2022 06:33:15 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Cluster-Members-IP-Address/m-p/150749#M24502</guid>
      <dc:creator>ela-in-sg-2017</dc:creator>
      <dc:date>2022-06-14T06:33:15Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Members IP Address</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Cluster-Members-IP-Address/m-p/150751#M24503</link>
      <description>&lt;P&gt;You can use private non-routable IPs for members and a routable VIP.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 14 Jun 2022 06:47:38 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Cluster-Members-IP-Address/m-p/150751#M24503</guid>
      <dc:creator>_Val_</dc:creator>
      <dc:date>2022-06-14T06:47:38Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Members IP Address</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Cluster-Members-IP-Address/m-p/151110#M24604</link>
      <description>&lt;P&gt;How else would you connect to a specific gateway member in the cluster for troubleshooting and the like?&lt;BR /&gt;It’s also needed for pushing policy, among other things.&lt;/P&gt;</description>
      <pubDate>Thu, 16 Jun 2022 23:59:21 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Cluster-Members-IP-Address/m-p/151110#M24604</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2022-06-16T23:59:21Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Members IP Address</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Cluster-Members-IP-Address/m-p/151142#M24627</link>
      <description>&lt;P&gt;It lets the members talk to each other on all of their interfaces. By default, they run a heartbeat protocol on the highest and lowest subinterfaces of every physical interface, as well as on all physical interfaces which have IP addresses. This allows the clustering mechanism to spot failures in complicated network topologies and use the member which has the best connectivity.&lt;/P&gt;</description>
      <pubDate>Fri, 17 Jun 2022 14:05:46 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Cluster-Members-IP-Address/m-p/151142#M24627</guid>
      <dc:creator>Bob_Zimmerman</dc:creator>
      <dc:date>2022-06-17T14:05:46Z</dc:date>
    </item>
  </channel>
</rss>

