SMI-S 1.0.0 Release Notes
SMI-S is an interface standard for storage management. SMI-S enables both hardware and software interoperability between different vendors’ enterprise storage products and allows vendors to develop to a single standard interface. For more information, see Storage Management Initiative at the Storage Networking Industry Association site.
Release 1.0 of the Pure Storage SMI-S provider is embedded in Purity 4.6.0+ release.
Release Compatibility
- This release is compatible with Purity releases that support REST API 1.2. We recommend the latest 4.6.x for this release.
Hardware Requirements
- This release is supported on FlashArray//M and FA-400 systems.
Software Requirements
- Purity 4.6 or higher.
SMI-S Specification Support
This release complies with the following:
- Storage Management Technical Specification, Part 3 Common Profiles Version 1.6.1, Revision 5
- Storage Management Technical Specification, Part 4 Block Devices Version 1.6.1, Revision 5
Certification Tests
- Passes the SNIA CTP tests.
- Passes the System Center Virtual Machine Manager (SCVMM) 2012 R2 with update rollup 8 test on fiber channel.
Known Issues
- When the array's CPU is under a very high workload, SMI-S clients may experience failures due to timeout. This is because the SMI-S service is running with lower priority than other critical array tasks.
- Some instance settings such as indication filters, listeners, and subscriptions maybe lost in the following scenarios:
- There is settings repository switch due to a controller failover.
- The SMI-S service fails unexpectedly and the settings repository is corrupted.
Troubleshooting
If the SMI-S provider cannot be added as a storage resource under SCVMM, check the following:
- Make sure that SMI-S is enabled using the Purity GUI (System > Configuration > SMI-S) or CLI (puresmis command).
- If the array does not have a valid certificate installed, modify the following registry key on the machine running SCVMM:
Key name: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Storage Management
Name: DisableHttpsCommonNameCheck
Type: REG_DWORD
Value: 1 - On Windows Server 2008R2, the TLS 1.1 protocol should be enabled. Manually add the following registry keys, subkeys, and values:
Key name: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1
Key name: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS1.1\Client
Name: DisabledByDefault
Type: REG_DWORD
Value: 0Key name: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS
1.1\Server
Name: DisabledByDefault
Type: REG_DWORD
Value: 0