Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … ·...

52
netapp Guide v1.2 series Nimsoft® Monitor™

Transcript of Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … ·...

Page 1: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

netapp Guide v1.2 series

Nimsoft® Monitor™

Page 2: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Legal Notices Copyright © 2012, CA. All rights reserved.

Warranty

The material contained in this document is provided "as is," and is subject to being changed, without notice, in future editions. Further, to the maximum extent permitted by applicable law, Nimsoft LLC disclaims all warranties, either express or implied, with regard to this manual and any information contained herein, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. Nimsoft LLC shall not be liable for errors or for incidental or consequential damages in connection with the furnishing, use, or performance of this document or of any information contained herein. Should Nimsoft LLC and the user have a separate written agreement with warranty terms covering the material in this document that conflict with these terms, the warranty terms in the separate agreement shall control.

Technology Licenses

The hardware and/or software described in this document are furnished under a license and may be used or copied only in accordance with the terms of such license.

No part of this manual may be reproduced in any form or by any means (including electronic storage and retrieval or translation into a foreign language) without prior agreement and written consent from Nimsoft LLC as governed by United States and international copyright laws.

Restricted Rights Legend

If software is for use in the performance of a U.S. Government prime contract or subcontract, Software is delivered and licensed as "Commercial computer software" as defined in DFAR 252.227-7014 (June 1995), or as a "commercial item" as defined in FAR 2.101(a) or as "Restricted computer software" as defined in FAR 52.227-19 (June 1987) or any equivalent agency regulation or contract clause. Use, duplication or disclosure of Software is subject to Nimsoft LLC’s standard commercial license terms, and non-DOD Departments and Agencies of the U.S. Government will receive no greater than Restricted Rights as defined in FAR 52.227-19(c)(1-2) (June 1987). U.S. Government users will receive no greater than Limited Rights as defined in FAR 52.227-14 (June 1987) or DFAR 252.227-7015 (b)(2) (November 1995), as applicable in any technical data.

Trademarks

Nimsoft is a trademark of CA.

Adobe®, Acrobat®, Acrobat Reader®, and Acrobat Exchange® are registered trademarks of Adobe Systems Incorporated.

Intel® and Pentium® are U.S. registered trademarks of Intel Corporation.

Java(TM) is a U.S. trademark of Sun Microsystems, Inc.

Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.

Netscape(TM) is a U.S. trademark of Netscape Communications Corporation.

Oracle® is a U.S. registered trademark of Oracle Corporation, Redwood City, California.

UNIX® is a registered trademark of the Open Group.

ITIL® is a Registered Trade Mark of the Office of Government Commerce in the United Kingdom and other countries.

All other trademarks, trade names, service marks and logos referenced herein belong to their respective companies.

Page 3: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Contact Nimsoft

For your convenience, Nimsoft provides a single site where you can access information about Nimsoft products.

At http://support.nimsoft.com/, you can access the following:

■ Online and telephone contact information for technical assistance and customer services

■ Information about user communities and forums

■ Product and documentation downloads

■ Nimsoft Support policies and guidelines

■ Other helpful resources appropriate for your product

Provide Feedback

If you have comments or questions about Nimsoft product documentation, you can send a message to [email protected].

Page 4: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version
Page 5: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Contents 5

Contents

Chapter 1: netapp 1.2 7

netapp Overview .......................................................................................................................................................... 7

Chapter 2: netapp Probe Deployment 9

Supported Platforms .................................................................................................................................................... 9

System Requirements .................................................................................................................................................. 9

Software Requirements ............................................................................................................................................... 9

Monitoring System Requirements ............................................................................................................................. 10

Probe Deployment Information ................................................................................................................................. 10

Installation Notes ....................................................................................................................................................... 10

Chapter 3: netapp Configuration 11

Probe Defaults ............................................................................................................................................................ 11

Probe Configuration Interface Installation ................................................................................................................. 11

Probe GUI ................................................................................................................................................................... 12

Toolbar Buttons................................................................................................................................................... 13

The Left Pane ...................................................................................................................................................... 13

The Right Pane .................................................................................................................................................... 14

Probe Configuration ................................................................................................................................................... 14

General Setup ..................................................................................................................................................... 15

MIB Setup Wizard ............................................................................................................................................... 16

Create New Agent ............................................................................................................................................... 19

Manage QoS Data and Alarms ............................................................................................................................ 24

Add Monitors ...................................................................................................................................................... 25

Chapter 4: QoS Threshold Metrics 43

netapp QoS Metrics.................................................................................................................................................... 43

netapp Alert Metrics Default Settings ........................................................................................................................ 47

Chapter 5: Troubleshooting and FAQs 49

Probe Performance Criteria ....................................................................................................................................... 49

Robot Environment for Running netapp .................................................................................................................... 50

Network Latency and Connectivity Considerations ................................................................................................... 50

System Memory Considerations ................................................................................................................................ 50

Disk Storage Considerations ....................................................................................................................................... 51

Page 6: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

6 netapp Guide

Number of Devices or Profiles per Probe ................................................................................................................... 51

Number of Metrics Collected per Device per Probe .................................................................................................. 51

Number of QoSs and Alarms Configured per Device Per Probe ................................................................................ 51

Frequency of Metrics Collection per Device per Probe.............................................................................................. 52

Global Metrics Collection Settings ...................................................................................................................... 52

Metrics Collection Settings ................................................................................................................................. 52

Page 7: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Chapter 1: netapp 1.2 7

Chapter 1: netapp 1.2

This description applies to NetApp probe version 1.2.

This section contains the following topics:

netapp Overview (see page 7) Documentation Changes (see page 8)

netapp Overview

The NetApp probe uses SNMP to communicate with storage arrays. The probe transparently handles discovering local as well as remote NetApp systems using SNMP. The probe runs specific SNMP queries and extracts the important information from the devices.

The NetApp filer, also known as NetApp Fabric-Attached Storage (FAS), is a type of disk storage device which owns and controls filesystems, directories, and files present over the network. The NetApp filer uses the Data ONTAP operating system (based on FreeBSD).

NetApp filers can offer the following:

■ Supports SAN, NAS, FC, SATA, iSCSI, FCoE and Ethernet all on the same platform

■ Supports either SATA, FC and SAS disk drives

■ Supports block protocols such as iSCSI, Fibre Channel and AoE

■ Supports file protocols such as NFS, CIFS , FTP, TFTP and HTTP

■ High availability

■ Easy Management

■ Scalable

Page 8: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

netapp Overview

8 netapp Guide

Documentation Changes

This table describes the version history for this document.

Version Date What's New?

1.2 November 2012 ■ Merged memory leak changes and a crash issue.

■ Merged monitoring latency changes.

■ Merged changes to display string corresponding to integer value of state OID.

■ Merged changes to display correct snapshot index.

■ Updated monitor section of documentation.

