5.5 VMware NSX Dynamic Routing Scenario (Provider/Tenant) with MPLS
As provider and tenant functional requirements begin to expand in the public cloud, there might be a need to enable VMware NSX dynamic routing protocols, such as OSPF, to multiple network and security elements for both provider and tenant environments. When connecting to a third-party MPLS backbone, you can use BGP (external BGP/eBGP) as a dynamic routing protocol to exchange network information with the local backbone provider. The following figure provides an example of a Dedicated Private Cloud scenario where the service provider offers an environment for a single tenant.
Figure 12. VMware NSX Dynamic Routing Scenario with eBGP (External BGP) and OSPF
The following are the design considerations of this use case:
• OSPF can be configured between the tenant distributed logical router (to redistribute connected routes) and the management NSX Edge services gateway (to redistribute connected and static routes). Provider Edge NSX Edge services gateway A defines a shared OSPF Area 0. This supports end-to-end connectivity from the tenant logical networks to the provider management networks.
• Dynamic routing is disabled between the provider management NSX Edge services gateway and the physical management router. Static routes for the management networks are created on the provider management NSX Edge services gateway.
• BGP filters are created on the tenant provider NSX Edge services gateway to deny collection of routes from the WAN edge router. There is a large amount of network information from the WAN backbone provider that does not need to be collected in the local provider environment.
• Overlapping IP addresses are unsupported for the Internal Tenant Networks (logical switches).
