[afnog] local pref issue with HE

[Andrew Alston]

Generally local pref in any major ISP/Telco is done on the following basis (or a variation of the same)

Customer > Peer > Transit

What this means is that any ISP that is following this generally acceptable model and is peered to HE, will prefer the HE route unless they are also peering with your second provider, and as-path prepend won’t help you very much.

You could de-aggregate on the link you want more traffic on, but I’d appeal to you to try and go easy on the de-aggregation (as in, de-aggregate as little as possible to achieve the desired result, the routing table is already to large!)

Thanks

Andrew

From: afnog <afnog-bounces at afnog.org<mailto:afnog-bounces at afnog.org>> on behalf of Tarig Yassin <tariq198487 at hotmail.com<mailto:tariq198487 at hotmail.com>>
Date: Wednesday, 23 December 2015 at 10:16 AM
To: afnog afnog <afnog at afnog.org<mailto:afnog at afnog.org>>
Subject: [afnog] local pref issue with HE


Hi Afnog


We're trying to loadshare two uplinks from different upstream providers using AS-PREPEND.


the issue is how matter we prepend the 2nd link still the 1st link is preferred.


To clarify more, despite the 2nd route below has longer AS-PATH,

but still HE prefers the 1st route, I try to understand the reason,and

why the prepend won't work and why HE changes the value of Local-pref.


> 41.202.160.0/24 AS-PATH: 1299, 2914,33788                        Local-pref:70

> 41.202.160.0/24 AS-PATH: 15412,33788,33788,33788        Local-pref:100

thanks,
--
Tarig Yassin
Sudan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.afnog.org/pipermail/afnog/attachments/20151224/19f4be69/attachment-0001.html>