3.2 Virtual Machine, Network, Hard Disk Creation Part 2
5 hours 8 minutes
eso Basically, that's what we're gonna get started on today. So
virtual switches. So the key to understanding virtual switches is realizing
that is truly a switch. It just like a physical switch. There's no
pretty much no difference between them. The way one operates is exactly the same to the way another operates
s o You may or may no have come across the OS I model. So the overtime model is the open systems interconnected.
This is a, uh it's a set up which basically addresses how data passes through a network.
Um, so have I got my ears on?
Can you know? Here. May,
uh, we have a look here.
No, I think he's going. Yeah. Why is it fun?
I thought wondering if there was there was a problem there. You get me worried.
Well, it's the Eric,
uh. Yes. So, um, the open systems interconnect.
It's, uh, the model in which data passes through the AI network. In general, it's a bit Maur than what we would cover here.
Um, so but to go basically over it,
um, the the entire OS I model.
So there's several layers.
Um, So you have a physical layer
that you have data link
s o data link his things like Ethan. It,
um the frame of the packet, the encapsulation of the packet, that kind of thing.
Then you have network God. Let me see if I remember these network
transport. So the transport, the data, the session,
the presentation on the application.
it's a bit more than what you might need. Thio kind of understand virtual switches in hyper V. Certainly you don't need to understand the other side model to get it working,
But it's nice to remember now if you don't want to remember, if you don't have,
if you have the same brain, I do, which means you won't remember all of those letters. I have a little kind of saying in my head that I go through, which reminds me of it
on dhe. The word in each. The anagram of it is so it's a P S
t N d
Yes, that's right. So the way it works is it's all people
seem to need
s so that that is the first letter of each of those matches. So you've got,
uh, that's going down from the start from the bottom application
all people seen transport network
Uh, and physical.
You can turn it the other way around if you prefer to remember it from physical first, which is
please do not throw sausage pizza away, Which I'm a great fan of pizza.
I wouldn't put sausage any, though. That's just me.
Probably got a few people riled up with that one.
Um, yes. Oh,
this sits on layer to off the other side
s. So you're basically looking at wth e, uh, datalink level.
Um, so if you're going through P d N T S P A. So please do not throw soft peter away.
It's the do
so data link.
basically, what that means is that is working on the actual packets itself. Yeah, and I know it's It is awesome thinking it's the only way. Remember, I'll tell you what, in 20 years of i t.
I will never forget the sausage pizza acronym. It got me through so many exams,
works every time.
So So what it does? Is it direct packets to Mac addresses? Now Mac addresses a Mac is a media access control. So when you say Mac address, it's a media access control address. This is a unique I D. That's handed to a network interface.
Eso, your network interface port on your motherboard, will have its own Mac address. Your phone will have its own Mac address
tablets, computers at work, laptops. Everything that has connectivity on a network has a Mac address, and they are unique.
So that's what it does. Is it it? It uses it on direct a packet to a Mac address, as opposed to a a NYPD address or anything like that. So it's
works much, much more secure, much safer. It also handles V land. Tagging of the land is virtual land tagging. What this means is also known as frame tacking.
it helps identify which villain virtual land.
A frame is being sent to frame being the data link that the item inside
the data link
s so that it can handle the land tagging as well, Which is handy when you've got lots of virtual networks flying date around everywhere on the system. You want to give each villain each virtual land its own. I d just stopped from two and work your way up. The reason you don't start from one hopefully one is your physical network if you don't have other villains in there
Generally, what most people do in a network environment as an example in the real world
is they go up in tens.
For whatever reason, I've never really understood why you would do that. But many people prefer it. They got 10 2030 40 50 and so on. That Sze just a choice you can do. You can pick whatever number you like, so whatever suits you for that one,
it can also perform quality of service tasks. So quality of service basically is. It prioritizes traffic on reserves bandwidth for specific resource is
s. So that's basically what what it can cover It does.
It doesn't do full like a full on quality of service system. You would actually need some quite serious switch technology to do that if you wanted like large networks doing that. But it does have some built in so it can make a little bit of a difference on before I forget
just to cover the V Land site. Because villain taiking
if any of you are looking to go into networking. If you've not done networking before villains,
we're gonna be your bread and butter in an enterprise environment. Basically, in its simplest form, a villain is a group of devices
on one arm or local area networks.
So one of more networks that you've designed
there are configured to communicate as if they were attached to the same wire, when in fact, they're located on different number of of land segments, if you will, so you could have four items on one switch three on another, two on another, six on another, over another side on what you do is you give
all of them together the same villain,
and they act as if they are all on the same switch. A ll the same connection effectively on the same network, and it allows you to segregate things up, which means that data doesn't have to then transmit all over your network. It just goes to the devices that actually needs to
s. So that's basically that the bottom line of the villa
so moving on, um,
virtuous witches. They're also responsible for isolating network traffic to the virtual adapter that is supposed to be receiving it, so it means that you can. Actually,
you're the data that's going to that virtual adapter, which we do discuss virtual adapters very shortly. It's only going to receive the the items that are relevant to it. It means that you're not flooding the network with if you've if any of you guys have been around, I'm showing my age a little bit here, where he usedto have hubs instead of switches
where they just used to repeat the data out across the entire network and cause
all kinds of trouble. And I never want to work with a hub ever again in my life.
But if you if you have worked on Hub's, you'll know what I'm talking about, the amount of data that it replicates out, which is just useless.
This allows it to be isolated, teach virtual machine
so hyper V network switches should be thought off in exactly the same way as a standard switch. So if you haven't ever worked with stunts, which I'm just gonna knock this up on the screen, don't worry about it covering the text on the screen. But basically
you think of virtual switch. This is what a normal switch would look like so you'd have a box with lots of blinking lights on it. You might have seen these in maybe online if you don't work with them already. But if you do work with them, you know exactly what I'm talking about.
Let what devices? Anything that wants to talk on. The network needs to go into a switch on anything that goes into a switch, then creates you can create the lambs with it, like we've just discussed. Andi allows you to route traffic properly on dhe. Accurately, effectively. So think of a virtual switch exactly
the same way as a physical one. There's no difference in configuration.
There's no difference in how the data works, either.