The most recent content from our members.
Has anyone else found that the snmp varbinds used in creating alert messages have incremented by 1? I can certainly go and 'fix' it, however one of the alerts was in varbind 10 and fixing it would mean using varbind 11 which doesn't exist. This has completely broken the tool for us. Did I miss something? Here is an example…
Natively support the parsing of incoming trap data into "varbind" elements (the same way it's done in Orion NPM's trap utility) so that these varbinds can be used in output options (send syslog, email, log to file, etc.,,
I am using NPM to notify staff when it receives certain SNMP traps via email for our UPS. The email includes the trap message and lists the Variable bindings for the trap. Included in this is the upsAlarmDescr OID for the alarm. Is there a way to display the OID name in the email rather than the directory path so that I…
When Orion NPM sends an SNMP trap to a north bound SNMP trap receiver or MoM (Manager of Managers) such as HP OM in our case, the source address of the packet is populated with the IP of the Solarwinds Orion server. As such the MoM cannot uniqely identify the end node that generated the trap. Has anyone come across this…
It looks like you're new here. Sign in or register to get started.