NetApp Adapter Installation and Configuration Guide

Transcription

1 NetApp Adapter Installation and Configuration Guide This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this document, see EN

2 NetApp Adapter Installation and Configuration Guide You can find the most up-to-date technical documentation on the VMware Web site at: The VMware Web site also provides the latest product updates. If you have comments about this documentation, submit your feedback to: Copyright 2013 VMware, Inc. All rights reserved. Copyright and trademark information. VMware, Inc Hillview Ave. Palo Alto, CA VMware, Inc.

3 Contents NetApp Adapter Installation and Configuration Guide 5 Updated Information 7 1 Introduction to the NetApp Adapter 9 Understanding NetApp Integration 10 Installation and Configuration Requirements 11 2 Installing the NetApp Adapter 13 Install the Adapter in a Standalone Installation 13 Install the Adapter in a vapp Installation 14 NetApp Adapter Folders and Files 15 3 Configuring the NetApp Adapter 17 Overview of Configuration Steps 17 Set Up a Resource Group to Filter Resources 18 Add a Credential 18 Add an Adapter Instance 19 Configure NetApp DFM Server 4.0 or Later to Collect Metrics 20 Configure NetApp DFM Server 3.8 to Collect Metrics 21 Manually Discover NetApp Resources 22 Validate Data Collection 23 Creating Relationships Between Datastores and NetApp LUNs or Volumes 24 Modifying Adapter Properties 25 4 Troubleshooting the NetApp Adapter 29 Troubleshooting a NetApp Adapter Instance 29 Viewing System Log Files 29 Resolving Common Problems 30 5 NetApp Metrics 35 NetApp System Metrics 35 NetApp vfiler Metrics 38 NetApp Volume Metrics 38 NetApp LUN Metrics 41 NetApp Aggregate Metrics 41 Index 43 VMware, Inc. 3

4 NetApp Adapter Installation and Configuration Guide 4 VMware, Inc.

5 NetApp Adapter Installation and Configuration Guide The NetApp Adapter Installation and Configuration Guide describes how to install and configure the NetApp adapter for vcenter Operations Manager. Intended Audience This information is intended for anyone who needs to install and configure the NetApp adapter. VMware, Inc. 5

6 NetApp Adapter Installation and Configuration Guide 6 VMware, Inc.

7 Updated Information The NetApp Adapter Installation and Configuration Guide is updated with each release of the product or when necessary. This table provides the update history of the NetApp Adapter Installation and Configuration Guide. Revision Description EN Added support for NetApp DFM Server 5.2. See NetApp DFM Server Compatibility, on page 11. Added a note that you must have the Global Full Control role in order to create relationships between datastores and NetApp LUNs. See Creating Relationships Between Datastores and NetApp LUNs or Volumes, on page 24. Added descriptions for the metricmapping.xml and metricmapping_3_8.xml files. See NetApp Adapter Folders and Files, on page 15. Added a clarification regarding the use of the metricmapping.xml. See Modifying Adapter Properties, on page 25. EN Added support for NetApp DFM Server 5.1. See NetApp DFM Server Compatibility, on page 11. Added support for relationships between VMFS datastores and NetApp LUNs. See Creating Relationships Between Datastores and NetApp LUNs or Volumes, on page 24. EN Updated the library files listed in NetApp Adapter Folders and Files, on page 15. EN Added information about specifying nested DFM resource groups to Add an Adapter Instance, on page 19. Described how to manually discover NetApp resources and select a manual discovery mode. See Manually Discover NetApp Resources, on page 22. EN Added a note about NFS datastore support to Creating Relationships Between Datastores and NetApp LUNs or Volumes, on page 24. EN Modified Relationships Adapter Requirement, on page 12. Added NetApp Adapter Folders and Files, on page 15. Added Using the Relationship Synchronization Feature, on page 25. EN Added Modifying Adapter Properties, on page 25. EN Added installation steps to Install the Adapter in a Standalone Installation, on page 13 and Install the Adapter in a vapp Installation, on page 14. Added troubleshooting information in Resolving Common Problems, on page 30. EN Added information about configuring the protocol and port to use to connect to the DFM server to Add an Adapter Instance, on page 19. Added Set Up a Resource Group to Filter Resources, on page 18. EN The NetApp Adapter Technical Note is now the NetApp Adapter Installation and Configuration Guide. Added Cannot Read Resource Relationships from a PostgreSQL Database, on page 30. The NetApp Adapter Technical Note was the initial release of this document. VMware, Inc. 7

8 NetApp Adapter Installation and Configuration Guide 8 VMware, Inc.

9 Introduction to the NetApp Adapter 1 The NetApp adapter is an embedded adapter for vcenter Operations Manager. The adapter retrieves data from NetApp DataFabric Manager (DFM) Server. This chapter includes the following topics: Understanding NetApp Integration, on page 10 Installation and Configuration Requirements, on page 11 VMware, Inc. 9

10 NetApp Adapter Installation and Configuration Guide Understanding NetApp Integration The NetApp adapter enables the exchange of information between NetApp DFM Server and vcenter Operations Manager. Figure 1 1. NetApp Integration Information Exchange Luns Filter Volumes Aggregates NetApp disk NetApp disk VFilter Luns Volumes NetApp disk Luns NetApp Manageability SDK NetApp DFM Server (Open ports 162, 8080, 8443, 8088, and 8488) Filter Volumes Aggregates Luns VFilter Volumes NetApp disk NetApp disk NetApp disk NetApp adapter instance Collector (inbuilt/remote) NetApp adapter configuration (DFM server address, user name, password) Web server vcenter Operations Manager How the Adapter Collects Data During each data collection cycle, the NetApp adapter opens a connection to the 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 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 DFM Server. 10 VMware, Inc.

11 Chapter 1 Introduction to the NetApp Adapter 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 For descriptions of the metrics that the adapter collects for these objects, see Chapter 5, NetApp Metrics, on page 35. When you add a NetApp adapter instance in vcenter Operations Manager, you can set an option to have the adapter instance configure the DFM server to collect the metrics that vcenter Operations Manager needs for analysis. If you do not set this option, you must use the NetApp Management Console to configure the 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 DFM Server Compatibility The NetApp adapter is compatible with NetApp DFM Server 3.8, 4.0.1, 5.0, 5.1, and 5.2. Connection Requirements The machine where you install the NetApp adapter must be able to access the DFM server. The NetApp adapter uses port 8088 to communicate with the DFM server. Port 8088 must be open on the DFM server. For more information about ports, see Figure 1-1. NetApp Adapter Instance Credential Requirements When you create a credential for a NetApp adapter instance, you must provide a DFM server user name and password. The NetApp adapter uses this credential to connect to and collect metrics from the DFM server. The 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. DFM Server User Account Requirements Auto Filer Configuration Setting true false DFM Server Role Global Read and Write Global Read VMware, Inc. 11

12 NetApp Adapter Installation and Configuration Guide vcenter Adapter Requirement You must install and configure the vcenter adapter before you install the NetApp adapter. See the VMware vcenter Adapter Installation and Configuration Guide. NOTE If you have a vcenter Operations Manager vapp installation, the vcenter adapter is installed by default. Relationships Adapter Requirement If you have a pre-5.6 version of vcenter Operations Manager, you must add a Relationships adapter instance to create and update parent-child relationships between vsphere datastores and NetApp LUNs or volumes. If you have vcenter Operations Manager 5.6 or later, you can use the relationship synchronization feature to create and update parent-child relationships between vsphere datastores and NetApp LUNs or volumes. When you enable the relationship synchronization feature, you do not need to create a Relationships adapter instance. For more information, see Creating Relationships Between Datastores and NetApp LUNs or Volumes, on page VMware, Inc.

13 Installing the NetApp Adapter 2 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 13 Install the Adapter in a vapp Installation, on page 14 NetApp Adapter Folders and Files, on page 15 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 Download the adapter installation TGZ file anonymously from ftp://ftp.integrien.com/. 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. VMware, Inc. 13

14 NetApp Adapter 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 Download the adapter installation PAK file anonymously from ftp://ftp.integrien.com. 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. 14 VMware, Inc.

