* [1]Multi Router Traffic Grapher - Configuration File Format
* [2]Global Configuration
* [3]Optional Global Parameters
+ [4]Refresh
+ [5]Interval
+ [6]WriteExpires
+ [7]IconDir
+ [8]LoadMIBs
+ [9]Language
+ [10]UseRRDTool
+ [11]RunAsDaemon
* [12]Configuration for each Target you want to monitor
+ [13]Target
+ [14]RouterUptime
+ [15]MaxBytes
+ [16]MaxBytes1
+ [17]MaxBytes2
+ [18]Title
+ [19]PageTop
* [20]Optional Target Configuration Tags
+ [21]AddHead
+ [22]AbsMax
+ [23]Unscaled
+ [24]WithPeak
+ [25]Suppress
+ [26]Directory
+ [27]XSize and YSize
+ [28]XZoom and YZoom
+ [29]XScale and YScale
+ [30]YTics and YTicsFactor
+ [31]Step
+ [32]Options
+ [33]kilo
+ [34]kMG
+ [35]Colours
+ [36]Background
+ [37]YLegend, ShortLegend, Legend[1234]
+ [38]Timezone
+ [39]Weekformat
* [40]Threshold Checking
+ [41]ThreshDir (GLOBAL)
+ [42]ThreshMinI (PER TARGET)
+ [43]ThreshMaxI (PER TARGET)
+ [44]ThreshDesc (PER TARGET)
+ [45]ThreshProgI (PER TARGET)
+ [46]ThreshProgOKI (PER TARGET)
+ [47]ThreshMinO, ThreshMaxO, ThreshProgO, and ThreshProgOKO
* [48]Two very special Target names
* [49]And one more very special Target name
* [50]NoSpaceChar
* [51]Some example mrtg.cfg files
+ [52]Minimal mrtg.cfg
+ [53]Cfg for several Routers.
_________________________________________________________________
[INLINE]
_________________________________________________________________
Multi Router Traffic Grapher -- Configuration File Format
This file is for use with MRTG 2.8.12
Note:
* Keywords must start at the beginning of a line.
* Lines which follow a keyword line which do start with a blank are
appended to the keyword line
* Empty Lines are ignored
* Lines starting with a # sign are comments.
_________________________________________________________________
Global Configuration
Workdir specifies where the logfiles and the webpages should be
created.
Example:
WorkDir: /usr/tardis/pub/www/stats/mrtg
_________________________________________________________________
Optional Global Parameters
_________________________________________________________________
Refresh
How many seconds apart should the browser (Netscape) be instructed to
reload the page? If this is not defined, the default is 300 seconds (5
minutes).
Example:
Refresh: 600
_________________________________________________________________
Interval
How often do you call mrtg? The default is 5 minutes. If you call it
less often, you should specify it here. This does two things:
* the generated HTML page does contain the right information about
the calling interval ...
* a META header in the generated HTML page will instruct caches
about the time to live of this page .....
In this example we tell mrtg that we will be calling it every 10
minutes. If you are calling mrtg every 5 minutes, you can leave this
line commented out.
Example:
Interval: 10
_________________________________________________________________
WriteExpires
With this switch mrtg will generate .meta files for CERN and Apache
servers which contain Expiration tags for the html and gif files. The
*.meta files will be created in the same directory as the other files,
so you will have to set ``MetaDir .'' and ``MetaFiles on'' in your
apache.conf or .htaccess file for this to work
NOTE: If you are running Apache-1.2 or later, you can use the
mod_expire to achieve the same effect ... see the file htaccess.txt
Example:
WriteExpires: Yes
_________________________________________________________________
IconDir
If you want to keep the mrtg icons in some place other than the
working directory, use the IconDir variable to give its url.
Example:
IconDir: /mrtgicons/
_________________________________________________________________
LoadMIBs
Load the MIB file(s) specified and make its OIDs available as symbolic
names. For better efficiancy, a cache of MIBs is maintained in the
WorkDir.
Example:
LoadMIBs: /dept/net/mibs/netapp.mib,/usr/local/lib/ft100m.mib
_________________________________________________________________
Language
Switch output format to the selected Language (At the moment, the
values: danish, french, english, dutch, brazilian, russian, spanish,
greek and italian are supported)
Example:
Language: danish
_________________________________________________________________
UseRRDTool
Setting UseRRDTool to Yes in your mrtg.cfg file enables rrdtool mode.
In rrdtool mode, mrtg relies on rrdtool to do its logging. Graphs and
html pages will be generated on the fly by the 14all.cgi which can be
found in the contrib section together with a short readme ... This
feature has been contributed by
[54]Rainer.Bawidamann@informatik.uni-ulm.de. Please check his website
for more information: [55]http://www.uni-ulm.de/~rbawidam/mrtg-rrd/
Example:
UseRRDTool: Yes
_________________________________________________________________
RunAsDaemon
The RunAsDaemon keyword enables daemon mode operation. The purpose of
daemon mode is that MRTG is launched once and not at regular basis by
cron as in native mode. This behavior saves computing resourses as
loading and parsing of configuration files only hapens once.
Using daemon mode MRTG itself is responible for timing the measurement
intervals. Therfore its important to set the Interval keyword to an
apropiate value.
Note that using daemon mode MRTG should no longer be started from cron
by regular basis as each started process runs forever. Instead MRTG
should be started from the command prompt or by a system startup
script.
Also note that in daemon mode restart of the process is required in
order to activate changes in the config file.
Under UNIX, the Daemon switch causes mrtg to fork into background
after checking its config file.
Example
RunAsDaemon:Yes
Interval:5
Makes MRTG run as a daemon beginning data collection every 5 minutes
_________________________________________________________________
Configuration for each Target you want to monitor
The configuration keywords Target must be followed by a unique name.
This will also be the name used for the webpages, logfiles and gifs
created for that target.
Note that the Target sections can be auto-generated with the cfgmaker
tool. Check readme.html for instructions.
_________________________________________________________________
Target
With the Target keyword you tell mrtg what it should monitor. The
Target keyword takes arguments in a wide range of formats:
* The most basic format is ``port:community@router'' This will
generate a traffic graph for the interface 'port' of the host
'router' (dns name or IP address) and it will use the community
'community' (snmp password) for the snmp query.
Example:
Target[ezwf]: 2:public@wellfleet-fddi.ethz.ch
* Sometimes you are sitting on the wrong side of the link, and you
would like to have mrtg report Incoming traffic as outgoing and