Monitoring using MIBs

[Miah, W (Wadud)]

Here's an example on using snmpwalk:

snmpwalk -Of -c public -v1 -m IFT-SNMP-MIB 172.16.140.35 private

where the MIB is stored in /usr/share/snmp/mibs/. The MIB can also be
specified in the check_snmp plugin, which obtains it from the specified
path. Examine the MIB first and browse through the output of snmpwalk to
obtain OID of interest. 

Hope this helps.

-----Original Message-----
From: nagios-users-bounces at lists.sourceforge.net
[mailto:nagios-users-bounces at lists.sourceforge.net] On Behalf Of Hugo
Rebello
Sent: 18 December 2007 11:20
To: nagios-users at lists.sourceforge.net
Subject: [Nagios-users] Monitoring using MIBs

Can anyone help me ?

I'd like to monitor a specific proxy service (Blue Coat) and I don't
know if Nagios works with different mibs.
Anybody knows a good tip about that ?

Thank you.

Cheers,
Hugo




------------------------------------------------------------------------
-
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketp
lace
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when
reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null

-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null