NetApp Adapter Installation and Configuration Guide ... · PDF fileNetApp Adapter Installation and Configuration ... The NetApp Adapter Installation and Configuration Guide is

NetApp Adapter Installation andConfiguration Guide

This document supports the version of each product listed andsupports all subsequent versions until the document isreplaced by a new edition. To check for more recent editionsof this document, see http://www.vmware.com/support/pubs.

EN-000914-09

http://www.vmware.com/support/pubs

NetApp Adapter Installation and Configuration Guide

2 VMware, Inc.

You can find the most up-to-date technical documentation on the VMware Web site at:

http://www.vmware.com/support/

The VMware Web site also provides the latest product updates.

If you have comments about this documentation, submit your feedback to:

[email protected]

Copyright © 2013 VMware, Inc. All rights reserved. Copyright and trademark information.

VMware, Inc.3401 Hillview Ave.Palo Alto, CA 94304www.vmware.com

http://www.vmware.com/support/

mailto:[email protected]

http://pubs.vmware.com/copyright-trademark.html

Contents

NetApp Adapter Installation and Configuration Guide 5

Updated Information 7

1 Introduction to the NetApp Adapter 9

Understanding NetApp Integration 10Installation and Configuration Requirements 11

2 Installing the NetApp Adapter 13

Install the Adapter in a Standalone Installation 13Install the Adapter in a vApp Installation 14NetApp Adapter Folders and Files 15

3 Configuring the NetApp Adapter 17

Overview of Configuration Steps 17Set Up a Resource Group to Filter Resources 18Add a Credential 18Add an Adapter Instance 19Configure NetApp DFM Server 4.0 or Later to Collect Metrics 20Configure NetApp DFM Server 3.8 to Collect Metrics 21Manually Discover NetApp Resources 22Validate Data Collection 23Creating Relationships Between Datastores and NetApp LUNs or Volumes 24Modifying Adapter Properties 25

4 Troubleshooting the NetApp Adapter 29

Troubleshooting a NetApp Adapter Instance 29Viewing System Log Files 29Resolving Common Problems 30

5 NetApp Metrics 35

NetApp System Metrics 35NetApp vFiler Metrics 38NetApp Volume Metrics 38NetApp LUN Metrics 41NetApp Aggregate Metrics 41

Index 43

VMware, Inc. 3


4 VMware, Inc.

NetApp Adapter Installation and ConfigurationGuide

The NetApp Adapter Installation and Configuration Guide describes how to install and configure the NetAppadapter for vCenter Operations Manager.

Intended AudienceThis information is intended for anyone who needs to install and configure the NetApp adapter.

VMware, Inc. 5


6 VMware, Inc.

Updated Information

The NetApp Adapter Installation and Configuration Guide is updated with each release of the product or whennecessary.

This table provides the update history of the NetApp Adapter Installation and Configuration Guide.

Revision Description

EN-000914-09 n Added support for NetApp DFM Server 5.2. See “NetApp DFM Server Compatibility,” on page 11.n 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 NetAppLUNs or Volumes,” on page 24.

n Added descriptions for the metricmapping.xml and metricmapping_3_8.xml files. See “NetAppAdapter Folders and Files,” on page 15.

n Added a clarification regarding the use of the metricmapping.xml. See “Modifying AdapterProperties,” on page 25.

EN-000914-08 n Added support for NetApp DFM Server 5.1. See “NetApp DFM Server Compatibility,” on page 11.n Added support for relationships between VMFS datastores and NetApp LUNs. See “Creating

Relationships Between Datastores and NetApp LUNs or Volumes,” on page 24.

EN-000914-07 Updated the library files listed in “NetApp Adapter Folders and Files,” on page 15.

EN-000914-06 n Added information about specifying nested DFM resource groups to “Add an Adapter Instance,” onpage 19.

n Described how to manually discover NetApp resources and select a manual discovery mode. See “Manually Discover NetApp Resources,” on page 22.

EN-000914-05 Added a note about NFS datastore support to “Creating Relationships Between Datastores and NetAppLUNs or Volumes,” on page 24.

EN-000914-04 n Modified “Relationships Adapter Requirement,” on page 12.n Added “NetApp Adapter Folders and Files,” on page 15 .n Added “Using the Relationship Synchronization Feature,” on page 25.

EN-000914-03 Added “Modifying Adapter Properties,” on page 25.

EN-000914-02 n 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.

n Added troubleshooting information in “Resolving Common Problems,” on page 30.

EN-000914-01 n Added information about configuring the protocol and port to use to connect to the DFM server to “Add an Adapter Instance,” on page 19.

n Added “Set Up a Resource Group to Filter Resources,” on page 18.

EN-000914-00 n The NetApp Adapter Technical Note is now the NetApp Adapter Installation and Configuration Guide.n 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 VMware, Inc.

Introduction to the NetApp Adapter 1The NetApp adapter is an embedded adapter for vCenter Operations Manager. The adapter retrieves datafrom NetApp DataFabric Manager (DFM) Server.

This chapter includes the following topics:

n “Understanding NetApp Integration,” on page 10

n “Installation and Configuration Requirements,” on page 11

VMware, Inc. 9

Understanding NetApp IntegrationThe NetApp adapter enables the exchange of information between NetApp DFM Server andvCenter Operations Manager.

Figure 1‑1. NetApp Integration Information Exchange

Filter

NetAppManageability SDK

Filter

Luns

Volumes

Aggregates

VFilter LunsVolumes

Collector (inbuilt/remote)

Web server

vCenter Operations Manager

NetApp DFM Server

(Open ports 162, 8080,8443, 8088, and 8488)

NetApp disk

NetApp disk

NetApp disk

Luns

Volumes

Aggregates

VFilter LunsVolumes

NetApp disk

NetApp disk

NetApp disk

NetApp adapterinstance

NetApp adapter configuration(DFM server address,user name, password)

