Everyone, Thanks for the help - OIDs figured out, configs written, and everything works like a beaut.
-H -----Original Message----- From: Manny Ortega [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 12, 2003 2:44 PM To: 'Barakat, Mehmet-Hasan'; [EMAIL PROTECTED] Subject: RE: [mrtg] Re: Calling MIBs About the whacked out temperature readings: First, you need to find out what the reading means, then you need to perform some calculations. Case in point: I have a Dell server and I'm monitoring ambient temperature on it. This is the OID: 1.3.6.1.4.1.674.10892.1.700.20.1.6.1.1 Doing an snmpget on that OID, I get the following result: 230 230 what? I researched the Dell website and found out that that is Celsius degrees x 10 so the actual temperature is 23 degrees celsius. Great, the ambient temp on that server is 23 degrees Celsius. Now, if I want to display the temp in Fahrenheit, I just perform the following calculation: x 1.8 + 32 That's the formula for converting Celsius to Fahrenheit. Here is the relevant line of my config file: Target[asahi.ambient.temp]: 1.3.6.1.4.1.674.10892.1.700.20.1.6.1.1&1.3.6.1.4.1.674.10892.1.700.20.1.6.1. 5:[EMAIL PROTECTED] / 10 * 1.8 + 32 All in one line. Check it out: http://houweb1.univ-wea.com look for 'temperatures' - they are both Dell servers. Hope that helps. -MannyO -----Original Message----- From: Barakat, Mehmet-Hasan [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 12, 2003 1:12 PM To: [EMAIL PROTECTED] Subject: [mrtg] Re: Calling MIBs Peter/Manny/Dan, Thanks guys - here's what I did: - I added options of gauge, noo, nopercent, integer, withzeroes, - I added a suffix of 1.2 to the OID for the temperature instance, - I check the value versus what I could walk in the MIB. Much further ahead now - I get readings and graphs, thanks. Of course, I only get so far being a rookie ;-) - As was stated by Manny, I get whacked out temp reading of Celsius in tenths times 100, so a typical chart looks like my LAN room is 180 degrees. How can I make that 18 degrees? How can I convert to Fahrenheit? - Every few times I run ./mrtg /configfile, I still get the old error of Target[temp1][_IN_] ' $$target[0]{$mode} ' did not eval into defined data WARNING: skipping update of temp1, inlast is not defined. Noticed if I wait a few minutes, it has a better chance of working. -H -----Original Message----- From: Peter Glanville [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 12, 2003 12:40 PM To: Barakat, Mehmet-Hasan; [EMAIL PROTECTED] Subject: RE: [mrtg] Re: Calling MIBs That's the stuff. "Instance": In a switch or Router, measuring Bytes In, you need to know which port's bytes in you are talking about. Hence you use ifInoctets.2 for port 2 and so on. Your MIB is incomplete. There should be translations all the way down to the end. A table has multiple instances. You might have two sensors, CPU and room perhaps. The chances are that you do not have two temperature sensors, so I would suggest you may be measuring Current and Max or Average, or something Look at the numbers and see what you think they mean (or plot them and see how they go) If MRTG has the MIB included, you could use Target[temp1]: tempHumidSensorTempValue.1.1&tempHumidSensorTempValue.1.2:[EMAIL PROTECTED] , or more reliably go for the more explicit Target[temp1]:.1.3.6.1.4.1.1718.3.2.5.1.6.1.1&.1.3.6.1.4.1.1718.3.2.5.1.6.1. 2:[EMAIL PROTECTED] Also: Gauge option, and Maxbytes values, mentioned in someone else's reply You can do OID maths for Farenheit/Centigrade convertion. GetIf only likes you starting from OIDs that it can translate, hence your problem there. 17:30 in this country, I'm off home now. Continue tomorrow if needed. Regards Peter |---------+----------------------------> | | "Barakat, | | | Mehmet-Hasan" | | | <[EMAIL PROTECTED]| | | m> | | | | | | 12/11/2003 17:17 | | | | |---------+----------------------------> >--------------------------------------------------------------------------- ---------------------------------------------------| | | | To: "'Peter Glanville'" <[EMAIL PROTECTED]>, [EMAIL PROTECTED] | | cc: | | Subject: RE: [mrtg] Re: Calling MIBs | >--------------------------------------------------------------------------- ---------------------------------------------------| Peter, Thanks for the info. I have Getif on a Windoze box, and I can browse the MIB fine. I get .1.3.6.1.4.1.1718.3.2.5.1.6 correlating to .iso.org.dod.internet.private.enterprises.serverTech.sentry3.systemTables.te mpHumidSensorTable.tempHumidSensorEntry.tempHumidSensorTempValue but down in the frame, there are two values that pop up when I hit Start : .iso.org.dod.internet.private.enterprises.serverTech.sentry3.systemTables.te mpHumidSensorTable.tempHumidSensorEntry.tempHumidSensorTempValue.1.1 *and* .iso.org.dod.internet.private.enterprises.serverTech.sentry3.systemTables.te mpHumidSensorTable.tempHumidSensorEntry.tempHumidSensorTempValue.1.2. Is this what you mean when you say "instance"? I need the info from the second one, which is the temperature. If I append the original entry up top to add in the suffix .1.1 or .1.2, Getif fails to retrieve the value - it only likes it when I leave it as .1.3.6.1.4.1.1718.3.2.5.1.6. Any clues? I'd like to browse the MIB from my RedHat MRTG station - any recommendations on what to use? -H -----Original Message----- From: Peter Glanville [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 12, 2003 11:29 AM To: Barakat, Mehmet-Hasan; [EMAIL PROTECTED] Subject: Re: [mrtg] Re: Calling MIBs > Target[temp1]: .1.3.6.1.4.1.1718.3.2.5.1.6&.1.3.6.1.4.1.1718.3.2.5.1.6:[EMAIL PROTECTED] > >There isn't much there. What's wrong? The above OID is listed in the MIBs, but does the box support it? Walk the MIB (eg using GetIf) and see what is there. That will also show the correct instance number if needed. PS. You do not NEED a MIB in MRTG. A MIB merely translates Name to OID number eg ifInOctets = .1.3.6.1.2.1.2.2.1.10 So if you wish to specify the Name on the Target line, MRTG needs to have the MIB to translate. If you are going to specify the full OID, Mrtg does not need the MIB. Peter **************************************************************************** * The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to our clients any opinions or advice contained in this email are subject to the terms and conditions expressed in the governing KPMG client engagement letter. **************************************************************************** * **************************************************************************** * The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to our clients any opinions or advice contained in this email are subject to the terms and conditions expressed in the governing KPMG client engagement letter. **************************************************************************** * -- Unsubscribe mailto:[EMAIL PROTECTED] 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 ***************************************************************************** The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to our clients any opinions or advice contained in this email are subject to the terms and conditions expressed in the governing KPMG client engagement letter. ***************************************************************************** -- Unsubscribe mailto:[EMAIL PROTECTED] 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
