To track the state of a Cisco IOS IP Service Level Agreements (SLAs) operation and to enter tracking configuration mode, use the track ip sla command in global configuration mode. To remove the tracking, use the no form of this command.
no trackobject-number ip sla operation-number [state | reachability]
Object number representing the object to be tracked. The range is from 1 to 1000.
Number used for the identification of the IP SLAs operation you are tracking.
(Optional) Tracks the operation return code.
(Optional) Tracks whether the route is reachable.
IP SLAs tracking is disabled.
Global configuration (config)
This command was introduced. This command replaces the track rtr command.
This command was integrated into Cisco IOS Release 12.2(33)SXI1. This command replaces the track rtr command.
Cisco IOS XE Release 2.4
This command was integrated into Cisco IOS XE Release 2.4. This command replaces the track rtr command.
This command was integrated into Cisco IOS XE 12.2(33)SRE. This command replaces the track rtr command.
This command was modified. The valid range of the object-number argument increased to 1000.
This command was modified. The valid range for the object-number argument increased to 1000.
Every IP SLAs operation maintains an operation return-code value. This return code is interpreted by the tracking process. The return code may return OK, OverThreshold, and several other return codes. Different operations may 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 79 shows the state and reachability aspects of IP SLAs operations that can be tracked.
Table 79 Comparison of State and Reachability Operations
(all other return codes)
OK or over threshold
(all other return codes)
As of Cisco IOS Release 15.1(3)T, 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 is dependent upon variables such as traffic load and how other protocols are configured and run. The ability to use 1000 tracked objects is dependent upon the available CPU. Testing should be conducted on site to ensure that the service works under the specific site traffic conditions.
The following example shows how to configure the tracking process to track the state of IP SLAs operation 2:
Router(config)# track 1 ip sla 2 state
The following example shows how to configure the tracking process to track the reachability of IP SLAs operation 3:
Router(config)# track 2 ip sla 3 reachability
track ip route
Tracks the state of an IP route and enters tracking configuration mode.
*Plz dont forget to rate if this info is helpfull.