probe continues to send alarms after being deleted or deactivated

book

Article ID: 36222

calendar_today

Updated On:

Products

DX Infrastructure Management NIMSOFT PROBES

Issue/Introduction

Problem

- Customer made an update to the configuration of interface_traffic that turns off monitoring for a particular metric.
- However, the customer continues to receive alarms from this probe.
- In the support ticket (00271583), interface_traffic was continuing to send alarms from a check point the customer had disabled (link state down).
- We tested completely removing (deleting), redeploying, and reconfiguring the probe - no improvements. Alarms continue to be sent unexpectedly.
 
Environment: 
- CA UIM 8.31
- UMP 8.31
- RedHat 6.5 (2.6.32-431.5.1.el6.x86_64)
- interface_traffic 5.45
- controller 7.80
- hub 7.80
- monitoring four Cisco C3750E's with the interface_traffic probe
 
Cause:
- Probe process is not appropriately shut down (killed) upon the probe's configuration update, deletion, or deactivation.
 
Workaround:
- Run the following command on the target system to find the probe's PID. In this example, we're using the interface_traffic probe:
>>> ps - ef | grep interface_traffic
- Once you have the PID, you may execute the following (inserting the PID# where appropriate):
>>> kill -9 PID#
- This should end the process and stop the probe from sending old alarms.
- If you've updated the configuration, the new changes should be applied once the probe restarts.
- If you've stopped or suspending monitoring, the probe should also respect these new changes after restarting.
 

Environment

Release: CNMSPP99000-8.31-Unified Infrastructure Mgmt-Server Pack-- On Prem
Component: