in reply to Re: Re: Re: Net::SNMP get_request() caching results?
in thread Net::SNMP get_request() caching results?

You're exactly right, the error happens on one remote node. So, say node 100 with ip 192.168.1.101 has 10 snmp commands run against it, well if there is one error on all snmp commands, the error will stay. Even though I'm destroying the snmp session and starting a new one, for the node will fail no matter how many commands I have to run.

Here's the error from the snmp object that I usually receive...

No response from remote host '192.168.1.101'

This has happened using a URL or a straight ip like above. So, it doesn't seem to be a timeout, it looks like it *thinks* it can't hit it, when I try telnetting into the router and everything is fine, it just got stuck again. hmmm.....
  • Comment on Re: Re: Re: Re: Net::SNMP get_request() caching results?

Replies are listed 'Best First'.
Re: Re: Re: Re: Re: Net::SNMP get_request() caching results?
by c (Hermit) on Nov 08, 2001 at 19:13 UTC
    That error response is one that I constantly see, however its usually comes up when either something is blocking the actual packets from getting through to the remote host. I would ask if it were possibly caused by sending an oid to the remote device that required a RW string and only a RO was configured, but I *think* that would produce a different error response.

    Have you tried running each of the snmp commands individually against the remote host to see if you can find one in particular that times out against it, or if its the host in general?

    humbly -c