NSX-T Edge T0 Router: Static Route + SNAT instead of BGP

[athisesan07]

Hi All,

We have some Migration scenario such as below, (Fortigate VDOM to NSX Edge)

1.  Customer have dedicated internet with /30 range on static route format.

2. Customer have dedicated P2P with /26 range on static route format.

3. Customer have dedicated MPLS with /30 range on static/BGP route format.

Thought to NSX Side configuration

We have PE-T0 with aligned with Shared-T0 toward all the customer VRF is to be connected. 

Creation customer VRF and connected T1 is completed (T1 creation by VCD), but how to be assign the that above scenarios in VCD Edge gateway and customer VM segments. 

Note: we knew service interface will not support the IPsec and tunnel. 

Are we go single node point of interface to configure the static route without any BGP? 

[Sreec]

I would prefer Dynamic Routing (BGP) in this case instead of doing Static routes considering your tenant's outbound connectivity requirements. You can certainly do the Static route and it will be a housekeeping exercise for the provider.  Creation of T1 is a manual step that you need to do in VCD portal and all workload segments can be routed via respective Tenant T1 ( which will be mapped to TO/VRF with outbound static routes) 

For IPSEC tunnels, Tenant will get this feature on all the T1 routers irrespective of the routing design.