A consultant successfully completes a Foundation using a flat switch. The consultant then works with the customer to move the cluster over to their production network. After the move, the CVMs and hypervisors can no longer communicate, which prevents the cluster from starting. Which option should be used to resolve this issue?

After Foundation, the hypervisor and CVM network interfaces are configured to send untagged traffic. When these nodes are connected to a production switch that uses VLANs, the switch ports must be configured to handle this. The standard practice is to set the VLAN intended for the CVMs and hypervisors as the "native" (or untagged) VLAN on the corresponding switch ports. This tells the switch to accept untagged frames from the node and place them on the correct VLAN, establishing L2 communication.

A. The problem is CVM-hypervisor communication on the primary network, not IPMI connectivity to the gateway.
B. The IPMI is on a separate network. VLAN tagging is configured on the hypervisor's virtual switch, not manually on the CVM.
C. The issue is a Layer 2 VLAN configuration mismatch, not a lack of IPv6 or DHCP, which operate at Layer 3.

1. Nutanix AHV Best Practices Guide v2.6, Section: "Physical Network Design", Subsection: "VLAN Configuration". "Nutanix recommends that you configure the native VLAN of the physical switch ports connected to the AHV hosts as the VLAN for the CVMs and AHV hosts."

2. Nutanix Field Installation Guide v5.3, Chapter: "Preparing for Imaging", Section: "Network Requirements". The guide details how initial flat network imaging leads to untagged traffic, which must be reconciled with the production network's VLAN scheme post-installation.