Panorama 10.1.6-h3 - Device Import Failed

[DanaHawkins]

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.

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 <serial number> to-sw-version is invalid"

I've searched Palo Alto KB and the Internet. I've found nothing related to this error.

Has anyone seen this one before? Or is there a system log that I can look at that might give some additional insight?

Your help would be greatly appreciated.

[aleksandar.astardzhiev · Accepted solution]

Hi @DanaHawkins ,

"Reassociate" have different purpose - it should be used if you want to assign already connected firewall to different device-group and template stack.

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
1. Remove FW from Panorama, with "delete" button under Managed Devices -> Summary

2. Commit to Panorama

3. Click on Add, generate new auth-key, (optionally uncheck associate devices), enter VM FW serial number

4. Commit to Panorama

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)

[JesseLeiker]

I'm stuck in the same cycle.  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.  Dynamics, plugins, softwares are all matched...I've followed the above (about 5 times on each of them) and still stuck.  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.  So odd.   

Any other suggestions on shunting this out?  It also looks like when I DO send off for a new auth key it's the same one as before.  How do I force a new auth key maybe?