--===============0537009018==
Content-Type: multipart/alternative;
boundary="----=_Part_64837_14631104.1157086564983"

------=_Part_64837_14631104.1157086564983
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

>
>
> 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 of
> retries have timed out will they report failure.
> Try "snmpgetnext -d ....." to see this happening.
>
> But a typical setup is something like 3 retries with a 5s timeout.
> So a 30s processing overhead wouldn't respond in time.



if an NMS timeout and retires(repeats the request), it might actually get
the response for the first request when it can actually think it is getting
for the nth repeat request it just made

How does the Master agent react to repeat requests ? Does it identify it. If
it does, does it ignore the responses for the earlier requests. Does it
ignore the later requests/responses etc.

------=_Part_64837_14631104.1157086564983
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


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 of
retries have timed out will they report failure.
Try   "snmpgetnext -d ....." to see this happening.

But a typical setup is something like 3 retries with a 5s timeout.

So a 30s processing overhead wouldn't respond in time.

if an NMS timeout and retires(repeats the request), it might actually get the response for the first request when it can actually think it is getting for the nth repeat request it just made


How does the Master agent react to repeat requests ? Does it identify it. If it does, does it ignore the responses for the earlier requests. Does it ignore the later requests/responses etc.

 



------=_Part_64837_14631104.1157086564983--


--===============0537009018==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=...057&dat=121642
--===============0537009018==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/...net-snmp-users

--===============0537009018==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=...057&dat=121642
--===============0537009018==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/...et-snmp-coders

--===============0537009018==--