Multipod with IPN in global table

[David Yang]

I understand Multipod IPN should a dedicated network or in a VRF. However customer has a Multipod implementation with IPN in the global table because of some technical issues with the DCI link capability. It hasn't had any issue until the regular L3Out for user tenant was brought up. It appeared that the both Multipod L3Out and regular L3Out started advertising TEP Pool IP's, IPN subnets and regular BD subnets and caused routing loops between ACI, IPN and legacy networks.

• Is Multipod via non-dedicated or non-VRF IPN a supported implementation?
• Is it the expected behavior that ACI advertises TEP pool and regular BD subnets through Multipod L3Out and regular L3Out which seemed strange?

Any advice is much appreciated.

Thanks,

David

[micgarc2]

Using a dedicated VRF is a best practice and makes the deployment a little cleaner. VRF separation can ensure the routing table is isolated for inter-fabric traffic and there is no unwanted traffic exposed to ACI since the underlay (overlay-1) of ACI is exposed to the IPN.