SMI-S Discovery

The Storage Management Service can use SLP to locate CIM Servers. From there, it can perform discovery of the managed elements. It can also be explicitly pointed to the access point - e.g., server-name:port - of a CIM server. The service aggregates requests and responses to multiple clients and maintains a cache of objects found during discovery and/or modified during provisioning operations. Credentials are checked for each client request so it is possible to use the service to manage storage for clients with different access privileges.

In Windows Server 2012, SLP can be used to locate providers which support the SNIA SMI-S profile. Providers can also be manually specified.

The service will query each provider for Registered Profiles, and then look at the associated objects of the supported types (Array, Virtualizer, Switch, Fabric, HHRC). From there, a multi-level discovery can take place.

Note  The service currently supports only one instance of the supported top-level objects. This means either an Array, a Virtualizer or an HHRC can be discovered.

The following are example objects and their discovery levels:

  • Level 0: Arrays, Fabrics, Switches
  • Level 1: Storage Pools, Target Ports, Hardware IDs
  • Level 2: Storage Volumes, Storage Groups (SPCs)
  • Level 3: Disk Drives

To identify a NAS-capable computer system (Windows Server 2012), the following criteria will be used.

  • The CIM_ComputerSystem instance must be associated to at least the NAS Head profile.
  • The Dedicated property of the SNIA representation of CIM_ComputerSystem (SNIA_ComputerSystem) must contain the value "16" (indicating a File Server).
Any computer system that does not meet the above criteria will be ignored during NAS discovery.


After a provider has been registered, a level 0 discovery will be performed. Registration is persistent and autodiscovery will be performed following system or service restart automatically. The default autodiscovery level can be modified via the registry.



Send comments about this topic to Microsoft