SNMP trap import - a couple of things that would make life easier

Started by paul, May 26, 2019, 06:50:50 AM

Previous topic - Next topic

paul

Having added a few traps now, these things slow me down the most.

1. In the tree can we simply start at enterprises when selecting load. I am sick of typing .1.3.6.1.4.1 and 99.99% of traps we load will be from an enterprise mib.
Next - this one is very painful.
1. When we select a trap from the mib, can we have it auto populate the description from the MIB into the description for the trap.
2. Once we have selected that trap OID, can it automatically populate the Parameters from the MIB definition. Each Mib defines which parameters are included - so can we automate this?
3. Same for Parameter Mapping - auto load that from the Mib - the description and the parameter.

These seem to be  obvious omissions given the laborious nature of doing thes - especially since each mib defines, for the traps, what the parameters are that are passed.

paul

How big an issue is this? Let me show you :)

I get traps from CISCO UCS that are 12 lines long. You want to read them line as that is the way CISCO designed them to be read. You also need the varbind dscriptions so as to make sense of what each of the 12 varbinds represents.

The MIB lists each one of those 12 objects - but only as their text objects. The Imports will include the OIDs for the text objects - but NetXMS does not Import either the text names of those objects or the OIDS of the objects. To do so manually is nearly impossible and the much simpler way would be simply to have a trap sent - and then use the trap log browser to find the OIDS.

That still leaves four huge problems.
Problem 1: The text descriptions of the objects need to be entered manually.
Problem 2: I cannot duplicate an existing trap in order to use the already filled out varbind object descriptions.
Problem 3: Even once they are entered, because only the values of the objects are passed across, all that effort to type in the description is wasted as it is not passed through to Event Configuration nor is it made available in Event Processing Policy to be included. I have to manually enter them all over again.
Problem 4: The message field in event processing policy would need to have the text of each of the varbinds entered in full plus the parameter plus a 'n for a new line. Being a field of about 40 characters visible and I would need to input up to 300 characters or even more, Event Processing Policy is simply not designed for that.

Now, as much as I am willing to do the hard yards to add things, the restrictive input regarding traps makes this aspect well past daunting, to the point of simply not practical for traps like these from CISCO.

Given that the OIDs for these traps are not obvious - but that the select option is looking up the textual representation of the mib AND it does know the textual varbind objects from the mib - is it not simply just a matter of having another box - "load varbind objects from mib" and automatically look up the OIDs of those varbinds in the mib and populate the trap table?

This also loads up the OID and text explanation of the object. For example - parameter 3 is %3 with %oidN3 and %oidT3 containg the OID number and text. Pass these through Event Configuration into Event  Processing Policy and Actions Configuration so they can be displayed as intended.

I have attached how it looks in the mib, how it looks in a different NMS from a configuration definition - and how it actually looks when a trap is received in a NMS and what it is supposed to look like.