VMware Cloud Community
TylerDurden77
Enthusiast
Enthusiast
Jump to solution

Windows 2016 failover cluster on ESXi 6.0

Hi,

I'm trying to setup a new windows 2016 failover cluster but when I validate my cluster i get some errors/warnings.

ESXi 6.0u2

RDMs (3par 7000)

Windows 2016 VMs

Error/Warning message :

List Disks To Be Validated

Physical disk {704dbde3-bc68-4c46-a49a-d428c2ef58cd} does not have the inquiry data (SCSI page 83h VPD descriptor) that is required by failover clustering.

Really don't understand what this means... right now I have only exported the Quorom disk to my VMs.

Except for the error message everything seems to be fine..

Any advise?  Is this something I can ignore and continue to export RDMs to my newly created failover cluster?

Cheers

Tyler

0 Kudos
1 Solution

Accepted Solutions
rcporto
Leadership
Leadership
Jump to solution

Unless I'm missing something, the error message you're getting on the second local disk, not on third disk (the shared disk), so you can ignore that message, since the tests with the shared disk passed without problems.

---

Richardson Porto
Senior Infrastructure Specialist
LinkedIn: http://linkedin.com/in/richardsonporto

View solution in original post

0 Kudos
6 Replies
SureshKumarMuth
Commander
Commander
Jump to solution

Hi,

VPD is the meta data which is located on every lun containing information about the lun, since the vpd data is missing, the cluster setup is failing.

Please check if the following articles help

validation fails on server 2012 cluster using one of the servers as an iscsi target

https://www.experts-exchange.com/questions/28657974/Windows-Server-2012-wont-create-a-failover-clust...

Regards,

Suresh

Regards,
Suresh
https://vconnectit.wordpress.com/
0 Kudos
TylerDurden77
Enthusiast
Enthusiast
Jump to solution

Hi,

Thanks for your swift reply.

Both your URLs seems to have to do with iSCSI.

My environment is FC. Still SCSI...

Have several virtual WFC up and running (Windows 2012)  but this is the first windows 2016 Failover Cluster.

Don't understand why it should be any different though Smiley Sad

Regards

Tyler

0 Kudos
rcporto
Leadership
Leadership
Jump to solution

Unless I'm missing something, the error message you're getting on the second local disk, not on third disk (the shared disk), so you can ignore that message, since the tests with the shared disk passed without problems.

---

Richardson Porto
Senior Infrastructure Specialist
LinkedIn: http://linkedin.com/in/richardsonporto
0 Kudos
TylerDurden77
Enthusiast
Enthusiast
Jump to solution

Thank you Richardson!

I have to learn to check the reports in a better way.... Smiley Happy

Regards

Tyler

0 Kudos
maheshvk
Contributor
Contributor
Jump to solution

Hi,

I got the same error while configuring the cluster. In the test report, it was showing the disk number and disk signature. I did disk reset from the disk management to change the disk signature.

That resolved the problem. !!

0 Kudos
ChrisHagan
Contributor
Contributor
Jump to solution

Can you give us more detail on how you reset your disk signatures ("disk reset from the disk management")?  I don't see that option in Windows Disk Manager

Thanks

0 Kudos