?
Solved

COnfiguring Vmware Networking for a server with 4 network ports (Dell R710)

Posted on 2014-08-13
9
Medium Priority
?
1,495 Views
Last Modified: 2016-11-23
Hi VMware experts.

Currently I'm running ESXi (paid for version) on a couple of Dell R710s.

At the moment each server configured via vSpehere so the Management Network and all the VMs on the Server are just using one of the 4 physical network cards.

Obviously this isnt making best use of the hardware. How can I set this up so I can make best use of the four cards sharing amongst the VMs? I'm using storage on the server so dont need to worry about SAN links.vSphere diagram of network config
I'm looking for a dummies guide with a little bit of hand holding.  Before suggesting RTFM, I've had a look at the VMware docs and need further guidance.  Am familiar with networking but not VMware networking...

Thanks!
0
Comment
Question by:jmsjms
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 4
9 Comments
 
LVL 123
ID: 40258042
If you have no SAN, no vMotion, no iSCSI, then this gets pretty simple....

you need to decide two things, do you want your management network ports to share the same network as your Virtual Machines.....

do you have a seperate management network in your organisation? (e.g. different IP Address range and network to your production Servers)

if so, you will need to split.....your VMs and Management onto two different vSwitches and I would suggest at least Two nics for resilience for both.

If you are happy, and do not have a dedicated Management Network, and are happy for management traffic to share the same network as VM Server traffic....

then just add four nics to the same vSwitch.....

You will then need to select a Teaming Policy, which is based on the Physical Network Hardware you have...

e.g. build network trunks with 4 x ports, etc or do not user trunks.

(trunk ports are best)
0
 

Author Comment

by:jmsjms
ID: 40258374
Hi Andew, Thanks for your reply.


>do you want your management network ports to share the same network as your Virtual Machines.....

I get the feeling that separating them into seperate networks would be viewed as best practise?  In real life for a smallish company is it worthwhile? Currenlty they are currently on the same IP subnet and Physical network as the VMs.

Could we start by sharing and when things have settled down I'll look at splitting them up.

>do you have a seperate management network in your organisation? (e.g. different IP Address range and network to your production Servers)

By Management network, do you mean the IPs of the ESXi host?  As above.

> if so, you will need to split.....your VMs and Management onto two different vSwitches and I would suggest at least Two nics for resilience for both.

So at the moment I dont, but I'll look again at it a a future date. thanks.

> If you are happy, and do not have a dedicated Management Network, and are happy for management traffic to share the same network as VM Server traffic....

 >then just add four nics to the same vSwitch.....

OK. How do i do this?  Is it just going to switch properties, then add the network adapters?

Can I add the NIcs to the vSwitch without downtime?  

> You will then need to select a Teaming Policy, which is based on the Physical Network Hardware you have...

I can setup a LAG group on a switch to setup Teaming.  Do I have to do anything on the Server end?

Does it matter if I leave it for a while without teaming?  If I dont setup team, what happens?

 > e.g. build network trunks with 4 x ports, etc or do not user trunks.

> (trunk ports are best)

Could I have a NIC per VM to seperate traffic or it is better to run a team and let VMware sort it out?
0
 
LVL 123
ID: 40258465
Okay, if you are a small-ish installation or no management network keep it simple.

So yes, just add the additional network interfaces to the vSwitch.

Edit the vSwitch Properties, and add nics.

We always recommend any networking work, be done outside or production hours, it should not cause massive mounts of downtime, e.g. 1-2 pings lost, but if this is a production server with VMs, and you make a human error, ALL will be down!

There are at least two teaming policies:-

Route Based in IP HASH (which needs physical switch configuration e.g. Trunk (non-LACP, Static only)

The Default Policy Route Based on the originating virtual port ID will work for you, with no switch config...

as for allocating a nic per VM......you'll get more bandwidth per VM with four on the vSwitch
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 

Author Comment

by:jmsjms
ID: 40258539
>There are at least two teaming policies:-

Is this both have to be configured or a choice?

>Route Based in IP HASH (which needs physical switch configuration e.g. Trunk (non-LACP, Static only)

I could set a Team on the switch, it that what you mean.  What I'm concerned with is do I need to set up a corresponding team on the Server?

 >The Default Policy Route Based on the originating virtual port ID will work for you, with no switch config...

Don't understand you sorry. Do you mean just plug the cables in and add the NICs to the vSwitch without further config?

> as for allocating a nic per VM......you'll get more bandwidth per VM with four on the vSwitch

Understood thanks.
0
 
LVL 123
ID: 40258565
You select a teaming policy on the vSwitch on the Host ESXi server.

If you do nothing, other than just allocated and add 4 nics, plug them into your physical switch and do nothing, the default teaming policy will work.

if you want to do anything fancy, change the teaming policy from the default this requires physical switch config!
0
 

Author Comment

by:jmsjms
ID: 40258612
>You select a teaming policy on the vSwitch on the Host ESXi server.

>If you do nothing, other than just allocated and add 4 nics, plug them into your physical switch and do nothing, the default teaming policy will work.

So, just add the NICs and it will work?

Will they all need a seperate IP address or does the vSwitch sort this out?

> if you want to do anything fancy, change the teaming policy from the default this requires physical switch config!

Is there much to gain to set them to a LAG group on the Switch?  

I think asking about the teaming policy warrants another question. I'll post one up when I've got it working with the default setup.
0
 
LVL 123

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 2000 total points
ID: 40258627
Yes it will work!

The benefit of creating correct etherchannel, static trunks is for data incoming into the ESXi Server!!!!

Traffic flows both ways in and out of the server, the Teaming Policy on the Server effects outgoing traffic only (e.g. from the VMs), Incoming traffic is defined by the physical switch configuration.

Production - High Bandwidth....inbound and outbound traffic

Create a Trunk with 4 x ports, and change the teaming config to IP HASH!

Teaming Policy has to be matched to your networking physical switch and it's config.

We use IP HASH with HP Switches.

http://blog.scottlowe.org/2006/12/04/esx-server-nic-teaming-and-vlan-trunking/

(and LACP is not supported)
0
 

Author Comment

by:jmsjms
ID: 40260045
Wow, thanks for the info.  I'll mark it as answered as I wont be able to progress to next week.
0
 
LVL 123
ID: 40260161
No problems, good luck....
0

Featured Post

Will your db performance match your db growth?

In Percona’s white paper “Performance at Scale: Keeping Your Database on Its Toes,” we take a high-level approach to what you need to think about when planning for database scalability.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If you’re involved with your company’s wide area network (WAN), you’ve probably heard about SD-WANs. They’re the “boy wonder” of networking, ostensibly allowing companies to replace expensive MPLS lines with low-cost Internet access. But, are they …
This month, Experts Exchange’s free Course of the Month is focused on CompTIA IT Fundamentals.
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…
Michael from AdRem Software outlines event notifications and Automatic Corrective Actions in network monitoring. Automatic Corrective Actions are scripts, which can automatically run upon discovery of a certain undesirable condition in your network.…

719 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question