15 Chapter 2 Installing the NetApp Adapter 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 contains several subfolders and files. Table 2 1. NetApp Adapter Folders and Files Folder File Description conf netapp.properties When you set the the Auto Filer Configuration option to true for a NetApp adapter instance, the properties in this file determine which events and metrics that the adapter instance collects. lib describe.xml history.txt version.txt open_source_license.txt metricmapping.xml metricmapping_3_8.xml OSS library files: dom4j jar Non-OSS library files: manageontap.jar Describes the adapter. Contains the history of adapter changes. Contains version information. Open source license file. Contains a list of metrics collected from the DFM server for DFM server version 4.0 and above. Metrics in this file are grouped by ResourceKind, then by ResourceGroup within every ResourceKind section. When you make changes to this file, follow the guidelines described in Modifying Adapter Properties, on page 25. Contains a list of metrics collected from the DFM server when working with DFM version 3.8. Metrics in this file are grouped by ResourceKind, then by ResourceGroup within every ResourceKind section. When you make changes to this file, follow the guidelines described in Modifying Adapter Properties, on page 25. JAR files that contain the classes and resources used to implement the adapter. VMware, Inc. 15

16 NetApp Adapter Installation and Configuration Guide 16 VMware, Inc.

17 Configuring the NetApp Adapter 3 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 17 Set Up a Resource Group to Filter Resources, on page 18 Add a Credential, on page 18 Add an Adapter Instance, on page 19 Configure NetApp DFM Server 4.0 or Later to Collect Metrics, on page 20 Configure NetApp DFM Server 3.8 to Collect Metrics, on page 21 Manually Discover NetApp Resources, on page 22 Validate Data Collection, on page 23 Creating Relationships Between Datastores and NetApp LUNs or Volumes, on page 24 Modifying Adapter Properties, on page 25 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 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 18 and Add an Adapter Instance, on page (Optional) If you set the Auto Filer Configuration option to false for the adapter instance, configure the DFM server to collect metrics. See Configure NetApp DFM Server 4.0 or Later to Collect Metrics, on page 20 or Configure NetApp DFM Server 3.8 to Collect Metrics, on page Validate the data that the adapter instance collects. See Validate Data Collection, on page Add a Relationships adapter instance to create and update parent-child relationships between vsphere datastores and NetApp LUNs or volumes. See Creating Relationships Between Datastores and NetApp LUNs or Volumes, on page (Optional) Modify adapter properties to customize adapter operation. See Modifying Adapter Properties, on page 25. VMware, Inc. 17

18 NetApp Adapter Installation and Configuration Guide Set Up a Resource Group to Filter Resources To filter the resources that a NetApp adapter instance imports from the 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. 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 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 13. 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. 18 VMware, Inc.

19 Chapter 3 Configuring the NetApp Adapter 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 DFM server from which the adapter instance retrieves data. If your DFM server does not use the default protocol and port, you can select a different protocol and port. You can also optionally specify a DFM server resource group to filter the resources that the adapter instance imports. If your environment is configured to support multiple DFM servers and the servers are monitored by vcenter Operations Manager, you must create an adapter instance for each DFM server. Prerequisites Install the NetApp adapter. See Chapter 2, Installing the NetApp Adapter, on page 13. 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 18. To filter the resources that the adapter instance imports from the DFM server, create a resource group. See Set Up a Resource Group to Filter Resources, on page 18. 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 DFM server in the 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 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 DFM server resource group is Global > TestGroup1 > TestGroup2, type TestGroup1/TestGroup2 in the Resource Group For Discovery text box. VMware, Inc. 19

20 NetApp Adapter Installation and Configuration Guide 10 Select an Auto Filer Configuration option. If you select true, the adapter instance configures the DFM server to collect metrics that vcenter Operations Manager needs for analysis. If you select false, you must configure the DFM server from the NetApp Management Console. The default setting is true. NOTE Because the auto filer configuration acts directly on the DFM settings, the option that you select affects all adapter instances for this DFM server. 11 Select the protocol to use to connect to the DFM server from the Protocol drop-down menu. Because the DFM server runs on HTTP by default, the default selection is HTTP. If your DFM server runs on HTTPS instead of HTTP, change the setting to HTTPS. 12 Type the DFM port to use to connect to the DFM server in the DFM Port text box. Because the DFM server runs on port 8088 by default, the default setting is If your DFM server runs on a different port, type that port number in the text box. 13 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. 14 Click OK to save your configuration. What to do next If you set the Auto Filer Configuration option to false, configure the DFM server to collect metrics. See Configure NetApp DFM Server 3.8 to Collect Metrics, on page 21 or Configure NetApp DFM Server 4.0 or Later to Collect Metrics, on page 20. 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 25. If you set the Auto Discovery option to false, manually discover NetApp resources. See Manually Discover NetApp Resources, on page 22. Configure NetApp DFM Server 4.0 or Later to Collect Metrics If you set the Auto Filer Configuration option to false for a NetApp adapter instance, you must configure the DFM server to collect the metrics that vcenter Operations Manager needs for analysis. If you have NetApp DFM Server 4.0, 5.0, or 5.1, you configure the 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 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 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 DFM server information. 3 Select Task > Manage Performance. 4 Click Setup. 5 Click Host and select the first host in the host list. 20 VMware, Inc.

