vcenter Operations Management Pack for NetApp Installation and Configuration Guide

Transcription

1 vcenter Operations Management Pack for NetApp Installation and Configuration Guide This document supports the version of each product listed and supports all subsequent versions until a new edition replaces the document. To check for more recent editions of this document, see

2 vcenter Operations Management Pack for NetApp Installation and Configuration Guide You can find the most up-to-date technical documentation on the Blue Medora support site at: The Blue Medora web site also provides the latest product updates. If you have comments about this documentation, submit your feedback to: Copyright 2014 Blue Medora LLC. All rights reserved. U.S. and international copyright and intellectual property laws protect this product. Blue Medora is a registered trademark or trademark of Blue Medora LLC in the United States and/or other jurisdictions. NetApp and the NetApp logo are trademarks or registered trademarks of NetApp, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies. Blue Medora LLC 3225 N Evergreen Dr. NE STE 103 Grand Rapids, MI

3 Table of Contents vcenter Operations Management Pack for NetApp Installation and Configuration Guide... 6 Intended Audience... 6 Updated Information Introduction to the NetApp Adapter... 9 Understanding NetApp Integration... 9 How the Adapter Collects Data Data that the Adapter Collects Installation and Configuration Requirements NetApp OnCommand Unified Manager Core (DFM) Server Compatibility Connection Requirements NetApp Adapter Instance Credential Requirements vcenter Adapter Requirement Understanding the NetApp Management Pack Dashboards NetApp Management Pack Licensing Information Mode Licensing CDOT (Clustered Data ONTAP) Licensing Licensing and monitoring a subset of the entire NetApp storage environment Mapping of DFM Events to vcenter Operations Manager Alerts Installing the NetApp Adapter Install the Adapter in a Standalone Installation Install the Adapter in a vapp Installation NetApp Adapter Folders and Files Install Dashboards in a Standalone Installation Licensing the Management Pack Installing the License NetApp Entity Status Tags Improved Dashboard Widget Filtering using Entity Status Resource Tags Configuring the NetApp Adapter Overview of Configuration Steps Set Up a Resource Group to Filter Resources Add a Credential Add an Adapter Instance Configure NetApp OnCommand Unified Manager Core (DFM) Server 5.x to Collect Metrics Manually Discover NetApp Resources Validate Data Collection Creating Relationships Between Datastores and NetApp LUNs or Volumes Using the Relationship Synchronization Feature Modifying Adapter Properties Troubleshooting the NetApp Adapter

4 vcenter Operations Management Pack for NetApp Installation and Configuration Guide Troubleshooting a NetApp Adapter Instance Viewing System Log Files NetApp Adapter Classes Resolving Common Problems Metrics Do Not Appear In the User Interface Adapter Instance Resource Status Is Red Capacity Data and Performance Data Collection Times Are Not Synchronized Data Collection Fails After Upgrading NetApp Metrics NetApp System Metrics Aggregate Performance Metrics Capacity Metrics CIFS Node Metrics CIFS Performance Metrics Disk Metrics Disk Performance Metrics FCP Lif Node Metrics FCP Performance Metrics IFNet Metrics iscsi Performance Metrics LUN Performance Metrics NetApp Object Counts Metrics NFSv3 Performance Metrics Priority Queue Metrics Processor Metrics Qtree Performance Metrics Resource Information Metrics System Performance Metrics Target Metrics Volume Node Metrics Volume Performance Metrics Volume Storage Virtual Machine Metrics NetApp vfiler Metrics Capacity Metrics Resource Information Metrics vfiler Performance Metrics NetApp Volume Metrics Capacity Metrics CIFS Performance Metrics NFS Performance Metrics Priority Queue Metrics Resource Information Metrics Volume Performance Metrics QoS Metrics NetApp LUN Metrics Capacity Metrics LUN Performance Metrics

5 Resource Information Metrics NetApp Aggregate Metrics Aggregate Performance Metrics Capacity Metrics Resource Information Metrics QoS Metrics NetApp Cluster Metrics Aggregate Performance Metrics Disk Performance Metrics LUN Performance Metrics Qtree Performance Metrics Resource Information Metrics System Performance Metrics Volume Performance Metrics Volume Storage Virtual Machine Metrics NetApp Storage Virtual Machine Metrics CIFS Storage Virtual Machine Metrics FCP Lif Storage Virtual Machine Metrics iscsi Logical Interface Performance Metrics NFSv3 Performance Metrics Resource Information Metrics Volume Performance Metrics Volume Storage Virtual Machine Metrics QoS Metrics Qtree Metrics Capacity Metrics Qtree Performance Metrics Resource Information Metrics Disk Metrics Disk Performance Metrics Resource Information Metrics

6 vcenter Operations Management Pack for NetApp Installation and Configuration Guide vcenter Operations Management Pack for NetApp Installation and Configuration Guide The vcenter Operations Management Pack for NetApp Installation and Configuration Guide describes how to install and configure the NetApp Management Pack for vcenter Operations Manager. Intended Audience This information is intended for anyone who needs to install and configure the Management Pack for NetApp. 6

