Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
a load balancer application is used for 2+ network connections. It will share the traffic across multiple links. allowing more traffic to the machine.
that's an impressively narrow view of a very generic term... tsk...
a load balancer essentially balances a load between various resources. now this *could* be internet connections as above, but that's actually a pretty rare use of a load balancer. the most common incarnation is to direct requests for data, such as web traffic, to destination servers. a standard internet facing architecture, such as google, ebay etc... will use them to spread connections coming from your browser and thousands, millions, like it to servers behind it. it'll normally take account of what kind of request is made, and keep a track of how busy each server it's aware of sitting behind it appears to be.
I was giving a general view. But if you really want to get specific the most common usage is not for machines in general but for network links. It is used in routed links for redunancy and load balancing. as far as the individual server go "Teaming" or "Port Channeling" is mostly what is used. Google uses a little different method because they use regional servers which trace your ip address back to a physical location then direct you to the closest location.
as above, not the main use by any means. someone like google will use a first line of load balancing based on DNS, but even then they do not have the french server, the german server... each public ip address dns resolves to will be backed by hundreds of servers, which are load balanced against irrespective of the geographical location.
etherchannel connections do load balancing of course, but the question is "what is a load balancer" and use of 802.3ad link aggregation doesn't correctly fit that question, when it's assumed that here a "load balancer" is assumed to be a black box doing a given task.
Last edited by acid_kewpie; 05-29-2007 at 02:02 AM.