I have 2 identical box, all same configuration, one works perfectly,
snmptrapd translates the trap packets well, another just not, packets
are seen in snmptrapd.log log which means the packets arrived, just a
matter that snmptrapd does not do the rest job for whatever reason.
Wondering how to debug snmptrap further in this case...
Thanks.
Angie
On 11/2/07, Mike Ayers <mike_...@tvworks.com> wrote:
>
> > From: net-snmp-us...@lists.sourceforge.net
> > [mailto:net-snmp-us...@lists.sourceforge.net] On
> > Behalf Of Angie Cao
> > Sent: Friday, November 02, 2007 10:10 AM
>
> > As a matter of fact, as mentioned in the first email, if I run same
> > command from localhost (which snmptrapd is running), the traps were
> > received properly. I do not know why snmptrapd does not translate the
> > traps receiving from remote boxes.
>
> Have you configured authorization for the remote host? Try adding in the flag "--disableAuthorization=yes" and see if the traps ahow up. If so, check the access control section of the snmptrapd.conf man page.
>
>
> HTH,
>
> Mike
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Net-snmp-users mailing list
Net-snm...@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
-------------
trace: _sess_process_packet(): snmp_api.c, 4919:
sess_process_packet: pre-parse fail
trace: _sess_read(): snmp_api.c, 5213:
sess_read: not reading 6 (fdset 0xbff5af10 set 0)
trace: _sess_read(): snmp_api.c, 5213:
sess_read: not reading 4 (fdset 0xbff5af10 set 0)
trace: snmp_sess_select_info(): snmp_api.c, 5632:
sess_select: for all sessions: 8 6 4
-----------------
Obviously it is not able to process the packets. But I am not sure how
to fix this problem...
Appreciate if anyone understand this..
Thanks.
Angie
> Ok... I turned on the verbose output for snmptrapd by adding "-D
> ip_interface" switch. In the debug trace, here are the failure I
> found:
>
> -------------
> trace: _sess_process_packet(): snmp_api.c, 4919:
> sess_process_packet: pre-parse fail
This appears to be the rejection of the trap because the source address is not authorized.
> trace: _sess_read(): snmp_api.c, 5213:
> sess_read: not reading 6 (fdset 0xbff5af10 set 0)
Not reading = no packet on this fd.
> trace: _sess_read(): snmp_api.c, 5213:
> sess_read: not reading 4 (fdset 0xbff5af10 set 0)
> trace: snmp_sess_select_info(): snmp_api.c, 5632:
> sess_select: for all sessions: 8 6 4
> -----------------
>
> Obviously it is not able to process the packets. But I am not sure how
> to fix this problem...
> Appreciate if anyone understand this..
Please calm down, slow down, and read the documentation on access control. This will be a lot less painful if you do.