7 Updated Information The vcenter Operations Management Pack for NetApp Installation and Configuration Guide is updated with each release of the product or when necessary. This table provides the update history of the vcenter Operations Management Pack for NetApp Installation and Configuration Guide. Revision Description REV-14 Various minor fixes. REV-13 Added QosSyncInterval and QosCollectionEnabled to netapp.properties section Added permissions requirements regarding QoS policy retrieval REV-12 Added new properties to netapp.properties section Added new configuration variables to Adding an Adapter Instance REV-11 Updated documentation for vcenter Operations Management Pack for NetApp version 4.0 release. Added out of the box dashboards. See Understanding the NetApp Management Pack Dashboards, on page 11. Added Entity Status Resource Tags. See NetApp Entity Status Tags, on page 18. Added NetApp Management Pack Licensing Information, on page 6. Discontinued support for DFM versions prior to 5.x. REV-10 Added Licensing the Management Pack, page 17. REV-09 Added support for NetApp OnCommand Unified Manager Core (DFM) Server 5.2. See NetApp OnCommand Unified Manager Core (DFM) Server Compatibility, on page 11. Added a note that you must have the Global Full Control role in order to create relationships between VMware Datastores and NetApp LUNs. See Creating Relationships Between Datastores and NetApp LUNs or Volumes, on page 28. Added descriptions for the metricmapping.xml and metricmapping_3_8.xml files. See NetApp Adapter Folders and Files, on page 17. Added a clarification regarding the use of the metricmapping.xml. See Modifying Adapter Properties, on page 28. REV-08 Added support for NetApp OnCommand Unified Manager Core (DFM) Server 5.1. See NetApp OnCommand Unified Manager Core (DFM) Server Compatibility, on page 10. Added support for relationships between VMFS datastores and NetApp LUNs. See Creating Relationships Between Datastores and NetApp LUNs or Volumes, on page 28. REV-07 Updated the library files listed in NetApp Adapter Folders and Files, on page 17 REV-06 Added information about specifying nested NetApp OnCommand Unified Manager Core (DFM) resource groups to Add an Adapter Instance, on page 23. Described how to manually discover NetApp resources and select a manual discovery mode. See Manually Discover NetApp Resources, on page 26. REV-05 Added a note about NFS datastore support to Creating Relationships Between Datastores and NetApp LUNs or Volumes, on page 28. REV-04 Added NetApp Adapter Folders and Files, on page 17. Added Using the Relationship Synchronization Feature, on page 28. 7

8 vcenter Operations Management Pack for NetApp Installation and Configuration Guide REV-03 Added Modifying Adapter Properties, on page 28. REV-02 Added installation steps to Install the Adapter in a Standalone Installation, on page 15 and Install the Adapter in a vapp Installation, on page 16. Added troubleshooting information in Resolving Common Problems, on page 34. REV-01 Added information about configuring the protocol and port to use to connect to the NetApp OnCommand Unified Manager Core (DFM) server to Add an Adapter Instance, on page 23. Added Set Up a Resource Group to Filter Resources, on page 21. REV-00 The NetApp Adapter Technical Note is now the NetApp Adapter Installation and Configuration Guide. The NetApp Adapter Technical Note was the initial release of this document. 8

9 1 Introduction to the NetApp Adapter The NetApp adapter is an embedded adapter for vcenter Operations Manager. The adapter retrieves data from NetApp OnCommand Unified Manager Core (DFM) Server. This chapter includes the following topics: Understanding NetApp Integration, on page 9 Installation and Configuration Requirements, on page 10 Understanding the NetApp Management Pack Dashboards, on page 11 NetApp Management Pack Licensing Information, on page 12 Understanding NetApp Integration The NetApp adapter enables the exchange of information between NetApp OnCommand Unified Manager Core (DFM) Server and vcenter Operations Manager. Figure 1-1. NetApp Integration Information Exchange 9

10 vcenter Operations Management Pack for NetApp Installation and Configuration Guide How the Adapter Collects Data During each data collection cycle, the NetApp adapter opens a connection to the NetApp OnCommand Unified Manager Core (DFM) server and runs a main collection query. The collection interval for the adapter instance resource determines how often the NetApp adapter collects data. The default collection interval is five minutes. For information about changing the collection interval, see the VMware vcenter Operations Manager custom user interface online help. The NetApp adapter supports auto-discovery and manual discovery of resources. When you enable auto-discovery for a NetApp adapter instance, the adapter creates resources in vcenter Operations Manager and collects data after the main collection query runs. If a new resource belongs to a resource kind that does not exist in vcenter Operations Manager, the adapter creates the resource kind. The adapter creates resource kinds according to the platform and server types in NetApp OnCommand Unified Manager Core (DFM) Server. Data that the Adapter Collects The NetApp adapter can collect performance data, relationship data, and events for NetApp storage objects. The NetApp adapter recognizes the following NetApp storage objects: System (host) vfiler Volume LUN Aggregate Cluster Storage Virtual Machine Disk Qtree When you add a NetApp adapter instance in vcenter Operations Manager, you can set an option to have the adapter instance configure the NetApp OnCommand Unified Manager Core (DFM) server to collect the metrics that vcenter Operations Manager needs for analysis. This option is only available for 7mode NetApp environments. If you do not set this option, you must use the NetApp Management Console to configure the NetApp OnCommand Unified Manager Core (DFM) server to collect metrics. Installation and Configuration Requirements Before you install and configure the NetApp adapter, you must make sure that your system meets certain installation and configuration requirements. NetApp OnCommand Unified Manager Core (DFM) Server Compatibility The NetApp adapter is compatible with NetApp OnCommand Unified Manager Core (DFM) Server 5.1.x and 5.2.x. 10

