From: "Chris Bennett" Date: Sat, 23 Apr 2005 23:18:19 +0000 Subject: Re: [LARTC] Spill over Message-Id: <001401c5485a$bc8c6060$200fa8c0@DELTA> MIME-Version: 1 Content-Type: multipart/mixed; boundary="===============2128599656==" List-Id: References: In-Reply-To: To: lartc@vger.kernel.org This is a multi-part message in MIME format. --===============2128599656== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0011_01C54830.D3A34590" This is a multi-part message in MIME format. ------=_NextPart_000_0011_01C54830.D3A34590 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable You can't split a particular IP connection between two links, but can = instead only determine which link a particular connection will occur on. = Given this, it sounds like you want to have some way to detect that = Link A is already saturated and then send all further connections to = Link B until Link A is no longer saturated. Maybe someone can tell you how to do that if that's really what you want = to do (others here know far more about this than me), but my guess is = you really don't want to do that. With the huge bandwidth disparity = between the two links, route cacheing, and the inability know how much = bandwidth any particular conneciton will consume, I think you'd end up = with a giant mess... those people with connections unlucky enough to end = up on Link A would probably be very unhappy people indeed. Generally speaking I think it would make more sense to put all traffic = over Link B, and then use Link A only for emergencies. Maybe route the = most critical traffic over Link A if you really want to feel like its = being utilized as something other than a pure backup, but personally I = wouldn't even do that. Just because Link A is more reliable and more expensive doesn't mean it = makes sense to use it as your primary conduit. With Link B having eight = times the bandwidth, it seems the obvious choice as the primary. Use = it, and keep the users happy most of the time (instead of making them = miserable most of the time). On the rare ocassions it goes down, use = bandwidth shaping to make sure the highest priority traffic gets access = to Link A first. In all the time I've used DSL, I've had severe outages twice for reasons = other than standard maintenance. In both cases (in two separate = locations), the cause was the ILEC phone company mistakingly dropping = the wire pair while doing other work (freakin took over a week in each = case to get my connectivity back!!). This sort of thing could just as = easily happen with a leased line though, so I'm not really sure I buy = that the leased line is really more reliable than DSL line from a high = quality ISP. Although maybe a particular SLA makes it so in some legal = sense since you can then sue someone. Personally, if your leased line = really costs more than the DSL, I'd get rid of it and get a 2nd DSL line = from another provider and use that as your backup instead. Anyway, I guess my main point is that the high cost of your leased line = might be clouding your thinking on this. I wouldn't let the comparitive = cost be your guiding light here. Go with what makes sense from a = technology perspective, and don't guilt yourself into trying to get full = utilization out of the slow link just because it costs more. ----- Original Message -----=20 From: Kenneth Kalmer=20 To: lartc=20 Sent: Saturday, April 23, 2005 4:34 PM Subject: [LARTC] Spill over List I need some help, advice or just a starting point on the following = situation: Link A - 64kbps leased line Link B - 512kbps ADSL line Is it possible to have Link A saturated constantly and have the excess = traffic "spill over" onto Link B? I know it's possible to have packets = sent down links in a round-robin fashion and I've read in the howto on = load sharing over multiple interfaces = (http://lartc.org/howto/lartc.loadshare.html), but I do not have control = over the termination of the link at the ISP's (two different one as = well). Also note that splitting different protocols over each of these = links are not possible in our case. Reason being, Link A is a more reliable and more expensive link, so I = need to over-use it's capacity if it we're, and use the cheaper ADSL = (link B) offering to keep al services running when the leased line (A) = is saturated. Any tips, suggestions and comments would be welcomed. Regards --=20 Kenneth Kalmer kenneth.kalmer@gmail.com http://opensourcery.blogspot.com=20 -------------------------------------------------------------------------= ----- _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc ------=_NextPart_000_0011_01C54830.D3A34590 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
You can't split a particular IP = connection=20 between two links, but can instead only determine which link a=20 particular connection will occur on.  Given this, it sounds = like you=20 want to have some way to detect that Link A is already saturated and = then send=20 all further connections to Link B until Link A is no longer=20 saturated.
 
Maybe someone can tell you how = to do that=20 if that's really what you want to do (others here know far more about = this than=20 me), but my guess is you really don't want to do that.  With = the=20 huge bandwidth disparity between the two links, route = cacheing, and=20 the inability know how much bandwidth any particular conneciton = will=20 consume, I think you'd end up with a giant mess... those people with = connections=20 unlucky enough to end up on Link A would probably be very unhappy people = indeed.
 
Generally speaking I think it = would make=20 more sense to put all traffic over Link B, and then use Link A only for=20 emergencies.  Maybe route the most critical traffic over Link A if = you=20 really want to feel like its being utilized as something other than a = pure=20 backup, but personally I wouldn't even do that.
 
Just because Link A is more = reliable and=20 more expensive doesn't mean it makes sense to use it as your primary=20 conduit.  With Link B having eight times the bandwidth, it=20 seems the obvious choice as the primary.  Use it, and keep the = users=20 happy most of the time (instead of making them miserable most of = the=20 time).  On the rare ocassions it goes down, use bandwidth shaping = to make=20 sure the highest priority traffic gets access to Link A = first.
 
In all the time I've used DSL, = I've=20 had severe outages twice for reasons other than standard=20 maintenance.  In both cases (in two separate locations), the cause = was the=20 ILEC phone company mistakingly dropping the wire pair while doing other = work=20 (freakin took over a week in each case to get my connectivity = back!!). =20 This sort of thing could just as easily happen with a leased line = though, so I'm=20 not really sure I buy that the leased line is really more reliable than = DSL line=20 from a high quality ISP.  Although maybe a particular SLA = makes it so=20 in some legal sense since you can then sue someone.  Personally, if = your=20 leased line really costs more than the DSL, I'd get rid of it and get a = 2nd DSL=20 line from another provider and use that as your backup = instead.
 
Anyway, I guess my main point = is that the=20 high cost of your leased line might be clouding your thinking on = this.  I=20 wouldn't let the comparitive cost be your guiding light here.  = Go with=20 what makes sense from a technology perspective, and don't guilt yourself = into=20 trying to get full utilization out of the slow link just because it = costs=20 more.
 
----- Original Message -----
From:=20 Kenneth Kalmer
To: lartc
Sent: Saturday, April 23, 2005 = 4:34=20 PM
Subject: [LARTC] Spill = over

List

I need some help, advice or just a starting = point=20 on the following situation:

Link A - 64kbps leased line
Link = B -=20 512kbps ADSL line

Is it possible to have Link A saturated = constantly=20 and have the excess traffic "spill over" onto Link B? I know it's = possible to=20 have packets sent down links in a round-robin fashion and I've read in = the=20 howto on load sharing over multiple interfaces (http://lartc.org/how= to/lartc.loadshare.html),=20 but I do not have control over the termination of the link at the = ISP's (two=20 different one as well). Also note that splitting different protocols = over each=20 of these links are not possible in our case.

Reason being, Link = A is a=20 more reliable and more expensive link, so I need to over-use it's = capacity if=20 it we're, and use the cheaper ADSL (link B) offering to keep al = services=20 running when the leased line (A) is saturated.

Any tips, = suggestions=20 and comments would be welcomed.

Regards

-- =

Kenneth=20 Kalmer
kenneth.kalmer@gmail.com
= http://opensourcery.blogspot.co= m=20


_______________________________________________
LARTC = mailing=20 = list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/l= istinfo/lartc
------=_NextPart_000_0011_01C54830.D3A34590-- --===============2128599656== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc --===============2128599656==--