SCVMM 2012 R2: Hyper-V Cluster validation warning (Virtual SAN HP VSA)

Hi Experts,

Here is the configuration:

- 2 HP Aruba 2920 Switches with 2 x SFP+ in HP Trunk linking them together with direct attached cables
  + 2 x 10 Gb Ethernet ports on each switch to connect to Hyper-V hosts in X.

- 2 Windows Server 2012 R2 with Hyper-V role and last HP StoreVirtual DSM for MPIO installed (12.6)

- Storage: 2 HP VSA 12.6 VMs: one on each Hyper-V host (OS as VHDX, two RAID arrays as direct attached disks for storage (2 x 480 GB SSD as RAID1 and 8 x SAS 10K 900 GB as RAID5 + 1 hotspare). Adaptive Optimization and space reclamation activated.

- 1 SCVMM 2012 R2 VM on another Hyper-V Host for the time being
  Logical switches:

* iSCSI (2 x 10 Gb Server 2012 R2 Team (dynamic, switch independant) iSCSI initiator AND vSwitch for VSA VMs... we don't have more 10 Gb NICs... If we separate initiators and non Hyper-V managed vSwitch for VSAs we lose redundancy... We looked to replace the SFP+ HP Trunk by stack cables in the futur to be able to use SFP+ to connect to Hyper-V hosts, but it is not planned for tomorrow...
                               
 * Management (VLAN1) + Live Migration (VLAN2)  (3 x 1 Gb  Server 2012 R2 Team (dynamic, switch independant)
HeartBeat and CSV network on Hyper-V hosts: 1 dedicated NIC, no VLAN, no switch, directely connected NIC to NIC.

I receive a warning at the Hyper-v Cluster validation:

Validate Storage Spaces Persistent Reservation
Description: Validate that storage supports the SCSI-3 Persistent Reservation commands needed by Storage Spaces to support clustering.

Verifying there are no Persistent Reservations, or Registration keys, on Test Disk 0 from node SRV-HyperV-01.Domain.local.
Issuing Persistent Reservation REGISTER AND IGNORE EXISTING KEY using RESERVATION KEY 0x0 SERVICE ACTION RESERVATION KEY 0xa for Test Disk 0 from node SRV-HyperV-01.Domain.local.
Issuing Persistent Reservation RESERVE on Test Disk 0 from node SRV-HyperV-01.Domain.local using key 0xa.
Issuing Persistent Reservation REGISTER AND IGNORE EXISTING KEY using RESERVATION KEY 0x0 SERVICE ACTION RESERVATION KEY 0x100aa for Test Disk 0 from node SRV-HyperV-02.Domain.local.
Issuing Persistent Reservation REGISTER using RESERVATION KEY 0xa SERVICE ACTION RESERVATION KEY 0xb for Test Disk 0 from node SRV-HyperV-01.Domain.local to change the registered key while holding the reservation for the disk.
Issuing Persistent Reservation REGISTER using RESERVATION KEY 0x100aa SERVICE ACTION RESERVATION KEY 0x100bb for Test Disk 0 from node SRV-HyperV-02.Domain.local to change the registered key on node that is not holding the reservation for the disk.
Issuing Persistent Reservation REGISTER using RESERVATION KEY 0xb SERVICE ACTION RESERVATION KEY 0xb for Test Disk 0 from node SRV-HyperV-01.Domain.local to change the registered key while holding the reservation for the disk.
Issuing Persistent Reservation REGISTER using invalid RESERVATION KEY 0xc and valid SERVICE ACTION RESERVATION KEY 0xd for Test Disk 0 from node SRV-HyperV-01.Domain.local.
Successfully issued call to Persistent Reservation REGISTER using Invalid RESERVATION KEY 0xc, SERVICE ACTION RESERVATION KEY 0xd, for Test Disk 0 from node SRV-HyperV-01.Domain.local.

Verifying there are no Persistent Reservations, or Registration keys, on Test Disk 1 from node SRV-HyperV-01.Domain.local.
Issuing Persistent Reservation REGISTER AND IGNORE EXISTING KEY using RESERVATION KEY 0x0 SERVICE ACTION RESERVATION KEY 0x10000000a for Test Disk 1 from node SRV-HyperV-01.Domain.local.
Issuing Persistent Reservation RESERVE on Test Disk 1 from node SRV-HyperV-01.Domain.local using key 0x10000000a.
Issuing Persistent Reservation REGISTER AND IGNORE EXISTING KEY using RESERVATION KEY 0x0 SERVICE ACTION RESERVATION KEY 0x1000100aa for Test Disk 1 from node SRV-HyperV-02.Domain.local.
Issuing Persistent Reservation REGISTER using RESERVATION KEY 0x10000000a SERVICE ACTION RESERVATION KEY 0x10000000b for Test Disk 1 from node SRV-HyperV-01.Domain.local to change the registered key while holding the reservation for the disk.
Issuing Persistent Reservation REGISTER using RESERVATION KEY 0x1000100aa SERVICE ACTION RESERVATION KEY 0x1000100bb for Test Disk 1 from node SRV-HyperV-02.Domain.local to change the registered key on node that is not holding the reservation for the disk.
Issuing Persistent Reservation REGISTER using RESERVATION KEY 0x10000000b SERVICE ACTION RESERVATION KEY 0x10000000b for Test Disk 1 from node SRV-HyperV-01.Domain.local to change the registered key while holding the reservation for the disk.
Issuing Persistent Reservation REGISTER using invalid RESERVATION KEY 0x10000000c and valid SERVICE ACTION RESERVATION KEY 0x10000000d for Test Disk 1 from node SRV-HyperV-01.Domain.local.
Successfully issued call to Persistent Reservation REGISTER using Invalid RESERVATION KEY 0x10000000c, SERVICE ACTION RESERVATION KEY 0x10000000d, for Test Disk 1 from node SRV-HyperV-01.Domain.local.

Test Disk 0 does not support SCSI-3 Persistent Reservations commands needed by clustered storage pools that use the Storage Spaces subsystem. Some storage devices require specific firmware versions or settings to function properly with failover clusters. Contact your storage administrator or storage vendor for help with configuring the storage to function properly with failover clusters that use Storage Spaces.


Test Disk 1 does not support SCSI-3 Persistent Reservations commands needed by clustered storage pools that use the Storage Spaces subsystem. Some storage devices require specific firmware versions or settings to function properly with failover clusters. Contact your storage administrator or storage vendor for help with configuring the storage to function properly with failover clusters that use Storage Spaces.


One LUN for Quorum and another for CSV were already mounted in the Hyper-V Cluster from SCVMM.

If someone would know how to fix it, I would greatly appreciate.

Thank you in advance for your help, regards,
Member_2_7966914Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Philip ElderTechnical Architect - HA/Compute/StorageCommented:
First: iSCSI connections should not be on teamed ports. It should be MPIO across ports. VLAN the ports, put iSCSI traffic on each VLAN port, then team the default ports.

Second, is the LUN storage hooked into each node via iSCSI Initiator? I gather that to be the case.

If so, why is the validation trying to run through Storage Spaces checks? No Storage Spaces setup can be run on a remote SAN/NAS setup via iSCSI. That's why there are errors. Storage Spaces needs _direct_ access to each physical disk.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Member_2_7966914Author Commented:
Hi Philip,

Thank you for your answer!

I don't get how to VLAN NICs and team them at the same time. I am very interested in your answer about it.
What would you use to accomplish it please ?
If initiators are on a VLAN and the teams used by VSA VMs are not on the same VLAN, it would be an issue, I don't want to route traffic, or must I do?
If I put the teams on the same VLAN, I can't tagg and untagg the same VLAN on the 10 Gb switch ports.
I need more light here please.

Yes, the LUNs (Quorum and CSV) are connected on each node via iSCSI initiators.
Storage provider was added to SCVMM through SMI-S.
iSCSI groups were created, one on each host in SCVMM.
LUNs (Quorum and CSV) were not attributed and so visible by the SCVMM Hyper-V creation Wizard.
I created the Hyper-V Cluster from SCVMM, after it I had a lot of unreachable on offline disks (I think it was the direct attached volumes used by VSA VMs for storage), I removed them since they were unrepairable. Validation warnings are from after these steps. The Hyper-V Cluster seems to works quite well except that warning, but I can't put it in production like that.

I dont' want to use Storage Spaces, so I think that I can ignore this warning ?  I found this page below telling that this warning can be safely ignored if iSCSI is used, what do you think about it ?
https://www.gabrewer.com/2013/01/misleading-error-in-cluster-validation-wizard/


Thank you for your help, regards,
Member_2_7966914Author Commented:
I opened a ticket to HPE, they told me to remove MPIO for my config.

So, for the time being, I removed HP MPIO, I then received a warning for HV validation cluster, telling me that at least two paths had to be present with Multi-Path enabled.
So I removed Microsoft MPIO and there is no more warning.
I'll activate HP MPIO when we add more 10 Gb cards on servers and stack the switches.

I would be happy if someone could tell me how to VLAN NICs and team them at the same time as Philip told me to do.

Thank you in advance for your help, best regards,
Member_2_7966914Author Commented:
Sorry about this question, but nobody answered my last question.

Please, I want to accept the single comment of the only person that answered to me: Philip Elder.

Thank you
Member_2_7966914Author Commented:
Thank you
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Hyper-V

From novice to tech pro — start learning today.