I suggest you do the following from the machine that will be running MRTG, which, in this case, is also a web server. All examples are for doing things to a LOCAL machine.
Unzip MRTG to C:\mrtg-2.12.1 on the Windowsmachine of your choice.
Install Perl on the same Windows machine. You might want to make sure that the Perl binary directory is listed in your system path.
C:\Perl\bin;%SystemRoot%\system32;%SystemRoot%;...You can manually check this by going to Control Panel->System->Environment
To see if everything is installed properly you can open a Command Shell and go into c:\mrtg-2.12.1\bin. Type:
This should give you a friendly error message complaining about the missing mrtg configuration file. Now, you have successfully installed mrtg and perl
Operating System All windows version
Fabric Operating System All fabric os that support SNMP
Other see: /mrtg-2.12.1/doc/mrtg-nt-guide.html for more detail
NOTES (INCLUDING LIMITATIONS)
Now it is time to create a configuration for mrtg. But before we begin you need to know a few things. Take an opportunity to gather the following information:
The IP address or hostname and the snmp port number, (if non standard), of the device you want to monitor.
If you want to monitor something other than bytes in and out, you must also know the SNMPOID of what you want to monitor.
Finally you need to know the read-only SNMP community string for your device. If you don't know it, try public, that is the default.
For the rest of this document we will be using device 10.10.10.1 ( a CISCO Catalyst 5000) with Community string public. We are interested in monitoring traffic, and the CPU load. Let's begin.
The first thing we do in setting up mrtg is making a default config file. Get to a cmd prompt and change to the c:\mrtg-2.12.1\bin directory. Type the following command:
perl cfgmaker email@example.com --global "WorkDir: c:\www\mrtg" --output mrtg.cfgThis creates an initial MRTG config file for you. Note that in this file all interfaces of your router will be stored by number. Unfortunately, these numbers are likely to change whenever you reconfigure your router. In order to work around this you can get cfgmaker to produce a configuration which is based on Ip numbers, or even Interface Descriptions. Check the cfgmaker manpage
If you get an error message complaining about no such name or no response, your community name is probably wrong.
Now, let's take a look at the mrtg.cfg file that was created.
NOTE: This contribution was migrated by Brocade from the former Brocade Connect community on March 13, 2008, on behalf of the author.