cc/td/doc/product/software/ios122sb/newft
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table Of Contents

Enhanced Object Tracking of IP SLAs Operations

Contents

Information About Enhanced Object Tracking of IP SLAs Operations

Feature Design of Enhanced Object Tracking of IP SLAs Operations

Benefits of Enhanced Object Tracking IP SLAs Operations

How to Configure Enhanced Object Tracking Integration with IP SLAs

Tracking the State of an IP SLAs Operation

Tracking the Reachability of an IP SLAs IP Host

Configuration Examples for Enhanced Object Tracking of IP SLAs Operations

IP Host Tracking: Example

Frame Relay DLCI Tracking: Example

Additional References

Related Documents

Standards

MIBs

RFCs

Technical Assistance

Command Reference

track rtr

Glossary


Enhanced Object Tracking of IP SLAs Operations


The Enhanced Object Tracking of IP SLAs Operations feature enables first-hop routing protocols (FHRPs) and other enhanced object tracking clients to track the output from Cisco IOS IP Service Level Agreements (SLAs) 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 IP SLAs operation with a tracking service and be notified when the tracked object changes state.

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.

History for the Enhanced Object Tracking of IP SLAs Operations Feature

Release
Modification

12.2(27)SBC

This feature was introduced.


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 IP SLAs Operations

How to Configure Enhanced Object Tracking Integration with IP SLAs

Configuration Examples for Enhanced Object Tracking of IP SLAs Operations

Additional References

Command Reference

Glossary

Information About Enhanced Object Tracking of IP SLAs Operations

Before you configure the Enhanced Object Tracking of IP SLAs Operations feature, you should understand the following concepts:

Feature Design of Enhanced Object Tracking of IP SLAs Operations

Benefits of Enhanced Object Tracking IP SLAs Operations

Feature Design of Enhanced Object Tracking of IP SLAs 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.

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 1 shows the state and reachability aspects of IP SLAs operations that can be tracked.

Table 1 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


Benefits of Enhanced Object Tracking IP SLAs Operations

Provides a scalable solution that allows FHRPs such as HSRP, VRRP, and GLBP to track objects.

Allows state and reachability tracking of IP SLAs 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 IP SLAs

This section contains the following tasks:

Tracking the State of an IP SLAs Operation (required)

Tracking the Reachability of an IP SLAs IP Host (required)

Tracking the State of an IP SLAs Operation

Perform this task to track the state of an IP SLAs operation.

SUMMARY STEPS

1. enable

2. configure terminal

3. track object-number rtr operation-number state

4. delay up seconds down seconds

5. end

6. show track object-number

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

track object-number rtr operation-number state

Example:

Router(config)# track 2 rtr 4 state

Tracks the state of an IP SLAs object and enters tracking configuration mode.

Step 4 

delay 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.

Use this command to verify the configuration. See the display output in the "Examples" section of this task.


Examples

The following example shows the state of the IP SLAs tracking:

Router# show track 2

Track 2
   Response Time Reporter 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

Tracking the Reachability of an IP SLAs IP Host

Perform this task to track the reachability of an IP host.

SUMMARY STEPS

1. enable

2. configure terminal

3. track object-number rtr operation-number reachability

4. delay up seconds down seconds

5. end

6. show track object-number

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

track object-number rtr operation-number reachability

Example:

Router(config)# track 3 rtr 4 reachability

Tracks the reachability of an IP SLAs IP host and enters tracking configuration mode.

Step 4 

delay 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.

Use this command to verify the configuration. See the display output in the "Examples" section of this task.


Examples

The following example shows whether the route is reachable:

Router# show track 3

Track 3
   Response Time Reporter 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

Configuration Examples for Enhanced Object Tracking of IP SLAs Operations

This section provides the following configuration examples:

IP Host Tracking: Example

Frame Relay DLCI Tracking: Example

IP Host Tracking: Example

The following example shows how to configure IP host tracking for IP SLAs operation 1:

rtr 1
   type echo protocol ipIcmpEcho 10.51.12.4
    timeout 1000
    frequency 3
    threshold 2
    request-data-size 1400
