Let us understand the logic and the topology.
What type of capacity we have in the lab section.
Now here you can see that we have the host and on top of hosted we have the guest operating system like
VM for TB app and will.
This is something like three tier application architecture where you have web app and we over one year
excite and then other iOS 6.
That is again inside a cluster called Reason is zero.
Then you have cluster for management and here you can see that we have the NSX Edge Edge when n is 2
First of all there inside the cluster gadgetry and edge for the air inside the cluster.
And then you have E6 I inside the management cluster.
Then we have other compute and there we have the Web 3 overcame him.
So we have a mix of E6 AI and the giving him the hypervisor as host and the guest operating system.
Now logically how this diagram look like it you can see that we have the segment for web that type is
172 116 segments for app that having IP twenty in third octet and then 3 0 cutie.
This is connected with Tier 0 Gateway.
This going to the uplink and then you have the outside world.
So you have your inside while here and then it is connected with the outside by direct.
Also here you can see it's a very straightforward simple topology nothing much here but there are so
many terms that we need to understand and we are going to use during this training.
So terms we have so for example we have Tier 0 Tier 1 Gateway routers.
What does it mean.
So you may have tier zero connected with Tier 1 and then this year one they may be connected with the
logical switch or the segment so maybe segment 1 segment to segment 3.
So they can think like you have the logical boundary and the physical connectivity it's not required
or it's not mandatory that always you have this type of structure you may have tier zero connected directly
with the logical switches are the subnets depending upon what type of use cases we have like.
Same thing here in scenario in this scenario layer 2 segments are connected technically to the TS equally
it happens.
Now these Gateway having two component one is beer that is nothing but distributed outer and one is
the ether.
So one is doing a routing things he has the routing capability and one function it has which is doing
the service routing.
There they are they are doing services like a VPN Lord balancing Nat ATC correct.
So you have to function service and routing.
And here again see some of the definition about that.
So these are is kernel based and span across hypervisor providing local routing function to those Williams
that are connected to it and also exist in any edge node the logic allowed to respond to it it's very
much like a router and program is kernel based program.
It is span across the hypervisor.
That's it.
It's very much similar to the NSX good or three or NSX where this city R represents a DLR distributed
logical around.
In the earlier version of NSX then we have the Acer as the name suggests that this is responsible for
the services.
Services like NAC load balancing DCP VPN etc.
Service out are deployed on edge node cluster that is selected when that easy to do and is initially
configured.
It's actually very straightforward.
If we go and check the diagram it is actually easy to understand.
So if I try to do out here you have zero you have T1 and this is connected with a logical segment.
Now here you can have routing here.
You can have services we'll see we'll see later on when we'll go much too deep inside this 60 architecture
and their functions and rules and different different components.
Then we'll see all these definitions and how it can be used correct.
Again you can see the gateway rotor in any society always associated with the R regardless of where
it's deployed at the level of D zero or T1.
It will also associated with its are created if the following cases are true.
So if you want to use the services or they take what out there is it easy to rotate even if no estate
services are gonna be there at the moment.
Do this thing that Okay you may whenever you have Gateway.
You have a routing capability as a gear and you have the services capability as a S.R. so who can do
all these functions like an act L.B. DCP and are reaping etc..
Right.
So this was the basic really basic understanding about the topology and a few of the terms in next session.
Next recording I will go and will check how many terms and terminologies that we have so that will be
the summary type of access I will.
Atlas will come to know that what type of terminologies we have inside the 60.