01-30-2025 05:59 PM
Hello,
I have an external switch connected to a leaf switch using a port channel. The port channel carried Vlan 100,200,300. I have EPGs 100,200 and 300 and tried statically mapping the port channel to each EPG, but is fails saying the port channel already has an encapsulation defined.
how do I make sure that traffic from any of these vlans are assigned the correct EPG, when entering the fabric via the port channel?
Solved! Go to Solution.
01-30-2025 10:21 PM
Hello @suya2024
For the visual understanding of your query; here is the diagram:
And here is a brief explanation:
And the Solution:
Hope This Helps!!!
AshSe
Forum Tips:
01-31-2025 01:31 AM - edited 01-31-2025 01:31 AM
Hi @suya2024 ,
The exact error message would help, plus a little more about your existing configuration.
However, with some guessing, I'm going to suggest you do this:
Go to one of the EPG's Configured Access Policies - let's say the VLAN 100 EPG (From your Tenant - Application Profiles > Your_Application_Profile > Application EPGs > Your_EPG |> [Operational] tab > Configured Access Policies
Now hover over the VLAN Pool column to see the name of the VLAN Pool - in my lab it's called T06:MappedVLANS_VLAN.Pool
Now make sure VLAN 100 is in that pool- using my example of T06:MappedVLANS_VLAN.Pool, navigate to Fabric > Access Policies >> Pools > VLAN > T06:MappedVLANS_VLAN.Pool and add an Encap Block for VLAN 100
Now try mapping the port-channel to the EPG again From your Tenant - Application Profiles > Your_Application_Profile > Application EPGs > Your_EPG > Static Ports >+ Deploy Static EPG on PC, VPC or Interface
Let me know if this gets you out of trouble - if now, a bit more detail would help
01-31-2025 08:37 AM
We do it all the time, basically extending L2 VLAN(s) from NXOS to ACI over a VPC_IPG. We use the same design as AshSe's diagram except our NXOS switch is VPC to leaf 101 and 102. You need to have VLAN(s) defined as static in your vlan pool and static port need to be in trunk mode.
VLAN_POOL, static, VLANs 100 ,200, 300
EPG_V100, static port VPC_IPG, vlan 100, trunk
EPG_V200, static port VPC_IPG, vlan 200, trunk
EPG_V300, static port VPC_IPG, vlan 300, trunk
01-30-2025 10:21 PM
Hello @suya2024
For the visual understanding of your query; here is the diagram:
And here is a brief explanation:
And the Solution:
Hope This Helps!!!
AshSe
Forum Tips:
01-31-2025 05:02 AM
Hello Ashse
Thank you for your detailed response, I have the setup you described, only difference is that my vlans are static and not dynamic. The PC is been mapped to EPGs with unique and not overlapping VLANs. This is the specific error i get
Error: 400 - Validation failed: Port: topology/pod-1/paths-1000/pathep-[AGGSWITCH-PC] has more than 1 native encap. So i mapped AGGSWITCH-PC to EPG100 with encap vlan 100. When i try to map AGGSWITCH-PC to EPG200 with encap vlan 200, i get that error.
01-31-2025 01:31 AM - edited 01-31-2025 01:31 AM
Hi @suya2024 ,
The exact error message would help, plus a little more about your existing configuration.
However, with some guessing, I'm going to suggest you do this:
Go to one of the EPG's Configured Access Policies - let's say the VLAN 100 EPG (From your Tenant - Application Profiles > Your_Application_Profile > Application EPGs > Your_EPG |> [Operational] tab > Configured Access Policies
Now hover over the VLAN Pool column to see the name of the VLAN Pool - in my lab it's called T06:MappedVLANS_VLAN.Pool
Now make sure VLAN 100 is in that pool- using my example of T06:MappedVLANS_VLAN.Pool, navigate to Fabric > Access Policies >> Pools > VLAN > T06:MappedVLANS_VLAN.Pool and add an Encap Block for VLAN 100
Now try mapping the port-channel to the EPG again From your Tenant - Application Profiles > Your_Application_Profile > Application EPGs > Your_EPG > Static Ports >+ Deploy Static EPG on PC, VPC or Interface
Let me know if this gets you out of trouble - if now, a bit more detail would help
01-31-2025 05:08 AM
Hey Chris,
Thanks for the response, the VLANs are in the vlan pool and here is the exact error
Error: 400 - Validation failed: Port: topology/pod-1/paths-1000/pathep-[AGGSWITCH-PC] has more than 1 native encap.
So i mapped AGGSWITCH-PC to EPG100 with encap vlan 100. When i try to map AGGSWITCH-PC to EPG200 with encap vlan 200, i get that error. vlan 100 and 200 are in the vlan pool, associated with the phydom, tied to the aep, assigned to the port channel group.
01-31-2025 07:48 AM
I think what i am attempting is not allowed in ACI. You cannot directly map a single port channel to multiple EPGs using different vlan encapsulation. Can someone confirm this. Thanks
01-31-2025 08:37 AM
We do it all the time, basically extending L2 VLAN(s) from NXOS to ACI over a VPC_IPG. We use the same design as AshSe's diagram except our NXOS switch is VPC to leaf 101 and 102. You need to have VLAN(s) defined as static in your vlan pool and static port need to be in trunk mode.
VLAN_POOL, static, VLANs 100 ,200, 300
EPG_V100, static port VPC_IPG, vlan 100, trunk
EPG_V200, static port VPC_IPG, vlan 200, trunk
EPG_V300, static port VPC_IPG, vlan 300, trunk
01-31-2025 09:09 AM
Thanks YanL, i have done this myself in the past, but surprised i was running into this problem. The issue was i was selecting Trunk (Native) and not Trunk. This allowed me to map the PC to multiple EPGs with different encaps
01-31-2025 11:51 AM
Ah ha! Yes - if you'd have put the error message in the original post, I'd have told you that that was the problem! Glad you got it all worked out while I slept!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide