In this session I am going to cover that how the NSX decontrol plane or the controller.
They are maintaining a different type of cable increase so they are maintaining global Mac cable.
So here you can see that global macro is to the table and then they are maintaining the optimal associating
MAC address to the IP.
Now while the control plane they're maintaining the MAC address to the DP table and the optimal or stay
use case why they're maintaining these cables.
So the logic behind this is actually taken from the class fabric.
The fabric is something known as leaf and the fine and then leaf so you have leaf one is pine one and
you have a leaf too.
And suppose you have a spine too as well at the moment.
This diagram is really fairly small but you may have any number of leaves and you want to send or receive
the graphic from this place to this place.
Now in that case suppose if a particular endpoint leaf is nothing but the hypervisor on that we have
some kernel module and they have the DPR.
So you you think this leaf has the eternal endpoint.
Nothing like this Suppose that a particular leaf they have to communicate with the end leaf.
So when VM is here I'm just associating when we aim to suppose when we were representing.
So for example one leaf but it's actually hypervisor.
Then you have in the years and then you have VM and in between you have tip they think everything as
a for example as a DP might end up with one end point I'll come this as an point.
So one of the endpoint wants to communicate with the other end point.
Now if you check this with our traditional network what is happening that all the end points have to
maintain all the Mac table all the Macintosh.
If they are not maintaining all the mechanisms then what will happen.
They will some day will send some broadcast or they will send some flack packet that flood back packet
will be flooded throughout the include women and then in the act as you can see how much will be the
bandwidth of the flag it back.
So just to suppress those flood and just to optimize the communication this control plan devices actually
they are maintaining the these cables.
The global Mac and global are.
So what is happening in this case that they have the Mac and do they have the IP apparently and now
if L1 wants to communicate with N or one in point One should communicate with far end point then they
will simply query to the control plan Hey controller do have this Mac to IP so I know that towards the
Mac.
So he wants to I don't know the Mac actually but I know the destination IP for example.
So I know their destination IP do we have the MAC address of this destination IP correct.
So the query will happen like this.
And in that case that you are not sending that request or you're not flagging that request to the domain
rather you're asking too one single point.
And because he has the entry he know oh you are looking for this particular destination IP whose Mac
is this.
So that's why they have this ARP tables oppression in there and even they have a Mac table as well that
this is the example of the art.
So for example you know Mac to IP binding or IP to mark binding.
So for example the other case when you're doing the L2 type of communication at that time also you can
query Oh this is the Mac actors do have this MAC address and because they know they know their DP to
the Mac binding so they can call this the location.
So very much the same thing that we can call plan devices they are doing in most of the Eastern solution
in NSX field so they are doing the same.
So you can see that they have the optical as well and this is actually there to do some sort of arm
separation mechanism.
And now the invidious loop the and our traffic loan Mac two IP associations they have active it now
here in the diagram we will understand what I try to tell the suppose what is happening I'll give point
number one is actually very important.
This mechanism is true for an SSD this mechanism is true for Cisco PCI as well.
So what is happening that whenever this particular VM VM is connected VM has the Nick that system as
a unique it is connected with n we d s so here you can see the end game is in the green glow so at the
moment and really is learn that Okay what is the v neck to Mac binding they are telling that information
so here obviously you have the IP as well so this information you are telling you they can go play.
So they are sending one message all this the interface is the Mac is the IP learn this.
Likewise this VM be also sending that information to the control plane.
So now the control plan know everything about a and b and now after that if the B wants to communicate
with a they will not send a flood in the network but they will simply go and query to the control plan.
Hagar Cohen I am looking for this particular MAC IP Mac so you know this particular towards the MAC
address and then they will try and then they will quickly respond.
So here you can see the response time is low already one central database knows the entries so watch
the IP to Mac resolution.
They can simply go in and they will do the communication.
Now there may be case that you are equating to the control pin and a control plane don't know what's
the destination then in that case control plane can do are bleeding.
So on behalf of this particular query the aggregates coming they will say there are query to all the
transport nodes and then they will collect the information and then they will bypass this information
to this particular VM.
Why are they in this.
So this is the mechanism and you can see that the layer to networking has been simplified.
Now in case of You reconstructed.
So what exactly this and really is is maintaining that they are also maintaining two type of entry they
are maintaining Vidic to Mac entry because obviously your virtual machine is connected with Vinick and
that is connected with switch.
So once you connect the switch with the interface which will learn that Mako gets over that interface
that's quite natural.
Correct.
So we need to make entry and other thing they have is tape to make entry.
So here you can see that tape to Mac entry also they are learning now what's the use of this same case
of Unix traffic.
One of the VM supposed web VM wants to communicate with the Web VM one so three wants to communicate
with one.
What will happen the query will come to the end radius and radius.
I am sending the query Do you know this Mac.
Now what will happen.
You can see the invidious entry to end which is how it is and really is is failing.
Okay Mac and Me Nick I know Mac two belongs to people to Mac three belongs to TB three.
Likewise Eric can see that they have the Mac too.
We need to Mac.
So we need to Mac and Mac to keep into these it is actually they are learning from the data and learning.
So once we have the dynamic channel they used to learn and install those entries so in general and it's
very important to note here that you have to type of entry here.
You have one entry call local entry or you can say that you have you are learning the local and point
and the other entry that you are learning is the remote end point now the switch is learning those entries.
Now they're learning from their data internal or they are learning from control plane query means they're
sending query to control plane control plane in sending the information to these devices that's the
different thing.
But this virtual distributed seat has truly angry local entry remote control.
I know obviously they have some sort of timer.
So for example 300 seconds or 600 seconds they can cash those entries inside their local memory inside
their local buffer for some period.
So that's the way they are the Unix traffic is floating and we have learned that highly controlled plane
they are maintaining the global Mac.
And the argument is that's what.