1.1 October 2011 Updated sections Adding New Agent, To Edit Monitor Properties for API-based Monitor; added information about delta per second; updated for applying default templates.

1.0 March 2011 Initial release of the probe.

Related Documentation

Documentation for other versions of the netapp probe

The Release Notes for the netapp probe

Getting Started with CA Nimsoft® Probes

Monitor Metrics Reference Information for CA Nimsoft Probes

Page 9: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Chapter 2: netapp Probe Deployment 9

Chapter 2: netapp Probe Deployment

This section contains the prerequisites, system requirements and deployment information for the netapp probe.

This section contains the following topics:

Supported Platforms (see page 9) System Requirements (see page 9) Software Requirements (see page 9) Monitoring System Requirements (see page 10) Probe Deployment Information (see page 10) Installation Notes (see page 10)

Supported Platforms

The netapp probe supports the same set of operating systems and databases as supported by the Nimsoft Server solution. Please refer to the Nimsoft Compatibility Support Matrix for the latest information on supported platforms.

System Requirements

The netapp probe should be installed on systems with the following minimum resources:

■ Memory: 2-4GB of RAM. Probe's OOB configuration requires 256MB of RAM'

■ CPU: 3GHz dual-core processor, 32-bit or 64-bit

Software Requirements

The netapp probe requires the following software environment:

■ Nimsoft Monitor Server 5.1.1 or later

■ Nimsoft Robot 5.23 or later

■ Java Virtual Machine 1.6 or later (typically installed with NMS 5.0 and above)

Note: For SOC functionality, NM Server 5.6 or later and UMP 2.5.2 or later is required.

Page 10: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Monitoring System Requirements

10 netapp Guide

Monitoring System Requirements

Some of the components you can monitor using the NetApp probe:

■ General Product information and System Statistics

■ Cluster status

■ Disk

■ Ethernet interface

■ Aggregates

■ Volumes

■ vFiler

■ SnapMirrors

■ SnapVaults

■ Qtree

■ Quotas

Probe Deployment Information

There are two ways to distribute archive packages. You can distribute the package within Infrastructure Manager or use the standalone Nimsoft Distribution application.

See Probe Deployment for more information on deploying probes.

Installation Notes

Follow these steps:

1. Install the package into your local archive

2. Drop the package from your local archive onto the targeted robot(s)

3. Double-click the probe for initial configuration

Page 11: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Chapter 3: netapp Configuration 11

Chapter 3: netapp Configuration

The NetApp probe uses the Simple Network Management Protocol (SNMP) to communicate with storage arrays. The probe uses SNMP to discover local and remote NetApp systems.

You can configure the probe to run specific SNMP queries and extract important information from the devices. You can define alarms to be raised and propagated when specified thresholds are breached.

This section contains the following topics:

Probe Defaults (see page 11) Probe Configuration Interface Installation (see page 11) Probe GUI (see page 12) Probe Configuration (see page 14)

Probe Defaults

At the time of deploying a probe for the first time on robot, some default configuration will get deployed automatically. These probe defaults could be Alarms, QoS, Profiles and so on which save time to configure the default settings. These probe defaults will be seen on a fresh install, that is no instance of that probe is already available on that robot in activated or deactivated state.

Probe Configuration Interface Installation

The probe configuration interface is automatically downloaded and installed by the Nimsoft Infrastructure Manager when the probe is deployed on a robot.

Page 12: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Probe GUI

12 netapp Guide

Probe GUI The GUI window consists of a row of toolbar buttons and two window panes. In addition, a status bar is located at the bottom of the window, showing probe version information and when the probe was started.

Double-click the line representing the probe in the Infrastructure Manager to bring up the configuration interface.

It initially appears with the following defaults in the left pane of the window:

■ The Default Group hierarchy, which is initially empty.

■ The QoS hierarchy, which contains all QoS definitions.

■ The Templates hierarchy, which contains the available templates. Initially only the Sample Templates are present.

Note: You must click the Apply button to activate any configuration modifications.

Page 13: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Probe GUI

Chapter 3: netapp Configuration 13

Toolbar Buttons

There are six toolbar buttons:

■ The General Setup button opens the probe settings dialog box.

■ The Launch MIB Setup Wizard button enables you to install and manage the SNMP MIB files.

■ The Create New Group button enables you to create a new group.

■ The Create New Agent button opens the Profile [New] dialog box.

■ The Get The Current Monitor Values button refreshes the screen and populates the latest values for the monitors.

■ The Create New Template button opens the Template Properties dialog box.

The Left Pane

The left pane shows the monitoring groups containing the defined Resources, the QoS definitions, monitoring Templates, and Messages. Initially the Default Group, the standard QoS definitions, default Templates, and default Messages appear in the pane.

■ Agent

Agents are Profiles that can discover NetApp systems. You can define one or more profile and the probe will display NetApp systems discovered underneath the Profile.

This symbol means the connection to the Profile is OK

This symbol means the Profile is not available.

This symbol means the probe is trying to connect to the Profile; and the status is currently undetermined.

There are subordinate hierarchies under the NetApp system node:

■ Auto Configurations

One or more checkpoints (or templates) can be added to this node using drag and drop. This is the preferred method to improve GUI performance. Refer section Using Auto Configurations (see page 42) for further information.

■ Auto Monitors

This node lists Auto Monitors created for previously unmonitored devices based on the contents added to the Auto Configurations node.

Page 14: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Probe Configuration

14 netapp Guide

■ All Monitors

This node lists all monitors either defined by an auto configuration or manual creation.

■ Custom Monitors

This node allows you to create and edit custom monitors for special needs.

■ QoS

This hierarchy contains the standard QoS definitions included with the probe package. These can be selected when editing the monitoring properties for a monitor. To define your own QoS definitions, right-click the QoS node and select New QoS from the menu. You can also right-click in the right pane and click New.

■ Templates

Following is the list of some of the default templates:

■ NetApp Basic Monitors

■ NetApp Cluster Monitors

■ NetApp Power Environment Monitors

■ NetApp Disks Monitors

■ NetApp Spare Disks Monitors

■ NetApp Enclosure Monitors

■ NetApp IOPs Monitors

■ NetApp Network Interface Monitors

■ NetApp Aggregate Monitors

■ NetApp Volumes Monitors

■ NetApp LUNS Monitors

■ NetApp SnapMirror Monitors

The Right Pane

The right pane displays details about the item selected in the left pane generally as a table.

Probe Configuration

The netapp probe uses SNMP and ONTAPI to communicate with storage arrays. This section describes how to set up the probe to monitor the storage arrays.

Page 15: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Probe Configuration

Chapter 3: netapp Configuration 15

General Setup

Click the General Setup button on the toolbar ( ) to bring up the Setup dialog.

The fields in the above dialog are explained below:

Default alarm message string

Defines the default alarm message issued when alarm situations occur.

Default samples array

Defines the default value of the number of samples for a probe.

Global Interval

