Re: Is it possible to expand the timeout duration of an SNMP query?

On Tue, 2008-11-11 at 12:26 -0800, Need Help wrote: > I am using NetSNMP v5.4.1 and I am using a subagent to gather data for > my MIB. > > When performing a SNMP query which needs to gather a bunch of data, > sometimes the SNMP query times out thus resulting in no data being > displayed. I am ass

Is it possible to expand the timeout duration of an SNMP query?

I am using NetSNMP v5.4.1 and I am using a subagent to gather data for my MIB. When performing a SNMP query which needs to gather a bunch of data, sometimes the SNMP query times out thus resulting in no data being displayed.  I am assuming this is because the master agent has timed out waiting f

Exit status on bind error

Hello, when the snmpd fails to bind listening port, it writes 'Error opening specified endpoint "udp:0.0.0.0:162", Server Exiting with code 1' to syslog and dies, but its exit code it 0. I looked into the sources and I can see that the agent is deamonized before the listening sockets are creat

Re: Why are "Entry" and "Index" table oids marked as "non-accessible"?

2008/11/11 Need Help <[EMAIL PROTECTED]>: > I have noticed that the "xEntry" and "xIndex" oids which are used to > define a Table are marked as "non-accessible", instead of "read-only". > > Why advantages do you get for defining it as "non-accessible" vs > "read-only"? That's the wrong que

Why are "Entry" and "Index" table oids marked as "non-accessible"?

I have noticed that the "xEntry" and "xIndex" oids which are used to define a Table are marked as "non-accessible", instead of "read-only". Why advantages do you get for defining it as "non-accessible" vs "read-only"?  ---

RE: Receive trash on the SET request value

Hi Magnus! Thanks a lot for your answer Well, I know now!!! And that solves my problem. Thank you very much, Ângela Lázaro -Original Message- From: Magnus Fromreide [mailto:[EMAIL PROTECTED] Sent: segunda-feira, 10 de Novembro de 2008 19:11 To: Angela Lazaro Cc: net-snmp-coders@lis