ZenPack:NetApp Monitor

From Zenoss Wiki
Revision as of 19:07, 9 April 2013 by Eedgar (Talk | contribs)$7

Jump to: navigation, search


Note: This ZenPack is available in commercial versions of Zenoss. Click here to request more information about this commercial ZenPack. Click here to see all commercial ZenPacks.

Organization
Zenoss, Inc.
ZenPack name
ZenPacks.zenoss.NetAppMonitor

Devices Monitored:

Applications Monitored: 



NetApp Monitor ZenPack

NetAppMonitor provides additional modeling and monitoring for NetApp devices. NFS, CIFS and HTTP opera- tions per second are collected, as well as file system and snapshot utilization information.

Warning

The ZenPack Catalog has moved to its new home at https://www.zenoss.com/product/zenpacks as of January 17, 2017. The following information may be out of date, and this page will eventually be removed.

Support

This ZenPack is included with commercial versions of Zenoss and enterprise support for this ZenPack is provided to Zenoss customers with an active subscription.

Releases

Background

NetAppMonitor provides additional modeling and monitoring for NetApp devices. NFS, CIFS and HTTP operations per second are collected, as well as file system and snapshot utilization information. Hardware model and operating system revision asset information is modeled.

The NetApp ZenPack uses reports provided by the StorageBase ZenPack.

Features

The features added by this ZenPack can be summarized as follows. They are each detailed further below.

  • Native NetApp ZAPI protocols or SNMP protocols
  • Monitoring of Peformance Component Metrics
  • Optional service impact with addition of Zenoss Service Dynamic Product.

Protocols

Place a device in the '/Storage/NetApp/7-Mode' or '/Storage/NetApp/C-Mode' Device classes to enable Native NetApp ZAPI based monitoring of the NetApp Appliance. Placing a device in the '/Storage/NetApp/SNMP' Device class will enable legacy snmp monitoring of the NetApp Appliance.

Asset information
  • Hardware Model
  • Operating System Revision
Device metrics
  • Network bits/sec: Send and Received
  • Operations/sec: NFS, CIFS and HTTP
File system metrics
  • File system utilization (90% threshold)
  • Snapshot utilization (120% threshold)
7-Mode and C-Mode Zapi monitoring will model
  • Disks
    • IO metrics; busy metrics; transfers
  • Volumes
    • Capacity; extensible by the user.
  • Luns
    • Latency; Data and Ops
  • Lun Clients
    • N/A
  • Plexes
    • N/A
  • Aggregates
    • Capacity of files and filesystems,
    • Inode and Space used metrics
  • Raid Groups
    • N/A
  • Interfaces
    • Network in/out/errors
  • Disk Shelves
    • N/A
  • VServers
    • N/A
  • QTrees
    • cifs/nfs/internal ops
  • System Nodes
    • uptime,busytime and failed fan counts.
  • Filesystems
    • usage
NetApp uses SSH to model NFS clients of file systems. It uses SNMP to model
  • Disks
  • storage enclosures
  • RAID groups
  • Plexes
  • Aggregates
  • Volumes
  • LUNs
  • QTrees
  • LUN clients
  • Licenses

Prerequisites

  • Zenoss >= 4.1.1
  • ZenPacks.zenoss.StorageBase
  • ZenPacks.zenoss.PythonCollector >= 1.0.1

Configuration

  • C-Mode/7-Mode
   zCommandUser
   zCommandPassword
   zNetAppSSL (true = enabled)
  • SNMP
   configure the snmp settings to match the NetApp Filer
   configure zCommandUser/zCommandPass for ssh access to gather NFS Client information
  • Events (all versions)
   configure v1 or v2 traps to be sent to Zenoss Resource Monitor
   forward syslog events by logging into the NetApp Device, configure syslog, add the following
   *.* @yourzenossserver
   replace yourzenossserver with the ip or dns entry of your zenoss server

Daemons

  • zenmodeler (modeling)
  • zenpython (zapi performance metrics)
  • zenperfsnmp (legacy snmp performance metrics)
  • zencommand (legacy command based performance metrics)


Collecting Additional ZAPI Performance metrics

   Most components are collecting performance metrics from the perf subsection of the zapi api calls.
   When modelling we collect the base uuid and store the information as a set of component xpath entries.
   In most cases we need to just add a new datapoint to the existing datasource, and then add the appropriate 
   xpath fragment to retrieve the appropriate data.
   Samples of the xpath strings can be found in ZenPacks.zenoss.NetAppMonitor/yaml/Cmode
   Be cautious when enabling new metrics as large numbers of components can significantly increase the number
   of monitored datapoints being collected.


Installation

Normal Installation (packaged egg)

  1. Download the appropriate egg file for the version of Zenoss you are running.
  2. Ensure you are logged in as the zenoss user:
    $ sudo su - zenoss
  3. Install the ZenPack:
    $ zenpack --install ZenPacks.zenoss.NetAppMonitor-*.egg
  4. Restart these services:
    $ zenoss restart


Discuss

Purplemarker.png New: Don't forget to add yourself to the Zenoss User Map!

blog comments powered by Disqus