Home » VMware » 2V0-621 v.2 » What action should the administrator take next?
An ESXi 6.x host in the vCenter Server inventory has disconnected due to an All Paths Down (APD) situation. An administrator has corrected the APD issue on the host, but it still remains disconnected.
What action should the administrator take next?
A. Select Restart Management Agents from the DCUI.
B. Execute esxcli system settings advanced set -d /Scsi/FailVMIOonAPD.
C. Modify the advanced parameter /Disk/ApdTokenRetryCount.
D. Enable the advanced parameter /Misc/APDHandlingEnable.
Correct Answer: A
Explanation/Reference:
Explanation: All-Paths-Down (APD)
A datastore is shown as unavailable in the Storage view
A storage adapter indicates the Operational State of the device as Dead or Error
All paths to the device are marked as Dead
You are unable to connect directly to the ESXi host using the vSphere Client The ESXi host shows as Disconnected in vCenter Server In the /var/log/vmkernel.log file, you see entries similar to:
cpu1:2049)WARNING: NMP: nmp_IssueCommandToDevice:2954:I/O could not be issued to device "naa.60a98000572d54724a34642d71325763" due to Not
found cpu1:2049)WARNING: NMP: nmp_DeviceRetryCommand:133:Device "naa.60a98000572d54724a34642d71325763": awaiting fast path state update for failover with I/O blocked. No prior reservation exists on the device. cpu1:2049)WARNING: NMP: nmp_DeviceStartLoop:721:NMP Device
"naa.60a98000572d54724a34642d71325763" is blocked. Not starting I/O from device. cpu1:2642)WARNING: NMP: nmpDeviceAttemptFailover:599:Retry world failover device "naa.60a98000572d54724a34642d71325763" – issuing command 0x4124007ba7c0 cpu1:2642)WARNING: NMP: nmpDeviceAttemptFailover:658:Retry world failover device "naa.60a98000572d54724a34642d71325763" – failed to issue command due to Not found (APD), try again… cpu1:2642)WARNING: NMP: nmpDeviceAttemptFailover:708:Logical device "naa.60a98000572d54724a34642d71325763":
awaiting fast path state update… cpu0:2642)WARNING: NMP: nmpDeviceAttemptFailover:599:Retry world failover device
"naa.60a98000572d54724a34642d71325763" – issuing command 0x4124007ba7c0 cpu0:2642)WARNING: NMP: nmpDeviceAttemptFailover:658:Retry world failover device "naa.60a98000572d54724a34642d71325763" – failed to issue command due to Not found (APD), try again… cpu0:2642)WARNING: NMP: nmpDeviceAttemptFailover:708:Logical device "naa.60a98000572d54724a34642d71325763": awaiting fast path state update…
A restart of the management agents may show these errors:
Not all VMFS volumes were updated; the error encountered was ‘No connection’. Errors:
Rescan complete, however some dead paths were not removed because they were in use by the system. Please use the ‘storage core device world list’ command to see the VMkernel worlds still using these paths.
Error while scanning interfaces, unable to continue. Error was Not all VMFS volumes were updated; the error encountered was ‘No connection’.
You may also see that the device is no longer listed:
cpu17:10107)WARNING: Vol3: 1717: Failed to refresh FS 4beb089b-68037158-2ecc-00215eda1af6 descriptor: Device is permanently unavailable cpu17:10107)
ScsiDeviceIO: 2316: Cmd(0x412442939bc0) 0x28, CmdSN 0x367bb6 from world 10107 to dev "eui.00173800084f0005" failed H:0x1 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0. cpu17:10107)Vol3: 1767: Error refreshing PB resMeta: Device is permanently unavailable
Reference: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2004684