Nimsoft Monitor. netapp Guide. v1.1 series

Transcription

1 Nimsoft Monitor netapp Guide v1.1 series

2 Legal Notices Copyright 2012, Nimsoft Corporation 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 Corporation 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 Corporation 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 Corporation 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 Corporation 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 (June 1995), or as a "commercial item" as defined in FAR 2.101(a) or as "Restricted computer software" as defined in FAR (June 1987) or any equivalent agency regulation or contract clause. Use, duplication or disclosure of Software is subject to Nimsoft Corporation 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 (c)(1-2) (June 1987). U.S. Government users will receive no greater than Limited Rights as defined in FAR (June 1987) or DFAR (b)(2) (November 1995), as applicable in any technical data. Trademarks 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.

3 Contact Nimsoft For your convenience, Nimsoft provides a single site where you can access information about Nimsoft products. At 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 support@nimsoft.com.

4

5 Contents Chapter 1: netapp Prerequisites and Supported Platforms... 8 Requirements... 8 Installation Notes... 8 Overview... 9 Monitoring Capabilities... 9 netapp Probe Configuration netapp GUI netapp Configuration Working with Monitors Manually Selecting Monitors to be Measured Using Templates Using Auto Configurations Contents 5

6

7 Chapter 1: netapp 1.1 This description applies to NetApp probe version 1.1. This section contains the following topics: Documentation Changes (see page 8) Prerequisites and Supported Platforms (see page 8) Overview (see page 9) netapp Probe Configuration (see page 10) Working with Monitors (see page 25) Chapter 1: netapp 1.1 7

8 Prerequisites and Supported Platforms Documentation Changes This table describes the version history for this document. Version Date What's New? 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 Getting Started with Nimsoft Probes Nimsoft Probes Reference Prerequisites and Supported Platforms Requirements Software: Platform: NetApp 7.2x and higher versions Windows NT/XP/2003/Vista (32/64 bit), Solaris 8,9,10 (sparc), Linux (32/64 bit) Installation Notes Install the package into your local archive Drop the package from your local archive onto the targeted robot(s) Double-click the probe for initial configuration 8 netapp Guide

9 Overview Overview The NetApp filer also know 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 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. The probe runs specific SNMP queries and extracts the important information from the devices. You can define alarms to be raised and propagated when specified thresholds are breached. Monitoring Capabilities 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 Chapter 1: netapp 1.1 9

10 netapp Probe Configuration netapp Probe Configuration 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 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. See the section netapp GUI for a description of the interface and the different terms, elements, tool buttons and window panes involved. Note: You must click the Apply button to activate any configuration modifications. Note: You must click the Apply button to activate any configuration modifications. netapp 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. 10 netapp Guide

11 netapp Probe Configuration 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. Chapter 1: netapp

12 netapp Probe Configuration 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: The Auto Configurations hierarchy One or more checkpoints (or templates) can be added to this node, using drag and drop. See the section Using Auto Configuration for further information. The Auto Monitors hierarchy This node lists Auto Monitors, created for previously unmonitored devices, based on the contents added to the Auto Configuration node. The All Monitors hierarchy This node lists All Monitors, either defined by an auto configuration or manual creation. 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 choose New 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 Disk Monitors NetApp Spare Disks Monitors NetApp Enclosure Monitors 12 netapp Guide

13 netapp Probe Configuration NetApp IOPs Monitors NetApp Network Interface Monitors NetApp Aggreaget 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. netapp Configuration Enter Probe Settings The netapp probe uses SNMP to communicate with storage arrays. This section describes how to set up the probe to monitor the storage arrays. Click the General Setup button on the toolbar ( ) to bring up the Setup dialog. Chapter 1: netapp

14 netapp Probe Configuration The following fields are available in the Setup dialog: Default alarm message string This is the default alarm message issued when alarm situations occur. Default Sample Array This field defines the default value of the number of samples for a probe. Global Interval Retries Enter the time interval for profile scheduling. Global Interval will be overwritten with the profile specific time interval, if any. Specify the maximum number of permissible retries for the SNMP connection. Max Thread Enter the number of profiles to be executed simultaneously. QoS Source Log Size Enter the QoS Source for overriding. Enter the maximum size (in KB) for the log file after which a new log file will be created. Get Status Timeout Enter 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 until the Get the current SNMP variable values button on the menu is clicked. Log-level Sets the level of details written to the log-file. Log as little as possible during normal operation to minimize disk consumption, and increase the amount of detail when debugging. 14 netapp Guide

15 netapp Probe Configuration MIB Setup Wizard MIB Setup Wizard enables you to install and manage the SNMP MIB files. 1. From the probe toolbar, click Launch MIB Setup Wizard button. The MIB Setup Wizard is launched. Chapter 1: netapp

