This particular session is a very important because we are going to Asgard a virtual machine networking
VM networking and there are so many nice domes that we should learn and know.
So let's start this.
Now you can see that.
What's the problem we have.
So once we have the host and once we have the hypervisor so we know that we have the.
So for example host and on top of that we have operating system multicast operating system.
So I have server host and the guest operating system no problem here is.
So let me try to draw here.
The problem here is that once we have a host and you have operating and kissed operating system the
first problem is that which software element should control the physical network adapter drive.
So here you have your physical network adapted in the server who will control Let the hypervisor or
the guest operating system obviously hypervisor has to control.
But how that's the first thing.
The second thing that how should communication occur between VM and the external resource.
So now in this game that we can see that you have your dreams and you have your server as well now these
servers may be connected with switch.
So for example in two or three switch and then you may have a router or you may have external world.
So now this VM how this VM will come because this VM has their virtual Nick.
So the virtual Nick adapter will come to the server and then it will go to the outside.
Here we have the diagram in this diagram we can see clearly that how these values will go and communicate
to the outside this is nothing but south to north and north south traffic.
So how this will happen that's the second point.
Second challenge.
The third challenge is that how the host will communicate to each other.
So inside that I may have so for example 25 Williams So how this is to with traffic or east to west
communication happen and who has the control over this communication.
So do the the cushions the solution that we came with in early 2000 that was installed this particular
host this particular hypervisor at that time you have network a standard switch.
So you have host standards which are real Sphere standards which we assess.
Now once we have the resources that means this particular we assess obviously we have the Winik from
the research you can think this as a switch in between.
So now this is the switch and then this switch will control the east to west or north to south to south
to north traffic et cetera.
Now once we have these particular standards which are the standard switch in terms of use we are a network
a standard switch will see the problem further we have some problem.
So before going to that particular problem let's see this particular diagram here.
So here clearly will see that you have your physical infrastructure.
And if I tried to analyze this with a switch you think like you have one switch and here we have not
just to analyze this particular diagram here you have salt mines here you have server virtual server.
So here you have virtual server.
And here we have for example outside put it out and domain.
Now we can think like this this particular Stander or to switch or virtual is trying to switch that
to you know in Cisco domain.
We used to be a steady about access port so access will and then access will end 20 access M.A. access
will end party etc. Then you have one interface that is going towards the outer that is nothing by trunk
so you can think at the moment your strength is nothing but the uplink going toward the external low
tech moment and then you have this access port.
This access ports belonging to certain wi Williams you can think this as a port.
Group will learn about Port group in the upcoming session.
Where do you think this as a port group.
And you may have certain a specific port groups as well certain of specific of import as well that is
that may be used for management traffic that may be useful for tolerance that may be useful motion.
So here you can see that the blue color is nothing but complete William related ports.
And there you have the uplink or your physical interfaces.
So here you have port group play related to management port group related to re motion maybe port group
related to fight ordinance etc. Then you have port group related to test port group related to production
and this is over one host.
So this is nothing but host one and same type of thing.
That's a problem here.
So if you want to scale up same type of port group with the same name everything you have to create
a cross.
For example if we have 25 host 25 E6 I was then you have to go and create the same name throughout.
And actually we have evolved to the distributed virtual switch that we would discuss later on.
But yeah here you can see that production here you can see that test and port group so the active boots
having common properties are common properties inside the same group a group of common properties.
Anything you can tell that support group or any other emotion you have the management.
So here you can see the uplink and you can see the downlink or you can see the VM link.
There's nothing work might be VM link and this is nothing by nothing but my uplink everything is defined
inside the port.
Group common property active Bute group a grouping of common property are common tasks things so clearly
have a VM one guest operating system one guest operating system two three and four for Williams two
of the reason they are part of for example cells two of the Williams for example they are part of nature
so they belong to each other they belong to cells like that you can group the ports and you can connect
with the virtual machines so you can analyze like your normal Cisco I also like this but again no at
this time we should understand that virtually how they look like right we should understand that to
stop know what is the issue we have when we are using this kind of switching system in that oh you can
see that the standard switch is created at the moment we have you will install E6 say you have your
reassess up and running.
Now the problem here is it switch on every year excite must be created and configure individual so you
have to go create go create etc. This can be time consuming although we can do some sort of automation
but still it is taking some time to do this.
The second thing one important note when using we as we this kind of switch and some of the higher mobility
features with we center in the standard switch must be name you have this naming convention so your
naming should be common through how the V sphere domain.
And then also know that the features like input our netbook Io control LLP network will check and the
backup and these two means some advance features they are not supporting in the standard switch.
So these are the issues we have and that's why we want to use the distributed virtual switch we'll see
in upcoming sections.