How the Adapter Collects DataDuring each data collection cycle, the NetApp adapter opens a connection to the DFM server and runs amain collection query.

The collection interval for the adapter instance resource determines how often the NetApp adapter collectsdata. 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 invCenter Operations Manager and collects data after the main collection query runs. If a new resourcebelongs to a resource kind that does not exist in vCenter Operations Manager, the adapter creates theresource kind. The adapter creates resource kinds according to the platform and server types in NetAppDFM Server.


10 VMware, Inc.

Data that the Adapter CollectsThe NetApp adapter can collect performance data, relationship data, and events for NetApp storage objects.

The NetApp adapter recognizes the following NetApp storage objects:

n System (host)

n vFiler

n Volume

n LUN

n 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 havethe adapter instance configure the DFM server to collect the metrics that vCenter Operations Manager needsfor analysis. If you do not set this option, you must use the NetApp Management Console to configure theDFM server to collect metrics.

Installation and Configuration RequirementsBefore you install and configure the NetApp adapter, you must make sure that your system meets certaininstallation and configuration requirements.

NetApp DFM Server CompatibilityThe NetApp adapter is compatible with NetApp DFM Server 3.8, 4.0.1, 5.0, 5.1, and 5.2.

Connection RequirementsThe machine where you install the NetApp adapter must be able to access the DFM server. The NetAppadapter 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 RequirementsWhen you create a credential for a NetApp adapter instance, you must provide a DFM server user nameand password. The NetApp adapter uses this credential to connect to and collect metrics from the DFMserver.

The DFM server user account that you provide must have certain roles depending on how you set the AutoFiler Configuration option for the adapter instance.

Table 1‑1. DFM Server User Account Requirements

Auto Filer Configuration Setting DFM Server Role

true Global Read and Write

false Global Read

Chapter 1 Introduction to the NetApp Adapter

VMware, Inc. 11

vCenter Adapter RequirementYou must install and configure the vCenter adapter before you install the NetApp adapter. See the VMwarevCenter Adapter Installation and Configuration Guide.

NOTE If you have a vCenter Operations Manager vApp installation, the vCenter adapter is installed bydefault.

Relationships Adapter RequirementIf you have a pre-5.6 version of vCenter Operations Manager, you must add a Relationships adapterinstance to create and update parent-child relationships between vSphere datastores and NetApp LUNs orvolumes.

If you have vCenter Operations Manager 5.6 or later, you can use the relationship synchronization feature tocreate 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 Relationshipsadapter instance.

For more information, see “Creating Relationships Between Datastores and NetApp LUNs or Volumes,” onpage 24.


12 VMware, Inc.

Installing the NetApp Adapter 2How you install the NetApp adapter depends on whether you have a vCenter Operations Managerstandalone or vApp installation.


n “Install the Adapter in a Standalone Installation,” on page 13

n “Install the Adapter in a vApp Installation,” on page 14

n “NetApp Adapter Folders and Files,” on page 15

Install the Adapter in a Standalone InstallationIf you have a standalone installation, you install the NetApp adapter by extracting the adapter installationfiles from a TGZ file and running an installation utility.

Prerequisites

n Download the adapter installation TGZ file anonymously from ftp://ftp.integrien.com/.

n Make a note of the build number in the TGZ file name. The build number appears after the adaptername, for example, adaptername-buildnumber.tgz.

n 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 Managerserver.

2 In the temporary folder, open the TAR file and extract and run the installer for your operating systemplatform.

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, itinstalls the adapter on the remote collectors.

The describe process might take several minutes. When the describe process is finished, the adapterappears in the Adapters Info pane. The build number is in the Adapter Version column.

VMware, Inc. 13

ftp://ftp.integrien.com/

7 Verify that the build number in the Adapter Version column for the adapter matches the build numberin the TGZ file that you downloaded.

The installation utility creates the netapp_adapter3 folder and netapp_adapter3.jar file under the vcenter-ops/user/plugins/inbound folder.

Install the Adapter in a vApp InstallationIf you have a vApp installation, you install the NetApp adapter from a PAK file.

Prerequisites

n Download the adapter installation PAK file anonymously from ftp://ftp.integrien.com.

n Make a note of the build number in the PAK file name. The build number appears after the adaptername, for example, adaptername-buildnumber.pak.

n 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: https://ipaddress/admin/

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 updateis finished.


For example: https://ipaddress/vcops-custom/

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 adapterappears 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 numberin the PAK file that you uploaded.

The installation utility creates the netapp_adapter3 folder and netapp_adapter3.jar file in the vcenter-ops/user/plugins/inbound folder.


14 VMware, Inc.

ftp://ftp.integrien.com

NetApp Adapter Folders and FilesThe installer places the NetApp adapter files in the netapp_adapter3 folder under the vcenter-ops/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 FilerConfiguration option to true for a NetAppadapter instance, the properties in this filedetermine which events and metrics thatthe adapter instance collects.

describe.xml Describes the adapter.

history.txt Contains the history of adapter changes.

version.txt Contains version information.

open_source_license.txt Open source license file.

metricmapping.xml Contains a list of metrics collected fromthe DFM server for DFM server version4.0 and above. Metrics in this file aregrouped by ResourceKind, then byResourceGroup within everyResourceKind section. When you makechanges to this file, follow the guidelinesdescribed in “Modifying AdapterProperties,” on page 25.

metricmapping_3_8.xml Contains a list of metrics collected fromthe DFM server when working with DFMversion 3.8. Metrics in this file are groupedby ResourceKind, then by ResourceGroupwithin every ResourceKind section. Whenyou make changes to this file, follow theguidelines described in “ModifyingAdapter Properties,” on page 25.

lib OSS library files:n dom4j-1.6.1.jar

Non-OSS library files:n manageontap.jar

JAR files that contain the classes andresources used to implement the adapter.

Chapter 2 Installing the NetApp Adapter

