Example Config for Palo Alto Network VM-Series in AWS¶
In this document, we provide an example to set up the VM-Series for you to validate that packets are indeed sent to the VM-Series for VPC to VPC and from VPC to internet traffic inspection.
For using bootstrap method to setup the VM-Series, follow this document.
VM-Series in Azure can be setup using the guide Palo Alto Networks VM-Series Azure Example.
The Aviatrix Firewall Network (FireNet) workflow launches a VM-Series at Step 7a. After the launch is complete, the console displays the VM-Series instance with its public IP address of management interface and allows you to download the .pem file for SSH access to the instance.
Below are the steps for initial setup.
1. Download VM-Series Access Key¶
After Step 7a is completed, you’ll see the Download button as below. Click the button to download the .pem file.
If you get a download error, usually it means the VM-Series is not ready. Wait until it is ready, refresh the browser and then try again.
2. Reset VM-Series Password¶
For Metered AMI, open a terminal and run the following command.
Once you download the .pem file, change the file permission to 600. If you are asked to enter a password during the login, the VM-Series is still not ready. Wait and try again. It usually takes up to 15 minutes for the VM-Series to be ready. When the VM-Series is ready, you will not be asked for a password anymore.
ssh -i <private_key.pem> admin@<public-ip_address> configure set mgt-config users admin password commit
For BYOL, open a terminal and run the following command.
ssh -i <private_key.pem> admin@<public-ip_address> configure set mgt-config users admin password set deviceconfig system dns-setting servers primary <ip_address> commit
Terminate the SSH session.
3. Login to VM-Series¶
Go back to the Aviatrix Controller Console. Go to Firewall Network workflow, Step 7a. Click on the Management UI. It takes you the VM-Series you just launched.
Login with Username “admin”. Password is the password you set at the previous step.
4. Activate VM license¶
5. Dynamic updates¶
From Device > Dynamic Updates > Click on “Check Now” > download and then install latest versions of a. Applications and Threats b. Wildfire updates > Click on “Check Now” again > download and then install latest version of Antivirus
6. Configure VM-Series ethernet1/1 with WAN Zone¶
Once logged in, click on the Network tab and you should see a list of ethernet interfaces. Click ethernet1/1 and configure as the following screenshot.
- Click Network tab
- Click ethernet1/1
- Select “layer3” for Interface Type
- Click Config tab in the pop up Ethernet Interface window.
- Select default for Virtual Router at Config tab
- Click New Zone for Security Zone to create a WAN zone.
- At the next pop up screen, name the new zone “WAN” and click OK
- Select IPV4 tab in the pop up Ethernet Interface window.
- Select DHCP Client
- Uncheck “Automatically create default route pointing to default gateway provided by server, as shown below.
Click Commit. Once Commit is complete, you should see the Link State turn green at the Network page for ethernet1/1.
7. Configure VM-Series ethernet1/2 with LAN Zone¶
Repeat Step 6 for ethernet1/2. Name the new zone LAN.
Click Commit. Once Commit is complete, you should see the Link State turn green at the Network page for ethernet1/2.
If Keepalive via Firewall LAN Interface is enabled in Firewall Network > Advanced, ensure that ping is allowed in the Firewall LAN interface configuration: https://docs.aviatrix.com/HowTos/firewall_advanced.html?#keep-alive-via-firewall-lan-interface
8. Configure Allow Outbound Policies¶
Policies > Security > Click “Add” > Name the policy Outbound > Source tab, Select LAN zone > Destination tab. Select WAN zone > Click “OK”
9. Configure NAT for egress¶
If you would also like to enable NAT to test egress, follow these steps.
Policies > NAT > Click “Add” > Click General tab, give it a name > Click Original Packet. At Source Zone, click Add, select “LAN”. At Destination Zone, select WAN. At Destination Interface, select Ethernet1/1, as shown below.
11. Setup API access¶
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.
Follow the instructions here to enable API access.
12. Ready to go!¶
Now your firewall instance is ready to receive packets!
The next step is to specify which Security Domain needs packet inspection by defining a connection policy that connects to the firewall domain. This is done by Step 8 in the Firewall Network workflow.
For example, deploy Spoke-1 VPC in Security_Domain_1 and Spoke-2 VPC in Security_Domain_2. Build a connection policy between the two domains. Build a connection between Security_Domain_2 to Firewall Domain.
Launch one instance in Spoke-1 VPC and Spoke-2 VPC. From one instance, ping the other instance. The ping should go through.
13. 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 VPC to another Spoke VPC where one or both of Security Domains are connected to Firewall Network Security Domain