Deploy the VM-Series with the Azure Gateway Load Balancer
Table of Contents
PAN.OS 11.1 & Later
Expand all | Collapse all
-
- VM-Series Deployments
- VM-Series in High Availability
- IPv6 Support on Public Cloud
- Enable Jumbo Frames on the VM-Series Firewall
- Hypervisor Assigned MAC Addresses
- Custom PAN-OS Metrics Published for Monitoring
- Interface Used for Accessing External Services on the VM-Series Firewall
- PacketMMAP and DPDK Driver Support
- Enable NUMA Performance Optimization on the VM-Series
- Enable ZRAM on the VM-Series Firewall
-
- Licensing and Prerequisites for Virtual Systems Support on VM-Series
- System Requirements for Virtual Systems Support on VM-Series
- Enable Multiple Virtual Systems Support on VM-Series Firewall
- Enable Multiple Virtual Systems Support on VM-Series in Panorama Console
- Enable Multiple Virtual Systems Support Using Bootstrap Method
-
- VM-Series Firewall Licensing
- Create a Support Account
- Serial Number and CPU ID Format for the VM-Series Firewall
- Use Panorama-Based Software Firewall License Management
-
- Activate Credits
- Create a Deployment Profile
- Activate the Deployment Profile
- Manage a Deployment Profile
- Register the VM-Series Firewall (Software NGFW Credits)
- Provision Panorama
- Migrate Panorama to a Software NGFW License
- Transfer Credits
- Renew Your Software NGFW Credits
- Deactivate License (Software NGFW Credits)
- Delicense Ungracefully Terminated Firewalls
- Set the Number of Licensed vCPUs
- Customize Dataplane Cores
- Migrate a Firewall to a Flexible VM-Series License
-
- Generate Your OAuth Client Credentials
- Manage Deployment Profiles Using the Licensing API
- Create a Deployment Profile Using the Licensing API
- Update a Deployment Profile Using the Licensing API
- Get Serial Numbers Associated with an Authcode Using the API
- Deactivate a VM-Series Firewall Using the API
- What Happens When Licenses Expire?
-
- Supported Deployments on VMware vSphere Hypervisor (ESXi)
-
- Plan the Interfaces for the VM-Series for ESXi
- Provision the VM-Series Firewall on an ESXi Server
- Perform Initial Configuration on the VM-Series on ESXi
- Add Additional Disk Space to the VM-Series Firewall
- Use VMware Tools on the VM-Series Firewall on ESXi and vCloud Air
- Use vMotion to Move the VM-Series Firewall Between Hosts
- Use the VM-Series CLI to Swap the Management Interface on ESXi
- Configure Link Aggregation Control Protocol
-
-
- Supported Deployments of the VM-Series Firewall on VMware NSX-T (North-South)
- Components of the VM-Series Firewall on NSX-T (North-South)
-
- Install the Panorama Plugin for VMware NSX
- Enable Communication Between NSX-T Manager and Panorama
- Create Template Stacks and Device Groups on Panorama
- Configure the Service Definition on Panorama
- Deploy the VM-Series Firewall
- Direct Traffic to the VM-Series Firewall
- Apply Security Policy to the VM-Series Firewall on NSX-T
- Use vMotion to Move the VM-Series Firewall Between Hosts
- Extend Security Policy from NSX-V to NSX-T
-
- Components of the VM-Series Firewall on NSX-T (East-West)
- VM-Series Firewall on NSX-T (East-West) Integration
- Supported Deployments of the VM-Series Firewall on VMware NSX-T (East-West)
-
- Install the Panorama Plugin for VMware NSX
- Enable Communication Between NSX-T Manager and Panorama
- Create Template Stacks and Device Groups on Panorama
- Configure the Service Definition on Panorama
- Launch the VM-Series Firewall on NSX-T (East-West)
- Add a Service Chain
- Direct Traffic to the VM-Series Firewall
- Apply Security Policies to the VM-Series Firewall on NSX-T (East-West)
- Use vMotion to Move the VM-Series Firewall Between Hosts
-
- Install the Panorama Plugin for VMware NSX
- Enable Communication Between NSX-T Manager and Panorama
- Create Template Stacks and Device Groups on Panorama
- Configure the Service Definition on Panorama
- Launch the VM-Series Firewall on NSX-T (East-West)
- Create Dynamic Address Groups
- Create Dynamic Address Group Membership Criteria
- Generate Steering Policy
- Generate Steering Rules
- Delete a Service Definition from Panorama
- Migrate from VM-Series on NSX-T Operation to Security Centric Deployment
- Extend Security Policy from NSX-V to NSX-T
- Use In-Place Migration to Move Your VM-Series from NSX-V to NSX-T
-
-
- Deployments Supported on AWS
-
- Planning Worksheet for the VM-Series in the AWS VPC
- Launch the VM-Series Firewall on AWS
- Launch the VM-Series Firewall on AWS Outpost
- Create a Custom Amazon Machine Image (AMI)
- Encrypt EBS Volume for the VM-Series Firewall on AWS
- Use the VM-Series Firewall CLI to Swap the Management Interface
- Enable CloudWatch Monitoring on the VM-Series Firewall
- VM-Series Firewall Startup and Health Logs on AWS
- Use AWS Secrets Manager to Store VM-Series Certificates
- Use Case: Secure the EC2 Instances in the AWS Cloud
- Use Case: Use Dynamic Address Groups to Secure New EC2 Instances within the VPC
-
- Intelligent Traffic Offload
- Software Cut-through Based Offload
-
- Deployments Supported on Azure
- Deploy the VM-Series Firewall from the Azure Marketplace (Solution Template)
- Deploy the VM-Series Firewall from the Azure China Marketplace (Solution Template)
- Deploy the VM-Series with the Azure Gateway Load Balancer
- Create a Custom VM-Series Image for Azure
- Deploy the VM-Series Firewall on Azure Stack
- Deploy the VM-Series Firewall on Azure Stack HCI
- Enable Azure Application Insights on the VM-Series Firewall
- Set up Active/Passive HA on Azure
- Use Azure Key Vault to Store VM-Series Certificates
- Use the ARM Template to Deploy the VM-Series Firewall
-
- About the VM-Series Firewall on Google Cloud Platform
- Supported Deployments on Google Cloud Platform
- Create a Custom VM-Series Firewall Image for Google Cloud Platform
- Prepare to Set Up VM-Series Firewalls on Google Public Cloud
-
- Deploy the VM-Series Firewall from Google Cloud Platform Marketplace
- Management Interface Swap for Google Cloud Platform Load Balancing
- Use the VM-Series Firewall CLI to Swap the Management Interface
- Enable Google Stackdriver Monitoring on the VM Series Firewall
- Enable VM Monitoring to Track VM Changes on Google Cloud Platform (GCP)
- Use Dynamic Address Groups to Secure Instances Within the VPC
- Use Custom Templates or the gcloud CLI to Deploy the VM-Series Firewall
- Enable Session Resiliency on VM-Series for GCP
-
- Prepare Your ACI Environment for Integration
-
-
- Create a Virtual Router and Security Zone
- Configure the Network Interfaces
- Configure a Static Default Route
- Create Address Objects for the EPGs
- Create Security Policy Rules
- Create a VLAN Pool and Domain
- Configure an Interface Policy for LLDP and LACP for East-West Traffic
- Establish the Connection Between the Firewall and ACI Fabric
- Create a VRF and Bridge Domain
- Create an L4-L7 Device
- Create a Policy-Based Redirect
- Create and Apply a Service Graph Template
-
- Create a VLAN Pool and External Routed Domain
- Configure an Interface Policy for LLDP and LACP for North-South Traffic
- Create an External Routed Network
- Configure Subnets to Advertise to the External Firewall
- Create an Outbound Contract
- Create an Inbound Web Contract
- Apply Outbound and Inbound Contracts to the EPGs
- Create a Virtual Router and Security Zone for North-South Traffic
- Configure the Network Interfaces
- Configure Route Redistribution and OSPF
- Configure NAT for External Connections
-
-
- Choose a Bootstrap Method
- VM-Series Firewall Bootstrap Workflow
- Bootstrap Package
- Bootstrap Configuration Files
- Generate the VM Auth Key on Panorama
- Create the bootstrap.xml File
- Prepare the Licenses for Bootstrapping
- Prepare the Bootstrap Package
- Bootstrap the VM-Series Firewall on AWS
- Bootstrap the VM-Series Firewall on Azure
- Bootstrap the VM-Series Firewall on Azure Stack HCI
- Bootstrap the VM-Series Firewall on Google Cloud Platform
- Verify Bootstrap Completion
- Bootstrap Errors
Deploy the VM-Series with the Azure Gateway Load Balancer
You can now deploy the VM-Series firewall for Azure in integration with the Azure
gateway load balancer (GWLB). Securing inbound traffic requires complete visibility
of the traffic source’s identity as it travels to its destination in the cloud. When
VM-Series firewalls are deployed behind a public standard load balancer, the source
IP addresses of inbound traffic are replaced with the IP address of the load
balancer. As a result, application source identity is obfuscated. By deploying the
VM-Series firewalls behind the Azure GWLB, traffic packet headers and payload are
kept intact, which provides complete visibility of the source’s identity as it
travels to its destination. When Azure GWLB integration is enabled, the VM-Series
uses VXLAN packets to inspect the inner packet of traffic and apply policy to that
packet.
When deployed behind the Azure GWLB, VM-Series firewalls can enforce zone-based
security policy. You can segment VNet-bound and Internet bound traffic by assigning
a trust zone to the VNet-bound traffic and untrust-zone for the Internet bound
traffic.
With this integration, you can deploy the VM-Series firewall as a backend to the
Azure GWLB in all supported regions.
VM-Series firewall integration with the Azure GWLB requires PAN-OS 10.1.4 or
later and VM-Series Plugin 2.1.4 or later.
Follow best practices to not overlap the CIDRs used by
different VNets.
- Deploy the VM-Series firewall behind Azure GWLB using the ARM template.(Optional) Add additional VM-Series firewall instances behind GWLB deployed in Step 1.
- Create a VM using the Microsoft Azure CLI.Provide the input parameters in the sample command below.az vm create \ --resource-group <myResourceGroup> \ --name <myPA-VM> \ --vnet-name secVnet \ --subnet Subnet-mgmt \ --public-ip-sku Standard \ --size Standard_DS3_V2 \ --nsg networkSecurityGroup1 \ --admin-username <username> \ --admin-password <password> \ --image paloaltonetworks:vmseries-flex:bundle1:10.1.4 \ --plan-name bundle1 \ --plan-product vmseries-flex \ --plan-publisher paloaltonetworks \ --custom-data "storage-account=<myStorageAccountName>,access-key=<myAccessKey>,file-share=<FileName>,share-directory=<SharedDirectoryName>"The init-cfg.txt file is required to bootstrap the VM-Series firewall. It provides the basic information the firewall needs to connect to your network. The init-cfg.txt file in the bootstrap folder includes the following information.
- To deploy the solution with default
ports:plugin-op-commands=azure-gwlb-inspect:enable
- To deploy the solution with custom ports, use the sample command in the init-cfg.txt file if custom data field is used to define the VNI IDs and port information. You must define the internal and external VNI identifiers in the range of 800 to 1000.
plugin-op-commands=azure-gwlb-inspect:enable+internal-port-<internalport>+external-port-<externalport>+internal-vni-<internalvni>+external-vni-<internalvni>If you choose to use custom ports, use these sample commands to configure the GWLB.az network lb address-pool tunnel-interface add --resource-group <myResourceGroup> --lb-name <myGatewayLoadBalancer> --address-pool <myBackendPool> --type external --protocol vxlan --identifier <VNI> --port <port> az network lb address-pool tunnel-interface add --resource-group <myResourceGroup> --lb-name <myGatewayLoadBalancer> --address-pool <myBackendPool> --type internal --protocol vxlan --identifier <VNI> --port <port>For more information, see Custom data and Cloud-init on Azure Virtual Machines. - To deploy the solution with custom ports, use the sample command in the init-cfg.txt file if custom data field is used to define the VNI IDs and port information. You must define the internal and external VNI identifiers in the range of 800 to 1000.
Create NIC in the data subnet.az network nic create -g <myResourceGroup> --vnet-name secVnet --subnet Subnet-data -n <myDataNIC> --accelerated-networking true --ip-forwarding trueStop the VM created in Step 1.az vm deallocate -n <myPA-VM> -g <myResourceGroup>Add the NIC created in Step 2 to the VM.az vm nic add -g <myResourceGroup> --vm-name <myPA-VM> --nics <myDataNIC>Add the VM to the backend address pool of the GWLB.az network nic ip-config address-pool add --address-pool BackendPool1 --ip-config-name ipconfig1 --nic-name <myDataNIC> --resource-group <myResourceGroup> --lb-name securityLBStart the VM.az vm start -n <myPA-VM> -g <myResourceGroup>Connect to the firewall using SSH. Enter the following in the firewall CLI to verify if the GWLB is enabled.show plugins vm_series azure gwlb(Optional) If you do not bootstrap the firewall, the user data is used to configure the ports and VNI IDs. Use the following sample commands on the firewall CLI to enable or disable GWLB, configure custom ports and VNI IDs, and view GWLB status and port/VNI ID mapping.The port numbers and VNI IDs must match with the ones in the GWLB backend address pool.request plugins vm_series azure gwlb inspect enable yes request plugins vm_series azure gwlb parameters internal-port 2000 external-port 2001 internal-vni 800 external-vni 801 show plugins vm_series azure gwlbSample output:GWLB enabled : True Internal Tunnel Port: 2000 Internal Tunnel VNI: 800 External Tunnel Port: 2001 External Tunnel VNI: 801(Manual bootstrap configuration) If you did not bootstrap the VM-Series firewall with GWLB in Step1 or Steps 2.1 to 2.7, perform the following manual processes.- Manually configure the dataplane network interfaces as Layer 3
interfaces on the firewall.
- On the VM-Series firewall web interface, select NetworkInterfacesEthernet.
- Click ethernet 1/1 and configure as
follows:
- Set Interface Type to Layer3 (default).
- On the Config tab, assign the interface to a virtual router.
- Also on the Config tab, expand the Security Zone drop-down and select New Zone. Define an internal and external zone, then click OK.
- On the IPv4 tab, select DHCP Client.
- Disable the Automatically create default route to default gateway provided by server to ensure that traffic handled by this interface does not flow directly to the default gateway in the VNet.
- On the Advanced tab, create a management profile to allow health checks to be received by the firewall.
- Commit your changes and verify that the link state for the interfaces is up.
- Create a static route on the VM-Series firewall.
- On the VM-Series firewall web interface, select NetworkVirtual Routers and select the virtual router associated with the data interface.
- Select Static Routes and click Add.
- Configure the static route.
- Click OK.
- Commit your changes.
- Create two subinterfaces under eth1/1 to enforce zone-based security
policies.
- On the VM-Series firewall web interface, select NetworkInterface.
- Highlight ethernet1/1 and click Add Subinterface.
- Enter a numerical suffix (1 to 9,999) to identify the subinterface.
- Enter a VLAN Tag for the subinterface.
This field is required but the VLAN is not used.VNI ID/Port for the internal tunnel is mapped to the VLAN 1 tag and external tunnel is mapped to the VLAN 2 tag. The VLAN 1 tag and VLAN 2 tag must always be mapped to the internal (trust) zone and external (untrust) zone respectively.
- Select the Virtual Router associated with the data interface.
- Select a Security Zone.
- On the IPv4 tab, set the Type to DHCP Client.
- Click OK.
- Repeat this command for the second subinterface.
- Commit your changes.
- To deploy the solution with default
ports: