<?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 Autocommit loop error and interfaces 'connected but down' after upgrade from 11.0.4-h2 to 11.1.4-h1 in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/autocommit-loop-error-and-interfaces-connected-but-down-after/m-p/599882#M3856</link>
    <description>&lt;P&gt;After upgrading my PA-VM VM-100 appliance from&amp;nbsp;from 11.0.4-h2 to 11.1.4-h1 i was met with the following errors:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;- Constant failed 'autocommit' jobs spawning, similar to&amp;nbsp;&lt;A href="https://live.paloaltonetworks.com/t5/next-generation-firewall/auto-commit-stuck-at-11-0-2-h2-pa-410/td-p/563107" target="_blank"&gt;https://live.paloaltonetworks.com/t5/next-generation-firewall/auto-commit-stuck-at-11-0-2-h2-pa-410/td-p/563107&lt;/A&gt;. This prevents any admin action from the Web UI,&lt;/P&gt;
&lt;P&gt;- All interfaces were listed as 'connected but down' (grey status for interfaces, and red status for VLAN subinterfaces). The underlying VMXNET3 virtual NICs were definitely connected, and the MGMT interface remained connected.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Due to the above errors, especially the interfaces refusing to come up, I was forced to use 'debug swm status' &amp;amp; 'debug swm revert' to revert to&amp;nbsp;11.0.4-h2 and reboot, at which point the FW restarted with software version 11.0.4-h2 and all interfaces were once again 'up'&lt;/P&gt;</description>
    <pubDate>Wed, 09 Oct 2024 12:34:18 GMT</pubDate>
    <dc:creator>OKelly</dc:creator>
    <dc:date>2024-10-09T12:34:18Z</dc:date>
    <item>
      <title>Autocommit loop error and interfaces 'connected but down' after upgrade from 11.0.4-h2 to 11.1.4-h1</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/autocommit-loop-error-and-interfaces-connected-but-down-after/m-p/599882#M3856</link>
      <description>&lt;P&gt;After upgrading my PA-VM VM-100 appliance from&amp;nbsp;from 11.0.4-h2 to 11.1.4-h1 i was met with the following errors:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;- Constant failed 'autocommit' jobs spawning, similar to&amp;nbsp;&lt;A href="https://live.paloaltonetworks.com/t5/next-generation-firewall/auto-commit-stuck-at-11-0-2-h2-pa-410/td-p/563107" target="_blank"&gt;https://live.paloaltonetworks.com/t5/next-generation-firewall/auto-commit-stuck-at-11-0-2-h2-pa-410/td-p/563107&lt;/A&gt;. This prevents any admin action from the Web UI,&lt;/P&gt;
&lt;P&gt;- All interfaces were listed as 'connected but down' (grey status for interfaces, and red status for VLAN subinterfaces). The underlying VMXNET3 virtual NICs were definitely connected, and the MGMT interface remained connected.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Due to the above errors, especially the interfaces refusing to come up, I was forced to use 'debug swm status' &amp;amp; 'debug swm revert' to revert to&amp;nbsp;11.0.4-h2 and reboot, at which point the FW restarted with software version 11.0.4-h2 and all interfaces were once again 'up'&lt;/P&gt;</description>
      <pubDate>Wed, 09 Oct 2024 12:34:18 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/autocommit-loop-error-and-interfaces-connected-but-down-after/m-p/599882#M3856</guid>
      <dc:creator>OKelly</dc:creator>
      <dc:date>2024-10-09T12:34:18Z</dc:date>
    </item>
  </channel>
</rss>

