Incorrect alerts from snmpcollector probe after threshold value was changed

book

Article ID: 242322

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management On-Premise (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM) Unified Infrastructure Management for Mainframe

Issue/Introduction

Threshold value has been changed for QOS_INTERFACE_PCTDISCARDSIN & QOS_INTERFACE_PCTDISCARDSOUT of DIB-IT-XXX-DA-ABCDE-ACCSW-02.

But we are still getting  alerts with the old threshold value. Please help to fix the issue.

Cause

- leftover artifact in the snmpcollector threshold cache

Environment

  • Release: UIM 20.4
  • Component : UIM - SNMPCOLLECTOR
  • snmpcollector probe v4.03

Resolution

Here are the steps that were followed to resolve this issue:
  1. Deactivated snmpcollector and baseline_engine 
  2. Renamed <baseline engine>/cache_dir/threshold.cache.zip
  3. Activated baseline engine
  4. Activated snmpcollector
  5. Forced rediscovery on the profile(s) - In the Admin Console (AC), Ran Query Discovery server but the customer will rediscover all individual profiles as well
  6. Restarted the hub-robot where snmpcollector is deployed so each probe can send its configuration to the baseline engine
The snmpcollector alarm threshold value was then correct in the IM alarm subconsole.