Versions Compared

Old Version 16

changes.mady.by.user Māris B.

Saved on

compared with

New Version 17

changes.mady.by.user Māris B.

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

PropertyDescription
add-path-out (all
|none; Default: )
address-families (ip | ipv6 | l2vpn | l2vpn-cisco | vpnv4; Default: ip)List of address families about which this peer will exchange routing information. The remote peer must support (they usually do) BGP capabilities optional parameter to negotiate any other families than IP.
allow-as-in (integer [0..10]; Default: )How many times to allow own AS number in AS-PATH, before discarding a prefix.
as (integer [0..4294967295]; Default: )32-bit BGP autonomous system number. Value can be entered in AS-Plain and AS-Dot formats.
as-override (yes | no; Default: no)If set, then all instances of remote peer's AS number in BGP AS PATH attribute are replaced with local AS number before sending route update to that peer. Happens before routing filters and prepending.
cisco-vpls-nlri-len-fmt (auto-bits | auto-bytes | bits | bytes; Default: )VPLS NLRI length format type. Used for compatibility with Cisco VPLS. [[Read more>>]].
cluster-id (IP address; Default: )In case this instance is a route reflector: cluster ID of the router reflector cluster this instance belongs to. This attribute helps to recognize routing updates that comes from another route reflector in this cluster and avoid routing information looping. Note that normally there is only one route reflector in a cluster; this case 'cluster-id' does not need to be configured and BGP router ID is used instead
default-originate (always | if-installed | never; Default: never)Specifies how to distribute default route
default-prepend (integer [0..255]; Default: )
disabled (yes | no; Default: no)Whether template is disabled.
hold-time (time[3s..1h] | infinity; Default: 3m)Specifies the BGP Hold Time value to use when negotiating with peers.

According to the BGP specification, if router does not receive successive KEEPALIVE and/or UPDATE and/or NOTIFICATION messages within the period specified in the Hold Time field of the OPEN message, then the BGP connection to the peer will be closed.

The minimal hold-time value of both peers will be actually used (note that the special value 0 or 'infinity' is lower than any other values)

  • infinity - never expire the connection and never send keepalive messages.
ignore-as-path-len (yes | no; Default: no)Whether to ignore AS_PATH attribute in BGP route selection algorithm
input - group of parameters associate with BGP input







.accept-comunities (string; Default: )Quick way to filter incoming updates with specific communities. It allows to filter incoming messages directly before they are even parsed and stored in memory, that way significantly reducing memory usage. Regular input filter chain can only reject prefix which means that it will still eat memory and will be visible in /routing route table as "not active, filtered".
.accept-ext-communities(string; Default: )Quick way to filter incoming updates with specific extended communities. It allows to filter incoming messages directly before they are even parsed and stored in memory, that way significantly reducing memory usage. Regular input filter chain can only reject prefix which means that it will still eat memory and will be visible in /routing route table as "not active, filtered".
.accept-large-comunities (string; Default: )Quick way to filter incoming updates with specific large communities. It allows to filter incoming messages directly before they are even parsed and stored in memory, that way significantly reducing memory usage. Regular input filter chain can only reject prefix which means that it will still eat memory and will be visible in /routing route table as "not active, filtered".
.accept-nlri(string; Default: )Quick way to filter incoming updates with specific NLRIs. It allows to filter incoming messages directly before they are even parsed and stored in memory, that way significantly reducing memory usage. Regular input filter chain can only reject prefix which means that it will still eat memory and will be visible in /routing route table as "not active, filtered".
.accept-unknown(string; Default: )Quick way to filter incoming updates with specific "unknown" attributes. It allows to filter incoming messages directly before they are even parsed and stored in memory, that way significantly reducing memory usage. Regular input filter chain can only reject prefix which means that it will still eat memory and will be visible in /routing route table as "not active, filtered".
.affinity(afi  | alone | instance | main | remote-as | vrf; Default: )

