License Firewall ESXi VM before bootstrapping

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

License Firewall ESXi VM before bootstrapping

L4 Transporter

We are trying to do automated deployment of multiple VM firewalls, managed by Panorama and using bootstrapping for the initial setup. All appliances will be hosted on ESXi server.  

 

The problem we have is how to license the VM firewalls before bootstrapping. I read the related admin guides and the VM licensing part is not quite clear. 

Documentation suggest that a firewall need to be licensed first, then PA-VM  and other license files downloaded and placed in the relevant bootstrap folder.

 

However, in order to license the firewall, you need to have the firewall CPUID and we can only get that after the firewall boot.

We can boot the firewall and license it then, but then it defeats the whole concept of bootstrapping and adds a lot of additional manual work to multi-firewall deployment. Also, if the firewall is not licensed, it does not have a serial number and adding it Panorama fails.

 

Have you done this before and how did you resolve the licence issue?

1 REPLY 1

L4 Transporter

Can anyone help?

  • 2628 Views
  • 1 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!