<?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-Interfaces down in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/Cluster-Interfaces-down/m-p/12244#M1946</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you see on fw B no CCP packet from fw A. The red filed shows the gateway ID from fw gateway A. If you not see this packet on gateway B, the switch drop the packet.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;23:14:06.615764 00:00:00:00:11:&lt;STRONG style="color: #ff0000;"&gt;00&lt;/STRONG&gt; &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 03 Apr 2018 18:49:56 GMT</pubDate>
    <dc:creator>HeikoAnkenbrand</dc:creator>
    <dc:date>2018-04-03T18:49:56Z</dc:date>
    <item>
      <title>Cluster-Interfaces down</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Cluster-Interfaces-down/m-p/12235#M1937</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Experts&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;We've configured cluster (HA) and we see 2 interfaces are down in Active and 4 interfaces are&amp;nbsp; Down in standby firewall. Is this due to cabling problem in the switch.&amp;nbsp; Please assist.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Active Device:&lt;/P&gt;&lt;P&gt;****************&lt;/P&gt;&lt;P&gt;[Expert@FW]# cphaprob stat&lt;/P&gt;&lt;P&gt;Cluster Mode: High Availability (Primary Up) with IGMP Membership&lt;/P&gt;&lt;P&gt;Number Unique Address Assigned Load State&lt;/P&gt;&lt;P&gt;1 (local) 192.168.252.253 100% Active Attention&lt;BR /&gt;2 192.168.252.254 0% Down&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;[Expert@FW]# cphaprob -a if&lt;/P&gt;&lt;P&gt;Required interfaces: 8&lt;BR /&gt;Required secured interfaces: 1&lt;/P&gt;&lt;P&gt;Mgmt UP non sync(non secured), multicast&lt;BR /&gt;Sync UP sync(secured), multicast&lt;BR /&gt;Lan1 UP non sync(non secured), multicast&lt;BR /&gt;&lt;STRONG&gt;Lan2 UP non sync(non secured), multicast&lt;/STRONG&gt;&lt;BR /&gt;Lan3 Inbound: DOWN (16151.2 secs) Outbound: DOWN (16151.5 secs) non sync(non secured), multicast ----&amp;gt;&amp;gt;&amp;gt;&lt;BR /&gt;&lt;STRONG&gt;Lan4 Inbound: UP Outbound: DOWN (&lt;/STRONG&gt;16151.5 secs) non sync(non secured), multicast&amp;nbsp;&lt;BR /&gt;Lan5 Inbound: DOWN (16151.2 secs) Outbound: DOWN (16151.5 secs) non sync(non secured), multicast&amp;nbsp; ---&amp;gt;&amp;gt;&amp;gt;&amp;gt;&lt;BR /&gt;Lan6 UP non sync(non secured), multicast&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Standby Device:&lt;/P&gt;&lt;P&gt;******************&lt;/P&gt;&lt;P&gt;[Expert@FW]# cphaprob stat&lt;/P&gt;&lt;P&gt;Cluster Mode: High Availability (Primary Up) with IGMP Membership&lt;/P&gt;&lt;P&gt;Number Unique Address Assigned Load State&lt;/P&gt;&lt;P&gt;1 192.168.252.253 100% Active Attention&lt;BR /&gt;2 (local) 192.168.252.254 0% Down&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;[Expert@FW]# cphaprob -a if&lt;/P&gt;&lt;P&gt;Required interfaces: 8&lt;BR /&gt;Required secured interfaces: 1&lt;/P&gt;&lt;P&gt;Mgmt UP non sync(non secured), multicast&lt;BR /&gt;Sync UP sync(secured), multicast&lt;BR /&gt;Lan1 UP non sync(non secured), multicast&lt;BR /&gt;&lt;STRONG&gt;Lan2 Inbound: DOWN (16222.1 secs) Outbound: DOWN (16222.3 secs) non sync(non secured), multicast&lt;/STRONG&gt;&amp;nbsp;&amp;nbsp;&lt;BR /&gt;Lan3 Inbound: DOWN (16222.1 secs) Outbound: DOWN (16222.3 secs) non sync(non secured), multicast&amp;nbsp; -------&amp;gt;&amp;gt;&amp;gt;&amp;gt;&lt;BR /&gt;&lt;STRONG&gt;Lan4 Inbound: DOWN (16222.1 secs) Outbound: DOWN&lt;/STRONG&gt; (16222.3 secs) non sync(non secured), multicast&amp;nbsp;&lt;BR /&gt;Lan5 Inbound: DOWN (16222.1 secs) Outbound: DOWN (16222.3 secs) non sync(non secured), multicast&amp;nbsp; &amp;nbsp;-------&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&lt;BR /&gt;Lan6 UP non sync(non secured), multicast&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Apr 2018 20:49:24 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Cluster-Interfaces-down/m-p/12235#M1937</guid>
      <dc:creator>SriNarasimha005</dc:creator>
      <dc:date>2018-04-02T20:49:24Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster-Interfaces down</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Cluster-Interfaces-down/m-p/12236#M1938</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- check multicast droping on switch&lt;/P&gt;&lt;P&gt;- check interface errors „netstat -in“&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;gt; show for rx-errors (drop,overload,....)&lt;/P&gt;&lt;P&gt;- as next step set ccp to broadcast&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Apr 2018 21:20:00 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Cluster-Interfaces-down/m-p/12236#M1938</guid>
      <dc:creator>Julian_Weiss</dc:creator>
      <dc:date>2018-04-02T21:20:00Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster-Interfaces down</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Cluster-Interfaces-down/m-p/12237#M1939</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A class="link-titled" href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk115142" title="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk115142"&gt;Switch drops Check Point CCP packets when CCP is working in multicast mode&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk65560" title="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk65560"&gt;The cphaprob -a if command shows Inbound: UP, Outbound: DOWN&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk114804" title="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk114804"&gt;Critical Device "Interface Active Check" on ClusterXL Member reports its state as "problem"&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk62570" title="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk62570"&gt;How to troubleshoot failovers in ClusterXL - Advanced Guide&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk106660" title="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk106660"&gt;ClusterXL member is down due to Monitor Mode being enabled on a cluster interface&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Apr 2018 21:41:26 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Cluster-Interfaces-down/m-p/12237#M1939</guid>
      <dc:creator>AlekseiShelepov</dc:creator>
      <dc:date>2018-04-02T21:41:26Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster-Interfaces down</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Cluster-Interfaces-down/m-p/12238#M1940</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think it's a CCP problem.&lt;/P&gt;&lt;P&gt;Use the following command to check the CCP packet:&lt;/P&gt;&lt;P&gt;# tcpdump -i LanX -nnn -vvv -e port 8116&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Change LanX to your ethernet interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now, you can see all 100 ms a packet from GW A to GW B&amp;nbsp;and the other way around.&amp;nbsp;If the packets are not visible, it is a multicast problem on the switch.&amp;nbsp;In that case, test it with CCP broadcast. To do this, execute the following command on both gateways.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;# cphaconf set_ccp broadcast&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Apr 2018 21:49:35 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Cluster-Interfaces-down/m-p/12238#M1940</guid>
      <dc:creator>HeikoAnkenbrand</dc:creator>
      <dc:date>2018-04-02T21:49:35Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster-Interfaces down</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Cluster-Interfaces-down/m-p/12239#M1941</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Srinivasan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think heiko described the right way. But I have another comment. You can also turn off multicast monitoring / security on the switch.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Julian&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Apr 2018 22:15:47 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Cluster-Interfaces-down/m-p/12239#M1941</guid>
      <dc:creator>Julian_Weiss</dc:creator>
      <dc:date>2018-04-02T22:15:47Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster-Interfaces down</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Cluster-Interfaces-down/m-p/12240#M1942</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Heiko&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;Thanks for the reply.&amp;nbsp; When&amp;nbsp;&amp;nbsp;I applied this on the&amp;nbsp;Sync and Lan4 interfaces , I see below logs. And Cluster-ID seems same on both firewalls.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Active&lt;/P&gt;&lt;P&gt;*******&lt;/P&gt;&lt;P&gt;[Expert@FW]# tcpdump -i Sync -nnn -vvv -e port 8116&lt;BR /&gt;tcpdump: listening on Sync, link-type EN10MB (Ethernet), capture size 96 bytes&lt;BR /&gt;23:13:36.515776 00:00:00:00:11:00 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:13:36.519628 00:00:00:00:11:00 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 76: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 62) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 34&lt;BR /&gt;23:13:36.519665 00:00:00:00:11:00 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 92: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 78) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 50&lt;BR /&gt;23:13:36.519673 00:00:00:00:11:00 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:13:36.553935 00:00:00:00:11:01 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:13:36.574478 00:00:00:00:11:00 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 138: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 124) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: UDP, length 96&lt;BR /&gt;23:13:36.595023 00:00:00:00:11:01 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:13:36.600765 00:00:00:00:11:01 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:13:36.615789 00:00:00:00:11:00 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:13:36.619641 00:00:00:00:11:00 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:13:36.653936 00:00:00:00:11:01 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:13:36.674492 00:00:00:00:11:00 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:13:36.695025 00:00:00:00:11:01 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:13:36.700825 00:00:00:00:11:01 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 76: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 62) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 34&lt;BR /&gt;23:13:36.700829 00:00:00:00:11:01 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [bad udp cksum de21!] UDP, length 40&lt;BR /&gt;23:13:36.715814 00:00:00:00:11:00 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:13:36.719660 00:00:00:00:11:00 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 76: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 62) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 34&lt;BR /&gt;23:13:36.719693 00:00:00:00:11:00 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:13:36.753988 00:00:00:00:11:01 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [bad udp cksum 7689!] UDP, length 40&lt;BR /&gt;23:13:36.759984 00:00:00:00:11:00 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 1410: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 1396) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: UDP, length 1368&lt;BR /&gt;23:13:36.774506 00:00:00:00:11:00 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:13:36.795027 00:00:00:00:11:01 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:13:36.800868 00:00:00:00:11:01 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:13:36.815840 00:00:00:00:11:00 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:13:36.854039 00:00:00:00:11:01 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:13:36.874521 00:00:00:00:11:00 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:13:36.895028 00:00:00:00:11:01 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:13:36.900928 00:00:00:00:11:01 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 76: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 62) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 34&lt;BR /&gt;23:13:36.900934 00:00:00:00:11:01 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [bad udp cksum de21!] UDP, length 40&lt;BR /&gt;23:13:36.915864 00:00:00:00:11:00 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:13:36.919711 00:00:00:00:11:00 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 76: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 62) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 34&lt;BR /&gt;23:13:36.919744 00:00:00:00:11:00 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 162: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 148) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: UDP, length 120&lt;BR /&gt;23:13:36.954091 00:00:00:00:11:01 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:13:36.974528 00:00:00:00:11:00 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:13:36.995030 00:00:00:00:11:01 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:13:37.000922 00:00:00:00:11:01 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 92: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 78) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 50&lt;BR /&gt;23:13:37.000928 00:00:00:00:11:01 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [bad udp cksum de21!] UDP, length 40&lt;BR /&gt;23:13:37.015903 00:00:00:00:11:00 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:13:37.019771 00:00:00:00:11:00 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 92: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 78) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 50&lt;BR /&gt;23:13:37.019793 00:00:00:00:11:00 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 162: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 148) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: UDP, length 120&lt;BR /&gt;23:13:37.054143 00:00:00:00:11:01 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;[Expert@FW# cphaconf cluster_id get&lt;/P&gt;&lt;P&gt;cphaconf cluster_id: 17&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;==================&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Standby&lt;/P&gt;&lt;P&gt;*********&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;[Expert@FW]# tcpdump -i Sync -nnn -vvv -e port 8116&lt;BR /&gt;tcpdump: listening on Sync, link-type EN10MB (Ethernet), capture size 96 bytes&lt;BR /&gt;23:14:06.598944 00:00:00:00:11:01 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:14:06.609044 00:00:00:00:11:01 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:14:06.615764 00:00:00:00:11:00 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:14:06.637632 00:00:00:00:11:00 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:14:06.653214 00:00:00:00:11:01 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:14:06.686510 00:00:00:00:11:00 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:14:06.698946 00:00:00:00:11:01 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:14:06.709065 00:00:00:00:11:01 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 76: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 62) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 34&lt;BR /&gt;23:14:06.709077 00:00:00:00:11:01 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:14:06.715767 00:00:00:00:11:00 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:14:06.737640 00:00:00:00:11:00 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 76: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 62) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 34&lt;BR /&gt;23:14:06.737646 00:00:00:00:11:00 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [bad udp cksum 11ee!] UDP, length 40&lt;BR /&gt;23:14:06.753224 00:00:00:00:11:01 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:14:06.786513 00:00:00:00:11:00 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 178: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 164) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: UDP, length 136&lt;BR /&gt;23:14:06.798956 00:00:00:00:11:01 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:14:06.809066 00:00:00:00:11:01 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:14:06.815770 00:00:00:00:11:00 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:14:06.826603 00:00:00:00:11:00 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 1258: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 1244) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: UDP, length 1216&lt;BR /&gt;23:14:06.853235 00:00:00:00:11:01 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:14:06.886516 00:00:00:00:11:00 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [bad udp cksum 4fb!] UDP, length 40&lt;BR /&gt;23:14:06.898967 00:00:00:00:11:01 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&lt;BR /&gt;23:14:06.909085 00:00:00:00:11:01 &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 76: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 62) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 34&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;[Expert@FW]# cphaconf cluster_id get&lt;/P&gt;&lt;P&gt;cphaconf cluster_id: 17&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;===================&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;[Expert@FW]# tcpdump -nneei Lan4 port 8116&lt;BR /&gt;tcpdump: verbose output suppressed, use -v or -vv for full protocol decode&lt;BR /&gt;listening on Lan4, link-type EN10MB (Ethernet), capture size 96 bytes&lt;BR /&gt;00:28:47.669350 00:00:00:00:11:00 &amp;gt; 01:00:5e:00:09:f0, ethertype IPv4 (0x0800), length 76: 0.0.0.0.8116 &amp;gt; 10.128.9.0.8116: UDP, length 34&lt;BR /&gt;00:28:47.669355 00:00:00:00:11:00 &amp;gt; 01:00:5e:00:09:f0, ethertype IPv4 (0x0800), length 74: 0.0.0.0.8116 &amp;gt; 10.128.9.0.8116: UDP, length 32&lt;BR /&gt;00:28:47.669385 00:00:00:00:11:00 &amp;gt; 01:00:5e:00:09:f0, ethertype IPv4 (0x0800), length 92: 0.0.0.0.8116 &amp;gt; 10.128.9.0.8116: UDP, length 50&lt;BR /&gt;00:28:47.769330 00:00:00:00:11:00 &amp;gt; 01:00:5e:00:09:f0, ethertype IPv4 (0x0800), length 74: 0.0.0.0.8116 &amp;gt; 10.128.9.0.8116: UDP, length 32&lt;BR /&gt;00:28:47.769356 00:00:00:00:11:00 &amp;gt; 01:00:5e:00:09:f0, ethertype IPv4 (0x0800), length 86: 0.0.0.0.8116 &amp;gt; 10.128.9.0.8116: UDP, length 44&lt;BR /&gt;00:28:47.869358 00:00:00:00:11:00 &amp;gt; 01:00:5e:00:09:f0, ethertype IPv4 (0x0800), length 76: 0.0.0.0.8116 &amp;gt; 10.128.9.0.8116: UDP, length 34&lt;BR /&gt;00:28:47.869370 00:00:00:00:11:00 &amp;gt; 01:00:5e:00:09:f0, ethertype IPv4 (0x0800), length 74: 0.0.0.0.8116 &amp;gt; 10.128.9.0.8116: UDP, length 32&lt;BR /&gt;00:28:47.969370 00:00:00:00:11:00 &amp;gt; 01:00:5e:00:09:f0, ethertype IPv4 (0x0800), length 74: 0.0.0.0.8116 &amp;gt; 10.128.9.0.8116: UDP, length 32&lt;BR /&gt;00:28:48.069409 00:00:00:00:11:00 &amp;gt; 01:00:5e:00:09:f0, ethertype IPv4 (0x0800), length 76: 0.0.0.0.8116 &amp;gt; 10.128.9.0.8116: UDP, length 34&lt;BR /&gt;00:28:48.069422 00:00:00:00:11:00 &amp;gt; 01:00:5e:00:09:f0, ethertype IPv4 (0x0800), length 74: 0.0.0.0.8116 &amp;gt; 10.128.9.0.8116: UDP, length 32&lt;BR /&gt;00:28:48.169431 00:00:00:00:11:00 &amp;gt; 01:00:5e:00:09:f0, ethertype IPv4 (0x0800), length 74: 0.0.0.0.8116 &amp;gt; 10.128.9.0.8116: UDP, length 32&lt;BR /&gt;00:28:48.169457 00:00:00:00:11:00 &amp;gt; 01:00:5e:00:09:f0, ethertype IPv4 (0x0800), length 92: 0.0.0.0.8116 &amp;gt; 10.128.9.0.8116: UDP, length 50&lt;BR /&gt;00:28:48.269457 00:00:00:00:11:00 &amp;gt; 01:00:5e:00:09:f0, ethertype IPv4 (0x0800), length 76: 0.0.0.0.8116 &amp;gt; 10.128.9.0.8116: UDP, length 34&lt;BR /&gt;00:28:48.269470 00:00:00:00:11:00 &amp;gt; 01:00:5e:00:09:f0, ethertype IPv4 (0x0800), length 74: 0.0.0.0.8116 &amp;gt; 10.128.9.0.8116: UDP, length 32&lt;BR /&gt;00:28:48.369477 00:00:00:00:11:00 &amp;gt; 01:00:5e:00:09:f0, ethertype IPv4 (0x0800), length 74: 0.0.0.0.8116 &amp;gt; 10.128.9.0.8116: UDP, length 32&lt;BR /&gt;00:28:48.469508 00:00:00:00:11:00 &amp;gt; 01:00:5e:00:09:f0, ethertype IPv4 (0x0800), length 76: 0.0.0.0.8116 &amp;gt; 10.128.9.0.8116: UDP, length 34&lt;BR /&gt;00:28:48.469521 00:00:00:00:11:00 &amp;gt; 01:00:5e:00:09:f0, ethertype IPv4 (0x0800), length 74: 0.0.0.0.8116 &amp;gt; 10.128.9.0.8116: UDP, length 32&lt;BR /&gt;00:28:48.569519 00:00:00:00:11:00 &amp;gt; 01:00:5e:00:09:f0, ethertype IPv4 (0x0800), length 74: 0.0.0.0.8116 &amp;gt; 10.128.9.0.8116: UDP, length 32&lt;BR /&gt;00:28:48.669559 00:00:00:00:11:00 &amp;gt; 01:00:5e:00:09:f0, ethertype IPv4 (0x0800), length 76: 0.0.0.0.8116 &amp;gt; 10.128.9.0.8116: UDP, length 34&lt;BR /&gt;00:28:48.669572 00:00:00:00:11:00 &amp;gt; 01:00:5e:00:09:f0, ethertype IPv4 (0x0800), length 74: 0.0.0.0.8116 &amp;gt; 10.128.9.0.8116: UDP, length 32&lt;BR /&gt;00:28:48.669601 00:00:00:00:11:00 &amp;gt; 01:00:5e:00:09:f0, ethertype IPv4 (0x0800), length 92: 0.0.0.0.8116 &amp;gt; 10.128.9.0.8116: UDP, length 50&lt;BR /&gt;00:28:48.769548 00:00:00:00:11:00 &amp;gt; 01:00:5e:00:09:f0, ethertype IPv4 (0x0800), length 74: 0.0.0.0.8116 &amp;gt; 10.128.9.0.8116: UDP, length 32&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Apr 2018 22:48:17 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Cluster-Interfaces-down/m-p/12240#M1942</guid>
      <dc:creator>SriNarasimha005</dc:creator>
      <dc:date>2018-04-02T22:48:17Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster-Interfaces down</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Cluster-Interfaces-down/m-p/12241#M1943</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Srinivasan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;it is correct. Both firewalls have the same ClusterXL ID.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Heiko&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Apr 2018 05:48:41 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Cluster-Interfaces-down/m-p/12241#M1943</guid>
      <dc:creator>HeikoAnkenbrand</dc:creator>
      <dc:date>2018-04-03T05:48:41Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster-Interfaces down</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Cluster-Interfaces-down/m-p/12242#M1944</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Did the following entry help?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;# cphaconf set_ccp broadcast&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is the cluster status now ok ( aktive/standby)?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;# cphaprob stat&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Apr 2018 05:54:53 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Cluster-Interfaces-down/m-p/12242#M1944</guid>
      <dc:creator>HeikoAnkenbrand</dc:creator>
      <dc:date>2018-04-03T05:54:53Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster-Interfaces down</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Cluster-Interfaces-down/m-p/12243#M1945</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Heiko, We've requested for Field engineer to check cable connectivity in addition to Multicast drops on switch. Is there any way we can check, is Multicast packets are dropped on switch from firewall end. If so, please assist with the commands to check in firewall to proceed with broadcast command.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Apr 2018 09:09:44 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Cluster-Interfaces-down/m-p/12243#M1945</guid>
      <dc:creator>SriNarasimha005</dc:creator>
      <dc:date>2018-04-03T09:09:44Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster-Interfaces down</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Cluster-Interfaces-down/m-p/12244#M1946</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you see on fw B no CCP packet from fw A. The red filed shows the gateway ID from fw gateway A. If you not see this packet on gateway B, the switch drop the packet.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;23:14:06.615764 00:00:00:00:11:&lt;STRONG style="color: #ff0000;"&gt;00&lt;/STRONG&gt; &amp;gt; 01:00:5e:28:fd:f6, ethertype IPv4 (0x0800), length 82: (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto: UDP (17), length: 68) 0.0.0.0.8116 &amp;gt; 192.168.252.252.8116: [udp sum ok] UDP, length 40&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Apr 2018 18:49:56 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Cluster-Interfaces-down/m-p/12244#M1946</guid>
      <dc:creator>HeikoAnkenbrand</dc:creator>
      <dc:date>2018-04-03T18:49:56Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster-Interfaces down</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Cluster-Interfaces-down/m-p/12245#M1947</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;nbsp;We've changed it to Broadcast, still issue persists..Meanwhile, we're checking switch conf as well. Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;[Expert@FW]# cphaprob -a if&lt;/P&gt;&lt;P&gt;Required interfaces: 8&lt;BR /&gt;Required secured interfaces: 1&lt;/P&gt;&lt;P&gt;Mgmt UP non sync(non secured), broadcast&lt;BR /&gt;Sync UP sync(secured), broadcast&lt;BR /&gt;Lan1 UP non sync(non secured), broadcast&lt;BR /&gt;Lan2 UP non sync(non secured), broadcast&lt;BR /&gt;Lan3 DOWN (15105.8 secs) non sync(non secured), broadcast -------&amp;gt;&amp;gt;&amp;gt;&lt;BR /&gt;Lan4 Inbound: DOWN (3.6 secs) Outbound: DOWN (15105.8 secs) non sync(non secured), broadcast -------&amp;gt;&amp;gt;&amp;gt;&amp;gt;&lt;BR /&gt;Lan5 DOWN (15105.8 secs) non sync(non secured), broadcast -----&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&lt;BR /&gt;Lan6 UP non sync(non secured), broadcast&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Apr 2018 20:04:04 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Cluster-Interfaces-down/m-p/12245#M1947</guid>
      <dc:creator>SriNarasimha005</dc:creator>
      <dc:date>2018-04-03T20:04:04Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster-Interfaces down</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Cluster-Interfaces-down/m-p/12246#M1948</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Heiko, We've found that there is a problem with the switch interfaces. Meanwhile when I check in cat&amp;nbsp; /var/log/messages, I didn't get any logs related to the interfaces down. How we can find what time the interfaces went down in CLI logs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Apr 2018 22:06:42 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Cluster-Interfaces-down/m-p/12246#M1948</guid>
      <dc:creator>SriNarasimha005</dc:creator>
      <dc:date>2018-04-03T22:06:42Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster-Interfaces down</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Cluster-Interfaces-down/m-p/53619#M10713</link>
      <description>&lt;P&gt;Did you ever resolve this? we are having the same issues on our 15600 gateways only they are connected via point to point patch cable. We have been dealing with tac on this case for months now to no avail.&lt;/P&gt;</description>
      <pubDate>Thu, 16 May 2019 17:15:51 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Cluster-Interfaces-down/m-p/53619#M10713</guid>
      <dc:creator>6fdcbce4-7d2e-4</dc:creator>
      <dc:date>2019-05-16T17:15:51Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster-Interfaces down</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Cluster-Interfaces-down/m-p/60878#M12348</link>
      <description>&lt;P&gt;What was the misconfiguration switch-sided?&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;</description>
      <pubDate>Wed, 21 Aug 2019 14:33:29 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Cluster-Interfaces-down/m-p/60878#M12348</guid>
      <dc:creator>AL_Bert</dc:creator>
      <dc:date>2019-08-21T14:33:29Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster-Interfaces down</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Cluster-Interfaces-down/m-p/70845#M14350</link>
      <description>&lt;P&gt;We recently has a similar issue and it was a vlan misconfiguration on the switch. The ports connecting the interfaces on both cluster members had the correct vlan, however, the output of 'cphaprob -a if' showed them as down. We were unable to ping between the directly connected firewall interface and even switched the CCP method from multicast to broadcast.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In the end while the swicthport configuration listed the vlan as part of the port, the actual vlan was not configured on the switch. The cluster interface status changed to UP once the vlan was added to the switch and verified on all required uplinks.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Basically to prevent this issue just ensure that the vlan is configured on all switches and uplinks.&lt;/P&gt;</description>
      <pubDate>Wed, 18 Dec 2019 19:27:12 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Cluster-Interfaces-down/m-p/70845#M14350</guid>
      <dc:creator>steve_warren</dc:creator>
      <dc:date>2019-12-18T19:27:12Z</dc:date>
    </item>
  </channel>
</rss>

