NSX-T Gateway and its components

 

NSX-T Gateway and Gateway components

                    - Prashant Pandey , VCAP-NV

 

In this blog we are going to discuss about all available options of Gateways and its components with NSX-T.

 

·       In NSX-T, we have 2 types of Gateways named as Tier-0 & Tier-1.

·       Each gateway has its own gateway components named DR (distributed router) and SR (service router).


Tier-0

Tier-1

T0 is needed for North-South connectivity.

T1 handles East-West connectivity.

Supports Static or dynamic routing
towards the upstream physical gateway.

No routing is needed, only connection is required with T0,
routing is taken care by NSX-T itself.

T0 is mandatory for any topology, be it
single tier or multi-tier architecture.

T1 is only required for multi-tier architecture,
since it can't have physical connectivity,
no single tier architecture is feasible with this.

NSX Edge cluster is always needed to
configure T0 Uplink for physical connectivity.

Edge cluster is only needed if state-ful services
are required on T1.

Once we spin up T0, both gateway
components (SR & DR) are created by default.

Once we spin up T1, only DR components gets created by default
and if we need SR component, we need to map this T1 to edge cluster.


SR

DR

SR stands for Service router.

DR stands for Distributed router.

SR enables gateway (T0 or T1)
to perform stateful services like NAT, stateful firewall.

DR enables distributed routing or
east-west routing.

SR components gets created on
Edge node only and not on transport node.

DR components gets created on
all Transport nodes including Edge nodes.




Representation of gateway components on Transport nodes & Edge nodes for better understanding.

 


·   

·       We can access CLI of T0-SR, T0-DR, T1-SR, T1-DR through edge node.

·       Login to edge node via admin credentials.

·       Get logical-router                          // to check all gateway components

·       VRF “id”                                           // to enter specific gateway component with VRF id 




Any Improvement points or suggestions are welcome.

-----ThankYou-----

Prashant Pandey





Comments

Post a Comment

Popular posts from this blog

Decision Factors to choose in between NVDS & CVDS during NSX-T deployments

Image
Decision Factors to choose in between NVDS & CVDS            - Prashant Pandey, VCAP-NV During NSX-T deployment, while preparing Transport nodes we have an option to choose between  NVDS (virtual switch dedicated to NSX tasks) & VDS (existing virtual switch used to manage vCenter environment) There are few design decisions which I have tried to consolidate and capture for easy reference. Decision Factors to choose N-VDS or Converge VDS. N-VDS Converge VDS Supports older version of vSphere, prior to 7.0 Requires vSphere 7.0 or more. Requires free pNics for uplinks No free pNics are required , can use original VDS uplinks only. Can only be managed in NSX and not in vCenter. Can be centralized managed in vCenter. Available with older version of NSX-T, prior to 3.0 Available with NSX-T 3.0 onwards ...
Read more

NSX-v to NSX-T workload migration with Network Coexistence via L2Bridge

Image
NSX-v to NSX-T workload migration with Network Co-existence - L2Bridging - Prashant Pandey , VCAP-NV   Use case -L2bridge is one of major use-case of workload migration from NSX-v to NSX-T along with network co-existence. Summary - There are mainly 3 use-cases for the workload migration from NSX-v to NSX-T . 1. Subnet based Migration - Shut one subnet at NSX-v  and add & advertise the same from NSX-T Pros - Easy to migrate, no addition VLAN requirement at physical network. Cons – No flexibility at Application level migration, it has be entire subnet in one go, might not be feasible in most of the production environment.   2. Network Co-existence with VMware HCX tool – Supports Network stretch with L2E feature. Pros – Network Co-existence can be achieved with ease. Cons – Separate license requires, includes extra cost.   3. Network Co-existence with L2Bridging - Supports Network stretch with layer 2 bridging feature. Pros – Netwo...
Read more

Independent Bridging : NSX-v to NSX-T In-Parallel Migration use case.

Image
                    Independent Bridging : NSX-v to NSX-T In-Parallel Migration use case. –  Prashant Pandey, VCAP-NV-2021 Agenda NSX-v to NSX-T workload migration using NSX Independent bridging option. •          Different Available Migration Approaches – High level •          Independent Bridging approach – In detail •          Customer use-case discussion – Why independent Bridging ? •          L2Bridging Readiness •          Validation & Testing Why Migrate to NSX-T ? NSX for vSphere (NSX-V) has already been out of general support since Jan/2022 & will be out of technical guidance from Jan/2023 onwards. Top of mind question for customers who have adopted NSX-V is - how do I upgrade my NSX-V based data center to...
Read more