[120710] in North American Network Operators' Group
RE: question regarding multi-homing
daemon@ATHENA.MIT.EDU (Jason Shearer)
Thu Dec 31 09:01:16 2009
From: Jason Shearer <jshearer@amedisys.com>
To: William Herrin <herrin-nanog@dirtside.com>,
Simon Chen<simonchennj@gmail.com>
Date: Thu, 31 Dec 2009 08:00:20 -0600
In-Reply-To: <3c3e3fca0912301025p22816282jbb6b1a857817aaa1@mail.gmail.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
>>Link up, receiving all routes but provider stops propagating your announc=
ement outward.
Longer AS path prepending on your secondary connection should take care of =
this, eh? Might end up with asymmetric routing but better than no traffic =
being returned.
>>Link up but unusably high packet loss to some or all destinations.
Assuming Cisco hardware what is the best way to handle this? Setup some IP=
SLA and bind them to a tracking objects? Use EEM and TCL scripting?
Thanks!
Jason
-----Original Message-----
From: William Herrin [mailto:herrin-nanog@dirtside.com]
Sent: Wednesday, December 30, 2009 12:25 PM
To: Simon Chen
Cc: nanog@nanog.org
Subject: Re: question regarding multi-homing
On Wed, Dec 30, 2009 at 12:02 PM, Simon Chen <simonchennj@gmail.com> wrote:
> I have a question regarding multi-homing, mostly from stub network's
> operational point of view. My big question is: what kind of failures
> do you usually see from your providers? Link down? Link up, but
> withdraw some routes? Link up, no route change, but blackholing
> partial or all traffic? Anything else?
Two more failure modes:
Link up, receiving all routes but provider stops propagating your
announcement outward.
Link up but unusably high packet loss to some or all destinations.
Regards,
Bill Herrin
--
William D. Herrin ................ herrin@dirtside.com bill@herrin.us
3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
Falls Church, VA 22042-3004
*** NOTICE--The attached communication contains privileged and confidential=
information. If you are not the intended recipient, DO NOT read, copy, or =
disseminate this communication. Non-intended recipients are hereby placed o=
n notice that any unauthorized disclosure, duplication, distribution, or ta=
king of any action in reliance on the contents of these materials is expres=
sly prohibited. If you have received this communication in error, please de=
lete this information in its entirety and contact the Amedisys Privacy Hotl=
ine at 1-866-518-6684. Also, please immediately notify the sender via e-mai=
l that you have received this communication in error. ***
