From: Jonathan V Hays (jhays@jtan.com)
Date: Wed Sep 10 2003 - 18:14:26 GMT-3
http://www.cisco.com/univercd/cc/td/doc/cisintwk/idg4/nd2003.htm#xtocid6
9
Quote:
Unlike local preference, the MED attribute is exchanged between ASs, but
a MED attribute that comes into an AS does not leave the AS. When an
update enters the AS with a certain MED value, that value is used for
decision making within the AS. When BGP sends that update to another AS,
the MED is reset to 0.
End Quote:
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Nordhoff, Michael G. (US - Hermitage)
Sent: Wednesday, September 10, 2003 4:39 PM
To: 'ccielab@groupstudy.com'
Subject: BGP Question Concerning MED attribute
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