* [EMAIL PROTECTED] (Jon Lewis) [Thu 30 Aug 2007, 17:13 CEST]:
On Wed, 29 Aug 2007, Andy Dills wrote:
Don't forget that you can prepend incoming announcements as well as
outgoing announcements.
This is what I'd do (and have done before) to even things out. Some would
argue that when
Niels Bakker wrote on Friday, August 31, 2007 3:22 PM:
* [EMAIL PROTECTED] (Jon Lewis) [Thu 30 Aug 2007, 17:13 CEST]:
On Wed, 29 Aug 2007, Andy Dills wrote:
Don't forget that you can prepend incoming announcements as well as
outgoing announcements.
This is what I'd do (and have done
On Fri, 31 Aug 2007, Oliver Boehmer (oboehmer) wrote:
On Wed, 29 Aug 2007, Andy Dills wrote:
Don't forget that you can prepend incoming announcements as well as
outgoing announcements.
This is what I'd do (and have done before) to even things out. Some
would argue that when prepending
On Wed, 29 Aug 2007, Andy Dills wrote:
Don't forget that you can prepend incoming announcements as well as
outgoing announcements.
For instance, to account for the fact that there is essentially an
extra AS in your transit path to 3356, you might just prepend a
single 22773 to everything
On Thu, Aug 30, 2007 at 11:07:36AM -0400, Jon Lewis wrote:
On Wed, 29 Aug 2007, Andy Dills wrote:
Don't forget that you can prepend incoming announcements as well as
outgoing announcements.
For instance, to account for the fact that there is essentially an
extra AS in your transit
On Tue, 28 Aug 2007, Justin Shore wrote:
Does anyone have any suggestions on how to work around this? L3 will
eventually fix it when they eliminate 19094 but who knows when that will
be. I thought about trying to use a regex to match 19094 3356 to
raise local pref even higher. I also
I'd suggest using route-maps to *lower* the local-pref on
routes that contain ASNs from two or your upstreams.
- Bob
I have a situation with one of our upstreams that I'm trying to fix. We
peer with Level3 (3356), specifically we peer with 19094 which is the
old Telcove (Adelphia)
I have a situation with one of our upstreams that I'm trying to fix. We
peer with Level3 (3356), specifically we peer with 19094 which is the
old Telcove (Adelphia) infrastructure that L3 bought and is slowing
migrating to 3356. I'm having trouble pushing traffic to that circuit.
The
'
Subject: [c-nsp] BGP path preference
I have a situation with one of our upstreams that I'm trying to fix. We
peer with Level3 (3356), specifically we peer with 19094 which is the
old Telcove (Adelphia) infrastructure that L3 bought and is slowing
migrating to 3356. I'm having trouble pushing traffic
Hi,
On Tue, Aug 28, 2007 at 11:24:22PM -0500, Justin Shore wrote:
a typical prefix advertised over L3 arrives at my border with 19094
3356 and other ASNs whereas Cox may still have the same number of
backend ASNs but only 22773 once it enters the Cox AS.
Does anyone have any suggestions
10 matches
Mail list logo
