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.


















Labels:

Comments

Post a Comment

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
2 comments
Read more

Collecting Logs from NSX-T Edge nodes using CLI

  This article explains how to extract the logs from NSX-T Edge nodes from CLI. Let's view the steps involved: 1) Login to NSX-T  Edge node using CLI from admin credentials. 2) Use of  " get support-bundle " for Log extraction. get support-bundle command will extract the complete logs from NSX-T manager/Edge nodes. nsx-manager-1> get support-bundle file support-bundle.tgz 3) Last step is to us e of " copy file support-bundle.tgz url " command. copy file will forward your collected logs from the NSX-T manager to the destination(URL) host from where you can download the logs. copy file support.bundle.tgz url scp://root@192.168.11.15/tmp Here, the URL specified is the ESXi host ( 192.168.11.15) under /tmp partition where logs will be copied and from there one can extract it for further log review. Happy Learning.  :)
Post a Comment
Read more

Removing NSX-T manager extension from vCenter

In NSX-T starting from ver 2.4 NSX-T appliance got decoupled from vCenter where now its not mandatory to run NSX-T on vCenter platform only. Now NSX-T can be managed through standalone ESXi host, KVM or through container platform. As in version 2.4 there is still an option available to connect vCenter to NSX-T using Compute Manager. Here in this blog we will learn how we can unregister and register NSX-T extenstion from vCenter in case of any sync or vCenter connectivity issue with NSX-T. Lets get started.. 1) Login to NSX-T UI Go to -> System ->Compute Manager Here, vCenter is showing in Down status where the status is showing as "Not Registered" 2) When we click on "Not Registered" option its states below error. 3) When try to click on Resolve option its states below. At this stage if the Resolve option doesn't work then its require the remove the NSX-T extenstion from vCenter. To remove the NSX-T e
Post a Comment
Read more