From: Grant Taylor <gtaylor@riverviewtech.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] bandwidth aggregation between 2 hosts in the same subnet
Date: Tue, 31 Jul 2007 16:31:41 +0000 [thread overview]
Message-ID: <46AF63ED.2080805@riverviewtech.net> (raw)
In-Reply-To: <20070730141010.GA27667@p15145560.pureserver.info>
On 07/31/07 10:31, Ralf Gross wrote:
> I've talked to one of the people of the network staff. He meant they
> never used CEF in this type of scenario. I'm also not very familiar
> with Cicso products.
My physical scenario is a Cisco 3640 router with two (10BaseT) ethernet
connections connected to external ethernet to SDSL bridging modems. The
SDSL modems bridge the ethernet to an ATM circuit. The ATM circuit is
terminated in a Cisco 7206 (I think it's a 6) UBR router at my ISP.
Cisco Express Forwarding is being run on the local 3640 and the remote
7206 to control which connection the packets are being routed down. The
local 3640 has two routes upstream, each being the remote IP for each of
the ATM links. Correspondingly the 7206 has two routes to a (globally)
routable subnet behind the local 3640.
As I understand it, CEF (ultimately) builds a forwarding information
base (a.k.a. FIB) from the routing tables. So if you have multiple
routes, CEF will know about them. CEF will then divide the traffic
either "per flow" or "per packet" across all available routes so that
more aggregate bandwidth is achieved.
In my scenario, I am using CEF via OSPF to combine two 1.1 Mbps SDSL
connections to get close to 2 Mbps worth of aggregate bandwidth to the
net. I can and do routinely receive 1.5 - 1.8 Mbps throughput via FTP /
HTTP / BitTorrent. (Though BitTorrent by nature is not the best example)
> If you could give me more details on your CEF setup, that would maybe
> help me to show them what a CEF config should look like.
I think I have done so above. If you want config examples, contact me
off list as I don't want to publish it to the world.
> But I'm still not sure if CEF is a thing that is designed to work
> with client-client connections.
I can't say for sure one way or the other. but It think that CEF will
achieve what you are wanting to do as long as the device you are
connecting to will support it. I know that more and more layer 3
devices support it. So, that being said if your switches are recent
layer 3 switches, I'd say that they will support CEF. I don't know for
sure though.
Grant. . . .
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2007-07-31 16:31 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
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 [this message]
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=46AF63ED.2080805@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.