 |
Note: Tracking a route that belongs to a routing instance from a different logical system is not supported. |
VRRP can track whether a route is reachable (that is, the route exists in the routing table of the routing instance included in the configuration) and dynamically change the priority of the VRRP group based on the reachability of the tracked route, which might trigger a new master router election.
To configure a route to be tracked, include the following statements:
- track {
- priority-hold-time seconds;
-
- route prefix routing-instance instance-name {
- priority-cost priority;
- }
- }
You can include these statements at the following hierarchy levels:
The route prefix specified is the route to be tracked for the VRRP group. The priority hold time is the minimum length of time that must elapse between dynamic priority changes. If the dynamic priority changes because of a tracking event, the priority hold timer begins. If another tracking event or manual configuration change occurs while the timer is running, the new dynamic priority update is postponed until the timer expires.
The routing instance is the routing instance in which the route is to be tracked. If the route is in the default, or global, routing instance, specify the instance name as default.
|
Note: Tracking a route that belongs to a routing instance from a different logical system is not supported. |
The priority cost is the value to be subtracted from the configured VRRP priority when the tracked route goes down, forcing a new master router election. The value can be from 1 through 254. The sum of the costs for all tracked logical interfaces or routes must be less than or equal to the configured priority of the VRRP group.