[SNMP4J] Determining Cause of Communication Error

[Frank Fock]

Hi Chuck,

When using UDP you cannot get any information
about why not getting a response. That's how
connection less protocols operate. With
ICMP you cannot check a port (you can only
check if a certain IP address is reachable).

So that only way to improve performance is
using async requests.

Best regards,
Frank

Chuck wrote:
> I am working on an application that is using 
> SNMP v1 to query a large number of devices
> for 3 or 4 OIDs.
> 
> We are running into a performance problem since
> we use retries for each read attempt and send
> a new PDU for each OID.  Is there a way to
> determine the cause of communications error
> using SNMP4J?  I'd really like to determine
> if there is no response or if an ICMP packet
> was received indicating that port 161 is
> unreachable.  Being able to determine the
> cause of the communication error, other 
> than timeouts, would go a long ways to
> improving performance.
> 
> So far the only indication I've found of
> determining a communication error is that
> the ResponseEvent#getResponse() returns
> a null if there was a problem.  This 
> doesn't really tell if the port itself
> is unreachable though. 
> 
> 
> Thanks in advance,
> 
> Chuck
> _______________________________________________
> SNMP4J mailing list
> SNMP4J at agentpp.org
> http://lists.agentpp.org/mailman/listinfo/snmp4j

-- 
AGENT++
http://www.agentpp.com
http://www.mibexplorer.com
http://www.mibdesigner.com