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 permissionUse above command in the command prompt of VCSA : /opt/vmware/share/vami/vami_config_netOpt for option 3 (Hostname)Change the hostname to new nameReboot 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 help of below KB 2112283 article.



Happy Sharin…

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 foreach ($vm in $vms) { #Progress bar: $foundString = "       Found: "+$v…

Could not connect to one or more vCenter Server systems: https://FQDN:443/sdk

Recently I got a case where vCenter 6.0 where the webclient was not showing inventory while loading. Issue occur when the customer was performing migration activity of virtual machine.
We verified that the vpxd services of vCenter, which is VCSA (Appliance), went into stopped stated just after starting means its crashing.
On VCSA Shell: service-control --status vmware-vpxd shows "stopped" service-control --start vmware-vpxd starts the service starts for a couple of seconds and stops again
VCSA 6.0 is linked with extrnal PSC 6.0. Verified the services of PSC and found all looks into good state.
Tried to power off both the VCSA and PSC and Power on in sequence where we started first PSC and later VCSA. After restarting the VCSA, status of the VPXD services was same as it was getting stopped after couple of seconds.
Checked the VPXD logs and found that the heartbeat between ESXi and VCSA was getting timed out for more than 1032 ms or more.
VCSA has generated the core dump at /var/core. …