Showing results for 
Search instead for 
Did you mean: 
Create Post

Forward "traps" to Orion NPM

Forward "traps" to Orion NPM

We want to use Kiwi to perform initial filtering of our trap and syslog messages, and then pass only the items we want to Orion NPM for association with nodes and (possibly) alerting.

This works fine for syslog since the "forward to another host" function was built for that.

But traps are a problem.

First - the trap message is "blobbed" into a single message string so that you can't parse out one trap variable (ie: a varbind) from another.

Second - traps can't be forwarded transparently (it can in other tools, and even free tools like net-snmp)

Third - traps can't be forwarded *at all*, so you have to pick a specific trap OID for your rule

What I'm asking for is either:

1) support for actually forwarding a trap transparently, as the "forward to another host" option does for syslog...


2) allowing the "forward to another host" option to support variables so that we can build our outbound message using the trap's varbind elements and pass THAT to Orion NPM so that the ultimate alert is something readable.

Level 17

Indeed, this is a yes!  I have been trying to do this since your post, I only searched today for this and found out that I am not the only one.

Level 16

I need that feature ...

I like kiwi as "first line of defence" and move up to NPM trap that i need to triger something.

any status on that feature??

Level 7

I would love to see integration of Kiwi to the Orion interface.  Even if it references a different server for the messages, I would like to see the information in one place.

Level 16

Hi antman

I found a work around for  that problem....the only problem is it's more expensive...

SNMP trap forwarding from kiwi to NPM is not working as it should.

Forwarding from NPM to NPM working just fine.

So if you have the budget for it  NPM SL100 as central trap server will do the trick.

it's not perfect but its working.

will sure prefer more redundant solution with  2-3 kiwis behind a   loadbalance , but till then I reuse my dev/test NPM SL100 to that...

Level 12

NPM sucks as a trap server though.

How about forwarding alerts or notable events to Orion as a possible action for a single trap, or XX number of traps so that alerts could be generated for single traps or XX traps in the last NN minutes/hours/days?


Level 17

The trap alert does have a threshold that you can set, as well as a delay after the trigger so you do not continuously get emails over and over. - but you need to do it for each node, otherwise the same type of traps from different nodes will build up to your threshold counts.

Level 16
Community Manager
Community Manager
Status changed to: Implemented
Community Manager
Community Manager
Status changed to: Implemented