You can run this and see your results by going into the c:\mrtg-2.16.2\bin directory and typing: perl mrtg mrtg.cfg PageTop: Traffic Analysis for ulink0Īnd that’s a very basic MRTG config file. This section determines how the web page headers will look PageTop: Traffic Analysis for ether0 TargetDevice’s IP Address:Interface Number:Community:IP Address Target: is the interface speed (Default is 10 megabits for 100Mbit devices use 12500000 and so on…) MaxBytes: 1250000 This is where the web pages are created, usually a web root. In Perl, a # is a comment, synonymous with REM in DOS.Īdd the following to the top of the mrtg.cfg file: WorkDir: c:\www\mrtg Now, let’s take a look at the mrtg.cfg file that was created. If you get an error message complaining about no such name or no response, your community name is probably wrong. In order to work around this you can get cfgmaker to produce a configuration which is based on Ip numbers, or even Interface Descriptions. Unfortunately, these numbers are likely to change whenever you reconfigure your router. Note that in this file all interfaces of your router will be stored by number. This creates an initial MRTG config file for you. Type the following command: perl cfgmaker -global "WorkDir: c:\www\mrtg" -output mrtg.cfg Get to a cmd prompt and change to the c:\mrtg-2.16.2\bin directory. The first thing we do in setting up MRTG is making a default config file. We are interested in monitoring traffic, and the CPU load. If you don’t know it, try public, that is the default.įor the rest of this document we will be using device 10.10.10.1 ( a CISCO Catalyst 5000) with Community string public.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |