Alerts are not being generated from the snmpcollector probe on one secondary hub
Article ID: 135320
Updated On:
Products
Issue/Introduction
The snmpcollector probe is configured to generate static alarms for monitored metrics when the metric exceeds a configured threshold. Even with the threshold set below the current value of the monitored metric, no alarms are generated.
Static alarms from the snmpcollector probe are actually generated by the baseline_engine probe. The baseline_engine logs at loglevel 5 indicated that alarms are being published:
2019-07-25 08:16:41.361 [ alarmEx-8] TRACE impl.NimsoftApiImpl - sendRawMessage() message = {"subject":"alarm","udata":{"values":{"ipaddress":"1.2.3.4","qos_name":"QOS_CPU_UTILIZATION","qos_source":"1.2.3.4","source":"1.2.3.4","qos_target":"CPU","target":"CPU","qos_value":13.0,"value":13.0,"unit":"pct","threshold_sign":"+","threshold":80.0,"threshold_symbol":"%","threshold_value":10.73,"operator":">=","baseline":5.96},"source":"1.2.3.4","qos":{"qos":"QOS_CPU_UTILIZATION","source":"1.2.3.4","target":"CPU","sampletime":1564064198,"sampletype":0,"samplevalue":13.0,"samplestdev":0,"samplerate":300},"stdev":12.09,"level":5,"message":"Warning: CPU utilization is more than 80% in last five minutes.","token":"!=Warning: CPU utilization is more than 80% in last five minutes.","subsys":"1.1.19"},"nimts":1564064198,"dev_id":"D4b8c009f776b965fcab950089c4f4f42","origin":"hub2","robot":"robot2","prid":"pollagent","met_id":"Me1723f878c0a2ec9e71259dec3949bcd","source":"1.3.5.1","nimid":"NH78985651-83338","domain":"UIM","mt_id":"11.2:1","et_id":"threshold.dynamic","hop":0,"hop0":"hub2","pri":5,"charset":"UTF-8","supp_key":"1.2.3.4CPUQOS_CPU_UTILIZATION_dynamic","suppression":"y+000000000#1.2.3.4CPUQOS_CPU_UTILIZATION_dynamic"}
The hub.log at loglevel 5 shows that the hub is discarding the alarms from the baseline_engine probe:
Jul 25 08:16:44:203 [4348] hub: spooled - NH78985651-83438 on alarm_enrichment (sub:alarm)
Jul 25 08:16:44:221 [4348] hub: postroute_sendnext - recurring message NH78985651-83438 dropped (q:alarm_enrichment sub:alarm)
but is successfully processing alarms from other probes on the same hub:
Jul 25 08:16:44:209 [4348] hub: spooled - QA90347933-30322 on alarm_enrichment (sub:alarm)
Jul 25 08:16:44:211 [4348] hub: spooled - ST36720688-02606 on alarm_enrichment (sub:alarm)
Jul 25 08:16:44:211 [4348] hub: spooled - ST36720688-02632 on alarm_enrichment (sub:alarm)
Jul 25 08:16:44:213 [4348] hub: spooled - TY14979148-73314 on alarm_enrichment (sub:alarm)
Jul 25 08:16:44:213 [4348] hub: spooled - TY14979148-73320 on alarm_enrichment (sub:alarm)
Environment
Release : 9.0.2
Component : UIM - SNMPCOLLECTOR v3.44
Robot: 7.97
Hub: 7.97
Cause
Failed hub 7.97 install on the problematic hub. The hub binary files found in the hub directory were as follows:
05/02/2019 11:46 AM 16,384 bus_plugin_utility.dll.7.97
09/18/2012 06:02 AM 2,088,960 hub.exe
05/02/2019 11:46 AM 3,528 hub_shared_libs_rename.bat
09/18/2012 05:52 AM 355,840 LDAPSDK.dll
09/18/2012 05:52 AM 953,856 LDAPSSL.dll
09/18/2012 05:52 AM 202,752 LDAPX.dll
05/02/2019 11:46 AM 2,506,240 nim_shared.dll.7.97
09/18/2012 06:02 AM 1,569,280 sdsfile.exe
04/11/2019 08:57 AM 2,280,960 tunnelsetup.exe
The expected set of 7.97 hub binaries are as follows:
04/29/2019 02:51 PM 132,096 brotlicommon.dll
04/29/2019 02:51 PM 49,152 brotlidec.dll
04/29/2019 02:51 PM 543,744 brotlienc.dll
04/29/2019 02:51 PM 16,384 bus_plugin_utility.dll
04/29/2019 02:51 PM 3,144,064 hub.exe
04/29/2019 02:51 PM 3,528 hub_shared_libs_rename.bat
04/29/2019 02:51 PM 2,506,240 nim_shared.dll
04/29/2019 02:51 PM 2,402,176 sdsfile.exe
04/29/2019 02:51 PM 2,412,928 tunnelsetup.exe
Resolution
Feedback