VMware, Inc. 15


16 VMware, Inc.

Configuring the NetApp Adapter 3To configure the NetApp adapter, you must add a credential and an adapter instance invCenter Operations Manager. Depending on your configuration, you might need to perform additionalsteps.


n “Overview of Configuration Steps,” on page 17

n “Set Up a Resource Group to Filter Resources,” on page 18

n “Add a Credential,” on page 18

n “Add an Adapter Instance,” on page 19

n “Configure NetApp DFM Server 4.0 or Later to Collect Metrics,” on page 20

n “Configure NetApp DFM Server 3.8 to Collect Metrics,” on page 21

n “Manually Discover NetApp Resources,” on page 22

n “Validate Data Collection,” on page 23

n “Creating Relationships Between Datastores and NetApp LUNs or Volumes,” on page 24

n “Modifying Adapter Properties,” on page 25

Overview of Configuration StepsConfiguring the NetApp adapter involves several steps.

1 (Optional) Create a resource group to filter the resources that the NetApp adapter instance importsfrom the DFM server. See “Set Up a Resource Group to Filter Resources,” on page 18.

2 Add an adapter instance and credential. See “Add a Credential,” on page 18 and “Add an AdapterInstance,” on page 19.

3 (Optional) If you set the Auto Filer Configuration option to false for the adapter instance, configure theDFM server to collect metrics. See “Configure NetApp DFM Server 4.0 or Later to Collect Metrics,” onpage 20 or “Configure NetApp DFM Server 3.8 to Collect Metrics,” on page 21.

4 Validate the data that the adapter instance collects. See “Validate Data Collection,” on page 23.

5 Add a Relationships adapter instance to create and update parent-child relationships between vSpheredatastores and NetApp LUNs or volumes. See “Creating Relationships Between Datastores andNetApp LUNs or Volumes,” on page 24.

6 (Optional) Modify adapter properties to customize adapter operation. See “Modifying AdapterProperties,” on page 25.

VMware, Inc. 17

Set Up a Resource Group to Filter ResourcesTo filter the resources that a NetApp adapter instance imports from the DFM server, create a resource groupand specify the name of that resource group when you define the adapter instance. The adapter instanceimports 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 resourcesbased 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 8080.

2 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 resourcegroup.

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 CredentialThe NetApp adapter uses a user name and password to connect to the DFM server. You use this user nameand 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 youdefine the adapter instance, or you can add the credential when you define the adapter instance.

Prerequisites

n Install the NetApp adapter. See Chapter 2, “Installing the NetApp Adapter,” on page 13.

n Verify that the user account meets the credential requirements. See “NetApp Adapter InstanceCredential Requirements,” on page 11.

Procedure


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.

8 Click OK to add the credential for the adapter.

The credential appears in the list in the Manage Credentials window.

Add an Adapter InstanceYou must create an adapter instance for the NetApp adapter. The adapter instance defines the adapter typeand 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 instanceimports.

If your environment is configured to support multiple DFM servers and the servers are monitored byvCenter Operations Manager, you must create an adapter instance for each DFM server.

Prerequisites

n Install the NetApp adapter. See Chapter 2, “Installing the NetApp Adapter,” on page 13.

n Create a credential, or, if you plan to create a credential when you add the adapter instance, becomefamiliar with creating credentials. See “Add a Credential,” on page 18.

n 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


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 StandardServer. 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 mustmanually 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 aparticular DFM server resource group, type the name of the resource group in the Resource Group ForDiscovery text box.

Use a forward slash (/) to specify nested resource groups. For example, if the DFM server resourcegroup is Global > TestGroup1 > TestGroup2, type TestGroup1/TestGroup2 in the Resource Group ForDiscovery text box.

Chapter 3 Configuring the NetApp Adapter

VMware, Inc. 19

10 Select an Auto Filer Configuration option.

If you select true, the adapter instance configures the DFM server to collect metrics thatvCenter Operations Manager needs for analysis. If you select false, you must configure the DFM serverfrom 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 selectaffects 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 serverruns 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 8088. If your DFM serverruns 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 clickAdd 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.0or 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 metricsthat 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 DiscoverNetApp Resources,” on page 22.

Configure NetApp DFM Server 4.0 or Later to Collect MetricsIf you set the Auto Filer Configuration option to false for a NetApp adapter instance, you must configurethe 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 enablingcounters for the NetApp Filers. You must enable the counters for all of the NetApp Filers on the DFMserver. You can enable the counters for each NetApp Filer individually, or you can configure one NetAppFiler 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 notconfigure the new NetApp Filer, vCenter Operations Manager adapter performs analysis based on only apartial 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.

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 Counters to Enable

cifs cifs_latency, cifs_ops, cifs_read_ops, cifs_write_ops

fcp fcp_ops, fcp_read_data, fcp_write_data, fcp_latency

iscsi iscsi_latency, iscsi_ops, iscsi_read_data, iscsi_write_data

lun avg_latency, other_ops, read_data, read_ops, total_ops, write_data, write_ops, queue_full

nfsv3 nfsv3_ops, nfsv3_read_latency, nfsv3_read_ops, nfsv3_write_latency, nfsv3_write_ops

priorityqueue max_user_reads, avg_sys_pending_ms, avg_usr_pending_ms, max_sys_reads

system 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 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

volume 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 theNetApp Filer and select Data Collection > Copy.

Configure NetApp DFM Server 3.8 to Collect MetricsIf you set the Auto Filer Configuration option to false for a NetApp adapter instance, you must manuallyconfigure 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 countersfor the NetApp Filers. You must enable the counters for all of the NetApp Filers on the DFM server. You canenable the counters for each NetApp Filer individually, or you can configure one NetApp Filer and apply itssettings 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.


Cifs ifs_latency, cifs_ops, cifs_read_ops, cifs_write_ops

Fcp fcp_ops, fcp_read_data, fcp_write_data, fcp_latency

