Hi
We are in the process of migrating from legacy infrastructure to ACI. We have stretched layer 2 EPGs using static bindings to the legacy infrastructure. The bridge domains are layer 2 and the gateway for the subnet is in the legacy environment(6500 switch).
Lets call this epg A. The subnet allocated to hosts in EPG A is 10.1.1.0/24. However this subnet is learnt by ACI via L3Out to the 6500 switch.
Some workloads have been migrated. The gateway for these workloads is in the ACI fabric under the bridge domain. This workload is part of epg B. The subnet associated with this epg is 10.2.2.0/24 which is configured under a bridge domain associated with EPG B.
To summarise:
-EPG-A workload IP 10.1.1.10/24 ; gateway 10.1.1.1; BD-A is layer 2, 10.1.1.0/24 learnt via L3Out-A from 6500 switch. The external epg associated with L3Out-A is EPG-C.
- EPG B workload IP 10.2.2.10/24; gateway 10.2.2.1, BD-B subnet IP 10.2.2.1.
So when workload in EPG A tries to communicate with workload in EPG B, the fabric treats this as an external epg C trying to talk to EPG B and the necessary contracts need to be applied under EPG C and EPG B.
Is this understanding correct?
Regards
Rohan
Query: If the workload in the layer 2 stretched EPG wants to communicate with another EPG that has subnet configured under
