<?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 member down after RMA in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/cluster-member-down-after-RMA/m-p/182891#M33548</link>
    <description>&lt;P&gt;R80.40 T294&lt;/P&gt;</description>
    <pubDate>Thu, 01 Jun 2023 10:28:30 GMT</pubDate>
    <dc:creator>a574591</dc:creator>
    <dc:date>2023-06-01T10:28:30Z</dc:date>
    <item>
      <title>cluster member down after RMA</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/cluster-member-down-after-RMA/m-p/182757#M33525</link>
      <description>&lt;P&gt;Hello,&amp;nbsp;&lt;/P&gt;&lt;P&gt;After RMA of one of the cluster nodes we are unable to restore the cluster according to the&amp;nbsp;sk160533.&amp;nbsp;&lt;/P&gt;&lt;P&gt;SIC status: Communicating&lt;/P&gt;&lt;P&gt;cphaprob state on on the down node shows Event Code: CLUS-110800&lt;/P&gt;&lt;P&gt;cphaprob -a if on the active member shows Required interfaces: 13, while on the down member: 4. Why is that and is it a reason why the cluster is not working properly?&lt;/P&gt;&lt;P&gt;The CCP mode is Manual (Unicast) for both nodes.&amp;nbsp;&lt;/P&gt;&lt;P&gt;The number of Virtual cluster interfaces is the same for both.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 31 May 2023 15:26:10 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/cluster-member-down-after-RMA/m-p/182757#M33525</guid>
      <dc:creator>a574591</dc:creator>
      <dc:date>2023-05-31T15:26:10Z</dc:date>
    </item>
    <item>
      <title>Re: cluster member down after RMA</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/cluster-member-down-after-RMA/m-p/182830#M33534</link>
      <description>&lt;P&gt;Which version &amp;amp; JHF is this system and did you verify/restore the network interface levels configurations, are they properly connected?&lt;/P&gt;
&lt;P&gt;Please contact TAC to help expedite resolution if not already having followed the process outlined in full.&lt;/P&gt;</description>
      <pubDate>Thu, 01 Jun 2023 00:34:55 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/cluster-member-down-after-RMA/m-p/182830#M33534</guid>
      <dc:creator>Chris_Atkinson</dc:creator>
      <dc:date>2023-06-01T00:34:55Z</dc:date>
    </item>
    <item>
      <title>Re: cluster member down after RMA</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/cluster-member-down-after-RMA/m-p/182838#M33538</link>
      <description>&lt;P&gt;You need to make sure both interfaces are the same between both cluster members.&lt;/P&gt;&lt;P&gt;Otherwise it will have cluster down.&lt;/P&gt;&lt;P&gt;Take a look at this &lt;SPAN&gt;sk125152&amp;nbsp;&lt;/SPAN&gt;for more detail&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Jun 2023 01:29:58 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/cluster-member-down-after-RMA/m-p/182838#M33538</guid>
      <dc:creator>just13pro</dc:creator>
      <dc:date>2023-06-01T01:29:58Z</dc:date>
    </item>
    <item>
      <title>Re: cluster member down after RMA</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/cluster-member-down-after-RMA/m-p/182891#M33548</link>
      <description>&lt;P&gt;R80.40 T294&lt;/P&gt;</description>
      <pubDate>Thu, 01 Jun 2023 10:28:30 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/cluster-member-down-after-RMA/m-p/182891#M33548</guid>
      <dc:creator>a574591</dc:creator>
      <dc:date>2023-06-01T10:28:30Z</dc:date>
    </item>
    <item>
      <title>Re: cluster member down after RMA</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/cluster-member-down-after-RMA/m-p/182898#M33550</link>
      <description>&lt;P&gt;Just throwing this out there...did you make sure that topology matches on both members? Meaning all interfaces that are supposed to be clustered are set as cluster in topology in smart console object?&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Thu, 01 Jun 2023 11:27:02 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/cluster-member-down-after-RMA/m-p/182898#M33550</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2023-06-01T11:27:02Z</dc:date>
    </item>
    <item>
      <title>Re: cluster member down after RMA</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/cluster-member-down-after-RMA/m-p/184264#M33850</link>
      <description>&lt;P&gt;After changing the fwha_monitor_all_vlan=0 to =1 and rebooting, the cluster returned to operation.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Topic can be closed.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jun 2023 08:55:15 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/cluster-member-down-after-RMA/m-p/184264#M33850</guid>
      <dc:creator>a574591</dc:creator>
      <dc:date>2023-06-19T08:55:15Z</dc:date>
    </item>
  </channel>
</rss>

