Hello, Does the same happen when you change the default timeout say with your snmpwalk -t 10 [the rest of your arguments] (for 10 sec), and does the same happen if you try to do a snmpwalk on the tree that appears last just before the timeout? 24.06.2014, 16:37, "sarath azad" :Hello, Could you ple
irely, if you
> don't need that data. But since it's Cacti, I guess you're doing network
> discovery and this is out of the question?
>
> BR,
> Joel
>
> On Tue, Jun 17, 2014 at 11:40 AM, chris tech wrote:
>> I think I know what this is now, no idea how
eed that data. But since it's Cacti, I guess you're doing network
> discovery and this is out of the question?
>
> BR,
> Joel
>
> On Tue, Jun 17, 2014 at 11:40 AM, chris tech wrote:
>
>> I think I know what this is now, no idea how to fix it.
>>
>> Apparently
xSize.127.0.0.1 = INTEGER: 32767
Timeout: No Response from 10.29.0.117
How come this starts happening, so weird.
13.06.2014, 13:03, "chris tech" :
> Hello all,
>
> Release 49.el6_5.1 on CentOS (2.6.32-279.9.1.el6.x86_64). Using this with
> Cacti and spine poller process though
rupt net-snmp's connection?
13.06.2014, 13:03, "chris tech" :
> Hello all,
>
> Release 49.el6_5.1 on CentOS (2.6.32-279.9.1.el6.x86_64). Using this with
> Cacti and spine poller process though I came here to ask for help as I can
> replicate the problem with only snmp tools
Hello all,
Release 49.el6_5.1 on CentOS (2.6.32-279.9.1.el6.x86_64). Using this with Cacti
and spine poller process though I came here to ask for help as I can replicate
the problem with only snmp tools on the same box. Firstly it's a big cacti,
1900 devices, been working for months with no pro
