
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 configuration and the tracked object’s status.
EXEC Privilege mode
show track
object-id
Examples of Configuring Object Tracking for an IPv4 or IPv6 Interface
Examples of Configuring Object Tracking for an IPv4 or IPv6 Interface
The following is an example of configuring object tracking for an IPv4 interface:
Dell(conf)#track 101 interface tengigabitethernet 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 TenGigabitEthernet 7/2 ip routing
Description: NYC metro
The following is an example of configuring object tracking for an IPv6 interface:
Dell(conf)#track 103 interface tengigabitethernet 7/11 ipv6
routing
Dell(conf-track-103)#description Austin access point
Dell(conf-track-103)#end
Dell#show track 103
Track 103
Interface TenGigabitEthernet 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 prefix-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 definition 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 prefix length match an entry in the table.
For example, when configured 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 prefix length, the tracked route is considered to be DOWN.
In addition to the entry of a route in the routing table, you can configure the UP/DOWN state of a tracked route to be determined in
the following ways:
•
By the reachability of the route's next-hop router.
The UP/DOWN state of the route is determined by the entry of the next-hop address in the ARP cache. A tracked route is
considered to be reachable if there is an ARP cache entry for the route's next-hop address. If the next-hop address in the ARP
570
Object Tracking
Содержание S4048-ON
Страница 1: ...Dell Configuration Guide for the S4048 ON System 9 9 0 0 ...
Страница 146: ...Figure 14 BFD Three Way Handshake State Changes 146 Bidirectional Forwarding Detection BFD ...
Страница 477: ...Figure 68 Inspecting Configuration of LAG 10 on ALPHA Link Aggregation Control Protocol LACP 477 ...
Страница 480: ...Figure 70 Inspecting a LAG Port on BRAVO Using the show interface Command 480 Link Aggregation Control Protocol LACP ...
Страница 481: ...Figure 71 Inspecting LAG 10 Using the show interfaces port channel Command Link Aggregation Control Protocol LACP 481 ...
Страница 522: ...Figure 87 Configuring Interfaces for MSDP 522 Multicast Source Discovery Protocol MSDP ...
Страница 523: ...Figure 88 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 523 ...
Страница 524: ...Figure 89 Configuring PIM in Multiple Routing Domains 524 Multicast Source Discovery Protocol MSDP ...
Страница 528: ...Figure 91 MSDP Default Peer Scenario 1 528 Multicast Source Discovery Protocol MSDP ...
Страница 529: ...Figure 92 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 529 ...
Страница 530: ...Figure 93 MSDP Default Peer Scenario 3 530 Multicast Source Discovery Protocol MSDP ...
Страница 633: ...Policy based Routing PBR 633 ...
Страница 777: ...Figure 119 Single and Double Tag TPID Match Service Provider Bridging 777 ...
Страница 778: ...Figure 120 Single and Double Tag First byte TPID Match 778 Service Provider Bridging ...