SNMP Trap Frames Appear to be Dropped

CAUSE

• The size of the pipe created by SNMPTRAP.EXE that collects Trap PDUs (Protocol Data Unit) from Trap Frames collected on UDP port 162 is equal to the maximum size of only one Trap PDU.
• MGMTAPI.DLL (loaded by SNMP Monitoring applications such as SNMPUTIL.EXE) does not change the state of the pipe created by SNMPTRAP.EXE to message mode. When the messages start queuing up on the server side of the pipe (SNMPTRAP.EXE), the client side of the pipe (SNMP Monitor) assumes that each read consists of only one Trap PDU. Because the mode of the pipe created by SNMPTRAP.EXE was never set manually by MGMTAPI.DLL, it would default to byte mode and the SNMP Monitor application would end up reading multiple Trap PDUs but only decoding the first one in the buffer, effectively dropping the rest.