SMI-S Reboot. New SMI-S Agent, and a new Windows OS

This is really a reload of my previous SMI-S post regarding how to get started with SMI-S.

Since that time we have released a new version of the SMI-S Agent which supports Clsutered DataONTAP and is conformant to SMI-S Spec 1.6, but has only been 1.5 certified yet.


Within Windows 2012+ may have noticed a new feature called 'Windows Storage Management Service". This feature lets a Serveradministrator do what have historically been storage management functions directly from the windows Server Manager pane. We already have MMCs for our applications such as SnapDrive (7.0 which also just came out) and we already have complete command coverage in our PowerShell Toolkit but most storage vendors have not had the foresight to do this. 


This feature is about using a standards approach (in this case the SNIA SMI-S) to allow a common set of PowerShell commands to do common storage deployment tasks such as creating an aggregate, create a LUN, create a masking group, and map a LUN to that masking group. The obvious advantage to you is that a common PowerShell script or application can request storage from multiple vendors storage without needing a script rewrite.

Ok, let’s do this.

  • Step 1 is to create a fresh Virtual Machine with the following minimums.
    • Processors: 2 (1 required), RAM: 2GB (1 required, but I recommend 6 for performance)
    • Disk Space: 100GB (for OS, the agent needs only 4GB)
    • OS: Windows2008r2 or Windows2012
    • Make sure that .net351 and SNMP features have been added
    • Software Name: Data ONTAP SMI-S Agent Version: 5.0 (From the site)
    • Be sure to log in under a LOCAL machine account, and NOT a domain account.
  • Step 3 Install the Software. Very quick process. Click Next, then Install, then Next, then Finish. Check the installation and verify the CIM Server is now running.

Look for Data ONAP SMI-S Agent, and click. It will open a Command window.

C:\Program Files (x86)\Ontap\smis\pegasus\bin> SMIS CIMSERVER STATUS
Data ONTAP SMI-S Agent is running.
  • Step 5 Create a SMI-S account that will be used to connect to and manage the array.

In this step you will create an account that will be given permissions to access an array. In this case I would create a user named SMIUser1 with a password of SMIPass1, and on the controller I would create an account called FASUser1 with the password FASPass1. Once these accounts exist, use the following command to make the connection.

C:\Program Files (x86)\Ontap\smis\pegasus\bin> CimServer –s enableAuthentication=true
C:\Program Files (x86)\Ontap\smis\pegasus\bin> CimUser –a –u SMIUser1 –w SMIPass1

C:\Program Files (x86)\Ontap\smis\pegasus\bin> SMIS cimserver start

C:\Program Files (x86)\Ontap\smis\pegasus\bin> SMIS addsecure FASUser1 FASPass1

Returned Path

  • Step 6 Gather some data. Check to make sure that the SMI-S Agent is gathering data from the Target Device. The simple command to list out the disks in the array can be issued. You should see a line for each disk in the system.
C:\Program Files (x86)\Ontap\smis\pegasus\bin> SMIS disks


  • Step 7 Go to the Server you want to use the new SMI-S connection. Enable its SMI-S feature.

From the Windows 2012 server, you can either use Server Manager to add a new feature or use PowerShell command window.

PS  C:\Users\Administrator> Add-WindowsFeature WindowsStorageManagementService 

  • Step 8 User the new Storage Module commands to connect this server to the SMI-S Server.

The acts of connecting to the SMI-S Agent will in addition to saving the credentials for future use, itwill also add the security certificate to the proper store and perform a ursory discovery of the environment.

PS  C:\Users\Administrator>  Register-SMISProvidor –connectionuri

WARNING: Failed:  Certificate Authority not recognized.

Do you want to add  the following certificate to Trusted Certificate Store?   [Y] Yes [N] No [S}  Suspend [?} Help (default is “Y”): y

PS  C:\Users\Administrator> 

  • Step 9 Use the SMIS Commands to list and discover(update) your Assets

The command get-storagesubsystems can be used to get alist of controllers that are currently available via that SMI-S controller. Inthe case above, we only have a single controller inventoried by an SMI-S Agent,but an agent could be used to inventory a farm of controllers. The output of those commands should look similar to the following.  

The default discovery level of 0 will not let you see LUNs and Aggregates or create such. We need to increase the discovery level to allow us to get useful data and then to create assets on the target device. The second command will let you increase this default discovery level.

PS  C:\Users\Administrator> get-StorageSubsystem

Friendly Name  HealthStatus OperationalStatus
-------------          --------------     ------------------
SMISConsumerType Healthy OK
FAS6240A Healthy OK 

PS C:\Users\Administrator> get-StorageSubsystem FAS6240A | update-StorageProviderCache –DiscoveryLevelLevel2

The Storage Service has an iterative, multi-level cache. Once objects arediscovered, they can be operated upon efficiently. But deep discoveries can take a long time, depending on the number of manageable objects! The response from a successful change is only a new command prompt with no status or error. 


Once this discovery has been made, you will want to launch the Windows Server Manager to get a graphical representation of the Storage within windows.


I should note a few things for troubleshooting. First is that the username and password on the CimServer ARE CASE SENSITIVE. This is one of those things that trips up a lot of people since regular windows accounts are not case sensitive. Also, the SMI-S storage name listed from the get-storagesubsystem are ALSO case sensistive.

I should also note that the SMI-S Agent that supports 1.5 is required to support Windows 2012R2, so you want this new version 5.0 of the NetApp SMIS Agent since it is conformant. I should also note that you should run the SMIS Agent 5 only on a 2012 or 2008r2 machine, as its isn't supported on 2012R2 yet.

I should also note that you should NOT use server manager to create your Aggregates for you. It will try and create them using RAID_4 instead of RAID_DP. This is one of those things we are working on.


I am trying to follow your guide, but I cannot add the filer:

ogram Files (x86)\Ontap\smis\pegasus\bin>smis.cmd addsecure root

password: ********

i CIMException:  Cmd= ci Object= ONTAP_FilerData Code= 1

RR_FAILED: Filer return: Can't connect to host (err=10060). - With storage system

If I type the wrong root password, I see on the filer that the connection fails

netappdev1a> Mon MarMon Mar  3 17:14:01   3 17:CET [netappdev1a: HTTPPool01:warning]: HTTP XML Authentication failed from
14:01 CET [netappdev1a: HTTPPool01:warning]: HTTP XML Authentication failed from

So I think that somehow the filer is trying to communicate with the server and it cannot access it?

Thank you and regards,


Hi Miguel,


Could you please share the resolution if you are able to the cluster successfully to add SMIS. Im facing simialr issue.