VMware Cloud Community
DaveavD
Contributor
Contributor

IPv4 Address for VMkernel network adapters

Good Morning,

I have a question that I can't seem to find the answer to anywhere. We are currently running vCenter Server v5.5. I right-click on one of our distributed switches and go here:

Add and Manage Hosts > Manage host networking > Attach hosts > Select network adapter tasks > Manage physical network adapters > Manage VMkernel network adapters

I then click on the VMkernel network adapter for a particular host and select Edit adapter > IPv4 settings.

I noticed that the IPv4 address is the same for this VMkernel network adapter on every host in the cluster that is utilizing this distributed switch. Is this normal (and is it okay)? We have not been experiencing any networking issues related to this.

Thank you,

David

Reply
0 Kudos
6 Replies
vcallaway
Enthusiast
Enthusiast

Are you using the C# client or the Web Client?

Reply
0 Kudos
DaveavD
Contributor
Contributor

Hello, I am using the web client.

Reply
0 Kudos
golddiggie
Champion
Champion

I know this isn't exactly what you're looking for, but VMware has stated (especially to me, since I ran into an issue at one point in the previous environment I managed) to NOT have the host management network in dvSwitches. At least through vSphere 6.5, since I haven't looked to see if there are any changes in that model with 6.7... Basically, if your dvSwitch setup goes at all sideways, you'll lose your host management connection (completely) and it's not a fast item to regain it. I know there are probably plenty of people out there using port groups on dvSwitches for host management, but it's not advisable.

While I do think that dvSwitches are great, they're not for absolutely everything (at least not yet).

Reply
0 Kudos
daphnissov
Immortal
Immortal

I generally agree and employ a hybrid networking strategy for most deployments where Management and vMotion are on vSS (and sometimes IP storage) while VM networks are all on vDS. Kernel services are fairly static in nature in that once you have them setup and configured, you generally don't go changing them too often. The biggest bang for your buck is for those virtual machine port groups which can and do change and which you want to have subject to the various advanced abilities that a vDS offers.

Reply
0 Kudos
golddiggie
Champion
Champion

I didn't mention in my previous post but I also typically use standard vSwitches for things like iSCSI connections. While I COULD use the dvSwitch setup for iSCSI, my stress level thanks me when I don't. Smiley Wink Especially since those things are typically very static and easy to configure with the standard vSwitches.

I know not everyone does this, and as long as it WORKS (and is trouble free) you're good. But when things go sideways (and Murphy kicks you in the nuts) many often change their OM.

Reply
0 Kudos
DaveavD
Contributor
Contributor

Hi everyone. These are all great points! Thank you for taking the time to post. I found the answer: IPv4 addresses should be different for each of the VMkernel network adapters for each host in the cluster utilizing a vDS. The person I spoke with also suggested that if you are using vDS, to export the configuration and put it in a safe place. This way you will not have to rebuild them if your environment is damaged. Again, thank you all for your help!

Reply
0 Kudos