Nimsoft Monitor. netapp Guide. v1.3 series

Transcription

1 Nimsoft Monitor netapp Guide v1.3 series

2 Copyright Notice This online help system (the "System") is for your informational purposes only and is subject to change or withdrawal by CA at any time. This System may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This System is confidential and proprietary information of CA and protected by the copyright laws of the United States and international treaties. This System may not be disclosed by you or used for any purpose other than as may be permitted in a separate agreement between you and CA governing your use of the CA software to which the System relates (the CA Software ). Such agreement is not modified in any way by the terms of this notice. Notwithstanding the foregoing, if you are a licensed user of the CA Software you may make one copy of the System for internal use by you and your employees, provided that all CA copyright notices and legends are affixed to the reproduced copy. The right to make a copy of the System is limited to the period during which the license for the CA Software remains in full force and effect. Should the license terminate for any reason, it shall be your responsibility to certify in writing to CA that all copies and partial copies of the System have been destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS SYSTEM AS IS WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS SYSTEM, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE. The manufacturer of this System is CA. Provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections , , and (c)(1) - (2) and DFARS Section (b)(3), as applicable, or their successors. Copyright 2014 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies. Legal information on third-party and public domain software used in this product is documented in the Third-Party Licenses and Terms of Use (

3 Contact CA Contact CA Support For your convenience, CA Technologies provides one site where you can access the information that you need for your Home Office, Small Business, and Enterprise CA Technologies products. At you can access the following resources: Online and telephone contact information for technical assistance and customer services Information about user communities and forums Product and documentation downloads CA Support policies and guidelines Other helpful resources appropriate for your product Providing Feedback about Product Documentation Send comments or questions about CA Technologies product documentation to To provide feedback about general CA Technologies product documentation, complete our short customer survey which is available on the support website at

4

5 Contents Chapter 1: netapp netapp Overview... 7 Chapter 2: netapp Probe Deployment 9 Supported Platforms... 9 System Requirements... 9 Software Requirements... 9 Monitoring System Requirements Probe Deployment Information Installation Notes Chapter 3: netapp Configuration 11 Probe Defaults Probe Configuration Interface Installation for netapp Probe GUI Toolbar Buttons The Left Pane The Right Pane Probe Configuration General Setup MIB Setup Wizard Toggle from Default mode to c-mode Create New Agent Manage QoS Data and Alarms Add Monitors Chapter 4: QoS Threshold Metrics 45 netapp QoS Metrics netapp Alert Metrics Default Settings Chapter 5: Troubleshooting and FAQs 53 Probe Performance Criteria Robot Environment for Running netapp Network Latency and Connectivity Considerations Contents 5

6 System Memory Considerations Disk Storage Considerations Number of Devices or Profiles per Probe Number of Metrics Collected per Device per Probe Number of QoSs and Alarms Configured per Device Per Probe Frequency of Metrics Collection per Device per Probe Global Metrics Collection Settings Metrics Collection Settings netapp Guide

7 Chapter 1: netapp 1.3 This description applies to NetApp probe version 1.3. 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). You can configure the probe for NetApp Ontap 8.1 c-mode and 7-mode operating system. 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 Chapter 1: netapp 1.3 7

8 netapp Overview Documentation Changes This table describes the version history for this document. Version Date What's New? 1.3 February 2014 Updated description of the Dynamic type OID in the Create Custom Monitors section. 1.3 October 2013 Added the SNMP V3 Support topic. 1.3 January 2013 Added support for NetApp Ontap 8.1 Cluster-mode operating system 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. Added Probe Defaults for the probe. 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 Monitor Metrics Reference Information for CA Unified Infrastructure Management Probes ( 8 netapp Guide

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 Refer to the Compatibility Support Matrix for the latest information about supported platforms. See also the Support Matrix for Probes for more specific information about the probe. 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 or later Nimsoft Robot 5.23 or later Java Virtual Machine 1.6 or later (typically installed with NMS 5.0 and above) Chapter 2: netapp Probe Deployment 9

10 Monitoring System Requirements 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 three ways to distribute archive packages. You can distribute the package within the web-based Admin Console (for supported probes), from within Infrastructure Manager, or use the standalone 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 10 netapp Guide

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. You can configure the probe for NetApp Ontap 8.1 Cluster-mode and 7-mode operating system. The Cluster-mode operation enhances the NetApp s storage efficiency value by introducing scalability and nondisruptive operations. The Netapp probe contains two different DTA files for checkpoint monitoring. Netapp.dta Used for the OIDs that are supported in 7-mode. Netapp_cmode.dta Used for the OIDs that are supported in c-mode. You can toggle between the two DTA files and use them as per your requirement. Refer section Toggle from Default mode to c-mode (see page 19) for details on the process of switching over between the two DTA files. This section contains the following topics: Probe Defaults (see page 11) Probe Configuration Interface Installation for netapp (see page 11) Probe GUI (see page 12) Probe Configuration (see page 15) 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 for netapp The probe configuration interface is automatically downloaded and installed by the Infrastructure Manager when the probe is deployed on a robot. Chapter 3: netapp Configuration 11

