<?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: IA traffic dropped after clusterXL failover in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/IA-traffic-dropped-after-clusterXL-failover/m-p/102103#M10181</link>
    <description>Turns out it is sk167174</description>
    <pubDate>Mon, 16 Nov 2020 05:17:33 GMT</pubDate>
    <dc:creator>Ryan_Ryan</dc:creator>
    <dc:date>2020-11-16T05:17:33Z</dc:date>
    <item>
      <title>IA traffic dropped after clusterXL failover</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/IA-traffic-dropped-after-clusterXL-failover/m-p/101947#M10179</link>
      <description>&lt;P&gt;R80.20 gateway T173&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Strange issue, after a cluster failover, all users across multiple terminal servers could no longer access resources, when we checked the logs the source ports of the traffic were on were not matching the allocated ranges as shown on the gateway.&lt;/P&gt;&lt;P&gt;Once we failed back traffic flowed correctly, strangely anytime I check the port allocation across the primary and standby now they are always matching. (unfortunately I didn't do this during the time of the incident).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone seen this before?&lt;/P&gt;</description>
      <pubDate>Fri, 13 Nov 2020 01:44:57 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/IA-traffic-dropped-after-clusterXL-failover/m-p/101947#M10179</guid>
      <dc:creator>Ryan_Ryan</dc:creator>
      <dc:date>2020-11-13T01:44:57Z</dc:date>
    </item>
    <item>
      <title>Re: IA traffic dropped after clusterXL failover</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/IA-traffic-dropped-after-clusterXL-failover/m-p/102094#M10180</link>
      <description>&lt;P&gt;Clearly there is (or was) some sort of sync issue that cleared itself up.&lt;BR /&gt;You'd probably need to engage the TAC to troubleshoot this further.&lt;/P&gt;</description>
      <pubDate>Mon, 16 Nov 2020 03:08:50 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/IA-traffic-dropped-after-clusterXL-failover/m-p/102094#M10180</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2020-11-16T03:08:50Z</dc:date>
    </item>
    <item>
      <title>Re: IA traffic dropped after clusterXL failover</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/IA-traffic-dropped-after-clusterXL-failover/m-p/102103#M10181</link>
      <description>Turns out it is sk167174</description>
      <pubDate>Mon, 16 Nov 2020 05:17:33 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/IA-traffic-dropped-after-clusterXL-failover/m-p/102103#M10181</guid>
      <dc:creator>Ryan_Ryan</dc:creator>
      <dc:date>2020-11-16T05:17:33Z</dc:date>
    </item>
  </channel>
</rss>

