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= | ( Optional ) 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= | Host name for the firewall. |
panorama-server= | IPv4 or IPv6 address of the primary Panorama
server. This field is not required but recommended for centrally
managing your firewalls. |
panorama-server-2= | IPv4 or IPv6 address of the secondary Panorama
server. This field is not required but recommended. |
tplname= | Panorama template stack name. If you add a Panorama
server IP address, as a best practice assign the firewall to a template
stack on Panorama and enter the template stack name in this field
so that you can centrally manage and push configuration settings
to the firewall. |
dgname= | Panorama device group name. If you add a Panorama
server IP address, as a best practice create a device group on Panorama
and enter the device group name in this field so that you can group
the firewalls logically and push policy rules to the firewall. |
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 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 Cortex Data Lake 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. |