Default Route Shared L3 Out

[Jv]

Hi Team,

After going through different Shared L3 Out document. I am confused now.

Fabric is running with Version: 1.3(2i). we have one tenant and default L3 out is configured for same. Now we have another tenant for which L3 out to be configured. and i version 1.3 support Shared L3 out.

Deployment scenario as below :-

Tanent1 - VRF - BD - EGP

Tanent2 - VRF - BD - EPG

We know in general networking scenario You cannot configure two static routes to advertise each prefix between the VRFs, because this method is not supported

How best i can use shared L3 out in my scenario.

Your suggestions will be highly appricated.

Thanks in advance

Jv

[micgarc2]

Hi,

Can you please clarify what you are trying to accomplish? A shared L3 out will allow an L3 out and EPG to do cross VRF communication. From your description it seems you have two L3 outs (one in each tenant) that you want to configure both in their own VRF. If this is the case are you trying to advertise routing information from one routing domain to another through the fabric that are in different VRFs? If so this would actually be inter-VRF transit routing between two L3 outs. If this is the case this feature is not supported until APIC release 2.2(2e). If you could please clarify this, I can better assist you.

Thanks!

Michael G.

[Jv]

Hi Michael,

Thanks for reply.

As mentioned earlier we have

Tanent1 - VRF - BD - EGP (Tanent 1 has 10.1.x.x/16 subnet dedicated )

Tanent2 - VRF - BD - EPG (Tanent 1 has 10.2.x.x/16 subnet dedicated )

My topology looks like below -

we want shared L3-out among tenants But between Tenants no communication should be there.

Note :- 

At present L3 out is configured in one tenant, with default route pointing to catalyst L3 switch(acc to HLD pic. Shared ) and reverser route from catalyst to LEAF switch is configured on it.

Hope i am able to explain my requirement.

Kindly suggest.

Regards,

Jv

[micgarc2]

"We want shared L3-out among tenants But between Tenants no communication should be there."

Well the point of a shared l3 out is to have one tenant shared its services (l3 out) with other tenants. You can create your shared l3 out and apply a global contract in between your L3 out and the EPGs in other tenants you want to be able to use this L3 out. If no contract is present no EPGs within the other tenants will be able to use that L3 out. 

Let me know if this helps.