AW: problem with hrStorage

2011-12-02 Thread Andreas Schnederle-Wagner - Futureweb . at
>On 2 December 2011 13:21, Andreas Schnederle-Wagner - Futureweb.at > wrote: >> using Nagios SNMP checks to monitor our Server HDD usage. >> >> With "snmpwalk  -v 2c -c public  localhost  hrStorage" I get back all >> the needed information. >> >> . other stuff . >> HOST-RESOURCES-MIB::hrStorageDe

AW: problem with hrStorage

2011-12-02 Thread Andreas Schnederle-Wagner - Futureweb . at
>On 2 December 2011 13:36, Andreas Schnederle-Wagner - Futureweb.at > wrote: >> the agent is vendor-supplied. Same Versions on both systems: > >> Also the config options look the same: > >Hmmm > >OK - so the difference must be something to do with the two systems themselves. > >What does the c

AW: problem with hrStorage

2011-12-05 Thread Andreas Schnederle-Wagner - Futureweb . at
-Ursprüngliche Nachricht- Von: dave.shi...@googlemail.com [mailto:dave.shi...@googlemail.com] Im Auftrag von Dave Shield Gesendet: Freitag, 02. Dezember 2011 17:43 An: Andreas Schnederle-Wagner - Futureweb.at Cc: net-snmp-users@lists.sourceforge.net Betreff: Re: problem with hrStorage On

AW: problem with hrStorage

2011-12-12 Thread Andreas Schnederle-Wagner - Futureweb . at
One other weird thing on this problem: it worked on one of our Servers for 4-5 days without problems. Today - about 1 hour ago - it stopped working ... "snmpwalk -v 2c -c public localhost hrStorage" just won't give out the partition anymore?! How can it be that it worked a few days - and the

Re: AW: problem with hrStorage

2012-08-09 Thread Andreas Schnederle-Wagner
Hello, maybe someone got a new idea after some time went by? As I still face the same Problem. I just updated some older Centos servers (5.4) to 5.8 --> and they got the same Problems as Centos 6.x now ... Can't get information about my parititons anymore ... so some change within SNMP (which has

Re: AW: problem with hrStorage

2014-04-08 Thread Andreas Schnederle-Wagner
Andreas Schnederle-Wagner futureweb.at> writes: > > Hello, > > maybe someone got a new idea after some time went by? As I still face the same > Problem. I just updated some older Centos servers (5.4) to 5.8 --> and they got > the same Problems as Centos 6.x now ... Can't get information about m