Configuration Example for PBR with Path Monitoring
-
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
Step 1 | 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.
|
Step 2 | Configure policy-based routing for a branch in an organization threat defense, select the ingress interfaces:
|
Step 3 | Specify the match criteria: |
Step 4 | Specify the egress interfaces:
|
Step 5 | Repeat Step 2 and Step 3 to create PBRs for the same interface (Inside1) to route Office365 and network-based access control traffic:
|
Step 6 | Save and Deploy. |
Step 7 | To view path monitoring metrics, choose More ( |
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.