hello,
We had a similar MPIO setting discrepancy case in some ouf our hyper-V clusters , and it turns out Peer Persistence has an addditionnal prerequisite : on both Arrays, the vlun for the replicated volumes
MUST HAVE an identical LUNid ! I have been putting lunid in auto for years in my commands createvlun MY_CSV auto set:MY_HOSTSET, thinkingthe lunid being quite an useless parameter in modern OSes...
To fix that, Since we can't perform a removevlun on the passive side as long as the CSV is in the cluster (the hyper-v Cluster service puts a SCSI reservation on every path of the CSV), I ended up creating a new VV for each faulty CSV, the new ones having the correct configuraiton for PP. the I moved my VMs online with Hyper-V Storage Migration, removing the CSV from the cluster once its is empty, and so on to the next one ( I had 28 dubious CSVs)
here is a bad one, with LUNId 2 on the active and LUNid 3 on the passive, right before I destroyed it :
Code:
8440dsimg cli% showvlun -v CSV-SAS-PROD-D-01
[...]
VLUN Templates
Lun VVName HostName -Host_WWN/iSCSI_Name- Port Type
[b] 2 [/b]CSV-SAS-PROD-D-01 set:Hset_CLUHYSAS ---------------- --- host set
---------------------------------------------------------------------------
1 total
8440dsimg cli%
8440batc cli% showvlun -v CSV-SAS-PROD-D-01.r
[...]
VLUN Templates
Lun VVName HostName -Host_WWN/iSCSI_Name- Port Type
[b] 3[/b] CSV-SAS-PROD-D-01.r set:Hset_CLUHYSAS ---------------- --- host set
-----------------------------------------------------------------------------
and checking the cluster doesn't lock it, becore I removevv it :
8440batc cli% showrsv CSV-SAS-PROD-D-01.r
no reservations found
8440batc cli%