I am looking for a suggestion how we can ensure a custom application traverses the correct circuit as it's primary. I can only identify it by IP address so I am unable to use a match dscp or application.
For example, custom server IP: 172.16.5.5
iWAN with MPLS and Internet DMVPN tunnels.
I want traffic to/from the custom applicaiton to always ride the MPLS circuit using "low-latency-data" policy.
iWAN, PFRv
Current Config:
domain default
vrf default
border
source-interface Loopback0
master local
master hub
source-interface Loopback0
site-prefixes prefix-list Data_Center_Production
monitor-interval 2 dscp ef
load-balance
enterprise-prefix prefix-list ENTERPRISE
class VOICE sequence 10
match dscp ef policy voice
path-preference MPLS fallback INET
class INTERACTIVE_VIDEO sequence 20
match dscp cs4 policy real-time-video
match dscp af41 policy real-time-video
match dscp af42 policy real-time-video
match dscp af43 policy real-time-video
path-preference MPLS fallback INET
class LOW_LATENCY_DATA sequence 30
match dscp cs2 policy low-latency-data
match dscp cs3 policy low-latency-data
match dscp af21 policy low-latency-data
match dscp af22 policy low-latency-data
match dscp af23 policy low-latency-data
path-preference MPLS fallback INET
class BULK_DATA sequence 40
match dscp af11 policy bulk-data
match dscp af12 policy bulk-data
match dscp af13 policy bulk-data
path-preference MPLS fallback INET
class SCAVENGER sequence 50
match dscp cs1 policy scavenger
path-preference MPLS fallback INET
class DEFAULT sequence 60
match dscp default policy best-effort
path-preference MPLS fallback INET
What I am envisioning is something like:
class LOW_LATENCY_DATA sequence 30
match dscp cs2 policy low-latency-data
match dscp cs3 policy low-latency-data
match dscp af21 policy low-latency-data
match dscp af22 policy low-latency-data
match dscp af23 policy low-latency-data
match CUSTOM_APPLICATION policy low-latency-data
path-preference MPLS fallback INET
