Well, this is Dean Pompilio. Welcome to Cyber Eri.
This is Module five. Lesson one
for the virtual ization installation configuration of management class. And this lesson will be talking about an introduction to network standards, switches, virtual network standards, which is
so we'll define what the virtual network wouldn't. What it is,
what the virtual switch actually is.
The different connection types that are available for a virtual switch,
some of its components
and then in the lab you'll actually get to create a switch.
So starting with the virtual switch itself, we can see
that we've got several viens here.
Each of them has their virtual network interface card,
and each of the virtual nix is connected to a port group.
reports defined for pork grouping production, another one named Test,
Other one named the Motion.
And there's a lot of flexibility for how you design your virtual switch.
These particular ports are the colored in red, are VM Colonel ports
and we need them colonel ports for various things.
For instance, your management network might be connected to one.
I might have another one designated for the motion, another one designated for I scuzzy or fault tolerance traffic,
and we'll get to look at that little bit later.
So these are special port types
that are that are used for things other than regular
host of B M R V M D V M network. In traffic
when I defined, or when you define a virtual switch, you need to create
coupling ports. If you want this switch to communicate with the outside network,
you don't always need up ling ports.
I could create several virtual switches and allow the networking to take place within the host.
So in that case, I don't need an up link port. But if you want to connect
to your external network external to the host itself,
then you need an up link.
So those get to find when you build the switch
and their given names like what we see here for our physical next bm nix
So those are Those are host network interface cards that are on the physical host.
within our virtual switch.
So if I connect my coupling ports from the back of the host to a physical switch, I can define villains I can have one for my management traffic
and maybe one for I p storage.
The lands are very useful
because they give you the ability to use a physical network but separated with separate logical networks.
Um, one of the caveats or little gotchas with using bee lands is that your physical switch must be in trunk mode in order to route this traffic properly
so you can't just enable V lands
in your switch configuration. Then expect that the traffic is going to go somewhere outside of your host without making the corresponding changes to the physical network.
if you do use the lands a tow to die. One Q B Land tagging is this current standard that supported,
which is ah, you know, modern modern standard in that case.
So I talked about our different connection types
and some of the pieces that are inside the switch.
Now we can have a look at the components,
so if we go to your host and click the configuration tab,
you have the hardware and software suction in the hardware section. We're interested in the networking link.
If I click the networking link, then I get a visual display off my switch
and you can see this a very simple switch. I've got ah VM pork group
with a pork group name Of'em Network,
which is pretty typical for what you'll see in the lab.
And then I also have some of'em colonel ports defined in my poor group named Management Network.
And when you look at your virtual switch, you can see the way that they're connected visually within the within the switch. This is basically the same as this.
It's just showing it a different representation.
And then, if I have up links to find, then I'll see a little network adapter card icon, the name of that physical adapter,
the M zero. And then it's speed and duplex settings, So I know it's BMX zero. I know it's
it's a gigabit speeds full duplex.
If you click the Properties link just above the switch,
you could bring up the properties to look a little bit further at some of the settings you can change. For instance, I can define the number of ports
anywhere from 24 reports up to 40 88
and it might seem a little strange that these air, not powers of two. You'd expect to see something like
32 ports all the way up to 40 96
and the reason for that is that eight ports are reserved for VM colonel.
So that way, we if we used all 40 88 available ports,
we still have the eight reserved
to give us the total of 40 96.
So just keep that in mind. That's why those numbers look a little strange. The default is usually 120 ports when you create a switch, and that's plenty for most purposes.
If you click the tab next to the ports, you can click network adapters
and this tab. We can add or remove physical network adapters from this virtual switch,
and sometimes that's necessary. You might configure a switch with two up ling ports, and then later you decide that you need
one of those adapters for another switch or for another host
another host. But another switch that's going to be communicating with your V EMS so you can remove one of these and then add it to another switch.
And if you go to the configuration, then you'd CVM nick one attached to this, which as you as you configure it
all right. So Lab five would be your next lab and this lab. You'll be looking at the standard switch configuration that's that's built when you could create the host
and you'll create the switch with a B M port group.
There were similar what we see here,
Emmanuel, add your virtual machine to that poor group
by following the are by just basically going to the properties of the settings of that B M
going to the network adapter and selecting the VM network from the dropdown.