Objectives
The simulator ticks each one as soon as the network meets it.
show faults names what is missing. Create VLAN pool POOL1 with encap-block 10 300.
Create physical domain PHYS1 using POOL1.
Create AEP AEP1 attached to PHYS1, and policy group HOSTS using AEP1.
Give leaf 101 port 1/3 and leaf 102 port 1/3 the policy group HOSTS.
show faults: no faults. Ping PC2 (192.168.10.20) from PC1.
Before you start
This looks like a lot for one VLAN, but it separates jobs: a network team says which VLANs may exist where, and a tenant only picks an EPG and a VLAN inside that limit. A VLAN outside the pool gives a fault that names the pool.
Concept
ACI: the physical domain chain
A VLAN works on a port only if a chain of policies allows it. The EPG names a physical domain, the domain names a VLAN pool that holds the VLAN, and the port’s policy group names an AEP attached to that domain. A break anywhere raises a fault that names it. A classic switch joins through this chain, on a port or a vPC.
Concept
Physical domains: joining classic switches to a fabric
Most fabrics must reach racks that know nothing about VXLAN: classic switches and bare-metal servers on tagged VLANs. The fabric treats that network as a physical domain. A leaf pair presents one LACP partner, carries the tagged VLANs on a trunk, and maps each VLAN to a VNI, so a host on a classic switch reaches a host anywhere in the fabric. Only VLANs that are mapped cross, and each stays separate.
