You need to use the snmp command snmpwalk to walk through the MIB of a device 
to know the OID of a particular object. I would suggest getif(runs on 
windows...use google you can find it). This will give in detail as which OID 
relates to which object, but it will only describe about that OID it if it has 
that particular MIB pre-compiled in it. I am not sure whether your device MIB's 
are pre-compiled in getif or not. So try using use getif to know the OID of 
what you are looking for, if you cant find it through getif then the only other 
way i know is to look for it in theĀ  vender documentation. Perhaps others over 
here can suggest better ways of finding an OID for a particular object.

Best regards  Venkat


--- On Mon, 8/31/09, Barun Biswas <[email protected]> wrote:

From: Barun Biswas <[email protected]>
Subject: Re: [mrtg] serverirons CPU utilization
To: "Venkat praneeth Nangineni" <[email protected]>, [email protected]
Date: Monday, August 31, 2009, 2:09 PM



Thanks Venkat, Mcdonald.



I have configured the MRTG graph
as per your suggestion and it looks fine now.





For last couple of days I am looking
for serveriron oid which can tell me the number of CPUs in the server.
Can anyone please point me to the right oid? Can you please let me know
the url from where I can get the oid for serveriron?





Regards,

Barun.=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you





      
_______________________________________________
mrtg mailing list
[email protected]
https://lists.oetiker.ch/cgi-bin/listinfo/mrtg

Reply via email to