NetApp SMI-S Provider takes a long time to start
NetApp SMI-S Provider can take up to 15 minutes to start on Windows systems with storage systems already under management, because the smis cimserver command waits for the provider local cache to populate. Use the smis cimserver command, the recommended method for starting the provider, and expect this delay before the provider becomes available.
-
Description
On Windows systems, with storage systems that are already under management, when you start NetApp SMI-S Provider using the
smis cimservercommand, the command does not return until the provider local cache is populated. It waits a maximum of 15 minutes while the cache is populated, and you cannot use NetApp SMI-S Provider until it returns.Using the
smis cimservercommand is the recommended method of starting NetApp SMI-S Provider.