Original subtitles

Visser networking consists of two major components

Vmkernel networking in virtual machine networking

Both use Virtual switches to manage configuration and connection information

A virtual switch provides us with a representation of how the vmkernel is going to pass traffic as it exits a virgin

Machine out to the physical Network or to another virtual machine

All of this is configured through V switches

Currently we have the switch zero that was created during installation

And we can see from the graphical representation here on the right hand side we have our physical adapters

Those are up links that are plugged into our physical switches

And on the left hand side we have our pork groups

Support groups determine which virtual machines or vmkernel interfaces are all going to have the same configuration

Under the physical adapters I can click on the I to get some information about that physical adapter

It shows what type of naked is

What driver choosing and then it's current status information

As well as any network information about what it's connected to

That's based off of observe incoming traffic and it's not necessarily reliable

But it does give us a good indication of what networks that particular interfaces Steam

If we were connected to a physical switch that supports either CDP or lldp we would see information here from the Disco

Every protocol

What part were plugged into what VLAN is configured for and things like that

On the left hand side we can also click on the little I here to get information about this port group

The first thing that I can configure is the default settings for the V switch to do that I select a v switch

I clicked on the little plus above it

From here I have four different categories where I can modify the configuration

The first one is properties

And here I can change the MTU

The default MTU is 1500 which is the standard for ethernet

Increases all the way up to 9000

Keep in mind however if you increases to 9000 then all of your physical devices also have to be configured to support jumbo frames

Our second option is security and this is going to determine

How are virtual machines are allowed to communicate

First Option under Heroes promiscuous mode in the default for that is reject

Promiscuous mode means that a virtual machine can receive traffic

Even if it's not intended for its Mac address by default a switch is not going to pass traffic to Virtual Machine

Unless it's intended for its Mac address

If we set that to accept

The not virtual machine or any virtual machine plugged into this port group RV switch

Is going to be able to monitor traffic even when it has a different destination

The default there is rejecting that's generally where you want to leave it

Next two options Mac address changes and forged transmits

The default here is except

For both of them

Mac address changes means do we want to allow for the virtual machine to report that it wants to receive traffic

Take for a different Mac address

From a different Mac address then it's hardcoded address

All three of these need to be set to accept

For any network where we're creating esxi host

Because they do need to receive traffic that is intended for Mac addresses other than their own and they're also going to need to forge trans

As well as report Mac address changes

We did that earlier for the physical cost report

Third option under here is traffic shaping this allows for us to control the amount of traffic that are virtual machine

Is allowed to transmit

We can set this to enabled and then we can configure the average Peak and the burst size

Very very rarely used so we'll leave it is disabled

First Option gear is load balancing this is going to determine how our virtual machines are bound to our up links

The default is route based on originating virtue important for the most part that's where we'll want to leave it

Second option here is Network failure detection there's two options link status only and Beacon probing

Once again in almost all cases were going to want to leave this as link status only

Notify switches indicates that when a virtual machine moves either as a result of emotion or the

Failure of a physical Nic

We want to send a gratuitous ARP up to the physical switches to notify them that the MAC address changed

Once again in almost all cases were going to want to leave that set to yes

The one place where you might want to change that is if you're using Microsoft network load balancing

Fourth option at the top is failback this is going to determine

EFA

Physical adapter fails and then later comes back do you want to fail the virtual machines back to it

The default is yes and more than likely want to leave it there

Finally we have the option of changing the failover order

The first category here is active adapters

Any adapters that are listed under active or going to be load balance based off as a load-balancing algorithm that I have configured

Any doctors that are listed under standby are only going to become active if one of the active adapter fails

And finally any adapters listed under unused or never going to be used for this particular pork group

I can click on an adapter and then I can use the arrows to move it up and down through the list

Hbm Colonel adapter plugged into a standard switch is going to have its own

Park group

If I had it settings on that I can change the same settings

If I want to edit the IP address of that vmkernel Port I need to go down to the internal adapters and I can select it here

For more detailed discussion of networking with vsphere

See my configure and manage VMware vsphere 6 networking course

Now I'm going to make some changes to our lab Network environment

In production environment typically each V switch will have at least two Uplink adapters each one connected to a separate

Physical switch to allow for redundancy

Even though it's not really important for a lab environment I'd like our loud environment to mimic a real-life environments I'm going to go

Add a second physical adapter

To my V switches

To do this I just like the V switch and click on the little green card here

Then click on the plus

Now see that there's two

Physical adapters there

New Edition I need to create a vmkernel interface for vmotion traffic

To do this I click on the little

Green Plus next to the world

It's like the internal network adapter

Go to next

I'm going to leave it on the same V switch that we already have

And I'm going to call this one the emotion

In a production environment we would typically change the VLAN however like I said we're not going to use the alliance in this environment so we'll leave it where

As of 5.5 VMware introduced the ability to do multiple tcp-ip stacks

Each stock is going to have its own vmkernel interfaces its own routing table and its own default router

There is a stock available for vmotion because vmotion can now be routable

Click on next in this is where I'll enter the IP information

Because we're not going to be riding vmotion in the lab environment I can make up whatever IP addresses I want as long as you're not being used anywhere

Nelson my network

Each esxi host is going to need its own separate IP address and they all need to be on the same subnet

Meaning that any traffic exiting this interface is going to use its own default gateway rather than the one that is a sign by the TC

VIP stock

Doing so is only necessary for specific situations and most of the time you're not going to want to override

The default gateway

Click on next

And

Finish

Now want to make the same two changes to our other esxi host but I've already done that in this case

Here's our new vmkernel adapter

4 v motion

And we can see it's IP address there and I can check the same information on the other two

To verify that each one has a unique IP address on the same subnet

I can also assign a vmotion interface to my physical

Esxi host also on the same subnet

And then I'd be able to be motion between my physical esxi host and my virtual esxi host

Use caution if you decide to do that

As you try to vmotion one of your esxi host to itself

It will crossout server

Next I want to create a distributed switch

To do this I go over to

Networking

Right click on my data center distributed switch

New distributed switch

Give it a name

There multiple versions of the distributed switch available

Which one matches the versions of esxi

A 6.5 distributed switch could only be used on 6.5 esxi host

Each one as additional enhancements to the distributed switch since all my hoes or 6.5

Women stick with a 6.5

Distributed switch

I've only got two available doctors so I can reduce that

I don't want to use Network IO control

And I'm going to create

Newport group

Click on finish

Now I have a distributed switch but I need to add my esxi host to it

Right click on it admin and host

I want to add hose to it

I'm going to select all three of my

The San Jose

Check on the little box down here now when I go to configure

One host I can use that as a template for configuring the other two

It's like my first host

Now I don't wanna move over any of my vmkernel adapter so all I need to do is manage physical adapters

This screen here shows my template host

And then it shows me the available Knicks

It shows the ones that are already being a noose I don't want to steal those ones

It's almost like being Nick to

Assign it to uplinks Lot 1

And it's like being mixed 3

And assign not to Uplink Slot 2

Now all I have to do is click on apply to all and those exact same settings get applied to my other two

Esxi host

Click on next going to verify that this isn't going to impact by scuzzi

Since I don't have ice cuz he can figure it won't

And it just verifies information and I click on finish

And that job finishes

Rather quickly

I go back to host in clusters

It's like one of my esxi host

For more information about distributed switches see my configure and manage VMware vsphere distributed switch course

Now let's take a look at our storage configuration for the lab