Since the release of System Centre Virtual Machine Manager 2012, administrators are now able to configure their storage devices as part of their cloud fabric. To control this process, Microsoft use an open standard called SMI-S. With NetApp being leaders in the storage market, they offer a decent SMI-S solution:
The NetApp Data ONTAP SMI-S Agent, which supports the entire line of NetApp FAS systems and NetApp V-Series Virtualized storage systems, has been certified by SNIA’s Conformance Testing Program (CTP) suite for compliance with SNIA’s SMI-S v1.2 specification.
The functionality supported by the NetApps’ Data ONTAP SMI-S Agent includes features supported via standard profiles as well as NetApp-specific extensions.
Standard profiles support:
•Fibre Channel SAN functionality, including LUN creation, mapping and masking, and reporting
•NAS functionality, including resource discovery (aggregates, volumes, RAID groups, etc.) and system health monitoring
•iSCSI SAN functionality, including LUN creation and export, and session and connection creation
•NetApp-specific extensions support
•Capacity utilization (in the context of multi-protocol storage systems)
To configure SMI-S, you will need to configure a broker that controls all communication between SCVMM and the storage device. To set this up in my lab, I have the following systems in place:
- ms-vmm01 – My SCVMM server.
- ms-smis – This is my SMI-S broker Server
- ms-filer01 – This is my NetApp Filer.
To ensure your SMI-S solution is scalable and remains in a supported state, it must not be installed on the SCVMM server.
Now time to get some configuration done. I assume that you already have the NetApp filer (or vSim) and SCVMM server up and running and is a member of your domain. You can then follow these steps:
1) Download the NetApp SMI-S provider from the NetApp Now Site (you will need a login).
2) Log into your SMI-S broker server (in my case ms-smis) as an administrator and run through the wizard:
– Run the MSI as an administrator and click Next/Install:
– The wizard will then run through the progress. Once complete, click finish:
3) Once installed, you need to add your storage device by running the following command:
SMIS ServiceAccount ServicePassword add ms-filer01.ms.local filerrootAccount FilerPassword
(Where ServiceAccount is an AD account, and fileroot is a local filer account).
- If this is successful, you will see the following output:
Returned Path ONTAP_FilerData.hostName="ms-filer01.ms.local",port=80
5) Now that you have the SMI-S broker configured, you will need to add it into your Fabric with SCVMM:
You will need to load up your SCVMM console and make your way into the Fabric screen. From here, right click on ‘Providers’ under the Storage drop down and choose add device:
You will need to point this to your SMIS-Provider server (in this example ms-smis.ms.local:5988) and choose a relevant RunAs account.
You will then be asked which aggregates you wish to add and what classification they will be given. I will cover designing your SMI-S setup in a later blog post.
This post is my own work and does not have any connection with my employer.
Following any of the information in these posts are at your own risk. TameYourCloud do not accept any responsibility for any issues that may arise.
This content is owned by Paul Sanders from TameYourCloud.com. This cannot be copied or distributed without his express permission. A simple quotation for up to 2 sentances maybe used, but a link to the original post must be provided.
Share and Enjoy