NetApp

Prerequisites

• NetApp Cluster Mode using ONTAP 8.0+ (excluding AFF and SolidFire)

• Transport Layer Security (TLS) is enabled

• A service account Turbonomic can use to connect to the NetApp target

Enabling TLS

Starting with version 5.4, by default Turbonomic requires Transport Layer Security (TLS) version 1.2 to establish secure communications with targets. NetApp filers have TLS disabled by default, and the latest version they support is TLSv1. If your NetApp target fails to validate on Turbonomic 5.4 or later, this is probably the cause.

If target validation fails because of TLS support, you might see validation errors with the following strings:

• No appropriate protocol

  To correct this error, ensure that you have enabled the latest version of TLS that your target technology supports. If this does not resolve the issue, contact IBM Support.

• Certificates does not conform to algorithm constraints

  To correct this error, refer to your NetApp documentation for instructions to generate a certification key with a length of 2048 or greater on your target server. If this does not resolve the issue, please contact IBM Support.

For information about enabling TLS, see the Data ONTAP System Administration Guide for sections on the SSL protocol.

Administrator role for the service user account

To discover and fully manage NetApp disk arrays, Turbonomic must have a service account that grants privileges to execute commands through the NetApp filer’s OnTap API (ontapi). In most cases, you can create the administrator account through the NetApp OnCommand System Manager, or from the NetApp command line as shown in the following example.

security login create -role admin -username <your_username> -application ontapi -authmethod password

If you prefer not to grant full administrator rights, see Creating Restricted Service Accounts In NetApp

Adding NetApp targets

1. Click Settings > Target configuration.

2. On the Target configuration page, click Add Target.

3. On the Select target page, click NetApp.

4. In the side panel, review the connection requirements and then click Connect Target.

5. On the Connection overview page, configure the following settings:

   • Hostname or IP address

     Specify the name or IP address of the NetApp cluster management server.

   • Username

     Specify the username for the NetApp service user account that Turbonomic uses to connect to the target.

   • Password

     Specify the password for the NetApp service user account that Turbonomic uses to connect to the target.

   • Connect using HTTPS

     If this option is selected, Turbonomic connects to the target by using SSL.

     This option is selected by default.

After validating the new target, Turbonomic discovers the connected storage entities. This table compares terms used in NetApp to those used in Turbonomic:

Entity mapping

After validating your targets, Turbonomic updates the supply chain with the entities that it discovered. The following table describes the entity mapping between the target and Turbonomic.

Storage targets (storage controllers) add Storage Controller and Disk Array entities to the supply chain. Disk Array entities then host Storage entities (datastores).

Monitored resources

Turbonomic monitors the following resources:

• Storage

  • Storage amount

    Storage amount is the measurement of storage capacity that is in use.

  • Storage provisioned

    Storage provisioned is the utilization of the entity's capacity, including overprovisioning.

  • Storage access (IOPS)

    Storage access, also known as IOPS, is the per-second measurement of read and write access operations on a storage entity.

    Note:

    When it generates actions, Turbonomic does not consider IOPS throttling that it discovers on storage entities. Analysis uses the IOPS it discovers on Logical Pool or Disk Array entities.

  • Latency

    Latency is the measurement of storage latency.

• Disk array

  • Storage amount

    Storage amount is the measurement of storage capacity that is in use.

  • Storage provisioned

    Storage provisioned is the utilization of the entity's capacity, including overprovisioning.

  • Storage access (IOPS)

    Storage access, also known as IOPS, is the per-second measurement of read and write access operations on a storage entity.

  • Latency

    Latency is the measurement of storage latency.

• Storage controller

  Note:

  Not all targets of the same type provide all possible commodities. For example, some storage controllers do not expose CPU activity. When a metric is not collected, its chart in the user interface will not display data.

  • CPU

    CPU is the measurement of CPU that is reserved or in use.

  • Storage amount

    Storage amount is the measurement of storage capacity that is in use.

    The storage allocated to a storage controller is the total of all the physical space available to aggregates managed by that storage controller.

Actions

Turbonomic supports the following actions:

• Storage

  • Move

  • Provision

    This action can only be executed outside Turbonomic.

  • Resize Up

    This action can only be executed outside Turbonomic.

• Disk array

  • Resize up

    This action can only be executed outside Turbonomic.

  • Move

    This action can only be executed outside Turbonomic.

  • Provision

    This action can only be executed outside Turbonomic.

• Storage controller

  • Provision

    This action can only be executed outside Turbonomic.

Note that Turbonomic can automate moving a datastore to a disk array on the same storage controller, as well as moves to a disk array on a different storage controller.