16 netapp Probe Configuration 2. Click Next to proceed with the setup. 16 netapp Guide

17 netapp Probe Configuration 3. Click the button to add an MIB file. Click button to remove the selected MIB file. 4. After adding/removing the MIB files, click Next to proceed. 5. Select the Reload new MIB on Finish checkbox. 6. On clicking Finish, the changes made to MIB directory are reflected in the probe. Chapter 1: netapp

18 netapp Probe Configuration Adding Agents General Profile Tab 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. There are two ways you can register a resource: Click the toolbar button for New Agent ( ), or Right click the Agent, and choose New Agent from the menu. The Profile [New] dialog appears with the following tabs: General SNMP Settings ONTAPI Settings 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. 18 netapp Guide

19 netapp Probe Configuration Enter the information in the following fields: Agent hostname or IP address Active Enter the host name or IP address of the agent that the profile must monitor. Select this checkbox to activate the profile that must monitor the selected SNMP Host. Check Interval Severity Group Specify the time interval (in minutes) between each SNMP agent check. Select the severity for messages sent if the agent host does not respond. Select the group where the SNMP host resides. QoS Identification Method Select the QoS identification method you want to assign an alarm identification method to. This value is set to Host Address by default. Alarm Identification Method Select 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 Click this button if you want the probe to apply the default monitoring templates to the new profile. For more information see Applying Default Templates to the Profile section. Click this button to allow the probe to send a test SNMP query and an ONTAPI connection request to the destination agent. Chapter 1: netapp

20 netapp Probe Configuration SNMP Settings Tab The SNMP tab allows you to define and configure the SNMP software for the monitored device. 20 netapp Guide

21 netapp Probe Configuration The monitored device and the probe uses these settings to communicate with each other. Enter the information in the following fields: Note: These SNMP settings are enabled by default. SNMP version Click the SNMP software version number supported by the monitored device. Authentication Port Click the type of authentication strategy (none, HMAC-MD5-96 or HMAC-SHA-96). This field is only available for SNMP version 3. Timeout Retries Enter the port number to be used by the SNMP device. Default is 161. Click the timeout value in seconds before a new SNMP Get request is sent to the SNMP agent. The default value is 1 second. Click 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 Enter the password for the profile. Username Here you can specify a username defined 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. Define 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 It is 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 It is 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 1: netapp

22 netapp Probe Configuration ONTAPI Settings Tab The ONTAPI tab allows you to enable the probe to display API-based checkpoints for the profile. 22 netapp Guide

23 netapp Probe Configuration Enter the following information in the following fields: Enable Select this checkbox if you want the probe to use ONTAPI SDK to display API-based checkpoints. Username Enter the username that has administrative privileges on the monitored device for ONTAPI. Password Enter the password with administrative privileges on the monitored device for ONTAPI. Transport Type Port Click the connection type that the probe must use to communicate with the monitored device. Enter 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 When finished, click the Test button. Click OK to save the Profile. Click the Apply button, and restart the probe. Chapter 1: netapp

24 netapp Probe Configuration Managing QoS Data and Alarms You can display QoS definitions by clicking on the QoS node in the left pane. When you select it, all QoS definitions are displayed in the table in 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 choose New QoS from the menu. 24 netapp Guide

25 Working with Monitors Either way, this action launches the QoS Definition dialog, which contains the following fields: Name Group The name of the QoS definition. The group the definition belongs to. Description Unit Descriptive text about the QoS definition The units of the measurement fully spelled out. Unit Abbreviation A useful abbreviation for the units of the measurement. Has Maximum Value The value will not exceed the given maximum. This sets the maximum value on an axis when the value is graphed. Working with Monitors There are three different ways to enable monitors to be measured NETAPP elements: Manually selecting the monitors This is done by navigating through the hierarchy appearing under 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. See also the section Manually Selecting Monitors to be Measured. Using templates Templates are a useful for defining monitors to be measured on multiple NetApp systems. See the section Using Templates 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. Example: 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. See the section Using Auto Configuration for further information. Chapter 1: netapp

26 Working with Monitors 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. To Edit Monitor Properties for SNMP Monitor You can double click the on monitor to open the Monitor Properties dialog. 26 netapp Guide

27 Working with Monitors This screen contains three sections: Monitor properties Value Properties Active The Monitor properties section contains the following fields: Name Type This is 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 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 This is 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 Defining 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 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. Chapter 1: netapp

28 Working with Monitors Samples Sampling 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. For example, in the following image, it is six. 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 Select this check box to multiply the variable value with a number (ratio): E.g. 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 Select this option to force the probe to treat a data type as a numeric value. E.g. 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 Selecting this option activates the monitoring. Note that 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. Rule / Extend Rule tabs These tabs are activated when the option Enable Monitoring is selected (see above). 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: 28 netapp Guide

