[NV-L] 7.1.5 FP2 AIX Traps from Dialogic device formatted OK in trapd.lo

Hi folks,

Wondering if someone has a suggestion for why a trap from the Dialogic device itself that reads fine in trapd.log would not make it through nvserverd processing, yet a test trap I send using the trapgen commandline tool will? At first I wondered if the brackets were causing trouble, but testing proved that’s not the case. Looking for ideas before I start turning on tracing/opening a PMR.

The ruleset is very simple, traps are filtered by Enterprise ID, and forwarded to TEC.

This entry in trapd is from the device and never makes it to nvserverd.log:

1228138568 3 Mon Dec 01 07:36:08 2008 10.15.0.22 A Dialogic DMG

Alarm Trap: Alarm Index = 27, Alarm ID = 64, Severity = 2 (1 = most severe), Des

cription = Gateway Warning, Device = 0, Message = VoIP[10.27.8.58] In-Service

This entry in trapd is from the trapgen tool, and makes it to nvserverd/TEC with no problem

1228229728 3 Tue Dec 02 08:55:28 2008 10.30.15.120 A Dialogic DMG

Alarm Trap: Alarm Index = Test, Alarm ID = Test1, Severity = Test2 (1 = most severe),

Description = Test3, Device = Test4, Message = Test[In Brackets] message

I wonder if the device is passing hidden params or characters that trapd’s fine with, but cause the ruleset to drop it.

Thanks!--Drew

This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message.

Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1]

_______________________________________________
NV-L mailing list
NV-L AT lists.ca.ibm DOT com
Unsubscribe:NV-L-leave AT lists.ca.ibm DOT com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to 
internal IBM'ers only)

[NV-L] 7.1.5 FP2 AIX Traps from Dialogic device formatted OK in trapd.log but being dropped in ruleset