nerdexam
Broadcom-VMware

VCP550 · Question #45

An administrator has configured hardware acceleration for a Fibre Channel storage array. After a recent maintenance event, the administrator finds that cloning and migration operations are taking exce

The correct answer is C. VMFS3.HardwareAcceleratedLocking = 0 D. Datamover.HardwareAcceleratedInit = 0. VAAI hardware acceleration can be disabled by setting specific advanced configuration parameters to 0, which turns off hardware-assisted locking and data movement operations.

Configure and Administer vSphere Storage

Question

An administrator has configured hardware acceleration for a Fibre Channel storage array. After a recent maintenance event, the administrator finds that cloning and migration operations are taking excessively long to complete. Which two settings could cause hardware acceleration to become disabled? (Choose two.)

Options

  • AVAAI Plugin Name = VMW_VAAIP_SYM
  • BVAAI Plugin Name = VMW_VAAIP_NETAPP
  • CVMFS3.HardwareAcceleratedLocking = 0
  • DDatamover.HardwareAcceleratedInit = 0

How the community answered

(21 responses)
  • A
    14% (3)
  • B
    10% (2)
  • C
    76% (16)

Why each option

VAAI hardware acceleration can be disabled by setting specific advanced configuration parameters to 0, which turns off hardware-assisted locking and data movement operations.

AVAAI Plugin Name = VMW_VAAIP_SYM

VMW_VAAIP_SYM is the VAAI plugin identifier for EMC Symmetrix arrays and is a descriptive identifier, not a configurable parameter that controls whether hardware acceleration is enabled or disabled.

BVAAI Plugin Name = VMW_VAAIP_NETAPP

VMW_VAAIP_NETAPP is the VAAI plugin identifier for NetApp storage arrays and serves only as a plugin name label, not an advanced host parameter that can be toggled to disable hardware acceleration.

CVMFS3.HardwareAcceleratedLocking = 0Correct

VMFS3.HardwareAcceleratedLocking controls the Atomic Test and Set (ATS) VAAI primitive, which replaces SCSI reservations for file locking on VMFS datastores; setting it to 0 disables this hardware acceleration feature and causes slower locking operations. This directly impacts cloning and migration performance because those operations require frequent locking of VMFS metadata.

DDatamover.HardwareAcceleratedInit = 0Correct

DataMover.HardwareAcceleratedInit controls the Write Same VAAI primitive used for zeroing out disk blocks during cloning and initialization; setting it to 0 forces the ESXi host to perform these operations in software rather than offloading them to the array. This dramatically slows cloning and migration tasks because the host CPU must handle block zeroing that the array would otherwise handle natively.

Concept tested: VAAI hardware acceleration advanced configuration parameters

Topics

#VAAI#hardware acceleration#Fibre Channel#advanced host settings

Community Discussion

No community discussion yet for this question.

Full VCP550 Practice