Cisco Systems Dial NMS User Manual

Task 3—Using MRTG to Monitor and Graph Traffic Loads

How to Inspect and Interpret Data

$"

Basic Dial NMS Implementation Guide

"/tmp/crontabmMaqZd" 14 lines, 610 characters 

#ident  "@(#)root       1.19    98/07/06 SMI"   /* SVr4.0 1.1.3.1       */

#

# The root crontab should be used to perform accounting data collection.

#

# The rtc command is run to adjust the real time clock if and when

# daylight savings time changes.

#

10 3 * * 0,4 /etc/cron.d/logchecker

10 3 * * 0   /usr/lib/newsyslog

15 3 * * 0 /usr/lib/fs/nfs/nfsfind

1 2 * * * [ -x /usr/sbin/rtc ] && /usr/sbin/rtc -c > /dev/null 2>&1

30 3 * * * [ -x /usr/lib/gss/gsscred_clean ] && /usr/lib/gss/gsscred_clean

On a 5-minute time interval, MRTG will start up, read the configuration file, and re-generate 
performance graphs.

Sending MRTG Graphs to a Web Server

MRTG builds all the graphs and web pages.

To browse and view the graphs produced by MRTG, make sure the web server is running. For 
information on how to set up a web server, go to http://www.apache.org/

To send MRTG graphs to a web server, follow these steps:

Step 1

Verify that the configuration file points to the correct working directory (WorkDir:) on your web server 
by entering the more command. See WorkDir: in the following example. 

igloo:/opt/downloads/mrtg/mrtg-2.8.8/run ->more travis-nas-01.cfg

WorkDir: /export/home/www/mrtg/travis-nas-01/dial

# set defaults

Options[_]: growright

# make legends reflect these are call counters

YLegend[_]: Active Calls

ShortLegend[_]: calls

LegendI[_]:  calls:

LegendO[_]:  calls:

Step 2

To send the web pages and graphs to the web-server directory, enter the following command:

igloo:/opt/downloads/mrtg/mrtg-2.8.8/run ->./mrtg travis-nas-01.cfg

igloo:/opt/downloads/mrtg/mrtg-2.8.8/run ->

Now, the crontab will automatically perform this function every five minutes.

Ignore any Rateup WARNING errors, which means that crontab is working in the background.

Rateup WARNING: .//rateup The backup log file for 172.21.101.20.178 was invalidl

Rateup WARNING: .//rateup Can't remove 172.21.101.20.178.old updating log file

Rateup WARNING: .//rateup Can't rename 172.21.101.20.178.log to 172.21.101.20.1e

Rateup WARNING: .//rateup could not read the primary log file for 172.21.101.209