I am looking for some good reading on if there is any gotchas for setting up your management network on two different VLANs.
This is only for managemnet traffic, and not for vMotion traffic, or FT traffic
This is for a larger environment. Multiple hosts, multiple clusters, multiple virtual datacenters.
Can you give more details? Do you mean that one set of servers will have a VLAn for Management and another set of servers will have another vLAN for Management?
If that is what you mean then it will really not matter as far as there is communication between the servers.
A separate Management network (separate VLAN) is a viable option although a bit more complex compared to the normal practice of having just one and use NIC teaming for redundancy. If you would like to go for this approach, ensure both managemement vmkernels are on a different physical networks (connected to different switches). Another thing to consider is adding an additional isolation address (das.isolationaddress) for each additional management network. Hope it helps.
I second the use of manually configuring additional isolation addresses. Using different subnets for management traffic within a cluster may introduce points of failure (think routing issues) with regards to HA. Please be certain that you really do need to use multiple subnets for management traffic within a cluster.
All the best,
Mike
-----------------------------------------
Please consider marking this answer "correct" or "helpful" if you found it useful.
Mike Brown
VMware, Cisco Data Center, and NetApp dude
Consulting Engineer
Twitter: @VirtuallyMikeB
Blog: http://VirtuallyMikeBrown.com
LinkedIn: http://LinkedIn.com/in/michaelbbrown
We are still sorting it out. Networking is saying that we have run out of ip addresses and we have more hosts comming in. We may be able to extend the range. I was looking for gotcha's on why we would not be able to just use a differnt vLAN which was one suggestion.