Target[ccu101_efficient]: (1.3.6.1.4.1.2979.11.3.3.37.0&1.3.6.1.4.1.2979.11.3.3.37.0:[EMAIL PROTECTED] +
1.3.6.1.4.1.2979.11.3.3.38.0&1.3.6.1.4.1.2979.11.3.3.38.0:[EMAIL PROTECTED]) / 1.3.6.1.4.1.2979.11.3.3.36.0&1.3.6.1.4.1.2979.11.3.3.36.0:[EMAIL PROTECTED] * 30000 YLegend[ccu101_efficient]: Channel Efficiency ShortLegend[ccu101_efficient]: % MaxBytes[ccu101_efficient]: 100 Options[ccu101_efficient]: growright, integer, unknaszero, nopercent, gauge I think it has to do with the fact that a real number is being logged and not an integer. But it was my understanding that MRTG would automatically ROUND, That's IN the DOC. But apparently it isn't so... How can I get around this? Notice that the config is a calculation based on multiple OIDs. It does work but the log is a real number. Thanks Duane ----- Original Message ----- From: "PAUL WILLIAMSON" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Monday, September 29, 2003 3:24 PM Subject: Re: [mrtg] Re: one more graph problem... Good point. What is that MaxBytes set to? Sorry, I deleted the previous post. Anyway, you may want to include integer as an option as well. Paul >>> "Duane Cox" <[EMAIL PROTECTED]> 09/29/03 04:16PM >>> Paul Thanks, but I'm using the gauge option, so I didn't think I would need to * 300 ... Duane -- 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
