2V0-622 · Question #480
What two reasons can explain why a host cannot be removed from a vSphere Distributed Switch? (Choose two.)
The correct answer is A. There are virtual machine network adapters connected to the switch. D. There are VMkernel network adapters connected to the switch.. A host cannot be removed from a vSphere Distributed Switch if active network adapters - either VM NICs or VMkernel adapters - are still connected to it.
Question
What two reasons can explain why a host cannot be removed from a vSphere Distributed Switch? (Choose two.)
Options
- AThere are virtual machine network adapters connected to the switch.
- BThere are blocked ports on the switch.
- CThere are LACP LAGs configured on the switch.
- DThere are VMkernel network adapters connected to the switch.
How the community answered
(30 responses)- A80% (24)
- B7% (2)
- C13% (4)
Why each option
A host cannot be removed from a vSphere Distributed Switch if active network adapters - either VM NICs or VMkernel adapters - are still connected to it.
Virtual machine network adapters connected to the dvSwitch must be migrated or disconnected before the host can be removed, because the host still has active uplink responsibilities for those VM port groups.
Blocked ports affect traffic flow but do not constitute an active adapter assignment that would prevent host removal from the dvSwitch.
LACP LAGs define uplink teaming policies on the switch itself, not adapter-to-host bindings that would block host removal.
VMkernel adapters (used for management, vMotion, storage, etc.) are tied to dvPort groups on the distributed switch; they must be migrated to a standard switch or removed before the host can leave the dvSwitch.
Concept tested: vSphere Distributed Switch host removal prerequisites
Source: https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-networking/GUID-A15C6A57-6C56-4F10-9600-08BC8326A8C4.html
Topics
Community Discussion
No community discussion yet for this question.