21 Chapter 3 Configuring the NetApp Adapter 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 Counters to Enable 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, nfsv3_write_latency, nfsv3_write_ops max_user_reads, 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, net_data_recv, net_data_sent, total_processor_busy, read_ops, write_ops vfiler_cpu_busy, vfiler_misc_ops, vfiler_net_data_recv, vfiler_net_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, nfs_read_data, nfs_read_latency, nfs_read_ops, nfs_write_latency, nfs_write_ops, other_latency, other_ops, read_data, read_latency, read_ops, total_ops, write_data, write_ops 8 Click Finish. 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. Configure NetApp DFM Server 3.8 to Collect Metrics If you set the Auto Filer Configuration option to false for a NetApp adapter instance, you must manually configure the DFM server to collect the metrics that vcenter Operations Manager needs for analysis. If you have NetApp DFM Server 3.8, you configure the 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 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. Procedure 1 Log in to NetApp Management Console as the Global Read and Write role. 2 Select Setup > Custom views and select Add. 3 Type a name for the view in the Custom View Name text box. 4 Under Counters, click Add. 5 Select a category option to select a group name and select the counters to enable in the selected group. Group Cifs Fcp Iscsi Lun Nfsv3 Counters to Enable ifs_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, nfsv3_write_latency, nfsv3_write_ops VMware, Inc. 21