Specifies the time interval for profile scheduling. Global Interval will be overwritten with the profile specific time interval, if any.

Retries

Specifies the maximum number of permissible retries for the SNMP connection.

Max Thread

Defines the number of profiles to be executed simultaneously.

QoS Source

Defines the QoS Source for overriding.

Page 16: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Probe Configuration

16 netapp Guide

Log Size

Specifies the maximum size (in KB) for the log file after which a new log file will be created.

Get status timeout

Defines the time interval to retrieve the values of the variables. After the defined number of seconds, the probe will retrieve the value of the variables.

Log-level

Sets the level of details written to the log-file. Log as little as possible during normal operation to minimize disk consumption, improve performance, and increase the amount of detail when debugging.

MIB Setup Wizard

MIB Setup Wizard installs and manages the SNMP MIB files.

Follow these steps:

1. From the probe toolbar, click the Launch MIB Setup Wizard button.

The MIB Setup Wizard is launched.

Page 17: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Probe Configuration

Chapter 3: netapp Configuration 17

2. Click Next to proceed with the setup.

3. Click the button to add an MIB file. To remove the selected MIB file, click

the button

4. After adding/removing the MIB files, click Next to proceed.

Page 18: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Probe Configuration

18 netapp Guide

5. Select the Reload new MIB on Finish check box.

6. Click Finish.

The changes made to MIB directory are reflected in the probe.

Page 19: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Probe Configuration

Chapter 3: netapp Configuration 19

Create New Agent

You can start by creating an Agent that the probe can use to connect to the NetApp systems. This lets the probe collect and store data and information from the monitored components.

Follow these steps:

1. Register a resource using one of the following options:

■ Click the Create New Agent toolbar button ( ), or

■ Right-click the Agent, and select New Agent from the menu.

The Profile [New] dialog appears.

2. Enter the data as described in the following sections:

■ General Tab (see page 20)

■ SNMP Settings Tab (see page 21)

■ ONTAPI Settings Tab (see page 23)

3. Click OK to save the profile.

4. Click Apply and restart the probe.

Page 20: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Probe Configuration

20 netapp Guide

General Tab

The General tab allows you to add a new agent to the profile and define various parameters, such as the check interval, severity of alarm, group to which the agent belongs and identification parameters that the probe must use for monitoring.

The fields in the above tab are explained below:

Agent hostname or IP address

Defines the host name or IP address of the agent that the profile must monitor.

Active

Allows you to activate the profile that must monitor the selected SNMP Host.

Check interval

Specifies the time interval (in minutes) between each SNMP agent check.

Severity

Specifies the severity for messages sent if the agent host does not respond.

Group

Specifies the group where the SNMP host resides.

QoS identification method

Specifies the QoS identification method you want to assign to an alarm identification method. This value is set to Host Address by default.

Page 21: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Probe Configuration

Chapter 3: netapp Configuration 21

Alarm identification method

Specifies the Alarm identification method for the QoS identified in the QoS identification method field. This value is set to Host Address by default.

Default Template Settings

Allows you to apply the default monitoring templates to the new profile. For more information, refer section Apply Default Templates to the Profile (see page 39).

Test

Allows the probe to send a test SNMP query or an ONTAPI connection request to the destination agent.

SNMP Settings Tab

The SNMP Settings tab allows you to define and configure the SNMP software for the monitored device.

The monitored device and the probe use these settings to communicate with each other.

Note: These SNMP settings are enabled by default.

The fields in the above tab are explained below:

SNMP Version

Specifies the SNMP software version number supported by the monitored device.

Page 22: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Probe Configuration

22 netapp Guide

Authentication

Specifies the type of authentication strategy (none, HMAC-MD5-96, or HMAC-SHA-96). This field is only available for SNMP version 3.

Port

Defines the port number to be used by the SNMP device. Default is 161.

Timeout

Specifies the timeout value in seconds before a new SNMP Get request is sent to the SNMP agent. The default value is 1 second.

Retries

Specifies the number of attempts to be done before giving up and reporting it as a failure. An alarm is issued. Default value is 5 retries.

Community /password

Defines the password for the profile.

Username

Defines the username on the monitored device. This field is available only when the SNMP Version is SNMPv3.

Show password

Select this check box if you want the probe to display the password as plain text.

Security

Specifies the security level for the user. Valid levels are NoAuthNoPriv, AuthNoPriv, and AuthPriv. This field is available only when the SNMP Version is SNMPv3.

Priv. Protocol

Defines the privacy protocol for the SNMP. It is not required if the security level is NoAuthNoPriv or AuthNoPriv. This field is available only when the SNMP Version is SNMPv3.

Priv. Passphrase

Defines the privacy passphrase. It is not required if the security level is NoAuthNoPriv or AuthNoPriv. It must be at least eight characters long. This field is available only when the SNMP Version is SNMPv3.

Page 23: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Probe Configuration

Chapter 3: netapp Configuration 23

ONTAPI Settings Tab

The ONTAPI Settings tab allows you to enable the probe to display API-based checkpoints for the profile.

The fields in the above tab are explained below:

Enable

Allows you to enable the probe to use ONTAPI SDK to display API-based checkpoints.

Username

Defines the username that has administrative privileges on the monitored device for ONTAPI.

Password

Defines the password with administrative privileges on the monitored device for ONTAPI.

Transport Type

Specifies the connection type that the probe must use to communicate with the monitored device.

Page 24: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Probe Configuration

24 netapp Guide

Port

Defines the port number that the probe must use to communicate with the monitored device. The following ports are configured by default:

HTTP: 80

HTTPS: 443

Test

Allows the probe to send a test ONTAPI connection request to the destination agent.

Manage QoS Data and Alarms

You can display QoS definitions by clicking the QoS node in the left pane. When you select it, all QoS definitions are displayed in the table in the right pane.

You can add or edit QoS definitions as follows:

■ To edit an existing QoS definition, double-click on it either in the hierarchy on the left, or in the table on the right.

■ To define a new QoS definition, right-click the QoS node in the left pane and select New QoS from the menu.

Either way, this action launches the QoS Properties dialog, which contains the following fields:

QoS Name

Defines the name of the QoS definition.

Page 25: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Probe Configuration

Chapter 3: netapp Configuration 25

QoS Group

Defines the group the definition belongs to.

QoS Description

Provides descriptive text about the QoS definition

QoS Unit

Specifies the units of the measurement fully spelled out.

QoS Unit Abbreviation

Specifies the abbreviation for the units of the measurement.

Has maximum value

Defines the value that will not exceed the given maximum. This sets the maximum value on an axis when the value is graphed.

Add Monitors

There are three different ways to enable monitors to measure NETAPP elements:

■ Manually selecting the monitors

This is done by navigating through the hierarchy appearing under the agent node. When you select a folder in the hierarchy on the left, the monitors for it are listed on the right. Simply select the ones you want to monitor. Refer section Manually Selecting Monitors to be Measured (see page 26).

