Guest

Preview Tool

Cisco Bug: CSCvu22392 - Object Tracking - state transitions not delayed for configured values

Last Modified

Sep 02, 2020

Products (11)

  • Cisco ASR 9000 Series Aggregation Services Routers
  • Cisco ASR 9910 Router
  • Cisco ASR 9922 Router
  • Cisco IOS XR Software
  • Cisco ASR 9010 Router
  • Cisco ASR 9904 Router
  • Cisco ASR 9006 Router
  • Cisco ASR 9901 Router
  • Cisco ASR 9001 Router
  • Cisco ASR 9906 Router
View all products in Bug Search Tool Login Required

Known Affected Releases

6.5.3.BASE

Description (partial)

Symptom:
The timers are not programmed in accordance with the configuration:
track <>
type rtr 5 reachability
delay up 90
delay down 90

Log:
09:03:05.704 utc: Reachability is DOWN
09:03:06.895 utc: Reachability is DOWN, delayed Up (1 secs remaining) <<<<<<<<<<< this is wrong as it should be 90 not 2 secs
09:03:08.067 utc: Reachability is DOWN, delayed Up (0 secs remaining)
09:03:09.220 utc: Reachability is UP
 
Trace:
Apr 23 09:03:06.867 ot/detail 0/RSP0/CPU0 t1  [TP18] Track TRACK_NAME state in SysDB Track_Down -> Track_Up will be set after UP delay 2 <<<< wrong as should be 90 not 2

Conditions:
Steps to repro the issue:
1)	create the track with delay up/down (without giving the track type)
e.g. track TRACK_NAME
        ! delay up 90
        ! delay down 90
       commit
2)	config track type in same track
e.g. track TRACK_NAME
        ! type rtr 1 reachability
        commit
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.