rtr sched 1 start-time now life forever
!
track 2 rtr 1 state
track 3 rtr 1 reachability
!
interface ethernet0/1
   ip address 10.21.0.4 255.255.0.0
   no shutdown
   standby 3 ip 10.21.0.10d
   standby 3 priority 120
   standby 3 preempt
   standby 3 track 2 decrement 10
   standby 3 track 3 decrement 10


Router# show rtr operational-state

Entry number:1
Modification time: 13:51:36.458 GMT Tue Nov 19 2002
Number of operations attempted: 16
Number of operations skipped: 0
Current seconds lift in Life: Forever
Operational stat of entry: Active
last time this entry was reset; never
Connection loss occurred: FALSE
Timeout occurred: FALSE
over thresholds occurred: TRUE
Latest RTT (milliseconds): 3
latest operation start time: 13:52:21.460 GMT Tue Nov 19 2002
Latest operation return code: Over threshold
TRR Values:
RTTavg: 3        RTTMin: 3        RTTMax: 3
NumOfTRR: 1      RTTSum: 3        RTTSum2: 9

Frame Relay DLCI Tracking: Example

The following example shows how to configure Frame Relay DLCI tracking for IP SLAs operation 1:

rtr 1
   type frame-relay interface serial 2/0 dlci 16
    timeout 1000
    frequency 3
rtr sched 1 start-time now life forever
!
track 2 rtr 1 state
!
interface serial2/0
   ip address 10.0.0.2 255.0.0.0
   encapsulation frame-relay
   frame-relay map ip 10.0.0.1 16
    no shutdown
!
interface ethernet0/1
   ip address 10.21.0.2 255.255.0.0
   no shutdown
   standby 3 ip 10.21.0.10
   standby 3 priority 120
   standby 3 preempt
   standby 3 track 2 decrement 10

Additional References

The following sections provide additional information related to the Enhanced Object Tracking of IP SLAs Operations feature.

Related Documents

Related Topic
Document Title

Enhanced Object Tracking concepts and configuration tasks

"Configuring Enhanced Object Tracking" chapter of the Cisco IOS IP Application Services Configuration Guide, Release 12.4

GLBP, HSRP, and VRRP commands: complete command syntax, command mode, command history, defaults, usage guidelines, and examples

Cisco IOS IP Application Services Command Reference, Release 12.4T


Standards

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
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 IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:

http://www.cisco.com/go/mibs


RFCs

RFCs
Title

No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.


Technical Assistance

Description
Link

Technical Assistance Center (TAC) home page, containing 30,000 pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content.

http://www.cisco.com/public/support/tac/home.shtml


Command Reference

This section documents one new command only.

track rtr

track rtr

To track the state of a Cisco IOS IP Service Level Agreements (SLAs) 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 operation-number {state | reachability}

no track object-number rtr operation-number {state | reachability}

Syntax Description

object-number

Object number representing the object to be tracked. The range is from 1 to 500.

operation-number

Number used for the identification of the IP SLAs operation you are tracking.

state

Tracks the operation return code.

reachability

Tracks whether the route is reachable.


Defaults

IP SLAs tracking is disabled.

Command Modes

Global configuration

Command History

Release
Modification

12.3(4)T

This command was introduced.

12.2(25)S

This command was integrated into Cisco IOS Release 12.2(25)S.

12.2(27)SBC

This command was integrated into Cisco IOS Release 12.2(27)SBC.


Usage Guidelines

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 2 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 over threshold

(all other return codes)

Up

Down


Examples

The following example shows how to configure the tracking process to track the state of IP SLAs operation 2:

track 1 rtr 2 state

The following example shows how to configure the tracking process to track the reachability of IP SLAs operation 3:

track 2 rtr 3 reachability

Glossary

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.

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, which 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.



hometocprevnextglossaryfeedbacksearchhelp

Posted: Mon Sep 12 22:31:15 PDT 2005
All contents are Copyright © 1992--2005 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.