Configure input multicore processing. Read more in Routing Protocol Multi-core Support article.

  • alone - input and output of each session is processed in its own process, most likely best option when there are a lot of cores and a lot of peers
  • afi, instance, vrf, remote-as - try to run input/output of new session in process with similar parameters
  • main - run input/output in the main process (could potentially increase performance on single-core even possibly on multicore devices with small amount of cores)
  • input - run output in the same process as input (can be set only for output affinity)
.filter(name; Default: )Name of the routing filter chain to be used on input prefixes. Happens after NLRIs are processed. If the chain is not specified, then BGP by defaults accepts everything.
keepalive-time (time [1s..30m]; Default:3m )How long to keep BGP session open after the last received "keepalive" message.
multihop (yes | no; Default: no)Specifies whether the remote peer is more than one hop away.

This option affects outgoing nexthop selection as described in RFC 4271 (for EBGP only, excluding EBGP peers local to the confederation).

It also affects:

  • whether to accept connections from peers that are not in the same network (the remote address of the connection is used for this check);
  • whether to accept incoming routes with NEXT_HOP attribute that is not in the same network as the address used to establish the connection;
  • the target-scope of the routes installed from this peer; routes from multi-hop or IBGP peers resolve their nexthops through IGP routes by default.
name (string; Default: )Name of the BGP template
nexthop-choice (default | force-self | propagate; Default: default)Affects the outgoing NEXT_HOP attribute selection. Note that nexthops set in filters always takes precedence. Also note that nexthop is not changed on route reflection, expect when it's set in filter.
  • default - select the nexthop as described in RFC 4271
  • force-self - always use a local address of the interface that used to connect to the peer as the nexthop;
  • propagate - try to propagate further the nexthop received; i.e. if the route has BGP NEXT_HOP attribute, then use it as the nexthop, otherwise fall back to the default case
no-client-to-client-reflection (yes | no; Default: )Disable client to client route reflection in Route Reflector setups.
no-early-cut (yes | no; Default: )Early cut is the mechanism, to guess (based on default RFC behaviour) what would happen with the sent NPLRI when received by the remote peer. If the algorithm determines that the NLRI is going to be dropped, peer will not even try to send it. However such a behaviour may not be desired in specific scenarios, then then this option should be used to disable early cut feature.
output - group of parameters associate with BGP output

.affinity(afi  | alone | instance | main | remote-as | vrf; Default: )

Configure output multicore processing. Read more in Routing Protocol Multi-core Support article.

  • alone - input and output of each session is processed in its own process, most likely best option when there are a lot of cores and a lot of peers
  • afi, instance, vrf, remote-as - try to run input/output of new session in process with similar parameters
  • main - run input/output in the main process (could potentially increase performance on single-core even possibly on multicore devices with small amount of cores)
  • input - run output in the same process as input (can be set only for output affinity)
.filter(name; Default: )Name of the routing filter selection chain to be used on output prefixes. If the chain is not specified, then BGP by defaults accepts everything.
.network(name; Default: )Name of the address list, used to send local networks. The network is sent only if matching IGP route exists in the routing table.
redistribute (bgp,connected,copy,dhcp,fantasy,modem,ospf,rip,static,vpn; Default: no)Enable redistribution of specified route types.
remove-private-as (yes | no; Default: noIf set, then BGP AS-PATH attribute is removed before sending out route update if attribute contains only private AS numbers.

removal process happens before routing filters are applied and before local AS number is prepended to the AS path.

router-id (IP | name; Default: main )

BGP Router ID to be used. Use the ID from the /routing/router-id configuration by specifying reference name, or set ID directly by specifying IP.

Equal router-ids are also used to group peers into one instance.

routing-table (string; Default: )Name of the routing table BGP connections operates on. By default always use the "main" routing table.
templates (name[,name]; Default: )List of template names from which to inherit parameters. Useful feature, to easily configure groups with overlapping configuration options.
use-bfd (yes | no; Default: no)Whether to use the BFD protocol for faster connection state detection.
vrf (name; Default: main )Name of the VRF, to install routes in.


/routing/bgp/connection

This menu is used to define BGP outgoing connections as well as listen on single or group of remote BGP peer connections.  In addition to connection specific parameters, template specific parameters are also directly exposed in this menu, for easier configuration in simple scenarios (when templates are not necessary).

...