<?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: Running 11.1.2 in production in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/running-11-1-2-in-production/m-p/583669#M2975</link>
    <description>&lt;P&gt;I as well am considering upgrading to 11.1 but am very concerned about this issue. I too would love to hear from anyone running the latest 11.1.2-h3 that has the CVE-2024-3400 fix as to their experience, or from an engineer as to what this actually means and what the likelihood of impact is. Being as the preferred release is seemingly affected by this I would think the likelihood is very small but I have been wrong before.&lt;/P&gt;</description>
    <pubDate>Mon, 15 Apr 2024 04:31:02 GMT</pubDate>
    <dc:creator>KKnowles1</dc:creator>
    <dc:date>2024-04-15T04:31:02Z</dc:date>
    <item>
      <title>Running 11.1.2 in production</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/running-11-1-2-in-production/m-p/582129#M2919</link>
      <description>&lt;P&gt;Hi everyone&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I read that 11.1.2 is now the preferred release for 34xx, and desiring to upgrade due to some of the new features, I find myself concerned about this known issue:&lt;/P&gt;
&lt;P&gt;PAN-224763 - A TDB engine version mismatch issue affecting all firewalls, which in turn produces heartbeat failures, can cause the firewall to crash when installing content updates.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It reads like "when you upgrade TBD engine, expect a heartbeat failure and crash.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is that the case? Or is it something that you can account for and work around?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Anyone running 11.1.2 (or -h1) in prod that who can give some feedback?&lt;/P&gt;</description>
      <pubDate>Fri, 29 Mar 2024 10:15:35 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/running-11-1-2-in-production/m-p/582129#M2919</guid>
      <dc:creator>SomeSuch</dc:creator>
      <dc:date>2024-03-29T10:15:35Z</dc:date>
    </item>
    <item>
      <title>Re: Running 11.1.2 in production</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/running-11-1-2-in-production/m-p/583260#M2965</link>
      <description>&lt;P&gt;I was also ready to update but read the known issues and got hung up on this same one.&amp;nbsp; Sounds like a show stopper to me.&lt;/P&gt;</description>
      <pubDate>Wed, 10 Apr 2024 17:38:05 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/running-11-1-2-in-production/m-p/583260#M2965</guid>
      <dc:creator>MHabeger</dc:creator>
      <dc:date>2024-04-10T17:38:05Z</dc:date>
    </item>
    <item>
      <title>Re: Running 11.1.2 in production</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/running-11-1-2-in-production/m-p/583669#M2975</link>
      <description>&lt;P&gt;I as well am considering upgrading to 11.1 but am very concerned about this issue. I too would love to hear from anyone running the latest 11.1.2-h3 that has the CVE-2024-3400 fix as to their experience, or from an engineer as to what this actually means and what the likelihood of impact is. Being as the preferred release is seemingly affected by this I would think the likelihood is very small but I have been wrong before.&lt;/P&gt;</description>
      <pubDate>Mon, 15 Apr 2024 04:31:02 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/running-11-1-2-in-production/m-p/583669#M2975</guid>
      <dc:creator>KKnowles1</dc:creator>
      <dc:date>2024-04-15T04:31:02Z</dc:date>
    </item>
  </channel>
</rss>

