Bare metal and VMM same EPG

[ericgregg]

Current environment contains a VMM domain with a VLAN pool that dynamically allocates VLANs in the range of 1501-1515.  The VMM is associated to an EPG name WKS and allocated vlan 1506 for the EPG.  My bare metal/physical domain has a VLAN pool of 100-200 and is set to static allocation.  When I add the physical domain to the WKS EPG the servers can only communicate with the BD SVI and not nodes in the VMM domain.  When I look at the client end-points under the operations tab on the EPG I see both end-points are marked with different VLANs which makes sense due to the VLAN pools.  I was told by the TAC DO NOT overlap VLANs in pools between physical and VMM.  If that is in fact the case, how do I get the two domains to communicate in the same EPG, or do I have to create separate EPGs?

[Rick1776]

Make sure that the Intra EPG Isolation is not enabled.


Please see this link for details.

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/aci/apic/sw/2-x/L2_config/b_Cisco_APIC_Layer_2_Configuration_Guide/b_Cisco_APIC_Layer_2_Configuration_Guide_chapter_011.html

[ericgregg]

The EPGs are set to Intra EPG isolation : unenforced. 

[Rick1776]

Hmm, they should be able to talk to one another.

To your point I would create two separate EGP's groups one for VMM and the other for the Bare Metal and then create a contract between them to communicate.

[ericgregg]

Tried that and still doesn't work....  I have all of these EPG's pointed back to a single BD with a single subnet.  I broke it out further and added an additional VMM EPG.  Two different endpoints in the same VMM domain in different EPG's can communicate with each other.  I did validate the contract is IP any/any.  thoughts?

[ericgregg · Accepted solution]

problem resolved...  blew away the entire APP profile and rebuilt from scratch.  I can only assume that I missed a setting the first time around.  Thanks for the input tho!

[Rick1776]

Thanks for sharing. Glad it's working