Configuration Example for PBR with Path Monitoring

This example details the configuration of PBR with path monitoring for the following applications with flexible metrics:

Audio or video sensitive applications (example, WebEx Meetings) with Jitter.
Cloud-based application (example, Office365) with RTT.
Network-based access control (with a specific source and destination) with Packet Loss.

Before you begin

This example assumes that you are aware of the basic configuration steps for PBR.
You have configured ingress and egress interfaces with logical names. In this example, the ingress interface is named Inside1, and egress interfaces are named ISP01, ISP02, and ISP03.

Procedure

Path monitoring configuration on interfaces ISP01, ISP02, and ISP03:

For the metrics collection on the egress interfaces, you must enable and configure path monitoring on them.

Choose Devices > Device Management, and edit Firewall Threat Defense.
Under the Interfaces tab, edit the interface (in our example, ISP01)
Click the Path Monitoring tab, select the Enable Path Monitoring check box, and then specify the monitoring type (see Configure Path Monitoring Settings).
Click Ok and Save.
Repeat the same steps and configure the path monitoring settings for ISP02 and ISP03.

Configure policy-based routing for a branch in an organization Firewall Threat Defense, select the ingress interfaces:

Choose Devices > Device Management, and edit the Firewall Threat Defense device.
Choose Routing > Policy Based Routing, and on the Policy Based Routing page, click Add.
In the Add Policy Based Route dialog box, select Inside 1 from the Ingress Interface drop-down list.

Specify the match criteria:

Click Add.
To define the match criteria, click the Add () button.
In New Extended Access List Object, enter the name for the ACL (example, PBR-WebEx), and click Add.
In the Add Extended Access List Entry dialog box, choose the required web-based applications (example, WebEx Meetings) from the Application tab.

On Firewall Threat Defense, the application group in an ACL is configured as a network service group and each of the applications as a network service object.
Click Save.
Select PBR-WebEx from the Match ACL drop-down list.

Specify the egress interfaces:

From the Send To drop-down list, choose Egress Interfaces.
From the Interface Ordering drop-down list, choose By Minimal Jitter.
Under Available Interfaces, click the Right Arrow ()button against the respective interface names to add ISP01, ISP02, and ISP03.
Click Save.

Repeat Step 2 and Step 3 to create PBRs for the same interface (Inside1) to route Office365 and network-based access control traffic:

Create a match criteria object, example PBR-Office365, and select the Office365 application from the Application tab.
From the Interface Ordering drop-down list, choose By Minimal Round Trip Time.
Specify the egress interfaces ISP01, ISP02, and ISP03, and click Save.
Now, create a match criteria object, example PBR-networks, and specify the source and destination interface in the Network tab.
From the Interface Ordering drop-down list, choose By Minimal Packet Loss.
Specify the egress interfaces ISP01, ISP02, and ISP03, and click Save.

Save and Deploy.

To view path monitoring metrics, choose Devices > Device Management, and from More ( more icon ) click Health Monitor. To view the metric details for the interfaces of the device, you must add the path metrics dashboard. For details, see Add Path Monitoring Dashboard.

The WebEx, Office365, and networks-based ACL traffic are forwarded through the best route derived from the metrics value collected on ISP01, ISP02, and ISP03.

Previous topic Configuration Example for Policy Based Routing Next topic Object Management