[mrtg] Need Help to Configure FWSM CPU utilization MRTG graph...

[Yogesh Suryawanshi]

Dear Daniel,

I am new to MRTG & to this forum

I have browsed multiple pages but can't the template.
I will be happy if you can text in your assistance once again.


Also need one more help
   How to perform SNMP get & SNMP walk.
   Where we have to put these commands i.e. on Cisco box (target device)
or on mrtg server.



Thanks & Regards,
Yogesh S


-----Original Message-----
From: mrtg-bounces at lists.oetiker.ch
[mailto:mrtg-bounces at lists.oetiker.ch] On Behalf Of Daniel J McDonald
Sent: Thursday, May 03, 2007 5:03 PM
To: mrtg at lists.oetiker.ch
Subject: Re: [mrtg] Need Help to Configure FWSM CPU utilization MRTG
graph...

On Thu, 2007-05-03 at 11:49 +0530, Yogesh Suryawanshi wrote:
> HI,
> 
>  
> 
> Here I am trying to configure MRTG for cat 6509 FWSM CPU utilization.
> 
> Following is the code which I am using for 6509 CPU data
> 

> Target[10.33.4.X.cpu]:
> 1.3.6.1.4.1.9.2.1.58.0&1.3.6.1.4.1.9.2.1.58.0:public at 10.33.4.X:


I published a template on this forum just this past week.  There are two
different CPU OIDs, and the instances vary as well.  The only reliable
way to find Cisco CPU is by walking both sets of variables.

You might be surprised to find that some of your boxes have more than
one CPU...

 
> 
-- 
Daniel J McDonald, CCIE # 2495, CISSP # 78281, CNX
Austin Energy
http://www.austinenergy.com

_______________________________________________
mrtg mailing list
mrtg at lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/mrtg


Disclaimer:
-----------------------------------------------------------------
This email and any files transmitted with it may be confidential and intended solely 
for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the sender.
The recipient should check this email and any attachments for the presence of viruses 
and the company accepts no liability for any damage caused by the same. 
Please note that any views or opinions presented in this email are those of the author 
and do not necessarily represent those of WNS Group. 
-----------------------------------------------------------------