<?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: PA-VM-300 refuse to boot because master key expired. in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/pa-vm-300-refuse-to-boot-because-master-key-expired/m-p/171804#M54280</link>
    <description>&lt;P&gt;An expired master key cannot be recovered. You must factory reset your VM.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Once it's booted into the fresh OS, you can load a backup config file or configure the device from scratch.&lt;/P&gt;</description>
    <pubDate>Wed, 16 Aug 2017 08:35:02 GMT</pubDate>
    <dc:creator>reaper</dc:creator>
    <dc:date>2017-08-16T08:35:02Z</dc:date>
    <item>
      <title>PA-VM-300 refuse to boot because master key expired.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pa-vm-300-refuse-to-boot-because-master-key-expired/m-p/171779#M54275</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;today i found my PA-VM-300 in maintenance mode, refusing to boot.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Maitenance Entry Reason:&lt;/P&gt;&lt;P&gt;Cryptod failure. Caused by: Master key expired.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;This firewall is a backup of our production firewall, in our &lt;SPAN class="lang-en"&gt;&lt;I&gt;Disaster Recovery Plan&lt;/I&gt;&lt;/SPAN&gt;, in addition to VMware SRM.&lt;/P&gt;&lt;P&gt;I use the API to push the production configuration to this firewall. In order to allow the backup firewall to accept the production configuration, I have manually set the same Master key on both firewall, and I use a script to perform some change in the .xml config file before pushing it via the API.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It works well, it sync every night. We tested our disaster recovery plan last year and everything worked as expected.&lt;/P&gt;&lt;P&gt;PANOS version is 6.1.15.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As I use the API to perform the change, and my firewall can't send mail to me because of his environment, I apparently missed the reminder about the Master key.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="2017-08-16_171551.jpg" style="width: 800px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/10797iD0AE722F88E21ED3/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="2017-08-16_171551.jpg" alt="2017-08-16_171551.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What can I do to get my VM booting again ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks for you help.&lt;/P&gt;</description>
      <pubDate>Wed, 16 Aug 2017 06:18:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pa-vm-300-refuse-to-boot-because-master-key-expired/m-p/171779#M54275</guid>
      <dc:creator>reseau.dtsi</dc:creator>
      <dc:date>2017-08-16T06:18:58Z</dc:date>
    </item>
    <item>
      <title>Re: PA-VM-300 refuse to boot because master key expired.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pa-vm-300-refuse-to-boot-because-master-key-expired/m-p/171788#M54276</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Boot into the maintenance mode and reset to its default:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="maint.JPG" style="width: 800px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/10798i12D3D97367C5B2ED/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="maint.JPG" alt="maint.JPG" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 16 Aug 2017 06:31:59 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pa-vm-300-refuse-to-boot-because-master-key-expired/m-p/171788#M54276</guid>
      <dc:creator>TranceforLife</dc:creator>
      <dc:date>2017-08-16T06:31:59Z</dc:date>
    </item>
    <item>
      <title>Re: PA-VM-300 refuse to boot because master key expired.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pa-vm-300-refuse-to-boot-because-master-key-expired/m-p/171804#M54280</link>
      <description>&lt;P&gt;An expired master key cannot be recovered. You must factory reset your VM.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Once it's booted into the fresh OS, you can load a backup config file or configure the device from scratch.&lt;/P&gt;</description>
      <pubDate>Wed, 16 Aug 2017 08:35:02 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pa-vm-300-refuse-to-boot-because-master-key-expired/m-p/171804#M54280</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2017-08-16T08:35:02Z</dc:date>
    </item>
    <item>
      <title>Re: PA-VM-300 refuse to boot because master key expired.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pa-vm-300-refuse-to-boot-because-master-key-expired/m-p/172133#M54352</link>
      <description>&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I was afraid that a factory reset change the UUID, and having issue with licenses, but it stay the same.&lt;/P&gt;&lt;P&gt;After reset, I set it back in function in half an hour.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I will be more careful with this master key in the future.&lt;/P&gt;</description>
      <pubDate>Fri, 18 Aug 2017 02:47:35 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pa-vm-300-refuse-to-boot-because-master-key-expired/m-p/172133#M54352</guid>
      <dc:creator>reseau.dtsi</dc:creator>
      <dc:date>2017-08-18T02:47:35Z</dc:date>
    </item>
  </channel>
</rss>

