Hi @channdy you must check ‘Is Volatile” option on your service definition or use Centreon DSM to manage alert by interface.

I have tried “Is Volatile” option but that is only sent alert when the last and the next trap event are in Non-OK state. If the last and the next trap event are in OK state then the trap event for another interface was not triggered the alert. I am not sure if Centreon DSM can be used to resolve this issue please advise me. Thanks

With Centreon DSM, you will have a “slot” per network interface.

So if you have 2 linkdown traps on 2 different network interface, you will have 2 different alerts.

When you will receive a linkup from a linkdown, this will recover the first alert and you will keep second alert. Then when you will receive the linkup for the second interface, you will see the change.

If you enable notification for the “generic-service-passive-custom” service template uses for the “slot”, you will receive all notifications

Hi Laurent, Thanks so much for your time. I tried Centreon DSM and let you know the result.

Hi @channdy,

I have the same problem as yours, did you manage to receive one ok trap after another? 

I don’t understand why ‘is volatil’ only works with non-ok traps, when working with snmp alarm traps normally I need all your traps to be managed, not only non-ok state ones. 

I achieved logging 2 ok state traps one after another activeting the ok stalking option in Data processing tab. But this only logs as documentation says, does not notificate.

Thank you in advance,

Sandra

Hi, ‘is volatil’ is an option to send notification, only for non-ok status, is status change or if output of the plugin change.

But for OK status, only one notification is sent.

If you want to send a notification for several OK received, you need to use Centreon DSM & slots.

Regards,

Thank you @Laurent . We’ll try. 

Hi @Laurent ,

We’ve tried to set up Centreon DSM in a test environment that we have but it was unsuccessful. As we activate the passive-pool, we missed the traps that enter normally without assigning it to a slot, and the ones redirected to the slots never arrived either.

We followed the instructions in centreon documentation but it never worked. Is there another place where we can find some examples or more information about the use of DSM Centreon. We are interested, as we have configured all our alarms, but there is still some traps that we are not seeing as we want, and ones crush others that have not reach an ok status.

Thanks

Hi @Sandra with DSM you need to link SNMP traps to an active service of your host, like the Ping service.

You need to configure the SNMP traps definition to execute DSM binary (execute special command) and select correct traps value for the “-i” option.

You need also to create the ALARM_ID custom macro on this host (or on a host template used by this host).

Then generate & export the configuration.

You can enable debug of centreontrapd processus (/etc/sysconfig/centreontrapd) to check if this process execute the special command and how.

Then you can enable DSM debug (/etc/sysconfig/dsmd)