Description

SNMP ifLastChange show bogus results on some interfaces.

Symptoms

root@JTAC> show snmp mib walk ascii ifLastChange

ifLastChange.4 = 272

ifLastChange.5 = 272

ifLastChange.193 = 893589

ifLastChange.194 = 893589

ifLastChange.509 = 272

ifLastChange.511 = 1054

ifLastChange.513 = 13116

ifLastChange.525 = 3243139646

ifLastChange.535 = 13123

ifLastChange.561 = 3243139646

ifLastChange.571 = 13539

ifLastChange.585 = 3391934645

ifLastChange.586 = 3391934645

ifLastChange.587 = 3105867931

ifLastChange.588 = 3105867931

Solution

We are hitting 1759506 & 1734421. The fixes are added via 1734421.

https://prsearch.juniper.net/problemreport/PR1759506

 

Earlier due to the bug, during ifLastChange polling, it was incorrectly reading system up time. Now after fix it will read correct sysUpTime (show system uptime) whenever there is a change in the interface state.

This issue was corrected post code changes and now after interface comes up it will populate proper values for ifLastChange.

Modification History

2024-04-02 : Article Created