SNMP TRAP Scripting in TM 3.0

[minermail]

We have a central NOC that monitors faults across many diverse IT systems. I would like to use the scripting capability in TM to modify traps received from our remote office PBXs and send them along to the NOC's NMS with more detail (ie port, circuit id attached, carrier, callout instructions, etc..) anyone know where (web sites). I see in the NTPs where this is possible.

Anyone see a site where can I find examples for this purpose other than NTPs or on the TM server itself? I did a search here and didn't find much on TM scripting. Thanks.

 

[jadexing]

OTM 2.2 had scripting wizards- but they took them out of 3.0 for whatever reason. I don't know if 3.1 has them or not.

-Jadexing

 

[minermail]

jadexing,

Thanks for taking the time to respond. Since my post I've been poking around in the script language mostly trying to emulate the alarming capability of the Gordon Kapes, Model 125 we use for dial-out notifications. It triggers alarm notification using ACSII pattern matching on the serial link from the PBX. ie see "DTA019" and dial back to NOC and send text string "Follow callout procedure abc123".

I've found ways to do just about everything (pattern match on events, send a trap, insert event specific text, ignore events/alarms during midnight routines). The one area I'm struggling with is how to ignore repeated alarms (ie allow first DTA019 and filter additional DTA019's for 1 hour) to prevent flooding the NOC when Ts are having troubles. The script language implies counter variables and timer vaiables can be used but I'm still trying to find a workable solution.

Minermail