Mixing VMkernel and Virtual Machine traffic

[StageCoach20111]

Is it allowable, supported or recommended to put virtual machines on the same network as vmkernel traffic?  For example, I have a vmkernel port on a virtual standard switch that uses vlan 10.  It is used for management traffic but not vmotion or fault tolerance.  Would it violate best practices to create a virtual machine port group assigned to the same vlan, and put VMs on it?

[a_p_]

I doesn't see an issue with using the same uplinks for Management ands VM traffic as along as you can ensure the Management IP address cannot accidentally be set by e.g. a user/client (i.e. duplicate IP addresses).

André

Message was edited by: a.p.

[mcowger]

Its allowable and supported, certainly.

Generally not a best practice if you can avoid it.

[rickardnobel]

A R wrote:

I have a vmkernel port on a virtual standard switch that uses vlan 10.  It is used for management traffic but not vmotion or fault tolerance.  Would it violate best practices to create a virtual machine port group assigned to the same vlan, and put VMs on it?

When you put clients on the same VLAN (broadcast domain) as your management then your have a higher risk of the management network being unstable. As mentioned a IP dublicate would break your access to your host and possible trigger a HA failover, also a broadcast storm created by incorrect user application or broken network card or looped network cables would also bring down your management network.