VMware Cloud Community
EBoucq
Enthusiast
Enthusiast
Jump to solution

ESXi 4.1 network configuration

Hi,

I just logged on a ESXi 4.1 cluster I'm in charge of now and noticed that the Management Network is configured as a Virtual Machine Port Group.

Shouldn't it be as a VMkernel Port like the Vmotion or Management console ?

What can be the consequence ?

Thanks.

Eric

Reply
0 Kudos
1 Solution

Accepted Solutions
admin
Immortal
Immortal
Jump to solution

Could not reach islation address is shown when your host mgmt. IP is not able to ping the default gateway... Please mark my answer as correct or helpful if it gave some guidance

View solution in original post

Reply
0 Kudos
9 Replies
MKguy
Virtuoso
Virtuoso
Jump to solution

VM Port Groups and vmkernel ports are two distinctly different things. You can't manage an ESXi host with just a normal VM port group, so you're probably missing or misunderstanding something here.

Do you have management on a distributed vSwitch? In that case you map a vmkernel port to a port group on the dvSwitch, but that's perfectly normal.

-- http://alpacapowered.wordpress.com
Reply
0 Kudos
admin
Immortal
Immortal
Jump to solution

By default, Management port group is vmkernel portgroup with label vmk0. Please check which portgroup has the label vmk0,

Reply
0 Kudos
EBoucq
Enthusiast
Enthusiast
Jump to solution

That's what I thought but this is the network setting I have:

Vmotion --> VMkernel Port

Management console --> VMkernel Port

Management Network --> Virtual Machine Port Group

and it works...

Reply
0 Kudos
admin
Immortal
Immortal
Jump to solution

So your Management console is your Management Network. Confirm if management console has vmk0 label. Somebody has renamed it.

Rename your management network to VM network and management console to management network portgroup.

EBoucq
Enthusiast
Enthusiast
Jump to solution

No distributed vswitch in the configuration.

What's named "Management console" is on vmk0

vMotion is on vmk1

Reply
0 Kudos
admin
Immortal
Immortal
Jump to solution

So your connecting to the ESXi host using the Management console IP address. Its just that portgroup has been renamed by someone.

Rename it back as recommended above.

Try connecting to the ESXi host using the vmk0 IP address using vsphere client and root credentials

EBoucq
Enthusiast
Enthusiast
Jump to solution

I guess the bad labelling got me all wrong.

Thanks everybody for your quick replies.

The reason why I was asking about the network configuration is because I have one ESXi in my cluster that loses its connection many times a day: "Host is not responding", "Could not reach isolation address".....

The server has been reinstalled, the network adapter drivers have been updated but the errors keep coming back.

So I was wondering if the network configuration could be the reason..Now I'm starting to wonder if the network adapters are failing....

Reply
0 Kudos
admin
Immortal
Immortal
Jump to solution

Could not reach islation address is shown when your host mgmt. IP is not able to ping the default gateway... Please mark my answer as correct or helpful if it gave some guidance

Reply
0 Kudos
EBoucq
Enthusiast
Enthusiast
Jump to solution

It's correct but I don't understand why this specific server can't suddenly ping the default gateway anymore...even after reinstalling vSphere....

Reply
0 Kudos