IBM Support

Migrating from SDDDSM to Microsoft's MSDSM - SVC/Storwize

Preventive Service Planning


Abstract

The recommended multi-path driver to use on the Microsoft Windows platform when attached to SVC and Storwize storage devices running microcode levels V7.6.1.5 and later is changing from the SDDDSM to the default MSDSM. Please see below for details on migrating between SDDDSM and MSDSM.

Content

We recommend a three-step process, which will require a reboot of the Windows server (so plan for an expected outage). In the first step, the customer should modify the Disk TimeOutValue (a Microsoft Windows Registry setting) to a value of 60 decimal, if they have not already done so.

Step #1: We recommend uninstalling IBM's SDDDSM product by running the SDDDSM "setup.exe" in the SDDDSM subdirectory with " -S -U -N" parameters.  The three parameters perform the following functions:

-S Silent

-U Uninstall

-N NO reboot

Alternatively, the customer provided they have a very good understanding of the Windows platform may query the UnInstall string stored in the Windows Registry by invoking the following CLI command in a CMD window.

reg.exe query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Subsystem Device Driver DSM" /v UninstallString

IBM has created a simple BATCH file to automate the procedure of UnInstalling IBM's SDDDSM from a customers system.  While the batch file script is known to work, IBM cannot guarantee it will work in all environments. Hence, IBM is providing the source code which may permit the customer to modify it as necessary for their particular environment.  In essence, the batch file looks for the subdirectory in which the "datapath.exe" command is located.  It saves the location of that subdirectory into an Operating System environment variable called SDDdir. Next, the subdirectory is changed to the %ProgramFiles% subdirectory (we can not reside within a subdirectory that is intended to be removed via the RMDIR command). Finally, we execute the SDDDSM "setup" command to remove the SDDDSM instance from the Windows platform.

Please view the source code for the Windows BATCH file towards the bottom of this article.

Step #2: The following CLI command can be executed in a CMD Window that has elevated (ie Administrator) privileges.

reg.exe ADD HKLM\SYSTEM\CurrentControlSet\Services\Disk /v TimeOutValue /t REG_DWORD /d 60 /F

Step #3: We recommend rebooting the Windows server IMMEDIATELY after having uninstalled IBM's SDDDSM package with the "mpclaim" command and having Microsoft's mpclaim command claim any SPC-3 devices not claimed by other Device Specific Modules.  Since the IBM SDD Device Specific Module (SDDDSM) was uninstalled in the previous step (Step #2), then Microsoft's MSDSM should recognize and claim control of the IBM 2145 device types.

To use mpclaim, you must be running cmd.exe with administrator privileges.

mpclaim.exe -r  -i  -a   ""

The command above will add MPIO support for all storage arrays that are SPC-3 compliant and for any such devices that have not already been claimed by another DSM.

MPCLAIM Examples

Please see Appendix A of this MS Word document Microsoft Multipath I/O (MPIO) User’s Guide for Windows Server 2012 that is downloadable from www.microsoft.com

Step #4: After having rebooted, please verify that SDDDSM is no longer installed and that the IBM 2145 devices are under MSDSM control.

To use mpclaim, you must be running cmd.exe with administrator privileges.

mpclaim.exe -v config.txt

OR

mpclaim.exe -v config.txt -n

Please see the following URLs for more information:

Referencing MPCLAIM Examples

https://technet.microsoft.com/es-es/library/ee619743(v=ws.10).aspx

"Access Denied" error when you run mpclaim.exe command to retrieve MPIO configuration reports in Windows Server 2012 R2

https://support.microsoft.com/en-gb/help/3161579

Contents of UnInstall_SDDDSM.bat file

@ECHO ON

TITLE %0

REM #

REM ##########################################################################

REM # Licensed Materials - Property of IBM

REM # IBM XIV Storage System Software (program number 5639-XXA)

REM # (c ) Copyright IBM Corp. 2008-2018.  All Rights Reserved.

REM # US Government Users Restricted Rights -

REM # Use, duplication or disclosure restricted by GSA ADP Schedule

REM # Contract with IBM Corporation

REM # DISCLAIMER:

REM # The following source code is sample code created by IBM Corporation.

REM # This sample code is not currently part of any standard IBM product and is provided

REM # to you solely for the purpose of assisting you in the development of your

REM # applications. The code is provided 'AS IS', without warranty or condition

REM # of any kind. IBM shall not be liable for any damages arising out of your

REM # use of the sample code, even if IBM has been advised of the possibility of

REM # such damages.

REM ##########################################################################

REM # Author: Richard Heffel

REM # Email:  rheffel@us.ibm.com

REM

REM

PUSHD .

:-there

sc.exe STOP SDD_Service > NUL

timeout.exe /T 5 /NOBREAK > NUL

sc.exe query SDD_Service | findstr.exe STOPPED > NUL

IF NOT ERRORLEVEL 0 GOTO -there

REM

CD /D "%ProgramFiles%"

FOR /F "usebackq tokens=*" %%i in (`dir /s /b datapath.exe`) DO CD /D %%~dpi

SET SDDdir="%CD%"

SET UnInstallStr="%CD%\setup.exe" -S -U -N

CD /D "%ProgramFiles%"

REM

ECHO %UnInstallStr%

%UnInstallStr%

ECHO RD /S /Q %SDDdir%

POPD

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"STVLF4","label":"IBM Spectrum Virtualize software"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
25 November 2020

UID

ibm10739011