Each and Every NSX Controller present in the NSX Controller cluster maintains the following tables:
ARP Table:
--> Contains the Information about IP, MAC address as well VNI of Virtual Machine
--> Basically to track IP to MAC Address Mapping of Virtual Machines
--> As soon as Virtual Machine starts sending traffic to other virtual machines in the network, The Transport node is going to capture the IP to MAC mappings from the traffic.
--> The copy of the ARP table is sent to all the transport nodes from NSX Controller
--> The purpose of the ARP Table is to reduce the number of broadcast traffic over the network
--> Does not have the information about Virtual Machine present in which host( TEP)
Format:
VNI IP Address MAC Address
5001 10.0.0.1 AAAA.BBBB.CCCC
Command:
get logical-switch <UUID > arp-table
MAC Table:
--> The purpose of MAC Table is to know the Transport Node associated with Virtual Machine
--> From MAC table we would get to know about the location of Virtual Machine present in which ESXI Host/KFM Host
--> As soon as VM gets powered on the ESXI host is going to update the MAC Table and send it to the NSX Controller
--> NSX Controller will update MAC Table with all other transport nodes.
Format:
VNI VTEP IP MAC Address
5001 172.16.0.1 AAAA.BBBB.CCCC
Command:
get logical-switch <UUID > mac-table
TEP Table:
--> The purpose of the TEP Table is to know the MAC address of Transport Node as well as VNI Information
--> TEP Table provides information about how many VNI's are configured on the Transport Node
--> Whenever you create a segment on the NSX Manager, It will be pushed to all transport nodes present in the transport zone
--> As soon as you add any virtual machine to the created segment, The TEP table is populated with VNI of Segment to make the NSX Controller know that Segment is in use
--> Every ESXI Node ( Transport Node) will receive the updated TEP table information from NSX Controller
Format:
VNI VTEP IP MAC Address
5001 172.16.0.1 CCCC.DDDD.EEEE
Command:
get logical-switch <UUID > vtep
Reference: VMWARE
0 comments:
Post a Comment