So our first device that we want to talk about are going to be Our virtual switch is now our virtual switches air going to allow us to have the same functionality on a virtual environment as we would using a physical switch. Now, why do we need a virtual switch? Why don't we just connect our server to a physical switch and use it that way? Well, our virtual switch may allow are different,
virtual computers inside of our single physical computer to communicate with each other as if they were communicating through a switch rather than having to go out to a physical switch and communicate back or having to be all be on the same sub net or all beyond the same virtual land. Now we can set up these virtual switch is just
so they have. So they have the same connective iti as if they were a physical switch.
They can communicate with each other over layer to they can communicate within the same broadcast domain. And we can also use these virtual switches to set up V lance now RV lanes that we've talked about before our virtual lands allow us to segment up our network. So if we're using a single, very heavy duty physical server in order to
set up multiple virtual servers within it,
then we may need to set up a virtual land within that virtual server. Are within that physical server for those virtual servers because we don't necessarily want all of those virtualized devices to be on the same network.
And this also allows us to utilize a single network interface card as a trunk port rather than having to have multiple network interface cards with our multiple virtual lands and then utilizing those network interface cards. So let's take a look at how this works together.
So in our virtualized environment, we have our single virtual. We have our single physical server here.
Now our physical server has its own I P addresses, and it's on, and it's on a particular sub nets on a particular vote virtual land. But we aren't really going to compete. We're going to really think too much about this physical server right now. What we're focused on are these virtualized servers within our single physical server.
These may be certain these maybe servers that provide data they may have
folders on them are shared folders on them or they may be providing Different service is like D H cp or they may be provided providing D N s. It really doesn't matter. But what we have in the middle here is going to be our virtual switch.
Now we have our different computers and our servers color coded, so we can get a better idea how this is all working together.
Now we have our red devices. Here are two servers and our physical client computer that are all on the 1 92.1 68 dot to dot X. That's gonna be our red devices.
And then we have our blue devices here.
They're all on our 1 92.1 68.1 dot exe
if we just had our single network interface card, it would be a little bit difficult for these devices to be separated out into different V lands because that single network interface card is going to send out those packets to a single port on our on our physical switch.
So we need something inside of our server, our physical server. We need a virtual lives component
in order to identify which the land those packets air coming from. Now we do have our different devices segmented into different sub nets. So it would be we would be able to use a single network interface card either way. But we're going to go ahead and identify those on V. Lanza's well in order to better
segment our network.
Now we have a virtual switch here, which is going to connect to all of our different devices
virtually via its standard access ports. So we would set this up and have our virtualized switch here,
and then we would configure it to talk out over our network interface card using a trunk port. Now we've talked about trunk ports earlier trunk ports, essentially what they do before they send out packets. Over that connection, they tag, which the land that these particular packets air from
So before it's sent a packet, say, if
our server here 1 92.1 68 dot to 68.0.3 we need to communicate with our red client over here 1 92.1 68 dot to 68.0.7
are switched before it's sent that packet out over the trunk port would tag that packet and say, OK, this packet is on the red V land,
so it would tag that packet and then it would send it out over the Trump Port. It allows communication between two different switches, which manage the lands, because over a single port, rather than having to have a different set up or not, be able to communicate between these two switches.
Now we have our physical switch
outside of our single physical server. This is our physical switch, and then we have our virtual switch, and our physical switch is actually going to receive that information over the cable that's plugged into it from the server and then identify those packets unidentified, which the land that they're on.
So we'll get those the packet over our trunk port, and then it'll say, OK, this is for the Red Be land. So I'm gonna send this out on the Red V land, and it's directed toward 1 92.1 68 dot to 68.0.7,
and it'll send it on down
the same exact scenario in reverse. If we have one of our clients, say 1 92 don't want 68 that 1.7
trying to communicate, communicate down and over to our servers over the trunk. Port will also take those packets and they'll tag them, and then we'll go ahead and pass them on.
So, for example, if we have one of these servers will say 1 92 that 1 68 that 1.3
performs D h cp. This particular port on this switch
is identified as being the Blue V Land.
So this port on the switch knows that it's already the blue Vineland because this computer won't have an I p address yet. So we can't
segment RV lands based on I p address. Because this computer isn't have an I P address yet. So we have to segment RV lands based on pork.
So this computer connects into our network, and we want it to be on the blue V land. So we plug it into our blue veal and pork
sends out a D H cp request, which is a broadcast request
There are network interface card over our trunk port. Into our virtual switch
are virtual switch. We have set up that our computer that is virtually connected here, and our computer that is virtually connected here are both on the Blue villain. So go ahead and past that. It'll pass that D H Cp Discover message
onto one only through that 1 68 out 1.3 in 1 92.1 68.1 dot four
1 92.1 68 1.4 does not perform the HCP
1 90 through that 1 68 that 1.3 does so then it'll communicate back with our our non i p address computer here. Give it to offer it a D H cp or it'll offer it a Give it a d h e p offer offered an I P address. Our computer will accept it, and then it will assign it
68.1 dot seven. That's the function of our virtual switches. That's how our virtual switches compare to our physical switches and how we can use our virtual switches to allow us to do things such a setup billions and use a single network interface card on our server as a trunk port