NetXMS Forum

Thanks, it's working fine an it proves to be very usefull. Defening event processing rules has become much easier now.

Geert

Hello Victor,

I found the new 'Tag'-field in the SNMP trap configuration, thanks for that. Which macro should I use in the Alarm key to access this Tag-field? I tried %t but this stands for a time stamp.

Regards,

Geert

Thanks for yor reply Victor. I'll check out the new release.

Regards,

Geert

I'm trying to setup handling of SNMP traps that result from hardware failures on HP Proliant servers. I would like to group all critical traps (about 50) in one event processing rule because they all require the same action (sendig e-mail and SMS). This rule could for example contain following events:

• SNMP HP Power supply failed
• SNMP HP NIC connectivity lost
• SNMP HP fan failed

Now I wan't to create a rule that automatically terminates these events. According to the example above this rule could contain these events:

• SNMP HP Power supply OK
• SNMP HP NIC connectivity restored
• SNMP HP fan OK

Offcourse I wan't a termination event to terminate the corresponding alarm. The 'SNMP HP Power supply OK' should only terminate the alarm raised by the 'SNMP HP Power supply failed' event, and not clear other alarms that exist for this node.

How can I accomplish this? I don't see how to define an suitable 'Alarm key'. (The failure and termination traps have different SNMP OIDs).

If this is not possible now it would be nice if one could define a custom parameter on a SNMP trap configuration. For example set a parameter with the value 'PowerFailed' on the traps 'SNMP HP Power supply failed' and 'SNMP HP Power supply OK'. This way you could use it to build an 'Alarm key' that links both events.

Regards,

Geert

Found the solution :). Correct syntax: ..\..\bin\nxmibc -d . -z

Geert

According to what I found on this forum I should copy new MIBs (with a .TXT extension) to the MIBs subdirectory, change to this directory and run the command ..\..\bin\nxmibc -d -z. This returns the error 'No source files given'. The only way to get it working is to specify the path of a MIB file as an argument. (Which is useless ofcourse).

(Using NetXMS 0.2.18 on W2K3SP1, NetXMS installed under C:\NetXMS).

Geert