Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

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

NPAR and Linux's NIC Bonding

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
netlynker
Asked:
netlynker
1 Solution
 
Daniel McAllisterPresident, IT4SOHO, LLCCommented:
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

What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

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