Iscsi iscsi_latency, iscsi_ops, iscsi_read_data, iscsi_write_data

Lun avg_latency, other_ops, read_data, read_ops, total_ops, write_data, write_ops,queue_full

Nfsv3 nfsv3_ops, nfsv3_read_latency, nfsv3_read_ops, nfsv3_write_latency, nfsv3_write_ops


VMware, Inc. 21


Priorityqueue max_user_reads, avg_sys_pending_ms, avg_usr_pending_ms, max_sys_reads

System 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 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

Volume 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 theNetApp Filer and select Data Collection > Copy.

Manually Discover NetApp ResourcesWith manual discovery, the NetApp adapter sends a request to NetApp DFM Server to return resources andyou select the resources to import into vCenter Operations Manager. The discovery mode that you configuredetermines whether the adapter imports only the selected resource, or the selected resource and all of itschild resources.

With Basic Discovery mode, the adapter discovers NetApp systems, vFilers, or all resources, depending onthe resource kind that you specify. The adapter imports only the resources that you select. With HierarchicalDiscovery mode, the adapter discovers only NetApp systems. After the first collection cycle, the adapterimports all child objects for the NetApp systems that you import.

The Retrieve Full Hierarchy resource identifier is enabled for resources imported in Hierarchical Discoverymode. For resources imported in Basic Discovery mode, the Retrieve Full Hierarchy resource identifier isdisabled.

NOTE When you use auto-discovery, the Retrieve Full Hierarchy resource identifier is set to disabled bydefault.

After the NetApp adapter imports a NetApp system in one discovery mode, it cannot rediscover the sameNetApp system in another discovery mode. However, you can change the discovery behavior for a specificNetApp system by editing the resource for the NetApp system and selecting a different value from theRetrieve Full Hierarchy drop-down menu. For information about editing resources, see the Custom userinterface online help.

Prerequisites

Create a NetApp adapter instance. See “Add an Adapter Instance,” on page 19.

Procedure


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 StandardServer. 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.

7 Select a discovery mode from the Discovery Info drop-down menu.

Option Description

Basic Discovery Discovers NetApp systems, vFilers, or all resources, depending on theresource kind you select from the Resource Kinds drop-down menu.

Hierarchical Discovery Discovers only NetApp systems. After the the first collection cycle, theadapter 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 OnlyNew 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 listby clicking any column header. To find a specific resource in the list, type all or part of the resourcename in the Search text box and click Search.

12 Select options for each kind of resource.

Option Description

Import Import the resources but do not start collecting data. Resources appear inthe resource list as Not Collecting and data is not stored and analysis isnot performed.

Collect Import the resources and start collecting data. When you select the Collectcheck box, the Import check box is also selected.

Attribute Package To use a nondefault attribute package for a resource, select an attributepackage from the drop-down menu or click Add to define a new attributepackage.

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 metriccollection after the resource is defined. For information about starting metric collection, see the Custom userinterface online help.

Validate Data CollectionAfter you add a NetApp adapter instance, validate the data that the adapter collects invCenter Operations Manager.

Prerequisites

Add a NetApp adapter instance. See “Add an Adapter Instance,” on page 19.


VMware, Inc. 23

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 beginscollecting metrics. If you disabled autodiscovery for the adapter instance, you must discover resourcesmanually.

2 Check the Health Tree for NetApp resource relationships.

The adapter creates a resource relationship when the parent and child resource exist invCenter 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 orVolumes

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 invCenter Operations Manager.

A vSphere datastore is a logical container, analogous to a file system, that hides the specifics of each storagedevice and provides a uniform model for storing virtual machine files. Depending on the type of storagethat 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 orvolume in a NetApp vFiler object.

A VMFS datastore has a LUN path and naa number. The same naa number is assigned to that LUN inNetApp, and a relationship is created between the VMFS datastore and NetApp LUN based on thatinformation.

NOTE If your DFM server version is lower than 5.0, you must have the Global Full Control role in order tocreate a relastionship between the NetApp LUN and the VMware adapter VMFS datastore. Otherwise, youwill not be able to create a relationship between the NetApp LUN and its corresponding VMware VMFSdatastore. This limitation applies only for creating relationships between the NetApp LUN and VMwareVMFS datastore. All other relationships will work without requiring the Global Full Control role.

Creating a Relationships Adapter InstanceIf you have a pre-5.6 version of vCenter Operations Manager, you must add a Relationships adapterinstance to create and update a parent-child relationship between vSphere datastores and NetApp LUNs orvolumes.

The Relationships adapter updates relationships between resources in the vCenter Operations Managerdatabase based on data that you store in an external database. You define parent-child relationshipsbetween resources in a table in this external database. The Relationships adapter reads resourcerelationships from this source relationships table.

To read the source relationships table, the Relationships adapter uses a SELECT statement that you store inan SQL file. When you install the NetApp adapter, the installation utility places sample relationships SQLfiles in the vcenter-ops/user/plugins/inbound/netapp_adapter3/doc folder. The folder containsrelationships SQL files for the Oracle and SQL Server database types.


24 VMware, Inc.

Table 3‑1. Sample Relationships SQL Files by Database Type

Database Type File Name

Oracle VMwareNetAppRelationship_oracle.sql

SQL Server VMwareNetAppRelationship_sqlserver.sql

You can also use VMwareNetAppRelationship_oracle.sql with a PostgreSQL database. Change the file nameto VMwareNetAppRelationship_pg.sql.

Because the Relationships adapter reads relationships SQL files in the vcenter-ops/user/plugins/inbound/relationship_adapter3/conf folder, you must copy the relationships SQL filefor 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 andpassword of a user account that can read the database that contains the source relationships table. Forinformation about specifying the correct privileges for a PostgreSQL database, see “Cannot Read ResourceRelationships from a PostgreSQL Database,” on page 30.