29 Working with Monitors 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 also that the Extended Rule tab is disabled if selecting the operator = in the Rule tab. Operator Select 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 above 90. = 90 means alarm condition if the measured value is exactly 90. Threshold The alarm threshold value. An alarm message will be sent if this threshold is exceeded. Alarm severity level 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 Select 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 that 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 type in 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. Missing OID tab The Missing OID tab manages alarm settings for the missing OIDs. Chapter 1: netapp

30 Working with Monitors Alarms on Missing OID Select this checkbox to raise an alarm when any OID is missing. Severity Level Define the alarm severity level by selecting an option from the drop down menu. Message from Missing OID (Error Message) Enter the alarm message string to be displayed when an OID is missing. Message from Missing OID (Clear Message) Enter the alarm message string to clear the Missing Alarm message. Publish Quality of Service Select this option if you want QoS messages to be issued on the monitor. QoS Name If Publish Quality of Service is enabled, you must select the name to be used on the QoS message issued. 30 netapp Guide

31 Working with Monitors To Edit Monitor Properties for API-Based Monitor Double click the monitor to open the Monitor Properties dialog. Chapter 1: netapp

32 Working with Monitors The following fields are enabled while editing an API-based monitor. For the other field descriptions, see To Edit Monitor Properties for SNMP Monitor. Name Type Displays the name of the checkpoint Displays 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 Enter the name of the Lua script file that the probe must use for the final calculation based on the collected values. Lua Details Function Enter the name of the function that the probe must use for the final calculation based on the collected values from the Lua script. 32 netapp Guide

33 Working with Monitors Creating custom monitors You can only create and edit custom monitors. Perform the following steps to create a custom monitor. 1. In the tree view, navigate to the Custom Monitor. 2. Right-click in the right-hand pane and select New Monitor option from the context menu. Chapter 1: netapp

34 Working with Monitors Following fields are enabled while creating Custom Monitors. For rest of the fields, please refer To Edit Monitor Properties Section. Type Enter the Type of Checkpoint you want to monitor. Type has following values: Static: Target OID where no Dynamic Indexing is required Example: System Time Up Static + Formula: Static checkpoint where formula is involved Dynamic: Target OID where Dynamic Indexing is required Example: Disk Usage Dynamic + Formula: Dynamic checkpoint where formula is involved Object Identifier (OID) Formula The Variable name in the format of an Object Identifier Provide the formula to get the OID values in desired format. For Example: If you have 2 OID s having No 1 and 2 and if you require the sum of its values then you can simply specify $1+$2. Similarly, you can use any mathematical formulas to get the desired result. 34 netapp Guide

35 Working with Monitors Specify the Dynamic Index Tracking details if the OID you want to monitor changes index. Note: These fields will be enabled only when you are creating Custom Monitor in which Type selected is Dynamic or Dynamic + Formula You should look for a value in a specified SNMP MIB Table and use the index of the entry that matches a specific value. 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 will do a snmpwalk of the specified table, and search 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. The Index will be updated on each poll interval. First, the last known Index is tried. If there is no match anymore (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). You can use the "Test" button to check the current Index and to confirm whether you have specified a valid MIB Table and/or value to search. The probe GUI has no restrictions on entering invalid 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). 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. Chapter 1: netapp

36 Working with Monitors To Create a Template You can create a Template in following manner: Right click the Templates node in the browser pane, and choose New Template from the menu. In the resulting Template Properties dialog, specify a Name and a Description for the new template. Note that 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. 36 netapp Guide

37 Working with Monitors Applying Default Templates to the Profile If you want the probe to apply the default monitoring templates provided with the probe to the new profile: 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 checkbox to remove this default template from the profile. The Apply to auto configuration checkbox 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 1: netapp

38 Working with Monitors To 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, as described in the To Edit Monitor Properties section. 38 netapp Guide

39 Working with Monitors To 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 configuration node to apply relevant dynamic monitors in the template to be Automonitors. See the section Using Auto Configuration for further information. Chapter 1: netapp

40 Working with Monitors Using Auto Configurations Auto Configurations provide a powerful method for automatically adding monitors to be measured. 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 Configuration node will be created (and listed under the Auto Monitor node, see below) 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 (see below). Auto Monitors This node lists Auto Monitors created for previously unmonitored devices, based on the contents added to the Auto Configuration 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 choose Edit from the menu. To define a new Auto Configuration, right click the Auto Configuration node in the left pane, and choose New Auto Configuration from the menu. Either way, this action launches the Monitor Properties dialog. For details about this dialog, see the To Edit Monitor Properties section. This dialog lets you define auto configurations for any type of object. 40 netapp Guide