Service Manual
Valid object IDs are from 1 to 65535.
2. (Optional) Congure the time delay used before communicating a change in the status of a tracked interface.
OBJECT TRACKING mode
delay {[up seconds] [down seconds]}
Valid delay times are from 0 to 180 seconds.
The default is 0.
3. (Optional) Identify the tracked object with a text description.
OBJECT TRACKING mode
description text
The text string can be up to 80 characters.
4. (Optional) Display the tracking conguration and the tracked object’s status.
EXEC Privilege mode
show track object-id
Example of Conguring Object Tracking (IPv4 Interface)
Example of Conguring Object Tracking (IPv6 Interface)
Dell(conf)#track 101 interface gigabitethernet 7/2 ip routing
Dell(conf-track-101)#delay up 20
Dell(conf-track-101)#description NYC metro
Dell(conf-track-101)#end
Dell#show track 101
Track 101
Interface GigabitEthernet 7/2 ip routing
Description: NYC metro
Dell(conf)#track 103 interface gigabitethernet 7/11 ipv6
routing
Dell(conf-track-103)#description Austin access point
Dell(conf-track-103)#end
Dell#show track 103
Track 103
Interface GigabitEthernet 7/11 ipv6 routing
Description: Austin access point
Track an IPv4/IPv6 Route
You can create an object that tracks the reachability or metric of an IPv4 or IPv6 route.
You specify the route to be tracked by its address and prex-length values. Optionally, for an IPv4 route, you can enter a VRF
instance name if the route is part of a VPN routing and forwarding (VRF) table. The next-hop address is not part of the denition of
a tracked IPv4/IPv6 route.
In order for an route’s reachability or metric to be tracked, the route must appear as an entry in the routing table. A tracked route is
considered to match an entry in the routing table only if the exact IPv4 or IPv6 address and prex length match an entry in the table.
For example, when congured as a tracked route, 10.0.0.0/24 does not match the routing table entry 10.0.0.0/8. Similarly, for an IPv6
address, 3333:100:200:300:400::/80 does not match routing table entry 3333:100:200:300::/64. If no route-table entry has the
exact IPv4/IPv6 address and prex length, the tracked route is considered to be DOWN.
In addition to the entry of a route in the routing table, you can congure the UP/DOWN state of a tracked route to be determined in
the following ways:
Object Tracking
493