
Object Tracking |
679
Tracking 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.
Tracking IPv4 and IPv6 Routes
You can create an object that tracks an IPv4 or IPv6 route entry in the routing table. You specify a tracked
route by its IPv4/IPv6 address and prefix-length, and optionally, by a 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.
A tracked route matches a route in the routing table only if the exact address and prefix length match an
entry in the routing 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. If no route-table entry has the exact 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 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
Tracking Route Reachability
If you configure the reachability of an IP route entry as a tracked object, 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 cache ages out for a route tracked for its reachability, an attempt is made to regenerate the ARP cache
entry to see if the next-hop address appears before considering the route DOWN.
Tracking a Metric Threshold
If you configure a metric threshold to track a route, the UP/DOWN state of the tracked route is determined
by the current metric for the route entered in the routing table.
To provide a common tracking interface for different clients, route metrics are scaled in the range 0 to 255,
where 0 is connected and 255 is inaccessible. The scaled metric value communicated to a client always
considers a lower value to have priority over a higher value. The resulting scaled value is compared against
the threshold values to determine the state of a tracked route as follows:
•
If the scaled metric for a route entry is less than or equal to the UP threshold, the state of a route is UP.
Summary of Contents for Force10 E300
Page 1: ...FTOS Configuration Guide FTOS 8 4 2 7 E Series TeraScale C Series S Series S50 S25 ...
Page 32: ...32 w w w d e l l c o m s u p p o r t d e l l c o m ...
Page 132: ...132 802 1X w w w d e l l c o m s u p p o r t d e l l c o m ...
Page 310: ...310 Configuration Replace and Rollback w w w d e l l c o m s u p p o r t d e l l c o m ...
Page 330: ...330 Dynamic Host Configuration Protocol w w w d e l l c o m s u p p o r t d e l l c o m ...
Page 402: ...402 High Availability w w w d e l l c o m s u p p o r t d e l l c o m ...
Page 462: ...462 Interfaces w w w d e l l c o m s u p p o r t d e l l c o m ...
Page 482: ...482 IPv4 Addressing w w w d e l l c o m s u p p o r t d e l l c o m ...
Page 506: ...506 IPv6 Addressing w w w d e l l c o m s u p p o r t d e l l c o m ...
Page 582: ...582 Layer 2 w w w d e l l c o m s u p p o r t d e l l c o m ...
Page 642: ...642 Multicast Source Discovery Protocol w w w d e l l c o m s u p p o r t d e l l c o m ...
Page 662: ...662 Multiple Spanning Tree Protocol w w w d e l l c o m s u p p o r t d e l l c o m ...
Page 690: ...690 Object Tracking w w w d e l l c o m s u p p o r t d e l l c o m ...
Page 754: ...754 PIM Dense Mode w w w d e l l c o m s u p p o r t d e l l c o m ...
Page 784: ...784 PIM Source Specific Mode w w w d e l l c o m s u p p o r t d e l l c o m ...
Page 800: ...800 Power over Ethernet w w w d e l l c o m s u p p o r t d e l l c o m ...
Page 876: ...876 Quality of Service w w w d e l l c o m s u p p o r t d e l l c o m ...
Page 892: ...892 Routing Information Protocol w w w d e l l c o m s u p p o r t d e l l c o m ...
Page 1006: ...1006 Simple Network Management Protocol w w w d e l l c o m s u p p o r t d e l l c o m ...
Page 1018: ...1018 SONET SDH w w w d e l l c o m s u p p o r t d e l l c o m ...
Page 1048: ...1048 Broadcast Storm Control w w w d e l l c o m s u p p o r t d e l l c o m ...
Page 1096: ...1096 Uplink Failure Detection UFD w w w d e l l c o m s u p p o r t d e l l c o m ...
Page 1098: ...1098 Upgrade Procedures w w w d e l l c o m s u p p o r t d e l l c o m ...
Page 1196: ...1196 C Series Debugging and Diagnostics w w w d e l l c o m s u p p o r t d e l l c o m ...
Page 1252: ...1252 Standards Compliance w w w d e l l c o m s u p p o r t d e l l c o m ...
Page 1262: ...1262 Index w w w d e l l c o m s u p p o r t d e l l c o m ...