<?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: Panorama 10.1.6-h3 - Device Import Failed in Panorama Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/panorama-discussions/panorama-10-1-6-h3-device-import-failed/m-p/517300#M1136</link>
    <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/136634"&gt;@DanaHawkins&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;"Reassociate" have different purpose - it should be used if you want to assign already connected firewall to different device-group and template stack.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I had similar experience last time I was adding VM firewall to Panorama - although the correct auth-key was used devices was still in disconnected state. My suggestion is to re-add the firewall again&lt;BR /&gt;1. Remove FW from Panorama, with "delete" button under Managed Devices -&amp;gt; Summary&lt;/P&gt;
&lt;P&gt;2. Commit to Panorama&lt;/P&gt;
&lt;P&gt;3. Click on Add, generate new auth-key, (optionally uncheck associate devices), enter VM FW serial number&lt;/P&gt;
&lt;P&gt;4. Commit to Panorama&lt;/P&gt;
&lt;P&gt;5. Go to firewall and enter the new auth-key (to be honest I am not sure if you need to commit fw config, but I would suggest to do it)&lt;/P&gt;</description>
    <pubDate>Mon, 10 Oct 2022 13:52:32 GMT</pubDate>
    <dc:creator>aleksandar.astardzhiev</dc:creator>
    <dc:date>2022-10-10T13:52:32Z</dc:date>
    <item>
      <title>Panorama 10.1.6-h3 - Device Import Failed</title>
      <link>https://live.paloaltonetworks.com/t5/panorama-discussions/panorama-10-1-6-h3-device-import-failed/m-p/516380#M1121</link>
      <description>&lt;P&gt;I'm trying to import an AWS Palo Alto VM-Series firewall running 10.1.5-h2 into an ESXi Panorama VM running 10.1.6-h3. Communication between the firewall and panorama is good and there doesn't seem to be any routing issues.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I added the serial number into Panorama and generated the Auth-Key for the firewall but the firewall is showing up as "Disconnected". When I try to "Reassociate" the device I get an error that reads "Import Failed &amp;lt;serial number&amp;gt; to-sw-version is invalid"&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I've searched Palo Alto KB and the Internet. I've found nothing related to this error.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Has anyone seen this one before? Or is there a system log that I can look at that might give some additional insight?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Your help would be greatly appreciated.&lt;/P&gt;</description>
      <pubDate>Thu, 29 Sep 2022 16:22:36 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/panorama-discussions/panorama-10-1-6-h3-device-import-failed/m-p/516380#M1121</guid>
      <dc:creator>DanaHawkins</dc:creator>
      <dc:date>2022-09-29T16:22:36Z</dc:date>
    </item>
    <item>
      <title>Re: Panorama 10.1.6-h3 - Device Import Failed</title>
      <link>https://live.paloaltonetworks.com/t5/panorama-discussions/panorama-10-1-6-h3-device-import-failed/m-p/517300#M1136</link>
      <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/136634"&gt;@DanaHawkins&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;"Reassociate" have different purpose - it should be used if you want to assign already connected firewall to different device-group and template stack.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I had similar experience last time I was adding VM firewall to Panorama - although the correct auth-key was used devices was still in disconnected state. My suggestion is to re-add the firewall again&lt;BR /&gt;1. Remove FW from Panorama, with "delete" button under Managed Devices -&amp;gt; Summary&lt;/P&gt;
&lt;P&gt;2. Commit to Panorama&lt;/P&gt;
&lt;P&gt;3. Click on Add, generate new auth-key, (optionally uncheck associate devices), enter VM FW serial number&lt;/P&gt;
&lt;P&gt;4. Commit to Panorama&lt;/P&gt;
&lt;P&gt;5. Go to firewall and enter the new auth-key (to be honest I am not sure if you need to commit fw config, but I would suggest to do it)&lt;/P&gt;</description>
      <pubDate>Mon, 10 Oct 2022 13:52:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/panorama-discussions/panorama-10-1-6-h3-device-import-failed/m-p/517300#M1136</guid>
      <dc:creator>aleksandar.astardzhiev</dc:creator>
      <dc:date>2022-10-10T13:52:32Z</dc:date>
    </item>
    <item>
      <title>Re: Panorama 10.1.6-h3 - Device Import Failed</title>
      <link>https://live.paloaltonetworks.com/t5/panorama-discussions/panorama-10-1-6-h3-device-import-failed/m-p/523560#M1259</link>
      <description>&lt;P&gt;I'm stuck in the same cycle.&amp;nbsp; I went to add 2 HA Pair's last night and the secondary of one pair went in without issue, the other 3 are stuck in disconnected.&amp;nbsp; Dynamics, plugins, softwares are all matched...I've followed the above (about 5 times on each of them) and still stuck.&amp;nbsp; They are all 4 on the same mgmt /24 subnet and I see the traffic for the one that is working (fw mgmt to pano mgmt via 3978) but none of the other traffics.&amp;nbsp; So odd.&amp;nbsp; &amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any other suggestions on shunting this out?&amp;nbsp; It also looks like when I DO send off for a new auth key it's the same one as before.&amp;nbsp; How do I force a new auth key maybe?&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 07 Dec 2022 19:20:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/panorama-discussions/panorama-10-1-6-h3-device-import-failed/m-p/523560#M1259</guid>
      <dc:creator>JesseLeiker</dc:creator>
      <dc:date>2022-12-07T19:20:17Z</dc:date>
    </item>
  </channel>
</rss>

