<html dir="ltr"><head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css">P {
MARGIN: 0px
}
</style>
<meta name="GENERATOR" content="MSHTML 8.00.6001.18812">
<style title="owaParaStyle"><!--P {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
--></style>
</head>
<body ocsi="x">
<div dir="ltr"><font color="#000000" size="2" face="Tahoma">I'd really suggest using cfgmaker templates to generate the various Targets. This way you will get all-numerical OIDs (so no problems with unrecognised short symbolic names) and also the host cfgmaker
template in the website probes for th existance of the various OIDs before creating the Target definition, so you wont get one that doesnt exist.</font></div>
<div dir="ltr"><font size="2" face="tahoma"></font> </div>
<div dir="ltr"><font size="2" face="tahoma">The cfgmaker documentation tells you the details, but basically you just use
</font></div>
<div dir="ltr"><font size="2" face="tahoma"> </font><font size="2" face="tahoma">cfgmaker --host-template=template.htp
<a href="mailto:community@hostname">community@hostname</a></font></div>
<div dir="ltr"><font size="2" face="tahoma">if your monitored host is 'hostname' with snmp community 'community' and the host template is called 'template.htp'. An interface template is similar, except that it is run once PER DETECTED INTERFACE rather than
just once.</font></div>
<div dir="ltr"><font size="2" face="tahoma"></font> </div>
<div dir="ltr"><font size="2" face="tahoma">Note that there are some problems with using SNMP -</font></div>
<div dir="ltr"><font size="2" face="tahoma">1. You need to make sure it is enabled</font></div>
<div dir="ltr"><font size="2" face="tahoma">2. You need to make sure the apporpriate sections are enabled - eg with Linux you need to have the appropriate lines in the /etc/snmp/snmpd.conf to enable disk space checks, load average checks, and so on</font></div>
<div dir="ltr"><font size="2" face="tahoma">3. Different OSs support different parts of the OID tree. For example, Windows and Linux give different places for data, and so do Solaris, Cisco and so on. Plus different vendors have vendor-specific extensions
which may or may not be useful.</font></div>
<div dir="ltr"><font size="2" face="tahoma">4. You need to set up your permissions correctly to allow the monitoring server rights to view the OID tree correctly</font></div>
<div dir="ltr"><font size="2" face="tahoma">5. With Windows in particular, the Storage mappings can be re-enumerated on the fly if you plug in or remove USB devices. This can mess up storage graphs done via SNMP. You may be better off with something the like
mrtg-storage check plugin which uses SNMP but confirms the table has not been re-enumerated.</font></div>
<div dir="ltr"><font size="2" face="tahoma"></font> </div>
<div dir="ltr"><font size="2" face="tahoma">If you run with the all-hosts host template from
<a href="http://www.steveshipway.org/cfgmaker">www.steveshipway.org/cfgmaker</a> and it doesnt generate any Targets then check your SNMP configuration.</font></div>
<div dir="ltr"><font size="2" face="tahoma"></font> </div>
<div dir="ltr"><font size="2" face="tahoma">Steve</font></div>
<div dir="ltr"><font size="2" face="tahoma"></font> </div>
<div style="DIRECTION: ltr" id="divRpF244740">
<hr tabindex="-1">
<font size="2" face="Tahoma"><b>From:</b> mrtg-bounces@lists.oetiker.ch [mrtg-bounces@lists.oetiker.ch] On Behalf Of Matt Baer [matt@baerconsult.com]<br>
<b>Sent:</b> Saturday, 26 September 2009 9:58 a.m.<br>
<b>To:</b> mrtg<br>
<b>Subject:</b> [mrtg] CPU and RAM Utiliziation for Windows Machine<br>
</font><br>
</div>
<div></div>
<div>
<div style="FONT-FAMILY: Arial; COLOR: #000000; FONT-SIZE: 12pt">I'm having some issues with monitoring the CPU and RAM of a Phenom machine running Vista. I'd like to watch all 4 cores. I'm sure it's a problem with OID. But don't know what to switch to.
This is what I get in my logs:<br>
<br>
SNMP Error:<br>
Received SNMP response with error code<br>
error status: noSuchName<br>
index 1 (OID: 1.3.6.1.4.1.2021.4.6.0)<br>
</div>
</div>
</body>
</html>