Create storage capability profiles
You can use ONTAP tools to manually create storage capability profiles, automatically generate a profile based on the capabilities of a datastore, or modify a profile to meet your requirements.
What you'll need
You must have registered your VASA Provider instance with ONTAP tools for VMware vSphere.
After setting up a profile, you can edit the profile as required.
On the ONTAP tools Home page, click Policies and Profiles.
Create a profile or edit an existing profile, as required:
If you want to…
Create a profile
Edit an existing profile
Click the profile that you want to modify from the profiles listed on the Storage Capability Profiles page.
To view the values that are associated with an existing profile, you can click the profile name in the Storage Capabilities Profile page. VASA Provider then displays the Summary page for that profile.
From New Datastore > Storage Systems, click on Create storage capability profile.
You Get the following message to confirm navigating away from the datastore window.
This will remove the data entered by closing the current workflow and opens the Create storage capability profile workflow. Do you wish to continue?
Click YES to open the Create storage capability profile window.
Complete the pages in the Create Storage Capability Profile wizard to set up a profile or to edit values to modify an existing profile.
Most of the fields in this wizard are self-explanatory. The following table describes some of the fields for which you might require guidance.
Identifying multiple profiles
You can use the Description field on the Name and Description tab to describe the purpose of the storage capability profile (SCP). Providing a good description is useful because it is a good practice to set up different profiles based on the applications that are being used.
For example, a business-critical application requires a profile with capabilities that support higher performance, such as AFF and ASA platform. A datastore that is used for testing or training might use a profile with a lower performance Flash Array Hybrid platform, and enable all of the storage efficiency capabilities and tiering to control costs. Combination of Platform type and asymmetric flag determines the type of SCPs. For example: Platinum_ASA_A, Platinum_AFF_A, Platinum_AFF_C.
If you have enabled “linked” mode for your vCenter Servers, then you must select the vCenter Server for which you are creating the storage capability profile.
Starting from ONTAP tools for VMware vSphere 9.13, you can create storage capability profiles using the combination of the following items:
Platform type - Performance, Capacity, and Flash Array Hybrid
Asymmetric flag - indicates storage system's SAN optimized (All San Array) status.
When Platform type is Performance and Asymmetric flag is TRUE, it considers storage system of type AFF-A
When Platform type is Performance and Asymmetric flag is False, it considers storage system of type ASA-A
When Platform type is Capacity and Asymmetric flag is True, it considers storage system of type AFF-C
When Platform type is Flash hybrid array and Asymmetric flag is NA, it considers storage system of type FAS
The options on the subsequent screens are updated based on your selection of the type of storage system.
You can select from the available protocols listed based on the platform selected for the storage system. While configuring virtual machines you can configure VM storage policies with storage capability profile and the protocol field filters datastores based on specific protocol. The field 'Any' allows you to work with all protocols.
You can set traditional QoS policies for your storage system by using the Performance tab.
When you select None, a QoS policy with no limit (infinite) is applied to a data VVol.
When you select QoS Policy Group, then a traditional QoS policy is applied to a VVol.
You can set the value for Max IOPS and Min IOPS which enables you to use the QoS functionality. If you select Infinite IOPS, the Max IOPS field is disabled. When applied for a traditional datastore, a QoS policy with “Max IOPS” value is created and assigned to a FlexVol volume. When used with a vVols datastore, a QoS policy with Max IOPS and Min IOPS values is created for each data vVols datastore.
Max IOPS and Min IOPS can also be applied to the FlexVol volume for a traditional datastore.
You must ensure that the performance metrics are not also set separately at an storage virtual machine (SVM) level, an aggregate level, or a FlexVol volume level.
The storage attributes that you can enable in this tab depend on the storage type that you select in the Personality tab.
If you select Flash Array Hybrid storage, you can configure space reserve (thick or thin), enable deduplication, compression, and encryption.
The tiering attribute is disabled because this attribute is not applicable to Flash Array Hybrid storage.
If you select AFF storage, you can enable encryption and tiering.
Deduplication and compression are enabled by default for AFF storage and cannot be disabled.
If you select ASA storage, you can enable encryption and tiering.
Deduplication and compression are enabled by default for ASA storage and cannot be disabled.
The tiering attribute enables the use of volumes that are part of a FabricPool-enabled aggregate (supported by VASA Provider for AFF systems with ONTAP 9.4 and later). You can configure one of the following policies for the tiering attribute:
None: Prevents volume data from being moved to the capacity tier
Snapshot: Moves user data blocks of volume Snapshot copies that are not associated with the active file system to the capacity tier
Review your selections on the Summary page, and then click OK.
After you create a profile, you can return to the Storage Mapping page to view which profiles match which datastores.