11 Connection Requirements The machine where you install the NetApp adapter must be able to access the OnCommand Unified Manager Core (DFM) server. By default, the NetApp adapter uses port 8088 to communicate with the OnCommand Unified Manager Core (DFM) server by using http. HTTPS with SSL is an option, with port NetApp Adapter Instance Credential Requirements When you create a credential for a NetApp adapter instance, you must provide an OnCommand Unified Manager Core (DFM) user name and password. The NetApp adapter uses this credential to connect to and collect metrics from the OnCommand Unified Manager Core (DFM) server. NOTE: At a minimum, the DFM user account configured for the NetApp adapter needs to have Global Read permissions. See below for additional requirements based on Auto Filer configuration. The OnCommand Unified Manager Core (DFM) server user account that you provide must have certain roles depending on how you set the Auto Filer Configuration option for the adapter instance. Table 1-1. OnCommand Unified Manager Core (DFM) Server User Account Requirements Auto Filer Configuration True (7mode only) False OnCommand Unified Manager Core (DFM) Server Role Global Read and Write Global Read NOTE: In order to collect QoS metrics and non-primary SVM IP Addresses, the DFM user account configured for the NetApp adapter also needs to have DFM.Core: Control permissions. vcenter Adapter Requirement You must install and configure the vcenter adapter before you install the NetApp adapter. See the vcenter Adapter Installation and Configuration Guide. NOTE: If you have a vcenter Operations Manager vapp installation, the vcenter adapter is installed by default. Understanding the NetApp Management Pack Dashboards Dashboards provide the user interface you use to monitor and troubleshoot NetApp data problems in vcenter Operations Manager. Table 1-2. Dashboards in the Management Pack for NetApp Dashboard Name NetApp Storage Topology Purpose Topology of your NetApp infrastructure. By selecting a NetApp resource within the Custom Relationship widget on the left, you can quickly view the key performance indicators and relationships for the selected resource. Note: Improved filtering of the VMware virtual machines and VMware datastores in the Custom Relationship widget is available. Please see Improved Dashboard Widget Filtering using Entity Status Resource Tags, on page

12 vcenter Operations Management Pack for NetApp Installation and Configuration Guide NetApp Datastores NetApp System Explorer VM on NetApp Troubleshooting NetApp System Overview NetApp Heatmaps Top-N NetApp Systems Top-N NetApp Volumes Top-N NetApp Storage Virtual Machines Top-N NetApp LUNS Top-N NetApp Disks Overview of all VMware datastores using NetApp storage. Note: Improved filtering of the VMware virtual machines and VMware datastores in the Custom Relationship widget is available. Please see Improved Dashboard Widget Filtering using Entity Status Resource Tags, on page 18 In depth view of the detailed metrics displayed for the selected NetApp Storage Systems. Note: Improved filtering of the VMware virtual machines and VMware datastores in the Custom Relationship widget is available. Please see Improved Dashboard Widget Filtering using Entity Status Resource Tags, on page 18 Quick overview of the health and capacity of each NetApp Storage System. Heatmaps focused on performance and capacity for NetApp Systems, Aggregates, Volumes, and Storage Virtual Machines. Key performance indicators for NetApp Systems displayed in a set of Top-N widgets. Key performance indicators for NetApp Volumes displayed in a set of Top-N widgets. Key performance indicators for NetApp Storage Virtual Machines displayed in a set of Top-N widgets. Key performance indicators for NetApp LUNS displayed in a set of Top-N widgets. Key performance indicators for NetApp Disks displayed in a set of Top-N widgets. NetApp Management Pack Licensing Information The licensing model is based on the NetApp Storage System. The NetApp Management Pack allows unlimited datastores, volumes, etc. for a given configuration because licensing is based on hardware. 7-Mode Licensing In a 7-Mode configuration, each controller in each monitored Storage System needs to be licensed. CDOT (Clustered Data ONTAP) Licensing With Clustered Data ONTAP, a single cluster can be made up of one or many Storage Systems that are nodes within that cluster. Each controller in the monitored Storage Systems needs to be licensed Licensing and monitoring a subset of the entire NetApp storage environment To monitor a subset of NetApp Storage Systems in an environment, create a group in OnCommand/DFM containing the Storage Servers that should be monitored. Then see Configuring the NetApp Adapter, on page 21 to configure the NetApp Management Pack to monitor that group of Storage Systems. The NetApp Management Pack will only require licenses for the monitored Storage Servers. Mapping of DFM Events to vcenter Operations Manager Alerts Overview of NetApp Event Statuses 12

13 NetApp Events are broken down into eight statuses. These are taken from DFM Documentation and are listed in increasing order of severity. unknown: An object has an unknown status when it transitions from one state to another. Ideally, an object will have this status briefly. For example, when an object has been added, but not yet discovered. normal: An object has normal status when it is working within the thresholds specified in DFM. information: The information events are normal occurrences on an object for which you can define alarms. unmanaged: An object is considered to be unmanaged when the login and password are not set for the storage system or agent. warning: An object has the warning status when an event related to the object occurred that an administrator should know about. The event will not cause service disruption. error: An object has error status when it does not cause any service disruption, but it may affect performance. critical: An object has critical status when it is still performing, but service disruption may occur if corrective action is not taken immediately. emergency: An object is in emergency status when it stops performing unexpectedly and could lose data. Overview of vcenter Operations Events and Alerts vcenter Operations Manager has concepts of anomalies, alarms, and alerts. Anomaly: Caused by a metric value breaching a (usually dynamic) threshold. Alarm: Triggered when an event occurs, such as a change in the monitored environment. Alert: Generated based on an anomaly, alarm, or combination thereof. Unlike anomalies and alarms, alerts are presented to the user in the Alerts section of vcenter Operations Manager. Thus, in order to generate a vcenter Operations Manager alert, the management pack is required to generate an event. Events come in different flavors and severities, some of which always generate alerts, and some which only generate alarms. Events can also have a criticality level in vcenter Operations Manager, which is independent of whether an alert is generated, and are used to determine alert criticalities. These levels are: none, info, warning, immediate, critical. In addition to providing filtering based on NetApp Event Statuses, the Blue Medora Management Pack for NetApp will change the event criticality of the events sent to vcenter Operations Manger, and explicitly generate alerts for events with high criticality. 13

