From: Muhamamd Durrani (dan_schaw@yahoo.com)
Date: Wed Sep 10 2003 - 18:47:53 GMT-3
This is default behavior of BGP , MED can only be
propagated to adjacent AS. (In your case R1 will
advertise MED to r2 and r2 will not forward it to r5).
This behavior can't bechanged.
It depends what you want to achieve ? do you want R5
to prefer R4 instead of R2 ? or vice versa . There are
several ways to achieve it.
1- AS_Path prepend
2- Advertising summary from one AS while more specific
from other.
Can you please further explain what you want to
achieve?
Regards,
--- "Nordhoff, Michael G. (US - Hermitage)"
<mnordhoff@deloitte.com> wrote:
> A quick question concerning the BGP MED attribute...
>
>
>
> Is it normal behavior for a BGP peer to NOT pass
> along MED information for
> prefixes learned from BGP peers in different AS's?
> My scenario is this...
> R1 is attached to R2. R3 is attached to R4. R2 and
> R4 are attached to R5.
> R1 advertises a prefix to R2 via EBGP as does R3 to
> R4. R2 and R4 then
> advertise these prefixes to R5 via EBGP. The MED
> attributes added by R1 and
> R3 are received by R2 and R4, respectively.
> However, these MEDs are not
> being passed along to R5. What is the reason for
> this behavior and what can
> be done to circumvent it?
>
>
>
> Thanks in advance!
>
>
>
> Mike Nordhoff - CCNP,CCDP
>
> Deloitte & Touche, National WAN Services
>
>
>
> This message (including any attachments) contains
> 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 message. Any
> disclosure, copying, or distribution of this
> message, or the taking of any
> action based on it, is strictly prohibited.
>
>
>
This archive was generated by hypermail 2.1.4 : Wed Oct 01 2003 - 07:24:26 GMT-3