Skip to main content

Posts

Showing posts with the label NSX-T

Architecture layout of NSX-T Data Center

Architecture layout of NSX-T Data Center As we all know that NSX is one of the retro product of VMware into the network and security. It run on any device, any cloud and and any application. At present one can run and its connectivity on most of the public cloud like Alibaba, IBM Cloud, AWS or Azure. Lets talk about the all rounder of NSX which is NSX Transformer (NSX-T) which can make communication with various hypervisor like ESXi, KVM, Containers, Openstack and many more. To continue conversation with NSX-T Data Center, lets discuss its major elements. There are 3 main elements of NSX -T Data Center which are: 1) Management Plane 2) Control Plane 3) Data Plane In NSX-T Datacenter ver 2.4 Management and Control Plane are converged means the are now available on single VM or you can say in one OVF. 1) Management Plane:   It is designed with advance clustering technology, which allow the platform to process l

CDO Mode in NSX Controller

CDO  ( Controller disconnect operation) Mode in NSX Controller. CDO mode ensures that the data plane connectivity in the multisite environment. When primary site loses connectivity. Here you can enable CDO mode on secondary site to avoid any temporary connectivity issue related to data plane.  When the primary site is down or not reachable, the CDO logical switch is used only for control plane. Purpose and therefore its a not visible under logical switches tab.

About NSX VTEP Reports

NSX VTEP Reports NSX Controller VXLAN directory services. There are basically 3 types of tables under VTEP 1) MAC Table 2) ARP Table 3) VTEP Table MAC Table:  The MAC table includes the VNI, the MAC address and VTEP ID that reported it. If a unknown unicast frame is reviewed by a VTEP. The VTEP sends a MAC table request to NSX Controller for a destination MAC address. If NSX controller has the MAC address in the MAC table, it replies to the VTEP with information on where to forward the frame. If NSX controller does not have MAC address in the MAC table then the VTEP floods the frame to other VTEP's. ARP Table: The ARP table used to suppress the broadcast traffic. IP report generate the ARP Table. The VTEP's send a copy to each MAC address and IP mapping that they have. This report is called the IP reports. NSX controller creates a ARP ta

NSX VXLAN Logical Switch Replication mode

NSX VXLAN Logical Switch Replication Mode. NSX controller is the central control point for all logical switches within a network and maintain information of all virtual machine, host, logical switch and VXLAN. The controller support two new logical switch control plane mode. 1) Unicast 2) Hybrid The replication mode tells NSX to manage BUM traffic which sent from virtual machine. Multicast mode Control plane operation is based on multicast flooding and learning. BUM traffic replication is based on L2 and L3 multicast. It require 1GMP and multicast routing. Unicast Mode Control Plane operation is based on NSX controller cluster. BUM traffic replication is based on unicast . (One destination at a time) Host depend on UTEP (unicast TAP) for replication for traffic on remote signal. Hybrid Mode Bum traffic replication based on unicast and L2 multicast. Local replication is offloaded to physical network. Remote replication is based on unicast.

Overview on VXLAN

VXLAN (Virtual Extensible Local Area Network) Logical Switch reproduce switching functionality (Unicast, multicast or broadcast) in virtual environment which completely decouple from underlying hardware. Logical Switches are similar to VXLAN in that they provides network connections to which you can attach virtual machine. The VM's can communicate with each other over VXLAN if they are connected to some logical switches. About VXLAN LIF The DLR support logical switches which are backed by VXLAN. First-hop routing is handling on the host, the traffic is switched to appropriate logical switch. If the destination is at another host. the ethernet frame is placed in the VXLAN frame & forward. Only one VXLAN LIF can connect to logical switch. The next-hop can be an NSX Edge service gateway. VXLAN LIF can span all distributed switch in the transport zone.