track
This command defines a tracking destination to be used by static routes or other configured elements. This command tracks a destination IP address from a given source interface. The tracking is done by sending ICMP probe packets and monitors the replies. If the destination is reachable, the Track Status is set to ‘up’. When a configurable number of replies are not received, the Track Status is set to ‘down’.
Syntax
track <Track ID> {icmpecho | icmp6echo} {<Destination Address>|dyn-dns-server} <Source Interface> <Interface ID> [source-ip-interface <Interface>] [interval <Value>] [retries <Value>] description <Description>
|
Command |
Description |
|---|---|
|
Destination Address |
Defines the IP address of the tracked destination (IPv4 or IPv6). |
|
description |
(Optional) Defines a description (max. 64 bytes) of the tracking destination. |
|
dyn-dns-server |
The device automatically obtains the tracking destination for the specific source interface (instead of specifying an IP address). The destination is obtained from the DNS server that is associated with the source interface when using DHCP or PPP. |
|
icmpecho |
Tracking is done by sending ICMP probes and monitors the replies. |
|
icmpv6echo |
Tracking is done by sending ICMPv6 probes and monitors the replies |
|
interval |
Defines the interval (in seconds) between probes. Range is 1-3600. The default is 5 seconds. |
|
max-rtt |
Defines the maximum round-trip time (RTT) in milliseconds for each probe of the retries command, after which the track status changes to "down". For example, if configured to 2 ms and retires to 3, if 4 consecutive probes (3 additional attempts after the first one fails) where each is within 2 ms is unsuccessful, the status changes to "down". The default is 0 (disabled). |
|
retries |
Defines the number of consecutive failed retries probes (after first probe failed) before the track status changes to “down”. Range is 0 – 20. (Default value is 3). Note: The maximum time for each probe can also be configured, by the max-rtt command. |
|
retries-up |
If the tracking destination status is "down" and the device probes it successfully for this user-defined number of consecutive attempts, the track status changes to "up" (i.e., reachable). For example, if configured to 0, the first successful probe changes the status to "up". The default is 0. |
|
Source Interface |
Defines the interface name and ID (see table below). |
|
source-ip-interface |
Defines an interface whose IP address is used as the source IP address for the probes (see table below). |
|
track id |
Defines the track identifier to be used by other entities. |
|
track protocol type |
Defines the reachability by sending ping packets of either IPv4 or IPv6 (currently only probe type). |
|
Interface Type (ifname) |
Interface ID |
|
|---|---|---|
|
gigabitethernet |
GigabitEthernet interface slot and port (VLAN ID is optional) |
[SLOT/PORT.VLANID] |
|
cellular |
Cellular interface ID |
0/0 |
|
gre |
Tunnel GRE ID |
[1-255] |
|
ipip |
Tunnel IPIP ID |
[1-255] |
|
l2tp |
L2TP ID |
[0-99] |
|
pppoe |
PPPoE interface ID |
[1-3] |
|
pptp |
PPTP ID |
[0-99] |
|
vlan |
Vlan ID |
[1-3999] |
|
loopback |
Loopback ID |
[1-5] |
|
bvi |
Bridge interface |
[1-255] |
Default
N/A
Command Mode
Privileged User
Related Commands
show data track brief, ip route
Examples:
| ■ | This example defines Track ID 5 for destination 10.30.4.5 from interface GigabitEthernet 0/0. |
(config-data)# track 5 icmpecho 10.30.4.5 GigabitEthernet 0/0 description Track_Google_from_GE
| ■ | This example defines Track ID 5 for a destination obtained automatically from a DNS server from interface GigabitEthernet 0/0. |
(config-data)# track 5 icmpecho dyn-dns-server GigabitEthernet 0/0 description Track_Google_from_GE
| ■ | This example defines Track ID 5 for destination 10.30.4.5 from interface GigabitEthernet 0/0 and source IP address of interface loopback 1. |
(config-data)# track 5 IcmpEcho 10.30.4.5 GigabitEthernet 0/0 source-ip-interface loopback 1