We've had some success using their API - I have python scripts that pull out network info and latency metrics into our graphite system. We are probably going to switch to this for our Nagios systems as we have seen the SNMP timeout under similar conditions.
I think you can get what you need from the diagnosis API, more specifically the diagnosis-alert-info, but I haven't tested it.
I do find that the API is much quicker than SNMP for bulk queries (all io stats for every volume, for example), and much more reliable. Its an area that rewards some time spent, IMHO..
On 06 Jan 13:53, Momonth wrote:
I'm currently using SNMP to monitor 7-M filers and I'm not entirely happy with it, eg SNMP agent doesn't answer on queries on a busy filer. I'd say the situaion is even worse with SNMP support in cDOT, see http://www.netapp.com/in/media/tr-4220.pdf for details.
I agree, "autosupport" is a "must".
On Wed, Dec 24, 2014 at 3:26 PM, Basil basilberntsen@gmail.com wrote:
No experience with CDOT yet (installing this spring), however generally, for any equipment, I'd be using SNMP for this. I'd have gone through the vendor's MIB file and ensured that the events (like power issues) I need to be notified about are above the notification threshold for my SNMP software. Also, I'd make sure that the box is able to call home and open tickets for critical issues. I've had the vendor help me with that in the past.
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters