Let us do the summary or whatever we have a study in the last section.
We have a management plan.
We have control plan.
We have a plan.
Now the management plan and control plan data plan.
All they are mixed and we have to separate them.
And we should the study we should write some points okay.
Management Plan your functionality is this control plan.
You are divided in two part data plan.
You have to segment it still you can see here in the data plan although they have the two segments.
They have the NSX is they have the transport node is still data plan maybe in the private cloud maybe
in premises maybe in the public cloud maybe over blue as are any other public cloud.
So we have to understand this clearly that what's the role of different components and where they are
situated.
And for that we have this particular diagram.
This is actually the summary that what we want to study that.
Okay what's the NSX MANAGER What's the NSX controller.
What's the NSX managed appliance.
Why I need three VM is I mean obviously we need a redundancy and higher ability.
So we have three Williams in higher ability John are in the cluster then we have the data playing devices.
Once we understand this once we understand okay in the control plan I have a centralized control plane.
We have localized control in north central and local control plane we have transport nodes et cetera.
No what we can do here that we can go and compare the NSX and the NSX to terms because what happened
in the 60s.
We have symptom of retailing different fragment.
So first of all if you see this part of diagram you can see you have Tier 0 Gateway you have Tier 1
gateway.
Now this deal when Gateway is connected with different different segments in NSX it was a logical switch.
So let me show you the comparison in normal NSX that suppose if we are coming from NSX domain.
You'll find that in NSX it was term as an advanced API you I object but inside NSX stood out for going
forward.
This is declarative API object so the name of the logical switch is the segment the physiological router
is Tier 1 Gateway the key one logical routing the router is Tier 1 gateway to the zero gateway to when
Gateway and then this implies this port is done as a service interface you're in this group your IP
said Max it is term as a group actually in the ACA applications and take for actually now it's very
much similar to NSX D because whatever we are restoring struggled so far ACA is also supporting those
things ACA is Cisco data center applications and centric infra where it is also anywhere to anywhere
we can think like it is supporting everything so containers bare metal virtual world hypervisor this
cloud everything and in the 60s also supporting everything in ACA the end points very nice name in ACA
the end point so whatever virtual are beer market makers are different groups you have the termed as
endpoint an inside endpoint you may have IP Mac it's a great set that those ingrates.
So that is term as a group firewall section is security policy these are actually the generic name gender
term and maybe you write those policy and those can be can work against cloud native active user cloud
native name are cloud native I can say that object and then again those things will be written over
the cloud that they actually will let the same policy once you create you can reuse either in premises
in the cloud.
So now you can see that these things have been simplified.
This is the simplified API object or declarative API object and going forward NSX stood out for we are
going to use these terms so in upcoming section we'll see different diagrams logical diagrams and other
terms but we are going to use these terminology in the upcoming videos.