SNMP TRAP Receiver not working properly

[darshakamodi]

Hi,
It seems SNMP trap receiver truncates some values

7-Sep-2011 16:13:50] Received SNMP trap .1.3.6.1.4.1.21067.1.3.4 from 10.152.163.39
[07-Sep-2011 16:13:50] EVENT 500 (F:0x0001 S:0) FROM CHN-AAA-4: SNMP trap received: .1.3.6.1.4.1.21067.1.3.4 (Parameters: .1.3.6.1.2.1.1.3.0 == '0'; .1.3.6.1.6.3.1.1.4.1.0 == '.1.3.6.1.4.1.21067.1.3.4'; .1.3.6.1.4.1.21067.1.3.4 == '30 37 2D 53 65 70 2D 32 30 31 31 20 31 36 3A 31 33 3A 35 30 3A 20 5B 53 45 52 56 45 52 55 50 5D 20 3A 53 65 72 76 65 72 20 53 74 61 72 74 65 64 20 53 75 63 63 65 73 73 66 75 6C 6C 79 20 57 69 74 68 20 53 65 72 76 69 63 65 73 3A 20 0A 53 4E 4D 50 20 53 65 72 76 69 63 65 20 53 74 61 72 74 65 64 20 53 75 63 63 65 73 73 66 75 6C 6C 79 2E 0A 52 41 44 5F 41 55 54 48 20 53 65 72 76 69 63 65 20 53 74 61 72 74 65 64 20 53 75 63 63 65 73 73 66 75 6C 6C 79 2E 0A 52 41 44 5F 41 43 43 54 20 53 65 72 76 69 63 65 20 53 7')

Above is log from netxms. Below i am attaching snap from trapviewer software. Which shows correct values .
I can see the hex values are cut/discarded in netxms

---

[victor]

It's not the trap receiver, but event processing. Currently event's message size limited to 255 characters. Because default event just put everything into message it gets truncated. Usually you will create separate events for traps of interest, and you can carry trap arguments as event parameters, and then use them in actions, for example, without length limitations.

Best regards,
Victor

[darshakamodi]

To receive Traps, i hadnt configure any event .
 Does it automatically calls Default Event?

Can you give an example for argument passing ?