![vmware mac address table aging vmware mac address table aging](https://jcutrer.com/wp-content/uploads/2019/10/show-mac-address-table.jpg)
Step 4: CCP periodically sends copy of the updated table to LCP of all transport nodes so that all nodes are aware of TEP IP-VNI association of rest of the nodes.Īt this point every transport node is aware of who all are participating in a given segment.Īnd that completes the process of TEP table creation.
#VMWARE MAC ADDRESS TABLE AGING FULL#
Step 3: CCP receives TEP report from all transport nodes and starts to build full TEP table corresponding to a given VNI. Step 2: Each transport nodes then send their VNI-TEP entry from its LCP to CCP (running on NSX-T Manager). Note: VTEP can be viewed by logging into ESXi host and running command: get logical-switch vtep-table Each transport node then send this info to Local Control Plane (LCP). Step 1: As soon as a segment is created in a TZ, all transport node of that TZ updates its local TEP table and registers VNI of the created segment against its TEP IP. Lets understand TEP table creation with the help of below diagram. Each transport node in that TZ will have a TEP IP.Each segment has a unique identifier called VNI.This table holds the VNI to TEP IP mapping. A couple of points before we start. These tables are continuously updated and modified as we provision new workloads and create new segments.
![vmware mac address table aging vmware mac address table aging](https://image1.slideserve.com/1638167/mac-address-notification-l.jpg)
![vmware mac address table aging vmware mac address table aging](http://www.ccieordie.com/wp-content/uploads/2018/08/ine_bgp.png)
Basically I will discuss about formation of below tables: In this post I will explain how NSX-T create and maintains various table which forms the building block of logical switching.