Downloads |
Table Of Contents
Configuring Enhanced Object Tracking
Information About Enhanced Object Tracking
Feature Design of Enhanced Object Tracking
Enhanced Object Tracking and Embedded Event Manager
Enhanced Object Tracking for Mobile IP Applications
Benefits of Enhanced Object Tracking
How to Configure Enhanced Object Tracking
Tracking the Line-Protocol State of an Interface
Tracking the IP-Routing State of an Interface
Tracking IP-Route Reachability
Tracking the Threshold of IP-Route Metrics
Tracking the State of an IP SLAs Operation
Tracking the Reachability of an IP SLAs IP Host
Configuring a Tracked List and Boolean Expression
Configuring a Tracked List and Threshold Weight
Configuring a Tracked List and Threshold Percentage
Configuring the Track List Defaults
Configuring Tracking for Mobile IP Applications
Configuration Examples for Enhanced Object Tracking
Interface Line Protocol: Example
IP-Route Reachability: Example
IP-Route Threshold Metric: Example
IP SLAs IP Host Tracking: Example
Boolean Expression for a Tracked List: Example
Threshold Weight for a Tracked List: Example
Threshold Percentage for a Tracked List: Example
Mobile IP Application Tracking: Example
Feature Information for Enhanced Object Tracking
Configuring Enhanced Object Tracking
First Published: May 2, 2005Last Updated: March 31, 2009Before 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 as well as 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 now register its interest in tracking objects and then be notified when the tracked object changes state.
Finding Feature Information
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 for Enhanced Object Tracking" section.
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Information About Enhanced Object Tracking
•
•
•
Information About Enhanced Object Tracking
Before you configure the Enhanced Object Tracking feature, you should understand the following concepts:
•
•
•
•
•
Feature Design of Enhanced Object Tracking
Enhanced Object Tracking 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 command-line interface (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 also 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:
•
•
•
Enhanced Object Tracking and Embedded Event Manager
Beginning with Cisco IOS Release 12.4(2)T, 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 IOS Network Management Configuration Guide for more information on how EOT works with EEM.
EOT Support for Carrier Delay
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.
Enhanced Object Tracking for Mobile IP Applications
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:
Cisco IOS Mobile Wireless Home Agent Configuration Guide
Cisco IOS Mobile Wireless Gateway GPRS Support Node Configuration Guide
Cisco IOS Mobile Wireless Packet Data Serving Node Configuration Guide
Cisco IOS IP Mobility Configuration Guide
Benefits of Enhanced Object Tracking
•
•
•
How to Configure Enhanced Object Tracking
The following sections describe configuration tasks for Enhanced Object Tracking:
•
•
•
•
•
•
•
•
•
•
Tracking the Line-Protocol State of an Interface
Perform this task to track the line-protocol state of an interface.
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. See the "Tracking the IP-Routing State of an Interface" section for more information.
You can optionally configure EOT to consider the carrier-delay timer when tracking the line-protocol state of an interface by using the carrier-delay command in tracking configuration mode.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
track timer interface seconds
Example:Router(config)# track timer interface 5
(Optional) Specifies the interval in which the tracking process polls the tracked object.
•
Step 4
track object-number interface type number line-protocol
Example:Router(config)# track 3 interface ethernet 0/1 line-protocol
Tracks the line-protocol state of an interface and enters tracking configuration mode.
Step 5
carrier-delay
Example:Router(config-track)# carrier-delay
(Optional) Enables EOT to consider the carrier-delay timer when tracking the status of an interface.
Step 6
delay {up seconds [down seconds] | [up seconds] down seconds}
Example:Router(config-track)# delay up 30
(Optional) Specifies a period of time (in seconds) to delay communicating state changes of a tracked object.
Step 7
end
Example:Router(config-track)# end
Exits to privileged EXEC mode.
Step 8
show track object-number
Example:Router# show track 3
(Optional) Displays tracking information.
•
Examples
The following example shows the state of the line protocol on an interface when it is tracked:
Router# show track 3Track 3Interface Ethernet0/1 line-protocolLine protocol is Up1 change, last change 00:00:05Tracked by:HSRP Ethernet0/3 1Tracking the IP-Routing State of an Interface
Perform this task to track the IP-routing state of an interface. An IP-routing object is considered up when the following criteria exist:
•
•
•
Interface IP routing will go down when one of the following criteria exist:
•
•
•
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 Point-to-Point Protocol (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 optionally configure EOT 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.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
track timer interface seconds
Example:Router(config)# track timer interface 5
(Optional) Specifies the interval in which the tracking process polls the tracked object.
•
Step 4
track object-number interface type number ip routing
Example:Router(config)# track 1 interface ethernet 0/1 ip routing
Tracks the IP-routing state of an interface and enters tracking configuration mode.
•
Step 5
carrier-delay
Example:Router(config-track)# carrier-delay
(Optional) Enables EOT to consider the carrier-delay timer when tracking the status of an interface.
Step 6
delay {up seconds [down seconds] | [up seconds] down seconds}
Example:Router(config-track)# delay up 30
(Optional) Specifies a period of time (in seconds) to delay communicating state changes of a tracked object.
Step 7
end
Example:Router(config-track)# end
Returns to privileged EXEC mode.
Step 8
show track object-number
Example:Router# show track 1
Displays tracking information.
•
Examples
The following example shows the state of IP routing on an interface when it is tracked:
Router# show track 1Track 1Interface Ethernet0/1 ip routingIP routing is Up1 change, last change 00:01:08Tracked by:HSRP Ethernet0/3 1Tracking IP-Route Reachability
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.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
track timer ip route seconds
Example:Router(config)# track timer ip route 20
(Optional) Specifies the interval in which the tracking process polls the tracked object.
•
Step 4
track object-number ip route ip-address/prefix-length reachability
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.
Step 5
delay {up seconds [down seconds] | [up seconds] down seconds}
Example:Router(config-track)# delay up 30
(Optional) Specifies a period of time (in seconds) to delay communicating state changes of a tracked object.
Step 6
ip vrf vrf-name
Example:Router(config-track)# ip vrf VRF2
(Optional) Configures a VPN routing and forwarding (VRF) table.
Step 7
end
Example:Router(config-track)# end
Returns to privileged EXEC mode.
Step 8
show track object-number
Example:Router# show track 4
(Optional) Displays tracking information.
•
Examples
The following example shows the state of the reachability of an IP route when it is tracked:
Router# show track 4Track 4IP route 10.16.0.0 255.255.0.0 reachabilityReachability is Up (RIP)1 change, last change 00:02:04First-hop interface is Ethernet0/1Tracked by:HSRP Ethernet0/3 1Tracking the Threshold of IP-Route Metrics
Perform this task to track the threshold of IP route metrics.
Scaled Route Metrics
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, route metric values are normalized 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. Table 1 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
Static
10
Enhanced Interior Gateway Routing Protocol (EIGRP)
2560
Open Shortest Path First (OSPF)
1
Intermediate System-to-Intermediate System (IS-IS)
10
1 RIP is scaled directly to the range from 0 to 255 because its
maximum metric is less than 255.
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 go above the maximum limit with a 2-Mbps 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.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
track timer ip route seconds
Example:Router(config)# track timer ip route 20
(Optional) Specifies the interval in which the tracking process polls the tracked object.
•
Step 4
track resolution ip route {eigrp resolution-value | isis resolution-value | ospf resolution-value | static resolution-value}
Example:Router(config)# track resolution ip route eigrp 300
(Optional) Specifies resolution parameters for a tracked object.
•
Step 5
track object-number ip route ip-address/ prefix-length metric threshold
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.
•
•
Step 6
delay {up seconds [down seconds] | [up seconds] down seconds}
Example:Router(config-track)# delay up 30
(Optional) Specifies a period of time (in seconds) to delay communicating state changes of a tracked object.
Step 7
ip vrf vrf-name
Example:Router(config-track)# ip vrf VRF1
(Optional) Configures a VRF table.
Step 8
threshold metric {up number [down number] | down number [up number]}
Example:Router(config-track)# threshold metric up 254 down 255
(Optional) Sets a metric threshold other than the default value.
Step 9
end
Example:Router(config-track)# end
Exits to privileged EXEC mode.
Step 10
show track object-number
Example:Router# show track 6
(Optional) Displays tracking information.
•
Examples
The following example shows the metric threshold of an IP route when it is tracked:
Router# show track 6Track 6IP route 10.16.0.0 255.255.0.0 metric thresholdMetric threshold is Up (RIP/6/102)1 change, last change 00:00:08Metric threshold down 255 up 254First-hop interface is Ethernet0/1Tracked by:HSRP Ethernet0/3 1Tracking IP SLAs Operations
Perform the following tasks to track Cisco IOS IP Service Level Agreements (SLAs) operations:
•
•
Object tracking of IP 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 relates to the acceptance of the OverThreshold return code. Table 2 shows the state and reachability aspects of IP SLAs operations that can be tracked.
Table 2 Comparison of State and Reachability Operations
State
OK
(all other return codes)
Up
Down
Reachability
OK or OverThreshold
(all other return codes)
Up
Down
Tracking the State of an IP SLAs Operation
Perform this task to track the state of an IP SLAs operation.
SUMMARY STEPS
1.
2.
3.
or
track object-number ip sla operation-number state4.
5.
6.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
Cisco IOS Releases Prior to 12.4(20)T and 12.2(33)SXI1
track object-number rtr operation-number state
Cisco IOS Release 12.4(20)T, 12.2(33)SXI1 or Later Releases
track object-number ip sla operation-number state
Example: Cisco IOS Releases Prior to 12.4(20)T and 12.2(33)SXI1:Router(config)# track 2 rtr 4 state
Example: Cisco IOS Release 12.4(20)T, 12.2(33)SXI1 or Later ReleasesRouter(config)# track 2 ip sla 4 state
Tracks the state of an IP SLAs object and enters tracking configuration mode.
Note
Step 4
delay {up seconds [down seconds] | [up seconds] down seconds}
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.
Step 5
end
Example:Router(config-track)# end
Exits to privileged EXEC mode.
Step 6
show track object-number
Example:Router# show track 2
(Optional) Displays tracking information.
•
Examples
The following example shows the state of the IP SLAs tracking:
Router# show track 2Track 2IP SLA 1 stateState is Down1 change, last change 00:00:47Latest operation return code: over thresholdLatest RTT (millisecs) 4Tracked by:HSRP Ethernet0/1 3Tracking the Reachability of an IP SLAs IP Host
Perform this task to track the reachability of an IP host.
SUMMARY STEPS
1.
2.
3.
or
track object-number ip sla operation-number reachability4.
5.
6.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
Cisco IOS Releases Prior to 12.4(20)T and 12.2(33)SXI1:
track object-number rtr operation-number reachability
Cisco IOS Release 12.4(20)T, 12.2(33)SXI1 or Later Releases
track object-number ip sla operation-number reachability
Example: Cisco IOS Releases Prior to 12.4(20)T and 12.2(33)SXI1:Router(config)# track 2 rtr 4 reachability
Example: Cisco IOS Release 12.4(20)T, 12.2(33)SXI1 or Later ReleasesRouter(config)# track 2 ip sla 4 reachability
Tracks the reachability of an IP SLAs IP host and enters tracking configuration mode.
Note
Step 4
delay {up seconds [down seconds] | [up seconds] down seconds}
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.
Step 5
end
Example:Router(config-track)# end
Exits to privileged EXEC mode.
Step 6
show track object-number
Example:Router# show track 3
(Optional) Displays tracking information.
•
Examples
The following example shows whether the route is reachable:
Router# show track 3Track 3IP SLA 1 reachabilityReachability is Up1 change, last change 00:00:47Latest operation return code: over thresholdLatest RTT (millisecs) 4Tracked by:HSRP Ethernet0/1 3Configuring a Tracked List and Boolean Expression
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 tracking two interfaces using the "and" operator, up means that both interfaces are up, and down means that either interface is down.
You may also configure a tracked list state to be measured using a weight or percentage threshold. See "Configuring a Tracked List and Threshold Weight" section and "Configuring a Tracked List and Threshold Percentage" section.
Note
Prerequisites
An object must exist before it can be added to a tracked list.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Configuring a Tracked List and Threshold Weight
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 its objects. A tracked list contains one or more objects. Using a threshold weight, the state of each object is determined 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.
Prerequisites
An object must exist before it can be added to a tracked list.
Restrictions
You cannot use the Boolean "not" operator in a weight or percentage threshold list.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
DETAILED STEPS
Configuring a Tracked List and Threshold Percentage
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. Using the threshold percentage, the state of the list is determined 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 "Configuring a Tracked List and Boolean Expression" section and "Configuring a Tracked List and Threshold Weight" section.
Prerequisites
An object must exist before it can be added to a tracked list.
Restrictions
You cannot use the Boolean "not" operator in a weight or percentage threshold list.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
DETAILED STEPS
Configuring the Track List Defaults
Perform this task to configure a default delay value for a tracked list, a default object, and default threshold parameters for a tracked list.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Configuring Tracking for Mobile IP Applications
Perform this task to configure a tracked list of Mobile IP application objects.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
Configuration Examples for Enhanced Object Tracking
This section provides the following configuration examples:
•
•
•
•
•
•
•
•
•
Interface Line Protocol: Example
The following example is very similar to the IP-routing example. Instead, the tracking process is configured to track the line-protocol state of serial interface 1/0. HSRP on Ethernet interface 0/0 then registers with the tracking process to be informed of any changes to the line-protocol state of serial interface 1/0. If the line protocol on serial interface 1/0 goes down, the priority of the HSRP group is reduced by 10.
Router A Configuration
track 100 interface serial1/0 line-protocol!interface Ethernet0/0ip address 10.1.0.21 255.255.0.0standby 1 preemptstandby 1 ip 10.1.0.1standby 1 priority 110standby 1 track 100 decrement 10Router B Configuration
track 100 interface serial1/0 line-protocol!interface Ethernet0/0ip address 10.1.0.22 255.255.0.0standby 1 preemptstandby 1 ip 10.1.0.1standby 1 priority 105standby 1 track 100 decrement 10Interface IP Routing: Example
In the following example, the tracking process is configured to track the IP-routing capability of serial interface 1/0. HSRP on Ethernet interface 0/0 then registers with the tracking process to be informed of any changes to the IP-routing state of serial interface 1/0. If the IP-routing state on serial interface 1/0 goes down, the priority of the HSRP group is reduced by 10.
In the following example, EOT is configured to take the carrier-delay timer into consideration when tracking the state of serial interface 1/0.
If both serial interfaces are operational, Router A will be the HSRP active router because it has the higher priority. However, if IP on serial interface 1/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 Figure 1 for a sample topology.
Figure 1 Topology for IP-Routing Support
Router A Configuration
track 100 interface serial1/0 ip routingcarrier-delay!interface Ethernet0/0ip address 10.1.0.21 255.255.0.0standby 1 preemptstandby 1 ip 10.1.0.1standby 1 priority 110standby 1 track 100 decrement 10Router B Configuration
track 100 interface serial1/0 ip routingcarrier-delay!interface Ethernet0/0ip address 10.1.0.22 255.255.0.0standby 1 preemptstandby 1 ip 10.1.0.1standby 1 priority 105standby 1 track 100 decrement 10IP-Route Reachability: Example
In the following example, the tracking process is configured to track the reachability of IP route 10.2.2.0/24:
Router A Configuration
track 100 ip route 10.2.2.0/24 reachability!interface Ethernet0/0ip address 10.1.1.21 255.255.255.0standby 1 preemptstandby 1 ip 10.1.1.1standby 1 priority 110standby 1 track 100 decrement 10Router B Configuration
track 100 ip route 10.2.2.0/24 reachability!interface Ethernet0/0ip address 10.1.1.22 255.255.255.0standby 1 preemptstandby 1 ip 10.1.1.1standby 1 priority 105standby 1 track 100 decrement 10IP-Route Threshold Metric: Example
In the following example, the tracking process is configured to track the threshold metric of IP route 10.2.2.0/24:
Router A Configuration
track 100 ip route 10.2.2.0/24 metric threshold!interface Ethernet0/0ip address 10.1.1.21 255.255.255.0standby 1 preemptstandby 1 ip 10.1.1.1standby 1 priority 110standby 1 track 100 decrement 10Router B Configuration
track 100 ip route 10.2.2.0/24 metric threshold!interface Ethernet0/0ip address 10.1.1.22 255.255.255.0standby 1 preemptstandby 1 ip 10.1.1.1standby 1 priority 105standby 1 track 100 decrement 10IP SLAs IP Host Tracking: Example
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 and Cisco IOS Release 12.2(33)SXI1:
ip sla 1icmp-echo 10.51.12.4timeout 1000frequency 3threshold 2request-data-size 1400exitip sla schedule 1 start-time now life foreverexittrack 2 rtr 1 statetrack 3 rtr 1 reachabilityexitinterface ethernet0/1ip address 10.21.0.4 255.255.0.0no shutdownstandby 3 ip 10.21.0.10dstandby 3 priority 120standby 3 preemptstandby 3 track 2 decrement 10standby 3 track 3 decrement 10The following example shows how to configure IP host tracking for IP SLAs operation 1 in Cisco IOS Release 12.4(20)T, Cisco IOS Release 12.2(33)SXI1 and later releases:
ip sla 1icmp-echo 10.51.12.4timeout 1000frequency 3threshold 2request-data-size 1400exitip sla schedule 1 start-time now life foreverexittrack 2 ip sla 1 statetrack 3 ip sla 1 reachabilityexitinterface ethernet0/1ip address 10.21.0.4 255.255.0.0no shutdownstandby 3 ip 10.21.0.10dstandby 3 priority 120standby 3 preemptstandby 3 track 2 decrement 10standby 3 track 3 decrement 10Boolean Expression for a Tracked List: Example
In the following example, a track list object is configured to track two serial interfaces when both serial interfaces are up and when either serial interface is down:
track 1 interface serial2/0 line-protocoltrack 2 interface serial2/1 line-protocolexittrack 100 list boolean andobject 1object 2In the following example, a track list object is configured to track two serial interfaces when either serial interface is up and when both serial interfaces are down:
track 1 interface serial2/0 line-protocoltrack 2 interface serial2/1 line-protocolexittrack 101 list boolean orobject 1object 2The 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):
track 4 list boolean andobject 1object 2 notThreshold Weight for a Tracked List: Example
In the following example, three serial 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:
track 1 interface serial2/0 line-protocoltrack 2 interface serial2/1 line-protocoltrack 3 interface serial2/2 line-protocolexittrack 100 list threshold weightobject 1 weight 20object 2 weight 20object 3 weight 20threshold weight down 0 up 40The above example means that the track-list object goes down only when all three serial interfaces go down, and only comes up again when at least two serial interfaces are up (since 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.
track 4 list threshold weightobject 1 weight 15object 2 weight 20object 3 weight 30threshold weight up 30 down 10This 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.
Threshold Percentage for a Tracked List: Example
In the following example, four serial interfaces in track list 100 are configured for an up threshold percentage of 75. The track list is up when 75 percent of the serial interfaces are up and down when fewer than 75 percent of the serial interfaces are up.
track 1 interface serial2/0 line-protocoltrack 2 interface serial2/1 line-protocoltrack 3 interface serial2/2 line-protocoltrack 4 interface serial2/3 line-protocolexittrack 100 list threshold percentageobject 1object 2object 3object 4threshold percentage up 75Mobile IP Application Tracking: Example
The following example shows how to configure EOT to track Mobile IP, GGSN, and PDSN traffic on a router:
track 1 application home-agentexittrack 2 application ggsnexittrack 3 application pdsnAdditional References
The following sections provide references related to Enhanced Object Tracking.
Related Documents
Standards
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
—
MIBs
RFCs
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.
—
Technical Assistance
Feature Information for Enhanced Object Tracking
Table 3 lists the features in this module and provides links to specific configuration information. Only features that were introduced or modified in Cisco IOS Releases 12.2(1) or 12.0(3)S or later appear in the table.
Not all commands may be available in your Cisco IOS software release. For details on when support for specific commands was introduced, see the command reference documents.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Table 3 Feature Information for Enhanced Object Tracking
Enhanced Tracking Support
12.2(15)T 12.2(25)S
12.2(28)SB
12.2(33)SRA
12.2(33)SXHThe 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 sections provide information about this feature:
•
•
•
•
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 of IP SLAs Operations
12.3(4)T 12.2(25)S
12.2(27)SBC
12.2(33)SRA
12.2(33)SXHThis 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 section provides information about this feature:
•
The following command was introduced by this feature: track rtr.
FHRP—EOT Deprecation of rtr Keyword
12.4(20)T
12.2(33)SXI1This feature replaces the track rtr command with the track ip sla command.
The following sections provide information about this feature:
•
The following command was introduced by this feature: track ip sla.
FHRP—Object Tracking List
12.3(8)T
12.2(30)S
12.2(33)SRA
12.2(31)SB2
12.2(33)SXHThis 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 sections provide information about this feature:
•
•
•
•
The following commands were introduced or modified by this feature: show track, threshold percentage, threshold weight, track list, track resolution.
FHRP—Enhanced Object Tracking Integration with Embedded Event Manager
12.4(2)T
12.2(33)SRB
12.2(33)SXIEOT 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 section provides information about this feature:
•
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 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 sections provide information about this feature:
•
•
•
The following command was introduced by this feature: track application.
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 sections provide information about this feature:
•
•
•
•
The following commands were introduced or modified by this feature: carrier-delay (tracking), show track.
Glossary
DHCP—Dynamic Host Configuration Protocol. DHCP is a protocol that delivers IP addresses and configuration information to network clients.
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.
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.
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.
CCDE, CCSI, CCENT, Cisco Eos, Cisco HealthPresence, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Stackpower, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website 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. (0903R)
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.
©2005-2009 Cisco Systems, Inc. All rights reserved.