■ Using templates

Templates are also useful for defining monitors to be measured on multiple NetApp systems. Refer section Using Templates (see page 38) for further information.

■ Using Auto Configurations

Auto Configurations provide a powerful method for automatically adding monitors to be measured. Auto Monitors will be created when new devices come on line with no need for you to reconfigure the NetApp probe to monitor them.

When new disks are added to the NetApp system, the Auto Configuration feature, if configured, creates Auto Monitor(s) for the new disks and automatically starts monitoring them. Refer section Using Auto Configurations (see page 42) for further information.

Important! The recommended usage for monitoring is to create auto-monitors first. Only create static monitors for a specific instance if necessary. Creating multiple static monitors will increase the size of your .cfg file. Large .cfg files can cause performance issues with your probe.

Page 26: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Probe Configuration

26 netapp Guide

Manually Selecting Monitors to be Measured

To select a monitor to be measured for a resource, simply select the agent in the left pane and browse the hierarchy appearing under the agent node. Select a folder in this hierarchy to list the associated monitors on the right. Then select the ones you want to monitor.

Edit Monitor Properties for SNMP Monitor

You can double click the monitor to open the Monitor Properties dialog.

Page 27: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Probe Configuration

Chapter 3: netapp Configuration 27

This screen contains three sections:

■ Monitor Properties

■ Value Properties

■ Active

The Monitor Properties section contains the following fields:

Name

Defines the name of the monitor. The name will be inserted into this field when the monitor is created, but you are allowed to modify the name.

Type

Displays the type of checkpoint. This field is enabled while configuring custom monitors.

Object Identifier (OID)

Defines the variable name in the format of an Object Identifier.

Formula

Displays the formula used to calculate. This field is enabled while configuring custom monitors.

Description

Provides a description of the monitor. This description will be inserted into this field when the monitor is created, but you are allowed to modify it.

The Value Properties section contains the following fields:

Definition

Defines which value to compare to the threshold value:

■ Automatic (based on type)

The value is automatically set based on variable type (integer, counter etc.).

When Automatic is chosen, the probe – based on data type – either fetches the current value or makes a delta calculation.

For the following data types a delta calculation is performed: counter32 and counter64.

For all other data types, the current value is fetched.

■ The current value

Uses the current (last measured) value

Page 28: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Probe Configuration

28 netapp Guide

■ The delta value (current – previous)

Uses the delta value, which is the difference between the current and the previous measured value.

Note: The main window displays a 3-second delta computation.

Samples

Defines normalized value for a performance object to be monitored.

By default, the sampling process is not enabled. The samples box is also not available. To perform the sampling process, select the Calculate average based on check box. The samples box becomes available, which displays default samples set in the General Setup Properties dialog.

You can change the number of samples. Enter a value other than zero or one in the samples box to override the default sample value for any variable. This value has higher precedence than the default value of the number of samples set in the General Setup Properties dialog for a probe.

If you enter number of samples equal to one, then sampling process is not performed. As a result, average value of the variable samples is not calculated.

Similarly, if you enter number of samples equal to zero, then sampling is not calculated. Next time when you open the Variable dialog, it displays the default number of samples.

You cannot keep the samples box blank. The OK button becomes unavailable if you keep the number of samples blank.

Calculate value using ratio

Allows you to multiply the variable value with a number (ratio):

Example: A ratio of 0, 1 (value * 0, 1) means 10 % of the value. Enter the ratio value in the box.

Force the variable value as a numeric value type

Allows you to force the probe to treat a data type as a numeric value.

Example: The string:"2.5" will be treated as the numeric value 2.5 if this option is ticked.

The Active section activates the monitoring of the probe and contains the following fields:

Enable Monitoring

Provides the option to activate the monitoring.

Note: The monitor will also be selected in the list of monitors in the right window pane when this option is selected, and that you can enable/disable monitoring of the checkpoint from that list.

Page 29: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Probe Configuration

Chapter 3: netapp Configuration 29

Rule / Extend Rule tabs

These tabs are activated when the option Enable Monitoring is selected.

The fields on these tabs define the alarm and QoS conditions for the variable.

You have the option to use one or two levels of alarm triggering rules:

You define a set of alarm triggering rules on the Rule tab and alternatively also a set of additional alarm triggering rules on the Extended Rule tab.

See the EXAMPLE later in this table.

Important! Rule has to trigger before the Extended Rule is checked.

Note: The Extended Rule tab is disabled if selecting the operator = in the Rule tab.

Operator

Selects from the drop-down list the operator to be used when setting the alarm threshold for the measured value. Generally speaking, exact equalities are not useful for values that vary with time.

Example:

=> 90 means alarm condition if the measured value is 90 or above.

= 90 means alarm condition if the measured value is exactly 90.

Threshold

Defines the alarm threshold value. An alarm message will be sent if this threshold is exceeded.

Alarm severity level

Specifies the severity level of the alarms issued when the specified threshold value is breached. You may choose between five severity levels (from Information to Critical).

Message String

Selects the alarm message to be issued if the specified threshold value is breached. These messages are kept in the message pool. The messages can be modified as noted in the Managing Messages section.

Note: You can use variables message string to create a message that provides an operator with specific information about the condition. Using variables is simple. As you enter the Message String, at the point where you want to use a variable, enter a dollar-sign ($). A dialog pops up with the available variables.

Advanced tab Subsystem ID

Allows you to define a subsystem ID on the NAS, which is included in the alarm message.

Advanced tab Message String On Clear

Allows you to define your own message to be issued when an alarm is cleared. This message overrules the default message.

Page 30: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Probe Configuration

30 netapp Guide

Missing OID tab

Manages alarm settings for the missing OIDs.

Alarms on Missing OID

Allows you to raise an alarm when any OID is missing.

Severity Level

Defines the alarm severity level by selecting an option from the drop down menu.

Message from Missing OID (Error Message)

Defines the alarm message string to be displayed when an OID is missing.

Message from Missing OID (Clear Message)

Defines the alarm message string to clear the Missing Alarm message.

Publish Quality of Service

Provides option for QoS messages to be issued on the monitor.

QoS Name

Defines the name to be used on the QoS message issued if Publish Quality of Service is enabled.

Page 31: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Probe Configuration

Chapter 3: netapp Configuration 31

Edit Monitor Properties for API-Based Monitor

Double click the monitor to open the Monitor Properties dialog.

The following fields are enabled while editing an API-based monitor. For the other field descriptions, refer section Edit Monitor Properties for SNMP Monitor (see page 26).

Name

Indicates the name of the checkpoint.

Page 32: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Probe Configuration

32 netapp Guide

Type

Indicates the type of checkpoint. This field is enabled while configuring custom monitors. You can use the following options:

■ API: ONTAPI is used to fetch values for the checkpoint.

■ API + Lua: ONTAPI is used to fetch the value for the checkpoint and Lua function is used to perform calculation on the collected values.

