InfoScale support for VMware vSphere and vSAN datastore with SCSI-3 enabled VMDK disks—VMware vSphere 7.0 and vSAN 6.7 U3/7.0

Article: 100048628
Last Published: 2020-10-21
Ratings: 5 2
Product(s): InfoScale & Storage Foundation

Description

VMware announced the General Availability of vSphere 7 on March 10th, 2020 and Veritas InfoScale is committed to provide support for the VMware major and update releases.

To support VMware vSphere 7 with Veritas InfoScale 7.4.2, several scenarios were tested along with the traditionally supported use-cases. The following table describes the qualification scenarios and the test results for these scenarios.

Use-cases supported with InfoScale 7.4.2

Qualification scenario Qualification test results (success)
Install and configure InfoScale Guest cluster Successfully installed and configured InfoScale Enterprise using Common Product Installer (CPI)
Export VMDKs with MWF/RDM-P to all 3 Guests in sharing mode Successfully configured VMDKs on VMFS datastore or RDM-P mapping files stored on VMFS datastore
Configure disk based NON SCSI3-PR server-based fencing using VMDKs with MWF or Disk-based SCSI-3 fencing using RDM-P disks Successfully configured fencing using Common Product Installer (CPI)
Configure VCS VMwareDisk agent to provide HA for VMDK or RDM-P disks assigned to a single VM in the InfoScale cluster Successfully configured VCS VMwareDisk agent using VCS Application Configuration Wizard along with Application agent, for example, Oracle
Install and configure of Oracle database on CFS and VxFS mounts Successfully installed and configured application-based HA for the Oracle database
Configure VCS agent for Oracle with the fast failover option Successfully configured VCS agent for Oracle with fast failover option to reduce the time required for failover and failback
Fail over and fail back of Oracle service group using the VCS agent Successfully tested failover and failback of VCS agent for Oracle service while database workload is running
Simulate network split-brain Successfully simulated the VCS cluster failure scenario by disabling LLT (cluster interconnects) and checking whether the database service fails over to an available node
Virtual machine live migration (host vMotion operations) Successfully performed live migration of a virtual machine that is a part of an InfoScale cluster and verified that no failure occurred in the cluster
ESXi hypervisor node failure Successfully configured VMware HA and tested the hypervisor node failure scenario; verified that the hosted virtual machine comes online on another hypervisor node, the VMDK disks are available and the virtual machine joins the InfoScale cluster

 

VMware also added support for SCSI-3 Persistent Reservations (SCSI-3 PR) on VMFS datastore. For details, refer to the article at: https://core.vmware.com/resource/vsphere-7-rdm-shared-vmdk-migration/#sec1-sub2.

Additionally, SCSI-3 support was introduced in vSAN datastore with vSAN 6.7 U3. For details, refer to the article at: https://blogs.vmware.com/virtualblocks/2019/08/23/vsan67-u3-wsfc-shared-disksupport/.

After the VMware announcement, Veritas carried out the qualification process for these capabilities with InfoScale. It was observed that the key SCSI3-PGR functionality used by InfoScale is not supported by VMware in the current versions. Hence, currently, InfoScale does not support the use of the SCSI3-PGR-based functionality for VMDKs.

The following table lists the scenarios where the roadblocks were observed.

Use-cases not supported with InfoScale 7.4.2

Qualification scenario Qualification test results (roadblocks)

Configure SCSI-3 disk-based fencing using VMDK disks on VMFS 6.0 datastores on vSphere 7.0

(Clustered VMDK support)

Using the vxfentsthdw utility, verified that a VMDK disk is supported for a fencing configuration.

The following errors was encountered:

Write to disk /dev/vx/rdmp/node1_vmdk0_29 from node node1 ... Failed.

The OS native SCSI-3 commands also failed on such VMDK disks with the following error:

Node1:/root>sg_persist --out --preempt-abort --param-rk=456abc --param-sark=123abc --prout-type=5 /dev/sdk
VMware    Virtual disk  2.0
Peripheral device type: disk
PR out: bad field in cdb including unsupported service action

This issue is being tracked with VMware through the DCPN Engineering request 00068904.

Configure SCSI-3 disk-based fencing using VMDK disks on vSAN 6.7 U3 and later datastores

Using the vxfentsthdw utility, verified that a VMDK disk is supported for a fencing configuration.

The following error was encountered:

Write to disk /dev/vx/rdmp/node1_vmdk0 from node node1 ... Failed.

The OS native SCSI-3 commands also failed on such VMDK disks with the following error:

Node1:/root>sg_persist --out --preempt-abort --param-rk=456abc --param-sark=123abc --prout-type=5 /dev/sdk
VMware    Virtual disk      2.0
Peripheral device type: disk
PR out: bad field in cdb including unsupported service action

This issue is being tracked with VMware through the DCPN Engineering request 00068904.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


 

 

 

 

Veritas is working with VMware to get a resolution for these defects and to announce the relevant support after another qualification cycle.

Reference: Veritas InfoScale 7.4.2 Virtualization Guide - Linux on ESXi

Was this content helpful?