Static route integration with path monitoring
Also known as 'static route path monitor tracking' or 'static route path monitor integration'. You can also consider this feature as part of the path performance monitoring (PPM) family of features.
This feature adds the ability to associate static routes with one or more path monitor monitor/policy pairs. The compliance state of each monitor with its paired policy determines whether the associated route is active in the FIB. This allows for route manipulation of traffic without requiring the use of PBR policies.
You can configure path monitor tracking on IPv4 and IPv6 static routes and interface routes, in any table or routing instance.
Associate a path monitor monitor/policy pair with a static route
We can associate a path monitor monitor/policy pair with a static route:
set protocols static route 22.214.171.124/32 next-hop 10.10.1.2 path-monitor monitor DC-2 policy DC
Now whenever the results of the
DC-2 monitor become "Non-compliant" with the
DC policy this route will become inactive and will be removed from the forwarder.
Track multiple monitor/policy pairs with a static route
We can configure a static route to track multiple monitor/policy pairs:
$ set protocols static route 126.96.36.199/32 next-hop 10.10.1.2 path-monitor monitor DC-2 policy voip $ set protocols static route 188.8.131.52/32 next-hop 10.10.1.2 path-monitor monitor DC-2-twping policy DC-twping
Now all of the monitor/policy pairs must each be "Compliant" or "Marginally compliant" in order for the route to be active in the forwarder. If any pair becomes "Non-compliant" then the route becomes inactive.