■ API+ Formula: ONTAPI is used to fetch the value for the checkpoint and formula is applied to calculate a final value.

APIs Details

Displays details of the checkpoint, such as the API name and method used.

Lua Details Filename

Defines the name of the Lua script file that the probe must use for the final calculation based on the collected values.

Lua Details Function

Defines the name of the function that the probe must use for the final calculation based on the collected values from the Lua script.

Page 33: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Probe Configuration

Chapter 3: netapp Configuration 33

Create Custom Monitors

You can create and edit custom monitors for special needs.

Follow these steps to create a custom monitor:

1. In the tree view under an existing agent host, navigate to the Custom Monitor node.

2. Right-click the Custom Monitor node in the left pane and select the New Monitor option from the context menu.

The Monitor Properties dialog appears.

The fields in the above dialog are explained below:

Name

Defines the name of your new Custom Monitor.

Page 34: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Probe Configuration

34 netapp Guide

Type

Specifies the type of checkpoint you want to monitor from the drop-down list.

It has the following values:

■ Static: Target OID where Dynamic Indexing is NOT required. If using the OID form it must end in an actual index integer. Example: .1.3.6.1.4.1.789.1.2.1.3.0 for CPU utilization.

■ Static + Formula: Static checkpoint where a formula is required.

■ Dynamic: Target OID where Dynamic Indexing is required. The index will be discovered by the probe. Add a .X suffix to the OID to indicate a placeholder for the Dynamic Index that will need to be resolved. Example: .1.3.6.1.4.1.789.1.6.2.1.19.X for number of failed disks.

■ Dynamic + Formula: Dynamic checkpoint where a formula is required.

Object Identifier (OID)

Defines the OID variable name in the format of an Object Identifier. If you will be using a formula calculation, the order in which you add the new OIDs will determine the $n value to be used in your formula. Example: The first OID you add will be assigned $1 and the second will be assigned $2.

Formula

Provides the formula to calculate the checkpoint value produced. If you plan to use a formula, make sure that you selected and set the correct type (see the list under type).

Example: If you have specified 2 OID’s that you want to add together to deliver a sum for the checkpoint value, the formula would be $1+$2.

Similarly, you can use any mathematical formula to get the desired result. To see more examples of formulas, open an existing, pre-configured checkpoint to review the formula.

3. Select the green Plus sign (+) to add each OID variable needed for the checkpoint.

Page 35: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Probe Configuration

Chapter 3: netapp Configuration 35

4. Specify the Dynamic Index Tracking details if the OID you want to monitor has a variable index that needs to be discovered and resolved.

Note: These fields will be enabled only when you are creating a Custom Monitor in which Type selected is Dynamic or Dynamic + Formula.

Important! You must provide a valid value (case insensitive) for the instance of the target OID. You can find these values by looking at other dynamically discovered entities shown in the UI prefixed with the double arrow symbol (>>).

The fields in the above dialog are explained below:

SNMP Discovery Table

Indicates the SNMP MIB Table column used to look up the index.

SNMP Discovery Value

Indicates the SNMP MIB Table column used to look up the value for the index.

Value (case insensitive)

Defines the value of the variable containing the index.

Page 36: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Probe Configuration

36 netapp Guide

5. Click the Test button to check the validity of your OIDs and index lookup.

A successful Test will show a window with the resolved index.

Example of a pre-existing, auto discovered instance value that can be used to help you specify a correct value for dynamic OID index resolution:

You can also look for an OID index in a specified SNMP MIB Table and use the index of the entry that matches a specific leaf node OID as a static OID rather than specifying the dynamic index placeholder with a .X.

Page 37: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Probe Configuration

Chapter 3: netapp Configuration 37

If you have the required MIBs loaded, you may specify the "MIB Table" using the symbolic (textual) form. Alternatively, you can use the numerical form (e.g., .1.3.6.1.2.1.2.2.1.2 that translates to IF-MIB: ifDescr).

The following are valid symbolic forms for the OID .1.3.6.1.2.1.2.2.1.2:

■ IF-MIB::ifDescr

■ ifTable.ifEntry.ifDescr

■ ifDescr

The probe performs an snmpwalk of the specified table, and searches for the specified value. The comparison of values is case insensitive. The index found for the value match will be used as the index for the specified OID when doing the snmpget operation.

For Dynamic OIDs, the Index will be updated on each polling interval. First, the last known Index is tried. If there is no longer a match (i.e. value has changed), the probe does a snmpwalk of the specified SNMP MIB table and updates the Index with a new one (if the specified value can be found at another index).

The probe GUI has no restrictions on entering invalid values. Use the Test button to verify your values.

Note: Use the Missing OID Alarm in order to receive alarms, which indicate that the OID cannot be found (i.e. OID is missing).

You can run your custom monitors by leaving them in the Custom Monitor folder or you can add them to existing monitor groups by first adding them to a new Template and then applying the template to the target host.

Best Practice: Add a custom monitor to a new Template called Custom Template.

Important! Do NOT apply a custom monitor in a template to the Auto Configurations node. Apply the custom monitor to the root host node as a static monitor.

Page 38: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Probe Configuration

38 netapp Guide

Using Templates

Templates are useful tools for defining monitors to be measured on the various elements of a NetApp system:

You may create templates and define a set of monitors belonging to that template. These templates can be applied to a folder or element by dragging and dropping the template on the node in the tree where you want to measure the monitors defined for the template. You may also drop a template on a resource in the tree structure, and the template will be applied to all elements for the resource.

Important! Be careful when applying templates to the inventory tree, this will result in the inventory being recursively navigated to create static monitors for everything applicable to the template. Essentially the auto-monitor behavior in static form with the negative side effect of creating an overly large config file and resulting in performance problems with your probe.

Create a Template

You can create a new template using this functionality.

Follow these steps:

1. Right click the Templates node in the browser pane and select New Template from the menu.

The Template Properties dialog appears

2. Specify a Name and a Description for the new template.

Similarly, you can also edit an existing template. Select one of the templates defined under the Templates node in the browser (left-side) pane, right-click it, and select Edit from the menu.

Page 39: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Probe Configuration

Chapter 3: netapp Configuration 39

Apply Default Templates to the Profile

You can apply the default monitoring templates provided with the probe to the new profile:

Follow these steps:

1. Click the Default Templates Settings button.

The Default Templates Settings dialog opens containing a list of all the default templates.

2. Select the check box for the templates that you want the probe to apply to the new profile. Clear the check box for the templates that you want the probe to remove from the new profile.

Note:

■ A default template named NetApp Basic Monitors is selected by default. This monitor is applied even if you do not click the Default Templates Settings button while creating a new profile. Clear the check box to remove this default template from the profile.

■ The Apply to auto configuration check box allows the probe to add the selected default templates to the Auto Configuration node. This check box is selected by default. Clear this check box if you do not want to add the selected templates to the Auto Configuration node.