14 vcenter Operations Management Pack for NetApp Installation and Configuration Guide Table 1-3. DFM Event Mapping to vcenter Operations Manager vcenter Operations Manager Criticality Levels None Info Warning Immediate Critical NetApp DFM Event Statuses Unknown Normal Information Unmanaged alarm alarm alarm alarm Warning alarm Error alarm, alert Critical Emergency alarm, alert alarm, alert 14

15 2 Installing the NetApp Adapter How you install the NetApp adapter depends on whether you have a vcenter Operations Manager standalone or vapp installation. This chapter includes the following topics: Install the Adapter in a Standalone Installation, on page 15 Install the Adapter in a vapp Installation, on page 16 NetApp Adapter Folders and Files, on page 17 Licensing the Management Pack, on page 18 NetApp Entity Status Tags, on page 18 Install the Adapter in a Standalone Installation If you have a standalone installation, you install the NetApp adapter by extracting the adapter installation files from a TGZ file and running an installation utility. Prerequisites Obtain the management pack installation file from Make a note of the build number in the TGZ file name. The build number appears after the adapter name, for example, adaptername-buildnumber.tgz. Read the release notes that are included with the TGZ file. Procedure 1 Open the TGZ file and extract the TAR file to a temporary folder on your vcenter Operations Manager server. 2 In the temporary folder, open the TAR file and extract and run the installer for your operating system platform. 3 Log in to the Custom user interface as an administrator. 4 Select Admin > Support. 5 On the Info tab, find the Adapters Info pane and click the Describe icon ( ). The Describe icon is located at the top right of the Adapters Info pane. 6 Click Yes to start the describe process and click OK. The custom user interface finds the adapter files, gathers information about the abilities of the adapter, and updates the user interface with information about the adapter. If you have remote collectors, it installs the adapter on the remote collectors. The describe process might take several minutes. When the describe process is finished, the adapter appears in the Adapters Info pane. The build number is in the Adapter Version column. 15

16 vcenter Operations Management Pack for NetApp Installation and Configuration Guide 7 Verify that the build number in the Adapter Version column for the adapter matches the build number in the TGZ file that you downloaded. The installation utility creates the netapp_adapter3 folder and netapp_adapter3.jar file under the vcenterops/user/plugins/inbound folder. Install the Adapter in a vapp Installation If you have a vapp installation, you install the NetApp adapter from a PAK file. Prerequisites Obtain the management pack installation file from Make a note of the build number in the PAK file name. The build number appears after the adapter name, for example, adaptername-buildnumber.pak. Read the release notes that are included with the PAK file. Procedure 1 Save the PAK file in a temporary folder. 2 Log in to the Admin user interface as the admin user. For example: 3 On the Update tab, click Browse to locate the temporary folder and select the PAK file. 4 Click Update and click OK to confirm the update. The Admin user interface uploads the PAK file. The upload might take several minutes. 5 Read and accept the EULA and click OK. 6 Click OK to confirm and start the update process. The update might take several minutes. Status information appears on the Update tab when the update is finished. 7 Log in to the Custom user interface as an administrator. For example: 8 Select Admin > Support. 9 On the Info tab, find the Adapters Info pane and click the Describe icon ( ). The Describe icon is located at the top right of the Adapters Info pane. 10 Click Yes to start the describe process and click OK. The Custom user interface finds the adapter files, gathers information about the abilities of the adapter, and updates the user interface with information about the adapter. The describe process might take several minutes. When the describe process is finished, the adapter appears in the Adapters Info pane. The build number is in the Adapter Version column. 11 Verify that the build number in the Adapter Version column for the adapter matches the build number in the PAK file that you uploaded. The installation utility creates the netapp_adapter3 folder and netapp_adapter3.jar file in the vcenterops/user/plugins/inbound folder. 16

17 NetApp Adapter Folders and Files The installer places the NetApp adapter files in the netapp_adapter3 folder under the vcenterops/user/plugins/inbound folder. The netapp_adapter3 folder Table 2-1. NetApp Adapter Folders and Files Folder File Description conf netapp.properties The properties in this file determine which events and metrics that the adapter instance collects. describe.xml Describes the adapter history.txt Contains the history of adapter changes lib version.txt license.properties open_source_license.txt OSS library files: dom4j jar Non-OSS library files: manageontap.jar license.properties Contains version information Template license file. Open source license file. JAR files that contain the classes and resources used to implement the adapter Contains the license key for the adapter. Install Dashboards in a Standalone Installation The NetApp management pack dashboards are deployed by default to a vapp. For a standalone installation, you can import the dashboards manually using a batch file or shell script. Prerequisites Install the Management Pack for NetApp Storage. See Installing the NetApp Adapter, on page 15. The VMware Management Pack is required for complete installation of all dashboards included in the management pack. See Understanding the NetApp Management Pack Dashboards, on page 11. Procedure 1. Navigate to %ALIVE_BASE/user/plugins/inbound/netapp_adapter3/conf/scripts. 2. Run the appropriate script file. OS Windows Linux Script File NetAppPostInstall.bat NetAppPostInstall.sh 17

