So, guys, let us discuss the real world example where the LAN imposes its limitation on the topology
deployment.
So you can see here that we have a company called Amazon Corporation, and the company has a building
which has three floors here.
That is floor four, floor three and floor two.
And you can see that on floor four, there sits only a testing team, whereas development team sits
only on floor three and management team folks sits only on floor two.
Now the company has deployed an L-3 router, and this L-3 router is using its three physical interfaces
to actually deploy the three subnets called line one, line two and line three.
Right.
So you can see that the cable one is actually going to the fourth floor.
And we know that on fourth floor, all the employees belong to the testing team.
Right.
So all the employees of the testing team is actually connected to a subnet.
LAN one.
Fair enough.
Now suppose tomorrow Amazon cooperation recruit an employee for the testing team so that employee is
actually forced to sit on the floor for.
Why?
Because that new recruitment belongs to the testing team.
And it is the requirement of Amazon network deployment that all the members of the testing team needs
to be connected only to line one.
So you can see that it is imposing a positional constraint or it is actually imposing the immobility
on the position of employees in the building.
The employ of the testing team simply cannot move to the floor three while being connected to its subnet.
LAN one.
Right.
And the same applies for development team and management team.
So you can see that the company would not like to impose such type of constraint in terms of mobility
of employees in the campus or in the building.
It will cushion the productivity of the company.
Definitely the ideal deployment would be such that that the employees of any team should be able to
sit and work on any floor of the building while at the same time it should stay connected with its subnet.
For example, the employee of the testing team should be able to move to floor three or should be able
to move to floor two, while at the same time the employee should stay connected with LAN one.
So this kind of topology deployment is not feasible using local area networks, using LAN technology.
If you try to deploy the network in such a way that employee of any team can move to any floor of the
building, then you will have to deploy a lot of cabling on all the floors of the building.
For example, Cable one should be deployed on floor four, floor three, as well as floor two.
So that employee of the testing team can be seated to floor three and flow to also.
So I think I'm able to describe you the real world problem that comes with the LAN technology.
So for an employee to sit in subnet that is this is LAN one, he has to connect himself to cable one
only and hence need to go to floor four only.
Right.
And moreover, you can see that at the same time we are eating or occupying physical interfaces of an
L3 router.
So you can see that we are consuming three physical interfaces of an L3 router in order to create three
local area networks.
We will see later that villain technology would allow you to create as many.
As many local area networks as you want, while consuming only one physical interface of an L3 router.