Please follow the steps to disable to Disabling VAAI using the vSphere Client :
1. Open the VMware vSphere Client.
2. In the Inventory pane, select the ESXi/ESX host.
3. Click the Configuration tab.
4. Under Software, click Advanced Settings.
5. Click DataMover.
6. Change the DataMover.HardwareAcceleratedMove setting to 0.
7. Change the DataMover.HardwareAcceleratedInit setting to 0.
8. Click VMFS3.
9. Change the VMFS3.HardwareAcceleratedLocking setting to 0.
10.Click OK to save your changes.
11.Repeat this process for the all ESXi/ESX hosts connected to the storage.
Kindly go through the below more information:
Note: Please be aware of the recently published ETA 207784: “VNX: Storage Processors may restart if VMware vStorage APIs for Array Integration (VAAI) is enabled resulting in potential data unavailable”.
This ETA reports an issue that can cause SP panics on both VNX1 and VNX2, and the issue is described in clear detail within.
(TLDR?: The problem is caused by an error on ESX hosts that causes an SP to Bugcheck. If the Bugcheck were met during the Block upgrade, it could potentially lead to DU for the customer.
For example, if the SP is rebooting as part of the NDU and the condition is met on the host, the Peer SP would Bugcheck, resulting in both SPs being offline simultaneously).
2. In the Inventory pane, select the ESXi/ESX host.
3. Click the Configuration tab.
4. Under Software, click Advanced Settings.
5. Click DataMover.
6. Change the DataMover.HardwareAcceleratedMove setting to 0.
7. Change the DataMover.HardwareAcceleratedInit setting to 0.
8. Click VMFS3.
9. Change the VMFS3.HardwareAcceleratedLocking setting to 0.
10.Click OK to save your changes.
11.Repeat this process for the all ESXi/ESX hosts connected to the storage.
Kindly go through the below more information:
Note: Please be aware of the recently published ETA 207784: “VNX: Storage Processors may restart if VMware vStorage APIs for Array Integration (VAAI) is enabled resulting in potential data unavailable”.
This ETA reports an issue that can cause SP panics on both VNX1 and VNX2, and the issue is described in clear detail within.
(TLDR?: The problem is caused by an error on ESX hosts that causes an SP to Bugcheck. If the Bugcheck were met during the Block upgrade, it could potentially lead to DU for the customer.
For example, if the SP is rebooting as part of the NDU and the condition is met on the host, the Peer SP would Bugcheck, resulting in both SPs being offline simultaneously).
No comments:
Post a Comment