Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
linustouchtips

What is the best NIC Teaming protocol to use for a novice

Recommended Posts

Posted · Original PosterOP

Okay I'm not a network admin or anything and i mainly using it at home hoping to get some kind of network going with NAS and stuff. But after looking into the properties of my network adapters i found a way to setup the teaming so i used the ieee802.3 something with full duplex @ 1 gb/s. I want performance and redundancy improvements i don't have a cisco switch or anything but i think i selected the wrong protocol any suggestions and direction would be great thanks.

specs for the lan.

 

Gigabit LAN 10/100/1000 Mb/s
2 x GigaLAN Intel® I211AT

 

Link to post
Share on other sites

If you want to team NIC's and connect them to a switch, you need to somehow tell the switch which physical connections are teamed. The protocol that's usually used is LACP. That's the one you need to configure.


If you want my attention, quote meh! D: or just stick an @samcool55 in your post :3

Spying on everyone to fight against terrorism is like shooting a mosquito with a cannon

Link to post
Share on other sites

LACP is great for redundancy but won't do anything to improve performance for single client access however if you need multiple clients to access then it will help :)


Current Network Layout:

Current Build Log/PC:

Prior Build Log/PC:

Link to post
Share on other sites

When you say performance and redundancy, is your objective to see speeds beyond 1Gbit? If you're fine with gigabit then setting up fail over or link aggregation will take care of the redundancy (fail over is a better option because link aggregation will require a managed switch which can be expensive). Though I have to say for a do it yourself at home job, redundancy isn't really a concern you should have unless your operations are mission critical. Just keep a spare NIC around in the event one fails. If this isn't sufficient then like I said before there's fail over but your OS has to support it.


Guides & Tutorials:

How To: Access Remote Systems at Home/Work Securely from Anywhere with Pritunl

How to Format Storage Devices in Windows 10

A How-To: Drive Sharing in Windows 10

VFIO GPU Pass-though w/ Looking Glass KVM on Ubuntu 19.04

A How-To Guide: Building a Rudimentary Disk Enclosure

Three Methods to Resetting a Windows Login Password

A Beginners Guide to Debian CLI Based File Servers

A Beginners Guide to PROXMOX

 

Guide/Tutorial in Progress:

How To: Remotely Access Your Server/NAS

 

In the Queue:

How to Use Memtest86 to Diagnose RAM Errors

 

Don't see what you need? Check the Full List or *PM me, if I haven't made it I'll add it to the list.

*NOTE: I'll only add it to the list if the request is something I know I can do.

Link to post
Share on other sites

You will never achieve true bandwidth over 1 Gbs using NIC teaming, LACP, or Ethernet bonding. The application itself must be able to perform multiple sessions via multiple interfaces (like SMBv3). Teaming is just for load balancing different sessions across NICS using different methods. The easiest method is round robin. Things can get a bit more complex when using IP hashing and such things like that.

 

If you need the redundancy linux and windows will perform link aggregation without a special switch. 

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


×