Disabling MPIO may not be at device level but for all the devices , which is not recommended when there is IO to the underlying Block Storage Device.
But following can be tried.
* Check if the initiator is logged in
fcp initiator show
(vserver fcp initiator show)
Logical Port Initiator Initiator
Vserver Interface Address WWNN WWPN Igroup
--------- ----------------- -------- ------------ ------------ ---------------
vserver LifFCP1 20:00:00:10:9b:57:94:ce 10:00:00:10:9b:57:94:ce igroupname
*
igroup show -igroup igroupname
Vserver Name: vserver
Igroup Name: igroupname
Protocol: mixed
OS Type: vmware
Portset Binding Igroup: -
Initiators: 10:00:00:10:9b:57:94:ce
Child Igroups: -
Initiator Comments: -
Initiator Comments: -
Igroup UUID: 3fc5b0e7-9370-11ee-b474-00a098f3e343
ALUA: true
Initiators: 10:00:00:10:9b:57:94:ce (logged in) << Check if the host initiator is logged in
Vserver UUID: 065f43a9-7ee7-11ee-86d3-00a098f3e357
Delete on Last Unmap: -
New Name: -
Igroup Comment: -
Child Names: -
Parent Names: -
Replication Peer: -
Replication Error: -
Replication Error Igroup: -
Peer Vserver UUID: -
Peer Igroup UUID: -
Replicated Igroup Contains Unreplicated LUNs: false
* And if the initiator is logged in then , Rescan for new Disks in the Windows Disk Management