init-cfg.txt File Components
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
init-cfg.txt File Components
The following table describes the bootstrap parameters
in the init-cfg.txt file.
Field | Description |
|---|---|
type= | Type of management IP address: static or
dhcp-client. This field is required. |
ip-address= | IPv4 address. This field is ignored if the
type is dhcp-client. If the type is static, an IPv4 address is required;
the ipv6-address field is optional and can be included. You
cannot specify the management IP address and netmask configuration
for the VM-Series firewall in AWS and Azure. If defined, the firewall
ignores the values you specify. |
default-gateway= | IPv4 default gateway for the management
interface. This field is ignored if the type is dhcp-client. If
the type is static, and ip-address is used, this field is required. |
netmask= | IPv4 netmask. This field is ignored if the
type is dhcp-client. If the type is static, and ip-address is used,
this field is required. |
ipv6-address= | IPv6 address and /prefix length of the management interface. This field is ignored if the type is
dhcp-client. If the type is static, this field can be specified
along with the ip-address field, which is required. |
ipv6-default-gateway= | IPv6 default gateway for the management
interface. This field is ignored if the type is dhcp-client. If
the type is static and ipv6-address is used, this field is required. |
hostname= | Hostname for the firewall. This field is required when adding Panorama configuration
parameters. |
panorama-server= | IPv4 or IPv6 address of the primary Panorama
server. This field is not required but recommended for centrally
managing your firewalls.
When creating a bootstrap package, set
panorama-server=cloud. The cloud
parameter should be used when connecting the firewall to Strata
Cloud Manager.
When you provide a Panorama IP address in
your init-cfg.txt file, Panorama pushes configuration to firewall
automatically upon first connection. |
panorama-server-2= | IPv4 or IPv6 address of the secondary Panorama
server. This field is not required but recommended.
A value defined for panorama-server-2 is
ignored when panorama-server=cloud is used. |
tplname= | Panorama template stack name. If
you add a Panorama server IP address, you must include a template
stack name in this field so that you can centrally manage and push
configuration settings to the firewall. If you do not include a
template stack name, the firewalls connection to Panorama fails. |
dgname= | Panorama device group name. If you
add a Panorama server IP address, you must include a device group
name in this field so that you can group the firewalls logically and
push policy rules to the firewall. If you do not include a device
group name, the firewalls connection to Panorama fails. |
cgname= | Panorama collector group name.
If you want to bootstrap the firewall to send logs to a Panorama
collector group, you must first configure a collector group on Panorama
and then configure the firewall to forward logs to Panorama. On
the M-Series appliances, a default Collector Group is predefined
and already contains the local Log Collector as a member. On the
Panorama virtual appliance, you must add the Collector Group and
add the local Log Collector as a member. |
dns-primary= | IPv4 or IPv6 address of the primary DNS
server. |
dns-secondary= | IPv4 or IPv6 address of the secondary DNS
server. |
vm-auth-key= | Virtual machine authentication key for Panorama
(see Generate the VM Auth Key on Panorama). This field
is ignored when bootstrapping hardware firewalls. |
op-command-modes= | The following values are allowed: multi-vsys,
jumbo-frame, mgmt-interface-swap. If you enter multiple values,
use a space or a comma to separate the entries.
|
op-cmd-dpdk-pkt-io= | The value on or off allows you to enable or disable Data Plane Development Kit (DPDK) in environments where the firewall supports DPDK. DPDK allows the host to process packets faster by bypassing the Linux kernel; interactions with the NIC are performed using drivers and the DPDK libraries. |
| plugin-op-commands= | Specify VM-Series plugin operation commands. Multiple
commands must be entered on a single, comma separated list with
no spaces.
|
dhcp-send-hostname= | The value of yes or no comes from the DHCP
server. If yes, the firewall will send its hostname to the DHCP
server. This field is relevant only if type is dhcp-client. |
dhcp-send-client-id= | The value of yes or no comes from the DHCP
server. If yes, the firewall will send its client ID to the DHCP
server. This field is relevant only if type is dhcp-client. |
dhcp-accept-server-hostname= | The value of yes or no comes from the DHCP
server. If yes, the firewall will accept its hostname from the DHCP
server. This field is relevant only if type is dhcp-client. |
dhcp-accept-server-domain= | The value of yes or no comes from the DHCP
server. If yes, the firewall will accept its DNS server from the
DHCP server. This field is relevant only if type is dhcp-client. |
vm-series-auto-registration-pin-id and vm-series-auto-registration-pin-value | The VM-Series registration PIN ID and value for installing the device certificate on the
VM-Series firewall. The PIN ID and value also enable you to
automatically activate the site licenses for AutoFocus and Strata
Logging Service on PAYG instances of the firewall. You must generate this in registration PIN
ID and value on the Palo Alto Networks CSP.
See Install a Device Certificate on the VM-Series Firewall for information
on generating PIN ID and value. |
|
redis-endpoint=
|
Provide the IP address or FQDN and port of your Redis endpoint. For
use with session resiliency in the VM-Series for AWS and GCP.
|
|
redis-auth=
| Optional The auth code your VM-Series firewall uses to connect with the Redis endpoint. For use with session resiliency in the VM-Series for AWS and GCP. |
|
redis-certificate=
| Optional The root CA certificate string used to connect to the Redis endpoint. The certificate must be a base64-encoded string using utf-8 encoding. For use with session resiliency in the VM-Series for GCP; not required for session resiliency on AWS. |