This is happening again (I assume as a result of Windows Updates) and all my graphs are staying at the last successful SNMP poll. What should I post up?
----- Original Message ----- From: "Steve Shipway" <[email protected]> To: "Matt Baer" <[email protected]> Sent: Friday, September 25, 2009 11:18:20 PM GMT -06:00 US/Canada Central Subject: RE: [mrtg] CPU and RAM Utiliziation for Windows Machine The *4096 and *65536 is to normalise the values reported in the SNMP to bytes (since they are reported in blocks or in MB). It is possible Vista has changed this (again) to report in differnet units. The multiple Warnings oyu get below are due to the SNMP lookup returning nothing. I'd need to snmpwalk your device to find out what OIDs are missing though Steve From: [email protected] [[email protected]] On Behalf Of Matt Baer [[email protected]] Sent: Saturday, 26 September 2009 3:36 p.m. To: mrtg Subject: Re: [mrtg] CPU and RAM Utiliziation for Windows Machine And here I thought I was done. When using the default output from the cfgmaker with that template, it uses a multiplication method as below: # Filesystem C:\ Label: Serial Number 3a8c3a33 Target[192.168.10.75.disk.C]: 1.3.6.1.2.1.25.2.3.1.6.2&1.3.6.1.2.1.25.2.3.1.6.2:[email protected] * 4096 && # Memory used Target[192.168.10.75-memory]: 1.3.6.1.2.1.25.2.3.1.6.14&1.3.6.1.2.1.25.2.3.1.5.14:[email protected] * 65536 2009-09-25 22:00:23: ERROR: Target[desktoppc.mem][_IN_] ' $target->[50]{$mode} * 65536' (warn): Use of uninitialized value in multiplication (*) at (eval 96) line 1. 2009-09-25 22:00:23: ERROR: Target[desktoppc.mem][_OUT_] ' $target->[50]{$mode} * 65536' (warn): Use of uninitialized value in multiplication (*) at (eval 97) line 1. 2009-09-25 22:00:23: ERROR: Target[desktoppc.du.c][_IN_] ' $target->[51]{$mode} * 4096' (warn): Use of uninitialized value in multiplication (*) at (eval 98) line 1. 2009-09-25 22:00:23: ERROR: Target[desktoppc.du.c][_OUT_] ' $target->[51]{$mode} * 4096' (warn): Use of uninitialized value in multiplication (*) at (eval 99) line 1. 2009-09-25 22:00:23: ERROR: Target[desktoppc.du.d][_IN_] ' $target->[52]{$mode} * 4096' (warn): Use of uninitialized value in multiplication (*) at (eval 100) line 1. 2009-09-25 22:00:23: ERROR: Target[desktoppc.du.d][_OUT_] ' $target->[52]{$mode} * 4096' (warn): Use of uninitialized value in multiplication (*) at (eval 101) line 1. So, how do I fix the multiplier issue? The desktoppc.mem is currently showing 128KB used memory.....it has 8GB in there and I have Vista Ultimate 64-bit, anyone notice an issue there? ----- Original Message ----- From: "Matt Baer" <[email protected]> To: "mrtg" <[email protected]> Sent: Friday, September 25, 2009 9:27:39 PM GMT -06:00 US/Canada Central Subject: Re: [mrtg] CPU and RAM Utiliziation for Windows Machine Using the generic template as suggested, I managed to get CPU going on a quad core. Still trying to find a better way to display it so I can see each individual core on one graph, but that's out there on the mailing list now as well. Thank you very much, I think that template may solve the issue I've been having trying to get load values populating in a graph. ----- Original Message ----- From: "Steve Shipway" <[email protected]> To: "Matt Baer" <[email protected]>, "mrtg" <[email protected]> Sent: Friday, September 25, 2009 7:58:43 PM GMT -06:00 US/Canada Central Subject: RE: [mrtg] CPU and RAM Utiliziation for Windows Machine 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. The cfgmaker documentation tells you the details, but basically you just use cfgmaker --host-template=template.htp commun...@hostname 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. Note that there are some problems with using SNMP - 1. You need to make sure it is enabled 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 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. 4. You need to set up your permissions correctly to allow the monitoring server rights to view the OID tree correctly 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. If you run with the all-hosts host template from www.steveshipway.org/cfgmaker and it doesnt generate any Targets then check your SNMP configuration. Steve From: [email protected] [[email protected]] On Behalf Of Matt Baer [[email protected]] Sent: Saturday, 26 September 2009 9:58 a.m. To: mrtg Subject: [mrtg] CPU and RAM Utiliziation for Windows Machine 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: SNMP Error: Received SNMP response with error code error status: noSuchName index 1 (OID: 1.3.6.1.4.1.2021.4.6.0) _______________________________________________ mrtg mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/mrtg
_______________________________________________ mrtg mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/mrtg
