SMI-S

SMI-S provides a standardized interface for vScope to access SAN configurations and data. This setup enhances storage visibility and management across various environments and vendor platforms.

vScope leverages SMI-S to access SAN storage data across multiple vendors, offering a standardized method for reading storage configurations and statuses. SMI-S is also useful for integrating SAN storage with Microsoft Hyper-V, making it a valuable feature for environments using SCVMM.

---

Supported Storage Systems and Configuration Details

Dell Compellent

For SMI-S integration, download the SMI-S Agent from Dell.

• Download the SMI-S Agent

Dell Equallogic

Dell Equallogic does not currently support SMI-S.

EMC VNX

• Target: SMI-S access requires a separate SMI-S Provider, as it is not integrated directly into the VNX appliance.

• Read More: Using the EMC SMI-S Provider with Windows Server 2012 and SCVMM

Hitachi Vantara

• SMI-S Guide: Hitachi Vantara SMI-S Guide

HP 3PAR

SMI-S must be enabled on the storage array.

• Enable SMI-S: Use the CLI command startcim.

• Check Status: Use the command showcim.

• Restart SMI-S Provider: Use stopcim –f –x.

• Target: Main cabinet IP

• Credentials: Use the highest access rights available.

IBM Storwize

• Target: Typically configured with the cluster IP using the default port 5989.

  Note

  IBM recommends using the cluster IP for CIM requests, not the management IP.

  • Use the lsnrctl status command to list instance IPs. Learn More

• Credentials: Access level should be “Operator” or higher. A “Monitor” role provides limited information; Superuser provides the most access. IBM User Roles Documentation

• Read More: IBM Knowledge Center on SMI-S

NetApp

NetApp provides a separate SMI-S Provider.

• Documentation: How to Enable SMI-S for NetApp

Nimble Storage

The Nimble SMI-S provider is embedded directly in the array, offering immediate SMI-S support.

• Documentation: Nimble SMI-S Overview

Tintri

For integrating Tintri with Hyper-V environments, refer to Tintri’s documentation.

• Documentation: Tintri VMStore with Hyper-V

Common Errors

Error	What happened?	Suggested action
Connection refused	The SMI-S probe was unable to inventory the storage.	Ensure that the credential is using the correct port and that the vScope server can communicate with the target.
No response: Connect timed out	The connection timed out.	Ensure that the credential is correct and that it uses the correct port.