A bank builds an ACI VLAN pool, a physical domain, and an AAEP that references the domain. An interface profile selects the right leaf ports and the right policy group. No switch profile references that interface profile. The leaf never programs the VLAN. Why?
Select an answer to reveal the explanation.
Short Explanation
You wrote the desk procedure and never told the branch it exists. The interface profile holds the port selectors. A switch profile is what binds that interface profile to the leaf node, and without it the leaf never receives the access policy.
Full Explanation
ACI access policy reaches a leaf only when a switch profile selects the node and references the interface profile. The bank built the VLAN pool, the physical domain, the AAEP, and the interface profile, and skipped the switch profile, so the leaf has nothing deployed and the VLAN stays off the port. The infrastructure VLAN is for fabric discovery. It does not belong in the AAEP as a substitute for a switch profile. A VMM domain pushes port groups for a hypervisor. A physical access port does not need one before its access policy can deploy. Hardware proxy is how a bridge domain forwards unknown unicast. It does not decide whether an access VLAN is programmed on a leaf port. Caveat: the switch profile has to select this leaf's node ID. A switch profile aimed at a different leaf deploys the ports in the wrong place. Operational check: attach the interface profile to a switch profile that includes this leaf, then confirm the port programs the VLAN. The policy group and the AAEP can be perfect and still never reach the leaf. The switch profile is the missing hop in this chain, not a replacement for them.