Data ONTAP SMI-S Agent 5.1 - Configure NetApp SMI-S provider with SCVMM 2012 R2 using Virtual Machine Manager GUI.

I hope you all enjoyed part 1 of the tutorial on how to configure Data ONTAP SMI-S Agent 5.1 - SCVMM integration with VMM Powershell cmdlets.


For all those folks who are not powershell savvy and want to go about the GUI way in this part 2 of my blog series i would demonstrate how you can perform these steps using SCVMM GUI console.


We would be covering these steps in three sections.


1)  Add a Storage Device using SMI-S to SCVMM 2012 R2 Console.

2)  Create SMI-S Run As Account.

3)  Discover and Import Storage Device Information and Assign Classification



1)  Add a Storage Device using SMI-S to SCVMM 2012 R2 Console.


Note :- The NetApp SMI-S server and the SCVMM 2012 server must be members of the same domain but reside on separate physical or virtual servers.


1) On the server hosting Microsoft SCVMM 2012 R2, open the SCVMM 2012 R2 Administrator console. Under the Home tab, select the Fabric Resources workspace as shown in below figure.


2) Expand Storage, right click on Arrays and choose Add Storage Devices from the drop down list and select a storage provider type as “SAN and NAS devices discovered and managed by a SMI-S provider” and click on next as shown in Figure below.



3)     In the Add Storage Devices Wizard screen, enter the IP address or fully qualified domain name (FQDN) of the NetApp SMI-S server along with the correct port number.


  • For http, uncheck the box for Use Secure Sockets Layer (SSL) connection and specify the correct port (5988 is the default)
  • For https, check the box for Use Secure Sockets Layer (SSL) connection and specify the correct port (5989 is the default)


It is recommended to use HTTPS protocol, enable Secure Sockets Layer (SSL)  for secure communication between the storage controller and the SMI-S Agent.



2) Create SMI-S Run As Account.


Click on the Browse button to the right of the Run As account field and click on “Create Run As Account”



Provide the account name (and description if desired) for the Run As account. Enter the user name and password and click ok to return to the previous screen.


Note :- The UserName and Password provided should be as the same credentials as the SMI-S local user account on the NetApp SMI-S server.



Click on the newly created Run As Account, and then click on the OK button.



Verify that the Run As Account and also the IP Address ( or FQDN ) is listed, then click on the next button.



3)   Discover and Import Storage Device Information and Assign Classification


As shown in Figure below, SCVMM 2012 R2 will display a progress bar as it begins to import the storage device information. The import process may require several minutes to complete.


During the discovery you may have a warning regarding the certificate. You can click “Import” to allow the connection. (More details at )


Note :- For managing a SVM (Storage Virtual machine)  in SMI-S, it is mandatory to have least one data LIF with firewall policy set to mgmt (to allow management traffic). It is also mandatory to have a cimuser (preferably a local user) added to SMIS agent using cimuser command.


Once the import process has finished, the NetApp storage arrays will be displayed as shown in the figure above. In this example, two SVM’s and two 7-mode controllers have been discovered and imported. Click on the Next button.



Classification of storage pools can be done along a number of different valid methods. The most commonly used method is to deploy your classifications based on the drive type and RPM such as the following:


  • Bronze: 7200 SATA
  • Silver: 10K RPM SAS 2.5”
  • Gold: 15K RPM SAS 3.5”
  • Platinum: SSD


Although these classification pools are commonly adopted, other methods to differentiate aggregates also these other methods might include the class of controller to which the storage is connected, because a mid range controller might not be capable of driving load as efficiently as a high-end controller, another possible classification type could be the size of the underlying aggregates; a 54-drive aggregate would have different performance and capacity considerations than a 10-drive set.


Your classification pools could also be defined strictly along financial boundaries, either by the cost of the underlying storage or by storage asset owner.


On the next screen, click on the Create Classification button to define one or more classifications for your imported NetApp storage arrays.


A “classification” is meant to describe the capabilities of the selected storage pool. Once a name and description have been provided for the storage classification, then click on the Add button as shown in above figure. Repeat the above steps to create additional storage classifications. In this example, four classifications were created: Gold, Silver, Bronze and Platinum.


Note :- Consider creating a special pool for monitoring the aggregates to which you don’t plan to deploy. An example of this is to create a pool for aggr0, which is commonly reserved for administrative use.



Once the classifications are created click on next. Next click on “Finish” to complete the wizard.



If a Storage Center has a large number of volumes, discovery will require extra time, up to 30 minutes or more per Storage Center.


I hope that you have enjoyed this blog entry  and have found this information helpful.


In the next series of blogs i would be talking about various use cases and powershell scripts which can be used to utilize  SCVMM - Data ONTAP SMI-S integration for effective Hyper-V storage management.

Good Luck !





Consider this scenario...

*Two heads, each with disk assigned to each.

*One vServer for both heads.

*Multiple LIFs so that traffic can come in on the head where the disk is located (avoids any interconnect traffic)

SCVMM seems to use on hostname for the array and I can't see any way to educate it about multiple LIFs.  That results in all traffic going to the same LIF and in some cases traversing the interconnect.  Do I have to create a second vserver just to get traffic to go via the other head?