Subscribe

Netapp monitoring

hi,

I am a newbie of Netapp filers. I have a question about the netap monitoring. 

we use check_netapp3.pl in groudwork(Nagios) to monitor our netapp filers.

1) we monitor the following items but I am not sure whether they are enough.   Would you please let me know if anything important I miss?

   by the way, our devices are all Netapp FASXXX.

connectivity(alive)

failed disk/fan/power supplies

global status

overtemperature

cpuload

volume utilization

uptime

nvram battery status

2) We have about 30 Netapp filers right now. and there are many volumes residing on each filer. 

Since we reclaim volumes or create new volumes every so often, the volumes are dynamic and changing. I am wondering that is that possible Groundwork can update these changes automatically or periodically?

Or else we need to inform the monitoring team to add volume or delete volume for monitoring from Groundwork every time we make the change……..

as far as I know, they update this mannually. thus some newly created volumes are omitted. and some obsolete volumes are still in the groudwork.......

hope you can help point me the right direction for me....

thanks in advance

Re: Netapp monitoring

Hi,

you can use NetApp® OnCommand® management software it will help you control,
automate, and analyze your storage infrastructure:

  http://www.netapp.com/us/products/management-software/

good luck,

Ariel

Re: Netapp monitoring

Hi,

You need to manually change nagios configs when adding / deleting a volume, unless you have some sort of inventory tool from what you generate nagios configs.

 

Have a look at OnCommand (DFM in the past), it's capable of sending SNMP traps, which you can convert into nagios sms's etc.

 

Vladimir

Re: Netapp monitoring

The most important things to add to your list are probably per volume IO latency for reads and writes, per volume operations (reads, write, others), and viewing these on the aggregate level as well, both in the total for the aggregate, and the top volume's contributing to that aggregate's IO load.

Plus snapmirror lag, snap shot volume utilization and autosupport success.

Less critical I'd add cache age, PAM statistics, LUN queueing, and physical disk utilization (good to know if oyu need to rebalance.)

You really need a tool that is going to dynamically discover new/deleted/changed volumes, and monitor all the right stuff automatically.

LogicMonitor does this very nicely.

Re: Netapp monitoring

thanks Ariel

Re: Netapp monitoring

good idea. I will try it .

thanks

Vladimir

Re: Netapp monitoring

it's helpful

thanks steve