3. Click OK.

The selected default templates are added to the new profile.

Page 40: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Probe Configuration

40 netapp Guide

Add Monitors to the Template

To add a monitor (checkpoint) to a template, drag it from the right pane and drop it on the template in the left pane.

You can then edit the properties for the monitors in the template.

Page 41: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Probe Configuration

Chapter 3: netapp Configuration 41

Apply a Template to a NetApp System

Drag and drop the template onto the NetApp system in the Agent hierarchy. This assigns the monitors defined in template to the corresponding NetApp components.

You can drag and drop the template onto Auto Configurations node to apply relevant dynamic monitors in the template to be Auto Monitors. Refer section Using Auto Configurations (see page 42) for further information.

Page 42: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Probe Configuration

42 netapp Guide

Using Auto Configurations

Auto Configurations provide a powerful method for automatically adding monitors to be measured. This is the preferred method for configuring your resources. Auto Monitors will be created for devices that are currently NOT monitored.

Example: When new Disks are added to the NetApp system, the Auto Configuration feature will, if configured, create Auto Monitor(s) for the new Disks and automatically start monitoring them.

The Auto Configuration feature consists of two nodes located under the resource node in the left pane:

■ Auto Configurations

One or more checkpoints (or templates) can be added to this node, using drag and drop. When this is done, you must click the Apply button and restart the probe to activate the changes.

The probe will search for the appropriate types of objects. Auto Monitors, representing the monitor(s)/template(s) added under the Auto Configurations node will be created (and listed under the Auto Monitors node) for devices that are currently NOT monitored.

Note: Adding many monitors/templates to the Auto Configurations node may result in a very large number of Auto Monitors.

■ Auto Monitors

This node lists Auto Monitors created for previously unmonitored devices based on the contents added to the Auto Configurations node. The Auto Monitors will only be created for devices that are currently NOT monitored.

You can add or edit Auto Configurations as follows:

■ To edit an existing Auto Configuration, double-click it either in the hierarchy on the left or in the table on the right and select Edit from the menu.

■ To define a new Auto Configuration, right click the Auto Configurations node in the left pane, and select New Auto Configuration from the menu.

Either way, this action launches the Monitor Properties dialog. For details about this dialog, refer section Edit Monitor Properties (see page 26) section.

This dialog lets you define Auto Configurations for any type of object.

Page 43: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Chapter 4: QoS Threshold Metrics 43

Chapter 4: QoS Threshold Metrics

Many Nimsoft Monitor probes ship with default QoS threshold values set. The default threshold values provide an idea of the type of values to be entered in the fields and are not necessarily recommended best practice values. To aid in tuning thresholds and reducing false-positive alarms, this section describes the QoS metrics and provides the default QoS thresholds.

This section contains the following topics:

netapp QoS Metrics (see page 43) netapp Alert Metrics Default Settings (see page 47)

netapp QoS Metrics

The following table describes the QoS metrics that can be configured using the netapp probe.

Monitor Name Unit Description

QOS_STORAGE_ADMINISTRATION_STATUS_INTERFACE

Info QOS_STORAGE_Administration Status

QOS_STORAGE_BAY Info QOS_STORAGE_Bay

QOS_STORAGE_BAY_SPARE Info QOS_STORAGE_Bay

QOS_STORAGE_CACHE_AGE Minutes QOS_STORAGE_Cache Age

QOS_STORAGE_CIFS_AVERAGE_LATENCY ms QOS_STORAGE_CIFS AVERAGE LATENCY

QOS_STORAGE_CIFS_IOPS IO per sec QOS_STORAGE_CIFS IOPS

QOS_STORAGE_CPU_UTILIZATION Percent QOS_STORAGE_CPU utilization

QOS_STORAGE_DISK_ID Info QOS_STORAGE_Disk ID

QOS_STORAGE_DISK_ID_SPARE Info QOS_STORAGE_Disk ID

QOS_STORAGE_DISK_READ Kilobytes/second

QOS_STORAGE_Disk Read

QOS_STORAGE_DISK_SIZE MBytes QOS_STORAGE_Disk Size

QOS_STORAGE_DISK_SIZE_SPARE MBytes QOS_STORAGE_Disk Size

QOS_STORAGE_DISK_STATUS Info QOS_STORAGE_Disk Status

QOS_STORAGE_DISK_STATUS_SPARE Info QOS_STORAGE_Disk Status_Spare

Page 44: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

netapp QoS Metrics

44 netapp Guide

Monitor Name Unit Description

QOS_STORAGE_DISK_WRITE Kilobytes/second

QOS_STORAGE_Disk Write

QOS_STORAGE_ENABLED_CLUSTER Info QOS_STORAGE_Enabled

QOS_STORAGE_ENCLOSURE_CURRENT_TEMPERATURE

Celcius QOS_STORAGE_Current Temperature

QOS_STORAGE_FAILED_FAN Count QOS_STORAGE_Failed Fan

QOS_STORAGE_FAILED_POWER_SUPPLY_COUNT Count QOS_STORAGE_Failed Power Supply Count

QOS_STORAGE_FCP_AVERAGE_LATENCY ms QOS_STORAGE_FCP AVERAGE LATENCY

QOS_STORAGE_FCP_IOPS IO per sec QOS_STORAGE_FCP IOPS

QOS_STORAGE_INTERCONNECT_STATUS Info QOS_STORAGE_Interconnect Status

QOS_STORAGE_INTERFACE_IN_ERRORS Count QOS_STORAGE_Interface In Errors

QOS_STORAGE_INTERFACE_IN_OCTETS Octets Per Sec

QOS_STORAGE_Interface In Octets

QOS_STORAGE_INTERFACE_OUT_ERRORS Count QOS_STORAGE_Interface Out Errors

QOS_STORAGE_INTERFACE_OUT_OCTETS Octets per Sec

QOS_STORAGE_Interface Out Octets

QOS_STORAGE_IOPS IO per sec QOS_STORAGE_IOPS

QOS_STORAGE_ISCSI_AVERAGE_LATENCY ms QOS_STORAGE_iSCSI AVERAGE LATENCY

QOS_STORAGE_ISCSI_IOPS IO per sec QOS_STORAGE_iSCSI IOPS

QOS_STORAGE_LUN_ERROR_COUNT Count QOS_STORAGE_LUN Error Count

QOS_STORAGE_LUN_IOPS IO per sec QOS_STORAGE_LUN IOPS

QOS_STORAGE_LUN_ONLINE Info QOS_STORAGE_LUN Online

QOS_STORAGE_LUN_OTHER_IOPS Operations per sec

QOS_STORAGE_LUN Other IOPS

QOS_STORAGE_LUN_OTHER_LATENCY Latency sec QOS_STORAGE_LUN Other Latency

QOS_STORAGE_LUN_READ_BYTES Kilobytes/second

QOS_STORAGE_LUN Read Bytes