For complete information about installing and configuring the Relationships adapter, see the RelationshipsAdapter Installation and Configuration Guide.

Using the Relationship Synchronization FeatureIf you have vCenter Operations Manager 5.6 or later, you can use the relationship synchronization feature tocreate 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 Relationshipsadapter instance.

When the relationship synchronization feature is enabled, the NetApp adapter uses the RMI API to retrievevSphere 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 arelationship between the datastore and the NetApp volume or LUN.

To enable the relationship synchronization feature, you set the RelationshipSyncFlag to true in thenetapp.properties file. The RelationshipSyncIntervals property determines the number of collectioncycles 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 PropertiesYou can customize NetApp adapter operation by modifying properties in the netapp.properties file in theconf folder. You must restart the collector service after modifying the netapp.properties file to make yourchanges 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 inthe netapp.properties determine which events and metrics the adapter instance collects. You can changethe events and metrics that the DFM server collects by modifying these properties. You can change themapping of metrics the DFM server returns to the NetApp adapter by modifying the metricmapping.xml ormetricmapping_3_8.xml file. You typically do not need to modify the properties in the metricmapping.xml ormetricmapping_3_8.xml file.


VMware, Inc. 25

Table 3‑2. netapp.properties File Properties

Property Description

lunsVolumesAndAggregatesAsIndependentResources

Boolean value that determines whether volumes and aggregates appear asindependent resources.

retrieveSelectedResources Boolean value that determines how the adapter requests performance data fromthe DFM server during a collection cycle. If you set this property to true, theadapter discovers and imports performance data only for the filers imported invCenter 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 setthis property to true to improve performance.

Events List of events. For a complete list of events, see the NetApp document OperationsManager Administration Guide for Use with DataFabric Manager Server 4.0. You candownload the guide from ftp://195.33.222.70/Netapp/DFM/4.0/opsmgr.pdf.

CifsDefaultMetrics List of metrics that belong to the cifs group.

FcpDefaultMetrics List of metrics that belong to the fcp group.

IscsiDefaultMetrics List of metrics that belong to the iscsi group.

LunDefaultMetrics List of metrics that belong to the LUN group.

Nfsv3DefaultMetrics List of metrics that belong to the nfsv3 group.

PriorityQueueDefaultMetrics List of metrics that belong to the priorityqueue group.

SystemDefaultMetrics List of metrics that belong to the System group.

VFilerDefaultMetrics List of metrics that belong to the vFiler group.

VolumeDefaultMetrics List of metrics tha belong to the volume group.

RelationshipSyncIntervals When RelationshipSyncFlag is set to true, determines the number of collectionscycles that must occur before the adapter synchronizes relationships. For example,a value of 10 causes the adapter to synchronize relationships after 10 collectioncycles. For more information, see “Using the Relationship SynchronizationFeature,” on page 25.

RelationshipSyncFlag Boolean value that determines whether the relationship synchronization feature isenabled. For more information, see “Using the Relationship SynchronizationFeature,” on page 25.This property is not included in the default netapp.properties file and therelationship synchronization feature is disabled.

PathStringCharacterLimit Maximum character limit of a path string. A path string is the absolute path to aspecific NetApp volume or LUN.Because a filer can have multiple IP addresses, the path string is created byconcatenating the paths for each IP address and filer name. For example, for avolume named vol1 on a filer named filer1, the path string might be|/filer1/vol/vol1/|/filer1_IP_ADDRESS1/vol/vol1/|/filer1_IP_ADDRESS2/vol/vol1/, where filer1_IP_ADDRESS1 is the first IP address andfiler1_IP_ADDRESS2 is the second IP address.If a path string exceeds the character limit set by this property, the adapter trimsthe path string and relationships are not created in vCenter Operations Manager.If this problem occurs, modify the database schema to allow the identifier to havemore characters and set this property to the new limit.

CollectHistoricDataEnabled Boolean value that determines whether the adapter collects historic data.

HistoricDataToCollectInHours Number of hours of historic data before the current time that the adapter collects.

HistoricDataChunkCollectionInHours

Number of hours of historic data that the adapter collects for each collection.


26 VMware, Inc.

ftp://195.33.222.70/Netapp/DFM/4.0/opsmgr.pdf

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 VMware, Inc.

Troubleshooting the NetApp Adapter 4Known troubleshooting information can help you diagnose and correct common problems with the NetAppadapter.


n “Troubleshooting a NetApp Adapter Instance,” on page 29

n “Viewing System Log Files,” on page 29

n “Resolving Common Problems,” on page 30

Troubleshooting a NetApp Adapter InstancePerform these general troubleshooting steps to diagnose and correct problems with a NetApp adapterinstance.

n Verify that the DFM server is running.

n Edit the adapter instance and click Test to verify the connection to the DFM server.

n View the collection status and collection state for the adapter instance resource on the EnvironmentOverview page in vCenter Operations Manager.

n Check the adapter and collector logs for errors. See “Viewing System Log Files,” on page 29.

Viewing System Log FilesYou can view NetApp adapter errors in the adapter and collector log files. You can view the adapter andcollector 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 collectorlog 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 viewdetailed 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/collectorfolder, 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 toDEBUG only for short periods of time.

For complete information about viewing log files and modifying log levels, see the online help.

VMware, Inc. 29

NetApp Adapter ClassesThe NetApp adapter uses certain adapter classes.

n com.integrien.adapter3.netapp.NetAppAdapter

n com.integrien.adapter3.netapp.NetAppProperties

n com.integrien.adapter3.netapp.operation.DFMOperationImpl

n com.integrien.adapter3.netapp.util.NetAppUtil

n com.integrien.adapter3.netapp.util.AdapterEnvironmentUtil

Resolving Common ProblemsFollow recommended procedures when you resolve common problems.

Cannot Read Resource Relationships from a PostgreSQL DatabaseThe 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 retrievingrelationships data: ERROR: permission denied for relation adapterkind appears in the Reason pane ofthe Alert Summary page for the alert.

