You can manage the Data ONTAP DSM for Windows MPIO using Windows PowerShell cmdlets. The cmdlets replace the dsmcli commands, which were deprecated (but still available) in DSM 3.5. The dsmcli commands are not available in DSM 4.1.
More information
What you can do with the PowerShell cmdlets
Data ONTAP DSM for Windows MPIO includes Windows PowerShell cmdlets that you can use to manage the DSM. The following table lists the common tasks that you can complete with the cmdlets. For users upgrading from previous releases, it also lists the corresponding deprecated dsmcli commands.
Requirements for the PowerShell cmdlets
The Windows host must meet the following requirements before you can use the Windows PowerShell cmdlets with Data ONTAP DSM.
Running PowerShell cmdlets from a remote host
You do not have to run the PowerShell cmdlets directly from the host on which you want to run the commands. You can run the cmdlets from a remote host.
Displaying DSM settings
You can use the get-ontapdsmparams cmdlet to get information about Data ONTAP DSM. The cmdlet displays the current values for the default load balance policy, for the event log level, and for the parameters that affect how the DSM works.
Getting information about virtual disks
You can use the get-sandisk cmdlet to view information about virtual disks. For example, you can view the load balance policies assigned to virtual disks and the number of paths to virtual disks.
Changing the load balance policy using a cmdlet
You can use the set-sandisk cmdlet to change the load balance policy for existing virtual disks. The DSM sets the load balance policy for newly discovered virtual disks based on your settings in the set-ontapdsmparams cmdlet.
Viewing path information using a cmdlet
You can use the get-sanpath cmdlet to view information about the paths for virtual disks. For example, you can view the path IDs and path states for virtual disks.
Changing path status using a cmdlet
You can use the set-sanpath cmdlet to change the status of a path. For example, you can enable and disable paths. The state that you can assign to a path depends on the load balance policy of the virtual disk and the status of the other paths.
Changing the path weight using a cmdlet
You can use the set-sanpath cmdlet to set the weight assigned to each path for virtual disks with a Least Weighted Path load balance policy. DSM uses the available path with the lowest weight to access the disk.
Displaying statistics about SAN connectivity
You can use the get-sanstats cmdlet to display statistics about SAN connectivity. You can use the statistics to analyze and monitor the input/output (I/O) for a path to a virtual disk. For example, you can see the number of reads and writes for a path.
Clearing SAN connectivity statistics
The get-sanstats cmdlet provides statistics about SAN connectivity. You can use the clear-sanstats cmdlet to reset the statistics values to 0.
Prioritizing FC paths over iSCSI paths
You can use the iSCSILeastPreferred parameter to specify that the Data ONTAP DSM uses iSCSI optimized paths only if there are no FC optimized paths available. You might enable this setting if you want to use iSCSI paths as backups to FC paths.
Modifying values for DSM parameters
You can use the set-ontapdsmparams cmdlet to modify values for the DSM parameters that affect how the DSM works. You should not change the values unless directed to do so by your storage system support representative.