I’m beginning to wrap my head around the pass script. I understand why if the
OID is COMPANY.4 that COMPANY.4.0 is returned so the next time a GETNEXT is
asked for a COMPANY.5.0 can be returned.
I’m wondering how to work without the .0 at the end and how to code this all in
sh(1)...?
Mike
Am Donnerstag, 6. November 2008 16:14 schrieb Engelbert Roidl:
> > Why don't you use laLoad or laLoadInt?
> >
> > Michael.
>
> WhatsUp uses predefined Perfomance Counter. I would like to use this!
> For laLoad/laLoadInt I have to define Custom Perfomance Counters.
>
> I defined them, but hrProcesso
> Why don't you use laLoad or laLoadInt?
> Michael.
WhatsUp uses predefined Perfomance Counter. I would like to use this!
For laLoad/laLoadInt I have to define Custom Perfomance Counters.
I defined them, but hrProcessorLoad would be more elegant and consistent.
The Problem are the HP Manag
2008/11/6 Engelbert Roidl <[EMAIL PROTECTED]>:
> Now I tried to pass the requests to a script via the "pass" directive in
> snmpd.conf
> "pass .1.3.6.1.2.1.25.3.3.1.2.768 /usr/bin/perl /root/stat.pl"
That tells the agent to use the script /root/stat.pl for any information
in the subtree rooted a
Am Donnerstag, 6. November 2008 15:15 schrieb Engelbert Roidl:
> Hello,
>
> I'm using Debain Etch on a HP Proliant DL380G5, HP Management Agents and
> WhatsUp Gold. WhatsUp tries to get CPU values from .1.3.6.1.2.1.25.3.3.1.2
> which is not implemented in Debian Etch.
>
> Now I tried to pass the re
Hello,
I'm using Debain Etch on a HP Proliant DL380G5, HP Management Agents and
WhatsUp Gold.
WhatsUp tries to get CPU values from .1.3.6.1.2.1.25.3.3.1.2 which is not
implemented in Debian Etch.
Now I tried to pass the requests to a script via the "pass" directive in
snmpd.conf
"pass .1.3.6.1