QOS_STORAGE_LUN_READ_IOPS IO Per Sec QOS_STORAGE_LUN Read IOPS

QOS_STORAGE_LUN_READ_LATENCY Sec QOS_STORAGE_LUN Read Latency

QOS_STORAGE_LUN_SIZE_MB MBytes QOS_STORAGE_LUN size

QOS_STORAGE_LUN_WRITE_BYTES Kilobytes/second

QOS_STORAGE_LUN Write Bytes

QOS_STORAGE_LUN_WRITE_IOPS IO Per Sec QOS_STORAGE_LUN Write IOPS

Page 45: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

netapp QoS Metrics

Chapter 4: QoS Threshold Metrics 45

Monitor Name Unit Description

QOS_STORAGE_LUN_WRITE_LATENCY Sec QOS_STORAGE_LUN Write Latency

QOS_STORAGE_MAXIMUM_NUMBER_OF_MODULES Count QOS_STORAGE_Maximum Number of Modules

QOS_STORAGE_NETWORK_RECEIVED Kilobytes/second

QOS_STORAGE_Network Received

QOS_STORAGE_NETWORK_SENT Kilobytes/second

QOS_STORAGE_Network Sent

QOS_STORAGE_NFS_AVERAGE_LATENCY ms QOS_STORAGE_NFS AVERAGE LATENCY

QOS_STORAGE_NFS_IOPS IO per sec QOS_STORAGE_NFS IOPS

QOS_STORAGE_NO_OF_AGGREGATES Count QOS_STORAGE_Number of Aggregates

QOS_STORAGE_NO_OF_ENCLOSURES Count QOS_STORAGE_No of Enclosures

QOS_STORAGE_NO_OF_ETHERNET_INTERFACES Count QOS_STORAGE_No of Ethernet Interfaces

QOS_STORAGE_NO_OF_VFILERS Count QOS_STORAGE_No of vFilers

QOS_STORAGE_NO_OF_VOLUMES Count QOS_STORAGE_No of Volumes

QOS_STORAGE_NUM_OF_CONFIGURED_DISKS Count QOS_STORAGE_Number of Configured Disks

QOS_STORAGE_NUM_OF_HOT_SPARES Count QOS_STORAGE_Number of Hot Spares

QOS_STORAGE_NUM_OF_UNCONFIGURED_DISKS Count QOS_STORAGE_Number of Unconfigured Disks

QOS_STORAGE_NUMBER_OF_DEVICES Count QOS_STORAGE_No of Devices

QOS_STORAGE_NUMBER_OF_DISK_BAYS Count QOS_STORAGE_Number of Disk Bays

QOS_STORAGE_NUMBER_OF_FAILED_DISKS Count QOS_STORAGE_Number of Failed Disks

QOS_STORAGE_NVRAM_BATTERY_STATUS Info QOS_STORAGE_NVRAM Battery Status

QOS_STORAGE_OPERATIONAL_STATUS_INTERFACE Info QOS_STORAGE_Operational Status

QOS_STORAGE_PARTNER_STATUS Info QOS_STORAGE_Partner Status

QOS_STORAGE_PARTNER_SYSTEM_ID Info QOS_STORAGE_Partner System ID

QOS_STORAGE_PERCENT_CAPACITY_FREE_AGGR Percent QOS_STORAGE_Percent Capacity Free

QOS_STORAGE_PERCENT_CAPACITY_USED_AGGR Percent QOS_STORAGE_Percent Capacity Used

QOS_STORAGE_PERCENT_CAPACITY_USED_VOL GBytes QOS_STORAGE_Percent Capacity Used

QOS_STORAGE_PERCENT_SNAPSHOT_FREE_AGGR Percent QOS_STORAGE_Percent Snapshot Free

QOS_STORAGE_PERCENT_SNAPSHOT_USED_AGGR Percent QOS_STORAGE_Percent Snapshot Used

QOS_STORAGE_PERCENT_SNAPSHOT_USED_VOL Percent QOS_STORAGE_Percent Snapshot Used

Page 46: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

netapp QoS Metrics

46 netapp Guide

Monitor Name Unit Description

QOS_STORAGE_POOL Info QOS_STORAGE_Pool

QOS_STORAGE_SHELF Info QOS_STORAGE_Shelf

QOS_STORAGE_SHELF_SPARE Info QOS_STORAGE_Shelf

QOS_STORAGE_SNAPMIRROR_ACTIVE State QOS_STORAGE_SnapMirror Active

QOS_STORAGE_SPEED_MBPS Megabits per sec

QOS_STORAGE_Speed

QOS_STORAGE_STATUS_AUTO_AUPPORT Info QOS_STORAGE_Status

QOS_STORAGE_STATUS_CLUSTER Info QOS_STORAGE_Status

QOS_STORAGE_STATUS_ENCLOSURE Info QOS_STORAGE_Status

QOS_STORAGE_SYSTEM_ID Number QOS_STORAGE_System ID

QOS_STORAGE_TAPE_READ Kilobytes/second

QOS_STORAGE_Tape Read

QOS_STORAGE_TAPE_WRITE Kilobytes/second

QOS_STORAGE_Tape Write

QOS_STORAGE_TOTAL_AVERAGE_LATENCY ms QOS_STORAGE_TOTAL AVERAGE LATENCY

QOS_STORAGE_TOTAL_CAPACITY_AGGR GBytes QOS_STORAGE_Total Capacity

QOS_STORAGE_TOTAL_CAPACITY_VOL GBytes QOS_STORAGE_Total Capacity

QOS_STORAGE_TOTAL_DESTINATION_FAILURES Count QOS_STORAGE_Total Destination Failures

QOS_STORAGE_TOTAL_DISK_COUNT Count QOS_STORAGE_Total Disk Count

QOS_STORAGE_TOTAL_SNAPSHOT_CAPACITY_AGGR GBytes QOS_STORAGE_Total Snapshot Capacity

QOS_STORAGE_TOTAL_SNAPSHOT_CAPACITY_VOL GBytes QOS_STORAGE_Total Snapshot Capacity

QOS_STORAGE_TOTAL_SOURCE_FAILURES Count QOS_STORAGE_Total Source Failures

QOS_STORAGE_VFILER_STATE Info QOS_STORAGE_vFiler State

QOS_STORAGE_VOLUME_STATUS Info QOS_STORAGE_Volume Status

QOS_STORAGE_VOLUME_STATE Info QOS_STORAGE_Volume State

QOS_STORAGE_LUN_SIZE_USED GBytes QOS_STORAGE_LUN size used

QOS_STORAGE_LUN_PERCENT_USED Percent QOS_STORAGE_LUN percent used

QOS_STORAGE_TOTAL_RAW_CAPACITY GBytes QOS_STORAGE_Total Raw Capacity

QOS_STORAGE_SNAPMIRROR_STATUS State QOS_STORAGE_SnapMirror Status

