Hi
I hope I understand your problem correctly but I will try, first of all
the local preference is a more powerful attribute than the AS_path.
There is a significant difference between them, local preference is not a
transitive attribute which means that when your update leaves your AS it
strips off the local preference value and the other AS will not take it in
to account in the path selection, the local preference attribute is only
transitive in side the AS.
The prepend option is used to "cheat" the other BGP router to think that the
way is longer.
When using that option you can only hope that there isn't any more powerful
attribute than shortest path.
There is no attribute that will change other AS's path selection, every AS
makes his own paths decision, that's way your local preference setting
didn't took effect on the path selection of your clients.
I hope it answer your question
Gil
-----Original Message-----
From: Yee, Jason [mailto:[EMAIL PROTECTED]]
Sent: ??? ????? 21 ?????? 2000 10:39
To: '[EMAIL PROTECTED]'
Subject: bgp path selection criteria
hi ,
Anyone here knows which BGP path criteria takes precedence ? AS_PATH or
local preference
>From what I read it is local preference , but in actual fact it is not so ,
why I said this is because I have a customer who prepends their prefixes
many times then advertise them to us but on our side we set local preference
to customers' routes to 90 which in fact will always come back to us if we
do this but this is not happening
Instead the prefixes go to another providers' link because their AS-PATH is
shorter
why is that so?
Jason
_________________________________
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
