All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Taylor <gtaylor@riverviewtech.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] bandwidth aggregation between 2 hosts in the same subnet
Date: Mon, 30 Jul 2007 21:19:12 +0000	[thread overview]
Message-ID: <46AE55D0.3050005@riverviewtech.net> (raw)
In-Reply-To: <20070730141010.GA27667@p15145560.pureserver.info>

On 07/30/07 15:12, Ralf Gross wrote:
> I've tried bonding before. But this didn't work either because the 
> cisco switch decides on a src/dst mac/ip hash which port of the port 
> channel will be used. But in my case the hash is always the same 
> because between host A and host B. Thus always the same interface was 
> used.

Dough!  So the switch is failing you.

> But not between host A and host B. I've gone through this a while 
> ago, everyone told me than that I've to solve the problem on L3 ;)

*SIGH*

> I think it's not possible with the Cisco switches we use here to 
> increase the bandwidth between 2 hosts on L2.

It sounds like a "per packet" or "per flow" decision that is defaulting 
to "per flow" for deciding which port on an EtherChannel to use.

I'm not that much of a Cisco person so I can't say for sure, but I'd 
think there would be a setting that could be changed in the switch that 
would alter this so that you could get an aggregate bandwidth increase.

Doing a quick Google search 
(http://www.google.com/search?hl=en&q=Cisco+CEF&btnG=Google+Search) 
reminded me that we had to turn on Cisco Express Forwarding (a.k.a. CEF) 
and set the CEF to be "per packet" rather than "per flow".  You might 
want to do some research on your switches to see if they support CEF or 
not.  If your switches do support it you may want to talk to your switch 
support staff (if it is not your self) to see if they would consider 
setting such up.

I am presently using CEF between a 3640 and an upstream 7204-ubr to load 
balance ethernet connections (bridged to SDSL) and am getting an 
aggregate bandwidth increase in "per packet" fashion.  So, this will 
work between routers and I believe switches that support it.

Good luck.  Let me know if there is any thing else that I can do to help.



Grant. . . .
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2007-07-30 21:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-30 14:10 [LARTC] bandwidth aggregation between 2 hosts in the same subnet Ralf Gross
2007-07-30 18:44 ` Grant Taylor
2007-07-30 18:46 ` Paul Zirnik
2007-07-30 20:12 ` Ralf Gross
2007-07-30 20:48 ` Ralf Gross
2007-07-30 21:19 ` Grant Taylor [this message]
2007-07-30 21:22 ` Grant Taylor
2007-07-31  7:52 ` Paul Zirnik
2007-07-31  8:05 ` Ralf Gross
2007-07-31 11:01 ` Ralf Gross
2007-07-31 15:25 ` Grant Taylor
2007-07-31 15:31 ` Ralf Gross
2007-07-31 16:31 ` Grant Taylor
2007-07-31 19:58 ` Jay Vosburgh
2007-07-31 21:00 ` Ralf Gross
2007-08-21 16:31 ` Ralf Gross

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46AE55D0.3050005@riverviewtech.net \
    --to=gtaylor@riverviewtech.net \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.