: Device > Setup > Interfaces
Focus
Focus

Device > Setup > Interfaces

Table of Contents
End-of-Life (EoL)

Device > Setup > Interfaces

Use this page to configure connection settings, allowed services, and administrative access for the management (MGT) interface on all firewall models and for the auxiliary interfaces (AUX-1 and AUX-2) on PA-5200 Series firewalls.
Palo Alto Networks recommends that you always specify the IP address and netmask (for IPv4) or prefix length (for IPv6) and the default gateway for every interface. If you omit any of these settings for the MGT interface (such as the default gateway), you can access the firewall only through the console port for future configuration changes.
To configure the MGT interface on the M-500 appliance or the Panorama virtual appliance, see Panorama > Setup > Interfaces.
You can use a loopback interface as an alternative to the MGT interface for firewall management (Network > Interfaces > Loopback).
Item
Description
Type
(
MGT interface only
)
Select one:
  • Static
    —Requires you to manually enter the IPv4 or IPv6 address (or both) and default gateway(s), which are described further down in this table.
  • DHCP Client
    —Configures the MGT interface as a DHCP client so that the firewall can send DHCP Discover or Request messages to find a DHCP server. The server responds by providing an IP address (IPv4), netmask (IPv4), and default gateway for the MGT interface. DHCP on the MGT interface is turned off by default for the VM-Series firewall (except for the VM-Series firewall in AWS and Azure).If you select
    DHCP Client
    , optionally select either or both of the following Client Options:
    • Send Hostname
      —Causes the MGT interface to send its hostname to the DHCP server as part of DHCP Option 12.
    • Send Client ID
      —Causes the MGT interface to send its client identifier as part of DHCP Option 61.
If you select
DHCP Client
, optionally click
Show DHCP Client Runtime Info
to view the dynamic IP interface status:
  • Interface—Indicates MGT interface.
  • IP Address—IP address of the MGT interface.
  • Netmask—Subnet mask for the IP address, which indicates which bits are network or subnetwork and which bits are host.
  • Gateway—Default gateway for traffic leaving the MGT interface.
  • Primary/Secondary NTP—IP address of up to two NTP servers serving the MGT interface. If the DHCP Server returns NTP server addresses, the firewall considers them only if you did not manually configure NTP server addresses. If you manually configured NTP server addresses, the firewall does not overwrite them with those from the DHCP server.
  • Lease Time—Number of days, hours, minutes, and seconds that the DHCP IP address is assigned.
  • Expiry Time—Year/Month/Day, Hours/Minutes/Seconds, and time zone, indicating when DHCP lease will expire.
  • DHCP Server—IP address of the DHCP Server responding to MGT interface DHCP Client.
  • Domain—Name of domain to which the MGT interface belongs.
  • DNS Server—IP address of up to two DNS servers serving the MGT interface. If the DHCP Server returns DNS server addresses, the firewall considers them only if you did not manually configure DNS server addresses. If you manually configured DNS server addresses, the firewall does not overwrite them with those from the DHCP server.
Optionally, you can
Renew
the DHCP lease for the IP address assigned to the MGT interface. Otherwise,
Close
the window.
Aux 1 / Aux 2
(
PA-5200 Series firewalls only
)
Select any of the following options to enable an auxiliary interface. These interfaces provide 10Gbps (SFP+) throughput for:
  • Firewall management traffic—You must enable the Network Services (protocols) that administrators will use when accessing the web interface and CLI to manage the firewall.
Enable HTTPS instead of HTTP for the web interface and enable SSH instead of Telnet for the CLI.
  • High availability (HA) synchronization between firewall peers—After configuring the interface, you must select it as the HA Control Link (
    Device
    High Availability
    General
    ).
  • Log forwarding to Panorama—You must configure a service route with the
    Panorama Log Forwarding
    service enabled (Device > Setup > Services).
IP Address (IPv4)
If your network uses IPv4, assign an IPv4 address to the interface. Alternatively, you can assign the IP address of a loopback interface for firewall management (see Network > Interfaces > Loopback). By default, the IP address you enter is the source address for log forwarding.
Netmask (IPv4)
If you assigned an IPv4 address to the interface, you must also enter a network mask (for example, 255.255.255.0).
Default Gateway
If you assigned an IPv4 address to the interface, you must also assign an IPv4 address to the default gateway (the gateway must be on the same subnet as the interface).
IPv6 Address/Prefix Length
If your network uses IPv6, assign an IPv6 address to the interface. To indicate the netmask, enter an IPv6 prefix length (for example, 2001:db8:300::1/64).
Default IPv6 Gateway
If you assigned an IPv6 address to the interface, you must also assign an IPv6 address to the default gateway (the gateway must be on the same subnet as the interface); for example, 2001:db8:300::5.
Speed
Configure a data rate and duplex option for the interface. The choices include 10Mbps, 100Mbps, and 1Gbps at full or half duplex. Use the default auto-negotiate setting to have the firewall determine the interface speed.
This setting must match the port settings on the neighboring network equipment. To ensure matching settings, select auto-negotiate if the neighboring equipment supports that option.
MTU
Enter the maximum transmission unit (MTU) in bytes for packets sent on this interface (range is 576 to 1,500; default is 1,500).
Administrative Management Services
  • HTTP
    —Use this service to access the firewall web interface.
    HTTP uses plaintext, which is not as secure as HTTPS. Therefore, Palo Alto Networks recommend you enable
    HTTPS
    instead of HTTP for management traffic on the interface.
  • Telnet
    —Use this service to access the firewall CLI.
    Telnet uses plaintext, which is not as secure as SSH. Therefore, Palo Alto Networks recommend you enable SSH instead of Telnet for management traffic on the interface.
  • HTTPS
    —Use this service for secure access to the firewall web interface.
  • SSH
    —Use this service for secure access to the firewall CLI.
Network Services
Select the services you want to enable on the interface:
  • Ping
    —Use this service to test connectivity with external services. For example, you can ping the interface to verify it can receive PAN-OS software and content updates from the Palo Alto Networks Update Server. In a high availability (HA) deployment, HA peers use ping to exchange heartbeat backup information.
  • SNMP
    —Use this service to process firewall statistics queries from an SNMP manager. For details, see Enable SNMP Monitoring.
  • User-ID
    —Use this service to enable Redistribution of user mappings among firewalls.
  • User-ID Syslog Listener-SSL
    —Use this service to enable the PAN-OS integrated User-ID™ agent to collect syslog messages over SSL. For details, see Configure Access to Monitored Servers.
  • User-ID Syslog Listener-UDP
    —Use this service to enable the PAN-OS integrated User-ID agent to collect syslog messages over UDP. For details, see Configure Access to Monitored Servers.
Permitted IP Addresses
Enter the IP addresses from which administrators can access the firewall through the interface. An empty list (default) specifies that access is available from any IP address.
Do not leave the list blank; specify only the IP addresses of firewall administrators to prevent unauthorized access.

Recommended For You