12 Probe GUI 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 default templates of the 7-mode are displayed on the UI. You can view the default templates of c-mode by changing the DTA file in the Setup dialog. Note: You must click the Apply button to activate any configuration modifications. 12 netapp Guide

13 Probe GUI 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 44) 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. Chapter 3: netapp Configuration 13

14 Probe GUI QoS 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. 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 Default templates are displayed in the UI based on the selection of DTA File in the Setup dialog. Following is the list of some of the templates available for the default mode: 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 You can view the default templates of c-mode by changing the DTA file to C Mode in the Setup dialog. Following is the default template available for the c-mode: NetApp C-mode Basic Monitors The Right Pane The right pane displays details about the item selected in the left pane generally as a table. 14 netapp Guide

15 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. 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. Chapter 3: netapp Configuration 15

16 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 Log Size Defines the QoS Source for overriding. 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. DTA File Allows you to specify the required DTA file. You can toggle between the Default DTA file for the 7-mode and the C Mode DTA file for the c-mode. By default, the Default DTA file is selected. 16 netapp Guide

17 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. Chapter 3: netapp Configuration 17

18 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. 18 netapp Guide

19 5. Select the Reload new MIB on Finish check box. 6. Click Finish. The changes made to MIB directory are reflected in the probe. Toggle from Default mode to c-mode In the Setup dialog, DTA File drop-down is available that can be used to toggle between default (7-mode) and c-mode. The probe can work in any one mode at any specified point of time. By default, the probe is configured to work in 7-mode. Before you toggle from one mode to another, all the profiles created in that mode has to be deleted. Follow these steps to toggle from default mode to c-mode: 1. Delete all the existing agents of the default mode. 2. Select c mode from the DTA File combo box and click OK. 3. Create a new agent for the c mode. You will observe that the new agent has different tree structure than the earlier default mode agent. Chapter 3: netapp Configuration 19

20 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 21) SNMP Settings Tab (see page 22) ONTAPI Settings Tab (see page 24) 3. Click OK to save the profile. 4. Click Apply and restart the probe. 20 netapp Guide

21 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 Active Defines the host name or IP address of the agent that the profile must monitor. Allows you to activate the profile that must monitor the selected SNMP Host. Check interval Severity Group Specifies the time interval (in minutes) between each SNMP agent check. Specifies the severity for messages sent if the agent host does not respond. 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. Chapter 3: netapp Configuration 21

22 SNMP Settings Tab 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 Test 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 41). Allows the probe to send a test SNMP query or an ONTAPI connection request to the destination agent. 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. 22 netapp Guide

23 Authentication Port Specifies the type of authentication strategy (none, HMAC-MD5-96, or HMAC-SHA-96). This field is only available for SNMP version 3. Timeout Retries Defines the port number to be used by the SNMP device. Default is 161. Specifies the timeout value in seconds before a new SNMP Get request is sent to the SNMP agent. The default value is 1 second. 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 Security Select this check box if you want the probe to display the password as plain text. 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. Chapter 3: netapp Configuration 23

24 SNMP V3 Support ONTAPI Settings Tab The netapp probe is enabled to monitor hosts/agents based on the SNMP V3 protocol. Few guidelines that must be adhered to when monitoring the SNMP V3 hosts are given as follows: If the same probe instance is monitoring multiple SNMP V3 hosts/agent, the user must ensure that the EngineID of all the hosts/agents is unique. The absence of unique EngineID causes sporadic connection timeouts and failure alarms. The probe does not support creating multiple monitoring profiles for one V3 host/agent. Adding such duplicate profiles is disabled in the probe GUI at most of the places, except the Bulk Configure screen. Do not use the Raw Configure option or add directly in the configuration file for creating multiple profiles for the same V3 host/agent. Doing so, causes the probe for producing some unpredictable results. 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. 24 netapp Guide

25 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 Port Test Specifies the connection type that the probe must use to communicate with the monitored device. 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 Allows the probe to send a test ONTAPI connection request to the destination agent. Note: The metrics that are monitored for ONTAPI-based configuration are: LUN size used, LUN Percent, Total Raw Capacity, and LUN Total Latency. Chapter 3: netapp Configuration 25

26 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. 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. 26 netapp Guide

27 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 27). Using templates Templates are also useful for defining monitors to be measured on multiple NetApp systems. Refer section Using Templates (see page 40) 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 44) 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. 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. Chapter 3: netapp Configuration 27

