This is important session.
Here we are going to discuss about NSX key architecture component means or what is the architecture
of an extra NSX.
How it look likes.
So suppose if someone will give you a plain piece of paper and he will tell you.
Okay go.
The NSX key architecture.
How You Can Write how you can explain that so for that let me open the whiteboard.
I have an online whiteboard and let me try to draw here because we know that we are dealing with the
esteemed type of concept.
This is his design and we are dealing with Einstein's what I can do here.
Let me go and take some of the boxes so I can go here and take.
So for example I take three boxes one for management plane one for control plane and one for decoupling
and we know that in Austrian solution yes you have three different type of plane.
So one is the nothing but the management plane the other one is nothing but the kind cool plane.
And the third one is the actual data inflow plane with actual data movement happen.
That is nothing but to pick up.
So now I have the three different plane than watch the rule of all these planes.
Now it's very important to understand this that the management plane that you have this will work as
a point of contact so you can integrate this with third party API.
Ah this is like Dubai integrated.
So from here you can create different type of rules policies and you can push through the control plane
from control plan it will get pushed through the decoupling correct.
So not only that we can integrate with the API or we select McLean here.
And let me add all those things so I can go and integrate with the API.
You can integrate with the movie as well.
I can go and integrate this or connect this with the cloud.
So for example I can go and connect with the CMB.
I can go and connect this with containers.
So we know that annex and its exterior supporting containers as well.
And then you can go and manage up to 16 V Center so you can see the capability these things you can
go and manage from NSX manager.
This is working as a for example management plans it is nothing but my management plan.
So once I understand my management plan the lobster roll off the control plan it's very important here
and we'll see that there is some hidden things here when we are talking about the control plan.
So this control plan obviously is the intelligence behind the scene.
And so for example all sort of routing intelligence is where you can go and create a routing related
control.
You can create go and create some sort of policies all the things we can create from the management
plan.
It will push through the control plan from control plan it will go right to the plan.
That's the flow actually so what exactly the control plane is doing that they are maintaining or they
are managing the dynamic a state within the system.
So what other dynamics you have that will be control all the dynamics of the data plane will be controlled
by the controlling threat.
And finally you have the data and all this data plane is again divided into certain portions and even
this controlled burn.
Let me go slowly.
So this is nothing by but the control plane and you will learn about control plane that we have two
different control plane.
So you have something called central control plane CCP.
You have something called local control plane in some of the intelligence we are giving to the data
plane devices means actually this data plane devices are this great airplane components.
They have the local intelligence like local control plane.
So now we can understand better about the management plane rule of management plane the role of the
control plane in the upcoming slides.
We have full slides so I'll read through those things.
Let the data plane on the radar plane is again very interesting inside the data plane.
You have to component and we'll see that that how the plane is divided into two components.
So one component is something like we have say yes it's a host.
And over the years it's a host.
You are managing with the NSX.
And the other part is nothing by the NSX edgy services so we'll come to know that this data plane is
termed as a transport node and these transport nodes either you have the workloads like Williams container
et cetera or yes it's a integrated with the NSX.
Yes it's a huge integrated with an asset or you have the services services maybe firewall load balance
and low balances routing and different services are there.
So NSX it's services inside the company or they are doing obviously the they are there that getting
instruction from the management via control plans all this control they're getting in the data plan
they are writing do changes in their data plan and then they are switching the traffic from one place
to other place.
How many will come to know about all these things like in short here.
You have your management plan where you can use API or the user interfaces you can write certain things
that will go and consult the control plane and the control plane will and struck the data plane.
Now again the data plane having two different portion the control plane having some control between
control plane and the local control plane et cetera.
OK.
So these are the things we have that we can learn here.
Let me go back to the slide and let's continue so once I am in the slide you can see that you have the
management control and data you have manager controller and transport.
That's a very important thing.
A management manager can cool controller data transport.
Now this is the diagram I was talking about.
So now here you can see that we have NSX manager.
It is recommended that you should have cluster of three.
So if one will go down it still you have the higher mobility.
Now in this diagram you'll find it's very interesting that the NSX managed appliance having to think
NSX manager appliance.
Having you can see this big box here from here to here.
So it has NSX manager and it has NSX control plane.
So NSX controller and NSX manager board are nothing but NSX manager appliance.
Correct.
And then he reconsidered the other data plans or data plan you have the transport.
Nor do you have the host workloads and switch it up in traffic.
They are switching their data plan traffic from one place to another place.
And still this diagram is quite busy and it will take some time to understand digest concepts because
by the end of the day this is also a Steve is the end solution.
But these services are the rules for different different planes are tightly copied.
Correct.
So you can see that control management and the control plan they are couple and again the control and
the data plan.
They are also a couple you'll see in the next slide.
So how I can remember this you can remember like this you have management plan you have control plane
and data plan management plan doing all type of management related stuff like configuration and template
database the repository is tactical can it configuration hieroglyphics etc etc. control plan is the
central intelligence see who will provide the control of flow of data in or outside throughout the different
different environments.
For example William hypervisor is cloud containers etc. and they're coupling with the actual work is
happening actual workloads is there the data.
So what's the role of management plan.
You can see here it serves a unique in viewpoint RESTful API CMB automation or any 60 user interface
are we.
So we have the UI other thing that it is being the object management and inventory collection it can
support up to 16 centers containers orchestration area blues as well.
So we have an integration with the cloud as well.
It has it is actually taking all the stack so it has all these tactics information related to configuration
policy template everything actually the management plan is collecting and having with them.
And finally it is working as a database.
That's actually the main difference between the traditional are between the existing network or existing
datacenter so the data center presently and data center related to SD.
So for example NSX key what's the main difference between them and now all this is the end solution.
They have their database and these databases are again really intelligent and they have like redundant
type of databases.
So once we have a cluster of three manage devices they may have Shahed database so whatever is practical
information one of the manager is getting he may replicate to other other databases.
So if one or even two of the B of two of the NSX manager will go down there still they have the high
end ability so that's the key you have that you have the powerful database connected with the cluster
of manager no control plan as I told you that you have the CCP central control plan you have the local
control plan as well as the use of the central control plan central control plane is there you can see
where the cluster form factor provides both redundancy and Haskell ability.
This is in terms of architecture but we will see some slides we have in terms of what control plane
is doing so elegantly that we have cluster or control plan which is providing higher mobility and redundancy
but the what the use of the control plan will see control plane related to routing intelligence related
to policy intelligence et cetera et cetera.
MIKE The main goal here that in this three tier architecture is that you have the management plan you
have the control plane and you have bigger topline now you are never sending data traffic to the control
plane so that means if your control plane is unavailable it's still the data plan they will forward
their traffic.
That's the main key we have and even you have the cluster of control devices even one or two of the
control devices will go down they still get a plane they will forward their traffic.
So we have high visibility in terms of control plan in terms of managing plane as well.
So if the failure of the controllers will not affect the actual movement of the data traffic then we
have the local control plane rolls runs on their transport node so our data plane is nothing but transport
naughty it is adjacent to the data plan it controls and connect to the CCP.
So LCP is connected with CCP.
The LCP is responsible for programming the forwarding entries and the firewall rules in inside the data
plan and that's true.
You are sending the instruction from control plan to the data plan and you have the CCP you have the
LCP CCP is instructing LCP to write the forwarding entries and the security rules in the in their forwarding
table are for example in their hardware.
Correct.
Alright then finally you have this NSX managed appliance.
And if I go back here I can show you the diagram.
So let me go back here because this the key diagram.
So here you can see that you have the NSX manager applies.
That is that having an Asics manager plus the NSX controller.
So it's a complete cluster you can see clear devices minimum three devices as recommended.
And now you have the definition of the NSX appliance.
So we have the management plans the one management plan to everything is in cluster.
And then you have control plan one control and we can think these two they are making the NSX manager
appliance.
So same thing.
They retain their and I mean this is the term you can see Manager Plus policy plus controller manager
appliance.
So each appliance has a dedicated IP address and its manager can be accessed directly or through the
load balancer optionally the three appliances can be configured to maintain a whip virtual IP that are
the cluster IP which will be serviced by one appliance selected among the three.
That's okay.
But to also use air you can see the management and the control control plane and management plan they're
giving one manager appliance and that can have one whip virtual IP or cluster IP where that it can be
accessed and the load across the manager appliance can can be load balanced with the low balances.
So different the user requested are different this tactical informations can be managed by the load
balance and that's the key.
So now we are steady about the management plane control plane and the managing appliance.
Let me quickly show you a little bit related to the use of the control planes or what exactly control
plane is doing control plane computes all femoral Orion demonstrated based on configuration from the
management plane disseminates topology information reported by the data plan elements and pushes the
state less configuration to the forwarding Indian it you can see this term is very important the stateless
configuration to the forwarding and then so you can see that the management plan as already we have
discussed so management plan they are sending the instruction to the control pin and then they are writing
those information inside the data plan the set of objects that control plan these include whip virtual
interface logical network a logical portal logical routers IP address and so on because again it is
dealing with how we are going to control the system correct.
Finally we have the data plan so what's the user data plan as we have discussed that we have two different
type of data plan component one is the hypervisor transport node one is the edge node and again you
can refer the planning diagram towards the use hypervisor transport nodes that hypervisor prepared and
configured on any sixty later we'll discuss about this in recent.
So for example in radius provides network services through the virtual machine running on those hypervisor
annexes we currently support we have E6 I am giving him hypervisor the NYPD is implementing it giving
him give him based on the open switch I will cover this in radius and options which way at the moment
you understand this that you have nodes over either yes X say are over k we m manage via the NSX that's
the trans transport node then the second component you have the edge node is no doubt nothing but a
collection of services the collection of services means you may have firewall you may have learned balancer
you may have.
Suppose you are doing some sort of netting you may doing routing etc etc. So different type of services
the VPN etc etc you are doing with help of each node now or this age node will do that the VM willingness
XP edge nodes are a service that lines this service means all type of services that we discussed dedicated
to runtime centralised network services that cannot be distributed to the hypervisor they can be instantiated
as a beer maker appliance are virtual machine form better they can grouped in one or several clusters
representing a pool of capacity.
Very simple you have workload you can think like you have workload hosting you were either giving him
or he is excite all you have independent either bare metal are formed for two services in the data plan
so actual data is moving inside the data plan and just for the reference.
Again I have given this diagram here so you can see that you have either this inside the data plan or
you may have either this inside the data plan.
Now you may be inside the private cloud or you may be inside public cloud inside public cloud you have
all these things hosted so portion 1 and portion 2 I believe you are using Ada Lewis as zero on any
type of cloud.
So this is where the escape of data plane hosting option or data plane variation actually they are of
two type either this transport node or NSX each collection of services are the workload correct light.
So this was the architecture and what I'm going to do that in the next section I will go and revise
or we have a study a lot.
In this particular session and there are so many terms so many new terms we have to learn and this.
So in the next section I am going to do the revision or to eat whatever we have a study in this section.