Cause

When you create a credential for a Relationships adapter instance, you must specify a user account that canread the database that contains the source relationships table. This problem occurs when that user accountdoes 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 Select Environment > Configuration > Adapter Instances and select the Relationships adapterinstance.

b Click the Edit Selected Adapter Instance icon.

c Click Edit next to the credential and type the name and password of the new user.

d Click OK in the Add Credential window to save the credential changes.

e Click OK in the Add Adapter Instance window


30 VMware, Inc.

4 Restart collection for the Relationships adapter instance.

a Select Environment > Environment Overview and select the Relationships adapter instance on theList tab.

b Click the Stop Collecting icon.

c Click the Start Collecting icon.

5 On the Environment Overview page, verify that the health status of the Relationships adapter instanceis 100.

Metrics Do Not Appear In the User InterfaceNetApp 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 instanceconfiguration.

Solution

1 If metrics do not appear in the user interface ten minutes after the first collection cycle, verify that othermetrics are being collected.

2 If vCenter Operations Manager is collecting other metrics, check the status of the NetApp adapterinstance resource on the Environment Overview page.

Option Description

Status is green There might be a metric collection configuration problem. When youconfigure a NetApp adapter instance, you can set the Auto FilerConfiguration option to true or you can manually configure filers formetric 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,” onpage 20.

Status is red 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 RedThe 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, andpassword are correct.

Chapter 4 Troubleshooting the NetApp Adapter

VMware, Inc. 31

Exception Occurs During CollectionAn exception occurs when the NetApp adapter instance attempts to collect metrics.

Problem

The message netapp.manage.NaAPIFailedException: direction should be 'forward' or 'backward'appears in the log file.

Cause

The NetApp adapter version that you installed does not support NetApp DFM Server 3.8.1.

Solution

Make sure you installed the latest NetApp adapter version. For a list of the NetApp DFM Server versionsthat are compatible with the latest NetApp adapter version, see “NetApp DFM Server Compatibility,” onpage 11.

Capacity Data and Performance Data Collection Times Are Not SynchronizedThe capacity data and performance data collection times are not synchronized.

Problem

The collection times for capacity data and performance data are different.

Cause

If data collection is not in historic data collection phase or the adapter has finished collecting all of thedesired historic data, this problem can be caused by one or both of the following situations:

n The DFM server time is not properly aligned with real time.

n The vCenter Operations Manager server time is not properly aligned with real time.

The DFM server provides the time stamp for performance data and the time stamp for capacity data is basedon the vCenter Operations Manager server time. As a result, if either server is not properly aligned with realtime, the capacity data and performance data collection times will not be synchronized.

Solution

Make sure that both the DFM server and vCenter Operations Manager server times are aligned with realtime.

Data Collection Fails After UpgradingThe NetApp adapter does not perform data collection.

Problem

After upgrading the NetApp adapter from a build prior to 1062390 to build 1062390 and later, the adapterinstance does not enter the colllection state.

Cause

The NetApp adapter instance remains in the start state.


32 VMware, Inc.

Solution

1 Update the ResourceIdentifier.

UPDATE ResourceIdentifier

SET STRINGVAL='disabled'

WHERE RESOURCE_ID IN (SELECT RESOURCE_ID FROM AliveResource WHERE FLAG=7)

AND RKIDENT_ID IN (SELECT RKIDENT_ID FROM ResourceKindIdent WHERE

RKIDENT_KEY='RetrieveFullHierarchy')

2 Update AliveResource.

UPDATE AliveResource

SET FLAG=NULL

WHERE RESOURCE_ID IN (SELECT RESOURCE_ID FROM AliveResource WHERE FLAG=7)

3 Restart vC Ops services.

Chapter 4 Troubleshooting the NetApp Adapter

VMware, Inc. 33


34 VMware, Inc.

NetApp Metrics 5The NetApp adapter collects metrics for the NetApp System (the host), vFiler, Volume, LUN, and Aggregateobjects.


n “NetApp System Metrics,” on page 35

n “NetApp vFiler Metrics,” on page 38

n “NetApp Volume Metrics,” on page 38

n “NetApp LUN Metrics,” on page 41

n “NetApp Aggregate Metrics,” on page 41

NetApp System MetricsThe NetApp adapter collects certain metrics for the NetApp System object.

Capacity MetricsThese metrics appear in the Capacity group in the user interface.

Table 5‑1. NetApp SystemFilerMetrics

DFM PerformanceCounter Metric Name Description

NA Available Capacity Available space capacity in megabytes.

NA Total Capacity Total space capacity in megabtyes.

CIFS MetricsThese metrics appear in the cifs group in the user interface.

Table 5‑2. CIFS Metrics


cifs_ops Cifs Ops Number of CIFS operations per second to the qtree.

cifs_read_ops Cifs Read Ops Total number of CIFS read operations per second.NOTE Not supported in NetApp DFM Server 3.8.

cifs_write_ops Cifs Write Ops Total number of CIFS write operations per second.NOTE Not supported in NetApp DFM Server 3.8.

VMware, Inc. 35

FCP MetricsThese metrics appear in the fcp group in the user interface.

Table 5‑3. FCP Metrics


fcp_latency Fcp Latency Average latency, in milliseconds, for FCP operations.NOTE Not supported in NetApp DFM Server 3.8.

fcp_ops Fcp Ops FCP operations per second.

fcp_read_data Fcp Read Data FCP bytes read per second.

fcp_throughput Fcp Throughput FCP throughput per second.

fcp_write_data Fcp Write Data Bytes written with the block protocol, per second, to thevolume.

iSCSI MetricsThese metrics appear in the iscsi group in the user interface.

Table 5‑4. FCP Metrics


iscsi_latency Iscsi Latency Average latency, in milliseconds, for iSCSI operations.NOTE Not supported in NetApp DFM Server 3.8.