18 vcenter Operations Management Pack for NetApp Installation and Configuration Guide Licensing the Management Pack The Management Pack requires a valid license for full operation. Installing the License 3. Navigate to %ALIVE_BASE/user/plugins/inbound/netapp_adapter3/conf/ 4. Create and/or open a file called license.properties in a text editor. NOTE In a vapp installation, modify the license.properties file on the Analytics virtual machine. 5. Add a licensekey property and set it to your provided license key string. For example: licensekey=1/sample/ /trial/ /limited/2DBE4EC0F314B6E3401E4A5AF38C5CF27390E Ensure that the license.properties is readable and writeable by user, is readable by group and other, and is owned by the user admin. To do this, run these commands: chmod 644 license.properties chown admin:admin license.properties 7. Restart any existing NetApp Adapter instances in the Custom UI. Navigate to Environment > Environment Overview. Expand Adapter Instances tag in the left hand tree view and select NetApp Adapter Instance. Select all adapter instances and click the Stop Collecting icon. Select all adapter instances and click the Start Collecting icon. NetApp Entity Status Tags The NetApp adapter creates Entity Status resource tags in the Custom user interface. NetApp 7 Mode Resources NetApp Cluster Mode Resources VMware Datastores hosted on NetApp Storage VMware VMs hosted on NetApp Storage These tag values represent groupings of NetApp and VMware resources to provided ease of troubleshooting and filtering on specific dashboards widgets. Improved Dashboard Widget Filtering using Entity Status Resource Tags vcenter Operations Manager Custom UI provided widgets that can further filter the resources displayed using Entity Status resource tags. NOTE: Entity Status resource tags for NetApp are not visible in the Custom UI until after at least one resource in a resource tag has been collected from a NetApp Storage System by the adapter. Dashboard - NetApp Storage Topology Open Dashboard Dashboards -> NetApp -> NetApp Storage Topology 18

19 Edit VMware on NetApp Select a Resource widget Apply Entity Status Tag for Virtual Machines Click on Select Tags for Virtual Machine within the Selected Resource Kinds section In the Select which tags to filter section, expand NetApp Entity Status Select VMware VMs hosted on NetApp Storage Apply Entity Status Tag for Datastores Click on Select Tags for Datastore within the Selected Resource Kinds section In the Select which tags to filter section, expand NetApp Entity Status Select VMware Datastores hosted on NetApp Storage Click OK Dashboard - NetApp Datastores Open Dashboard Dashboards -> NetApp -> NetApp Datastores Edit Select Datastore (on NetApp Storage) widget Apply Entity Status Tag In the Select which tags to filter section, expand NetApp Entity Status Select VMware Datastores hosted on NetApp Storage Click OK Dashboard - VM on NetApp Troubleshooting Open Dashboard Dashboards -> NetApp -> VM on NetApp Troubleshooting Edit Select VMware VM (Running off of NetApp Storage) widget Apply Entity Status Tag In the Select which tags to filter section, expand NetApp Entity Status Select VMware VMs hosted on NetApp Storage Click OK Edit NetApp Environment widget Apply Entity Status Tag for Virtual Machines Click on Select Tags for Virtual Machine within the Selected Resource Kinds section In the Select which tags to filter section, expand NetApp Entity Status Select VMware VMs hosted on NetApp Storage Apply Entity Status Tag for Datastores Click on Select Tags for Datastore within the Selected Resource Kinds section In the Select which tags to filter section, expand NetApp Entity Status Select VMware Datastores hosted on NetApp Storage Click OK 19

20 vcenter Operations Management Pack for NetApp Installation and Configuration Guide 20

21 3 Configuring the NetApp Adapter To configure the NetApp adapter, you must add a credential and an adapter instance in vcenter Operations Manager. Depending on your configuration, you might need to perform additional steps. This chapter includes the following topics: Overview of Configuration Steps, on page 21 Set Up a Resource Group to Filter Resources, on page 21 Add a Credential, on page 22 Add an Adapter Instance, on page 23 Configure NetApp OnCommand Unified Manager Core (DFM) Server 5.x to Collect Metrics, on page 25 Manually Discover NetApp Resources, on page 26 Validate Data Collection, on page 27 Creating Relationships Between Datastores and NetApp LUNs or Volumes, on page 28 Modifying Adapter Properties, on page 28 Overview of Configuration Steps Configuring the NetApp adapter involves several steps. 1 (Optional) Create a resource group to filter the resources that the NetApp adapter instance imports from the OnCommand Unified Manager Core (DFM) server. See Set Up a Resource Group to Filter Resources, on page Add an adapter instance and credential. See Add a Credential, on page 22 and Add an Adapter Instance, on page (Optional) If you set the Auto Filer Configuration option to false for the adapter instance, configure the OnCommand Unified Manager Core (DFM) server to collect metrics. See Configure NetApp OnCommand Unified Manager Core (DFM) Server 5.x to Collect Metrics, on page Validate the data that the adapter instance collects. See Validate Data Collection, on page (Optional) Modify adapter properties to customize adapter operation. See Modifying Adapter Properties, on page 28. Set Up a Resource Group to Filter Resources To filter the resources that a NetApp adapter instance imports from the OnCommand Unified Manager Core (DFM) server, create a resource group and specify the name of that resource group when you define the adapter instance. The adapter instance imports only the resources that belong to the resource group. 21

