Configure service routes to change the interface the firewall uses to send requests
to external services or for log forwarding.
| Where Can I Use This? | What Do I Need? |
|
|
One of these licenses for Strata Cloud Manager managed NGFWs:
- Strata Cloud Manager Essentials
- Strata Cloud Manager Pro
|
The firewall uses the management (MGT) interface by default to access
external services, such as DNS servers, external authentication servers, Palo Alto
Networks
® services such as software, URL updates, licenses and
AutoFocus. An alternative to using the MGT interface is to configure a data port (a
regular interface) to access these services. The path from the interface to the
service on a server is known as a
service route. For example, you can
configure a service route for Panorama log forwarding exclusively on PA-5200
platforms to explicitly control the data port and source IP for forwarding logs to
Panorama.
The service packets exit the firewall on the port assigned for the
external service and the server sends its response to the configured source
interface and source IP address.
You can configure service routes globally for the firewall or
customize service routes for a virtual
system on a firewall enabled for multiple virtual systems so that you
have the flexibility to use interfaces associated with a virtual system. Any virtual
system that does not have a service route configured for a particular service
inherits the interface and IP address that are set globally for that service.
The following procedure enables you to configure service routes to change the
interface that the firewall uses to send requests to external services such as the
Palo Alto Network cloud services or for log forwarding. For firewalls in a
high availability (HA) configuration, the
service route configuration is synchronized across the HA peers
For firewalls in an
active/passive high availability (HA), the
service route you configured to leverage an external service or for log forwarding
sees activity only on the
active HA peer while the
passive HA peer sees no activity if you configured
an Ethernet interface as the
Source Interface. For example,
you configure a service route with Ethernet 1/3 as the source interface to forward
logs to
Strata Logging Service. In this scenario, all logs are forwarded from
the
active HA peer but no logs, including the system
and configuration logs, are forwarded from the
passive
HA peer. However, if you configure the MGT interface as the service route
Source Interface, activity occurs on both the
active and
passive HA
peers.