Overview of VTEP (VXLAN TUNNEL END POINT) in VMware NSX !!

-

VTEP also know as VXLAN Tunnel Endpoint  has a very significant role on NSX platform. VTEP works on VMKernel port group created on ESXi host. VXLAN is hyper-visor based kernel module and installed during ESX host preparation via NSX manager.
It handles all encapsulation and decapsulation for VXLAN network.


VTEP Table- Every VTEP on ESXi hosts reports the VNIs that they are a member of to the NSX                            Controller. NSX Controllers maintain this list and send it to all VTEPs.
                      Each VTEPs has a full inventory for VNIs in which they participate. NSX Controllers                          also use this list to select the VTEP Proxies as well.

MAC Table - VTEPs will report every known MAC address in each VNI to the NSX Controller. this                        will cut the unnecessary ARP request flooded among the individual hosts VTEPs. If a                         VTEP needs a MAC of an IP, it will request to NSX controller. If NSX Controller has                           the entry of that it will return to the VTEP and if not then NSX controller will flood this                       request to other VTEPs like a broadcast.


IP Report- Each VTEPs will send the MAC address and IP mappings details to NSX controller.

ARP Table- NSX controller uses the IP report which includes MAC address and IP mappings to                             create the ARP table.

Whenever a VM sends an ARP request, it is captured by the VTEP.
If the VTEP knows the answer it will reply to VM.
If VTEP does not know the answer then it will request from NSX controller.
If NSX controller does not know the answer, the request will broadcast to all VMs in the same VNI.













Comments

Post a Comment

Popular posts from this blog

How to migrate the N-VDS as the host switch to VDS 7.0 in NSX-T 3.x

-
Image
  Hello There, In this article, i am covering how to migrate the ESXi host switch from N-VDS to VDS 7.0 switch in NSX-T 3.2.x version. When using N-VDS as the host switch,  NSX-T  is represented as an opaque network in  vCenter Server . N-VDS owns one or more of the physical interfaces (pNICs) on the transport node, and port configuration is performed from  NSX-T Data Center . You can migrate your host switch to  vSphere  Distributed Switch (VDS) 7.0 for optimal pNIC usage and manage the networking for  NSX-T  hosts from  vCenter Server . When running  NSX-T  on a VDS switch, a segment is represented as an  NSX-T  Distributed Virtual Port Groups. Any changes to the segments on the  NSX-T  network are synchronized in  vCenter Server. We have an NSX-T environment running with NSX-T 3.2.2.1 version. this environment was designed and implemented with NSX-T 2.x version and that time we used the N-VDS as host switch configuration on the transport nodes bcuz VDS was not supported that time. 
Read more

vROPS appliances password remediation tasks failed from SDDC manager

-
Image
Issue details:-   Password remediation tasks on SDDC manager getting failed with below error. However, we are able to connect SSH with root password on the vROPS appliances, no issues with credentials. I checked Operations logs on SDDC manager and found below logs, indicating the SSH connectivity issues from SDDC to vROPS appliances. Tried to do SSH vROPS appliance from SDDC manager, getting below error... Seems some issue with ECDSA key.. Resolution:- SSH to vROPS appliance and retrieve the ECDSA ssh keys as below. Now, we have 2 options to update the correct SSH keys for vROPS appliance on SDDC manager known_Hosts files located at below location.   /root/.ssh/known_hosts   /etc/vmware/vcf/commonsvcs/known_hosts   /home/vcf/.ssh/known_hosts   /opt/vmware/vcf/commonsvcs/defaults/hosts/known_hosts First option is manually copy and paste the SSH key on all the known_hosts files and restart the SDDC manager services and then try to remediate the password again. it will be successful this
Read more

How to Import/Register a VM into vRA portal

-
Image
You can import an unmanaged virtual machine to a vRealize Automation environment. An unmanaged virtual machine exists in a vCenter but is not managed in a vRealize Automation environment and cannot be viewed in the vRA portal . Once you import an unmanaged virtual machine, the virtual machine is managed by using the vRealize Automation management interface. you can see the virtual machine on the Managed Machines tab or the Items tab. Please follow below steps to Import/Register VM into a vRA portal. Log in to vRealize Automation as a fabric administrator and as a business group manager. If you are importing virtual machines that use static IP addresses, prepare a properly configured address pool.  If you use bulk import to import a virtual machine with a static IP address that is allocated to another virtual machine, the import fails. Create a Blueprint and should not have even network attached as well. See below snapin. Create Network profile that shoul
Read more