BGP Route Re-Distribution for Tier-0 VRF Gateways - More than NAT IP

[marc6272]

A Provider Gateway has been created using a Tier-0 VRF Gateway (Cloud Director 10.5)
The Tier-0 VRF Gateway has eBGP configured and running with our core routers

By default, only NAT-IPs from Tier-1 (Edges) are redistributed by that Tier-0 VRF Gateway to the Core Routers via eBGP.

All the networks that we need to redistribute are correctly located in the T0 VRF routing table (that part works fine).

But, if we want to advertise Connected Segments (t1c), do we need to manually modify the default BGP Distribution using the NSX-T UI or API? I can't find an option in the Cloud Director UI to do this (Cloud Director only configure the T0 with NAT redistribution). 

[dawid_dudek]

Hi,

It sounds like you asking for IP Prefix List in BGP:
https://docs.vmware.com/en/VMware-Cloud-Director/10.5/VMware-Cloud-Director-Service-Provider-Admin-G...

Have a nice day,
Dawid

[marc6272]

Hi,

Not really. IP Prefix lists can be used to restrict what is advertised. But only NAT IPs are advertised to begin with (unless you manually change the VRF Gateway using the NSX-T UI/API which I was hoping to avoid).

Thanks,

Marc.

[Sreec]

You can perform this if you have dedicated T0/VRF configured in the VDC. 

[marc6272]

It is a dedicated VRF Gateway... But I have not found the option in Cloud Director 10.5 to make that change. I can of course do it directly in NSX.

Thanks,

Marc.

[Sreec]

It should work in 10.5 as well, i have a running config in my lab and it shows right output. Can you share the screenshot of org-vdc--->Networking->Edges->T1->Configuration->General . Also may i know the version of NSX ? 

[marc6272]

Hi Sreec,

Attached are the screenshots. It's a test environment as well.
NSX is version 4.1.1.0.0.22224312

After doing a few things, the route redistribution in the VRF Gateway (SYSTEM-VCD-EDGE-SERVICES-REDISTRIBUTION) changed to also advertise Connected Interface & Segments (Service Interface Subnet + Connected Segment). No idea what triggered that change (and how to control it)

Thanks,

Marc.