Overlay Networks

In a small Data Center, it's common to find clusters with management components such as vCenter, NSX Manager, vRealize Automation, vRealize Network Insight, vRealize Log Insight, and so on. This is what we called a "Shared" Management and Compute cluster. Edge VMs can be deployed in a shared cluster. In the following diagram, the hosts are ESXi based and they have 4 pNICs available or more on each. In this scenario, we are going to dedicated two (2) pNICs for management components and EdgeVMs. Two (2) other pNICs will be used for workloads traffic (or compute). I use the following VLAN information in my setup for the Edge VM configuration. Management VLAN: 599 vMotion VLAN: 598 TEP VLAN for Compute: 596 Uplink1 Trunk for Edge VM: 0-4094 Uplink2 Trunk for Edge VM: 0-4094 N-VDS Edge VM Diagram We are going to configure the "Single N-VDS Edge VM Design on VDS with four (4) pNICs". This design is available since NSX-T 2.5 release. The si

In a small Data Center, it's common to find clusters with management components such as vCenter, NSX Manager, vRealize Automation, vRealize Network Insight, vRealize Log Insight, and so on. This is what we called a "Shared" Management and Compute cluster. Edge VMs can be deployed in a shared cluster. In the following diagram, the hosts are ESXi based and they have 4 pNICs available or more on each. In this scenario, we are going to dedicated two (2) pNICs for management components and EdgeVMs. Two (2) other pNICs will be used for workloads traffic (or compute). I use the following VLAN information in my setup for the Edge VM configuration. Management VLAN: 599 vMotion VLAN: 598 TEP VLAN for Compute and Edge VMs: 596 Uplink1 VLAN for Edge VM: 10 Uplink2 VLAN for Edge VM: 20 N-VDS Edge VM Diagram We are going to configure the "Multiple N-VDS Edge VM Design on VDS with four (4) pNICs". This design is required for NSX-T 2.4 release and below.