Example Config for Palo Alto Networks VM-Series in Azure¶
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 VNET to VNET and from VNET to internet traffic inspection.
Please follow the below steps to launch and configure Palo Alto Networks VM-Series in Azure.
If you are looking to deploy VM-Series in AWS environment, your starting point is here.
1. Launch Palo Alto Networks Firewall from Aviatrix Controller¶
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.
Go to Aviatrix Controller’s console, Firewall Network -> Setup -> Step 7a. Here is the VM-Series information in this example for your reference. Please adjust it depending on your requirements.
|Example setting||Example value|
|VPC ID||Select VPC (e.g. TR-Firenet-VNET)|
|Gateway Name||Select correct Transit FireNet Gateway|
|Firewall Instance Name||Give any Good Name (e.g. PAN-Azure-Firenet)|
|Firewall Image||Palo Alto Networks VM-Series Next-Generation Firewall Bundle 1|
|Firewall Image Version||9.1.0|
|Firewall Instance Size||Standard_D3_v2|
|Management Interface Subnet||Select the subnet whose name contains “Public-gateway-and-firewall-mgmt”.|
|Egress Interface Subnet||Select the subnet whose name contains “Public-FW-ingress-egress”.|
|Username||Any Good Name (e.g. panadmin)|
|Authentication Method||Password or SSH Public Key|
|Password||Input a good password of your choice|
Palo Alto Networks VM-Series instance has 3 interfaces as described below.
|Palo Alto VM interfaces||Description||Inbound Security Group Rule|
|eth0 (on subnet -Public-gateway-and-firewall-mgmt)||Management interface||Allow SSH, HTTPS, ICMP, TCP 3978|
|eth1 (on subnet -Public-FW-ingress-egress)||Egress or Untrusted interface||Allow ALL|
|eth2 (on subnet -dmz-firewall_lan)||LAN or Trusted interface||Allow ALL (Do not change)|
Note that firewall instance eth2 is on the same subnet as FireNet gateway eth2 interface.
2. Vendor Firewall Integration¶
This step automatically configures the RFC 1918 and non-RFC 1918 routes between Aviatrix Gateway and Vendor’s firewall instance in this case Palo Alto Networks VM-Series. This can also be done manually through Cloud Portal and/or Vendor’s Management tool.
- Go to Firewall Network -> Vendor Integration -> Select Firewall, fill in the details of your Firewall instance.
- Click Save, Show and Sync.
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 “panadmin”. Password is the password you set at the previous step.
4. Activate VM license¶
5. Dynamic updates¶
Go to Device > Dynamic Updates > Click on “Check Now”
- Download and Install latest versions of Applications and Threats.
- 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.
8. Enable VM-Series Health Check Policy¶
By default, VM-Series do not allow HTTPS or TCP 443 port. Pleas follow the given steps to enable it:
- Go to Network -> Interface Mgmt under Network Profiles and click “Add”.
- Give any name in “Interface Management Profile”, check HTTPS checkbox under Administrative Management Service and click “OK”.
- Attach Profile with LAN interface. Network -> Interfaces -> Select LAN Ethernet Interface -> Advanced -> Management Profile -> Select appropiate profile.
See an example screenshot below how to attach profile to an interface.
Firewall health check probes can be verified in Monitor -> Traffic.
9. Configure basic traffic policy to allow traffic VNET to VNET¶
In this step, we will configure a basic traffic security policy that allows traffic to pass through the VM-Series firewall.
- Click Policies tab.
- Click +Add at the bottom left corner to create a new policy.
- Click General tab. Name the policy Allow-all.
- Click Source tab. Select Any for both panels.
- Click Destination tab. Select Any for both panels.
- Click Application tab. Select Any
- Click OK
- Click Commit to commit the Allow-all policy.
10. [Optional] Configure basic traffic policy to allow traffic VNET to Internet¶
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. 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.).
12. View Traffic Log¶
You can view if traffic is forwarded to the firewall instance by logging in to the VM-Series console. Go to Monitor –> Traffic.
VNET to VNET traffic:¶
Launch one instance in Spoke VNET-1 and one in Spoke VNET-2. Start ping packets from a instance in Soke VNET-1 to the private IP of another instance in Spoke VNET-2. The ICMP traffic should go through the firewall and can be inspected in firewall.
[Optional] For VNET to Internet traffic:¶
Similarly, VNET to internet traffic can be also inspected by launching a private instance in the Spoke VNET and start ping packets from the private instance towards Internet (e.g 220.127.116.11) to verify the egress function.
The Egress Inspection is only applicable to all VNets that deploys non public facing applications. If you have any Spoke VNet that has public facing web services, you should not enable Egress Inspection. This is because Egress Inspection inserts a default route (0.0.0.0/0) towards Transit GW to send the Internet traffic towards firewall to get inspected. Azure’s System Default Route pointing towards Internet will be overwritten by User-defined default route inserted by the Controller.