Users Guide

A tracked route matches a route in the routing table only if the exact address and prex length match an entry in the routing table.
For example, when congured as a tracked route, 10.0.0.0/24 does not match the routing table entry 10.0.0.0/8. If no route-table
entry has the exact address and prex length, the tracked route is considered to be DOWN.
In addition to the entry of a route in the routing table, you can congure how the status of a route is tracked in either the following
ways:
By the reachability of the route's next-hop router.
By comparing the UP or DOWN threshold for a route’s metric with current entries in the route table.
Set Tracking Delays
You can congure an optional UP and/or DOWN timer for each tracked object to set the time delay before a change in the state of a
tracked object is communicated to clients. The congured time delay starts when the state changes from UP to DOWN or the
opposite way.
If the state of an object changes back to its former UP/DOWN state before the timer expires, the timer is cancelled and the client is
not notied. If the timer expires and an object’s state has changed, a notication is sent to the client. For example, if the DOWN
timer is running when an interface goes down and comes back up, the DOWN timer is cancelled and the client is not notied of the
event.
If you do not congure a delay, a notication is sent when a change in the state of a tracked object is detected. The time delay in
communicating a state change is specied in seconds.
VRRP Object Tracking
As a client, VRRP can track up to 20 objects (including route entries, and Layer 2 and Layer 3 interfaces) in addition to the 12
tracked interfaces supported for each VRRP group.
You can assign a unique priority-cost value from 1 to 254 to each tracked VRRP object or group interface. The priority cost is
subtracted from the VRRP group priority if a tracked VRRP object is in a DOWN state. If a VRRP group router acts as owner-master,
the run-time VRRP group priority remains xed at 255 and changes in the state of a tracked object have no eect.
NOTE: In VRRP object tracking, the sum of the priority costs for all tracked objects and interfaces cannot equal or
exceed the priority of the VRRP group.
Object Tracking Conguration
You can congure three types of object tracking for a client.
Track Layer 2 Interfaces
Track Layer 3 Interfaces
Track an IPv4/IPv6 Route
For a complete listing of all commands related to object tracking, refer to the Dell Networking OS Command Line Interface
Reference Guide.
Tracking a Layer 2 Interface
You can create an object that tracks the line-protocol state of a Layer 2 interface and monitors its operational status (UP or DOWN).
You can track the status of any of the following Layer 2 interfaces:
1 Gigabit Ethernet: Enter gigabitethernet slot/port in the track interface interface command (see Step 1).
10 Gigabit Ethernet: Enter tengigabitethernet slot/port.
Port channel: Enter port-channel number, where valid port-channel numbers are from 1 to 128:
VLAN: Enter vlan vlan-id, where valid VLAN IDs are from 1 to 4094
A line-protocol object only tracks the link-level (UP/DOWN) status of a specied interface. When the link-level status goes down,
the tracked object status is DOWN; if the link-level status is up, the tracked object status is UP.
Object Tracking
159