<?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: FIPS Failure upon boot in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/fips-failure-upon-boot/m-p/344699#M86225</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/112329"&gt;@BryanSG&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Maintenance mode is effectively the recovery menu when something is wrong with the OS. It's quite possible that something in your OS image was corrupt when the device unexpectedly lost power. If simply restarting the box is still causing issues I would either attempt to re-install the OS or contact TAC and open a ticket on it.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 20 Aug 2020 03:06:16 GMT</pubDate>
    <dc:creator>BPry</dc:creator>
    <dc:date>2020-08-20T03:06:16Z</dc:date>
    <item>
      <title>FIPS Failure upon boot</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/fips-failure-upon-boot/m-p/344670#M86220</link>
      <description>&lt;P&gt;One of devices was not properly shut down due to a power outage in a building.&amp;nbsp; When the device started back up, it appears that it entered maintenance mode.&amp;nbsp; The reason is FIPS failure.&amp;nbsp; I have attempted to reboot the device from maintenance mode and appeared to work (was able to get to the normal prompt for asking password when attempting ssh).&amp;nbsp; But a few minutes later, the device went back to maintenance mode.&amp;nbsp; Is there any way to exit maintenance mode or to stop the device going into maintenance mode when booted?&lt;/P&gt;</description>
      <pubDate>Wed, 19 Aug 2020 21:31:59 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/fips-failure-upon-boot/m-p/344670#M86220</guid>
      <dc:creator>BryanSG</dc:creator>
      <dc:date>2020-08-19T21:31:59Z</dc:date>
    </item>
    <item>
      <title>Re: FIPS Failure upon boot</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/fips-failure-upon-boot/m-p/344699#M86225</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/112329"&gt;@BryanSG&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Maintenance mode is effectively the recovery menu when something is wrong with the OS. It's quite possible that something in your OS image was corrupt when the device unexpectedly lost power. If simply restarting the box is still causing issues I would either attempt to re-install the OS or contact TAC and open a ticket on it.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 20 Aug 2020 03:06:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/fips-failure-upon-boot/m-p/344699#M86225</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2020-08-20T03:06:16Z</dc:date>
    </item>
    <item>
      <title>Re: FIPS Failure upon boot</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/fips-failure-upon-boot/m-p/467298#M102772</link>
      <description>&lt;P&gt;Thank you and sorry for late response.&amp;nbsp; A case was opened and found that the system had to be RMAed.&lt;/P&gt;</description>
      <pubDate>Mon, 21 Feb 2022 17:53:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/fips-failure-upon-boot/m-p/467298#M102772</guid>
      <dc:creator>BryanSG</dc:creator>
      <dc:date>2022-02-21T17:53:00Z</dc:date>
    </item>
  </channel>
</rss>