28 Edit Monitor Properties for SNMP Monitor You can double click the monitor to open the Monitor Properties dialog. 28 netapp Guide

29 This screen contains three sections: Monitor Properties Value Properties Active The Monitor Properties section contains the following fields: Name Type 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. Displays the type of checkpoint. This field is enabled while configuring custom monitors. Object Identifier (OID) Formula Defines the variable name in the format of an Object Identifier. 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 Chapter 3: netapp Configuration 29

30 Samples 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. 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. 30 netapp Guide

31 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. Chapter 3: netapp Configuration 31

32 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. 32 netapp Guide

33 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 28). Name Indicates the name of the checkpoint. Chapter 3: netapp Configuration 33

34 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. 34 netapp Guide

35 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 Monitor Properties dialog contains the following fields: Name Defines the name of your new Custom Monitor. Chapter 3: netapp Configuration 35

36 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: for CPU utilization. Static + Formula: Static checkpoint where a formula is required. Dynamic: Target OID where Dynamic Indexing is required. The index is discovered by the probe. The probe automatically adds symbol X at the end of the OID. 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. 36 netapp Guide

37 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. Chapter 3: netapp Configuration 37

38 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. 38 netapp Guide

39 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., that translates to IF-MIB: ifdescr). The following are valid symbolic forms for the OID : 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. Chapter 3: netapp Configuration 39

40 Using Templates Templates are useful tools for defining monitors to be measured on the various elements of a NetApp system. There are two separate sets of default templates that is available based on the selection of the DTA file (Default or c-mode) in the Setup dialog. 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. 40 netapp Guide

41 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. Chapter 3: netapp Configuration 41

42 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. 42 netapp Guide

43 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 44) for further information. Chapter 3: netapp Configuration 43

44 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 28) section. This dialog lets you define Auto Configurations for any type of object. 44 netapp Guide

45 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 45) netapp Alert Metrics Default Settings (see page 51) 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_INTERFAC E Info Current state of an interface set by the administrator. Possible values for the administrative status of the interface are: Unknown: Unknown administrative status Up: Administratively up Shutdown: Administratively down Testing: Administrator is testing the interface QOS_STORAGE_BAY Info Number identifying the disk bay within the shelf where the disk is located. QOS_STORAGE_BAY_SPARE Info Number identifying the disk bay within the shelf where the spare disk is located. QOS_STORAGE_CACHE_AGE Minutes Age of the oldest read-only blocks in the buffer cache. If the system reads very large files, the cache age is very low. QOS_STORAGE_CIFS_AVERAGE_LATENCY ms Average latency for CIFS. QOS_STORAGE_CIFS_IOPS IO per sec Total number of server side CIFS calls since last reboot. Chapter 4: QoS Threshold Metrics 45

46 netapp QoS Metrics Monitor Name Unit Description QOS_STORAGE_CPU_UTILIZATION Percent Percent of CPU utilization since the last request of the system CPU busy time. QOS_STORAGE_DISK_ID Info Identifier for the referenced disk drive on the referenced SCSI adapter. QOS_STORAGE_DISK_ID_SPARE Info The disk identifier for the referenced spare disk drive. QOS_STORAGE_DISK_READ Kilobytes/se cond Number of kilobytes read from the disk since last reboot. QOS_STORAGE_DISK_SIZE MBytes Physical space available on the referenced disk drive. QOS_STORAGE_DISK_SIZE_SPARE MBytes Physical space available on the referenced spare disk drive. QOS_STORAGE_DISK_STATUS Info Status of the referenced disk drive. QOS_STORAGE_DISK_STATUS_SPARE Info Status of the referenced spare disk drive. QOS_STORAGE_DISK_WRITE Kilobytes/se cond Number of kilobytes written to the disk since last reboot. QOS_STORAGE_ENABLED_CLUSTER Info Clustered failover configuration setting. QOS_STORAGE_ENCLOSURE_CURRENT_TEMPERATUR E Celcius List of temperatures reported by all temperature sensors in the enclosure, including the ambient temperature. QOS_STORAGE_FAILED_FAN Count Number of chassis fans not operating within the recommended RPM range. QOS_STORAGE_FAILED_POWER_SUPPLY_COUNT Count Number of power supplies in degraded mode. QOS_STORAGE_FCP_AVERAGE_LATENCY ms Average latency for FCP. QOS_STORAGE_FCP_IOPS IO per sec Total number of FCP operations handled since last reboot. QOS_STORAGE_INTERCONNECT_STATUS Info Current status of the interconnected hardware. QOS_STORAGE_INTERFACE_IN_ERRORS Count Number of inbound packets that contain errors preventing them from delivered to a higher layer protocol. QOS_STORAGE_INTERFACE_IN_OCTETS Octets Per Sec Total number of octets received on the interface, including framing characters. QOS_STORAGE_INTERFACE_OUT_ERRORS Count Number of outbound packets that could not be transmitted because of errors. 46 netapp Guide

