This is the next post on a series of posts on NSX-T Edge Node design topologies. In this blog post I will describe an Edge Node design topology hosting a Tier-0 Gateway with Dynamic Routing with BGP. This Edge Node topology supports Active/Active and Active/Standby Tier-0 design.
With the Edge Node Virtual Appliances it is important to know on which vSphere Hosts the Edge Nodes are going to run, how many physical NICs are available and if the Edge Node is running on top of a VSS/VDS or N-VDS and how teaming is configured. In this design topology the Edge Nodes are running on hosts with one VDS with two Physical NICs.
In NSX BGP filters work like access lists for route advertisements (prefixes). The NSX BGP filters are prefix lists which work very similarly to firewall access lists. A prefix list contains one or more ordered entries which are processed sequentially. For each prefix entry you can specify inbound or outbound filters to allow certain routes to be advertised to or from the Edge Services Gateway/Distributed Logical Router.
For example you to want to prevent a route for 10.0.0.0/24 from being advertised in BGP from the NSX Edge Services Gateway.
In this blog post I would like to share how BGP is configured on VMware NSX to automatically update routing information with the physical network.
Recently I was involved in a project where we used BGP to peer the NSX environment with the physical network. The design we did was challenging because of scale. The NSX environment we deployed meant for a multi-tenant Cloud platform scaled for several hundreds of tenants.