nerdexam
Broadcom-VMware

VCP550 · Question #90

A number of virtual machines in a vSphere 5.5 DRS cluster are connected to the same virtual switch port group. After several of these VMs are migrated to another host, an administrator notices that th

The correct answer is D. The virtual switch port allocation was changed from the default setting.. Virtual machines lose network connectivity after DRS migration because the destination host's virtual switch ran out of ports. This happens when the port allocation mode was changed from elastic (default) to a fixed count too low to accommodate migrated VMs.

Configure and Administer vSphere Networking

Question

A number of virtual machines in a vSphere 5.5 DRS cluster are connected to the same virtual switch port group. After several of these VMs are migrated to another host, an administrator notices that they have lost network connectivity. The Events tab in vCenter Server shows this error message:

Failed to initialize ethernet0. The vmkernel log file on the host running the affected VMs contains this message:

Can't connect device:'port group name': Out of resources. Which caused this issue?

Options

  • ANetwork I/O Control was enabled.
  • BThe DRS cluster containing the VMs was set to Fully Automated with the Migration Threshold set
  • CThere were insufficient uplinks configured on the virtual switches.
  • DThe virtual switch port allocation was changed from the default setting.

How the community answered

(55 responses)
  • A
    5% (3)
  • B
    9% (5)
  • C
    24% (13)
  • D
    62% (34)

Why each option

Virtual machines lose network connectivity after DRS migration because the destination host's virtual switch ran out of ports. This happens when the port allocation mode was changed from elastic (default) to a fixed count too low to accommodate migrated VMs.

ANetwork I/O Control was enabled.

Network I/O Control manages bandwidth allocation and traffic shaping but does not limit the number of ports available on a virtual switch, so it would not produce an 'Out of resources' port exhaustion error.

BThe DRS cluster containing the VMs was set to Fully Automated with the Migration Threshold set

DRS automation level and migration threshold control when migrations are triggered, not port capacity on the destination host's virtual switch - changing this setting would not cause port exhaustion.

CThere were insufficient uplinks configured on the virtual switches.

Insufficient uplinks would reduce available bandwidth and potentially cause packet loss or failover events, but would not produce the 'Out of resources' port count exhaustion error seen in the vmkernel log.

DThe virtual switch port allocation was changed from the default setting.Correct

In vSphere 5.5, the default virtual switch port allocation is elastic, meaning ports are created on demand. If an administrator changed the allocation to a fixed number that is lower than the total number of virtual machine NICs that need to connect post-migration, the switch exhausts its available ports and the vmkernel logs 'Out of resources', preventing the vNIC from connecting to the port group.

Concept tested: vSphere virtual switch port allocation and resource exhaustion

Source: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.networking.doc/GUID-7B5F3B6C-5A8F-4B4A-9F8B-2E3D1F4C5B6A.html

Topics

#virtual switch ports#port group#DRS migration#network resource exhaustion

Community Discussion

No community discussion yet for this question.

Full VCP550 Practice