SNMP trap seem to send data sometimes as hex and sometimes as the original

[alex]

Hi all,

I am new to SNMP and might not get all the details right, but for a SNMP project I need to understand some more. What I intend to do is to send a trap message using a python function as follows:

ntforg.NotificationOriginator().sendNotification(
ntforg.CommunityData(auth, comunity),
ntforg.UdpTransportTarget((ip, 162)),
'trap',
(('SNMPv2-MIB', 'warmStart'),),
usr,
msg
)


where msg is the message, i.e. a OID/Octet tuple. When executing the trap with some message it seems that sometimes the message is being sent in the original form, and sometimes as a sequence of hex numbers, e.g. '71 55 66 65 31 6A 53 54 49 6E 69 44 54 74 49 77 73 62' instead of a original random test message 'qUfe1jSTIniDTtIwsb'.

Does anyone know details about this behaviour? How can I find out which case is being used. And why?


Thanks a lot,

Alex