iscsi_ops Iscsi Ops iSCSI operations per second.

iscsi_read_data Iscsi Read Data iSCSI bytes read per second.

iscsi_throughput Iscsi Throughput iSCSI throughput per second.

iscsi_write_data Iscsi Write Data iSCSI bytes written per second.

NFS v3 MetricsThese metrics appear in the nfsv3 group in the user interface.

Table 5‑5. NFS v3 Metrics


nfsv3_ops Nfsv3 Ops Total number of NFS v3 operations per second.

nfsv3_read_latency Nfsv3 Read Latency Average latency, in milleseconds, for NFS v3 readoperations.

nfsv3_read_ops Nfsv3 Read Ops Total observed NFS V3 read operations per second.

nfsv3_write_latency Nfsv3 Write Latency Average latency, in milliseconds, for NFS v3 writeoperations.

nfsv3_write_ops Nfsv3 Write Ops Total observed NFS v3 write operations per second.

Priority Queue MetricsThese metrics appear in the priorityqueue group in the user interface.


36 VMware, Inc.

Table 5‑6. Priority Queue Metrics


avg_sys_pending_ms Average Sys Pending Millisecond Average pending time for system messages inmilliseconds.

avg_usr_pending_ms Average User PendingMillisecond

Average pending time for user messages in milliseconds.

max_sys_reads Max Sys Reads Maximum number of system read requests everoutstanding at one time for this queue.

max_user_reads Max User Reads Maximum number of user reads ever outstanding at onetime for this queue.

System MetricsThese metrics appear in the System group in the user interface.

Table 5‑7. System Metrics


avg_processor_busy Average Processor Busy Average processor use across all processors in the system.

cpu_busy Cpu Busy System CPU resource use.

disk_data_read Disk Data Read Disk KB read per second.

disk_data_read_mbps Disk Data Read Mbps Disk Data Read Rate in MBs per second.

disk_data_written Disk Data Written Disk KB written per second.

disk_data_written_mbps

Disk Data Written Mbps Disk Data Write Rate in MBs per second.

disk_throughput Disk Throughput Disk throughput per second.

load_inbound_mbps Load Inbound Mbps Total data received by the system

load_outbound_mbps Load Outbound Mbps Total data sent by the system.

load_read_bytes_ratio Load Read Bytes Ratio Ratio of the disk data read and load outbound mbps.

load_total_mbps Load Total Mbps Total data sent and received by the system.

load_write_bytes_ratio Load Write Bytes Ratio Ratio of the disk data write and load inbound megabytesper second.

max_disk_busy Max Disk Busy Use of the busiest disk in the system.

nas_throughput N/A Total NAS data sent and recieved by the system.

net_data_recv Net Data Received Network KB received per second.

net_data_sent Net Data Sent Network KB sent per second.

read_ops Read Ops Read operations per second.NOTE Not supported in NetApp DFM Server 3.8.

san_throughput San Throughput Total SAN data sent and recieved by the system.

total_processor_busy Total Processor Busy Total processor use of all processors in the system.

write_ops Write Ops Write operations per second.

Chapter 5 NetApp Metrics

VMware, Inc. 37

NetApp vFiler MetricsThe NetApp adapter collects certain metrics for the NetApp vFiler object.

vFiler MetricsThese metrics appear in the vFiler group in the user interface.

Table 5‑8. vFiler Metrics


vFiler_cpu_busy Cpu Busy Percentage CPU time used by the vfiler.

vFiler_data_transferred Data Transferred Total data transferred by the vfiler.

vFiler_misc_ops Misc Ops Number of other miscellaneous ops for the vfiler.

vFiler_net_data_recv Net Data Received Network KB received per second by the vfiler.

vFiler_net_data_sent Net Data Sent Network KB sent per second by the vfiler.

vFiler_nw_throughput Nw Throughput Total network data received and transmitted by thevfiler.

vFiler_read_bytes Read Bytes Number of bytes read by the vfiler.

vFiler_read_ops Read Ops Number of read ops for the vfiler

vFiler_total_ops Total Ops Total operations on the vfiler

vFiler_write_bytes Write Bytes Number of bytes written by the vfiler.

vFiler_write_ops Write Ops Number of write ops for the vfiler


Table 5‑9. Capacity Metrics

DFM Performance Counter Metric Name

Available Capacity Available Capacity

Total Capacity Total Capacity

NetApp Volume MetricsThe NetApp adapter collects certain metrics for the NetApp Volume object.

Volume MetricsThese metrics appear in the volume group in the user interface.

Table 5‑10. Volume Metrics


avg_latency Average Latency Average latency in microseconds for all operations on thevolume.

read_data Read Data Read bytes from filer per second.

read_latency Read Latency Average time for CIFS reads to the volume.


38 VMware, Inc.

Table 5‑10. Volume Metrics (Continued)


read_ops Read Ops Read operations per second.

san_latency San Latency Average time for SAN operations to the volume.

san_op San Ops Average time for SAN operations to the volume.

sys_ops System Ops SYS operations per second on the volume.

throughput Throughput Total data sent and received by the volume in bytes per second.

total_ops Total Ops Total operations per second.

user_ops User Ops User operations per second on the volume.

write_data Write Data Bytes written per second to the volume.

write_latency Write Latency Average time for writes to the volume.

write_ops Write Ops Number of writes per second to the volume.

CIFS MetricsThese metrics appear in the Cifs group in the user interface.

Table 5‑11. CIFS Metrics


cifs_latency Cifs Latency Average latency for CIFS operations in milliseconds.

cifs_ops Cifs Ops CIFS operations per second.

cifs_other_latency Cifs Other Latency Average time for other CIFS operations to the volume.

cifs_other_ops Cifs Other Ops Number of other CIFS operations per second to the volume.

