Bootstrap Configuration Example for VM-Series in Azure¶
Using bootstrap option significantly simplifies VM-Series initial configuration setup.
In this document, we provide a bootstrap example to set up an to allow HTTPS for Health Check Policy , “Allow All” firewall Policy and Egress NAT policy for the VM-Series to validate that traffic is indeed sent to the VM-Series for VNET to VNET traffic inspection. This example does not use Panorama.
Please use 9.1.0 and above version for better results.
Note that Panorama PAN-OS version should be the same or higher than the firewall VMs when they are added to the Panorama, like, 9.1.0 for both Panorama and VMs.
For a manual setup, follow manual setup example.
1. Create Storage Account and Private Container¶
Login to Azure’s console and create a storage account and file share in the storage for bootstrap with a unique name, for example “pan bootstrap”, using this guide Step 1 and 2 with the following structure:
Storage Account (e.g. bootstrapstorage) File Share (e.g. pan-bootstrap) Config/ init-cfg.txt bootstrap.xml Content License Software
2. Upload config files¶
Follow Step 2.3 to upload the configuration. Example Bootstrap.xml and config file is provided below.
2.1 The example bootstrap.xml file contains the “Allow All”, Egress and API admin setup. To downloady the file, click
2.2 For the example init-cfg.txt file, click
In the example bootstrap.xml, the API admin user name is avxadmin and the password is Aviatrix123#. You can customize it.
2.3 upload these two files to your config folder under Storage Account-> File Shares.
3. Launch the VM-Series instance¶
First follow Step 3 to get an access key which will be required at a time of VM-Series launch.
Follow the Aviatrix Firewall Network (FireNet) workflow Step 7a.
Fill in the required fields. Click Advanced. Fill in the following parameters.
|Advanced Field||Example Value|
|Bootstrap Storage Name||Azure Storage Name (e.g. bootstrapstorage)|
|Storage Access Key||Azure Storage key (e.g. XiFiEeCzBLueMDTcKGdxhSV+ZUG3UvnLgfqA==)|
|File-share Folder||File Share Folder Name (e.g. pan-bootstrap)|
|Share-directory (Optional)||Config (Optional)|
Launch the VM-Series instance. Wait for 15 minutes for it to boot up and initialize.
Login to the HTTPS interface of VM-Series management public IP with username “admin”, password “Aviatrix123#”
4. Configure API Vendor Integration¶
In order for the Aviatrix Controller to automatically update firewall instance route tables, monitor the firewall instance health and manage instance failover, you need to setup API access permissions.
Go to Controller -> Firewall Network -> Vendor Integration -> Firewall. Note the following fields.
- Firewall Login User Name field, use “avxadmin” without the double quotes.
- Firewall Login Password field, use “Aviatrix123#” without the double quotes.
If you are manually configuring the firewall from scratch, follow the instructions here to enable API access.
5. Ready to go!¶
Now your firewall instance is ready to receive packets!
Next step is to validate your configurations and polices using FlightPath and Diagnostic Tools (ping, traceroute etc.).
6. View Traffic Log¶
You can view if traffic is forwarded to the firewall instance by logging in to the VM-Series console. Click Monitor. Start ping packets from one Spoke VNET to another Spoke VNET.