carrier-delay (tracking)
To enable Enhanced Object Tracking (EOT) to consider the carrier-delay timer when tracking the status of an interface, use the carrier-delay command in tracking configuration mode. To disable EOT from considering the carrier-delay timer when tracking the status of an interface, use the no form of this command.
carrier-delay
no carrier-delay
Syntax Description
This command has no arguments or keywords.
Command Default
EOT does not consider the carrier-delay timer configured on an interface when tracking the status of the interface.
Command Modes
Tracking configuration (config-track)
Command History
Release |
Modification |
---|---|
12.4(9)T |
This command was introduced. |
15.3(3)M |
This command was integrated into Cisco IOS Release 15.3(3)M. |
Cisco IOS XE 3.3SE |
This command was implemented in Cisco IOS XE Release 3.3SE. |
Usage Guidelines
If a link fails, by default there is a two-second timer that must expire before an interface and the associated routes are declared down. If a link goes down and comes back up before the carrier delay timer expires, the down state is effectively filtered, and the rest of the software on the switch is not aware that a link-down event occurred. You can configure the carrier-delay seconds command in interface configuration mode to extend the timer up to 60 seconds.
When Enhanced Object Tracking (EOT) is configured on an interface, the tracking may detect the interface is down before a configured carrier-delay timer has expired. This is because EOT looks at the interface state and does not consider the carrier-delay timer.
Examples
The following example shows how to configure the tracking module to wait for the interface carrier-delay timer to expire before notifying clients of a state change:
Router(config)# track 101 interface ethernet1/0 line-protocol
Router(config-track)# carrier-delay