Refer to the Exhibit. An administrator is configuring an ESXi 6.x host to use multiple NICs to resolve a management network redundancy error. After configuring a second NIC, the server is not able to communicate when the primary connection is taken down. The administrator analyzes the Exhibit shown here. Based on the exhibit, what is the likely cause of the issue?

Question

Accepted Answer

B. vmnic2 is not connected to a physical switch. vmnic2 may be configured as an active or standby uplink on the vSwitch, but if it is not physically connected to a port on a physical switch, it will have no viable network path. When the primary NIC is taken down, ESXi attempts to fail over to vmnic2, but because there is no physical link, traffic cannot traverse the network and communication fails.

Answer

A. vmnic4 is not attached to a vSwitch. vmnic4 not being attached to a vSwitch would make it an unused adapter with no role in the management network configuration, so it would not cause the described failover failure.

Answer

C. E1000 is the incorrect NIC Driver for this card. The E1000 is a standard, well-supported NIC driver in ESXi environments and would not specifically cause failover to fail when only the primary uplink is disabled.

Answer

D. There is a MAC address conflict on the network. A MAC address conflict would cause erratic or intermittent connectivity across both active and standby paths, not a clean failure that occurs only when the primary NIC is taken offline.

Refer to the Exhibit. An administrator is configuring an ESXi 6.x host to use multiple NICs to resolve a management network redundancy error. After configuring a second NIC, the server is not able…

Question

Exhibit

Options

How the community answered

Why each option

Topics

Community Discussion