[mrtg] Re: Monitor Solaris CPU from MRTG

[PAUL WILLIAMSON]

You need to add a .0 to the end.  I missed that you were using the 
walk command.  If you look at the response, snmpwalk is kindly filling

in the instance (.0), on to the end of your requested walk.

Try to run an snmpget with the OID and the instance number appended 
before modifying your conf file to verify this is the problem, but I'm
willing 
to bet that's exactly the issue.

Paul


>>> "Brian Steele" <bsteele at morrisprintinggroup.com> 1/25/2005 11:17:06
AM >>>
Paul,

I've used the line you suggested:
Target[milesv_cpu]:
1.3.6.1.4.1.42.3.13.1&1.3.6.1.4.1.42.3.13.1:public at 192.168.150.250 

Now I get a different error:

SNMPGET Problem for 1.3.6.1.4.1.42.3.13.1 1.3.6.1.4.1.42.3.13.1 on
public at 192.168.150.250::::::v4only 
 at /usr/bin/mrtg line 1847
ERROR: Target[milesv_cpu][_IN_] ' $target->[8]{$mode} ' did not eval
into defined data
ERROR: Target[milesv_cpu][_OUT_] ' $target->[8]{$mode} ' did not eval
into defined data

What does v4only mean?

Brian


-----Original Message-----
From: PAUL WILLIAMSON [mailto:pwilliamson at mandtbank.com] 
Sent: Tuesday, January 25, 2005 8:53 AM
To: mrtg at list.ee.ethz.ch; bsteele at morrisprintinggroup.com 
Subject: Re: [mrtg] Monitor Solaris CPU from MRTG

You must use TWO OIDs, not one, not three, but two.  They must be
joined

in the center with an ampersand, otherwise, the magical divination 
shall not work.

Try something like:

Target[milesv_cpu]:
.1.3.6.1.4.1.42.3.13.1&.1.3.6.1.4.1.42.3.13.1:public at 192.168.150.250: 


I can't remember if you need the leading dot in each OID or not...

Paul

>>> "Brian Steele" <bsteele at morrisprintinggroup.com> 1/25/2005 9:45:14
AM >>>
I'm attempting to use MRTG to monitor CPU time on a Solaris 9 server. 
I
cannot figure out how to set up the Target line.  Snmpwalk works fine
with the specified OID.  Here is an example:
 

>snmpwalk -v 1 -c public 192.168.150.250 .1.3.6.1.4.1.42.3.13.1

SNMPv2-SMI::enterprises.42.3.13.1.0 = Counter32: 29628917

 

However, when I set the target line to: 

 

Target[milesv_cpu]: .1.3.6.1.4.1.42.3.13.1:public at 192.168.150.250: 

 

The result is:

 

0' instead of a numberpu][_IN_] '.1.3.6.1.4.1.42.3.13.
$target->[8]{$mode} ' evaluated to '*

0' instead of a numberpu][_OUT_] '.1.3.6.1.4.1.42.3.13.
$target->[8]{$mode} ' evaluated to '*

 

Why does one work and the other not?

 

Brian

 



--
Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe 
Archive     http://www.ee.ethz.ch/~slist/mrtg 
FAQ         http://faq.mrtg.org    Homepage     http://www.mrtg.org 
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi 








--
Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
Archive     http://www.ee.ethz.ch/~slist/mrtg
FAQ         http://faq.mrtg.org    Homepage     http://www.mrtg.org
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi