Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 372
  • Last Modified:

help allocate vmware NICs

We have ESXi Entperise Plus license. We have three servers with 8 Intel gigabit NICs. We also have two FC ports for storage access. I'm trying to design how I will allocate the nics and somehow tie that into the configuration of the cluster. (vmnic0 to vmnic3 are on one card; vmnic4 to vmnic7 are on the other)

I imagine:
* vmnic0 as management (the default) - this is called the Service Console right?
* vmnic7 as potentially a redunandt service console port (per best practices, though I don't know how to set this up).
* vmnic 3 and vmnic 4 for vmotion
*vmnics 1, 2, 5, 6 for vm networking.

do I build multiple dVswitches and port groups on each host?

thanks. if you're so inclined a picture is worht a thousand words to me. :)
0
DITGUY
Asked:
DITGUY
  • 2
2 Solutions
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
ESXi no longer has a service console, it's now called the Management Network.

vmnic0 & vmnic7 (setup up a teaming policy in ESXi) and configure on physical switches.

(this makes sense to split the resilience across two different cards).

vmnic3 & vmnic 4 for vMotion (find, same as above - resilience on two different cards).

vmnics 1,2,5 and 6 teamed, trunk configured on physcial.switch. (channel group, etherchannel depends on physical switch)

with only three hosts, you can create 2 additional vSwitches (so you would have three including the default).

Distributed switches, is probably overkill for three hosts.

an example only!

example
0
 
DITGUYAuthor Commented:
Thanks so much.

dVSwitch is preferred to prep for future growth. That's how our other cluster is configured for another group and so we'd prefer to keep it the same. however that's a UCS blade setup and professional services set it up so we're trying to re-acclimate why and how.

by teaming do you mean I need to do something on the cisco switch (or rather have our network engineer do it)? I've only ever set up teaming on windows servers and always just plugged them into separate switches if I recall.

also, I always thought management network and vmotion were on same physical ports. is that not necessary?

also, the server is being managed in vcenter through vsphere client on a given subnet for management network on vmnic0. if I change the ip to another vlan (assumign the switchport can see both), will I need to reconnect or do something from the host console?

lastly, what's the order, set up teaming policy, then have network changes made or vice versa?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Yes, teaming needs to be configured on the Cisco physical switches, usally etherchannel.

vMotion can be on any port group, you enable.

If you change the Management Network, you will need to ensure this can still be reached from vCenter Server, vSphere Client connects to vCenter Server. So vCenter Server needs to be on two networks at least.

Setup physical switches first, and then teaming policy to match.
0

Featured Post

Put Machine Learning to Work--Protect Your Clients

Machine learning means Smarter Cybersecurity™ Solutions.
As technology continues to advance, managing and analyzing massive data sets just can’t be accomplished by humans alone. It requires huge amounts of memory and storage, as well as the high-speed power of the cloud.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now