A retail bank's ACI VMM domain created port groups in vCenter, yet virtual machines on the new port group never reach the fabric. The host ports' AAEP does not include this VMM domain. What is missing?
Select an answer to reveal the explanation.
Short Explanation
vCenter got the port groups, and the leaf never got the matching hallway. You left the VMM domain off the AAEP on the host ports, so the dynamic VLAN is not programmed and the virtual machines stop at the leaf. A SAN zoneset or an HSRP group on the APIC does not attach that domain.
Full Explanation
A VMM domain lets the APIC create port groups in vCenter and allocate VLANs from the dynamic pool. Those VLANs are programmed on the leaf ports that face the hosts only when the AAEP on those ports includes the VMM domain. The bank already has the port groups, which shows the controller integration is up, and the virtual machines still fail because the host-port AAEP never received the domain. Associating the VMM domain to that AAEP is the missing piece. A SAN zoneset authorizes Fibre Channel members in a VSAN. It does not gate an ACI port group, and the virtual machines are not waiting on a VSAN. Fabric binding authorizes switch WWNs and domain IDs in a Fibre Channel fabric. vCenter is not a Fibre Channel switch, and binding it would not program an Ethernet VLAN. The APIC is the controller. It is not the default gateway for the virtual machines, and an HSRP group on the APIC is not how ACI gateways work. Caveat: the VMM domain also needs a dynamic VLAN pool with free VLANs, or the port group exists and the APIC still has no encapsulation to push. Operational check: attach the VMM domain to the AAEP used by the host ports, then confirm the leaf programs the dynamic VLAN when a virtual machine connects to the port group.