Cisco Bug: CSCta59615 - Fix 32-bit overflow in timers_secs32.h
Sep 28, 2015
- Cisco IOS
Known Affected Releases
None Symptoms: After a router has been running continuously for more than 7 weeks, the last update time for routes in the routing table will be shown as "7w0d" when the route has recently been updated. For example: router#show ip route 192.168.116.152 Routing entry for 192.168.116.152/30 Known via "rip", distance 120, metric 1 Redistributing via bgp 6747, rip Advertised by bgp 6747 Last update from 192.168.117.154 on GigabitEthernet2/5.2583, 7w0d ago Routing Descriptor Blocks: * 192.168.117.154, from 192.168.117.154, 7w0d ago, via GigabitEthernet2/5.2583 Route metric is 1, traffic share count is 1 The following traceback may also be seen: Jan 4 10:42:33.357 ROUTER: %IPRT-3-NDB_STATE_ERROR: NDB state error (BAD EVENT STATE) (0x00) 192.168.116.152/30, state 7, event 2->1, nh_type 1 flags 4 -Process= "RIP Router", ipl= 0, pid= 494 If the traceback is seen the updated route will no longer be visible in the forwarding plane and will not be redistributed. Conditions: Router must be running continuously for 7 weeks. Conditions for the traceback to occur: Router must be running continuously for at least 7 weeks. A distance vector protocol is being used (e.g. RIP) and the route goes into holddown state and then comes out of holddown before the flushtimer has expired.
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)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases