Skip to main content

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 table with the information in the IP request.





  • The ARP table includes the MAC to IP addrEss mapping and VTEP IP that reported it.





  • The VTEP intercepts all APR request from VM.





  • If the VTEP does not have the MAC address in its local ARP table, then VTEP queries the NSX controller instance from the information.





  • If the NSX controller instance does not have MAC address in the ARP, then ESXi host (VTEP) broadcast the frame to all virtual machine in the same VNI that are running in the VTEP and to all other VTEP in same VNI.









VTEP Table:






  • The function of VTEP table is to track all its VTEP's IP's, and VTEP MAC address via VNI.
  • The ESXi host updates its local VTEP and its send report to NSX Controller with this information.





  • NSX controller then pushes out the VTEP table to all hosts for the related VNI via the UWA.


















Comments

Popular posts from this blog

Changing the FQDN of the vCenter appliance (VCSA)

This article states how to change the system name or the FQDN of the vCenter appliance 6.x You may not find any way to change the FQDN from the vCenter GUI either from VAMI page of from webclient as the option to change the hostname always be greyed out. Now the option left is from the command line of VCSA appliance. Below steps will make it possible to change the FQDN of the VCSA from the command line. Access the VCSA from console or from Putty session. Login with root permission Use above command in the command prompt of VCSA : /opt/vmware/share/vami/vami_config_net Opt for option 3 (Hostname) Change the hostname to new name Reboot the VCSA appliance.   After reboot you will be successfully manage to change the FQDN of the VCSA . Note: Above step is unsupported by VMware and may impact your SSL certificate and face problem while logging to vSphere Web Client. If you are using self-signed certificate, you can regenerate the certificate with the

VM Creation Date & Time from Powercli

Most of the times we have several requirement when we talk about IT environment like designing , deployment , compliance check or for Security auditing the environment. Somewhere during security auditing we require to provide several information to security team to get successful audit. One of them is the compliance of Virtual machine auditing of creation date and time. Here into this post we will explore how to get the creation date and time of virtual machine hosted into the vCenter or ESXi. To get the details we will use VMware Powercli to extract the details. By default there is no function added into Powercli to get such details, so here we will add a function of vm creation date. Below is the function which needed to be copy and paste into the Powercli. ======================================================================= function  Get-VMCreationTime  {     $vms  =  get-vm     $vmevts  = @()     $vmevt  =  new-object  PSObject     for

Unable to poweron the VM. (Failed to lock the file)

I have encountered may issues like where after some upgrade or migration we were unable to power on the VM. Figure 1 An error was received from the ESX host while powering on VM HSSVSQL01. Failed to start the virtual machine. Cannot open the disk '/vmfs/volumes/578d835c-18b2c97a-9b0d-0025b5f13920/SAMPLE1_cloud/000000.vmdk' or one of the snapshot disks it depends on. Failed to lock the file In above Figure:1, where while powering on the VM, its prompt for an error. Well, there are several reason for where the VM unable to poweron and you can find many article on this. Here in this article we will discuss to resolve this issue. Please use below step to resolve the disk lock issue  C hecked that VM is running on snapshot if its getting error " VM Consolidation required". Checked the snapshot manager if its showing any snapshot. If yes, try to delete the  snapshot. Verified the same from Esxi cl