cifs_write_data Cifs Write Data Bytes written per second through CIFS to the volume.NOTE Not supported in NetApp DFM Server 3.8.

cifs_write_latency Cifs Write Latency Average time for CIFS writes to the volume.

cifs_write_ops Cifs Write Ops Total number of CIFS write operations per second.

NFS MetricsThese metrics appear in the NFS group in the user interface.

Table 5‑12. NFS Metrics


nfs_latency Nfs Latency Average time for NFS operations to the volume.

nfs_ops Nfs Ops Number of NFS operations per second to the qtree.

nfs_other_latency Nfs Other Latency Average time for other NFS operations to the volume.

nfs_other_ops Nfs Other Ops Number of other NFS operations per second to the volume.

nfs_read_data Nfs Read Data Bytes read per second through NFS from the volume.NOTE Not supported in NetApp DFM Server 3.8.

nfs_read_latency Nfs Read Latency Average time for NFS reads to the volume.

nfs_read_ops Nfs Read Ops Number of NFS reads per second to the volume.


VMware, Inc. 39

Table 5‑12. NFS Metrics (Continued)


nfs_write_latency Nfs Write Latency Average time for NFS writes to the volume.

nfs_write_ops Nfs Write Ops Number of NFS writes per second to the volume.

nfs_other_latency Nfs Other Latency Average time for other NFS operations to the volume.

nfs_other_ops NFs Other Ops Other operations per second.

Priority Queue MetricsThese metrics appear in the Priority Queue group in the user interface.

Table 5‑13. Priority Queue Metrics


pq_max_sys_reads Priority Queue Max SystemReads

Maximum number of system read requests ever outstanding atone time for the default queue for the volume.

pq_max_user_reads Priority Queue Max UserReads

Maximum number of user reads ever outstanding at one timefor this queue in the volume.

pq_nvlog_limit Priority Queue Nvlog Limit Amount of NVLog this queue may use during CP for thevolume.

pq_nvlog_limit_full Priority Queue Nvlog LimitFull

Number of times the NVLog queue limit was hit during CP forthe volume.

pq_nvlog_used_max Priority Queue Nvlog LimitMax

Maximum amount of NVLog this queue may use during CP forthe volume.

pq_sys_read_limit Priority Queue SystemRead Limit

Limit on System reads outstanding on this queue in the volume.

pq_sys_sched_total Priority Queue SystemScheduled Total

Number of scheduling system requests in the volume.

pq_sys_weight Priority Queue SystemWeight

System request scheduling weight in the volume.

pq_usr_read_limit Priority Queue User ReadLimit

Limit on user reads outstanding on this queue in the volume.

pq_usr_sched_total Priority Queue UserScheduled Total

Number of scheduling user requests with in the volume.

pq_usr_weight Priority Queue User Weight User request scheduling weight within the volume.



Metric Name Description

Available Capacity Available capacity.

Total Capacity Total capacity.


40 VMware, Inc.

NetApp LUN MetricsThe NetApp adapter collects certain metrics for the NetApp LUN object.

LUN MetricsThese metrics appear in the lun group in the user interface.

Table 5‑15. LUN Metrics


avg_latency Average Latency Average latency in microseconds for all operationson the volume.

other_ops Other Ops Other operations per second.

queue_full Queue Full SCSI queue full responses per second.NOTE Not supported in NetApp DFM Server 3.8.

read_data Read Data Read bytes per second.

read_ops Read Ops Read operations per second.

throughput Throughput Total data sent and recieved by the LUN.

total_ops Total Ops Total operations per second.

write_data Write Data Bytes written per second to the volume.

write_ops Write Ops Number of writes per second to the volume.



DFM Performance Counter Metric Name

Total Capacity Total Capacity

NetApp Aggregate MetricsThe NetApp adapter collects certain metrics for the NetApp Aggregate object type.

All of the metrics appear in the Aggregate group in the user interface.

Table 5‑17. Aggregate Metrics


cp_read_blocks CP Read Blocks Number of blocks read per second during a CP on theaggregate.

cp_reads CP Reads Number of reads per second done during a CP to theaggregate.

pa_avg_disk_busy Average Disk Busy Average disk use in the aggregate.

pa_max_disk_busy Max Disk Busy Use of the busiest disk in the aggregate.

pa_min_disk_busy Min Disk Busy Use of the least busy disk in the aggregate.

total_transfers Total Transfers Total number of transfers per second services by theaggregate.


VMware, Inc. 41

Table 5‑17. Aggregate Metrics (Continued)


user_read_blocks User Read Blocks Number of blocks read per second on the aggregate.

user_reads User Reads Number of user reads per second to the aggregate.

user_write_blocks User Write Blocks Number of blocks written per second on the aggregate.

user_writes User Writes Number of user writes per second to the aggregate.


42 VMware, Inc.

Index

Aadapter classes 30adapter instances 19audience information 5

Ccapacity and performance data not

synchronized 32common problems 30configuration steps 17credentials 18

Ddata collected 11data collection 10

Eerror retrieving relationships data 30exception during collection 32

Iinstalling the adapter 13, 14integration overview 10introduction 9

Mmanual discovery 22metric collection problems 31

NNetapp Aggregate metrics 41NetApp Filer configuration 20, 21NetApp LUN metrics 41NetApp metrics 35NetApp System metrics 35NetApp vFiler metrics 38NetApp Volume metrics 38netapp_adapter3 folder 15netapp.properties file 25

Rred health status 31Relationships adapter 24Relationships adapter instance 24RelationshipSyncIntervals property 25

resource groups 18

Ssystem requirements 11system log files 29

Ttroubleshooting steps 29

Uupdated information 7

Vvalidating data collection 23

VMware, Inc. 43


44 VMware, Inc.

Documents

NetApp Adapter Installation and Configuration Guide ... · PDF fileNetApp Adapter Installation and Configuration ... The NetApp Adapter Installation and Configuration Guide is