diff options
author | Ondrej Zajicek <santiago@crfreenet.org> | 2008-10-26 22:59:21 +0100 |
---|---|---|
committer | Ondrej Zajicek <santiago@crfreenet.org> | 2008-10-26 22:59:21 +0100 |
commit | b6bf284a905412cfe107b4967e55649e6194187e (patch) | |
tree | f0098a6d05a72982c6cd9f7e85c195b8a4861b94 /doc/bird.sgml | |
parent | 4819c3e17ac22c6810ee80261ac3bffb5127e39d (diff) |
Bugfixes in MULIT_EXIT_DISC attribute handling.
- Old MED handling was completely different from behavior
specified in RFCs - for example they havn't been propagated
to neighboring areas.
- Update tie-breaking according to RFC 4271.
- Change default value for 'default bgp_med' configuration
option according to RFC 4271.
Diffstat (limited to 'doc/bird.sgml')
-rw-r--r-- | doc/bird.sgml | 16 |
1 files changed, 11 insertions, 5 deletions
diff --git a/doc/bird.sgml b/doc/bird.sgml index 5ee9562f..8fa55f85 100644 --- a/doc/bird.sgml +++ b/doc/bird.sgml @@ -784,7 +784,7 @@ for each neighbor using the following configuration parameters: <tag>default bgp_med <m/number/</tag> Value of the Multiple Exit Discriminator to be used during route selection when the MED attribute - is missing. Default: infinite. + is missing. Default: 0. <tag>default bgp_local_pref <m/number/</tag> Value of the Local Preference to be used during route selection when the Local Preference attribute @@ -806,10 +806,16 @@ with `<tt/O/') are optional. selection among multiple BGP routes (see the selection rules above). It's used as an additional metric which is propagated through the whole local AS. - <tag>int <cf/bgp_med/ [IO]</tag> The Multiple Exit Discriminator of the route - is an optional attribute which is often used within the local AS to - reflect interior distances to various boundary routers. See the route selection - rules above for exact semantics. + <tag>int <cf/bgp_med/ [O]</tag> The Multiple Exit Discriminator of the route + is an optional attribute which is used on on external (inter-AS) links to + convey to an adjacent AS the optimal entry point into the local AS. + The received attribute may be also propagated over internal BGP links + (and this is default behavior). The attribute value is zeroed when a route + is exported from a routing table to a BGP instance to ensure that the attribute + received from a neighboring AS is not propagated to other neighboring ASes. + A new value might be set in the export filter of a BGP instance. + See RFC 4451<htmlurl url="ftp://ftp.rfc-editor.org/in-notes/rfc4451.txt"> + for further discussion of BGP MED attribute. <tag>enum <cf/bgp_origin/</tag> Origin of the route: either <cf/ORIGIN_IGP/ if the route has originated in an interior routing protocol or |