The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Before the introduction of the Enhanced Object Tracking feature, the Hot Standby Router Protocol (HSRP) had a simple tracking mechanism that allowed you to track the interface line-protocol state only. If the line-protocol state of the interface went down, the HSRP priority of the router was reduced, allowing another HSRP router with a higher priority to become active.
The Enhanced Object Tracking feature separates the tracking mechanism from HSRP and creates a separate standalone tracking process that can be used by other Cisco IOS processes and HSRP. This feature allows tracking of other objects in addition to the interface line-protocol state.
A client process such as HSRP, Virtual Router Redundancy Protocol (VRRP), or Gateway Load Balancing Protocol (GLBP), can register its interest in tracking objects and then be notified when the tracked object changes state.
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the Feature Information Table at the end of this document.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Enhanced Object Tracking is not stateful switchover (SSO)-aware and cannot be used with Hot Standby Routing Protocol (HSRP), Virtual Router Redundancy Protocol (VRRP), or Gateway Load Balancing Protocol (GLBP) in SSO mode.
The Enhanced Object Tracking feature provides complete separation between the objects to be tracked and the action to be taken by a client when a tracked object changes. Thus, several clients such as HSRP, VRRP, or GLPB can register their interest with the tracking process, track the same object, and each take different action when the object changes.
Each tracked object is identified by a unique number that is specified on the tracking CLI. Client processes use this number to track a specific object.
The tracking process periodically polls the tracked objects and notes any change of value. The changes in the tracked object are communicated to interested client processes, either immediately or after a specified delay. The object values are reported as either up or down.
You can configure a combination of tracked objects in a list and a flexible method for combining objects using Boolean logic. This functionality includes the following capabilities:
As of Cisco IOS Release 15.1(3)T, 15.1(1)S and 12.2(50)SY a maximum of 1000 objects can be tracked. Although 1000 tracked objects can be configured, each tracked object uses CPU resources. The amount of available CPU resources on a router depends on variables such as traffic load and how other protocols are configured and run. The ability to use 1000 tracked objects depends on the available CPU. Testing should be conducted on site to ensure that the service works under the specific site traffic conditions.
An IP-routing object is considered up when the following criteria exist:
Interface IP routing will go down when one of the following criteria exists:
Tracking the IP-routing state of an interface using the track interface ip routing command can be more useful in some situations than just tracking the line-protocol state using the track interface line-protocol command, especially on interfaces for which IP addresses are negotiated. For example, on a serial interface that uses the PPP, the line protocol could be up (link control protocol [LCP] negotiated successfully), but IP could be down (IPCP negotiation failed).
The track interface ip routing command supports the tracking of an interface with an IP address acquired through any of the following methods:
You can configure Enhanced Object Tracking to consider the carrier-delay timer when tracking the IP-routing state of an interface by using the carrier-delay command in tracking configuration mode.
The track ip route command enables tracking of a route in the routing table. If a route exists in the table, the metric value is converted into a number. To provide a common interface to tracking clients, normalize route metric values to the range from 0 to 255, where 0 is connected and 255 is inaccessible. Scaled metrics can be tracked by setting thresholds. Up and down state notification occurs when the thresholds are crossed. The resulting value is compared against threshold values to determine the tracking state as follows:
Tracking uses a per-protocol configurable resolution value to convert the real metric to the scaled metric. The table below shows the default values used for the conversion. You can use the track resolution command to change the metric resolution default values.
Table 1 | Metric Conversion |
Route Type1 |
Metric Resolution |
---|---|
Static |
10 |
Enhanced Interior Gateway Routing Protocol (EIGRP) |
2560 |
Open Shortest Path First (OSPF) |
1 |
Intermediate System-to-Intermediate System (IS-IS) |
10 |
For example, a change in 10 in an IS-IS metric results in a change of 1 in the scaled metric. The default resolutions are designed so that approximately one 2-Mbps link in the path will give a scaled metric of 255.
Scaling the very large metric ranges of EIGRP and IS-IS to a 0 to 255 range is a compromise. The default resolutions will cause the scaled metric to exceed the maximum limit with a 2-Mb/s link. However, this scaling allows a distinction between a route consisting of three Fast-Ethernet links and a route consisting of four Fast-Ethernet links.
Object tracking of IP Service Level Agreements (SLAs) operations allows tracking clients to track the output from IP SLAs objects and use the provided information to trigger an action.
Cisco IOS IP SLAs is a network performance measurement and diagnostics tool that uses active monitoring. Active monitoring is the generation of traffic in a reliable and predictable manner to measure network performance. Cisco IOS software uses IP SLAs to collect real-time metrics such as response time, network resource availability, application performance, jitter (interpacket delay variance), connect time, throughput, and packet loss.
These metrics can be used for troubleshooting, for proactive analysis before problems occur, and for designing network topologies.
Every IP SLAs operation maintains an operation return-code value. This return code is interpreted by the tracking process. The return code can return OK, OverThreshold, and several other return codes. Different operations can have different return-code values, so only values common to all operation types are used.
Two aspects of an IP SLAs operation can be tracked: state and reachability. The difference between these aspects is the acceptance of the OverThreshold return code. The table below shows the state and reachability aspects of IP SLAs operations that can be tracked.
Table 2 | Comparison of State and Reachability Operations |
Tracking |
Return Code |
Track State |
---|---|---|
State |
OK (all other return codes) |
Up Down |
Reachability |
OK or OverThreshold (all other return codes) |
Up Down |
Enhanced Object Tracking (EOT) is now integrated with Embedded Event Manager (EEM) to allow EEM to report on status change of a tracked object and to allow EOT to track EEM objects. A new type of tracking object--a stub object--is created. The stub object can be modified by an external process through a defined Application Programming Interface (API). See the Embedded Event Manager Overview document in the Cisco IOSNetwork Management Configuration Guide for more information on how EOT works with EEM.
The EOT Support for Carrier Delay feature enables Enhanced Object Tracking (EOT) to consider the carrier-delay timer when tracking the status of an interface.
If a link fails, by default there is a two-second timer that must expire before an interface and the associated routes are declared as being 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 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. Use the carrier-delay command in tracking configuration mode to enable tracking to consider the carrier-delay timer configured on an interface.
The Enhanced Object Tracking Support for Mobile IP feature enables EOT to monitor the presence of Home Agent, Packet Data Serving Node (PDSN), or Gateway GPRS Support Node (GGSN) traffic on a router for mobile wireless applications.
When a redundant pair of Home Agents running HSRP between them loses connectivity, both HSRP nodes become active. Once the connectivity is restored between the two nodes, a graceful way is needed to restore proper HSRP states without losing Home Agent bindings. During the time of no connectivity, one of the nodes will continue to process Home Agent, GGSN, or PDSN traffic while the other will not. The node that continues to process traffic needs to remain active once connectivity is restored. To ensure that the active node remains in the active state, the priority of the HSRP group member that does not process Home Agent traffic is reduced. Reducing the priority of the node that is not processing Home Agent traffic ensures that this node will become the standby after connectivity is restored. When connectivity is restored, the normal Home Agent state synchronization will get all bindings back into the inactive node and, depending on the preempt configuration, it may switch over again. This state synchronization ensures that no Mobile IP, GGSN, or PDSN bindings are lost.
For more information on configuring Mobile IP services, see the following Cisco IOS configuration guides:
The following example shows the state of the line protocol on an interface when it is tracked:
Router# show track 3
Track 3
Interface Ethernet0/1 line-protocol
Line protocol is Up
1 change, last change 00:00:05
Tracked by:
HSRP Ethernet0/3 1
Command or Action | Purpose | |||
---|---|---|---|---|
|
Example: Router> enable |
Enables privileged EXEC mode. |
||
|
Example: Router# configure terminal |
Enters global configuration mode. |
||
|
Example: Router(config)# track timer interface 5 |
(Optional) Specifies the interval in which the tracking process polls the tracked object.
|
||
|
Example: Router(config)# track 1 interface ethernet 0/1 ip routing |
Tracks the IP-routing state of an interface and enters tracking configuration mode. |
||
|
Example: Router(config-track)# carrier-delay |
(Optional) Enables EOT to consider the carrier-delay timer when tracking the status of an interface. |
||
|
Example: Router(config-track)# delay up 30 |
(Optional) Specifies a period of time (in seconds) to delay communicating state changes of a tracked object. |
||
|
Example: Router(config-track)# end |
Returns to privileged EXEC mode. |
||
|
Example: Router# show track 1 |
Displays tracking information. |
The following example shows the state of IP routing on an interface when it is tracked:
Router# show track 1
Track 1
Interface Ethernet0/1 ip routing
IP routing is Up
1 change, last change 00:01:08
Tracked by:
HSRP Ethernet0/3 1
Perform this task to track the reachability of an IP route. A tracked object is considered up when a routing table entry exists for the route and the route is accessible.
Command or Action | Purpose | |||
---|---|---|---|---|
|
Example: Router> enable |
Enables privileged EXEC mode. |
||
|
Example: Router# configure terminal |
Enters global configuration mode. |
||
|
Example: Router(config)# track timer ip route 20 |
(Optional) Specifies the interval in which the tracking process polls the tracked object.
|
||
|
Example: Router(config)# track 4 ip route 10.16.0.0/16 reachability |
Tracks the reachability of an IP route and enters tracking configuration mode. |
||
|
Example: Router(config-track)# delay up 30 |
(Optional) Specifies a period of time (in seconds) to delay communicating state changes of a tracked object. |
||
|
Example: Router(config-track)# ip vrf VRF2 |
(Optional) Configures a VPN routing and forwarding (VRF) table. |
||
|
Example: Router(config-track)# end |
Returns to privileged EXEC mode. |
||
|
Example: Router# show track 4 |
(Optional) Displays tracking information. |
The following example shows the state of the reachability of an IP route when it is tracked:
Router# show track 4
Track 4
IP route 10.16.0.0 255.255.0.0 reachability
Reachability is Up (RIP)
1 change, last change 00:02:04
First-hop interface is Ethernet0/1
Tracked by:
HSRP Ethernet0/3 1
Command or Action | Purpose | |||
---|---|---|---|---|
|
Example: Router> enable |
Enables privileged EXEC mode. |
||
|
Example: Router# configure terminal |
Enters global configuration mode. |
||
|
Example: Router(config)# track timer ip route 20 |
(Optional) Specifies the interval in which the tracking process polls the tracked object.
|
||
|
Example: Router(config)# track resolution ip route eigrp 300 |
(Optional) Specifies resolution parameters for a tracked object. |
||
|
Example: Router(config)# track 6 ip route 10.16.0.0/16 metric threshold |
Tracks the scaled metric value of an IP route to determine if it is above or below a threshold and enters tracking configuration mode. |
||
|
Example: Router(config-track)# delay up 30 |
(Optional) Specifies a period of time (in seconds) to delay communicating state changes of a tracked object. |
||
|
Example: Router(config-track)# ip vrf VRF1 |
(Optional) Configures a VRF table. |
||
|
Example: Router(config-track)# threshold metric up 254 down 255 |
(Optional) Sets a metric threshold other than the default value. |
||
|
Example: Router(config-track)# end |
Exits to privileged EXEC mode. |
||
|
Example: Router# show track 6 |
(Optional) Displays tracking information. |
The following example shows the metric threshold of an IP route when it is tracked:
Router# show track 6
Track 6
IP route 10.16.0.0 255.255.0.0 metric threshold
Metric threshold is Up (RIP/6/102)
1 change, last change 00:00:08
Metric threshold down 255 up 254
First-hop interface is Ethernet0/1
Tracked by:
HSRP Ethernet0/3 1
Command or Action | Purpose | |
---|---|---|
|
Example: Router> enable |
Enables privileged EXEC mode. |
|
Example: Router# configure terminal |
Enters global configuration mode. |
|
Example: Router(config)# track 2 ip sla 4 state |
Tracks the state of an IP SLAs object and enters tracking configuration mode. Effective with Cisco IOS Release 12.4(20)T, 12.2(33)SXI1, and 12.2(33)SRE the track rtr command was replaced by the track ip sla command. |
|
Example: Router(config-track)# delay up 60 down 30 |
(Optional) Specifies a period of time (in seconds) to delay communicating state changes of a tracked object. |
|
Example: Router(config-track)# end |
Exits to privileged EXEC mode. |
|
Example: Router# show track 2 |
(Optional) Displays tracking information. |
The following example shows the state of the IP SLAs tracking:
Router# show track 2
Track 2
IP SLA 1 state
State is Down
1 change, last change 00:00:47
Latest operation return code: over threshold
Latest RTT (millisecs) 4
Tracked by:
HSRP Ethernet0/1 3
Command or Action | Purpose | |||
---|---|---|---|---|
|
Example: Router> enable |
Enables privileged EXEC mode. |
||
|
Example: Router# configure terminal |
Enters global configuration mode. |
||
|
Example: Router(config)# track 2 ip sla 4 reachability |
Tracks the reachability of an IP SLAs IP host and enters tracking configuration mode.
|
||
|
Example: Router(config-track)# delay up 30 down 10 |
(Optional) Specifies a period of time (in seconds) to delay communicating state changes of a tracked object. |
||
|
Example: Router(config-track)# end |
Exits to privileged EXEC mode. |
||
|
Example: Router# show track 3 |
(Optional) Displays tracking information. |
The following example shows whether the route is reachable:
Router# show track 3
Track 3
IP SLA 1 reachability
Reachability is Up
1 change, last change 00:00:47
Latest operation return code: over threshold
Latest RTT (millisecs) 4
Tracked by:
HSRP Ethernet0/1 3
Perform this task to configure a tracked list of objects and a Boolean expression to determine the state of the list. A tracked list contains one or more objects. The Boolean expression enables two types of calculations by using either “and” or “or” operators. For example, when you configure tracking for two interfaces using the “and” operator up means that both interfaces are up, and down means that either interface is down.
You may configure a tracked list state to be measured using a weight or percentage threshold. See the Configuring a Tracked List and Threshold Weight section and the Configuring a Tracked List and Threshold Percentage section.
An object must exist before it can be added to a tracked list.
Note |
The “not” operator is specified for one or more objects and negates the state of the object. |
Command or Action | Purpose | |||
---|---|---|---|---|
|
Example: Router> enable |
Enables privileged EXEC mode. |
||
|
Example: Router# configure terminal |
Enters global configuration mode. |
||
|
Example: Router(config)# track 100 list boolean and |
Configures a tracked list object and enters tracking configuration mode. |
||
|
Example: Router(config-track)# object 3 not |
|
||
|
Example: Router(config-track)# delay up 3 |
(Optional) Specifies a tracking delay in seconds between up and down states. |
||
|
Example: Router(config-track)# end |
Returns to privileged EXEC mode. |
Perform this task to configure a list of tracked objects, to specify that weight be used as the threshold, and to configure a weight for each of the objects in the list of tracked objects. A tracked list contains one or more objects. Enhanced object tracking uses a threshold weight to determine the state of each object by comparing the total weight of all objects that are up against a threshold weight for each object.
You can also configure a tracked list state to be measured using a Boolean calculation or threshold percentage. See the Configuring a Tracked List and Boolean Expression section and the Configuring a Tracked List and Threshold Percentage section.
An object must exist before it can be added to a tracked list.
Note |
You cannot use the Boolean “not” operator in a weight or percentage threshold list. |
Command or Action | Purpose | |
---|---|---|
|
Example: Router> enable |
Enables privileged EXEC mode. |
|
Example: Router# configure terminal |
Enters global configuration mode. |
|
Example: Router(config)# track 100 list threshold weight |
Configures a tracked list object and enters tracking configuration mode. The keywords are as follows: |
|
Example: Router(config-track)# object 3 weight 30 |
Specifies the object to be tracked. The object-number argument has a valid range from 1 to 500. There is no default. The optional weight keyword specifies a threshold weight for each object. |
|
Example: Router(config-track)# threshold weight up 30 |
Specifies the threshold weight. |
|
Example: Router(config-track)# delay up 3 |
(Optional) Specifies a tracking delay in seconds between up and down states. |
|
Example: Router(config-track)# end |
Returns to privileged EXEC mode. |
Perform this task to configure a tracked list of objects, to specify that a percentage will be used as the threshold, and to specify a percentage for each object in the list. A tracked list contains one or more objects. Enhanced object tracking uses the threshold percentage to determine the state of the list by comparing the assigned percentage of each object to the list.
You may also configure a tracked list state to be measured using a Boolean calculation or threshold weight. See the Configuring a Tracked List and Boolean Expression section and the Configuring a Tracked List and Threshold Weight section.
Note |
You cannot use the Boolean “not” operator in a weight or percentage threshold list. |
An object must exist before it can be added to a tracked list.
Command or Action | Purpose | |
---|---|---|
|
Example: Router> enable |
Enables privileged EXEC mode. |
|
Example: Router# configure terminal |
Enters global configuration mode. |
|
Example: Router(config)# track 100 list threshold percentage |
Configures a tracked list object and enters tracking configuration mode. The keywords are as follows: |
|
Example: Router(config-track)# object 3 |
Specifies the object to be tracked. |
|
Example: Router(config-track)# threshold percentage up 30 |
Specifies the threshold percentage. |
|
Example: Router(config-track)# delay up 3 |
(Optional) Specifies a tracking delay in seconds between up and down states. |
|
Example: Router(config-track)# end |
Returns to privileged EXEC mode. |
Perform this task to configure a default delay value for a tracked list, a default object, and default threshold parameters for a tracked list.
Command or Action | Purpose | |
---|---|---|
|
Example: Router> enable |
Enables privileged EXEC mode. |
|
Example: Router# configure terminal |
Enters global configuration mode. |
|
Example: Router(config)# track 3 |
Enters tracking configuration mode. |
|
Example: Router(config-track)# default delay |
Specifies a default delay value for a tracked list, a default object, and default threshold parameters for a tracked list. |
|
Example: Router(config-track)# end |
Returns to privileged EXEC mode. |
Perform this task to configure a tracked list of Mobile IP application objects.
Command or Action | Purpose | |
---|---|---|
|
Example: Router> enable |
Enables privileged EXEC mode. |
|
Example: Router# configure terminal |
Enters global configuration mode. |
|
Example: Router(config)# track 100 application home-agent |
(Optional) Tracks the presence of Home Agent traffic on a router and enters tracking configuration mode. |
|
Example: Router(config-track)# exit |
Returns to global configuration mode. |
|
Example: Router(config)# track 100 application pdsn |
(Optional) Tracks the presence of Packet Data Serving Node (PDSN) traffic on a router tracking configuration mode. |
|
Example: Router(config-track)# exit |
Returns to global configuration mode. |
|
Example: Router(config)# track 100 application ggsn |
(Optional) Tracks the presence of Gateway GPRS Support Node (GGSN) traffic on a router tracking configuration mode. |
|
Example: Router(config)# end |
Returns to privileged EXEC mode. |
In the following example, the tracking process is configured to track the line-protocol state of GigabitEthernet interface 1/0/0. HSRP on GigabitEthernet interface 0/0/0 then registers with the tracking process to be informed of any changes to the line-protocol state of GigabitEthernet interface 1/0/0. If the line protocol on GigabitEthernet interface 1/0/0 goes down, the priority of the HSRP group is reduced by 10.
Router(config)# track 100 interface GigabitEthernet1/0/0 line-protocol ! Router(config)# interface GigabitEthernet0/0/0 Router(config-if)# ip address 10.1.0.21 255.255.0.0 Router(config-if)# standby 1 preempt Router(config-if)# standby 1 ip 10.1.0.1 Router(config-if)# standby 1 priority 110 Router(config-if)# standby 1 track 100 decrement 10
Router(config)# track 100 interface GigabitEthernet1/0/0 line-protocol ! Router(config)# interface GigabitEthernet0/0/0 Router(config-if)# ip address 10.1.0.22 255.255.0.0 Router(config-if)# standby 1 preempt Router(config-if)# standby 1 ip 10.1.0.1 Router(config-if)# standby 1 priority 105 Router(config-if)# standby 1 track 100 decrement 10
In the following example, the tracking process is configured to track the IP-routing capability of GigabitEthernet interface 1/0/0. HSRP on GigabitEthernet interface 0/0/0 then registers with the tracking process to be informed of any changes to the IP-routing state of GigabitEthernet interface 1/0/0. If the IP-routing state on GigabitEthernet interface 1/0/0 goes down, the priority of the HSRP group is reduced by 10.
If both serial interfaces are operational, Router A will be the HSRP active router because it has the higher priority. However, if IP on GigabitEthernet interface 1/0/0 in Router A fails, the HSRP group priority will be reduced and Router B will take over as the active router, thus maintaining a default virtual gateway service to hosts on the 10.1.0.0 subnet.
See the figure below for a sample topology.
Figure 1 | Topology for IP-Routing Support |
Router(config)# track 100 interface GigabitEthernet1/0/0 ip routing ! Router(config)# interface GigabitEthernet0/0/0 Router(config-if)# ip address 10.1.0.21 255.255.0.0 Router(config-if)# standby 1 preempt Router(config-if)# standby 1 ip 10.1.0.1 Router(config-if)# standby 1 priority 110 Router(config-if)# standby 1 track 100 decrement 10
Router(config)# track 100 interface GigabitEthernet1/0/0 ip routing ! Router(config)# interface GigabitEthernet0/0/0 Router(config-if)# ip address 10.1.0.22 255.255.0.0 Router(config-if)# standby 1 preempt Router(config-if)# standby 1 ip 10.1.0.1 Router(config-if)# standby 1 priority 105 Router(config-if)# standby 1 track 100 decrement 10
In the following example, the tracking process is configured to track the reachability of IP route 10.2.2.0/24:
Router(config)# track 100 ip route 10.2.2.0/24 reachability ! Router(config)# interface GigabitEthernet0/0/0 Router(config-if)# ip address 10.1.1.21 255.255.255.0 Router(config-if)# standby 1 preempt Router(config-if)# standby 1 ip 10.1.1.1 Router(config-if)# standby 1 priority 110 Router(config-if)# standby 1 track 100 decrement 10
Router(config)# track 100 ip route 10.2.2.0/24 reachability ! Router(config)# interface GigabitEthernet0/0/0 Router(config-if)# ip address 10.1.1.22 255.255.255.0 Router(config-if)# standby 1 preempt Router(config-if)# standby 1 ip 10.1.1.1 Router(config-if)# standby 1 priority 105 Router(config-if)# standby 1 track 100 decrement 10
In the following example, the tracking process is configured to track the threshold metric of IP route 10.2.2.0/24:
Router(config)# track 100 ip route 10.2.2.0/24 metric threshold ! Router(config)# interface GigabitEthernet0/0/0 Router(config-if)# ip address 10.1.1.21 255.255.255.0 Router(config-if)# standby 1 preempt Router(config-if)# standby 1 ip 10.1.1.1 Router(config-if)# standby 1 priority 110 Router(config-if)# standby 1 track 100 decrement 10
Router(config)# track 100 ip route 10.2.2.0/24 metric threshold ! Router(config)# interface GigabitEthernet0/0/0 Router(config-if)# ip address 10.1.1.22 255.255.255.0 Router(config-if)# standby 1 preempt Router(config-if)# standby 1 ip 10.1.1.1 Router(config-if)# standby 1 priority 105 Router(config-if)# standby 1 track 100 decrement 10
The following example shows how to configure IP host tracking for IP SLAs operation 1 in Cisco IOS releases prior to Cisco IOS Release 12.4(20)T, 12.2(33)SXI1, and 12.2(33)SRE:
Router(config)# ip sla 1 Router(config-ip-sla)# icmp-echo 10.51.12.4 Router(config-ip-sla-echo)# timeout 1000 Router(config-ip-sla-echo)# threshold 2 Router(config-ip-sla-echo)# frequency 3 Router(config-ip-sla-echo)# request-data-size 1400 Router(config-ip-sla-echo)# exit Router(config)# ip sla schedule 1 start-time now life forever Router(config-ip-sla)# track 2 rtr 1 state Router(config-ip-sla)# exit Router(config)# track 3 rtr 1 reachability Router(config-track)# exit Router(config)# interface ethernet0/1 Router(config-if)# ip address 10.21.0.4 255.255.0.0 Router(config-if)# no shutdown Router(config-if)# standby 3 ip 10.21.0.10 Router(config-if)# standby 3 priority 120 Router(config-if)# standby 3 preempt Router(config-if)# standby 3 track 2 decrement 10 Router(config-if)# standby 3 track 3 decrement 10
The following example shows how to configure IP host tracking for IP SLAs operation 1 in Cisco IOS Release 12.4(20)T, 12.2(33)SXI1, 12.2(33)SRE, and later releases:
Router(config)# ip sla 1 Router(config-ip-sla)# icmp-echo 10.51.12.4 Router(config-ip-sla-echo)# threshold 2 Router(config-ip-sla-echo)# timeout 1000 Router(config-ip-sla-echo)# frequency 3 Router(config-ip-sla-echo)# request-data-size 1400 Router(config-ip-sla-echo)# exit Router(config)# ip sla schedule 1 start-time now life forever Router(config)# track 2 ip sla 1 state Router(config-track)# exit Router(config)# track 3 ip sla 1 reachability Router(config-track)# exit Router(config)# interface ethernet0/1 Router(config-if)# ip address 10.21.0.4 255.255.0.0 Router(config-if)# no shutdown Router(config-if)# standby 3 ip 10.21.0.10 Router(config-if)# standby 3 priority 120 Router(config-if)# standby 3 preempt Router(config-if)# standby 3 track 2 decrement 10 Router(config-if)# standby 3 track 3 decrement 10
In the following example, a track list object is configured to track two GigabitEthernet interfaces when both interfaces are up and when either interface is down:
Router(config)# track 1 interface GigabitEthernet2/0/0 line-protocol Router(config)# track 2 interface GigabitEthernet2/1/0 line-protocol Router(config-track)# exit Router(config)# track 100 list boolean and Router(config-track)# object 1 Router(config-track)# object 2
In the following example, a track list object is configured to track two GigabitEthernet interfaces when either interface is up and when both interfaces are down:
Router(config)# track 1 interface GigabitEthernet2/0/0 line-protocol Router(config)# track 2 interface GigabitEthernet2/1/0 line-protocol Router(config-track)# exit Router(config)# track 101 list boolean or Router(config-track)# object 1 Router(config-track)# object 2
The following configuration example shows that tracked list 4 has two objects and one object state is negated (if the list is up, the list detects that object 2 is down):
Router(config)# track 4 list boolean and Router(config-track)# object 1 Router(config-track)# object 2 not
In the following example, three GigabitEtherent interfaces in tracked list 100 are configured with a threshold weight of 20 each. The down threshold is configured to 0 and the up threshold is configured to 40:
Router(config)# track 1 interface GigabitEthernet2/0/0 line-protocol Router(config)# track 2 interface GigabitEthernet2/1/0 line-protocol Router(config)# track 3 interface GigabitEthernet2/2/0 line-protocol Router(config-track)# exit Router(config)# track 100 list threshold weight Router(config-track)# object 1 weight 20 Router(config-track)# object 2 weight 20 Router(config-track)# object 3 weight 20 Router(config-track)# threshold weight up 40 down 0
In the example above the track-list object goes down only when all three serial interfaces go down, and comes up again only when at least two interfaces are up (because 20 + 20 >= 40). The advantage of this configuration is that it prevents the track-list object from coming up if two interfaces are down and the third interface is flapping.
The following configuration example shows that if object 1 and object 2 are down, then track list 4 is up, because object 3 satisfies the up threshold value of up 30. But, if object 3 is down, both objects 1 and 2 need to be up in order to satisfy the threshold weight.
Router(config)# track 4 list threshold weight Router(config-track)# object 1 weight 15 Router(config-track)# object 2 weight 20 Router(config-track)# object 3 weight 30 Router(config-track)# threshold weight up 30 down 10
This configuration may be useful to you if you have two small bandwidth connections (represented by object 1 and 2) and one large bandwidth connection (represented by object 3). Also the down 10 value means that once the tracked object is up, it will not go down until the threshold value is lower or equal to 10, which in this example means that all connections are down.
In the following example, four GigabitEthernet interfaces in track list 100 are configured for an up threshold percentage of 75. The track list is up when 75 percent of the interfaces are up and down when fewer than 75 percent of the interfaces are up.
Router(config)# track 1 interface GigabitEthernet2/0/0 line-protocol Router(config)# track 2 interface GigabitEthernet2/1/0 line-protocol Router(config)# track 3 interface GigabitEthernet2/2/0 line-protocol Router(config)# track 4 interface GigabitEthernet2/3/0 line-protocol Router(config-track)# exit Router(config)# track 100 list threshold percentage Router(config-track)# object 1 Router(config-track)# object 2 Router(config-track)# object 3 Router(config-track)# object 4 Router(config-track)# threshold percentage up 75
The following example shows how to configure EOT to track Mobile IP, GGSN, and PDSN traffic on a router:
Router(config)# track 1 application home-agent Router(config-track)# exit Router(config)# track 2 application ggsn Router(config-track)# exit Router(config)# track 3 application pdsn
Related Topic |
Document Title |
---|---|
Cisco IOS commands |
|
Embedded Event Manager |
Embedded Event Manager Overview |
HSRP concepts and configuration tasks |
Configuring HSRP |
GLBP concepts and configuration tasks |
Configuring GLBP |
IP SLAs commands |
Cisco IOS IP SLAs Command Reference |
VRRP concepts and configuration tasks |
Configuring VRRP |
GLBP, HSRP, and VRRP commands |
Cisco IOS IP Application Services Command Reference |
Standards |
Title |
---|---|
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature. |
— |
MIBs |
MIBs Link |
---|---|
No new or modified MIBs are supported by this feature, and support for existing MIBs has not been modified by this feature. |
To locate and download MIBs for selected platforms, Cisco software releases, and feature sets, use Cisco MIB Locator found at the following URL: |
RFCs |
Title |
---|---|
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature. |
— |
Description |
Link |
---|---|
The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password. |
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Table 3 | Feature Information for Enhanced Object Tracking |
Feature Name |
Releases |
Feature Configuration Information |
---|---|---|
Enhanced Tracking Support |
Cisco IOS XE 3.1.0SG 12.2(15)T 12.2(25)S 12.2(28)SB 12.2(33)SRA 12.2(33)SXH |
The Enhanced Tracking Support feature separates the tracking mechanism from HSRP and creates a separate standalone tracking process that can be used by other Cisco IOS processes as well as HSRP. This feature allows tracking of other objects in addition to the interface line-protocol state. The following commands were introduced or modified by this feature: debug track, delay tracking,ip vrf, show track, standby track, threshold metric, track interface,track ip route, track timer. |
FHRP--Enhanced Object Tracking Integration with Embedded Event Manager |
12.2(33)SRB 12.2(33)SXI 12.4(2)T |
EOT is now integrated with EEM to allow EEM to report on a status change of a tracked object and to allow EOT to track EEM objects. The following commands were introduced or modified by this feature: action track read, action track set, default-state,event resource, event rf,event track, show track, track stub. |
FHRP--Enhanced Object Tracking of IP SLAs Operations |
Cisco IOS XE 3.1.0SG 12.2(25)S 12.2(27)SBC 12.2(33)SRA 12.2(33)SXH 12.3(4)T 15.0(1)S |
This feature enables First Hop Redundancy Protocols (FHRPs) and other Enhanced Object Tracking (EOT) clients to track the output from IP SLAs objects and use the provided information to trigger an action. The following command was introduced by this feature: track rtr. |
FHRP--Enhanced Object Tracking Support for Mobile IP |
12.4(11)T |
The FHRP--Enhanced Object Tracking Support for Mobile IP feature provides new tracking objects needed by mobile wireless applications to track the presence of Home Agent, GGSN, or PDSN traffic on a router. The following command was introduced by this feature: track application. |
FHRP--EOT Deprecation of rtr Keyword |
12.2(33)SRE 12.2(33)SXI1 12.4(20)T |
This feature replaces the track rtr command with the track ip sla command. The following command was introduced by this feature: track ip sla. |
FHRP--Object Tracking List |
Cisco IOS XE 3.1.0SG 12.2(30)S 12.2(31)SB2 12.2(33)SRA 12.2(33)SXH 12.3(8)T 15.0(1)S |
This feature enhances the tracking capabilities to enable the configuration of a combination of tracked objects in a list, and a flexible method of combining objects using Boolean logic. The following commands were introduced or modified by this feature: show track, threshold percentage, threshold weight, track list, track resolution. |
EOT Support for Carrier Delay |
12.4(9)T |
The EOT Support for Carrier Delay feature enables Enhanced Object Tracking (EOT) to consider the carrier-delay timer when tracking the status of an interface. The following commands were introduced or modified by this feature: carrier-delay (tracking), show track. |
DHCP—Dynamic Host Configuration Protocol. DHCP is a protocol that delivers IP addresses and configuration information to network clients.
GGSN—Gateway GPRS Support Node. A wireless gateway that allows mobile cell phone users to access the public data network (PDN) or specified private IP networks. The GGSN function is implemented on the Cisco routers.
GLBP—Gateway Load Balancing Protocol. Provides automatic router backup for IP hosts that are configured with a single default gateway on an IEEE 802.3 LAN. Multiple first-hop routers on the LAN combine to offer a single virtual first-hop IP router while sharing the IP packet forwarding load. Other routers on the LAN may act as redundant (GLBP) routers that will become active if any of the existing forwarding routers fail.
GPRS—General Packet Radio Service. A 2.5G mobile communications technology that enables mobile wireless service providers to offer their mobile subscribers with packet-based data services over GSM networks.
GSM network—Global System for Mobile Communications network. A digital cellular technology that is used worldwide, predominantly in Europe and Asia. GSM is the world’s leading standard in digital wireless communications.
Home Agent—A Home Agent is a router on the home network of the Mobile Node (MN) that maintains an association between the home IP address of the MN and its care-of address, which is the current location of the MN on a foreign or visited network. The HA redirects packets by tunneling them to the MN while it is away from the home network.
HSRP—Hot Standby Router Protocol. Provides high network availability and transparent network topology changes. HSRP creates a Hot Standby router group with a lead router that services all packets sent to the Hot Standby address. The lead router is monitored by other routers in the group, and if it fails, one of these standby routers inherits the lead position and the Hot Standby group address.
IPCP—IP Control Protocol. The protocol used to establish and configure IP over PPP.
LCP—Link Control Protocol. The protocol used to establish, configure, and test data-link connections for use by PPP.
PDSN—Packet Data Serving Node. The Cisco PDSN is a standards-compliant, wireless gateway that enables packet data services in a Code Division Multiplex Access (CDMA) environment. Acting as an access gateway, the Cisco PDSN provides simple IP and Mobile IP access, foreign-agent support, and packet transport for Virtual Private Networks (VPN).
PPP—Point-to-Point Protocol. Provides router-to-router and host-to-network connections over synchronous and asynchronous circuits. PPP is most commonly used for dial-up Internet access. Its features include address notification, authentication via CHAP or PAP, support for multiple protocols, and link monitoring.
VRF—VPN routing and forwarding instance. A VRF consists of an IP routing table, a derived forwarding table, a set of interfaces that use the forwarding table, and a set of rules and routing protocols that determine what goes into the forwarding table. In general, a VRF includes the routing information that defines a customer VPN site that is attached to a provider edge router.
VRRP—Virtual Router Redundancy Protocol. Eliminates the single point of failure inherent in the static default routed environment. VRRP specifies an election protocol that dynamically assigns responsibility for a virtual router to one of the VRRP routers on a LAN. The VRRP router that controls the IP addresses associated with a virtual router is called the master, and forwards packets sent to these IP addresses. The election process provides dynamic failover in the forwarding responsibility should the master become unavailable. Any of the virtual router IP addresses on a LAN can then be used as the default first-hop router by end hosts.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.