Hello everyone!
I need a help.
On what occasions should I not deploy EDGE or DLR, and what are the functionalities I get out of it?
Thank you!
Accepted Solutions
The basic difference between NSX Edge and DLR is Edge is one entity which contains both Control Plane and Data Plane , however when it comes to DLR - Control Plane functionality is handled by Control VM and data plane is residing in ESXI host. NSX DLR control Plane is handled by DLR Control VM and via NSX Controllers Routes are pushed to underlying ESXI hosts. DLR Kernel module will help us to route between different subnets,however if there is a demand for dynamic routing DLR Control VM is mandatory and the control VM functionality/deployment is not required if the demand is only for static route.Each ESXi host has its own copy of each configured DLR instance. Each DLR instance has its own unique set of tables containing the information needed to forward packets. This information is synchronized across all hosts where this DLR instance exists. Instances of an individual DLR across different hosts have exactly the same information.Routing is always handled by a DLR instance on the same host where the source VM is running. This means that when source and destination VMs are on different hosts, the DLR instance that provides routing between them sees packets only in one direction, from source VM to destination. Return traffic is only seen by the corresponding instance of the same DLR on the destination VM’s host.
The DLR has the following properties:
- High performance, low overhead first-hop routing:
- Scales linearly with the number of hosts
- Supports 8-way ECMP on uplink
- Up to 1,000 DLR instances per host
- Up to 999 logical interfaces (LIFs) on each DLR (8 x uplink + 991 internal) + 1 x management
- Up to 10,000 LIFs per host distributed across all DLR instances (not enforced by NSX Manager)
The ESG is essentially a router in a virtual machine. It is delivered in an appliance-like form factor with four sizes, with its complete lifecycle managed by the NSX Manager. The ESG’s primary use case is as a perimeter router, where it is deployed between multiple DLRs and between the physical world and the virtualized network.
The ESG has the following properties:
- Each ESG can have up to 10 vNIC interfaces, or 200 trunk sub-interfaces.
- Each ESG supports 8-way ECMP for path redundancy and scalability.
ESG and DLR Differences ,Query regarding nsx edge
There are some differences between the wizard screens when an ESG is deployed, compared to a DLR.
The first one is on the “Configure deployment” screen:
For an ESG, “Configure Deployment” allows selection of the Edge size. If an ESG is used only for routing, “Large” is a typical size that is suitable in most scenarios. Selecting a larger size will not provide more CPU resources to the ESG’s routing processes, and will not lead to more throughput.
It is also possible to create an ESG without deploying it, which still requires configuration of an Edge Appliance.
A “Non-deployed” Edge can be later deployed via an API call or with the “Deploy” UI action.
If Edge HA is selected, you must create at least one “Internal” interface, or HA will fail silently, leading to the “split-brain” scenario.
The NSX UI and API allow an operator to remove the last “Internal” interface, which will cause HA to silently fail.
Thanks Sreec
The main differences between EDGE and DLR are quite clear, thanks for the response.
I still have questions regarding the use of DLR with the option below unchecked.
* What is the difference of the deployed DLR and the non deployed DLR?
* Which one is recommended? (DLR deployed or non deployed)
Thank you again!