QOS_STORAGE_SNAPMIRROR_STATE State QOS_STORAGE_SnapMirror State

QOS_STORAGE_SNAPMIRROR_LAG Seconds QOS_STORAGE_SnapMirror Lag

Page 47: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

netapp Alert Metrics Default Settings

Chapter 4: QoS Threshold Metrics 47

netapp Alert Metrics Default Settings

The following table describes the default settings for the netapp alert metrics

Alert Metric Error Threshold Error Severity Description

Default metric - Information

Note: The user can change this as per requirement.

Alarms to be issued when the checkpoint value is below threshold

Page 48: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version
Page 49: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Chapter 5: Troubleshooting and FAQs 49

Chapter 5: Troubleshooting and FAQs

This section provides guidance to Nimsoft customer for the probes based on best practices with Nimsoft implementation of probes to monitor support devices and sample optimal characterization of running the probe.

This section contains the following topics:

Probe Performance Criteria (see page 49) Robot Environment for Running netapp (see page 50) Network Latency and Connectivity Considerations (see page 50) System Memory Considerations (see page 50) Disk Storage Considerations (see page 51) Number of Devices or Profiles per Probe (see page 51) Number of Metrics Collected per Device per Probe (see page 51) Number of QoSs and Alarms Configured per Device Per Probe (see page 51) Frequency of Metrics Collection per Device per Probe (see page 52)

Probe Performance Criteria

The guidance provided in this section can vary for specific customer environments based on various IT environment factors including but not limited to the following:

■ Available compute power of the machine (robot) that runs the probe

■ Available network bandwidth of the machine that runs the probe

■ Network connectivity and latency between the device or profile that is monitored by the probe and the machine that runs the probe

■ Network latency and connectivity with respect to the device element manager, such as SNMP agent or SMI-S manager

■ Available system memory on the machine that runs the probe

■ Available disk storage on the machine that runs the probe

■ Number of devices or profiles monitored by one instance of the probe

■ Number of metrics collected/expected per device per probe instance

■ Interval selected for collecting the metrics per device per probe instance

■ Number of QoSs and alarms selected/expected per device per probe instance

Page 50: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Robot Environment for Running netapp

50 netapp Guide

Robot Environment for Running netapp

Nimsoft probes are typically run on robots that connect to a hub which connects to the primary hub. For the netapp probe, the following best practice is suggested for selecting maching configuration for the robot that runs them:

■ Machine type - physical or virtual (VM)

■ HA Configuration - not required

■ Machine CPU Computer - 2 to 4 core 64-bit Pentium or equivalent with speed of 2.0 Ghz with 50% available on average

■ Machine system memory - 4 to 6 GB

■ Machine disk storage - 10 GB available

■ Machine Network bandwidth - standard LAN connectivity bandwidth, typically 1 Gbps. For better results, the robot machine should be in the same subnet as the devices monitored by the probes running on that robot.

■ Operating Systems - all robot supported OS

Network Latency and Connectivity Considerations

The netapp probe is dependent mainly on SNMP-based data collection.

The network latency of 30 ms or less between devices getting monitored and the robot machine running the probe collecting SNMP data is recommended for collecting 1000+ metrics per device/probe instance/robot.

Network latency plays a big role in getting the SNMP-based value for a metric at a given time but also affects the effective data calculation rates in the probe for the respective devices configured in each instance of the probe.

System Memory Considerations

The netapp probe uses system memory for internal processing and in a typical scenario this probe uses 16 MB of system memory.

Important! When setting up QoSs and alarms use AutoConfigurations rather than static monitors to ensure that the system memory consumed is optimal.

Page 51: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Disk Storage Considerations

Chapter 5: Troubleshooting and FAQs 51

Disk Storage Considerations

The netapp probe produces log files and data files that are used for diagnostic reasons and internal processing purposes respectively. The log file creates a copy of its last version before reaching the size limit as set by the probe. The probe also saves the entire granular settings for each metric it collects information for, in the configuration file. The best practice for setting up monitoring configurations is to use AutoConfiguration monitors instead of static monitors.

The netapp probe requires 10 MB of disk space and twice the log file space (typically in Kbytes). Configuration file space depends on the monitoring configuration setup. It can be as high as 100 MB if thousands of metrics are monitored.

Number of Devices or Profiles per Probe

The number of devices or profiles monitored by one instance of the probe affects the performance of the probe. Netapp has about 400 different types of monitoring data that can be collected, of which 200 are typically used for QoS metrics and 50 for threshold setting for alarm. Depending on the size of the netapp system, certain types of metrics can multiply to reach 6000+ metrics collected. For optimal Nimsoft netapp probe implementation, the best practices based on typical usage are:

■ Typical usage = 100 volumes and optimal devices per probe is 4.

■ Low end usage < 80 volumes and optimal devices per probe is 6.

■ High end usage > 200 volumes and optimal devices per probe is 2

Number of Metrics Collected per Device per Probe

The Nimsoft netapp probe is mainly based on SNMPgets. There are 400 types of metrics collected by the netapp probe and in a typical mid-sized system the total number of metrics per device is 19000.

Number of QoSs and Alarms Configured per Device Per Probe

QoSs can be selected only for the metrics that produce numerical values. Alarms are generally used for10% of the metrics collected. The total number of alarms collected in a mid-sized system per device is 2000 and the total number of QoS collected in a mid-sized system per device is 12000.

Page 52: Nimsoft Monitor netapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/netapp/1.2/netapp … · netapp Overview 8 netapp Guide Documentation Changes This table describes the version

Frequency of Metrics Collection per Device per Probe

52 netapp Guide

Frequency of Metrics Collection per Device per Probe

The netapp probe provides user-configurable interval settings for collecting the metrics per device per probe instance. There are also global interval settings per probe instance.

Global Metrics Collection Settings

Global Interval

The time interval per device for scheduling metrics collection for the device. Global interval will be overwritten with the device profile specific time interval, if any.

The default global interval is effective only when the time it takes to complete one pass of the metrics collection for a device is less than the settings. Otherwise, the global interval automatically becomes equal to the time for each pass of data collection per device.

Retries

The maximum number of permissible retries for the SNMP connection. The default setting is appropriate for most systems. You can increase the number of retries if necessary for high latency network environments.

Max Thread

The number of profiles to be executed simultaneously. It is important to have the number of threads more than the number of active device profiles per probe instance. Increasing the number of threads increases the CPU utilization of the robot machine.

Metrics Collection Settings

Check Interval

The time interval (in minutes) between each SNMP agent check. The default time of 5 minutes is optimal for most systems.

Timeout

The timeout value in seconds before a new SNMPget request is sent to the SNMP agent. In a high network latency environment, the optimal value would be 1 to 5 seconds.

Retries

The number of attempts performed before reporting a failure and sending an alarm. The default value is 5 retry attempts. In a high network latency environment, the optimal value for the retry count is 3 to 5.