<?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: Probing is not allowed without probe next hop in Spark Firewall (SMB)</title>
    <link>https://community.checkpoint.com/t5/Spark-Firewall-SMB/Probing-is-not-allowed-without-probe-next-hop/m-p/147809#M6806</link>
    <description>&lt;P&gt;Usually, you only configure the active cluster node - standby will sync from active automatically.&lt;/P&gt;</description>
    <pubDate>Wed, 04 May 2022 08:53:54 GMT</pubDate>
    <dc:creator>G_W_Albrecht</dc:creator>
    <dc:date>2022-05-04T08:53:54Z</dc:date>
    <item>
      <title>Probing is not allowed without probe next hop</title>
      <link>https://community.checkpoint.com/t5/Spark-Firewall-SMB/Probing-is-not-allowed-without-probe-next-hop/m-p/147785#M6805</link>
      <description>&lt;P&gt;Hello CheckMates,&lt;/P&gt;
&lt;P&gt;I have a customer with two 1490 clusters in HA, centrally managed, in version R77.20.87 (990173120). We are trying to enable Connection Monitoring with ICMP probing method on a Internet interface. In one cluster we are getting the error "Probing is not allowed without probe next hop", we have verified that both members of this cluster have connectivity and have created a specific route for the monitored IP address.&lt;/P&gt;
&lt;P&gt;On the second cluster, the feature is working ok and the configuration is very similar, the monitored IP address is the same.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This feature was enabled during 2021, but because of a change in the Service Provider, the interface was disabled for two months, now the service is connected again but with this problem now.&lt;/P&gt;
&lt;P&gt;We have a SR opened for more than a month now, and the final answer from TAC was that it is a "known issue" but with no explanation about why it works on one cluster and not in the second cluster, or details about the issue, but while we ask for this information, wanted to check if someone could have any suggestion with the problem. Thanks in advance.&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Captura de pantalla 2022-05-03 223525.jpg" style="width: 541px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/16368i93F679E3E6F40B65/image-dimensions/541x447?v=v2" width="541" height="447" role="button" title="Captura de pantalla 2022-05-03 223525.jpg" alt="Captura de pantalla 2022-05-03 223525.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 04 May 2022 02:37:27 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Spark-Firewall-SMB/Probing-is-not-allowed-without-probe-next-hop/m-p/147785#M6805</guid>
      <dc:creator>RS_Daniel</dc:creator>
      <dc:date>2022-05-04T02:37:27Z</dc:date>
    </item>
    <item>
      <title>Re: Probing is not allowed without probe next hop</title>
      <link>https://community.checkpoint.com/t5/Spark-Firewall-SMB/Probing-is-not-allowed-without-probe-next-hop/m-p/147809#M6806</link>
      <description>&lt;P&gt;Usually, you only configure the active cluster node - standby will sync from active automatically.&lt;/P&gt;</description>
      <pubDate>Wed, 04 May 2022 08:53:54 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Spark-Firewall-SMB/Probing-is-not-allowed-without-probe-next-hop/m-p/147809#M6806</guid>
      <dc:creator>G_W_Albrecht</dc:creator>
      <dc:date>2022-05-04T08:53:54Z</dc:date>
    </item>
  </channel>
</rss>

