Re: Cisco CPU [7:36765]
You will be needing the scripts for monitoring the CPU and memory .Add them in your mrtg.cfg file and run the mrtg again. The MIBs are Memory :1.3.6.1.4.1.9.2.1.8.0 CPU :1.3.6.1.4.1.9.2.1.57.0 1.3.6.1.4.1.9.2.1.57.0 Make sure you calculate your memory correctly so that your graph show the correct levels. Let me know if it helps Ziyad - Original Message - From: Richard Tufaro To: Sent: Thursday, February 28, 2002 9:01 AM Subject: Cisco CPU [7:36765] Hey guys..a little off topic but where is the BEST place to find out how to install and configure Cisco CPU and Memory stats with MRTG. I get to somix and the MIB's but what do i do with them? Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=36789t=36765 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: Cisco CPU [7:36765]
Here's a pretty good link to clarify what mibs you can use per product http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml Cisco Press' Performance Fault Management reccomends the following for monitoring CPU utilization: Name: avgBusy5 Type: OBJECT-TYPE OID: 1.3.6.1.4.1.9.2.1.58 Full path: iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).cisco(9).local(2) .lsystem(1).avgBusy5(58) Module: OLD-CISCO-CPU-MIB Parent: lsystem Prev sibling: avgBusy1 Next sibling: idleCount Numerical syntax: Integer (32 bit) Base syntax: INTEGER Composed syntax: INTEGER Status: mandatory Max access: read-only Description: 5 minute exponentially-decayed moving average of the CPU busy percentage. and Name: avgBusy1 Type: OBJECT-TYPE OID: 1.3.6.1.4.1.9.2.1.57 Full path: iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).cisco(9).local(2) .lsystem(1).avgBusy1(57) Module: OLD-CISCO-CPU-MIB Parent: lsystem Prev sibling: busyPer Next sibling: avgBusy5 Numerical syntax: Integer (32 bit) Base syntax: INTEGER Composed syntax: INTEGER Status: mandatory Max access: read-only Description: 1 minute exponentially-decayed moving average of the CPU busy percentage. and Name: busyPer Type: OBJECT-TYPE OID: 1.3.6.1.4.1.9.2.1.56 Full path: iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).cisco(9).local(2) .lsystem(1).busyPer(56) Module: OLD-CISCO-CPU-MIB Parent: lsystem Prev sibling: authAddr Next sibling: avgBusy1 Numerical syntax: Integer (32 bit) Base syntax: INTEGER Composed syntax: INTEGER Status: mandatory Max access: read-only Description: CPU busy percentage in the last 5 second period. Not the last 5 realtime seconds but the last 5 second period in the scheduler. versions of IOS later than 12.0(3)T may use similar entries from the CISCO-PROCESS mib, such as Name: cpmCPUTotal5minRev Type: OBJECT-TYPE OID: 1.3.6.1.4.1.9.9.109.1.1.1.1.8 Full path: iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).cisco(9).ciscoMgm t(9).ciscoProcessMIB(109).ciscoProcessMIBObjects(1).cpmCPU(1).cpmCPUTotalTab le(1).cpmCPUTotalEntry(1).cpmCPUTotal5minRev(8) Module: CISCO-PROCESS-MIB Parent: cpmCPUTotalEntry Prev sibling: cpmCPUTotal1minRev Numerical syntax: Gauge (32 bit) Base syntax: Gauge Composed syntax: Gauge Status: mandatory Max access: read-only Size list: 1: 0..100 Description: The overall CPU busy percentage in the last 5 minute period. This object deprecates the object cpmCPUTotal5min and increases the value range to (0..100). Most of the lsystem node is actually devoted to buffer counters. Even though I figure that most of the others might be useful for monitoring memory, the authors single out: Name: bufferNoMem Type: OBJECT-TYPE OID: 1.3.6.1.4.1.9.2.1.47 Full path: iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).cisco(9).local(2) .lsystem(1).bufferNoMem(47) Module: OLD-CISCO-MEMORY-MIB Parent: lsystem Prev sibling: bufferFail Next sibling: busyPer Numerical syntax: Integer (32 bit) Base syntax: INTEGER Composed syntax: INTEGER Status: mandatory Max access: read-only Description: Count of the number of buffer create failures due to no free memory. and Name: bufferFail Type: OBJECT-TYPE OID: 1.3.6.1.4.1.9.2.1.46 Full path: iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).cisco(9).local(2) .lsystem(1).bufferFail(46) Module: OLD-CISCO-MEMORY-MIB Parent: lsystem Prev sibling: bufferLgCreate Next sibling: bufferNoMem Numerical syntax: Integer (32 bit) Base syntax: INTEGER Composed syntax: INTEGER Status: mandatory Max access: read-only Description: Count of the number of buffer allocation failures. Which should help in pinpointing memory limitations. In general, I found the information to be more accessible offline than on, but that could just be a lack of patience . . . - Original Message - From: Richard Tufaro To: Sent: Wednesday, February 27, 2002 11:01 PM Subject: Cisco CPU [7:36765] Hey guys..a little off topic but where is the BEST place to find out how to install and configure Cisco CPU and Memory stats with MRTG. I get to somix and the MIB's but what do i do with them? Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=36790t=36765 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: Cisco CPU [7:36765]
Caveat regarding the available memory The textfile itself reveals: OID: 1.3.6.1.4.1.9.2.1.8 Full path: iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).cisco(9).local(2) .lsystem(1).freeMem(8) Description: Return the amount of free memory in bytes. NOTE WELL: this mib object is obsolete as of IOS release 11.1. IOS release 11.1 introduced the CISCO-MEMORY-POOL-MIB which better instruments all of the memory pools Here's the pointer to the allegedly more modern set of counters: OID: 1.3.6.1.4.1.9.9.48 Full path: iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).cisco(9).ciscoMgm t(9).ciscoMemoryPoolMIB(48) Again, I'm not sure when or if cisco will stop supporting the deprecated MIBs. - Original Message - From: Ziyad To: Sent: Thursday, February 28, 2002 7:05 AM Subject: Re: Cisco CPU [7:36765] You will be needing the scripts for monitoring the CPU and memory .Add them in your mrtg.cfg file and run the mrtg again. The MIBs are Memory :1.3.6.1.4.1.9.2.1.8.0 CPU :1.3.6.1.4.1.9.2.1.57.0 1.3.6.1.4.1.9.2.1.57.0 Make sure you calculate your memory correctly so that your graph show the correct levels. Let me know if it helps Ziyad - Original Message - From: Richard Tufaro To: Sent: Thursday, February 28, 2002 9:01 AM Subject: Cisco CPU [7:36765] Hey guys..a little off topic but where is the BEST place to find out how to install and configure Cisco CPU and Memory stats with MRTG. I get to somix and the MIB's but what do i do with them? Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=36793t=36765 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Cisco CPU [7:36765]
Target[2621_cpu]: 1.3.6.1.4.1.9.2.1.57.01.3.6.1.4.1.9.2.1.58.0:@ MaxBytes[2621_cpu]: 100 AbsMax[2621_cpu]: 100 Options[2621_cpu]: gauge,nopercent,growright Unscaled[2621_cpu]: dwmy YLegend[2621_cpu]: Utilization ShortLegend[2621_cpu]: % LegendI[2621_cpu]: nbsp;1 Min: LegendO[2621_cpu]: nbsp;5 Min: Legend1[2621_cpu]: AvgBusy 1 Min Legend2[2621_cpu]: AvgBusy 5 Min Title[2621_cpu]: 2621_Kansas Router CPU Utilization PageTop[2621_cpu]: 2621_Kansas Router CPU Utilization Target[2621_mem]: 1.3.6.1.4.1.9.9.48.1.1.1.5.11.3.6.1.4.1.9.9.48.1.1.1.6.1:@ MaxBytes[2621_mem]: 15365292 Options[2621_mem]: gauge,nopercent,growright Unscaled[2621_mem]: dwmy YLegend[2621_mem]: Memory Used ShortLegend[2621_mem]: Bytes LegendI[2621_mem]: nbsp;Used LegendO[2621_mem]: nbsp;Free Legend1[2621_mem]: Memory Used Legend2[2621_mem]: Memory Free Title[2621_mem]: 2621_Kansas Memory Utilization PageTop[2621_mem]: Memory Utilization of 2621_Kansas Memory CPU = Just go with 100% MEMORY is router specific.. telnet to the router and do show mem.. if i found MIT_CORE_1sh mem HeadTotal(b) Used(b) Free(b) Lowest(b) Largest(b) Processor 62298CE090600224 48963288570389685493368 85631408 I/O790 7340032 2273784 5066248 5041504 5066012 90600224 would be my maxbytes for mem. I use Processor mem in my mrtg configs.. because i think the other parts of my memory in I/0 are reserved for IOS and shouldn't be counted.. plus the OID only concerns processor memory. Joseph Brunner ASN 21572 MortgageIT MITLending New York, NY 10038 (212) 651 - 7695 Voice (212) 651 - 7795 Fax -Original Message- From: Richard Tufaro [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 27, 2002 11:02 PM To: [EMAIL PROTECTED] Subject: Cisco CPU [7:36765] Hey guys..a little off topic but where is the BEST place to find out how to install and configure Cisco CPU and Memory stats with MRTG. I get to somix and the MIB's but what do i do with them? Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=36769t=36765 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: Cisco CPU [7:36765]
I'm not sure you can get away without knowing the exact addressing for the value you wish to monitor. Unless things have changed recently, you need to take the oid values for the parameter you want to monitor, figure out what the index number of the entity you want information about (such as a ppp interface, ospf area or a global parameter), join them together and place the result in a configuration for a particular graph. (Note: these examples are using generic mibs, since I don't have compiled versions of the cisco mibs handy. Since, based on your subject line, you're interested in router health, and want CPU statistics, I'm concerned that IOS version might be an issue, since Cisco has been migrating from one set of mibs to another over time, and I'm not aware of non-proprietary mibs for router memory cpu usage-If anyone knows better, please enlighten). Unfortunately, I've not been happy with the detail on readily available sites addressing non-prepackaged snmp monitoring of cisco-specific variables: the most comprehensive one I've found is the somix templates site. For those willing to work through it , here's a partial overview addressing the what do you do with them part of the question. 1. figuring out what you want to monitor: MIB files are generally viewable via wordpad; I'm told they're in ASN.1 syntax (I haven't read the ISO documents myself, so I can't verify that), which some people find unwieldy, but you can certainly find descriptions associated with a given OID: Name: ospfSpfRuns Type: OBJECT-TYPE OID: 1.3.6.1.2.1.14.2.1.4 Full path: iso(1).org(3).dod(6).internet(1).mgmt(2).mib-2(1).ospf(14).ospfAreaTable(2). ospfAreaEntry(1).ospfSpfRuns(4) Module: OSPF-MIB Parent: ospfAreaEntry Prev sibling: ospfImportAsExtern Next sibling: ospfAreaBdrRtrCount Numerical syntax: Counter (32 bit) Base syntax: Counter32 Composed syntax: Counter32 Status: mandatory Max access: read-only Description: The number of times that the intra-area route table has been calculated using this area's link-state database. This is typically done using Dijkstra's algorithm. So, If you're interested in the description (to verify your ospf implementation's stability or lack thereof) , you'd use the OID value indicated. Note some tools such as MG-SOFT (disclosure: paying customer) or even snmputilg make this a lot, lot easier (I don't remember if Getif, the free one, can display the description of the object). The transmission node, iso(1).org(3).dod(6).internet(1).mgmt(2).mib-2(1).transmission(10), contains some useful media-specific sub-nodes (frame-relay, DS3 others) featuring, at a minimium, error traffic counts as well as state information. 2. Figuring out the instance ID/index: if you're interested in, say excessive collisions for a specific interface, you would issue an SNMPWALK on the following oid to get the list of available instances, and append the one you're looking for to 1.3.6.1.2.1.10.7.2.1.9 Name: dot3StatsExcessiveCollisions Type: OBJECT-TYPE OID: 1.3.6.1.2.1.10.7.2.1.9 Full path: iso(1).org(3).dod(6).internet(1).mgmt(2).mib-2(1).transmission(10).dot3(7).d ot3StatsTable(2).dot3StatsEntry(1).dot3StatsExcessiveCollisions(9) Module: EtherLike-MIB Parent: dot3StatsEntry Prev sibling: dot3StatsLateCollisions Next sibling: dot3StatsInternalMacTransmitErrors Numerical syntax: Counter (32 bit) Base syntax: Counter Composed syntax: Counter Status: mandatory Max access: read-only Reference: IEEE 802.3 Layer Management Description: A count of frames for which transmission on a particular interface fails due to excessive collisions. 3. Placing the results in a graph's configuration (sample excerpted from http://www.bubbagates.com/mrtg/mrtg.cfg): The line beginning with Target specifies the target SNMP object. ### PPP Dial-In Modem Lines on AS53001 (Scranton) ### Target[AS53001]: 1.3.6.1.4.1.9.10.19.1.1.4.01.3.6.1.4.1.9.10.19.1.1.5.0:[EMAIL PROTECTED] PageTop[AS53001]: PPP Dial-In Modem Lines on AS53001 (Scranton) - Original Message - From: Richard Tufaro To: Sent: Wednesday, February 27, 2002 11:01 PM Subject: Cisco CPU [7:36765] Hey guys..a little off topic but where is the BEST place to find out how to install and configure Cisco CPU and Memory stats with MRTG. I get to somix and the MIB's but what do i do with them? Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=36777t=36765 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
