Thomas Anders wrote: > Please run "snmpget -DALL ..." and have a look for suspicious errors.
Thanks for the hint, the last part of the output has indeed an error. The "error" is in the snmp_pdu_parse method (snmp_api.c), because asn_parse_header(...) returns null. To be more specific, there is a length mismatch. The method asn_parse_header in asn1.c has at the beginning a header lenght check _asn_parse_length_check (...), which fails. The length of the pdu is 2e. However, the snom phone returns a size of 42. Thus, the check of the asn length and the actual data length fails. The snom phone always returns 42, no matter how big the packet is. Conclusion: It is a broken agent. Thanks for your help! Regards, Thomas snmp_api: Parsing SNMPv1 message... trace: _snmp_parse(): snmp_api.c, 4033: dumph_recv: SNMPv1 message trace: snmp_comstr_parse(): snmp_auth.c, 132: dumph_recv: SNMP version dumpx_recv: 02 01 00 dumpv_recv: Integer: 0 (0x00) trace: snmp_comstr_parse(): snmp_auth.c, 144: dumph_recv: community string dumpx_recv: 04 06 70 75 62 6C 69 63 dumpv_recv: String: public trace: _snmp_parse(): snmp_api.c, 4076: dumph_recv: PDU trace: _sess_process_packet(): snmp_api.c, 5027: sess_process_packet: parse fail trace: snmp_sess_select_info(): snmp_api.c, 5703: sess_select: for all sessions: 3 (to in 1135695379.793754 sec) verbose:sess_select: timer due in 0.956926 sec verbose:sess_select: setting timer to 0.956926 sec, clear block (was 1) Timeout: No Response from 192.168.1.112. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