22 vcenter Operations Management Pack for NetApp Installation and Configuration Guide You can use only one resource group as a filter. The NetApp adapter does not support filtering resources based on multiple resource groups. Prerequisites You must have access to and be familiar with NetApp Operations Manager. Procedure 1 Log in to NetApp Operations Manager. NetApp Operations Manager typically runs on port Select Groups from the Setup drop-down menu. 3 Type a name for the new resource group in the text box and click Add. NetApp Operations Manager creates the resource group. 4 Click the link under Group Membership and select the NetApp objects to add to the new resource group. For a newly created resource group, the link is called Empty. What to do next Specify the resource group when you define the NetApp adapter instance. See Add an Adapter Instance, on page 19. Add a Credential The NetApp adapter uses a user name and password to connect to the OnCommand Unified Manager Core (DFM) server. You use this user name and password to create a credential for the adapter instance in vcenter Operations Manager. You can add the credential before you create the adapter instance and select the correct credential when you define the adapter instance, or you can add the credential when you define the adapter instance. Prerequisites Install the NetApp adapter. See chapter 2, Installing the NetApp Adapter, on page 15. Verify that the user account meets the credential requirements. See NetApp Adapter Instance Credential Requirements, on page 11. Procedure 1 Log in to the Custom user interface as an administrator. 2 Select Environment > Configuration > Credentials. 3 Select NetApp Adapter from the Adapter Kind drop-down menu. 4 Select a credential from the Credential kind drop-down menu. 5 At the top of the list of credentials, next to Action, click Add. 6 Type a unique name for the credential instance in the Instance name text box. 7 Type the user name and password combination in the User name and Password text boxes. 22

23 8 Click OK to add the credential for the adapter. The credential appears in the list in the Manage Credentials window. Add an Adapter Instance You must create an adapter instance for the NetApp adapter. The adapter instance defines the adapter type and identifies the OnCommand Unified Manager Core (DFM) server from which the adapter instance retrieves data. If your OnCommand Unified Manager Core (DFM) server does not use the default protocol and port, you can select a different protocol and port. You can also optionally specify an OnCommand Unified Manager Core (DFM) server resource group to filter the resources that the adapter instance imports. If your environment is configured to support multiple OnCommand Unified Manager Core (DFM) servers and the servers are monitored by vcenter Operations Manager, you must create an adapter instance for each OnCommand Unified Manager Core (DFM) server. Prerequisites Install the NetApp adapter. See chapter 2, Installing the NetApp Adapter, on page 15. Create a credential, or, if you plan to create a credential when you add the adapter instance, become familiar with creating credentials. See Add a Credential, on page 22. To filter the resources that the adapter instance imports from the OnCommand Unified Manager Core (DFM) server, create a resource group. See Set Up a Resource Group to Filter Resources, on page 21. Procedure 1 Log in to the Custom user interface as an administrator. 2 Select Environment > Configuration > Adapter Instances. 3 Select the collector to use from the Collector drop-down menu. Unless you added additional collectors, the only available collector is vcenter Operations Standard Server. You can change the name of this collector when you install the standalone version. 4 Select NetApp Adapter from the Adapter Kind drop-down menu. 5 Click the Add New Adapter Instance icon. 6 Type a name for the adapter in the Adapter Instance Name text box. 7 Type the host name or IP address of the OnCommand Unified Manager Core (DFM) server in the OnCommand Unified Manager Core (DFM) Server text box. 8 Select an Auto Discovery option. If you select True, the adapter instance creates NetApp resources for you. If you select False, you must manually discover NetApp resources. The default setting is True. 9 (Optional) To limit the resources that the adapter instance imports to the resources that belong to a particular OnCommand Unified Manager Core (DFM) server resource group, type the name of the resource group in the Resource Group For Discovery text box. Use a forward slash (/) to specify nested resource groups. For example, if the OnCommand Unified Manager Core (DFM) server resource group is Global > TestGroup1 > TestGroup2, type TestGroup1/TestGroup2 in the Resource Group For Discovery text box. 23

