We help IT Professionals succeed at work.

Management vMkernel Port and Vcenter Subnet

jskfan
jskfan asked
on
Medium Priority
25 Views
Last Modified: 2020-02-22
Management vMkernel Port and Vcenter Subnet

I would like to know if Management vMkernel Port and Vcenter should always be in the same Subnet. if that 's the case it means all ESX Hosts will be in the same subnet as Vcenter.
OR
it is OK to have the Management vmKernel Ports on each ESX Host in different subnets from Vcenter Subnet ?

Thank you
Comment
Watch Question

Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
CERTIFIED EXPERT
Fellow
Expert of the Year 2017

Commented:
It really is up to your Design and Management of devices.

Many organisations have a Management VLAN and all devices, e.g. printers, switches are only accessible using the Management VLAN.

I would like to know if Management vMkernel Port and Vcenter should always be in the same Subnet. if that 's the case it means all ESX Hosts will be in the same subnet as Vcenter.

this is also not true, because vCenter Server could be at Head Office managing ESXi hosts at Remote Offices, which would likely be on several different subnets.

There are NO RULES!

Author

Commented:
I thought if Vcenter subnet is in different subnet than ESX Hosts , then L3 device should be in the middle and this will slow down  traffic... unless if Management traffic is not that heavy..

by the way any of other traffic is recommended to be in the same subnet between Source and Destination...

I know vMkernel Storage Port and the Storage device should be on the same subnet
vmkernel port for vmotion should be on the same subnet, thought latest versions will allow different subnets using TCP stack.
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
CERTIFIED EXPERT
Fellow
Expert of the Year 2017

Commented:
Again there are no hardened rules about anything....

Management Traffic is Management Traffic so very light, but it really depends what you do via Management Port!

LATENCY is key to network links, especially for vMotion and Long Distance vMotion.

Author

Commented:
which of the traffic is very sensitive to Network Latency:

vMotion
Storage

I think if there is Latency sensitivity, then it will be better to AVOID L3 on the path.
VMware and Virtualization Consultant
CERTIFIED EXPERT
Fellow
Expert of the Year 2017
Commented:
vMotion and Storage vMotion.

But depends how latent your link is, some clients with remote vCenter locations and hosts, also suffer. (e.g. non 1Gbe LANs) - WAN links.

But how then do you route traffic!

Author

Commented:
Thanks

Explore More ContentExplore courses, solutions, and other research materials related to this topic.