A national retailer created a VLAN pool and a physical domain and attached that domain to an EPG. A leaf access port still does not encapsulate the VLAN. The port's policy group uses an AAEP that does not include this domain. What should be linked?
Select an answer to reveal the explanation.
Short Explanation
The AAEP is the clip that holds a domain onto a port. You built the VLAN pool and the physical domain, then left them off the AAEP this port's policy group uses, so the leaf never programs the VLAN. A leaf-to-leaf cable or a VRF preferred group does not make that clip.
Full Explanation
ACI access policy chains a VLAN pool to a physical domain, the domain to an attachable access entity profile, and that AAEP to the interface policy group on the switch port. The EPG can reference the domain and still have no encapsulation on the wire when the AAEP used by the port does not include the domain. Associating the physical domain to that AAEP is the missing link that lets the policy group program the VLAN. A leaf-to-leaf cable is not an access-policy object, and a standard fabric does not use it to deploy host VLANs. Preferred group permits communication among member EPGs inside a VRF. It does not attach a domain to a port and it does not program a VLAN pool onto an interface. OSPF on the spine is an underlay or route-peering choice elsewhere. The area number does not select the encapsulation on an ACI access port. Caveat: the EPG still needs a static path, or a VMM binding, that uses this VLAN and this port, or the access policy can be complete and the endpoint still has no path. Operational check: add the domain to the AAEP, deploy the access policies, and confirm the leaf interface shows the VLAN from the pool.