<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
<div class="moz-cite-prefix">On 25/Dec/15 17:40, Tarig Yassin wrote:<br>
</div>
<blockquote cite="mid:DUB120-W36930FC6DDEA384B8219F5BBF80@phx.gbl"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<div dir="ltr">sorry for the mistake....<br>
<br>
I mean the 2nd link still preferred even it has longer AS-PATH.<br>
<br>
Also I've contacted <b>HE</b>, they said all routes received
from AS_1299 "telia" will be assigned local_pref =70.<br>
this is by design and can't be changed.<br>
<br>
this is a real issue for us, because we can't loadshare traffic
properly via AS-PREPEND technique.<br>
</div>
</blockquote>
<br>
As others have already mentioned, LOCAL_PREF trumps AS_PATH
prepends, as a traffic engineering technique.<br>
<br>
Your options are to "intelligently" de-aggregate" (longest match
trumps everything else as a traffic engineering technique), or to
re-think how you choose your transit providers and how much
bandwidth you buy from each them.<br>
<br>
Mark.<br>
</body>
</html>