Time Over Threshold setting is not updating in UIM Admin Console

Document ID : KB000007627
Last Modified Date : 10/08/2018
Show Technical Document Details
Issue:

It is possible to change the Time Over Threshold (TOT) configuration in a monitoring probe; however, after saving the configuration, the changes may not be reflected.   This can also happen after adjusting a template - the template appears correctly, but the actual device profile remains incorrect.

Cause:

We have seen these issues happen mainly with snmpcollector, cdm, and vmware.

Snmpcollector and vmware's Time Over Threshold settings are stored in the alarm_enrichment probe and then populated in the admin console UI by ppm.  If these settings are not updating, it is possible that alarm_enrichment is not updating correctly.  Most issues are corrected by clearing the cached information and letting the probe update it.   Sometimes the alarm_enrichment  xml or json file also needs to be renamed to correct the issue.

Resolution:

To resolve this:
1) Update the following probes to the most current version. 

ppm
baseline_engine, nas (which also updates alarm_enrichment)
and the monitoring probe, (snmpcollector, cdm, vmware, etc.).

2) Deactivate nas, alarm_enrichment, baseline_engine, and ppm.

3) Make a backup copy and remove the contents of "C:\Program Files (x86)\Nimsoft\probes\slm\baseline_engine\cache_dir"

4) Rename the 'rule_config.xml' and 'rule_config.json ' files found in "C:\Program Files (x86)\Nimsoft\probes\service\nas\alarm_enrichment"

**Depending on the nas version, there may only be one of these files and not both.

5) Redeploy nas (and alarm_enrichment).

6) Restart snmpcollector, cdm, or vmware which is seeing this problem.

Restarting the monitoring probe will cause it to send new messages on the tot_rule_config queue.  These will be consumed by alarm_enrichment and creat the appropriate configuration there.