spk-logo-tm-2023
0%
1-888-310-4540 (main) / 1-888-707-6150 (support) info@spkaa.com
Select Page

How to Monitor NetApps with Nagios

windchill features best plm software
Written by Mike Solinap
Published on January 17, 2011
I just came to the realization that I’ve been working with Network Appliance filers for over a decade now. They’re great — rock solid stability, an ever expanding feature set, excellent tech support, and they’re certified against many enterprise applications including VMware and Oracle. In terms of remote server monitoring, Netapps are most commonly managed through either a web interface (FilerView), or through the Data OnTap command line interface. They also support SNMP, which is essential not only for large scale monitoring deployments such as HP OpenView, but it is also essential for smaller, roll-your-own solutions such as Nagios. What I love most about Nagios is its flexibility. You can monitor a device in a way that you’re most familiar with. For instance, to check a volume’s capacity, you could write a perl script that fetches the appropriate FilerView page and parses it for the appropriate value. Or, you could write an expect script that logs into the CLI. The Nagios plugins package does include a check_snmp utility, but wading through MIB files, parsing snmpwalk output, setting up communities can be a little aggravating at times. I’ve put together a brief howto document that can get you monitoring Netapps with Nagios in no time flat. Subscribe to our blog to keep informed on remote server monitoring, remote server management and remote application management. Mike Solinap Sr. Systems Integrator, SPK

Latest White Papers

Introducing Atlassian’s Service Collection

Introducing Atlassian’s Service Collection

Are you looking for new tools that empower your teams to deliver exceptional service experiences? Atlassian’s Service Collection ensures great service for both employees and customers. What You Will Learn In the following eBook, you will discover: The tools and...

Related Resources

5 Ways to Reduce Engineering Cycle Time Without Adding Headcount

5 Ways to Reduce Engineering Cycle Time Without Adding Headcount

Key takeaways Faster engineering does not always require more headcount: Disconnected systems, manual handoffs, rework, and poor visibility often create more delays than a lack of engineering capacity. A digital thread can eliminate major sources of wasted time:...

Why Late-Stage Changes Are Killing Your Time to Market

Why Late-Stage Changes Are Killing Your Time to Market

Key Takeaways Late-stage changes get expensive fast: The farther a problem travels through design, testing, and manufacturing, the more time, cost, and rework it creates. Disconnected systems and weak traceability are major causes: When requirements, design, software,...

The Engineering Digital Thread Playbook

The Engineering Digital Thread Playbook

In many organizations, systems operate independently, creating a large visibility problem. A digital thread addresses this by creating a connected flow of product information across the lifecycle. This playbook explains why engineering visibility matters, and how...