Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Search instead for
Did you mean:
Per Port VLAN
Customer needs to use the same VLAN for two different EPGs? Encap already in use fault? PPV is for you!
Seperate VLAN pool for VLANs to be duplicated (namespace)
EPGs need to have unique BD (can be same VRF or different)
Interface Policy Group needs to have L2 Interface policy for Port Local scope
Configure Unique(different) VLAN pools with the same encap inside
Enable port local scope for the Interface Policy Group for the existing interface already using the VLAN
Under the Tenant, create a new BD and EPG for the VLAN.
The output below from ELTMC shows two sets of BD/EPG. the FD_VLAN for 373 is shown twice but its important to note the Fabric_encap is unique. This fabric_encap is generated based on the VLAN pool/namespace. Thats why its required to have a unique VLAN pool, so that the fabric_encap VXLAN/vnid is unique.
Note: BD1/EPG1 has encap vlan-373 and uniquely identified in the fabric as BD-16416668/EPG-9809. BD2/EPG2 has encap vlan-373 again BUT the fabric_encap for the BD/EPG is different than before BD-16416668/EPG-10592
Also interesting to note is the HW column. This shows the front panel ASIC VLAN and how it is translated uniquely.
With the output above we queried ELTMC again but this time for information on how the interface is programmed. Highlighted we see the scope field is set to local. This allows the front panel ASIC to have extra translations as well as have ACI classify traffic with (vlan, port)
The moquery below for the concrete vlan "vlanCktEp" and filtered by "encap==vlan-373" shows two objects on that particular leaf. Highlighted are the duplicated encap vlan and unique DN and EPG DN as well