VMware Cloud Community
milesmcever
Contributor
Contributor

Multi Nic Config

I have currently added some new 2950's to our vm ESX infrasctructure but I am up in the air as how to configure the network for these, Currently the on board nics are broadcom and the riser card is intel 1000, so I have 4 nics avalible. On the switch side we I am doing nothing special with these boxes only accessing 1 vlan so to speak. The biggest question is how to load balance, have two console ports, and anything else I missed. Any help will be greatly appreciated.

Reply
0 Kudos
4 Replies
Texiwill
Leadership
Leadership

Hello,

For a 4 pNIC situation you have far too few pNICs for true security and redundancy. But you do have enough for partial security/redundancy. I would set things up this way:

vSwitch0 -> SC Portgroup -> pNIC0 (For SC/Administrative Network --- backup for vMotion)
             -> vMotion Portgroup -> pNIC1 (for just vMotion give it a different IP --- backup for SC)
vSwitch1 -> VM Network -> pNIC2, pNIC3 (Just for your VMs)

This will give the best performance for the VMs and vMotion, yet there is a security risk when the SC or vMotion network fails. Then both SC/vMotion traffic travels over the same pNIC. It may be a minor risk but since vMotion traffic is clear text it is wiser to keep this separate. But this setup will minimize the risk.

Best regards,

Edward L. Haletky, author of the forthcoming 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', publishing January 2008, Copyright 2008 Pearson Education. Available on Rough Cuts at http://safari.informit.com/9780132302074

--
Edward L. Haletky
vExpert XIV: 2009-2023,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill
Abaronov
Enthusiast
Enthusiast

If you have two physical switches than your config would be obvious - dedicate two NICs for vmkernel/console and two - to the virtual VM network. Vmotion uses vmkernel to transfer memory snapshot from one host to another - so you will appreciate 2 NICs dedicated just to vmkernel. If vmotion is not a concern, you would give three NICs to virtual networks. Having a separate NIC dedicated to SC/vmkernel is still a good idea.

Thanks,

Andrei

milesmcever
Contributor
Contributor

That is close to what I have done but that makes sense, ports are not an issue on these switches with this being said how many network ports should I have on these boxes? I am currently in the process of ordering more nic cards just to have as backups. Thanks for the prompt reply and information it helps alot.

Reply
0 Kudos
Texiwill
Leadership
Leadership

Hello,

There are issues with having more than 2 pNICs per vSwitch if you are load balancing. THere is a chance you could loose network connectivity for over 10 minutes.... If you are not load balancing the VM network then 3 pNICs is a bit of a waste.

If you can place in the the servers 2 more NICs a peice then you get the best of everything:

2 pNIC for SC

2 pNIC for vMotion

2 pNIC for VM Network.

It is secure, redundant, and gives the best performance. Note that for vMotion you really want that on its on pSwitch or even VLAN on a pSwitch. I would not put that on your internal network as it can contain your login credentials.

Best regards,

Edward L. Haletky, author of the forthcoming 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', publishing January 2008, Copyright 2008 Pearson Education. Available on Rough Cuts at http://safari.informit.com/9780132302074

--
Edward L. Haletky
vExpert XIV: 2009-2023,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill
Reply
0 Kudos