]> git.proxmox.com Git - mirror_frr.git/commit - bgpd/bgp_vty.c
bgpd-maxmed-administrative-onstartup.patch
authorDonald Sharp <sharpd@cumulusnetworks.com>
Wed, 20 May 2015 00:40:42 +0000 (17:40 -0700)
committerDonald Sharp <sharpd@cumulusnetworks.com>
Wed, 20 May 2015 00:40:42 +0000 (17:40 -0700)
commitabc920f85ea2e2e42c6cf1df7c14373ec1226d20
treeef5c7d67646f98e6f56f98aee28a21a227131910
parent5ca5f1c8af48b4e5aa7e6ff36b4cc69f0a896eab
bgpd-maxmed-administrative-onstartup.patch

COMMAND:

Possible forms of the command configuration:

[no] bgp max-med administrative
[no] bgp max-med administrative <max-med-value>
[no] bgp max-med on-startup <period>
[no] bgp max-med on-startup <period> <max-med-value>

DESCRIPTION:

'administrative' takes effect from the time of the config until the config is
removed.

'on-startup' is effective only at the startup time for the given '<period>'
after the first peer is established.

'<max-med-value>' is used as the MED value to be sent out when the max-med
is effective. Default max-med value is 4294967294.

NOTE:
When max-med is active, MED is changed only in the outgoing attributes to the
peers, it doesn't modify any MED specific state of the attributes in BGP on
the local node.

Signed-off-by: Vipin Kumar <vipin@cumulusnetworks.com>
Reviewed-by: Daniel Walton <dwalton@cumulusnetworks.com>
bgpd/bgp_attr.c
bgpd/bgp_fsm.c
bgpd/bgp_fsm.h
bgpd/bgp_vty.c
bgpd/bgpd.c
bgpd/bgpd.h