Unsolved

This post is more than 5 years old

14 Posts

999

December 29th, 2015 09:00

ViPR SRM Alert Definitions and SNMP Traps

I love the ability to customize the alert definitions, but something has confounded me that I have not been able to answer through documentation.  We desire to use our ViPR SRM implementation as a device which send SNMP traps to our already existing internal monitoring and ticketing systems.  I can individually edit each of the the alert definitions "SNMP Trap" actions to specify my SNMP trap destination (in this case an HP Openview server), but this is a bit burdensome when you have dozens of alerts.  I have tried using the Templates features, but this seems to overwrite all the properties of the alerts which I edit (including the trap content which is unique to many of the Alert Definitions).

If I edit the "SNMP Trap" action of an alert definition and replace localhost:2041 with the IP and port of my Openview server we seem to get the alerts fine in OpenView, but will this prevent the alerts from showing up in the SRM Alerts console? (I haven't noticed yet) And, isn't there an easier way to specify trap destinations for all these alerts other than individually editing the SNMP trap actions in each definition manually?

Ideally I'd like a place to centrally specify an external SNMP trap destination that would apply to all the definitions, or an ability to alter a template and apply it to applicable definitions which are base upon that template (without the template wiping out the trap content field).

Any suggestions as to what a best-practice would be in this area would be appreciated.

Thanks,
REID

No Responses!
No Events found!

Top