End-of-Life (EoL)
In cloud and multi-tenant service provider environments, one goal is to automatically deploy and provision firewalls without manually assigning an IP address to the management interface. The management interface on the firewall now supports the option to enable a DHCP client for IPv4 so that the management interface can receive its IPv4 address from a DHCP server. The management interface also supports DHCP Option 12 and Option 61; these options allow the firewall to send its host name and client identifier, respectively, to DHCP servers.
DHCP client functionality on the management interface is enabled by default on VM-Series firewalls in the AWS and Azure public cloud deployments and on VMware NSX edition firewalls. VM-Series firewalls in these environments require this automation and must use the management interface as a DHCP client to obtain the IP address (instead of using a static IP address). For VM-Series firewalls on all other hypervisors and on all hardware-based firewalls, DHCP client functionality on the management interface is disabled by default. You can enable the DHCP client using the web interface or the CLI on the firewall, or as a part of the process to Bootstrap the Firewall.
WildFire and Panorama do not support DHCP on the management interface—you must assign a static IP address, instead.
Configure the Management Interface as a DHCP Client
Configure the Management interface as a DHCP client. The Management interface can receive its IPv4 address, netmask, and default gateway from the DHCP server. Additionally, you have the option to configure your firewall to receive its hostname and domain from the server. You can also send the hostname and client identifier of the firewall to the server if the orchestration system you use accepts this information.

Recommended For You