<?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 Critical error on PA 5000 series running 8.0.12 IOS in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/critical-error-on-pa-5000-series-running-8-0-12-ios/m-p/286109#M76540</link>
    <description>&lt;P&gt;Guys,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;have 2 PA in HA activs-passive mode, couple of days back Active PA was displaying a notification as&lt;/P&gt;&lt;P&gt;"A critical error has been detected preventing proper boot up of the device.The system is in maintenance mode"&lt;/P&gt;&lt;P&gt;We rebooted and reconfigured with all HA configs and integrated into HA pair again.&lt;/P&gt;&lt;P&gt;This week i see the same ERROR on our other device(passive). Does anyone faced this issue? what is the possible solution ?&lt;/P&gt;&lt;P&gt;Help !&lt;/P&gt;</description>
    <pubDate>Sun, 01 Sep 2019 05:43:17 GMT</pubDate>
    <dc:creator>NSRCSupport</dc:creator>
    <dc:date>2019-09-01T05:43:17Z</dc:date>
    <item>
      <title>Critical error on PA 5000 series running 8.0.12 IOS</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/critical-error-on-pa-5000-series-running-8-0-12-ios/m-p/286109#M76540</link>
      <description>&lt;P&gt;Guys,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;have 2 PA in HA activs-passive mode, couple of days back Active PA was displaying a notification as&lt;/P&gt;&lt;P&gt;"A critical error has been detected preventing proper boot up of the device.The system is in maintenance mode"&lt;/P&gt;&lt;P&gt;We rebooted and reconfigured with all HA configs and integrated into HA pair again.&lt;/P&gt;&lt;P&gt;This week i see the same ERROR on our other device(passive). Does anyone faced this issue? what is the possible solution ?&lt;/P&gt;&lt;P&gt;Help !&lt;/P&gt;</description>
      <pubDate>Sun, 01 Sep 2019 05:43:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/critical-error-on-pa-5000-series-running-8-0-12-ios/m-p/286109#M76540</guid>
      <dc:creator>NSRCSupport</dc:creator>
      <dc:date>2019-09-01T05:43:17Z</dc:date>
    </item>
    <item>
      <title>Re: Critical error on PA 5000 series running 8.0.12 IOS</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/critical-error-on-pa-5000-series-running-8-0-12-ios/m-p/286371#M76581</link>
      <description>&lt;P&gt;Ok, so I am so to start out and say I am confused... &lt;span class="lia-unicode-emoji" title=":face_with_tongue:"&gt;😛&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I get that the Active FW did not boot up properly (so this leads me to believe that the other FW was actually the one passing traffic)&lt;/P&gt;&lt;P&gt;I then understood that you rebooted and otherwise fixed the Active box, so now it is properly passing traffic.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What I am not clear about, is.. that is appears your passive FW was shutdow/rebooted, with same/similar issue.&amp;nbsp;&lt;/P&gt;&lt;P&gt;My question would be... did you know that you/coworker rebooted passive FW?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You will need to get a tech support file (after getting passive FW back online) and open ticket with TAC.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The troubleshooting for RCA (root cause analysis) is beyond the scope of us at the LiveCommunity.&amp;nbsp; &lt;span class="lia-unicode-emoji" title=":face_with_tongue:"&gt;😛&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 03 Sep 2019 19:14:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/critical-error-on-pa-5000-series-running-8-0-12-ios/m-p/286371#M76581</guid>
      <dc:creator>S.Cantwell</dc:creator>
      <dc:date>2019-09-03T19:14:38Z</dc:date>
    </item>
  </channel>
</rss>

