Table Of Contents
Enhanced Object Tracking of Service Assurance Agent Operations
Information About Enhanced Object Tracking of Service Assurance Agent Operations
Feature Design of Enhanced Object Tracking of Service Assurance Agent Operations
Benefits of Enhanced Object Tracking Service Assurance Agent Operations
How to Configure Enhanced Object Tracking Integration with SAA
Enabling the SAA Tracking State
Enabling SAA Reachability Tracking
Configuration Examples for Enhanced Object Tracking of SAA Operations
Frame Relay DLCI Tracking: Example
Enhanced Object Tracking of Service Assurance Agent Operations
The Enhanced Object Tracking of Service Assurance Agent Operations feature enables first-hop routing protocols (FHRPs) and other enhanced object tracking clients to track the output from the Service Assurance Agent (SAA) objects and use the provided information to trigger an action.
FHRPs such as Hot Standby Router Protocol (HSRP), Virtual Router Redundancy Protocol (VRRP), and Gateway Load Balancing Protocol (GLBP) can now register interest in tracking an SAA operation with a tracking service and be notified when the tracked object changes state.
The Cisco SAA 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 SAA 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.
Feature History for the Enhanced Object Tracking of Service Assurance Agent Operations Feature
Release Modification12.3(4)T
This feature was introduced.
12.2(25)S
This feature was integrated into Cisco IOS Release 12.2(25)S.
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.
Contents
•
Information About Enhanced Object Tracking of Service Assurance Agent Operations
•
How to Configure Enhanced Object Tracking Integration with SAA
•
Configuration Examples for Enhanced Object Tracking of SAA Operations
Information About Enhanced Object Tracking of Service Assurance Agent Operations
Before you configure Enhanced Object Tracking of Service Assurance Agent Operations, you should understand the following concepts:
•
Feature Design of Enhanced Object Tracking of Service Assurance Agent Operations
•
Benefits of Enhanced Object Tracking Service Assurance Agent Operations
Feature Design of Enhanced Object Tracking of Service Assurance Agent Operations
Enhanced object tracking provides complete separation between the objects to be tracked and the action to be taken by a client when the state of a tracked object changes. Several protocols such as HSRP, VRRP, or GLBP can register an interest in an object with the tracking service, track the same object, and each take different action when the state of the object changes.
Each tracked object is identified by a unique number that is specified by using the tracking command-line interface (CLI). Client processes use this number to track a specific object.
The tracking service periodically polls the tracked objects and notes any change of value. The changes in the tracked object are communicated to interested clients, either immediately or after a specified delay. The object values are reported as either up or down.
Note
SAA was called the Response Time Reporter and is configured using the track rtr CLI command.
Every SAA 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 SAA operation can be state and reachability. The difference between these states relates to the acceptance of the OverThreshold return code. Table 1 shows the state and reachability aspects of SAA operations that can be tracked.
Table 1 Comparison of State and Reachability Operations
Tracking Return Code Track StateState
OK
(everything else)
Up
Down
Reachability
OK or OverThreshold
(everything else)
Up
Down
Benefits of Enhanced Object Tracking Service Assurance Agent Operations
•
Provides a scalable solution that allows FHRPs such as HSRP, VRRP, and GLBP to track objects.
•
Allows state and reachability tracking of SAA operations.
•
Enables static routes to be added or deleted, depending on the state of the tracked object.
•
Increases the availability and speed of recovery of a router system.
•
Decreases the number of outages and their duration.
How to Configure Enhanced Object Tracking Integration with SAA
This section contains the following procedures:
•
Enabling the SAA Tracking State (required)
•
Enabling SAA Reachability Tracking (required)
Enabling the SAA Tracking State
This task shows how to enable SAA operation return-code tracking.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
track object-number rtr saa-id state
4.
delay up seconds down seconds
5.
end
6.
show track object-number
DETAILED STEPS
Examples
The following example shows the state of the SAA tracking:
Router# show track 2Track 2Response Time Reporter 1 stateState is Down1 change, last change 00:00:47Latest operation return code: over thresholdLatest RTT (millisecs) 4Tracked by:HSRP Ethernet0/1 3Enabling SAA Reachability Tracking
This task describes how to track the reachability of an IP host.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
track object-number rtr saa-id reachability
4.
delay up seconds down seconds
5.
end
6.
show track object-number
DETAILED STEPS
Examples
The following example shows whether the route is reachable:
Router# show track 3Track 3Response Time Reporter 1 reachabilityReachability is Up1 change, last change 00:00:47Latest operation return code: over thresholdLatest RTT (millisecs) 4Tracked by:HSRP Ethernet0/1 3Configuration Examples for Enhanced Object Tracking of SAA Operations
This section provides the following configuration examples:
•
Frame Relay DLCI Tracking: Example
IP Host Tracking: Example
The following example shows SAA tracking on router 1:
rtr 1type echo protocol ipIcmpEcho 10.51.12.4timeout 1000frequency 3threshold 2request-data-size 1400rtr sched 1 start-time now life forever!track 2 rtr 1 statetrack 3 rtr 1 reachability!interface e0/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 10Router# show rtr operation-stateEntry number:1Modification time: 13:51:36.458 GMT Tue Nov 19 2002Number of operations attempted: 16Number of operations skipped: 0Current seconds lift in Life: ForeverOperational stat of entry: Activelast time this entry was reset; neverConnection loss occurred: FALSETimeout occurred: FALSEover thresholds occurred: TRUELatest RTT (milliseconds): 3latest operation start time: 13:52:21.460 GMT Tue Nov 19 2002Latest operation return code: Over thresholdTRR Values:RTTavg: 3 RTTMin: 3 RTTMax: 3NumOfTRR: 1 RTTSum: 3 RTTSum2: 9Frame Relay DLCI Tracking: Example
The following examples show SAA tracking of router 1:
rtr 1type frame-relay interface serial 2/0 dlci 16timeout 1000frequency 3rtr sched 1 start-time now life forever!track 2 rtr 1 state!interface serial2/0ip address 10.0.0.2 255.0.0.0encapsulation frame-relayframe-relay map ip 10.0.0.1 16no shutdown!interface e0/1ip address 10.21.0.2 255.255.0.0no shutdownstandby 3 ip 10.21.0.10standby 3 priority 120standby 3 preemptstandby 3 track 2 decrement 10Additional References
The following sections provide additional information related to the Enhanced Object Tracking of Service Assurance Agent Operations feature.
Related Documents
Related Topic Document TitleHSRP configuration tasks
"Configuring IP Services" chapter in the Cisco IOS IP Configuration Guide
HSRP commands: complete command syntax, command mode, defaults, usage guidelines, and examples
"IP Services Commands" chapter in the Cisco IOS IP Command Reference, Volume 1 of 4: Addressing and Services, Release 12.3 T
Enhanced Object Tracking documentation
Enhanced Object Tracking feature document, Release 12.2(15)T
Service Assurance Agent documentation
"Network Monitoring Using Service Assurance Agent" chapter in the Cisco IOS Configuration Fundamentals Configuration Guide
Standards
Standards TitleNo new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
—
MIBs
RFCs
RFCs TitleNo new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.
—
Technical Assistance
Command Reference
This section documents the new track rtr command only.
track rtr
To track the state of a Service Assurance Agent (SAA) operation and to enter tracking configuration mode, use the track rtr command in global configuration mode. To remove the tracking, use the no form of this command.
track object-number rtr saa-id {state | reachability}
no track object-number rtr saa-id {state | reachability}
Syntax Description
Defaults
SAA tracking is disabled.
Command Modes
Global configuration
Command History
Release Modification12.3(4)T
This command was introduced.
12.2(25)S
This command was integrated into Cisco IOS Release 12.2(25)S.
Usage Guidelines
Every SAA 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 SAA operation can be tracked: state and reachability. The difference between these relates to the acceptance of the OverThreshold return code. Table 2 shows the state and reachability aspects of SAA operations that can be tracked.
Table 2 Comparison of State and Reachability Operations
Tracking Return Code Track StateState
OK
(everything else)
Up
Down
Reachability
OK or over threshold
(everything else)
Up
Down
In the following example, the tracking process is configured to track the state of SAA router 2.
track 1 rtr 2 stateIn the following example, the SAA tracking process is configured to track the reachability of SAA router 3.
track 2 rtr 3 reachabilityGlossary
FHRP—first-hop routing protocol. FHRPs can be HSRP, VRRP, and GLBP.
GLBP—Gateway Load Balancing Protocol. Provides automatic router backup for IP hosts 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.
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.
RTR—Response Time Reporter. SAA was previously called RTR.
SAA—Service Assurance Agent. Monitors network performance by measuring response time, network resource availability, application performance, jitter (interpacket delay variance), connect time, throughput, and packet loss. Performance measurement statistics can be used for troubleshooting, for problem analysis, and for designing network topologies.
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 controlling 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's IP addresses on a LAN can then be used as the default first hop router by end hosts.
Note
Refer to Internetworking Terms and Acronyms for terms not included in this glossary.
Copyright © 2004 Cisco Systems, Inc. All rights reserved.

