
Figure 100. Object Tracking Example
When you configure a tracked object, such as an IPv4/IPv6 a route or interface, you specify an object number to identify the object.
Optionally, you can also specify:
•
UP and DOWN thresholds used to report changes in a route metric.
•
A time delay before changes in a tracked object’s state are reported to a client.
Track Layer 2 Interfaces
You can create an object to track the line-protocol state of a Layer 2 interface. In this type of object tracking, the link-level
operational status (UP or DOWN) of the interface is monitored.
When the link-level status goes down, the tracked resource status is considered to be DOWN; if the link-level status goes up, the
tracked resource status is considered to be UP. For logical interfaces, such as port-channels or virtual local area networks (VLANs),
the link-protocol status is considered to be UP if any physical interface under the logical interface is UP.
Track Layer 3 Interfaces
You can create an object that tracks the Layer 3 state (IPv4 or IPv6 routing status) of an interface.
•
The Layer 3 status of an interface is UP only if the Layer 2 status of the interface is UP and the interface has a valid IP address.
•
The Layer 3 status of an interface goes DOWN when its Layer 2 status goes down or the IP address is removed from the routing
table.
Track IPv4 and IPv6 Routes
You can create an object that tracks an IPv4 or IPv6 route entry in the routing table.
Specify a tracked route by its IPv4 or IPv6 address and prefix-length. Optionally specify a tracked route by a virtual routing and
forwarding (VRF) instance name if the route to be tracked is part of a VRF. The next-hop address is not part of the definition of the
tracked object.
566
Object Tracking
Summary of Contents for S4048-ON
Page 1: ...Dell Configuration Guide for the S4048 ON System 9 9 0 0 ...
Page 146: ...Figure 14 BFD Three Way Handshake State Changes 146 Bidirectional Forwarding Detection BFD ...
Page 522: ...Figure 87 Configuring Interfaces for MSDP 522 Multicast Source Discovery Protocol MSDP ...
Page 523: ...Figure 88 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 523 ...
Page 528: ...Figure 91 MSDP Default Peer Scenario 1 528 Multicast Source Discovery Protocol MSDP ...
Page 529: ...Figure 92 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 529 ...
Page 530: ...Figure 93 MSDP Default Peer Scenario 3 530 Multicast Source Discovery Protocol MSDP ...
Page 633: ...Policy based Routing PBR 633 ...
Page 777: ...Figure 119 Single and Double Tag TPID Match Service Provider Bridging 777 ...
Page 778: ...Figure 120 Single and Double Tag First byte TPID Match 778 Service Provider Bridging ...