[mrtg] Re: monitoring a cisco 3640...(Newbie needs help!!!)

Daniel J McDonald dmcdonald at digicontech.com
Tue Aug 28 15:48:56 MEST 2001


>I,m a newbie in monitoring and have not this big experience in mrtg..
Nor, obviously, of reading maillist archives

>I want to monitor a cisco 3640 (Cpu load/util ,traffic ) .
Right.
>Do i only need the mibs ???
No, you need a config for mrtg that uses the mibs.

>Has someone ever monitored this device??
Naturally.  This question is asked about once every other week.
OK, here we go again:
traffic can be monitored just fine using the cfgmaker program.

cpu and memory need to have hand-crafted entries.  The entries are pretty
much the same whether the router is a Cisco 1600 or a GSR or anything in
between, but you've got to check how many cpus are being monitored and find
the right one, and how many memory pools are being monitored and pick the
one you are interested in.

There are two mibs that contain this information.  The Cisco monolithic mib,
supported since before I started playing with these beasts (IOS 7), has a
couple of basic counters.  As of IOS 10.3 Cisco has been promising to
eliminate the monolithic mib "in a version upcoming soon" and has added new
mib trees with much more information available.  These mibs are known as the
CISCO-PROCESS-MIB and the CISCO-MEMORY-POOL-MIB.

Temperature cannot be measured on this box since the sensor has only three
settings: not hot enough to worry about, pretty hot, and "Help me! I'm
melting!"

Lots of other things can be monitored, depending on what you have in the
box.  ISDN lines in use?  No problem.  Concurrent voice calls?  Little
harder, still doable.  T1 Physical errors?  if someone can figure that one
out, let me know - The DS1 mib resets counters every 15 minutes.

All that said, here's a config for memory and cpu monitoring on a 3640:
unscaled[_]: M
toptalker*group[_]: memory
######################################################################
# System: Austin3640
# Description: Cisco Internetwork Operating System Software
#     Contact:
# System Name: Austin3640
#    Location:
#.....................................................................

Target[Austin3640_cpu]:
1.3.6.1.4.1.9.9.109.1.1.1.1.5.1&1.3.6.1.4.1.9.9.109.1.1.
1.1.3.1:11874 at 172.16.0.1
MaxBytes[Austin3640_cpu]: 100
toptalker*group[Austin3640_cpu]: cpu
RouterUptime[Austin3640_cpu]: 11874 at 172.16.0.1
Options[Austin3640_cpu]: Gauge
Title[Austin3640_cpu]: Austin3640 CPU
YLegend[Austin3640_cpu]: CPU Utilization
ShortLegend[Austin3640_cpu]: %
Legend1[Austin3640_cpu]: 5 min CPU Utilization
Legend2[Austin3640_cpu]: 5 sec CPU Utilization
Legend3[Austin3640_cpu]:
Legend4[Austin3640_cpu]:
LegendI[Austin3640_cpu]: 5min
LegendO[Austin3640_cpu]: 5sec
PageTop[Austin3640_cpu]: <H1>CPU</H1>
 <TABLE>
   <TR><TD>System:</TD><TD>Austin3640 in </TD></TR>
 </TABLE>


######################################################################
# Description: Cisco Internetwork Operating System Software IOS (tm) 3600
Softwa
re (C3640-IO3S56I-M), Version 12.0(5)T1, RELEASE SOFTWARE (fc1) Copyright
(c) 19
86-1999 by cisco Systems, Inc. Compiled Tue 17-Aug-99 20:50 by cmong
#     Contact:
# System Name: Austin3640
#    Location:
#.....................................................................

Target[Austin3640_mem]:
1.3.6.1.4.1.9.9.48.1.1.1.7.1&1.3.6.1.4.1.9.9.48.1.1.1.6.
1:11874 at 172.16.0.1
MaxBytes[Austin3640_mem]: 100663296
RouterUptime[Austin3640_mem]: 11874 at 172.16.0.1
Options[Austin3640_mem]: Gauge
Title[Austin3640_mem]: Austin3640 Memory
YLegend[Austin3640_mem]: Free memory
ShortLegend[Austin3640_mem]: B
Legend1[Austin3640_mem]: Largest Block
Legend2[Austin3640_mem]: Free Memory
Legend3[Austin3640_mem]:
Legend4[Austin3640_mem]:
LegendI[Austin3640_mem]: Block
LegendO[Austin3640_mem]: Free

PageTop[Austin3640_mem]: <H1>Memory</H1>
 <TABLE>
   <TR><TD>System:</TD><TD>Austin3640 in </TD></TR>
 </TABLE>


This same setup should be fine on virtually any router made by Cisco with an
IOS version greater than 10.3.  You may need to walk the mibs to check the
cpu instance or the memory pool instance, but these should work fine for a
3640.



--
Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
Archive     http://www.ee.ethz.ch/~slist/mrtg
FAQ         http://faq.mrtg.org    Homepage     http://www.mrtg.org
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi



More information about the mrtg mailing list