[mrtg] Re: Cisco 7500 --long, repost from "router temperature" th read

[Roth, Gabrielle]

> Greetings,
> 
> Does anyone know the OIDs for temperature in CISCO 7500 routers?
> 
> Thanks all,

Here is my post from a few days ago that never made it into the archive:
-----

> -----Original Message-----
> From: Sharon Segal [mailto:SharonSe at INFONET-IL.com]
> Sent: Tuesday, November 27, 2001 4:05 AM
> To: Mrtg Mailing List (E-mail)
> Subject: [mrtg] Router temperature .
> 
> 
> may be some body can help me with the router temperature graph .

Assuming Cisco routers...(sing it with me:) this is only going to work on
certain model #s/IOS combos.  I have done this successfully with 72xx, 75xx,
and 12008s running >12.0.  You can do this on certain switches as well, but
it requires a completely different set of OIDs and isn't nearly as
entertaining.

There are a few examples of temperature cfgs in the list archive (see link
at bottom of email). But instead of just giving you the OIDs, let's create
the target "from scratch".  This is fun, and will help you create your own
targets in the future.

To save some time, we'll pretend we already know the OID we need is in
CISCO-ENVMON-MIB (ftp://ftp.cisco.com/pub/mibs/oid/CISCO-ENVMON-MIB.oid):
(There may be other MIBs that work for you...that's the fun part.)

ciscoEnvMonTemperatureStatusEntry looks promising, so let's go for a walk:
snmpwalk myrouter public .1.3.6.1.4.1.9.9.13.1.3.1

We get back something like this:
enterprises.9.9.13.1.3.1.2.1 = "RSP(4) Inlet"
<--ciscoEnvMonTemperatureStatusDescr
enterprises.9.9.13.1.3.1.2.2 = "RSP(4) Hotpoint"
enterprises.9.9.13.1.3.1.2.3 = "RSP(4) Exhaust"
enterprises.9.9.13.1.3.1.3.1 = Gauge32: 18
<--ciscoEnvMonTemperatureStatusValue
enterprises.9.9.13.1.3.1.3.2 = Gauge32: 25
enterprises.9.9.13.1.3.1.3.3 = Gauge32: 28
enterprises.9.9.13.1.3.1.4.1 = 50
<--ciscoEnvMonTemperatureThreshold
enterprises.9.9.13.1.3.1.4.2 = 60
enterprises.9.9.13.1.3.1.4.3 = 101
	...other stuff

(Note these are in °C...probably not a problem for anyone but certain
countries who refuse to convert to the metric system.  But I'm not bitter.)

I usually monitor inlet and exhaust, and set my "MaxBytes" to RoomTemp
(72°F, 25°C?), and the "AbsMax" to the value of the inlet Treshold.

Plug in the values and create our target cfg:
Target[myrouter.temp]:
1.3.6.1.4.1.9.9.13.1.3.1.3.1&1.3.6.1.4.1.9.9.13.1.3.1.3.3:public at myrouter*1.
8+32
MaxBytes[myrouter.temp]: 72
AbsMax[myrouter.temp]: 122
Options[myrouter.temp]: gauge, nopercent, growright
YLegend[myrouter.temp]: Temp in deg F
ShortLegend[myrouter.temp]: \260F
LegendI[myrouter.temp]: &nbsp;Inlet:
LegendO[myrouter.temp]: &nbsp;Exhaust:
Legend1[myrouter.temp]: Average Inlet
Legend2[myrouter.temp]: Average Exhaust
Legend3[myrouter.temp]: Max Inlet
Legend4[myrouter.temp]: Max Exhaust
	...etc

Note that this has been modified for °F.

I am working on a patch to cfgmaker that will create target(s) for
temperature monitoring if the box supports it.  Don't hold your breath
though, it's one of those "in my spare time" projects, and the 12000s are
giving me fits.

-----
-gabrielle
"Five out of four people have a problem with math."

--
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