The sample MRTG script from Smartbridges (Version 1.2 anyway - I didn't check 1.1) has an error in the scaling of values:
The following line causes MRTG to report bits/second: Options[DEVICE_NAME]: noinfo, growright, bits which would be OK if it didn't then force the labels to be Bytes with this line: Legend1[DEVICE_NAME]: Bytes In Legend2[DEVICE_NAME]: Bytes Out And it's Bits/Sec not: YLegend[DEVICE_NAME]: Bytes/min Using the sample as is gives you bits/second, labeled Bytes, with a Bytes/Min legend. Quite confusing and maybe the cause of some of the perceived throughput problems. If you omit the Legend1, Legend2 and YLegend lines MRTG will nicely figure things out automatically with the correct units. Including the option 'bits' is, um, optional but MRTG will do the correct thing with regard to labeling. Mark Radabaugh Amplex (419) 720-3635 The PART-15.ORG smartBridges Discussion List To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe smartBridges <yournickname> To Remove: mailto:[EMAIL PROTECTED] (in the body type unsubscribe smartBridges) Archives: http://archives.part-15.org
