SNMP Trap Eventsource

Recommended Posts

We need to be able to filter on the message context inside the SNMP trap, not just:

enterpriseOid, generalCode, snmpVersion, specificCode, trapOid


  • Upvote 1

Share this post

Link to post
Share on other sites

As a precise example as to why this would be a useful feature:  vCenter alarms SNMP trap notifications.  At least in my experience these are sent from vCenter as v1 traps but all the juicy information is in the trap variable bindings.  Here's a trap sent from a CPU Usage Alarm: Green Red alarm.VmCPUUsageAlarm - Metric CPU Usage = 100% SERVER-1 3 
generalCode: 6 
snmpVersion: v1 
specificCode: 203 
sysUpTime: 1778505188 
trapVariableBindingCount: 5

All the /really/ useful information is in the trap variables:

  • (vmwVpxdOldStatus)
  • (vmwVpxdNewStatus)
  • (vmwVpxdObjValue - What alarm got tripped!)
  • ( vmwVpxdTargetObj - What vCenter object tripped the alarm!)

Being able to filter on the contents of bound variables, and address them as tokens in alarm subject/message, as something like ##TRAPVAR01##, ##TRAPVAR02##, ##TRAPVAR03## would be a massive workflow improvement for us.

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.