[143376] in North American Network Operators' Group
Re: AT&T -> Qwest ... Localpref issue?
daemon@ATHENA.MIT.EDU (Alan Bryant)
Mon Aug 8 12:02:29 2011
In-Reply-To: <CA6402F1.3BDB7%graham@g-rock.net>
From: Alan Bryant <alan@gtekcommunications.com>
Date: Mon, 8 Aug 2011 11:01:32 -0500
To: Graham Wooden <graham@g-rock.net>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Graham,
We have the same issue as you, although it has been that way since the
beginning. Our primary is Level 3, and backup CenturyLink.
We have been forced to only announce certain prefixes out each in
order to get a balance. CenturyLink has told me that they do not
support communities.
Unfortunately I have much longer on my contract than you.
We are even having problems routing to AOL & Yahoo on CenturyLink.
I've had to refuse those routes from CenturyLink since Yahoo prepends
out Level 3.
On Sun, Aug 7, 2011 at 8:53 AM, Graham Wooden <graham@g-rock.net> wrote:
> I should also note that Centurylink has been less than cooperative on eve=
n
> 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.
>>
>> 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). =A0I am a direct customer of CenturyL=
ink and
>> unfortunately the two networks haven=B9t really come together as one jus=
t 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 (th=
e
>> 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 =
much
>> as possible.
>>
>> 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 as a
>>> peer prior to today (and you tagged as a customer), it probably should =
have
>>> been 80 since the beginning.=A0 What was the local pref to AT&T before?=
=A0 Maybe
>>> they found a misconfiguration on a router.
>>>
>>> If your only objective is to make your Qwest peering "backup", send com=
munity
>>> 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.
>>>
>>> I also suggest you read:
>>> http://www.onesc.net/communities/as209/
>>> and
>>> http://www.onesc.net/communities/as7018/
>>>
>>> However, depending on if your network topology and situational circumst=
ances
>>> permit it, it may not be a bad idea to take on-net customer routes for
>>> performance reasons.
>>>
>>> On Sat, Aug 6, 2011 at 8:51 PM, Graham Wooden <graham@g-rock.net> wrote=
:
>>>> Hi folks,
>>>>
>>>> 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, causi=
ng my
>>>> backup transit peering with Centurylink to take preference with Qwest
>>>> originators ... =A0All was working fine with my prepends .. But not an=
ymore...
>>>>
>>>> Any insight would be great. I haven=B9t reached out to AT&T or Qwest y=
et.
>>>> Curious if this is a bigger change than just me.
>>>>
>>>> Thanks,
>>>>
>>>> -graham
>>>
>>>
>>
>
>
>
>
--=20
Alan Bryant
Gtek Computers & Wireless L.L.C.
Office: 361-777-1400 | Fax: 361-777-1405
alan@gtekcommunications.com | www.gtek.biz
CONFIDENTIALITY NOTICE: This communication (including any attachments)
may contain privileged or confidential information intended for a
specific individual and purpose, and is protected by law. If you are
not the intended recipient, you should delete this communication
and/or shred the materials and any attachments and are hereby notified
that any disclosure, copying, or distribution of this communication,
or the taking of any action based on it, is strictly prohibited. Thank
you.
