Hi Victor!
Yes, that fixed my immediate issue. The traps are certainly creating alarms now.
My trap sender is an NMS that will send traps on behalf of other devices; ultimately, it is the 'remote device' that I'd like to have referenced as "$node". I've been digging through the documentation and what I think I need to do is create a node on the fly upon trap reception based on one of the OID value's. I think the workflow would work like this:
1) Receive Trap
2) Identify Remote Node from MIB
3) Use FindNodeObject to see if the proper node exists
4) If yes, script a finagling and use PostEvent
5) If no, create a new object using CreateNode, and then modify the new alarm
Does this sound feasible to you? Would you be able to provide me with a one-liner as to how CreateNode works and the parameters it needs?
Thanks again!
Victor W
Yes, that fixed my immediate issue. The traps are certainly creating alarms now.
My trap sender is an NMS that will send traps on behalf of other devices; ultimately, it is the 'remote device' that I'd like to have referenced as "$node". I've been digging through the documentation and what I think I need to do is create a node on the fly upon trap reception based on one of the OID value's. I think the workflow would work like this:
1) Receive Trap
2) Identify Remote Node from MIB
3) Use FindNodeObject to see if the proper node exists
4) If yes, script a finagling and use PostEvent
5) If no, create a new object using CreateNode, and then modify the new alarm
Does this sound feasible to you? Would you be able to provide me with a one-liner as to how CreateNode works and the parameters it needs?
Thanks again!
Victor W