|MRTG Implementation Manual
Table of Contents
3. Configuring MRTG tasks
A .cfg file is required for each monitored host or a global .cfg file can be used for all monitored hosts, but the flexibility will decrease.
A .cfg file defines the SNMP OIDs for each entity that you intend to monitor from the destination host. MRTG parses the associated .cfg file and collects the SMNP values for all OIDs defined in the .cg file.
To build a .cfg file run the “CFGMAKER” script, which resides in the \mrtg\bin\ directory. This script scans a host for the network-interfaces only and constructs the .cfg file
The syntax is:
perl cfgmaker [options] [community@]router1 [[options] [community@]router2 ... ]
The CFGMAKER options are:
MRTG will interrogate the target host, will extract the SNMP OIDs for all network interfaces and construct the .cfg file for that specific host.
Once the .cfg file has bee constructed, the following
folder options must be added to the file:
The PNG graphs are growing by default from right
to left and are represented in Bytes/sec.
Options[_]: growright, bits
Here is a CFGMAKER usage example and the resulted
The HTML index files are being built based on the previously created .cfg file. The role of the index.html file is to put together the html links to the individual network interfaces that are being monitored.
The index file is created by INDEXMAKER script.
perl indexmaker [options] [.cfg file]
The options are:
IndexMaker will create an html file, which has to be copied (recommended as index.html) into the folder where the html/image/log files are stored.
perl indexmaker --output d:\mrtg\10.1.1.10.index
After proceeding with the previous steps, the current MRTG status should be:
a. Perl, MRTG and the WebServer are installed.
d. Next step: Get the MRTG process running and visualize
the variation graphs.