I'm just starting to get the hang of the SNMP traps. It took a while to get them working until I found a message on the forum about turning off Windows' own Trap Processor service. It might be helpful to others to publish this tidbit more prominently, or better yet, have OpMan notify on startup that it cannot processor Traps because the OS service is running.
I have a couple questions or wishes.
I initially wanted to add all the traps in my add-on MIBs, but some of them have 50 or more. The function to select all, then add them as trap processors does not work if there are too many traps in a MIB. You have to manually select a bunch and try to add them. If it works, you have to go back and do the rest in bunches until you get them all - rather tedious.
It would also be nice to specify a default trap processor template, rather than the standard "Trap received from $SourceMO(sysName) with SNMP Varbinds $*". I find this is often too verbose and usually contains redundant info (lots of OIDs, etc.). I would prefer to just list the individual VARBINDS ($1 $2 $3 $4) - another tidbit buried in your forum. By specifying a default format, I could add traps in quantity with my desired format, rather than having to wait for an unsolicited trap and manually configure it.
Finally, is it possible to clear unsolicited traps? As I add a trap processor for an unsolicited trap, it would be nice to get it out of the list so I know which ones have not been configured!