[143352] in North American Network Operators' Group
Re: AT&T -> Qwest ... Localpref issue?
daemon@ATHENA.MIT.EDU (Graham Wooden)
Sun Aug 7 09:53:54 2011
Date: Sun, 07 Aug 2011 08:53:05 -0500
From: Graham Wooden <graham@g-rock.net>
To: PC <paul4004@gmail.com>
In-Reply-To: <CA63FDAF.3BDB3%graham@g-rock.net>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
I should also note that Centurylink has been less than cooperative on even
thinking about changing my routes to a pref of 70 on our behalf (they don't
accept communities). I think time to get the account rep involved ...
On 8/7/11 8:30 AM, "Graham Wooden" <graham@g-rock.net> wrote:
> Thanks Paul.
>=20
> Localpref with Qwest on my AT&T prefixes was 100 until last week ... So m=
y
> 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.
>=20
> 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 a=
nd
> unfortunately the two networks haven=B9t really come together as one just y=
et.
> I sent a note to AT&T =AD maybe the can help do something, as I reviewed th=
e
> communities with them and I am already doing what I need to do.
>=20
> 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 m=
uch
> as possible. =20
>=20
> Contract is up in December ... can=B9t wait until it=B9s gone.
>=20
>=20
> On 8/6/11 11:57 PM, "PC" <paul4004@gmail.com> wrote:
>=20
>> Qwest uses 80 for peers; 100 for customers.=A0 As I'm sure Qwest had AT&T =
as a
>> peer prior to today (and you tagged as a customer), it probably should h=
ave
>> been 80 since the beginning.=A0 What was the local pref to AT&T before?=A0 M=
aybe
>> they found a misconfiguration on a router.
>>=20
>> If your only objective is to make your Qwest peering "backup", send comm=
unity
>> 209:70 to Qwest and it'll drop your local pref on their network to 70.=A0 =
This
>> 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 circumsta=
nces
>> 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 A=
T&T
>>> prefixes? =A0I noticed my AT&T assigned prefixes dropping to 80, causing =
my
>>> backup transit peering with Centurylink to take preference with Qwest
>>> originators ... =A0All was working fine with my prepends .. But not anymo=
re...
>>>=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
>=20
