Parameters in the Auto Scaling Templates for Azure
Table of Contents
9.1 (EoL)
Expand all | Collapse all
-
- VM-Series Deployments
- VM-Series in High Availability
- 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
-
- VM-Series Firewall Licensing
- Create a Support Account
- Serial Number and CPU ID Format for the VM-Series Firewall
-
- Activate Credits
- Transfer Credits
- Create a Deployment Profile
- Manage a Deployment Profile
- Provision Panorama
- Migrate Panorama to a Software NGFW License
- Renew Your Software NGFW Credits
- Amend and Extend a Credit Pool
- Deactivate License (Software NGFW Credits)
- Delicense Ungracefully Terminated Firewalls
- Create and Apply a Subscription-Only Auth Code
- Migrate 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
- Use Panorama-Based Software Firewall License Management
- What Happens When Licenses Expire?
- Install a Device Certificate on the VM-Series Firewall
-
- 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
-
-
- VM-Series Firewall for NSX-V Deployment Checklist
- Install the VMware NSX Plugin
- Apply Security Policies to the VM-Series Firewall
- Steer Traffic from Guests that are not Running VMware Tools
- Add a New Host to Your NSX-V Deployment
- Dynamically Quarantine Infected Guests
- Migrate Operations-Centric Configuration to Security-Centric Configuration
- Use Case: Shared Compute Infrastructure and Shared Security Policies
- Use Case: Shared Security Policies on Dedicated Compute Infrastructure
- Dynamic Address Groups—Information Relay from NSX-V Manager to Panorama
-
- 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
- Extend Security Policy from NSX-V to NSX-T
- Use Migration Coordinator 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 Case: Secure the EC2 Instances in the AWS Cloud
- Use Case: Use Dynamic Address Groups to Secure New EC2 Instances within the VPC
-
-
- What Components Does the VM-Series Auto Scaling Template for AWS (v2.0) Leverage?
- How Does the VM-Series Auto Scaling Template for AWS (v2.0 and v2.1) Enable Dynamic Scaling?
- Plan the VM-Series Auto Scaling Template for AWS (v2.0 and v2.1)
- Customize the Firewall Template Before Launch (v2.0 and v2.1)
- Launch the VM-Series Auto Scaling Template for AWS (v2.0)
- SQS Messaging Between the Application Template and Firewall Template
- Stack Update with VM-Series Auto Scaling Template for AWS (v2.0)
- Modify Administrative Account and Update Stack (v2.0)
-
- Launch the Firewall Template (v2.1)
- Launch the Application Template (v2.1)
- Create a Custom Amazon Machine Image (v2.1)
- VM-Series Auto Scaling Template Cleanup (v2.1)
- SQS Messaging Between the Application Template and Firewall Template (v2.1)
- Stack Update with VM-Series Auto Scaling Template for AWS (v2.1)
- Modify Administrative Account (v2.1)
- Change Scaling Parameters and CloudWatch Metrics (v2.1)
-
-
- Enable the Use of a SCSI Controller
- Verify PCI-ID for Ordering of Network Interfaces on the VM-Series Firewall
-
- 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 Firewall on Azure Stack
- Enable Azure Application Insights on the VM-Series Firewall
- Set up Active/Passive HA on Azure
- 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 GCP
- Use Dynamic Address Groups to Secure Instances Within the VPC
- Locate VM-Series Firewall Images in the GCP Marketplace
-
- 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 Google Cloud Platform
- Verify Bootstrap Completion
- Bootstrap Errors
End-of-Life (EoL)
Parameters in the Auto Scaling Templates for Azure
What are the inputs in each template in the auto scaling
templates for the VM-Series on Azure?
This section describes the values you
need to provide as input when you deploy the template resources
that enable you to auto scale the VM-Series firewalls on Azure with
your application workloads.
Infrastructure Template Parameters
Inputs for the infrastructure template are as follows:
- Panorama Plugin Message Handler Name—The name of the Azure Function that will pass messages to the Panorama plugin for Azure. The Azure function URL will begin with this name.
- Storage Account Type—Select the type you want to use.
- Repo URL—The URL for the parent GitHub repository that hosts the templates. The location where Palo Alto Networks posts these templates is: https://github.com/PaloAltoNetworks/azure-autoscaling/tree/master/Version-1-0
- Branch—leave as is.
- Service Bus Name—The name of the Service Bus to which Panorama subscribes for notifications from Azure. The value must be between 6 and 50 characters long. This name has to be globally unique, must start and end with a letter or number, and can contain letters, numbers, and hyphens only.
Inbound Firewall Template Parameters
The inputs for the Inbound Firewall template vary depending
on whether you are starting from scratch and are using the template
for a greenfield deployment or you have an existing VNet with an
Azure Application Gateway and want to deploy the VM-Series firewalls
along with the associated subnets and internal load balancer for
the VMSS.
Inputs for the
Inbound Firewall template for a greenfield deployment are as follows:
- Resource Group Name and Location—Create a new Resource group and pick a location.
- App GatewayDns Name—A name for the Azure Application Gateway.
- Network Security Group Inbound Src IP: To restrict inbound access to the firewall management interface. CIDR format for example 199.16.5.122/32.
- Fw Load Balancer IP: Enter an IP address from the Untrust subnet CIDR to assign to the Azure load balancer that fronts the firewall VMSS. The Azure Application Gateway will use this IP address to send traffic onward to the firewall. For example: 192.168.1.4
- Deploy Into Existing Vnet—NoA new VNet with all the components listed in the Inbound firewall template are deployed for you. See Auto Scaling on Azure - Components and Planning Checklist.
- virtualNetworkName—The name of the VNet in which you want to deploy the resources in this template.
- virtualNetworkAddressPrefix—For example: 192.168.0.0/21
- mgmtSubnetPrefix—For example:192.168.0.0/24
- untrustSubnetPrefix—For example: 192.168.1.0/24
- trustSubnetPrefix—For example: 192.168.2.0/24
- appGatewaySubnetPrefix: For example: 192.168.3.0/24
- vmSeriesFirewallModel: BYOL or PAYG bundles
- vmSeriesImageVersion: Azure Auto Scale Template 1.0—8.1 or 9.0; Azure Auto Scale template 1.1—9.1.3. See the Panorama plugin version information in the Compatibility Matrix.If you choose PAN-OS 9.0, you must install the VM-Series plugin on Panorama. See Auto Scaling on Azure - Components and Planning Checklist for details.
- appInsightsRegion: Specify the region for your Application Insights Resource (Azure Auto Scale Template 1.1 and later). The default region iseast us.
- vmSeriesFirewallVmSize: Standard_D3_v2 (default). See VM instance types for minimum system requirements on the VM-Series firewall on Azure, and refer to Azure Virtual Machines for a list of instance types available for your region.
- Username—Enter a username for logging in to the firewall web interface.
- Authentication Type: password or SSH key
- Bootstrap Storage Account—Enter the Name of the storage account.
- Bootstrap Storage Account Access Key—Specify the storage account key.
- bootstrapFileShare—The name of the fileshare that holds the bootstrap folder structure.
- bootstrapSharedDir—This directory name is optional.
- VM Scale Set Min Count—Enter a value between 1 and 3. Default is 1
- VM Scale Set Max Count— Enter a value between 1 and 3. Default is 1.
- Auto Scale Metric—Active Sessions (default). To view all the supported metrics, see Custom PAN-OS Metrics Published for Monitoring.
- scaleInThreshold—Enter the threshold for a scaling event. This input can be a number or a percentage based on the scaling metric you selected above.
- scaleOutThreshold—Enter the threshold for a scaling event. This input can be a number or a percentage based on the scaling metric you selected above.
- Panorama Plugin Message Handler URL: This is the name for the Azure Function that entered in the infrastructure template. This URL allows the Service Bus queue and the Panorama plugin for Azure to send messages about your Azure resources. For example: https://test-asc-function-handler.azurewebsites.net/api/infra?code=IKDDx5U2HddsabcdE==
Inputs for the
Inbound Firewall template for a brownfield deployment are as follows:
- Resource Group Name and Location—Create a new Resource group and pick a location.
- App GatewayDns Name—Leave the default value. In a brownfield deployment, this template assumes that you have already deployed the Application Gateway, so this value is not relevant.
- Network Security Group Inbound Src IP: To restrict inbound access to the firewall management interface. CIDR format for example 199.16.5.122/32.
- Fw Load Balancer IP: Enter an IP address from the Untrust subnet CIDR to assign to the Azure load balancer that fronts the firewall VMSS. The Azure Application Gateway will use this IP address to send traffic onward to the firewall. For example: 192.168.1.4
- Deploy Into Existing Vnet— Yes
- virtualNetworkName—The name of the existing VNet in which you want to deploy the firewall VMSS resources.
- virtualNetworkAddressPrefix—For example: 192.168.0.0/21
- mgmtSubnetPrefix—For example:192.168.0.0/24
- untrustSubnetPrefix—For example: 192.168.1.0/24
- trustSubnetPrefix—For example: 192.168.2.0/24
- appGatewaySubnetPrefix: Enter the subnet in which your Application Gateway is deployed. For example: 192.168.3.0/24
- vmSeriesFirewallModel: BYOL or PAYG bundles
- vmSeriesImageVersion: Azure Auto Scale Template 1.0—8.1 or 9.0; Azure Auto Scale template 1.1—9.1.3. See the Panorama plugin version information in the Compatibility Matrix.If you choose PAN-OS 9.0, you must install the VM-Series plugin on Panorama. See Auto Scaling on Azure - Components and Planning Checklist for details.
- appInsightsRegion: Specify the region for your Application Insights Resource (Azure Auto Scale Template 1.1 and later). The default region iseast us.
- vmSeriesFirewallVmSize: Standard_D3_v2 (default). See VM instance types for minimum system requirements on the VM-Series firewall on Azure, and refer to Azure Virtual Machines for a list of instance types available for your region.
- Username—Enter a username for logging in to the firewall web interface.
- Authentication Type: password or SSH key
- Bootstrap Storage Account—Enter the Name of the storage account.
- Bootstrap Storage Account Access Key—Specify the storage account key.
- bootstrapFileShare—The name of the fileshare that holds the bootstrap folder structure.
- bootstrapSharedDir—This directory name is optional.
- VM Scale Set Min Count—Enter a value between 1 and 3. Default is 1
- VM Scale Set Max Count— Enter a value between 1 and 3. Default is 1.
- Auto Scale Metric—Active Sessions (default). To view all the supported metrics, see Custom PAN-OS Metrics Published for Monitoring.
- scaleInThreshold—Enter the threshold for a scaling event. This input can be a number or a percentage based on the scaling metric you selected above.
- scaleOutThreshold—Enter the threshold for a scaling event. This input can be a number or a percentage based on the scaling metric you selected above.
- Panorama Plugin Message Handler URL: This is the name for the Azure Function that entered in the infrastructure template. This URL allows the Service Bus queue and the Panorama plugin for Azure to send messages about your Azure resources. For example: https://test-asc-function-handler.azurewebsites.net/api/infra?code=IKDDx5U2HddsabcdE==
Hub Template Parameters
Inputs for the Hub firewall template that enables you
to secure outbound traffic and east-west traffic between the application
tiers are as follows:
- virtualNetworkName—The name of the VNet in which you want to deploy the resources in this template.
- virtualNetworkAddressPrefix—
- mgmtSubnetPrefix—
- untrustSubnetPrefix—
- trustSubnetPrefix—
- Load Balancer IP—Enter an IP address from the Trust subnet CIDR. The Load balancer will use this IP address to send traffic to the trust interface on the firewall.
- Network Security Group Inbound Src IP: To restrict inbound access to the firewall management interface. CIDR format, for example: 199.16.5.122/32.
- Bootstrap Storage Account—Enter the Name of the storage account.
- Bootstrap Storage Account Access Key—Specify the storage account key.
- bootstrapFileShare—The name of the fileshare that holds the bootstrap folder structure.
- bootstrapSharedDir—This directory name is optional.
- VM Scale Set Min Count—Enter a value between 1 and 3. Default is 1
- VM Scale Set Max Count— Enter a value between 1 and 3. Default is 1.
- Auto Scale Metric—Active Sessions (default). To view all the supported metrics, see Custom PAN-OS Metrics Published for Monitoring.
- scaleInThreshold—Enter the threshold for a scaling event. This input can be a number or a percentage based on the scaling metric you selected above.
- scaleOutThreshold—Enter the threshold for a scaling event. This input can be a number or a percentage based on the scaling metric you selected above.
- Panorama Plugin Message Handler URL: This is the name for the Azure Function that entered in the infrastructure template. This URL allows the Service Bus queue and the Panorama plugin for Azure to send messages about your Azure resources. For example: https://test-asc-function-handler.azurewebsites.net/api/infra?code=IKDDx5U2HddsabcdE==
- appInsightsRegion: Specify the region for your Application Insights Resource (Azure Auto Scale Template 1.1 and later). The default region iseast us.
Application Template Parameters
The inputs for the App template are:
- Connect to Hub: yes or no.
- Hub Resource Group Name—Required only if yes. The name of the Resource Group that hosts the resources you deployed with the Hub Firewall template.
- Hub VNET Name—Required only if yes. The name of the VNet that hosts the resources you deployed with the Hub Firewall template.
- Hub Load Balancer IP—Required only if yes. This is the IP address that you had assigned to the load balancer when you launched the Hub Firewall template.
- Application Load Balancer IP—Enter an IP address that belongs to the trust subnet. The application gateway that is in the Inbound Firewall Resource Group will use this IP address to send traffic to the firewall and then on to the application workloads.
- Inbound Firewall Resource Group Name—
- Inbound Firewall VNet Name—
- virtualNetworkAddressPrefix—The CIDR of the VNet in which you want to deploy the resources in this template.
- virtualNetworkName—The name of the VNet in which you want to deploy the resources in this template.
- mgmtSubnetPrefix—
- trustedSubnetPrefix—
- backendSubnetPrefix—The subnet in which your application workloads are deployed.
- username—To log in to the sample application server.
- password—The password for the administrative user you entered above.