Solved

NPAR and Linux's NIC Bonding

Posted on 2013-05-21
1
740 Views
Last Modified: 2014-08-06
Hi Guys,

We have blade servers with 2 x physical NIC ports. After I enabled NPAR , I get 4 virtual ports per each physical ports (Broadcom) totalling 8 virtual ports.
Servers are running RHEL6 and I would like to create NIC bonding using virtual ports.

Here are some pointers I got so far -
You can not use virtual ports from the same physical port in the same bond.
You can't not use bonding mode 4 (802.3ad LACP) because that requires entire physical port to work.
For Windows OS, SLB(Smart Load Balancing) mode is used for same setup.

I want to know which mode I should use for Linux Servers.

Remarks: I don't want Active/Backup or Round-robin.

Thanks in advance,
0
Comment
Question by:netlynker
[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
1 Comment
 
LVL 20

Accepted Solution

by:
Daniel McAllister earned 500 total points
ID: 39188551
NPAR is an acronym used by several vendors for different technologies. What you describe appears to be the VMware version, where you are creating virtual NIC interfaces for use by VM client Operating Systems.

If that is the case, then you'll want your Linux client to be assigned two virtual ports, making sure that they are mapped to (the 2) physically different NICs.

Once the assignment is done in VMware, the Linux client just sees 2 separate NICs and can load balance however you desire -- however, know that, as you pointed out, there will be limitations due to the fact that the virtual NIC in the client will have no visibility to the physical NIC's queues, and so schemes like alb or tlb will not balance on the correct criteria.

Linux bonding drivers have 7 modes:
 0 is round-robin (which you've ruled out)
 1 is active-backup (which you've ruled out)
 2 is xor balanced (probably too similar to round robin, although you are promised to use the same interface to the same "other device" based on mac addresses
 3 is broadcast and can cause issues with some switches
 4 is 803.3ad (which you've ruled out -- probably because your local switch and/or VM host can't support it)
 5 is tlb (transmit load balance) -- probably your best option
 6 is alb (adaptive load balance) -- which also requires a suitable switch and/or VM host capability that probably is not present

Personally, I use tlb -- or mode 5, as it doesn't assume anything about the switch -- or, in this case, the VM host.

I hope this helps.

Dan
IT4SOHO
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

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

After running Ubuntu some time, you will be asked to download updates for fixing bugs and security updates. All the packages you download replace the previous ones, except for the kernel, also called "linux-image". This is due to the fact that w…
The purpose of this article is to fix the unknown display problem in Linux Mint operating system. After installing the OS if you see Display monitor is not recognized then we can install "MESA" utilities to fix this problem or we can install additio…
How to Install VMware Tools in Red Hat Enterprise Linux 6.4 (RHEL 6.4) Step-by-Step Tutorial
If you're a developer or IT admin, you’re probably tasked with managing multiple websites, servers, applications, and levels of security on a daily basis. While this can be extremely time consuming, it can also be frustrating when systems aren't wor…

690 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