IOS: IP SLA : SNMP : Router crashes and reloads if up for more than 497 days

CSCsa57468
rttmon-mib does not return getnext value when queried via snmp

Symptom:
Concord poller crashes when polling a router that has been configured with IP SLA. Infact this DDTS will surface when doing snmp gets for the objects mentioned in the Conditions section below coming from any NMS (e.g. Concord, IPM, Spectrum, etc.)

Conditions:
The SNMP GETNEXT request is sent to the router for the following OIDs:

• rttMonJitterStatsCompletions
• rttMonStatsCaptureCompletions
• rttMonStatsTotalsInitiations
• rttMonStatsCaptureEntry (rttMonStatsCaptureCompletion etc.)
• rttMonStatsCollectEntry
• rttMonStatsTotalsEntry
• rttMonJitterStatsEntry
• rttMonHTTPStatsEntry.

The router does not return the next index of these OIDs, but the same index. This happens only when the router has been up and running for longer than 497 days.

Affected IOS Versions:

• 12.2(15)T
• 12.2SXH

Workaround:
This problem is only happening when polling the CISCO-RTTMON-MIB via snmp get. Use the IOS CLI to avoid it.

Permanent Fix:
Upgrade the IOS version.

Fixed in:

• 12.3(14.12)M
  
• 12.4(1.5)M
  
• 12.2(33)SRC
  
• 12.2(40)SE
  
• 12.2(44)SE
  
• 12.3(11)T6
  
• 12.3(11)YW
  
• 12.3(14)T2
  
• 12.4(1.8)T
  
• 12.4(1a)M
  
• 12.2(33)SXI
  
• 12.2(32.8.80)SR
  
• 12.2(32.8.11)XID112.9
  
• 12.2(33.1.7)SXH
  
• 12.2(33)SXH2
  
• 12.2(33)SB
  
• 12.2(32.8.99a)SR133
  
• 12.2(32.8.11)XJC153.1