We have summary of all the components used inside NSX key so we know at this point that in this askin
solution obviously we have management plane we have control plane we have great airplane use of management
fluent plane.
Is that a point.
A single point to manage the entire NSX fabric.
It has decentralized database.
It is in a cluster format.
It is taking all this tactical information from all the places inside the fabric.
It can do query.
It can configure it can create certain type of reports as well so it has all the management capabilities
and obviously it can be integrated with the API correct.
So that's the management plan.
Then we have we can say that we have collapsed management plus control plan we'll see in the next slide.
So we have a control plan as well.
That's the intelligence we behind the scene.
So all the devices when they want to see the routing visibility are if they are looking for routing
visibility this controlled plane is working as it out reflector and he can reflect that out cross domain
from one place to another place.
Apart from that control plane that they are creating the rules and they're putting those rules are pushing
those rules inside the data plan devices.
So data planning devices they can program their hardware or we can say that they can program themselves
and then they can act like a plane is simply use forwarding the data so we can see their definition
that performance paperless forwarding our transformation package based on tables populated by the control
plane.
So they are getting the instruction from the control plane according to that.
It is forwarding the data.
So we have management plane control plane and get a plane knowing is one thing here that we have the
NSX manager to it for.
We are using the simpler simplified version of Gwi and we have so many things added inside the NSX manager
NSX a to do it for.
It can integrate with various things that we have discussed already.
Now the other thing here you can see that we have the NSX controller cluster towards this NSX can go
local this also we have discussed earlier that NSX manager with the control plane and if they're in
a cluster of minimum three so we can think as airplanes for three airplanes in a cluster providing higher
mobility that's nothing by the NSX control last year.
And area can see their definition as well.
So NSX manager and NSX controller services both exist in the controller cluster for the high visibility
have endorsed the use of the control plane we have is there to a full control plane guard grasp its
failure rate airplane will forward the traffic there is no impact right now we have the edge cluster
going forward we can create the cluster with respect to NSX controller with respect to edge so we have
the higher ability in terms of devices as well external network how my and access NSX key fabric will
communicate with the outside world so any outside are outdated or maybe any outside switch or the breeze
network that they want to communicate it's the external network then we have the concept of transportation
and that's actually very important we important because in NSX you'll find that you have transport June
you have host transport June you have edge transport jet so let's understand that what's the meaning
of this transfer John this transfer John as the definition such as that collection of transport nodes
that define the maximum span of logical switch a transfer John represent a set of similarly similarly
provisioned hypervisor and logical sets that connect to VM to those hypervisor it's simply this feeling
that the transport June is something that having the host host is nothing but the hypervisor s and those
who are still connected with logical switch or segment we have the concert segment and obviously when
you have the host those host having the beams so you can see that they are the collection or the set
of similar hypervisor logical switch and Williams host straight over hypervisor static transportation
now is a broad term because in transportation we have host for transport node by the host transport
node host means hypervisor so the hypervisor node that can be a registration that's the key here.
So when we are talking about and as ex D fabric so that means whatever hypervisor are host.
I have those holster hypervisor should integrate with NSX.
Correct.
That's the key here.
You have.
You can see that hypo is a law that has been registered with NSX key management plan and has NSX key
module installed in it.
So NSX key module has been installed here.
Then really they can get the control instruction or they can get the instruction from the manager.
Correct.
So for a hypervisor host to be part of an X and a 60 overlay must be added to NSX the fabric.
That's true that the host transport host integrated with NSX team manager.
Then we have Ed's transport and we have discussed about this in the early section.
Its transport means you have edge node that is registered with NSX we manage it so its transport is
nothing but the edge plus NSX key registration they have now.
Here you can see that the transport node host the NSX service routers and associated with the year 0
and Tier 1 doubters we have discussed about this DL and the U.N. hierarchy in the previous section including
uplink connectivity the external network as a straight full service such as an active.
So what's the bottom line here is that your edge so whatever edge I have edge devices edge.
Those edge you select me right to hear properly those edge they are installed with an X NSX team manager
and we know that edge they can do the services related to IP routing they can do services related to
IP services they can do routing plus various services that we have discussed like a nag load balancing
the etc..
Provided you have common configuration a template that you can push through the devices and we may have
different type of profile that we can create and push from the management to the control plane to the
up lights and now you can see that we have a last minute control man management control Caplin and his
its manager control cholesterol and S6 Edge cluster external network transport June transport hosted
transport node edge transport node then edge NSX node profile like many things we have so if I summarize
little quickly here we can understand here that you have the management plan the other control plan
you have the good airplane inside data plan you have the host packages everything is integrated we have
discussed about this you have the host and you have the VM you have the logical switch as a function
you have the edge devices who can do routing who can do service functions is still we have so many things
we haven't discussed more about the logical switch are the segments we haven't discussed about the other
hypervisor so of whatever things that we can do in other words the end solution everything we can do
here as well.
Maybe they're terms that we are using as different.
But the operation more works the same.
What's the main difference we have inside the NSX the.
And the ACA.
These are the two most popular is the data center solution at the moment that everything is integrated
inside and is X key so they don't have to go look outside come back.
They're going to have to integrate with some third party devices and do some sort of research regulation.
Everything is there but everything is there in one type of a thing like one box inside one box everything
is there but you have to differentiate it or.
Where is the control plan management plan data plan logical suite routers load balance etc. etc. So
this particular section will help you to access fine of what type of terms we have.
What other times are going to use.
We have a gateway router it can be easy to our once ahead we can see that and it's a sphere routing
entry that provide distributed East-West routing a gateway router also links to 1.0 with DS routing
it depends that what type of design we have but we can have great routing that can be linked with these
zero T1.
At the moment we regard excel like this let us know select where and how it can be used.
Then we have our outer logical put wrote a large logical port is nothing but which is connected with
logical switch.
So you have a logical switch and you have the logical outer to the service routing the logical network
port which can be attached to either a logical switch segment or a physical network uplink so you can
think that like normal a router it can go and connect with router or it can be connected with switch.
So I went into this can dial 3 other interface can be a little so it can be connected with routers which
is like normal Cisco term that we use to learn that we are that easy route and T1 gateway as diesel
as a logical outlet into one as a gateway to this we have this because one thing I want to tell you
here that the upper road so whoever they're in the top they are running BGP and BGP is actually very
important and you can think that BGP is there and let's say we have the out reflection type of features
so whatever data plan road they are learning they can reflect to the other decoupling devices and this
physical this device can we go outside as well.
So you may have different eye for concert means you may have and communication or you may have been
in decades going to the outside.
So how you're going out coming in everything because will be dependent upon the T Zero because that's
the last router or the aggregator we have inside the NSX fabric.
Matea they're learning the BGP they can be active active active the standby library the Tier 1 also
can be active active and active a standby so we'll see here.
You can also reconfigure the active a standby letter and we'll see in the data here that the T1 Tier
1 can be configured as a active active or not as per the this thing taking forms.
Obviously the weaver site and I haven't seen that in the NSX t this gateway can be configured as an
active active.
So we'll see that later on indicate assured that can configure the key when as a active active as well.
And what type of support would design and all those things we can discuss later at the moment.
We are just going through that what type of domes we have and we have a last minute terms that if we
count one two three four five six seven eight nine ten eleven twelve thirteen fourteen fifteen sixteen
so how are we going to sixteen terminologies used and is still we have to.
So let's quickly go and complete this.
You have the segment and logical switch think like your L2 switch but it can be expanded.
It can be it can be distributed it can be reachable to multiple host.
So the next thing here it is a span through various hypervisor and hosts.
We have the logical switch.
So this thing also you can check and read it.
But let me quickly redo these lines so segments can segment so that's the term we have in the 2.0 for
it's the segment into your three and previous version it was the logical switch segments called logical
switch in the previous version of analytics are API entities that provide what you layer to switching
for both of them and they're altering enterprises.
Right.
Segment give still in network administrator the logical equivalence of a two sets so you can think this
as as agencies and it has it can be expanded across various hypervisor.
Obviously you have to connect this logical switch with the Williams Williams They are connected with
the logical switch and then they can pass the traffic then we'll see later on much more detail about
this in the packet flow and where exactly correcting then we have a logical switch port obviously in
the logical switch the ports are logical switch ports and this logical switch port reports applied switching
profile port is taking a status just like Cisco Technics 2 9 6 0 switch where we have the interfaces
here we have everything logical then we have gave him opens it's because we know that and X is actually
supporting mighty hypervisor.
So for ABM we have the open switch and the things are almost seem really important thing here.
You can see that they can do the same to logical road traffic.
William to William.
Traffic forwarding and they're using Tsarnaev as a tunnel encapsulation protocol.
So we have like more openness standards going to be use inside and then 60 going off widely used is
the giving him open switch.
Likewise we'll be we will have open suites for Gen servers then give him and other Linux was hypervisor
as they can be integrated inside.
And it's extreme for these type of communication like William to William and William to logical road
traffic.
Then we have the concept of overlay network.
Then we have the concept of find alien network as well to overlay network agency overlay network for
NSX the fabric logical network implemented the using layer two in layer through tunneling will see this
thing later on.
Which led to two later trending such as such tag data quality seen by VM is decoupled from the physical
network.
No at this point of time if you know little bit of Cisco ECI then you can understand that you have Mac
in IP encapsulation etc. So layer 2 is nothing like Mac.
And then you have layer 3s IP encapsulation and actually we are using a week's lan very heavily and
that is UDP type of encapsulation but we'll see later on all these things.
Let's quickly move and see how many terminologies are there.
So we have this overlay network that layer to in layer threatening.
We can have the physical like network interfaces on physical servers that the hypervisor side providers
they may have uplink terms of physical links.
Then finally we have two more terminology.
We have v neck so so far the easiest one in this particular presentation is the meanings of whatever
guest operating system you have that is term as a virtual machine.
Those virtual machines have been and they have their unique IP etc. But these vinegar can be connected
with a logical switch and then the traffic and forwarded from large closest to from one minute to whether
we think it may go from one we need to the gateway devices and from there it can go to the outside et
cetera we will see the traffic flow on video the virtual network interface we and I.
What is the VNS this network identifier associated with a given logical switch as Layer two segments
are created in NSX and associated VNS.
So when we are talking about the logical switch the associated with an eye is attach with that.
And this Vienna is used in the encapsulation encapsulated overlay packet and facility Layer 2 separation.
So we'll see that the VNS used where it is going to be used but it is associated with the logical switch.
Now the final slide for this action is this that tunnel end point.
Again it's very much like Cisco Application Centric Infrastructure where we have the final endpoint
tunnels.
So when you are forwarding the packet inside the fabrics as a whole this is my NSX Steve fabric.
Then the packet will come it will get encapsulate and it will go to their destination and other destination
point it will be d capsule.
So basically the tip at that point encapsulation and decaf solution happens the tunnel endpoints enable
hypervisor who's to participate in the in an NSX v network overlay.
This is nothing but you all were late.
Now here you can see that the gap is the connection point equity encapsulation and Dick absolution takes
place and we have the v x excellent encapsulation dig at religion that is again this layer to inside
layer 3 encapsulation etc. Those things will happen at the level of depth the NSX overlay applies a
layer to network over an existing physical network fabric by encapsulating frame inside the package
and transferring the encapsulated form over the underlay transport network so the same thing that we
have discussed.
The cape is responsible for Do the encapsulation and encapsulation over the fabric are we can see the
inside the NSX to fabric or life.
So these are the terms you can see and these germs are going to be used very heavily heavily so you
have to spend what you have done in these slides I am going to upload to this recording that I have
done some sort of restructuring of these terminologies so first of all we try on this carnival the management
plane then tried to understand about the cluster in terms of NSX controller the host and the edge.
So we have actually cluster for the controller cluster for the edge then what is your external network
transportation related to host an edge.
Once you understand the V and the term then will come and we have to study about the routing and switching
stuffs.
So once you understand this then you have the routing related things like Gateway logical road report
what is DLR what is T1 what is is are what is the are so distributed outer and we have the service rotors
once the onus and then it will go inside the switch.
So we have the logical switch logical switch port then the switch are the open switch for the other
hypervisor s and then what type of encapsulation they are going to do.
So we have the open switch open switch we switch open giving him seats then we have the overlay network
an airline network we may have the physical network we have the VM related interface that Dominik and
the logical switch related interface that is the we and I and finally we have the final point wow so
these are the 10 million elite terminologies we are going to use in the upcoming sections.