snmpcollector probe operational stabilization and restart guidelines

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

What is the expected time span for the probe to stabilize after it stops and starts? We need to understand how long it takes for SNMP profiles to stabilize after on or multiple planned restarts (Eg. Via callback). 

Environment

• DX UIM 23.4.*
• SNMPcollector (Any Version)

 

Cause

There is no fixed stabilization time coded into the snmpcollector probe; instead, stabilization is dependent on the completion of the discovery process for all newly added devices and components. Frequent restarts interrupt this re-initialization and discovery phase, which can significantly delay total stabilization time.

Resolution

Understand Stabilization Factors:

Stabilization occurs once the discovery process is complete for the newly added devices. For environments with 600 or more profiles, the time required depends on the number of components per device and network responsiveness. It is expected that after a restart or large batch update, it may take several hours—and in some cases up to 24 hours—to see all QoS data populate.

Monitor the Discovery process in snmpcollector log level 5: (Log examples)

 

May 21 12:10:40:939 [Timer-0, snmpcollector] Initializing SNMPCollector 

May 21 12:10:40:939 [Timer-0, snmpcollector] Force discovery on restart flag is set - triggering discovery for all devices 

[...]

May 21 12:17:42:593 [Thread-10, snmpcollector] DiscoveryController ended

Additional Information

Review this article for general optimization annd performance obtimization snmpcollector probe scalability, performance tuning and optimization guidelines