So let's talk about virtual servers. Now. Our virtual servers are servers that we virtualized that provide us with a full service. So say we may have a virtual server that performs D H CP or a virtual server that performs Windows deployment or virtual server. That is, a file server or
multiple virtual service, which provide multiple service, is
so it's essentially like having a physical server except in a virtual environment.
Now these virtual servers can provide us with the extensive bility and can provide us with all the functions of an actual physical server without having toe have a full physical server dedicated to them. So if we had, if we need three logical servers,
but we only had are we only have the funds for one very, very good physical server,
we can take those three logical servers and put them on that one physical server
with virtual servers. This allows us for logical distribution, and scalability of resource is so we can logically assign different functions or different different jobs to our different virtual servers and weaken scale. How much? How many resource is our dedicated to each individual server, based on how much they're used.
$2000 for three servers, we may pay $5000 for one really nice server That can give us the functionality that we need for those three servers if we only use those 3 $2000 servers up to 50% of their capabilities.
But we still need three separate servers that instead we just purchased with 1 $5000 server
and install the three virtual servers on it.
So it provides us we can scale. Those resource is if the time comes when we say, OK, this service being used Maur, and this is being used less. But if we have three physical servers that we can't say, Well, we could do this, but we wouldn't want to, especially if they were different physical serve server types. We wouldn't want to say, Oh,
I'm gonna steal some RAM from this physical server and install it in this other server
or I'm going to swap their CPU use because this servers being used more and this one's being used less and this one has a stronger CTU. That's not what we want to be doing in our shop so we can install that one strong, powerful
physical server and then the multiple virtual servers on it and then using our virtualization software is using our hyper visor weaken scale. The resource is between the three very easily on Biff. One is being used more. We can give it more power. We can you dedicate more of our resource is, and then, if another one's being used less, we just
lower. The amount of resource is that that one has.
Now these virtual service can communicate over our physical network interface cards. Justus, a physical server, would, um, and we can use just one physical network interface card if we want to install ah virtual virtual switch. Or we want to allow our hyper visor to run a virtual switch between between our servers. But if
necessary, we may actually decide to install multiple network interface cards
in order to allow us to load balance our network interface cards better and to allow our virtual servers Maur more room to talk on the network interface cards rather than having to share that one cable with everybody else. So that's really up to our situation that's really determined by our situation
and determined determined by how much network connectivity that we need.
So let's take a look over here at our diagram and it illustrates are two different points.
Now, these air to different environments that we have set up. These are two different workplaces. One is a definitely more of an enterprise type environment, and another one is going to be our small office environment.
Now, in our inner type prize environment, we have
300 client computers,
and all of these 300 client computers are going to be on the same. They're gonna be on the same sub net now.
Actually, we will go ahead and
And we're going to have 100 client computers on
sub Net 100 client computers on sub net, too,
and 100 client computers on our sub net. Three.
Now we have three physical servers
that are dedicated to these three different sub nets. They may be doing everything from acting as domain controllers toe acting. His file servers toe to performing D H cp or D. N s really just depends on what we have them set up as, But we're going to say we have three physical servers for the sub nets
Server one. Our server three is going to be for our green villian. Our RV are green. Sub net
servitude is gonna be for our blue sub net
and server one is going to be for a red sub net.
Now, each of these servers
provides jar provide functionality are connected to ah 100 client computers. Now,
in this situation, we really need to have these three physical servers or in our shop. We need to have these three physical servers. We could go out, we could go out and we could get the equipment to start up a large date of very large data center if we needed to and set up extremely powerful servers which provide
us with the extensive bility for
virtual servers and clustering and fail overs. But we don't really have the funds to do that. And we don't really know what We don't want to sink that much money. Our management doesn't want to sink that much money into this. So, really, in our situation, it's more cost effective
and it's better for our environment. Just have our three physical servers
because we can purchase the servers. Maybe we purchased 3 $2000 servers or 3 $3000 servers on each of these servers are almost always functioning at about 60 to 70% of their max. Resource is
if we were to try to go out and buy. And we were if we were to try to go out and find a device which would allow us to host all three of these servers,
providing functionality for 300 clients on one single device, we'd be looking at a much, much higher price tag than what we paid for these three physical servers. So we wantto way evaluated our network, and we said, OK, it's better to have our three physical servers for our 300 clients.
Now we switch over to our small business, where we have 15 clients and we have these 15 clients, for whatever reason, segmented into three different V Lance say we have our back office villian say this is a small, small
environment. Where we're providing service is like it's a small grocery store
or a small hardware store, and we have our back office computers. We have our computers that we manage our accounting on, and we do our payroll on. We have five of those, and then we have our point of sale computers that we ring up transactions. That
and then we have five additional computers that do everything from being the computer that we have over in the paint department, where customers can go on and they confined different colors. Thio computer that we have over in the the notes of the nuts and bolts department work or customers can go on.
And they confined what the different type of bolts that they need, depending on which item that they're using.
So we really need these three distinct v Lance because we don't want our custom. The computers are customers are gonna be on to be connected to either of these two different computer environments. And this visits this subject in particular, our point of sale. Sub net. Our point of sale of the land really has to be on its own V land in order to function properly
with its point of sale server.
So everything needs to be on three distinct the lance and everything has their own servers that provide them with provide them with different
functionalities, provide them with different service is
but Our small shop doesn't want to go out and buy three separate servers because we don't have the funds to. If we were set up these three separate servers, they would only be running at our computers and our paint department and our customer computers fluctuate. They would only be using between 10 and 30%
of their max. Resource is at most,
even if these were lower in servers are point of sale. Computers are using very, very little. Resource is they're not really doing anything at all other than using their own local resource is, but they need somewhere to save their data. So we get the idea. We get why we don't need to buy three actual physical servers. But
we do have this one pretty hardy we paid about. We got it on for a good deal.
It's a decent server. It's not anything super high into the line, but we don't We don't need that. We don't need anything to be performing super really, really. Resource intensive service is we just need something to have data, something that can provide us with D A C P. D. And ask things like that.
So we set up our one server and within that one server
we set up our three virtual servers. We set up our hyper We we just have a no up. We don't have any operating system on this single physical server. It just acts is a hyper visor. And that hyper visor hosts three virtual servers.
Now, in this set up, we have our virtual switch
and our single network interface card.
Now our virtual switch is going to have
the cable running out of it, acting as its trunk port.
So are its trunk line.
And that's going to carry the data from our three different servers on our three V lands over to our physical switch.
Which service is our administrative computers, or point of sale computers and our customer computers are 15 computers.
now we have our three logical servers that are completely logically distinct that are on three separate villains. But we didn't have to go out and buy three separate physical servers. So this is definitely more cost effective in our AR 15 computer model,
then in our 300 computer model, and we see why we would use these different scenarios we would use thes different setups
in each of these different models.
Now, in our virtual model down here we have a single network interface card working with a virtual switch in order to provide Are different, are different lines out. But say we don't have just one switch servicing these different computers
say this servers back in our administrative offices. So the server is physically located near
and then our point of sale computers are all up at the front of the store and are green are green,
be lan. Our customer computers are scattered in multiple locations during in the store.
So when we did all of our network wiring, we actually set up
three distinct switches. So we set up our three distinct switches. We have a red villian switch,
our blue villain switch, and our green V lan switch.
Which service are different sets of computers
Now. We could still utilize our single network, and we could still utilize our single network interface card. We could take our single network interface card, have a trunk line going to our first switch because both the server and the switch are located near each other and then set up
access. Or we could set up additional trunk ports that are going out to
the are additional access ports rather that air going out to these different switches, providing the computers with their functionality. But we don't really want to do that. We don't wanna have to manage this additional switch and this virtual switch. Or maybe we're setting this up in an environment where
the computers may move around a lot. These point of sale computers may need to be switched out. This customer computers maybe moves around quite often.
And they this shop doesn't have a full time I t person who understands and knows how to manage this virtual sweat. Are this this physical switch and knows how to manage this virtual switch
we don't set it up like this?
two additional network interface cards
no longer use a virtual switch to manage RV lands are hyper visors still managing our network connections. But we're not gonna do so in a virtual switch. Fashion
have are three separate
and then, logically, we assign our first network interface card to our greeting villain. Our second network interface card we assigned to a red villain and our third network interface card we assigned to our blue V lamp.
logical virtual servers
each have a physical, physical network interface card assigned to them that they use.
our feelings. Are our v Land's going accordingly?
And now we don't even really. We really don't even have them set up so much as villains anymore, as we do just physical network interface card assigned to the correct components so we can see how are different. Um,
we can see how we can see now. How are different networks
maybe utilizing different types of different types of setups for virtual servers or physical servers. We can see how virtual servers may be better in certain environments, and physical servers may be better in certain environments, and we can utilize our different physical servers and virtual servers
for providing us with
scalable resource is or non scalable. Resource is, and how our virtual service can communicate over either one physical network interface card utilizing a virtual switch. Or we could install multiple network interface cards so our virtual servers can have more use of the band with more use of a single network interface card