10-22-2020 07:58 AM
Hi everyone,
I am currently trying to register a newly created VM-Series firewall to Panorama.
The bootstrap process is working and the firewall can register to Panorama, nevertheless, it cannot apply the configuration pushed by Panorama since the content update packages are not installed and therefore some objects like EDLs from Palo Alto are not available (this causes an error during the commit process). I really would like to avoid to install these content packages manually and automate the deployment as much as possible. I would also like to have my default shared policies containing these EDLs pushed to these firewalls right after they have been deployed.
I tried to put the content update packages directly in the /content folder in my S3 bootstrap bucket, but it looks like the Firewall does not see them and never installs them during the bootstrap process. I made sure the files have the correct name and downloaded these content files from the Palo Alto support center before uploading them to my S3 bucket.
Please note that during my tests I was using PAYG VM-300 Bundle 2 instances, version 9.0.9-h1.xfr
Did someone manage to make this work somehow?
Any help would be greatly appreciated 🙂
Thanks.
Yann
11-13-2020 12:16 AM - edited 11-13-2020 12:19 AM
For those who might be interested, I finally figured out why this was not working.
This was due to server-side encryption being enabled on the S3 bucket.
After disabling server-side encryption on the S3 bucket, the bootstrap worked fine and the content updates could also be installed. Please note that you will need at list version 9.1.7 or 10.0.2 if you want the self-registration to Panorama to work together with the installation of content updates during the bootstrap, otherwise autocommit will fail at the end of the bootstrap process and your vm-series will not self-register to panorama using its vm-auth-key.
Many thanks to the Palo Alto TAC Engineer who took the time to reproduce this in his lab to confirm what was the expected behavior.
11-13-2020 12:16 AM - edited 11-13-2020 12:19 AM
For those who might be interested, I finally figured out why this was not working.
This was due to server-side encryption being enabled on the S3 bucket.
After disabling server-side encryption on the S3 bucket, the bootstrap worked fine and the content updates could also be installed. Please note that you will need at list version 9.1.7 or 10.0.2 if you want the self-registration to Panorama to work together with the installation of content updates during the bootstrap, otherwise autocommit will fail at the end of the bootstrap process and your vm-series will not self-register to panorama using its vm-auth-key.
Many thanks to the Palo Alto TAC Engineer who took the time to reproduce this in his lab to confirm what was the expected behavior.
02-23-2024 07:01 AM
Hi guys, since January 2023 it is no longer possible to disable server-side encryption on AWS, is there another workaround?
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
