2V0-621 · Question #142
An administrator is experiencing network connectivity issues between virtual machines. The virtual machines and hosts are configured as follows: - VM1 is running on Host1 - VM2 is running on Host2…
The correct answer is A. VLANs of the physical NICs B. Failover order of the uplinks C. Virtual NIC connectivity to the dvSwitch. Troubleshooting inter-VM connectivity on a vSphere Distributed Switch requires checking that VLAN tags are consistent end-to-end, that uplink failover order is correct, and that each VM's vNIC is actually connected to the dvSwitch.
Question
An administrator is experiencing network connectivity issues between virtual machines. The virtual machines and hosts are configured as follows:
- VM1 is running on Host1
- VM2 is running on Host2
- Both Host1 and Host2 are attached to the vSphere Distributed Switch
dvSwitch1
- Both Host1 and Host2 are using vmnic0 and vmnic1 on dvSwitch1
- Both virtual machines are using the default portgroup for network
traffic What are three settings the administrator should investigate while troubleshooting the connectivity issue? (Choose three.)
Options
- AVLANs of the physical NICs
- BFailover order of the uplinks
- CVirtual NIC connectivity to the dvSwitch
- DSecurity policy of the portgroup
- ETraffic shaping on the portgroup
How the community answered
(32 responses)- A63% (20)
- D13% (4)
- E25% (8)
Why each option
Troubleshooting inter-VM connectivity on a vSphere Distributed Switch requires checking that VLAN tags are consistent end-to-end, that uplink failover order is correct, and that each VM's vNIC is actually connected to the dvSwitch.
VLAN mismatches between the dvPortgroup and the upstream physical switch trunks are a common cause of inter-host connectivity failure, because frames will be tagged or untagged incorrectly at the physical boundary.
An incorrect failover order can route traffic through an uplink that is not carrying the required VLAN or is not properly cabled, silently breaking connectivity between hosts.
If a VM's vNIC is disconnected from the dvSwitch or assigned to the wrong dvPortgroup, it will not be able to communicate even if all other settings are correct.
Security policy settings such as promiscuous mode or MAC address changes affect frame visibility and spoofing protection but do not typically block basic unicast connectivity between two VMs on the same portgroup.
Traffic shaping controls bandwidth allocation and burst limits; it does not block or drop connectivity and would not explain a complete network connectivity failure.
Concept tested: vSphere Distributed Switch connectivity troubleshooting
Source: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.networking.doc/GUID-E0BDC976-2A1E-4F09-B6E7-A6A5ED79B65B.html
Topics
Community Discussion
No community discussion yet for this question.