Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

Cached MIB2D update in 5 second intervals

0

0

Article ID: KB32850 KB Last Updated: 01 Aug 2018Version: 1.0
Summary:

This article explains the interval of cached MIB2D data update. The time interval is 5 seconds.

Symptoms:

Cached MIB2D data will update at 5 sec intervals.

Example:

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
Solution:
This behavior is by design and is part of the specification.
Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search