Re: cpu load thr MRTG

alsayed · ‎04-28-2007

Hello!

i have this version of switch:

Switch#sh ver

Cisco Internetwork Operating System Software

IOS (tm) C3500XL Software (C3500XL-C3H2S-M), Version 12.0(5)XU, RELEASE SOFTWARE (fc1)

Compiled Mon 03-Apr-00 17:31 by swati

Image text-base: 0x00003000, data-base: 0x00301398

ROM: Bootstrap program is C3500XL boot loader

Switch uptime is 1 hour, 39 minutes

System returned to ROM by power-on

System image file is "flash:c3500XL-c3h2s-mz-120.5-XU.bin"

cisco WS-C3548-XL (PowerPC403) processor (revision 0x01) with 16384K/1024K bytes of memory.

Processor board ID 0x17, with hardware revision 0x00

Last reset from power-on

Processor is running Enterprise Edition Software

Cluster command switch capable

Cluster member switch capable

48 FastEthernet/IEEE 802.3 interface(s)

2 Gigabit Ethernet/IEEE 802.3 interface(s)

32K bytes of flash-simulated non-volatile configuration memory.

Base ethernet MAC Address: 00:02:B9:B8:C7:40

Motherboard assembly number: 73-3903-04

Power supply part number: 34-0971-01

Motherboard serial number: FAA04299PML

Power supply serial number: PAC042801MZ

Model revision number: A0

Motherboard revision number: B0

Model number: WS-C3548-XL-EN

System serial number: FAA0428F1HV

Configuration register is 0xF

i need to monitor the CPU Load for this switch;can i know the MIB OR OID To use it in my cfg file?

10xs

royalblues · ‎04-28-2007

I did not find the MIB for this switch in the Cisco MIB locator.

However we use solarwinds and it is able to poll a 3548XL for CPU load.

Will try to find out the OID from the solarwinds database

Narayan

Amit Singh · ‎04-28-2007

Hi Ali,

Which Network Management software are you using in the network? I have few customers of mine using the same CPU load montioring with HO Openview Unicenter. They have built in OID's to montior the CPU load for devices.

HTH,

-amit singh

alsayed · ‎04-28-2007

Hi Amit!

i will monitor the CPU Thought the MRTG;AMIT I Sent u mail plz check it.

Regards

ALI

10XS

Danilo Dy · ‎04-29-2007

Hi Ali,

I'm not using 3500 anymore. I use mrtg to monitor cpu, memory and disk of win2k3 and linux servers and cpu, memory, and interfaces of pix firewalls. I use cricket primarily for cisco devices. I'm able to run cricket in windows 2k3.

However, try this for 3500;

Target[hostname.cpu]: .1.3.6.1.4.1.9.9.109.1.1.1.1.4.1&.1.3.6.1.4.1.9.9.109.1.1.1.1.5.1:snmp_read_only_community@hostname

Dandy

m_elbatniji · ‎04-29-2007

I am using the same OID I found on MRTG website (http://oss.oetiker.ch/mrtg/doc/mrtg-nt-guide.en.html) check the example at the end of the page. I didn't know that there are different OIDs for CPU for each model. I have different models in my network (6513,4507,3750) and I have configured MRTG to monitor the CPUs of all these model using the same OID:

Target[traget_CPU]:1.3.6.1.4.1.9.2.1.58.0&1.3.6.1.4.1.9.2.1.58.0:community_string@ipaddress

So far I am getting results from MRTG on CPU usage from all models. So try that OID. Please anyone let me know If I really should be using different OIDs for each model. Thanks.

Joe Clarke · ‎05-13-2007

The OID 1.3.6.1.4.1.9.2.1.58.0 is avgBusy5 from the OLD-CISCO-SYS-MIB. This OID is deprecated, and may not be accurate for all devices. It certainly will not work for CatOS devices. A more current OID is cpmCPUTotal5min (1.3.6.1.4.1.9.9.109.1.1.1.1.5) from the CISCO-PROCESS-MIB. It, too, is deprecated, but it much more universally supported. The best object to use (provided your device is new enough to support it) is cpmCPUTotal5minRev (1.3.6.1.4.1.9.9.109.1.1.1.1.8).

There is a big difference between these two objects and avgBudy5, though. The two cpmCPUTotal5min objects are part of a table, and so they will have non-zero instance numbers. Before you can use these objects in MRTG, you will need to figure out which instance to monitor. Typically, the instance you want will be 1 (for example, this will always be 1 on the 3750), but on multi-CPU boxes, you may want to monitor all CPUs. So you should first walk the cpmCPUTotalTable (1.3.6.1.4.1.9.9.109.1.1.1) to see which CPU instances you can monitor, then configure MRTG accordingly.