-1

H i ,

I've been experiencing that with MRTG .. the bandwidth not goes larger than 120 Mbps, MRTG would not display it correctly
my servers 1Gb port speed, and I download and upload by this speed, But MRTG graph not shoving traffic more than 120M.
Please, has anyone experienced this? can somebody help?

http://oss.oetiker.ch/mrtg/

Thanks.

ALMGHARI
  • 9
  • 2
  • 6

1 Answers1

0

This is a common problem caused by 16-bit counter rollover.

If you are polling your device every 5min (the default) using SNMPv1, then a traffic greater than 120Mbps will cause the 16bit counter to wraparound in this time window. Hence, MRTG only displays the lower traffic as it cannot tell how many times the counter has rolled over.

You have two options:

  1. Use SNMPv2. This is the best option, if your device supports it (most do). If using SNMPv2, then you can use the 64bit counters, which will not wrap around. To do this, add ':::::2' as a suffix to your Target definition to specify SNMPv2. Eg:

Target[ezwf]: 1:community@router:::::2

  1. Increase polling frequency. You can change your polling to every 1 minute using 'Interval:1' , which increases your capacity by a factor of 5. However, note that this will require you to delete your old rrd or log file and recreate it; also you will need to deal with any changes to your scheduling method, and all Targets will use the same polling frequency.

MRTG documentation is available at http://oss.oetiker.ch/mrtg/doc/mrtg-reference.en.html and covers the SNMPv2c target syntax as well as the changes in interval.

Steve Shipway
  • 3,754
  • 3
  • 22
  • 39
  • Thank you,, But for the first option, What is the commands that I add in ssh , for edit this? >>>> # Target[ezwf]: 1:community@router:::::2 >>>> -bash: Target[ezwf]:: command not found – ALMGHARI Oct 29 '14 at 07:48
  • I succeeded by change time in crontab -e from 5m */5 * * * * to */1 * * * * 1m >>> */1 * * * * LANG=C /usr/local/mrtg-2/bin/mrtg /etc/mrtg/mrtg.cfg ,, only ,,, now my MRTG Graph more 120Mb >> Thanks. – ALMGHARI Oct 29 '14 at 10:31
  • But stop now on 560Mb , no more !! – ALMGHARI Oct 29 '14 at 12:48
  • This is why option 1 was the best choice -- option 2 only gives you 5x as much headroom. The line I gave is only an example of the line in the MRTG configuration file, not a command to type in; you'll need to edit your MRTG configuration file /etc/mrtg/mrtg.cfg and add the trailing :::::2 to the appropriate Target lines. – Steve Shipway Oct 29 '14 at 22:53
  • like this?: Target[localhost_2]: 2:public@localhost:::::2 ***** this old line: Target[localhost_2]: 2:public@localhost: – ALMGHARI Oct 30 '14 at 10:16
  • Yes, that should tell MRTG to use SNMPv2c to make the query. – Steve Shipway Nov 02 '14 at 05:18