when a client timeouts and resends the request - will it get duplicate responses or will it get only one response?How is it handled by the master agent? do the client detect duplicates responses or/and the master agent detect duplicate requests?
That's how the Net-SNMP client tools work, yes.They'll make the request, and if they don't receive an answer within a
reasonable time, they'll try again. Only when a certain number ofretries have timed out will they report failure.Try "snmpgetnext -d ." to see this happening.But a typical se
Hello Coders,
I generated C language codes by using "mib2c CCbsInfoTable", w/t 2-Net-SNMP
sytle, 2-"list of rows is held by the agent itself", and 5-Net-SNMP container
MFD.
Our private MIBs looks like
-
sndaSnmpMIB MODULE-IDENTITY
...
::= { ucdExperimenta
[EMAIL PROTECTED] wrote:
> We are not able to enable IPv6 support on Solaris 9 when building
> Net-SNMP_5.3.1
I can reproduce your problem and confirm that this is a bug. I've checked in a
fix for CVS MAIN that should allow you to build net-snmp on Solaris (and AIX,
Tru64, ...) with support for t
On 31/08/06, Mike Varley <[EMAIL PROTECTED]> wrote:
> One problem we have with this bug is it is very difficult to reproduce;
> I am trying to create some samples which will simulate the failure.
Oh :-(
Never a good sign.
> The current hypothesis is we have a buffer overrun, and its messing with
Thanks Dave.
One problem we have with this bug is it is very difficult to reproduce;
I am trying to create some samples which will simulate the failure.
The indexes are accessible.
Thanks for the clarification on what a 'gap' or '?' might be; it will
help me in creating the samples :)
The cur
On 31/08/06, Mike Varley <[EMAIL PROTECTED]> wrote:
> Don't you hate it when people withhold information? :)
a) You might say that - I couldn't possibly comment
b) You get used to it after two or three years on the list :-(
> So here is a more accurate sample of the output:
>
> id(index1) num(
Thanks Dave, here is some more information on our bug.
Dave Shield wrote:
> On 31/08/06, Mike Varley <[EMAIL PROTECTED]> wrote:
>
>> we are seeing an snmptable command respond with question
>> marks ('?') as the result for some of the column entries; and I am
>> wondering if this is normal be
On 31/08/06, Mike Varley <[EMAIL PROTECTED]> wrote:
> we are seeing an snmptable command respond with question
> marks ('?') as the result for some of the column entries; and I am
> wondering if this is normal behaviour if net-snmp encounters an error
> while trying to interpret a response.
No
Appologies if this is the wrong list to ask, but I am currently chasing
a bug where we are seeing an snmptable command respond with question
marks ('?') as the result for some of the column entries; and I am
wondering if this is normal behaviour if net-snmp encounters an error
while trying to i
>>I know that SNMP works over UDP.
>>I am developing a subagent over agentx
Agentx
will be over TCP.
>>So how long can I take or is there any other way in the SNMP
protocol itself to solve this issue?
By
default snmpget will wait for 5 seconds and resends the requ
I know that SNMP works over UDP.I am developing a subagent over agentx. When I get a GEt request I need to do some calculations based on the values at that time and return it.It takes some time to fetch & calculate those value. So how long can I take or is there any other way in the SNMP protocol i
On 31/08/06, Zhang Chuan <[EMAIL PROTECTED]> wrote:
> 1.if rowStatus is CreateAndGot(4), the "case MODE_SET_COMMIT:" will not be
> executed? if CreateAndWait(5), it will be executed?
No.
COMMIT should be run for *any* (successful) SET request.
> What is difference between them?
c&Go makes the n
Thank Dave for his patient answer of my first question!
But I have another one:
I wonder when I set a line to a table.There is a rowStatus field.When I set the rowStatus to CreateAndGo(4). Everything is OK, the line can be insert into table.
But if the rowStatus is CreateAndWait(5). In "case
14 matches
Mail list logo
