[143351] in North American Network Operators' Group
Re: AT&T -> Qwest ... Localpref issue?
daemon@ATHENA.MIT.EDU (Graham Wooden)
Sun Aug 7 09:32:29 2011
Date: Sun, 07 Aug 2011 08:30:39 -0500
From: Graham Wooden <graham@g-rock.net>
To: PC <paul4004@gmail.com>
In-Reply-To: <CAJAdsDn+tB--XWPkOtSHUH5Ch4t7nFVD7xRCU=YXjXAMYG4yJg@mail.gmail.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Thanks Paul.
Localpref with Qwest on my AT&T prefixes was 100 until last week ... So my
prepends to balance between the two was working just fine for the past 2
years or so.
My announcements to CenturyLink to Qwest are coming out as 100.
I am not a direct customer of Qwest, so sending the community of 209:70
won=B9t work (already tried that). I am a direct customer of CenturyLink and
unfortunately the two networks haven=B9t really come together as one just yet=
.
I sent a note to AT&T =AD maybe the can help do something, as I reviewed the
communities with them and I am already doing what I need to do.
The main problem here is that our CenturyLink connection is pure crap ...
Even originating routes from their network, I had them take our AT&T (the
other transit at this particular POP) - faster and less hops (go figure).
At our other pops with more than 1 transits, we like to utilize both as muc=
h
as possible. =20
Contract is up in December ... can=B9t wait until it=B9s gone.
On 8/6/11 11:57 PM, "PC" <paul4004@gmail.com> wrote:
> Qwest uses 80 for peers; 100 for customers.=A0 As I'm sure Qwest had AT&T a=
s a
> peer prior to today (and you tagged as a customer), it probably should ha=
ve
> been 80 since the beginning.=A0 What was the local pref to AT&T before?=A0 Ma=
ybe
> they found a misconfiguration on a router.
>=20
> If your only objective is to make your Qwest peering "backup", send commu=
nity
> 209:70 to Qwest and it'll drop your local pref on their network to 70.=A0 T=
his
> will cause their 80 local pref peering with AT&T to be preferred.
>=20
> I also suggest you read:
> http://www.onesc.net/communities/as209/
> and
> http://www.onesc.net/communities/as7018/
>=20
> However, depending on if your network topology and situational circumstan=
ces
> permit it, it may not be a bad idea to take on-net customer routes for
> performance reasons.
>=20
> On Sat, Aug 6, 2011 at 8:51 PM, Graham Wooden <graham@g-rock.net> wrote:
>> Hi folks,
>>=20
>> Anyone else noticed a localpref change on Qwest network in regards to AT=
&T
>> prefixes? =A0I noticed my AT&T assigned prefixes dropping to 80, causing m=
y
>> backup transit peering with Centurylink to take preference with Qwest
>> originators ... =A0All was working fine with my prepends .. But not anymor=
e...
>>=20
>> Any insight would be great. I haven=B9t reached out to AT&T or Qwest yet.
>> Curious if this is a bigger change than just me.
>>=20
>> Thanks,
>>=20
>> -graham
>=20
>=20
