Hi Eric, 

SCSI Persistent Reservations with policy-based high availability is supported in that code version so it's odd that it's showing as unsupported. 

The Broadcom article you've linked to has three criteria:

• Support SCSI-3 reservation type WEAR (i.e., write exclusive all registrant)
• Support ATS commands
• Have 512/512e sector size disks

and all of these are supported in this code version with PBHA.

Please open a support ticket so we can take a look at what's going on.

Thanks,

Chris

Chris,

Thank you for your reply. I have opened a case and will update the thread with their response.

Eric

Hi Eric, 

SCSI Persistent Reservations with policy-based high availability is supported in that code version so it's odd that it's showing as unsupported. 

The Broadcom article you've linked to has three criteria:

• Support SCSI-3 reservation type WEAR (i.e., write exclusive all registrant)
• Support ATS commands
• Have 512/512e sector size disks

and all of these are supported in this code version with PBHA.

Please open a support ticket so we can take a look at what's going on.

Thanks,

Chris

If a VMFS filesystem was in place at the volume (so already mapped and formatted) previously you update to 8.7.3.x I believe it wont update WEAR support on VMware. I would try first rebooting the hosts, if no success unmap and map back the volume, if still no Clustered VMDK support, present a new volume to check, you will see if the device supports while creating the datastore on it. 

Chris,

Thank you for your reply. I have opened a case and will update the thread with their response.

Eric

Hi Eric, 

SCSI Persistent Reservations with policy-based high availability is supported in that code version so it's odd that it's showing as unsupported. 

The Broadcom article you've linked to has three criteria:

• Support SCSI-3 reservation type WEAR (i.e., write exclusive all registrant)
• Support ATS commands
• Have 512/512e sector size disks

and all of these are supported in this code version with PBHA.

Please open a support ticket so we can take a look at what's going on.

Thanks,

Chris

Thiago,

   Thank you very much for your response. It worked. I couldn't reboot the server as it's in production, but both creating 

a new volume, and un-mapping and remapping the hosts to a current volume both worked. And yes, that was the situation that we did the code upgrade after the volumes had been created. Again, thank you very much.

Eric 

------------------------------
Eric Derr
------------------------------


Original Message:
Sent: Tue August 19, 2025 02:12 PM
From: Thiago Lucas
Subject: Policy Based HA and VmWare

If a VMFS filesystem was in place at the volume (so already mapped and formatted) previously you update to 8.7.3.x I believe it wont update WEAR support on VMware. I would try first rebooting the hosts, if no success unmap and map back the volume, if still no Clustered VMDK support, present a new volume to check, you will see if the device supports while creating the datastore on it. 

------------------------------
Thiago Lucas


Original Message:
Sent: Mon August 18, 2025 12:26 PM
From: Eric Derr
Subject: Policy Based HA and VmWare

Chris,

Thank you for your reply. I have opened a case and will update the thread with their response.

Eric

------------------------------
Eric Derr


Original Message:
Sent: Fri August 15, 2025 06:27 AM
From: Chris Bulmer
Subject: Policy Based HA and VmWare

Hi Eric, 

SCSI Persistent Reservations with policy-based high availability is supported in that code version so it's odd that it's showing as unsupported. 

The Broadcom article you've linked to has three criteria:

• Support SCSI-3 reservation type WEAR (i.e., write exclusive all registrant)
• Support ATS commands
• Have 512/512e sector size disks

and all of these are supported in this code version with PBHA.

Please open a support ticket so we can take a look at what's going on.

Thanks,

Chris

------------------------------
Chris Bulmer

Software architect, IBM Storage Virtualize