question regarding multi-homing
jshearer at amedisys.com
Thu Dec 31 08:00:20 CST 2009
>>Link up, receiving all routes but provider stops propagating your announcement 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?
From: William Herrin [mailto:herrin-nanog at dirtside.com]
Sent: Wednesday, December 30, 2009 12:25 PM
To: Simon Chen
Cc: nanog at nanog.org
Subject: Re: question regarding multi-homing
On Wed, Dec 30, 2009 at 12:02 PM, Simon Chen <simonchennj at 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
Link up but unusably high packet loss to some or all destinations.
William D. Herrin ................ herrin at dirtside.com bill at 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 on notice that any unauthorized disclosure, duplication, distribution, or taking of any action in reliance on the contents of these materials is expressly prohibited. If you have received this communication in error, please delete this information in its entirety and contact the Amedisys Privacy Hotline at 1-866-518-6684. Also, please immediately notify the sender via e-mail that you have received this communication in error. ***
More information about the NANOG