24 vcenter Operations Management Pack for NetApp Installation and Configuration Guide 10 Select an Auto Filer Configuration option. If you select True, the adapter instance configures the OnCommand Unified Manager Core (DFM) server to collect metrics that vcenter Operations Manager needs for analysis. If you select False, you must configure the OnCommand Unified Manager Core (DFM) server from the NetApp Management Console. The default setting is True. Auto Filer Configuration only works in 7mode. NOTE: Because the auto filer configuration acts directly on the OnCommand Unified Manager Core (DFM) settings, the option that you select affects all adapter instances for this OnCommand Unified Manager Core (DFM) server. 11 Select the protocol to use to connect to the OnCommand Unified Manager Core (DFM) server from the Protocol drop-down menu. Because the OnCommand Unified Manager Core (DFM) server runs on HTTP by default, the default selection is HTTP. If your OnCommand Unified Manager Core (DFM) server runs on HTTPS instead of HTTP, change the setting to HTTPS. 12 Type the OnCommand Unified Manager Core (DFM) port to use to connect to the OnCommand Unified Manager Core (DFM) server in the OnCommand Unified Manager Core (DFM) DFM Port text box. Because the OnCommand Unified Manager Core (DFM) server runs on port 8088 by default, the default setting is If your OnCommand Unified Manager Core (DFM) server runs on a different port, type that port number in the text box. 13 Select True for Collect Disks to create NetApp disk resources in vcenter Operations Manager and collect all disk related metrics. You will also need to uncomment the disk metrics you want in metricmapping.xml. WARNING: Enabling this feature in large NetApp environments could significantly impact the performance of your DFM and vcenter Operations Management environments. 14 Select the credential to use to sign on to the data source from the Credential drop-down menu, or click Add to add a new credential. 15 For each resource kind, you can choose Off, Metadata, or Metadata and Performance Data. A resource kind set to Off will not be discovered or collected. A resource kind set to Metadata will be discovered, but only a few metadata metrics will be collected for it. A resource kind set to Metadata and Performance Data will be discovered, and all of its performance metrics will be collected. 16 Click OK to save your configuration. What to do next If you set the Auto Filer Configuration option to false, configure the OnCommand Unified Manager Core (DFM) server to collect metrics. See Configure NetApp OnCommand Unified Manager Core (DFM) Server 5.x to Collect Metrics, on page 25. If you set the Auto Filer Configuration option to True, you might want to modify the events and metrics that the adapter instance collects. For more information, see Modifying Adapter Properties, on page 28. If you set the Auto Discovery option to False, manually discover NetApp resources. See Manually Discover NetApp Resources, on page

25 Configure NetApp OnCommand Unified Manager Core (DFM) Server 5.x to Collect Metrics If you set the Auto Filer Configuration option to false for a NetApp adapter instance, you must configure the OnCommand Unified Manager Core (DFM) server to collect the metrics that vcenter Operations Manager needs for analysis. Due to a NetApp restriction, Auto Filer Configuration is only possible in 7mode environments. Enabling Auto Filer Configuration in a clustered environment will have no effect. If you have NetApp OnCommand Unified Manager Core (DFM) Server 5.x you configure the OnCommand Unified Manager Core (DFM) server to collect metrics by enabling counters for the NetApp Filers. You must enable the counters for all of the NetApp Filers on the OnCommand Unified Manager Core (DFM) server. You can enable the counters for each NetApp Filer individually, or you can configure one NetApp Filer and apply its settings to the remaining NetApp Filers. NOTE: You must also perform these steps if a NetApp Filer is added to the OnCommand Unified Manager Core (DFM) server. If you do not configure the new NetApp Filer, vcenter Operations Manager adapter performs analysis based on only a partial list of counters. Procedure 1 Log in to NetApp Management Console as Administrator. 2 Type the OnCommand Unified Manager Core (DFM) server information. 3 Select Tasks > Manage Performance. 4 Click Setup. 5 Click Host and select the first host in the host list. 6 Select Data Collection > Edit. A configuration wizard appears and lists the disabled and enabled counters for the NetApp Filer. 7 Move counters from the Disabled Counters list to the Enabled Counters list to enable them. Group CIFS FCP ISCSI LUN NFSv3 PriorityQueue System vfiler Volume Description cifs_latency, cifs_ops, cifs_read_ops, cifs_write_ops fcp_ops, fcp_read_data, fcp_write_data, fcp_latency iscsi_latency, iscsi_ops, iscsi_read_data, iscsi_write_data avg_latency, other_ops, read_data, read_ops, total_ops, write_data, write_ops, queue_full nfsv3_ops, nfsv3_read_latency, nfsv3_read_ops, nsv3_write_latency, nfsv3_write_ops max_user_read_ms, avg_sys_pending_ms, avg_usr_pending_ms, max_sys_reads cifs_ops, fcp_ops, avg_processor_busy, cpu_busy, disk_data_read, disk_data_written, net_data_recv, net_data_sent, totalprocessor_busy, read_ops, write_ops vfiler_cpu_busy, vfiler_misc_ops, vfiler_net_data_recv, vfiler_data_sent, vfiler_read_bytes, vfiler_read_ops, vfiler_write_bytes, vfiler_write_ops avg_latency, cifs_other_latency, cifs_other_ops, cifs_read_data, cifs_read_latency, cifs_read_ops, cifs_write_data, cifs_write_latency, cifs_write_ops, nfs_other_latency, nfs_other_ops, nft_read_data, read_data, read_latency, read_ops, total_ops, write_data, write_ops 8 Click Finish. 25