47 netapp QoS Metrics Monitor Name Unit Description QOS_STORAGE_INTERFACE_OUT_OCTETS Octets per Sec Total number of octets transmitted out of the interface, including framing characters. QOS_STORAGE_IOPS IO per sec Total number of Input/Output operations per second since the last reboot. QOS_STORAGE_ISCSI_AVERAGE_LATENCY ms Average latency for iscsi. QOS_STORAGE_ISCSI_IOPS IO per sec Total number of iscsi operations handled since last reboot. QOS_STORAGE_LUN_ERROR_COUNT Count Total number of errors seen on the LUN since last reset of the statistics. QOS_STORAGE_LUN_IOPS IO per sec Total number of target side SCSI operations for the LUN since last reset of the statistics. QOS_STORAGE_LUN_ONLINE Info Whether LUN is online. QOS_STORAGE_LUN_OTHER_IOPS Operations per sec Total number of target side SCSI operations that are not read or write for the LUN since last reset of the statistics. QOS_STORAGE_LUN_OTHER_LATENCY Latency sec Latency of the target side SCSI operations that are not read or write for the LUN since last reset of the statistics. QOS_STORAGE_LUN_READ_BYTES Kilobytes/se cond Total number of bytes read from the LUN since last rest of the statistics. QOS_STORAGE_LUN_READ_IOPS IO Per Sec Total number of target side SCSI read operations for the LUN since last reset of the statistics. QOS_STORAGE_LUN_READ_LATENCY Sec Latency based on total number of target side SCSI read operations for the LUN since last reset of the statistics. QOS_STORAGE_LUN_SIZE_MB MBytes Size of the LUN in megabytes. QOS_STORAGE_LUN_WRITE_BYTES Kilobytes/se cond Total number of bytes written to the LUN since last reset of the statistics. QOS_STORAGE_LUN_WRITE_IOPS IO Per Sec Total number of target side SCSI write operations for the LUN since last reset of the statistics. QOS_STORAGE_LUN_WRITE_LATENCY Sec Latency of target side SCSI write operations for the LUN since last reset of statistics. Chapter 4: QoS Threshold Metrics 47

48 netapp QoS Metrics Monitor Name Unit Description QOS_STORAGE_MAXIMUM_NUMBER_OF_MODULES Count Number of enclosure services electronics modules that are possible for the enclosure to detect and monitor. QOS_STORAGE_NETWORK_RECEIVED QOS_STORAGE_NETWORK_SENT Kilobytes/se cond Kilobytes/se cond Total number of kilobytes received on all network interfaces since last reboot. Total number of kilobytes sent on all network interfaces since last reboot. QOS_STORAGE_NFS_AVERAGE_LATENCY ms Average latency for NFS. QOS_STORAGE_NFS_IOPS IO per sec Total number of server side NFS calls since last reboot. QOS_STORAGE_NO_OF_AGGREGATES Count Number of aggregates in the system. QOS_STORAGE_NO_OF_ENCLOSURES Count Number of storage enclosures in the storage subsystem. QOS_STORAGE_NO_OF_ETHERNET_INTERFACES Count Number of network interfaces on the system. QOS_STORAGE_NO_OF_VFILERS Count Number of vfilers in the physical Filer. QOS_STORAGE_NO_OF_VOLUMES Count Number of volumes in the system. QOS_STORAGE_NUM_OF_CONFIGURED_DISKS Count Number of active disks, including parity disks. QOS_STORAGE_NUM_OF_HOT_SPARES Count Number of available spare disks. QOS_STORAGE_NUM_OF_UNCONFIGURED_DISKS Count Number of unconfigured disks. QOS_STORAGE_NUMBER_OF_DEVICES Count Number of LUNs in the Filer. QOS_STORAGE_NUMBER_OF_DISK_BAYS Count Number of disk bays in the enclosure. QOS_STORAGE_NUMBER_OF_FAILED_DISKS Count Number of current broken disks. QOS_STORAGE_NVRAM_BATTERY_STATUS Info Current status of the NVRAM battery. QOS_STORAGE_OPERATIONAL_STATUS_INTERFACE Info Current operational state of the interface. QOS_STORAGE_PARTNER_STATUS Info Last displayed status by the Clustered Failover partner. QOS_STORAGE_PARTNER_SYSTEM_ID Info System ID of the Clustered Failover partner. QOS_STORAGE_PERCENT_CAPACITY_FREE_AGGR Percent Percentage of disk space currently free on the referenced file system. QOS_STORAGE_PERCENT_CAPACITY_USED_AGGR Percent Percentage of disk space currently in use on the referenced file system. 48 netapp Guide