22 NetApp Adapter Installation and Configuration Guide Group Priorityqueue System vfiler Volume Counters to Enable max_user_reads, 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, net_data_recv, net_data_sent, total_processor_busy,read_ops,write_ops vfiler_cpu_busy, vfiler_misc_ops, vfiler_net_data_recv, filer_net_data_sent vfile, r_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, nfs_read_data, nfs_read_latency, nfs_read_ops, nfs_write_latency, nfs_write_ops, other_latency,other_ops, read_data, read_latency, read_ops,total_ops, write_data, write_ops 6 (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 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 19. 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. 22 VMware, Inc.

23 Chapter 3 Configuring the NetApp Adapter 7 Select a discovery mode from the Discovery Info drop-down menu. Option Basic Discovery Hierarchical Discovery Description Discovers NetApp systems, vfilers, or all resources, depending on the resource kind you select from the Resource Kinds drop-down menu. Discovers only NetApp systems. After the the first collection cycle, the adapter imports all child objects for the NetApp systems that you import. 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 Collecting 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 nondefault 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 19. VMware, Inc. 23

24 NetApp Adapter Installation and Configuration Guide Procedure 1 Check the Environment Overview page for NetApp resources. If you enabled autodiscovery for the adapter instance, the adapter creates resources as soon as it begins collecting metrics. If you disabled autodiscovery 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. NOTE If your DFM server version is lower than 5.0, you must have the Global Full Control role in order to create a relastionship between the NetApp LUN and the VMware adapter VMFS datastore. Otherwise, you will not be able to create a relationship between the NetApp LUN and its corresponding VMware VMFS datastore. This limitation applies only for creating relationships between the NetApp LUN and VMware VMFS datastore. All other relationships will work without requiring the Global Full Control role. Creating a Relationships Adapter Instance If you have a pre-5.6 version of vcenter Operations Manager, you must add a Relationships adapter instance to create and update a parent-child relationship between vsphere datastores and NetApp LUNs or volumes. The Relationships adapter updates relationships between resources in the vcenter Operations Manager database based on data that you store in an external database. You define parent-child relationships between resources in a table in this external database. The Relationships adapter reads resource relationships from this source relationships table. To read the source relationships table, the Relationships adapter uses a SELECT statement that you store in an SQL file. When you install the NetApp adapter, the installation utility places sample relationships SQL files in the vcenter-ops/user/plugins/inbound/netapp_adapter3/doc folder. The folder contains relationships SQL files for the Oracle and SQL Server database types. 24 VMware, Inc.

25 Chapter 3 Configuring the NetApp Adapter Table 3 1. Sample Relationships SQL Files by Database Type Database Type Oracle SQL Server File Name VMwareNetAppRelationship_oracle.sql VMwareNetAppRelationship_sqlserver.sql You can also use VMwareNetAppRelationship_oracle.sql with a PostgreSQL database. Change the file name to VMwareNetAppRelationship_pg.sql. Because the Relationships adapter reads relationships SQL files in the vcenterops/user/plugins/inbound/relationship_adapter3/conf folder, you must copy the relationships SQL file for your database type to that folder before you create a Relationships adapter instance. When you create a credential for the Relationships adapter instance, you must specify the user name and password of a user account that can read the database that contains the source relationships table. For information about specifying the correct privileges for a PostgreSQL database, see Cannot Read Resource Relationships from a PostgreSQL Database, on page 30. For complete information about installing and configuring the Relationships adapter, see the Relationships Adapter Installation and Configuration Guide. Using the Relationship Synchronization Feature If you have vcenter Operations Manager 5.6 or later, you can use the relationship synchronization feature to create and update parent-child relationships between vsphere datastores and NetApp LUNs or volumes. When you enable the relationship synchronization feature, you do not need to create a Relationships adapter instance. 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 the RelationshipSyncFlag to true in the netapp.properties file. The RelationshipSyncIntervals property 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. NOTE In a vapp installation, you modify the netapp.properties file on the Analytics virtual machine. When you set the Auto Filer Configuration option to true for a NetApp adapter instance, the properties in the netapp.properties determine which events and metrics the adapter instance collects. You can change the events and metrics that the DFM server collects by modifying these properties. You can change the mapping of metrics the DFM server returns to the NetApp adapter by modifying the metricmapping.xml or metricmapping_3_8.xml file. You typically do not need to modify the properties in the metricmapping.xml or metricmapping_3_8.xml file. VMware, Inc. 25

26 NetApp Adapter Installation and Configuration Guide Table 3 2. netapp.properties File Properties Property lunsvolumesandaggregatesasind ependentresources retrieveselectedresources Events CifsDefaultMetrics FcpDefaultMetrics IscsiDefaultMetrics LunDefaultMetrics Nfsv3DefaultMetrics PriorityQueueDefaultMetrics SystemDefaultMetrics VFilerDefaultMetrics VolumeDefaultMetrics RelationshipSyncIntervals RelationshipSyncFlag PathStringCharacterLimit CollectHistoricDataEnabled HistoricDataToCollectInHours HistoricDataChunkCollectionIn Hours Description Boolean value that determines whether volumes and aggregates appear as independent resources. Boolean value that determines how the adapter requests performance data from the DFM server during a collection cycle. If you set this property to true, the adapter discovers and imports performance data only for the filers imported in vcenter Operations Manager. If you set this property to false (the default setting), the adapter imports performance data for all DFM resources. If your DFM environment includes a large number of filers, you might want to set this property to true to improve performance. List of events. For a complete list of events, see the NetApp document Operations Manager Administration Guide for Use with DataFabric Manager Server 4.0. You can download the guide from ftp:// /netapp/dfm/4.0/opsmgr.pdf. List of metrics that belong to the cifs group. List of metrics that belong to the fcp group. List of metrics that belong to the iscsi group. List of metrics that belong to the LUN group. List of metrics that belong to the nfsv3 group. List of metrics that belong to the priorityqueue group. List of metrics that belong to the System group. List of metrics that belong to the vfiler group. List of metrics tha belong to the volume group. When RelationshipSyncFlag is set to true, determines the number of collections cycles that must occur before the adapter synchronizes relationships. For example, a value of 10 causes the adapter to synchronize relationships after 10 collection cycles. For more information, see Using the Relationship Synchronization Feature, on page 25. Boolean value that determines whether the relationship synchronization feature is enabled. For more information, see Using the Relationship Synchronization Feature, on page 25. This property is not included in the default netapp.properties file and the relationship synchronization feature is disabled. Maximum character limit of a path string. A path string is the absolute path to a specific NetApp volume or LUN. Because a filer can have multiple IP addresses, the path string is created by concatenating the paths for each IP address and filer name. For example, for a volume named vol1 on a filer named filer1, the path string might be /filer1/vol/vol1/ /filer1_ip_address1/vol/vol1/ /filer1_ip_addre SS2/vol/vol1/, where filer1_ip_address1 is the first IP address and filer1_ip_address2 is the second IP address. If a path string exceeds the character limit set by this property, the adapter trims the path string and relationships are not created in vcenter Operations Manager. If this problem occurs, modify the database schema to allow the identifier to have more characters and set this property to the new limit. Boolean value that determines whether the adapter collects historic data. Number of hours of historic data before the current time that the adapter collects. Number of hours of historic data that the adapter collects for each collection. 26 VMware, Inc.

27 Chapter 3 Configuring the NetApp Adapter The following example shows the default settings for each property in the netapp.properties file. lunsvolumesandaggregatesasindependentresources=true retrieveselectedresources=false Events=Host Up,Host Down CifsDefaultMetrics=cifs_latency,cifs_ops,cifs_read_ops,cifs_write_ops FcpDefaultMetrics=fcp_ops,fcp_read_data,fcp_write_data,fcp_latency IscsiDefaultMetrics=iscsi_latency,iscsi_ops,iscsi_read_data,iscsi_write_data LunDefaultMetrics=avg_latency,other_ops,read_data,read_ops,total_ops,write_data,write_ops,queue_f ull Nfsv3DefaultMetrics=nfsv3_ops,nfsv3_read_latency,nfsv3_read_ops,nfsv3_write_latency,nfsv3_write_o ps PriorityQueueDefaultMetrics=max_user_reads,avg_sys_pending_ms,avg_usr_pending_ms,max_sys_reads SystemDefaultMetrics=cifs_ops,fcp_ops,avg_processor_busy,cpu_busy,disk_data_read,disk_data_writte n,net_data_recv,net_data_sent,net_data_recv,net_data_sent,total_processor_busy,read_ops,write_ops VFilerDefaultMetrics=vfiler_cpu_busy,vfiler_misc_ops,vfiler_net_data_recv,vfiler_net_data_sent,vf iler_read_bytes,vfiler_read_ops,vfiler_write_bytes,vfiler_write_ops VolumeDefaultMetrics=avg_latency,cifs_other_latency,cifs_other_ops,cifs_read_data,cifs_read_laten cy,cifs_read_ops,cifs_write_data,cifs_write_latency,cifs_write_ops,nfs_other_latency,nfs_other_op s,nfs_read_data,nfs_read_latency,nfs_read_ops,nfs_write_latency,nfs_write_ops,other_latency,other _ops,read_data,read_latency,read_ops,total_ops,write_data,write_ops RelationshipSyncIntervals=10 PathStringCharacterLimit=1000 CollectHistoricDataEnabled=false HistoricDataToCollectInHours=0 HistoricDataChunkCollectionInHours=1 VMware, Inc. 27

28 NetApp Adapter Installation and Configuration Guide 28 VMware, Inc.

29 Troubleshooting the NetApp Adapter 4 Known troubleshooting information can help you diagnose and correct common problems with the NetApp adapter. This chapter includes the following topics: Troubleshooting a NetApp Adapter Instance, on page 29 Viewing System Log Files, on page 29 Resolving Common Problems, on page 30 Troubleshooting a NetApp Adapter Instance Perform these general troubleshooting steps to diagnose and correct problems with a NetApp adapter instance. Verify that the DFM server is running. Edit the adapter instance and click Test to verify the connection to the DFM server. View the collection status and collection state for the adapter instance resource on the Environment Overview page in vcenter Operations Manager. Check the adapter and collector logs for errors. See Viewing System Log Files, on page 29. Viewing System Log Files You can view NetApp adapter errors in the adapter and collector log files. You can view the adapter and collector log files in the vcenter Operations Manager user interface or in an external log viewer. The NetApp adapter log files are in the vcenter-ops/user/log/adapters/netappadapter folder. The collector log files are in the vcenter-ops/user/log folder. The logging level is set to ERROR by default. To troubleshoot issues, set the logging level to INFO. To view detailed messages, including micro steps, queries, and returned results, set the logging level to DEBUG. You can set the log level for each class in the log4j.properties file in the vcenter-ops/log/conf/collector folder, for example: log4j.logger.com.integrien.adapter3.netapp.netappadapter=debug NOTE If you set the logging level to DEBUG, log files can become large very quickly. Set the logging level to DEBUG only for short periods of time. For complete information about viewing log files and modifying log levels, see the online help. VMware, Inc. 29

30 NetApp Adapter Installation and Configuration Guide NetApp Adapter Classes The NetApp adapter uses certain adapter classes. com.integrien.adapter3.netapp.netappadapter com.integrien.adapter3.netapp.netappproperties com.integrien.adapter3.netapp.operation.dfmoperationimpl com.integrien.adapter3.netapp.util.netapputil com.integrien.adapter3.netapp.util.adapterenvironmentutil Resolving Common Problems Follow recommended procedures when you resolve common problems. Cannot Read Resource Relationships from a PostgreSQL Database The Relationships adapter cannot read relationships for NetApp resources from a PostgreSQL database. Problem An alert occurs for the Relationships adapter instance. The message Resource is down. Error retrieving relationships data: ERROR: permission denied for relation adapterkind appears in the Reason pane of the Alert Summary page for the alert. Cause When you create a credential for a Relationships adapter instance, you must specify a user account that can read the database that contains the source relationships table. This problem occurs when that user account does not have the correct privileges. Solution 1 On the Analysis virtual machine, log in to the database as postgres and create a new user. # su postgres # psql -d alivem alivevm=# create user username with password 'password'; CREATE ROLE 2 Grant SELECT privileges to the new user. alivevm=# grant SELECT on adapterkind,resourcekind,resourceidentifier,aliveresource,resourcekindident to relusr; GRANT 3 In the Custom UI, edit the credential for the Relationships adapter instance. a b c d e Select Environment > Configuration > Adapter Instances and select the Relationships adapter instance. Click the Edit Selected Adapter Instance icon. Click Edit next to the credential and type the name and password of the new user. Click OK in the Add Credential window to save the credential changes. Click OK in the Add Adapter Instance window 30 VMware, Inc.

31 Chapter 4 Troubleshooting the NetApp Adapter 4 Restart collection for the Relationships adapter instance. a b c Select Environment > Environment Overview and select the Relationships adapter instance on the List tab. Click the Stop Collecting icon. Click the Start Collecting icon. 5 On the Environment Overview page, verify that the health status of the Relationships adapter instance is 100. Metrics Do Not Appear In the User Interface NetApp metrics do not appear in the user interface. Problem The NetApp adapter instance is not collecting metrics. Cause There is a problem with the DFM server connection, metric collection configuration, or adapter instance configuration. Solution 1 If metrics do not appear in the user interface ten minutes after the first collection cycle, verify that other metrics are being collected. 2 If vcenter Operations Manager is collecting other metrics, check the status of the NetApp adapter instance resource on the Environment Overview page. Option Status is green Status is red Description There might be a metric collection configuration problem. When you configure a NetApp adapter instance, you can set the Auto Filer Configuration option to true or you can manually configure filers for metric collection. For information about manually configuring filers, see Configure NetApp DFM Server 3.8 to Collect Metrics, on page 21 or Configure NetApp DFM Server 4.0 or Later to Collect Metrics, on page 20. The DFM server is down or the NetApp adapter instance is misconfigured. See Adapter Instance Resource Status Is Red, on page 31. Adapter Instance Resource Status Is Red The adapter instance resource's status is red. Problem The status icon for the adapter instance resource is red on the Environment Overview page. Cause The DFM server is down or the NetApp adapter instance is misconfigured. Solution 1 Verify that the DFM server is running. 2 In the NetApp adapter instance configuration, verify that the DFM server IP address, user name, and password are correct. VMware, Inc. 31