26 vcenter Operations Management Pack for NetApp Installation and Configuration Guide 9 (Optional) To copy and apply the configuration of the NetApp Filer to another NetApp Filer, select the NetApp Filer and select Data Collection > Copy. Manually Discover NetApp Resources With manual discovery, the NetApp adapter sends a request to NetApp OnCommand Unified Manager Core (DFM) Server to return resources and you select the resources to import into vcenter Operations Manager. The discovery mode that you configure determines whether the adapter imports only the selected resource, or the selected resource and all of its child resources. With Basic Discovery mode, the adapter discovers NetApp systems, vfilers, or all resources, depending on the resource kind that you specify. The adapter imports only the resources that you select. With Hierarchical Discovery mode, the adapter discovers only NetApp systems. After the first collection cycle, the adapter imports all child objects for the NetApp systems that you import. The Retrieve Full Hierarchy resource identifier is enabled for resources imported in Hierarchical Discovery mode. For resources imported in Basic Discovery mode, the Retrieve Full Hierarchy resource identifier is disabled. NOTE: When you use auto-discovery, the Retrieve Full Hierarchy resource identifier is set to disabled by default. After the NetApp adapter imports a NetApp system in one discovery mode, it cannot rediscover the same NetApp system in another discovery mode. However, you can change the discovery behavior for a specific NetApp system by editing the resource for the NetApp system and selecting a different value from the Retrieve Full Hierarchy drop-down menu. For information about editing resources, see the Custom user interface online help. Prerequisites Create a NetApp adapter instance. See Add an Adapter Instance, on page 23. Procedure 1 Log in to the Custom user interface as an administrator. 2 Select Environment > Environment Overview. 3 On the List tab, click the Discover Resources icon. 4 Select the collector to use from the Collector drop-down menu. Unless you added additional collectors, the only available collector is vcenter Operations Standard Server. You can change the name of this collector when you install the standalone version. 5 Select NetApp Adapter from the Adapter kind drop-down menu. 6 Select the NetApp adapter instance from the Adapter instance drop-down menu. 7 Select a discovery mode from the Discovery Info drop-down menu. Option Basic Discovery Hierarchical Discovery Description Discovers NetApp resources depending on the resource kind you select from the Resource Kinds drop-down menu. Discovers only NetApp systems. After the first collection cycle the adapter imports all child objects for the NetApp systems that you import. 26

27 8 If you configured Basic Discovery mode, select the resource kind to discover from the Resource Kinds drop-down menu. You can select All to discover all resources. 9 (Optional) To omit resources that have already been added from the discovery results, select the Only New Resources check box. 10 Click OK to start the discovery process. The discovery process can take several seconds to several minutes. When the discovery process is finished, the Discovery Results window lists your resources. 11 Double-click each resource kind that contains resources to add. The resource list shows all of the resources of the specified resource kind. You can sort the resource list by clicking any column header. To find a specific resource in the list, type all or part of the resource name in the Search text box and click Search. 12 Select options for each kind of resource. Option Import Collect Attribute Package Description Import the resources but do not start collecting data. Resources appear in the resource list as Not Collection and data Is not stored and analysis is not performed. Import the resources and start collecting data. When you select the Collect check box, the Import check box is also selected. To use a non-default attribute package for a resource, select an attribute package from the drop-down menu or click Add to define a new attribute package. 13 Click OK. The Discovery Results window closes and the new resources appear on the List tab. What to do next If you did not select the option to start metric collection when you defined a resource, you can start metric collection after the resource is defined. For information about starting metric collection, see the Custom user interface online help. Validate Data Collection After you add a NetApp adapter instance, validate the data that the adapter collects in vcenter Operations Manager. Prerequisites Add a NetApp adapter instance. See Add an Adapter Instance, on page 23. Procedure 1 Check the Environment Overview page for NetApp resources. If you enabled Auto Discovery for the adapter instance, the adapter creates resources as soon as it 27

28 vcenter Operations Management Pack for NetApp Installation and Configuration Guide begins collecting metrics. If you disabled Auto Discovery for the adapter instance, you must discover resources manually. 2 Check the Health Tree for NetApp resource relationships. The adapter creates a resource relationship when the parent and child resource exist in vcenter Operations Manager. The adapter creates resource relationships during manual discovery. 3 View the Metric Graph to compare values to the data source. The NetApp adapter creates metrics during data collection. Creating Relationships Between Datastores and NetApp LUNs or Volumes When you create parent-child relationships between vsphere datastores and a NetApp LUNs or Volumes, you can quickly navigate to the NetApp object that corresponds to the datastore object in vcenter Operations Manager. A vsphere datastore is a logical container, analogous to a file system that hides the specifics of each storage device and provides a uniform model for storing virtual machine files. Depending on the type of storage that you use, a datastore can be backed by the Network File System (NFS) or Virtual Machine File System (VMFS) system format. A NFS datastore has a Server and a Folder property. The combination of these properties maps to a LUN or volume in a NetApp vfiler object. A VMFS datastore has a LUN path and naa number. The same naa number is assigned to that LUN in NetApp, and a relationship is created between the VMFS datastore and NetApp LUN based on that information. Using the Relationship Synchronization Feature Use the relationship synchronization feature to create and update parent-child relationships between vsphere datastores and NetApp LUNs or volumes. When the relationship synchronization feature is enabled, the NetApp adapter uses the RMI API to retrieve vsphere datastores from the vcenter Operations Manager server. The RMI API runs on port 1100 by default. If a datastore has the same path information as a NetApp volume or LUN, the NetApp adapter creates a relationship between the datastore and the NetApp volume or LUN. To enable the relationship synchronization feature, you set RelationshipSyncFlag to True in netapp.properties. The RelationshipSyncIntervals property in the netapp.properties file determines the number of collection cycles that must occur before the NetApp adapter synchronizes relationships. For example, a value of 10 (the default value) causes the adapter to synchronize relationships after 10 collection cycles. Modifying Adapter Properties You can customize NetApp adapter operation by modifying properties in the netapp.properties file in the conf folder. You must restart the collector service after modifying the netapp.properties file to make your changes take effect. You typically do not need to modify the properties in the netapp.properties file. 28