jeffj2000
Enthusiast
Enthusiast

Do I need a Tier-1 Gateway in NSX-T?

Jump to solution

Hi. We are currently in an NSX-V deployment and are starting to learn NSX-T. If we are single tenant, do we actually need a Tier-1 Gateway? Or can we simply use Tier-0 to connect our segments to our Edges?

We are currently in a cross-vCenter deployment between 2 sites, so we would want to keep that topology of course. Thanks,,,

0 Kudos
1 Solution

Accepted Solutions
bayupw
Leadership
Leadership

Hi, single tier routing (Tier-0 only) and two-tier/multi-tier routing would be design options and based on requirements.

If in the future you have a strategy to do tenant-based routing, automation, scale-out north-south,

I would suggest to two-tier in advance so you don't need to migrate in the future.

pastedImage_0.png

Bayu Wibowo | VCIX6-DCV/NV
Author of VMware NSX Cookbook http://bit.ly/NSXCookbook
https://github.com/bayupw/PowerNSX-Scripts
https://nz.linkedin.com/in/bayupw | twitter @bayupw

View solution in original post

0 Kudos
3 Replies
Lalegre
Virtuoso
Virtuoso

Hey Jeffery,

If you need it or not it would be definitely based on the type of design you have, your routing construction and the type of features you want to use. For example if you want to configure ECMP and have more than one Tier-0 as active then you will definitely need the Tier-1 as you will need them for configuring stateful services such as NAT, Firewall (Gateway) and Load balancing.

If you are only going to use NSX-T for providing L2 and L3 connectivity then maybe it is not needed but as i said it depends on how is the logic and the network construction you want to apply.

For going deeper in the configurations and recommendations i suggest you to take a look at the next document which explains all in great details even for the ones who are just starting with the product: https://images.nsx.techzone.vmware.com/sites/default/files/NSX-T-Reference-Design-Guide-Version-2.0_... . This is the reference design guide of the whole product not only for vSphere but also with KVM. Take into account that this document has not been updated yet to version 3.0.0 so for example you won't see recomendations of N-VDS vs VDS.

Finally and personal opinion is that today you have one tenant but if you want to grow in the future and there is a possibility of having more tenants or you think in a way of having multiple segregation i would go with a Tier-0 and then a single Tier-1. Doing that you will be able to scale on the Tier-0 is the throughput is desired and keep growing in Tier-1 (Tenants) as needed.

0 Kudos
bayupw
Leadership
Leadership

Hi, single tier routing (Tier-0 only) and two-tier/multi-tier routing would be design options and based on requirements.

If in the future you have a strategy to do tenant-based routing, automation, scale-out north-south,

I would suggest to two-tier in advance so you don't need to migrate in the future.

pastedImage_0.png

Bayu Wibowo | VCIX6-DCV/NV
Author of VMware NSX Cookbook http://bit.ly/NSXCookbook
https://github.com/bayupw/PowerNSX-Scripts
https://nz.linkedin.com/in/bayupw | twitter @bayupw
0 Kudos
jeffj2000
Enthusiast
Enthusiast

Hi. Thank you much. I understand it now. Thanks,,,

0 Kudos