4.2 Virtual Standard Switches Part 2
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *
Already have an account? Sign In »
2 hours 58 minutes
well, the management I P addresses configured on VM Colonel Port that lives on V's, which is zero as well.
Which brings us to the fact that a virtual switch has to pour types
fort groups that are layer to ports exclusively used by virtual machines
and Veum Colonel ports that are layer three ports exclusively used by the E S X. I host itself toe carry different types of traffic like the management traffic or V motion traffic. For example,
let me repeat this.
Veum Colonel Port is a layer three port that can be configured with an I p entrance,
and it is used to carry yes, excite traffic.
A port group is a group off layer to ports that are used to carry virtual machine traffic. Only
now, both of'em colonel ports and port groups must use the physical next off the server to carry traffic to and from the virtual switch.
So the physical next off the server are also layer to ports that carry both virtual machine traffic and, yes, excite traffic.
You can't survive inside V's fear without knowing the difference between the port types we just spoke about. If you can wrap your mind around this, you're in a really good shape for what's coming
now. To make things better
here's a bit off family terminology. You absolutely need to know
a virtual machine. Nick is called Vina,
and depending on how many you have, they are numbered. Starting from zero
apart Group is named and can be configured with villain
of'em. Colonel Port is called V M K, and depending on how many you have, they are also numbered, starting from zero.
A physical Nick on the server is called V M nick,
and depending on how many you have, they are also numbered, starting from zero
now, the V switch is always configured with one or more VM. Nick's in orderto carry virtual machine traffic and, yes, excite traffic to and from the outside network.
Pause the video and contemplate this slide. It can save you hours off confusing documentation.
I can go on and on into intricate details that are just as important. But I'm trying to hold back on the flood off information that I feel like you must know.
Here's one of them
and I promise it will be the last one for this lesson.
take a closer look at this diagram. V Switch zero will have to carry traffic from the VM Network Port group, The test support group
V. M K zero Andrea M'kay one all through the same physical Knicks off the server.
This means that at some point the management traffic off. Yes, exciting is going to share the same VM Nick with the Web database and email v EMS.
Does this sound like he best practice to you?
Sure it doesn't.
Not all kinds of traffic are created equal.
Yes, excite traffic and VM traffic should not use the same medium. In fact, even VM traffic itself coming from different port groups should not cross the same VM Nick. Think about delay sensitive applications. For example, traffic from the database B m, for example,
should be treated with more
care than the one coming from the email. Vian.
So you get the point. In such a configuration, quality off service must be implemented toe prioritize from traffic over the other.
And if you've got a few of'em next work with good luck with that now, there is a more fireable solution. If you want to separate different types of traffic without using quality of service. In fact, you can create multiple virtual switches, and you can configure different types of traffic on each.
And then you can assign a different VM nick. Tow each virtual switch
this looks better. You won't have to worry about configuring complicated quality of service rules, but still your physical servers need to have enough Veum necks. If you plan to use this architecture to support multiple traffic times,
that's it, my friends. There is a lot more to virtual switches, but I already flooded you with information.
It's now time to recap SX I has a native virtual switch called V Switch zero,
the V's, which has to pour times port groups that are layer to ports toe, which virtual machines are connected.
And PM colonel ports that are layer three ports configured with an I P address, to which yes, excite traffic is connected.
Avi's, which must be connected to the physical next off the server to carry traffic from your *** I and the virtual machines to the outside world, and vice versa.
You can create multiple veterans witches and assigned different physical next to each in order to separate traffic times.
Thanks for watching and stay tuned as I show you how to configure. Virtual is, which is in the next video.