nsx-v and nsx-t differences

[jvm2016]

Hi All,

Can some one check following points and suggest if they are correct

1:nsx-v uses vmkernel port on esxi for TEP .does it hold good good nsx-t also.

2.recommended MTU for nsx-v is 1600 bytes is it same for nsx-t or is it 1700 (being geneve as overlay technology comapared to vxlan for nsx-v)

3.ESGs in nsx-v provide stateful functions like NAT ,vpn,dhcp etc ... what is equivalent in nsx-t that provides these functionalists .

4:T0 and T1 gateways have corresponding DR and SR components do they reside on edge??

[p0wertje]

Hi,

1. nsx-t 3.0 + vsphere 7.0 uses dvswitch. vmk is created for tep traffic.

2. nsx-t recommendation is 1600 minimum, but 1700 is advised.

Jumbo Frame Support – A minimum required MTU is 1600, however MTU of 1700 bytes is recommended to address the full possibility of variety of functions and future proof the environment for an expanding Geneve header. As the recommended MTU for the N-VDS is 9000, the underlay network should support at least this value, excluding overhead.

3. Nsx-t uses edge-nodes. T0 and T1  can do the statefull functions.

4. DR component is on the esxi host (in kernel) SR component is on the edge node.

See  VMware® NSX-T Reference Design

[jvm2016]

thanks for sharing design guide

however it seems to and t1 gateways can not be used for centralized services like vpn nat dhcp .they can only be configured fon edge nodes .

this is from guide.

 Edge Nodes: VMware NSX-T EdgeTM nodes are service appliances dedicated to running

centralized network services that cannot be distributed to the hypervisors. They can be

instantiated as a bare metal appliance or in virtual machine form factor. They are grouped

in one or several clusters, representing a pool of capacity.

[p0wertje]

Hi,

There the SR comes in play.

The SR takes care of those services.

You need edge nodes to run SR (they can be virtual)

4.1

Tier-0 Gateway consists of two components: distributed routing component (DR) and centralized services routing component (SR).

4.1.2 Services Router

East-West routing is completely distributed in the hypervisor, with each hypervisor in the transport zone running a DR in its kernel. However, some services of NSX-T are not distributed, including, due to its locality or stateful nature:

● Physical infrastructure connectivity

● NAT

● DHCP server

● Load Balancer

● VPN

● Gateway Firewall

● Bridging

● Service Interface

● Metadata Proxy for OpenStack

A services router (SR) – also referred to as a services component – is instantiated when a service is enabled that cannot be distributed on a gateway. 

A centralized pool of capacity is required to run these services in a highly-available and scale-out fashion. The appliances where the centralized services or SR instances are hosted are called Edge nodes. An Edge node is the appliance that provides connectivity to the physical infrastructure.