This article explains the interval of cached MIB2D data update. The time interval is 5 seconds.
Cached MIB2D data will update at 5 sec intervals.
Monitor input packets with cached MIB2D data.
Topology <------------------------------- ping +--------+ +--------+ | MX |ge-0/0/0.0 ge-0/0/0.0| MX | | (R1) |--------------------------------| (R2) | | |SNMP ifIndex 542 | | +--------+A +--------+ | monitor point
Test results :
:
user@R1> show snmp mib walk ifInUcastPkts | match .542 | refresh 1 ---(refreshed at 2018-01-24 22:34:34 PST)--- ifInUcastPkts.542 = 120 <<<<<< 1 ---(refreshed at 2018-01-24 22:34:36 PST)--- ifInUcastPkts.542 = 120 <<<<<< 2 ---(refreshed at 2018-01-24 22:34:37 PST)--- ifInUcastPkts.542 = 120 <<<<<< 3 ---(refreshed at 2018-01-24 22:34:38 PST)--- ifInUcastPkts.542 = 120 <<<<<< 4 ---(refreshed at 2018-01-24 22:34:39 PST)--- ifInUcastPkts.542 = 120 <<<<<< 5 ---(refreshed at 2018-01-24 22:34:40 PST)--- ifInUcastPkts.542 = 126 <<<<<< 1 ---(refreshed at 2018-01-24 22:34:41 PST)--- ifInUcastPkts.542 = 126 <<<<<< 2 ---(refreshed at 2018-01-24 22:34:42 PST)--- ifInUcastPkts.542 = 126 <<<<<< 3 ---(refreshed at 2018-01-24 22:34:43 PST)--- ifInUcastPkts.542 = 126 <<<<<< 4 ---(refreshed at 2018-01-24 22:34:44 PST)--- ifInUcastPkts.542 = 126 <<<<<< 5 ---(refreshed at 2018-01-24 22:34:45 PST)--- ifInUcastPkts.542 = 131 <<<<<< 1 ---(refreshed at 2018-01-24 22:34:46 PST)--- ifInUcastPkts.542 = 131 <<<<<< 2 ---(refreshed at 2018-01-24 22:34:47 PST)--- ifInUcastPkts.542 = 131 <<<<<< 3 ---(refreshed at 2018-01-24 22:34:48 PST)--- ifInUcastPkts.542 = 131 <<<<<< 4 ---(refreshed at 2018-01-24 22:34:49 PST)--- ifInUcastPkts.542 = 131 <<<<<< 5 ---(refreshed at 2018-01-24 22:34:50 PST)--- ifInUcastPkts.542 = 136 <<<<<< 1
This behavior is by design and is part of the specification.