]>
Commit | Line | Data |
---|---|---|
0efdf0fe | 1 | .. _bgp: |
42fc5d26 QY |
2 | |
3 | *** | |
4 | BGP | |
5 | *** | |
6 | ||
8fcedbd2 | 7 | :abbr:`BGP` stands for Border Gateway Protocol. The latest BGP version is 4. |
d1e7591e | 8 | BGP-4 is one of the Exterior Gateway Protocols and the de facto standard |
8fcedbd2 QY |
9 | interdomain routing protocol. BGP-4 is described in :rfc:`1771` and updated by |
10 | :rfc:`4271`. :rfc:`2858` adds multiprotocol support to BGP-4. | |
42fc5d26 | 11 | |
0efdf0fe | 12 | .. _starting-bgp: |
42fc5d26 QY |
13 | |
14 | Starting BGP | |
15 | ============ | |
16 | ||
8fcedbd2 QY |
17 | The default configuration file of *bgpd* is :file:`bgpd.conf`. *bgpd* searches |
18 | the current directory first, followed by |INSTALL_PREFIX_ETC|/bgpd.conf. All of | |
19 | *bgpd*'s commands must be configured in :file:`bgpd.conf` when the integrated | |
20 | config is not being used. | |
42fc5d26 | 21 | |
c1a54c05 | 22 | *bgpd* specific invocation options are described below. Common options may also |
0efdf0fe | 23 | be specified (:ref:`common-invocation-options`). |
42fc5d26 | 24 | |
c1a54c05 | 25 | .. program:: bgpd |
42fc5d26 | 26 | |
c9365894 | 27 | .. option:: -p, --bgp_port <port> |
42fc5d26 | 28 | |
db759bb0 | 29 | Set the bgp protocol's port number. When port number is 0, that means do not |
30 | listen bgp port. | |
42fc5d26 | 31 | |
c9365894 | 32 | .. option:: -l, --listenon |
42fc5d26 | 33 | |
d1aed873 | 34 | Specify specific IP addresses for bgpd to listen on, rather than its default |
c0868e8b | 35 | of ``0.0.0.0`` / ``::``. This can be useful to constrain bgpd to an internal |
d1aed873 AMR |
36 | address, or to run multiple bgpd processes on one host. Multiple addresses |
37 | can be specified. | |
38 | ||
39 | In the following example, bgpd is started listening for connections on the | |
40 | addresses 100.0.1.2 and fd00::2:2. The options -d (runs in daemon mode) and | |
41 | -f (uses specific configuration file) are also used in this example as we | |
42 | are likely to run multiple bgpd instances, each one with different | |
43 | configurations, when using -l option. | |
42fc5d26 | 44 | |
c17537f9 MBG |
45 | Note that this option implies the --no_kernel option, and no learned routes will be installed into the linux kernel. |
46 | ||
d1aed873 AMR |
47 | .. code-block:: shell |
48 | ||
49 | # /usr/lib/frr/bgpd -d -f /some-folder/bgpd.conf -l 100.0.1.2 -l fd00::2:2 | |
50 | ||
11a9a236 DS |
51 | .. option:: -n, --no_kernel |
52 | ||
53 | Do not install learned routes into the linux kernel. This option is useful | |
54 | for a route-reflector environment or if you are running multiple bgp | |
55 | processes in the same namespace. This option is different than the --no_zebra | |
56 | option in that a ZAPI connection is made. | |
57 | ||
8dad2243 DS |
58 | This option can also be toggled during runtime by using the |
59 | ``[no] bgp no-rib`` commands in VTY shell. | |
60 | ||
61 | Note that this option will persist after saving the configuration during | |
62 | runtime, unless unset by the ``no bgp no-rib`` command in VTY shell prior to | |
63 | a configuration write operation. | |
64 | ||
11a9a236 DS |
65 | .. option:: -S, --skip_runas |
66 | ||
67 | Skip the normal process of checking capabilities and changing user and group | |
68 | information. | |
69 | ||
70 | .. option:: -e, --ecmp | |
71 | ||
72 | Run BGP with a limited ecmp capability, that is different than what BGP | |
73 | was compiled with. The value specified must be greater than 0 and less | |
74 | than or equal to the MULTIPATH_NUM specified on compilation. | |
75 | ||
76 | .. option:: -Z, --no_zebra | |
77 | ||
78 | Do not communicate with zebra at all. This is different than the --no_kernel | |
79 | option in that we do not even open a ZAPI connection to the zebra process. | |
80 | ||
81 | .. option:: -s, --socket_size | |
82 | ||
83 | When opening tcp connections to our peers, set the socket send buffer | |
84 | size that the kernel will use for the peers socket. This option | |
85 | is only really useful at a very large scale. Experimentation should | |
86 | be done to see if this is helping or not at the scale you are running | |
87 | at. | |
88 | ||
89 | LABEL MANAGER | |
90 | ------------- | |
91 | ||
92 | .. option:: -I, --int_num | |
93 | ||
94 | Set zclient id. This is required when using Zebra label manager in proxy mode. | |
95 | ||
8fcedbd2 | 96 | .. _bgp-basic-concepts: |
42fc5d26 | 97 | |
8fcedbd2 QY |
98 | Basic Concepts |
99 | ============== | |
42fc5d26 | 100 | |
8fcedbd2 | 101 | .. _bgp-autonomous-systems: |
c3c5a71f | 102 | |
8fcedbd2 QY |
103 | Autonomous Systems |
104 | ------------------ | |
42fc5d26 | 105 | |
c0868e8b QY |
106 | From :rfc:`1930`: |
107 | ||
108 | An AS is a connected group of one or more IP prefixes run by one or more | |
109 | network operators which has a SINGLE and CLEARLY DEFINED routing policy. | |
110 | ||
111 | Each AS has an identifying number associated with it called an :abbr:`ASN | |
112 | (Autonomous System Number)`. This is a two octet value ranging in value from 1 | |
113 | to 65535. The AS numbers 64512 through 65535 are defined as private AS numbers. | |
114 | Private AS numbers must not be advertised on the global Internet. | |
115 | ||
116 | The :abbr:`ASN (Autonomous System Number)` is one of the essential elements of | |
8fcedbd2 | 117 | BGP. BGP is a distance vector routing protocol, and the AS-Path framework |
c0868e8b | 118 | provides distance vector metric and loop detection to BGP. |
42fc5d26 | 119 | |
c0868e8b | 120 | .. seealso:: :rfc:`1930` |
42fc5d26 | 121 | |
8fcedbd2 | 122 | .. _bgp-address-families: |
42fc5d26 | 123 | |
8fcedbd2 QY |
124 | Address Families |
125 | ---------------- | |
42fc5d26 | 126 | |
c0868e8b QY |
127 | Multiprotocol extensions enable BGP to carry routing information for multiple |
128 | network layer protocols. BGP supports an Address Family Identifier (AFI) for | |
129 | IPv4 and IPv6. Support is also provided for multiple sets of per-AFI | |
130 | information via the BGP Subsequent Address Family Identifier (SAFI). FRR | |
131 | supports SAFIs for unicast information, labeled information (:rfc:`3107` and | |
132 | :rfc:`8277`), and Layer 3 VPN information (:rfc:`4364` and :rfc:`4659`). | |
c3c5a71f | 133 | |
8fcedbd2 | 134 | .. _bgp-route-selection: |
42fc5d26 | 135 | |
8fcedbd2 QY |
136 | Route Selection |
137 | --------------- | |
42fc5d26 | 138 | |
8fcedbd2 QY |
139 | The route selection process used by FRR's BGP implementation uses the following |
140 | decision criterion, starting at the top of the list and going towards the | |
141 | bottom until one of the factors can be used. | |
42fc5d26 | 142 | |
8fcedbd2 | 143 | 1. **Weight check** |
42fc5d26 | 144 | |
c1a54c05 | 145 | Prefer higher local weight routes to lower routes. |
42fc5d26 | 146 | |
8fcedbd2 QY |
147 | 2. **Local preference check** |
148 | ||
c1a54c05 | 149 | Prefer higher local preference routes to lower. |
42fc5d26 | 150 | |
8fcedbd2 QY |
151 | 3. **Local route check** |
152 | ||
c1a54c05 | 153 | Prefer local routes (statics, aggregates, redistributed) to received routes. |
42fc5d26 | 154 | |
8fcedbd2 QY |
155 | 4. **AS path length check** |
156 | ||
c1a54c05 | 157 | Prefer shortest hop-count AS_PATHs. |
42fc5d26 | 158 | |
8fcedbd2 QY |
159 | 5. **Origin check** |
160 | ||
c1a54c05 QY |
161 | Prefer the lowest origin type route. That is, prefer IGP origin routes to |
162 | EGP, to Incomplete routes. | |
42fc5d26 | 163 | |
8fcedbd2 QY |
164 | 6. **MED check** |
165 | ||
c1a54c05 | 166 | Where routes with a MED were received from the same AS, prefer the route |
0efdf0fe | 167 | with the lowest MED. :ref:`bgp-med`. |
42fc5d26 | 168 | |
8fcedbd2 QY |
169 | 7. **External check** |
170 | ||
c1a54c05 QY |
171 | Prefer the route received from an external, eBGP peer over routes received |
172 | from other types of peers. | |
42fc5d26 | 173 | |
8fcedbd2 QY |
174 | 8. **IGP cost check** |
175 | ||
c1a54c05 | 176 | Prefer the route with the lower IGP cost. |
42fc5d26 | 177 | |
8fcedbd2 QY |
178 | 9. **Multi-path check** |
179 | ||
c1a54c05 QY |
180 | If multi-pathing is enabled, then check whether the routes not yet |
181 | distinguished in preference may be considered equal. If | |
9e146a81 | 182 | :clicmd:`bgp bestpath as-path multipath-relax` is set, all such routes are |
c1a54c05 QY |
183 | considered equal, otherwise routes received via iBGP with identical AS_PATHs |
184 | or routes received from eBGP neighbours in the same AS are considered equal. | |
42fc5d26 | 185 | |
8fcedbd2 QY |
186 | 10. **Already-selected external check** |
187 | ||
07738543 QY |
188 | Where both routes were received from eBGP peers, then prefer the route |
189 | which is already selected. Note that this check is not applied if | |
190 | :clicmd:`bgp bestpath compare-routerid` is configured. This check can | |
191 | prevent some cases of oscillation. | |
192 | ||
8fcedbd2 QY |
193 | 11. **Router-ID check** |
194 | ||
07738543 QY |
195 | Prefer the route with the lowest `router-ID`. If the route has an |
196 | `ORIGINATOR_ID` attribute, through iBGP reflection, then that router ID is | |
197 | used, otherwise the `router-ID` of the peer the route was received from is | |
198 | used. | |
199 | ||
8fcedbd2 QY |
200 | 12. **Cluster-List length check** |
201 | ||
07738543 QY |
202 | The route with the shortest cluster-list length is used. The cluster-list |
203 | reflects the iBGP reflection path the route has taken. | |
204 | ||
8fcedbd2 QY |
205 | 13. **Peer address** |
206 | ||
07738543 QY |
207 | Prefer the route received from the peer with the higher transport layer |
208 | address, as a last-resort tie-breaker. | |
42fc5d26 | 209 | |
8fcedbd2 QY |
210 | .. _bgp-capability-negotiation: |
211 | ||
212 | Capability Negotiation | |
213 | ---------------------- | |
214 | ||
215 | When adding IPv6 routing information exchange feature to BGP. There were some | |
216 | proposals. :abbr:`IETF (Internet Engineering Task Force)` | |
217 | :abbr:`IDR (Inter Domain Routing)` adopted a proposal called Multiprotocol | |
218 | Extension for BGP. The specification is described in :rfc:`2283`. The protocol | |
219 | does not define new protocols. It defines new attributes to existing BGP. When | |
220 | it is used exchanging IPv6 routing information it is called BGP-4+. When it is | |
221 | used for exchanging multicast routing information it is called MBGP. | |
222 | ||
223 | *bgpd* supports Multiprotocol Extension for BGP. So if a remote peer supports | |
224 | the protocol, *bgpd* can exchange IPv6 and/or multicast routing information. | |
225 | ||
226 | Traditional BGP did not have the feature to detect a remote peer's | |
227 | capabilities, e.g. whether it can handle prefix types other than IPv4 unicast | |
228 | routes. This was a big problem using Multiprotocol Extension for BGP in an | |
229 | operational network. :rfc:`2842` adopted a feature called Capability | |
230 | Negotiation. *bgpd* use this Capability Negotiation to detect the remote peer's | |
231 | capabilities. If a peer is only configured as an IPv4 unicast neighbor, *bgpd* | |
232 | does not send these Capability Negotiation packets (at least not unless other | |
233 | optional BGP features require capability negotiation). | |
234 | ||
235 | By default, FRR will bring up peering with minimal common capability for the | |
236 | both sides. For example, if the local router has unicast and multicast | |
237 | capabilities and the remote router only has unicast capability the local router | |
238 | will establish the connection with unicast only capability. When there are no | |
239 | common capabilities, FRR sends Unsupported Capability error and then resets the | |
240 | connection. | |
241 | ||
8fcedbd2 QY |
242 | .. _bgp-router-configuration: |
243 | ||
244 | BGP Router Configuration | |
245 | ======================== | |
246 | ||
247 | ASN and Router ID | |
248 | ----------------- | |
249 | ||
250 | First of all you must configure BGP router with the :clicmd:`router bgp ASN` | |
251 | command. The AS number is an identifier for the autonomous system. The BGP | |
252 | protocol uses the AS number for detecting whether the BGP connection is | |
253 | internal or external. | |
254 | ||
8fcedbd2 QY |
255 | .. clicmd:: router bgp ASN |
256 | ||
257 | Enable a BGP protocol process with the specified ASN. After | |
258 | this statement you can input any `BGP Commands`. | |
259 | ||
8fcedbd2 QY |
260 | .. clicmd:: bgp router-id A.B.C.D |
261 | ||
262 | This command specifies the router-ID. If *bgpd* connects to *zebra* it gets | |
263 | interface and address information. In that case default router ID value is | |
264 | selected as the largest IP Address of the interfaces. When `router zebra` is | |
265 | not enabled *bgpd* can't get interface information so `router-id` is set to | |
266 | 0.0.0.0. So please set router-id by hand. | |
267 | ||
c8a5e5e1 QY |
268 | |
269 | .. _bgp-multiple-autonomous-systems: | |
270 | ||
271 | Multiple Autonomous Systems | |
272 | --------------------------- | |
273 | ||
274 | FRR's BGP implementation is capable of running multiple autonomous systems at | |
275 | once. Each configured AS corresponds to a :ref:`zebra-vrf`. In the past, to get | |
276 | the same functionality the network administrator had to run a new *bgpd* | |
277 | process; using VRFs allows multiple autonomous systems to be handled in a | |
278 | single process. | |
279 | ||
280 | When using multiple autonomous systems, all router config blocks after the | |
281 | first one must specify a VRF to be the target of BGP's route selection. This | |
282 | VRF must be unique within respect to all other VRFs being used for the same | |
283 | purpose, i.e. two different autonomous systems cannot use the same VRF. | |
284 | However, the same AS can be used with different VRFs. | |
285 | ||
286 | .. note:: | |
287 | ||
288 | The separated nature of VRFs makes it possible to peer a single *bgpd* | |
edde3ce9 QY |
289 | process to itself, on one machine. Note that this can be done fully within |
290 | BGP without a corresponding VRF in the kernel or Zebra, which enables some | |
291 | practical use cases such as :ref:`route reflectors <bgp-route-reflector>` | |
292 | and route servers. | |
c8a5e5e1 QY |
293 | |
294 | Configuration of additional autonomous systems, or of a router that targets a | |
295 | specific VRF, is accomplished with the following command: | |
296 | ||
c8a5e5e1 QY |
297 | .. clicmd:: router bgp ASN vrf VRFNAME |
298 | ||
299 | ``VRFNAME`` is matched against VRFs configured in the kernel. When ``vrf | |
300 | VRFNAME`` is not specified, the BGP protocol process belongs to the default | |
301 | VRF. | |
302 | ||
303 | An example configuration with multiple autonomous systems might look like this: | |
304 | ||
305 | .. code-block:: frr | |
306 | ||
307 | router bgp 1 | |
308 | neighbor 10.0.0.1 remote-as 20 | |
309 | neighbor 10.0.0.2 remote-as 30 | |
310 | ! | |
311 | router bgp 2 vrf blue | |
312 | neighbor 10.0.0.3 remote-as 40 | |
313 | neighbor 10.0.0.4 remote-as 50 | |
314 | ! | |
315 | router bgp 3 vrf red | |
316 | neighbor 10.0.0.5 remote-as 60 | |
317 | neighbor 10.0.0.6 remote-as 70 | |
318 | ... | |
319 | ||
c8a5e5e1 QY |
320 | .. seealso:: :ref:`bgp-vrf-route-leaking` |
321 | .. seealso:: :ref:`zebra-vrf` | |
322 | ||
323 | ||
324 | .. _bgp-views: | |
325 | ||
326 | Views | |
327 | ----- | |
328 | ||
329 | In addition to supporting multiple autonomous systems, FRR's BGP implementation | |
330 | also supports *views*. | |
331 | ||
332 | BGP views are almost the same as normal BGP processes, except that routes | |
195c7461 QY |
333 | selected by BGP are not installed into the kernel routing table. Each BGP view |
334 | provides an independent set of routing information which is only distributed | |
335 | via BGP. Multiple views can be supported, and BGP view information is always | |
336 | independent from other routing protocols and Zebra/kernel routes. BGP views use | |
337 | the core instance (i.e., default VRF) for communication with peers. | |
edde3ce9 | 338 | |
c8a5e5e1 QY |
339 | .. clicmd:: router bgp AS-NUMBER view NAME |
340 | ||
341 | Make a new BGP view. You can use an arbitrary word for the ``NAME``. Routes | |
342 | selected by the view are not installed into the kernel routing table. | |
343 | ||
344 | With this command, you can setup Route Server like below. | |
345 | ||
346 | .. code-block:: frr | |
347 | ||
348 | ! | |
349 | router bgp 1 view 1 | |
350 | neighbor 10.0.0.1 remote-as 2 | |
351 | neighbor 10.0.0.2 remote-as 3 | |
352 | ! | |
353 | router bgp 2 view 2 | |
354 | neighbor 10.0.0.3 remote-as 4 | |
355 | neighbor 10.0.0.4 remote-as 5 | |
356 | ||
c8a5e5e1 QY |
357 | .. clicmd:: show [ip] bgp view NAME |
358 | ||
359 | Display the routing table of BGP view ``NAME``. | |
360 | ||
361 | ||
8fcedbd2 QY |
362 | Route Selection |
363 | --------------- | |
c3c5a71f | 364 | |
29adcd50 | 365 | .. clicmd:: bgp bestpath as-path confed |
42fc5d26 | 366 | |
c1a54c05 QY |
367 | This command specifies that the length of confederation path sets and |
368 | sequences should should be taken into account during the BGP best path | |
369 | decision process. | |
42fc5d26 | 370 | |
29adcd50 | 371 | .. clicmd:: bgp bestpath as-path multipath-relax |
42fc5d26 | 372 | |
c1a54c05 QY |
373 | This command specifies that BGP decision process should consider paths |
374 | of equal AS_PATH length candidates for multipath computation. Without | |
375 | the knob, the entire AS_PATH must match for multipath computation. | |
c3c5a71f | 376 | |
29adcd50 | 377 | .. clicmd:: bgp bestpath compare-routerid |
42fc5d26 | 378 | |
c1a54c05 QY |
379 | Ensure that when comparing routes where both are equal on most metrics, |
380 | including local-pref, AS_PATH length, IGP cost, MED, that the tie is broken | |
381 | based on router-ID. | |
42fc5d26 | 382 | |
c1a54c05 QY |
383 | If this option is enabled, then the already-selected check, where |
384 | already selected eBGP routes are preferred, is skipped. | |
42fc5d26 | 385 | |
c1a54c05 QY |
386 | If a route has an `ORIGINATOR_ID` attribute because it has been reflected, |
387 | that `ORIGINATOR_ID` will be used. Otherwise, the router-ID of the peer the | |
388 | route was received from will be used. | |
42fc5d26 | 389 | |
c1a54c05 QY |
390 | The advantage of this is that the route-selection (at this point) will be |
391 | more deterministic. The disadvantage is that a few or even one lowest-ID | |
d1e7591e | 392 | router may attract all traffic to otherwise-equal paths because of this |
c1a54c05 QY |
393 | check. It may increase the possibility of MED or IGP oscillation, unless |
394 | other measures were taken to avoid these. The exact behaviour will be | |
395 | sensitive to the iBGP and reflection topology. | |
42fc5d26 | 396 | |
ee88563a JM |
397 | .. clicmd:: bgp bestpath peer-type multipath-relax |
398 | ||
399 | This command specifies that BGP decision process should consider paths | |
400 | from all peers for multipath computation. If this option is enabled, | |
401 | paths learned from any of eBGP, iBGP, or confederation neighbors will | |
402 | be multipath if they are otherwise considered equal cost. | |
403 | ||
8fcedbd2 QY |
404 | .. _bgp-distance: |
405 | ||
406 | Administrative Distance Metrics | |
407 | ------------------------------- | |
408 | ||
8fcedbd2 QY |
409 | .. clicmd:: distance bgp (1-255) (1-255) (1-255) |
410 | ||
411 | This command change distance value of BGP. The arguments are the distance | |
412 | values for for external routes, internal routes and local routes | |
413 | respectively. | |
414 | ||
8fcedbd2 QY |
415 | .. clicmd:: distance (1-255) A.B.C.D/M |
416 | ||
8fcedbd2 QY |
417 | .. clicmd:: distance (1-255) A.B.C.D/M WORD |
418 | ||
419 | Sets the administrative distance for a particular route. | |
42fc5d26 | 420 | |
713c64dd DA |
421 | .. _bgp-requires-policy: |
422 | ||
423 | Require policy on EBGP | |
424 | ------------------------------- | |
425 | ||
03750f1e | 426 | .. clicmd:: bgp ebgp-requires-policy |
713c64dd | 427 | |
8955d9e5 | 428 | This command requires incoming and outgoing filters to be applied |
b56f274a DS |
429 | for eBGP sessions as part of RFC-8212 compliance. Without the incoming |
430 | filter, no routes will be accepted. Without the outgoing filter, no | |
431 | routes will be announced. | |
8955d9e5 | 432 | |
b56f274a DS |
433 | This is enabled by default for the traditional configuration and |
434 | turned off by default for datacenter configuration. | |
713c64dd | 435 | |
b3cbe765 DA |
436 | When you enable/disable this option you MUST clear the session. |
437 | ||
62c42b0e DA |
438 | When the incoming or outgoing filter is missing you will see |
439 | "(Policy)" sign under ``show bgp summary``: | |
440 | ||
441 | .. code-block:: frr | |
442 | ||
443 | exit1# show bgp summary | |
444 | ||
6cac2fcc | 445 | IPv4 Unicast Summary (VRF default): |
62c42b0e DA |
446 | BGP router identifier 10.10.10.1, local AS number 65001 vrf-id 0 |
447 | BGP table version 4 | |
448 | RIB entries 7, using 1344 bytes of memory | |
449 | Peers 2, using 43 KiB of memory | |
450 | ||
451 | Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd PfxSnt | |
452 | 192.168.0.2 4 65002 8 10 0 0 0 00:03:09 5 (Policy) | |
453 | fe80:1::2222 4 65002 9 11 0 0 0 00:03:09 (Policy) (Policy) | |
454 | ||
b56f274a DS |
455 | Additionally a `show bgp neighbor` command would indicate in the `For address family:` |
456 | block that: | |
457 | ||
458 | .. code-block:: frr | |
459 | ||
460 | exit1# show bgp neighbor | |
461 | ... | |
462 | For address family: IPv4 Unicast | |
463 | Update group 1, subgroup 1 | |
464 | Packet Queue length 0 | |
465 | Inbound soft reconfiguration allowed | |
466 | Community attribute sent to this neighbor(all) | |
467 | Inbound updates discarded due to missing policy | |
468 | Outbound updates discarded due to missing policy | |
469 | 0 accepted prefixes | |
470 | ||
f0c81afe | 471 | Reject routes with AS_SET or AS_CONFED_SET types |
5031d886 | 472 | ------------------------------------------------ |
f0c81afe | 473 | |
03750f1e | 474 | .. clicmd:: bgp reject-as-sets |
f0c81afe DA |
475 | |
476 | This command enables rejection of incoming and outgoing routes having AS_SET or AS_CONFED_SET type. | |
477 | ||
105227af DA |
478 | Suppress duplicate updates |
479 | -------------------------- | |
480 | ||
03750f1e | 481 | .. clicmd:: bgp suppress-duplicates |
105227af DA |
482 | |
483 | For example, BGP routers can generate multiple identical announcements with | |
484 | empty community attributes if stripped at egress. This is an undesired behavior. | |
485 | Suppress duplicate updates if the route actually not changed. | |
486 | Default: enabled. | |
487 | ||
835e9c5d DA |
488 | Disable checking if nexthop is connected on EBGP sessions |
489 | --------------------------------------------------------- | |
490 | ||
03750f1e | 491 | .. clicmd:: bgp disable-ebgp-connected-route-check |
835e9c5d DA |
492 | |
493 | This command is used to disable the connection verification process for EBGP peering sessions | |
494 | that are reachable by a single hop but are configured on a loopback interface or otherwise | |
495 | configured with a non-directly connected IP address. | |
496 | ||
0efdf0fe | 497 | .. _bgp-route-flap-dampening: |
42fc5d26 | 498 | |
8fcedbd2 QY |
499 | Route Flap Dampening |
500 | -------------------- | |
42fc5d26 | 501 | |
03750f1e | 502 | .. clicmd:: bgp dampening [(1-45) [(1-20000) (1-20000) (1-255)]] |
c1a54c05 | 503 | |
54b34709 DS |
504 | This command enables (with optionally specified dampening parameters) or |
505 | disables route-flap dampening for all routes of a BGP instance. | |
506 | ||
03750f1e | 507 | .. clicmd:: neighbor PEER dampening [(1-45) [(1-20000) (1-20000) (1-255)]] |
54b34709 DS |
508 | |
509 | This command enables (with optionally specified dampening parameters) or | |
510 | disables route-flap dampening for all routes learned from a BGP peer. | |
511 | ||
03750f1e | 512 | .. clicmd:: neighbor GROUP dampening [(1-45) [(1-20000) (1-20000) (1-255)]] |
54b34709 DS |
513 | |
514 | This command enables (with optionally specified dampening parameters) or | |
515 | disables route-flap dampening for all routes learned from peers of a peer | |
516 | group. | |
42fc5d26 | 517 | |
c1a54c05 | 518 | half-life |
54b34709 | 519 | Half-life time for the penalty in minutes (default value: 15). |
42fc5d26 | 520 | |
c1a54c05 | 521 | reuse-threshold |
54b34709 | 522 | Value to start reusing a route (default value: 750). |
42fc5d26 | 523 | |
c1a54c05 | 524 | suppress-threshold |
54b34709 | 525 | Value to start suppressing a route (default value: 2000). |
42fc5d26 | 526 | |
c1a54c05 | 527 | max-suppress |
54b34709 DS |
528 | Maximum duration to suppress a stable route in minutes (default value: |
529 | 60). | |
42fc5d26 | 530 | |
c1a54c05 | 531 | The route-flap damping algorithm is compatible with :rfc:`2439`. The use of |
54b34709 | 532 | these commands is not recommended nowadays. |
42fc5d26 | 533 | |
319a7d06 DA |
534 | At the moment, route-flap dampening is not working per VRF and is working only |
535 | for IPv4 unicast and multicast. | |
536 | ||
54b34709 DS |
537 | With different parameter sets configurable for BGP instances, peer groups and |
538 | peers, the active dampening profile for a route is chosen on the fly, | |
539 | allowing for various changes in configuration (i.e. peer group memberships) | |
540 | during runtime. The parameter sets are taking precedence in the following | |
541 | order: | |
542 | ||
543 | 1. Peer | |
544 | 2. Peer group | |
545 | 3. BGP instance | |
546 | ||
547 | The negating commands do not allow to exclude a peer/peer group from a peer | |
548 | group/BGP instances configuration. | |
549 | ||
c1a54c05 | 550 | .. seealso:: |
8fcedbd2 | 551 | https://www.ripe.net/publications/docs/ripe-378 |
42fc5d26 | 552 | |
0efdf0fe | 553 | .. _bgp-med: |
42fc5d26 | 554 | |
8fcedbd2 QY |
555 | Multi-Exit Discriminator |
556 | ------------------------ | |
42fc5d26 | 557 | |
8fcedbd2 | 558 | The BGP :abbr:`MED (Multi-Exit Discriminator)` attribute has properties which |
c1a54c05 QY |
559 | can cause subtle convergence problems in BGP. These properties and problems |
560 | have proven to be hard to understand, at least historically, and may still not | |
561 | be widely understood. The following attempts to collect together and present | |
562 | what is known about MED, to help operators and FRR users in designing and | |
563 | configuring their networks. | |
42fc5d26 | 564 | |
07a17e6d QY |
565 | The BGP :abbr:`MED` attribute is intended to allow one AS to indicate its |
566 | preferences for its ingress points to another AS. The MED attribute will not be | |
567 | propagated on to another AS by the receiving AS - it is 'non-transitive' in the | |
568 | BGP sense. | |
42fc5d26 | 569 | |
c1a54c05 QY |
570 | E.g., if AS X and AS Y have 2 different BGP peering points, then AS X might set |
571 | a MED of 100 on routes advertised at one and a MED of 200 at the other. When AS | |
572 | Y selects between otherwise equal routes to or via AS X, AS Y should prefer to | |
573 | take the path via the lower MED peering of 100 with AS X. Setting the MED | |
574 | allows an AS to influence the routing taken to it within another, neighbouring | |
575 | AS. | |
42fc5d26 QY |
576 | |
577 | In this use of MED it is not really meaningful to compare the MED value on | |
c1a54c05 QY |
578 | routes where the next AS on the paths differs. E.g., if AS Y also had a route |
579 | for some destination via AS Z in addition to the routes from AS X, and AS Z had | |
580 | also set a MED, it wouldn't make sense for AS Y to compare AS Z's MED values to | |
581 | those of AS X. The MED values have been set by different administrators, with | |
582 | different frames of reference. | |
42fc5d26 QY |
583 | |
584 | The default behaviour of BGP therefore is to not compare MED values across | |
dc1046f7 | 585 | routes received from different neighbouring ASes. In FRR this is done by |
c1a54c05 QY |
586 | comparing the neighbouring, left-most AS in the received AS_PATHs of the routes |
587 | and only comparing MED if those are the same. | |
588 | ||
589 | Unfortunately, this behaviour of MED, of sometimes being compared across routes | |
590 | and sometimes not, depending on the properties of those other routes, means MED | |
591 | can cause the order of preference over all the routes to be undefined. That is, | |
592 | given routes A, B, and C, if A is preferred to B, and B is preferred to C, then | |
593 | a well-defined order should mean the preference is transitive (in the sense of | |
013f9762 | 594 | orders [#med-transitivity-rant]_) and that A would be preferred to C. |
42fc5d26 | 595 | |
c3c5a71f QY |
596 | However, when MED is involved this need not be the case. With MED it is |
597 | possible that C is actually preferred over A. So A is preferred to B, B is | |
598 | preferred to C, but C is preferred to A. This can be true even where BGP | |
c1a54c05 QY |
599 | defines a deterministic 'most preferred' route out of the full set of A,B,C. |
600 | With MED, for any given set of routes there may be a deterministically | |
601 | preferred route, but there need not be any way to arrange them into any order | |
602 | of preference. With unmodified MED, the order of preference of routes literally | |
603 | becomes undefined. | |
42fc5d26 | 604 | |
c3c5a71f | 605 | That MED can induce non-transitive preferences over routes can cause issues. |
c1a54c05 QY |
606 | Firstly, it may be perceived to cause routing table churn locally at speakers; |
607 | secondly, and more seriously, it may cause routing instability in iBGP | |
608 | topologies, where sets of speakers continually oscillate between different | |
609 | paths. | |
42fc5d26 | 610 | |
c3c5a71f | 611 | The first issue arises from how speakers often implement routing decisions. |
c1a54c05 QY |
612 | Though BGP defines a selection process that will deterministically select the |
613 | same route as best at any given speaker, even with MED, that process requires | |
614 | evaluating all routes together. For performance and ease of implementation | |
615 | reasons, many implementations evaluate route preferences in a pair-wise fashion | |
616 | instead. Given there is no well-defined order when MED is involved, the best | |
617 | route that will be chosen becomes subject to implementation details, such as | |
618 | the order the routes are stored in. That may be (locally) non-deterministic, | |
619 | e.g.: it may be the order the routes were received in. | |
42fc5d26 QY |
620 | |
621 | This indeterminism may be considered undesirable, though it need not cause | |
c1a54c05 QY |
622 | problems. It may mean additional routing churn is perceived, as sometimes more |
623 | updates may be produced than at other times in reaction to some event . | |
42fc5d26 QY |
624 | |
625 | This first issue can be fixed with a more deterministic route selection that | |
c3c5a71f | 626 | ensures routes are ordered by the neighbouring AS during selection. |
9e146a81 | 627 | :clicmd:`bgp deterministic-med`. This may reduce the number of updates as routes |
c1a54c05 QY |
628 | are received, and may in some cases reduce routing churn. Though, it could |
629 | equally deterministically produce the largest possible set of updates in | |
630 | response to the most common sequence of received updates. | |
42fc5d26 QY |
631 | |
632 | A deterministic order of evaluation tends to imply an additional overhead of | |
c3c5a71f | 633 | sorting over any set of n routes to a destination. The implementation of |
dc1046f7 | 634 | deterministic MED in FRR scales significantly worse than most sorting |
c1a54c05 QY |
635 | algorithms at present, with the number of paths to a given destination. That |
636 | number is often low enough to not cause any issues, but where there are many | |
637 | paths, the deterministic comparison may quickly become increasingly expensive | |
638 | in terms of CPU. | |
639 | ||
640 | Deterministic local evaluation can *not* fix the second, more major, issue of | |
641 | MED however. Which is that the non-transitive preference of routes MED can | |
642 | cause may lead to routing instability or oscillation across multiple speakers | |
643 | in iBGP topologies. This can occur with full-mesh iBGP, but is particularly | |
644 | problematic in non-full-mesh iBGP topologies that further reduce the routing | |
645 | information known to each speaker. This has primarily been documented with iBGP | |
749afd7d RF |
646 | :ref:`route-reflection <bgp-route-reflector>` topologies. However, any |
647 | route-hiding technologies potentially could also exacerbate oscillation with MED. | |
c1a54c05 QY |
648 | |
649 | This second issue occurs where speakers each have only a subset of routes, and | |
650 | there are cycles in the preferences between different combinations of routes - | |
651 | as the undefined order of preference of MED allows - and the routes are | |
652 | distributed in a way that causes the BGP speakers to 'chase' those cycles. This | |
653 | can occur even if all speakers use a deterministic order of evaluation in route | |
654 | selection. | |
655 | ||
656 | E.g., speaker 4 in AS A might receive a route from speaker 2 in AS X, and from | |
657 | speaker 3 in AS Y; while speaker 5 in AS A might receive that route from | |
658 | speaker 1 in AS Y. AS Y might set a MED of 200 at speaker 1, and 100 at speaker | |
659 | 3. I.e, using ASN:ID:MED to label the speakers: | |
42fc5d26 QY |
660 | |
661 | :: | |
662 | ||
c1a54c05 QY |
663 | . |
664 | /---------------\\ | |
42fc5d26 | 665 | X:2------|--A:4-------A:5--|-Y:1:200 |
c1a54c05 QY |
666 | Y:3:100--|-/ | |
667 | \\---------------/ | |
c3c5a71f | 668 | |
42fc5d26 | 669 | |
42fc5d26 | 670 | |
c1a54c05 QY |
671 | Assuming all other metrics are equal (AS_PATH, ORIGIN, 0 IGP costs), then based |
672 | on the RFC4271 decision process speaker 4 will choose X:2 over Y:3:100, based | |
673 | on the lower ID of 2. Speaker 4 advertises X:2 to speaker 5. Speaker 5 will | |
674 | continue to prefer Y:1:200 based on the ID, and advertise this to speaker 4. | |
675 | Speaker 4 will now have the full set of routes, and the Y:1:200 it receives | |
676 | from 5 will beat X:2, but when speaker 4 compares Y:1:200 to Y:3:100 the MED | |
677 | check now becomes active as the ASes match, and now Y:3:100 is preferred. | |
678 | Speaker 4 therefore now advertises Y:3:100 to 5, which will also agrees that | |
679 | Y:3:100 is preferred to Y:1:200, and so withdraws the latter route from 4. | |
680 | Speaker 4 now has only X:2 and Y:3:100, and X:2 beats Y:3:100, and so speaker 4 | |
681 | implicitly updates its route to speaker 5 to X:2. Speaker 5 sees that Y:1:200 | |
682 | beats X:2 based on the ID, and advertises Y:1:200 to speaker 4, and the cycle | |
683 | continues. | |
42fc5d26 QY |
684 | |
685 | The root cause is the lack of a clear order of preference caused by how MED | |
686 | sometimes is and sometimes is not compared, leading to this cycle in the | |
687 | preferences between the routes: | |
688 | ||
689 | :: | |
690 | ||
c1a54c05 QY |
691 | . |
692 | /---> X:2 ---beats---> Y:3:100 --\\ | |
693 | | | | |
694 | | | | |
695 | \\---beats--- Y:1:200 <---beats---/ | |
c3c5a71f | 696 | |
42fc5d26 | 697 | |
42fc5d26 QY |
698 | |
699 | This particular type of oscillation in full-mesh iBGP topologies can be | |
700 | avoided by speakers preferring already selected, external routes rather than | |
c1a54c05 QY |
701 | choosing to update to new a route based on a post-MED metric (e.g. router-ID), |
702 | at the cost of a non-deterministic selection process. FRR implements this, as | |
703 | do many other implementations, so long as it is not overridden by setting | |
9e146a81 | 704 | :clicmd:`bgp bestpath compare-routerid`, and see also |
8fcedbd2 | 705 | :ref:`bgp-route-selection`. |
42fc5d26 QY |
706 | |
707 | However, more complex and insidious cycles of oscillation are possible with | |
c3c5a71f | 708 | iBGP route-reflection, which are not so easily avoided. These have been |
c1a54c05 QY |
709 | documented in various places. See, e.g.: |
710 | ||
711 | - [bgp-route-osci-cond]_ | |
712 | - [stable-flexible-ibgp]_ | |
713 | - [ibgp-correctness]_ | |
714 | ||
715 | for concrete examples and further references. | |
716 | ||
717 | There is as of this writing *no* known way to use MED for its original purpose; | |
718 | *and* reduce routing information in iBGP topologies; *and* be sure to avoid the | |
719 | instability problems of MED due the non-transitive routing preferences it can | |
720 | induce; in general on arbitrary networks. | |
721 | ||
722 | There may be iBGP topology specific ways to reduce the instability risks, even | |
723 | while using MED, e.g.: by constraining the reflection topology and by tuning | |
013f9762 | 724 | IGP costs between route-reflector clusters, see :rfc:`3345` for details. In the |
c1a54c05 QY |
725 | near future, the Add-Path extension to BGP may also solve MED oscillation while |
726 | still allowing MED to be used as intended, by distributing "best-paths per | |
727 | neighbour AS". This would be at the cost of distributing at least as many | |
728 | routes to all speakers as a full-mesh iBGP would, if not more, while also | |
729 | imposing similar CPU overheads as the "Deterministic MED" feature at each | |
730 | Add-Path reflector. | |
42fc5d26 QY |
731 | |
732 | More generally, the instability problems that MED can introduce on more | |
733 | complex, non-full-mesh, iBGP topologies may be avoided either by: | |
734 | ||
013f9762 | 735 | - Setting :clicmd:`bgp always-compare-med`, however this allows MED to be compared |
42fc5d26 QY |
736 | across values set by different neighbour ASes, which may not produce |
737 | coherent desirable results, of itself. | |
4b44467c | 738 | - Effectively ignoring MED by setting MED to the same value (e.g.: 0) using |
013f9762 QY |
739 | :clicmd:`set metric METRIC` on all received routes, in combination with |
740 | setting :clicmd:`bgp always-compare-med` on all speakers. This is the simplest | |
42fc5d26 QY |
741 | and most performant way to avoid MED oscillation issues, where an AS is happy |
742 | not to allow neighbours to inject this problematic metric. | |
743 | ||
42fc5d26 QY |
744 | As MED is evaluated after the AS_PATH length check, another possible use for |
745 | MED is for intra-AS steering of routes with equal AS_PATH length, as an | |
c1a54c05 QY |
746 | extension of the last case above. As MED is evaluated before IGP metric, this |
747 | can allow cold-potato routing to be implemented to send traffic to preferred | |
748 | hand-offs with neighbours, rather than the closest hand-off according to the | |
749 | IGP metric. | |
750 | ||
751 | Note that even if action is taken to address the MED non-transitivity issues, | |
752 | other oscillations may still be possible. E.g., on IGP cost if iBGP and IGP | |
753 | topologies are at cross-purposes with each other - see the Flavel and Roughan | |
754 | paper above for an example. Hence the guideline that the iBGP topology should | |
755 | follow the IGP topology. | |
756 | ||
29adcd50 | 757 | .. clicmd:: bgp deterministic-med |
42fc5d26 | 758 | |
c1a54c05 QY |
759 | Carry out route-selection in way that produces deterministic answers |
760 | locally, even in the face of MED and the lack of a well-defined order of | |
761 | preference it can induce on routes. Without this option the preferred route | |
762 | with MED may be determined largely by the order that routes were received | |
763 | in. | |
42fc5d26 | 764 | |
c1a54c05 QY |
765 | Setting this option will have a performance cost that may be noticeable when |
766 | there are many routes for each destination. Currently in FRR it is | |
767 | implemented in a way that scales poorly as the number of routes per | |
768 | destination increases. | |
42fc5d26 | 769 | |
c1a54c05 | 770 | The default is that this option is not set. |
42fc5d26 QY |
771 | |
772 | Note that there are other sources of indeterminism in the route selection | |
773 | process, specifically, the preference for older and already selected routes | |
8fcedbd2 | 774 | from eBGP peers, :ref:`bgp-route-selection`. |
42fc5d26 | 775 | |
29adcd50 | 776 | .. clicmd:: bgp always-compare-med |
42fc5d26 | 777 | |
c1a54c05 QY |
778 | Always compare the MED on routes, even when they were received from |
779 | different neighbouring ASes. Setting this option makes the order of | |
780 | preference of routes more defined, and should eliminate MED induced | |
781 | oscillations. | |
42fc5d26 | 782 | |
c1a54c05 | 783 | If using this option, it may also be desirable to use |
9e146a81 | 784 | :clicmd:`set metric METRIC` to set MED to 0 on routes received from external |
c1a54c05 | 785 | neighbours. |
42fc5d26 | 786 | |
9e146a81 QY |
787 | This option can be used, together with :clicmd:`set metric METRIC` to use |
788 | MED as an intra-AS metric to steer equal-length AS_PATH routes to, e.g., | |
789 | desired exit points. | |
42fc5d26 | 790 | |
efcb2ebb | 791 | |
792 | .. _bgp-graceful-restart: | |
793 | ||
794 | Graceful Restart | |
795 | ---------------- | |
796 | ||
797 | BGP graceful restart functionality as defined in | |
798 | `RFC-4724 <https://tools.ietf.org/html/rfc4724/>`_ defines the mechanisms that | |
799 | allows BGP speaker to continue to forward data packets along known routes | |
800 | while the routing protocol information is being restored. | |
801 | ||
802 | ||
803 | Usually, when BGP on a router restarts, all the BGP peers detect that the | |
804 | session went down and then came up. This "down/up" transition results in a | |
805 | "routing flap" and causes BGP route re-computation, generation of BGP routing | |
806 | updates, and unnecessary churn to the forwarding tables. | |
807 | ||
808 | The following functionality is provided by graceful restart: | |
809 | ||
810 | 1. The feature allows the restarting router to indicate to the helping peer the | |
811 | routes it can preserve in its forwarding plane during control plane restart | |
812 | by sending graceful restart capability in the OPEN message sent during | |
813 | session establishment. | |
814 | 2. The feature allows helping router to advertise to all other peers the routes | |
815 | received from the restarting router which are preserved in the forwarding | |
816 | plane of the restarting router during control plane restart. | |
817 | ||
818 | ||
819 | :: | |
820 | ||
821 | ||
822 | ||
823 | (R1)-----------------------------------------------------------------(R2) | |
824 | ||
825 | 1. BGP Graceful Restart Capability exchanged between R1 & R2. | |
826 | ||
827 | <---------------------------------------------------------------------> | |
828 | ||
829 | 2. Kill BGP Process at R1. | |
830 | ||
831 | ----------------------------------------------------------------------> | |
832 | ||
833 | 3. R2 Detects the above BGP Restart & verifies BGP Restarting | |
834 | Capability of R1. | |
835 | ||
836 | 4. Start BGP Process at R1. | |
837 | ||
838 | 5. Re-establish the BGP session between R1 & R2. | |
839 | ||
840 | <---------------------------------------------------------------------> | |
841 | ||
842 | 6. R2 Send initial route updates, followed by End-Of-Rib. | |
843 | ||
844 | <---------------------------------------------------------------------- | |
845 | ||
846 | 7. R1 was waiting for End-Of-Rib from R2 & which has been received | |
847 | now. | |
848 | ||
849 | 8. R1 now runs BGP Best-Path algorithm. Send Initial BGP Update, | |
850 | followed by End-Of Rib | |
851 | ||
852 | <---------------------------------------------------------------------> | |
853 | ||
854 | ||
4907bcd8 | 855 | .. _bgp-GR-preserve-forwarding-state: |
856 | ||
857 | BGP-GR Preserve-Forwarding State | |
858 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
859 | ||
860 | BGP OPEN message carrying optional capabilities for Graceful Restart has | |
861 | 8 bit “Flags for Address Family” for given AFI and SAFI. This field contains | |
862 | bit flags relating to routes that were advertised with the given AFI and SAFI. | |
863 | ||
864 | .. code-block:: frr | |
865 | ||
866 | 0 1 2 3 4 5 6 7 | |
867 | +-+-+-+-+-+-+-+-+ | |
868 | |F| Reserved | | |
869 | +-+-+-+-+-+-+-+-+ | |
870 | ||
871 | The most significant bit is defined as the Forwarding State (F) bit, which | |
872 | can be used to indicate whether the forwarding state for routes that were | |
873 | advertised with the given AFI and SAFI has indeed been preserved during the | |
874 | previous BGP restart. When set (value 1), the bit indicates that the | |
875 | forwarding state has been preserved. | |
876 | The remaining bits are reserved and MUST be set to zero by the sender and | |
877 | ignored by the receiver. | |
878 | ||
4907bcd8 | 879 | .. clicmd:: bgp graceful-restart preserve-fw-state |
880 | ||
881 | FRR gives us the option to enable/disable the "F" flag using this specific | |
882 | vty command. However, it doesn't have the option to enable/disable | |
883 | this flag only for specific AFI/SAFI i.e. when this command is used, it | |
884 | applied to all the supported AFI/SAFI combinations for this peer. | |
885 | ||
efcb2ebb | 886 | .. _bgp-end-of-rib-message: |
887 | ||
888 | End-of-RIB (EOR) message | |
889 | ^^^^^^^^^^^^^^^^^^^^^^^^ | |
890 | ||
891 | An UPDATE message with no reachable Network Layer Reachability Information | |
892 | (NLRI) and empty withdrawn NLRI is specified as the End-of-RIB marker that can | |
893 | be used by a BGP speaker to indicate to its peer the completion of the initial | |
894 | routing update after the session is established. | |
895 | ||
896 | For the IPv4 unicast address family, the End-of-RIB marker is an UPDATE message | |
897 | with the minimum length. For any other address family, it is an UPDATE message | |
898 | that contains only the MP_UNREACH_NLRI attribute with no withdrawn routes for | |
899 | that <AFI, SAFI>. | |
900 | ||
901 | Although the End-of-RIB marker is specified for the purpose of BGP graceful | |
902 | restart, it is noted that the generation of such a marker upon completion of | |
903 | the initial update would be useful for routing convergence in general, and thus | |
904 | the practice is recommended. | |
905 | ||
906 | .. _bgp-route-selection-deferral-timer: | |
907 | ||
908 | Route Selection Deferral Timer | |
909 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
910 | ||
911 | Specifies the time the restarting router defers the route selection process | |
912 | after restart. | |
913 | ||
914 | Restarting Router : The usage of route election deferral timer is specified | |
915 | in https://tools.ietf.org/html/rfc4724#section-4.1 | |
916 | ||
917 | Once the session between the Restarting Speaker and the Receiving Speaker is | |
918 | re-established, the Restarting Speaker will receive and process BGP messages | |
919 | from its peers. | |
920 | ||
921 | However, it MUST defer route selection for an address family until it either. | |
922 | ||
923 | 1. Receives the End-of-RIB marker from all its peers (excluding the ones with | |
924 | the "Restart State" bit set in the received capability and excluding the ones | |
925 | that do not advertise the graceful restart capability). | |
926 | 2. The Selection_Deferral_Timer timeout. | |
927 | ||
efcb2ebb | 928 | .. clicmd:: bgp graceful-restart select-defer-time (0-3600) |
929 | ||
930 | This is command, will set deferral time to value specified. | |
931 | ||
932 | ||
efcb2ebb | 933 | .. clicmd:: bgp graceful-restart rib-stale-time (1-3600) |
934 | ||
935 | This is command, will set the time for which stale routes are kept in RIB. | |
936 | ||
2b3de9e5 DA |
937 | .. clicmd:: bgp graceful-restart stalepath-time (1-4095) |
938 | ||
939 | This is command, will set the max time (in seconds) to hold onto | |
940 | restarting peer's stale paths. | |
941 | ||
942 | It also controls Enhanced Route-Refresh timer. | |
943 | ||
944 | If this command is configured and the router does not receive a Route-Refresh EoRR | |
945 | message, the router removes the stale routes from the BGP table after the timer | |
946 | expires. The stale path timer is started when the router receives a Route-Refresh | |
947 | BoRR message. | |
948 | ||
efcb2ebb | 949 | .. _bgp-per-peer-graceful-restart: |
950 | ||
951 | BGP Per Peer Graceful Restart | |
952 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
953 | ||
954 | Ability to enable and disable graceful restart, helper and no GR at all mode | |
955 | functionality at peer level. | |
956 | ||
957 | So bgp graceful restart can be enabled at modes global BGP level or at per | |
958 | peer level. There are two FSM, one for BGP GR global mode and other for peer | |
959 | per GR. | |
960 | ||
961 | Default global mode is helper and default peer per mode is inherit from global. | |
962 | If per peer mode is configured, the GR mode of this particular peer will | |
963 | override the global mode. | |
964 | ||
2ba1fe69 | 965 | .. _bgp-GR-global-mode-cmd: |
efcb2ebb | 966 | |
967 | BGP GR Global Mode Commands | |
968 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
969 | ||
efcb2ebb | 970 | .. clicmd:: bgp graceful-restart |
971 | ||
972 | This command will enable BGP graceful restart ifunctionality at the global | |
973 | level. | |
974 | ||
efcb2ebb | 975 | .. clicmd:: bgp graceful-restart disable |
976 | ||
977 | This command will disable both the functionality graceful restart and helper | |
978 | mode. | |
979 | ||
980 | ||
981 | .. _bgp-GR-peer-mode-cmd: | |
982 | ||
983 | BGP GR Peer Mode Commands | |
984 | ^^^^^^^^^^^^^^^^^^^^^^^^^ | |
985 | ||
efcb2ebb | 986 | .. clicmd:: neighbor A.B.C.D graceful-restart |
987 | ||
988 | This command will enable BGP graceful restart ifunctionality at the peer | |
989 | level. | |
990 | ||
efcb2ebb | 991 | .. clicmd:: neighbor A.B.C.D graceful-restart-helper |
992 | ||
993 | This command will enable BGP graceful restart helper only functionality | |
994 | at the peer level. | |
995 | ||
efcb2ebb | 996 | .. clicmd:: neighbor A.B.C.D graceful-restart-disable |
997 | ||
998 | This command will disable the entire BGP graceful restart functionality | |
999 | at the peer level. | |
1000 | ||
1001 | ||
df465afe DS |
1002 | .. _bgp-shutdown: |
1003 | ||
1004 | Administrative Shutdown | |
1005 | ----------------------- | |
1006 | ||
03750f1e | 1007 | .. clicmd:: bgp shutdown [message MSG...] |
df465afe DS |
1008 | |
1009 | Administrative shutdown of all peers of a bgp instance. Drop all BGP peers, | |
1010 | but preserve their configurations. The peers are notified in accordance with | |
1011 | `RFC 8203 <https://tools.ietf.org/html/rfc8203/>`_ by sending a | |
1012 | ``NOTIFICATION`` message with error code ``Cease`` and subcode | |
1013 | ``Administrative Shutdown`` prior to terminating connections. This global | |
1014 | shutdown is independent of the neighbor shutdown, meaning that individually | |
1015 | shut down peers will not be affected by lifting it. | |
1016 | ||
1017 | An optional shutdown message `MSG` can be specified. | |
1018 | ||
1019 | ||
0efdf0fe | 1020 | .. _bgp-network: |
42fc5d26 | 1021 | |
8fcedbd2 QY |
1022 | Networks |
1023 | -------- | |
42fc5d26 | 1024 | |
c1a54c05 | 1025 | .. clicmd:: network A.B.C.D/M |
42fc5d26 | 1026 | |
9eb95b3b | 1027 | This command adds the announcement network. |
c3c5a71f | 1028 | |
9eb95b3b QY |
1029 | .. code-block:: frr |
1030 | ||
1031 | router bgp 1 | |
1032 | address-family ipv4 unicast | |
1033 | network 10.0.0.0/8 | |
1034 | exit-address-family | |
42fc5d26 | 1035 | |
c1a54c05 QY |
1036 | This configuration example says that network 10.0.0.0/8 will be |
1037 | announced to all neighbors. Some vendors' routers don't advertise | |
1038 | routes if they aren't present in their IGP routing tables; `bgpd` | |
1039 | doesn't care about IGP routes when announcing its routes. | |
c3c5a71f | 1040 | |
42fc5d26 | 1041 | |
03750f1e | 1042 | .. clicmd:: bgp network import-check |
f990a416 DS |
1043 | |
1044 | This configuration modifies the behavior of the network statement. | |
1045 | If you have this configured the underlying network must exist in | |
1046 | the rib. If you have the [no] form configured then BGP will not | |
1047 | check for the networks existence in the rib. For versions 7.3 and | |
1048 | before frr defaults for datacenter were the network must exist, | |
1049 | traditional did not check for existence. For versions 7.4 and beyond | |
1050 | both traditional and datacenter the network must exist. | |
1051 | ||
ef1b6319 | 1052 | .. _bgp-ipv6-support: |
547ba033 MH |
1053 | |
1054 | IPv6 Support | |
1055 | ------------ | |
1056 | ||
03750f1e | 1057 | .. clicmd:: neighbor A.B.C.D activate |
547ba033 | 1058 | |
ef1b6319 | 1059 | This configuration modifies whether to enable an address family for a |
547ba033 MH |
1060 | specific neighbor. By default only the IPv4 unicast address family is |
1061 | enabled. | |
1062 | ||
1063 | .. code-block:: frr | |
1064 | ||
1065 | router bgp 1 | |
1066 | address-family ipv6 unicast | |
1067 | neighbor 2001:0DB8::1 activate | |
1068 | network 2001:0DB8:5009::/64 | |
1069 | exit-address-family | |
1070 | ||
1071 | This configuration example says that network 2001:0DB8:5009::/64 will be | |
1072 | announced and enables the neighbor 2001:0DB8::1 to receive this announcement. | |
1073 | ||
547ba033 MH |
1074 | By default, only the IPv4 unicast address family is announced to all |
1075 | neighbors. Using the 'no bgp default ipv4-unicast' configuration overrides | |
1076 | this default so that all address families need to be enabled explicitly. | |
1077 | ||
1078 | .. code-block:: frr | |
1079 | ||
1080 | router bgp 1 | |
1081 | no bgp default ipv4-unicast | |
1082 | neighbor 10.10.10.1 remote-as 2 | |
1083 | neighbor 2001:0DB8::1 remote-as 3 | |
1084 | address-family ipv4 unicast | |
1085 | neighbor 10.10.10.1 activate | |
1086 | network 192.168.1.0/24 | |
1087 | exit-address-family | |
1088 | address-family ipv6 unicast | |
1089 | neighbor 2001:0DB8::1 activate | |
1090 | network 2001:0DB8:5009::/64 | |
1091 | exit-address-family | |
1092 | ||
1093 | This configuration demonstrates how the 'no bgp default ipv4-unicast' might | |
1094 | be used in a setup with two upstreams where each of the upstreams should only | |
1095 | receive either IPv4 or IPv6 annocuments. | |
1096 | ||
2c853e5e DA |
1097 | Using the ``bgp default ipv6-unicast`` configuration, IPv6 unicast |
1098 | address family is enabled by default for all new neighbors. | |
1099 | ||
547ba033 | 1100 | |
8fcedbd2 | 1101 | .. _bgp-route-aggregation: |
42fc5d26 QY |
1102 | |
1103 | Route Aggregation | |
1104 | ----------------- | |
1105 | ||
5101fece | 1106 | .. _bgp-route-aggregation-ipv4: |
1107 | ||
1108 | Route Aggregation-IPv4 Address Family | |
1109 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
1110 | ||
c1a54c05 | 1111 | .. clicmd:: aggregate-address A.B.C.D/M |
c3c5a71f | 1112 | |
c1a54c05 | 1113 | This command specifies an aggregate address. |
42fc5d26 | 1114 | |
ac2201bb DA |
1115 | .. clicmd:: aggregate-address A.B.C.D/M route-map NAME |
1116 | ||
1117 | Apply a route-map for an aggregated prefix. | |
1118 | ||
a87d2ef7 DA |
1119 | .. clicmd:: aggregate-address A.B.C.D/M origin <egp|igp|incomplete> |
1120 | ||
1121 | Override ORIGIN for an aggregated prefix. | |
1122 | ||
c1a54c05 | 1123 | .. clicmd:: aggregate-address A.B.C.D/M as-set |
42fc5d26 | 1124 | |
c1a54c05 QY |
1125 | This command specifies an aggregate address. Resulting routes include |
1126 | AS set. | |
42fc5d26 | 1127 | |
c1a54c05 | 1128 | .. clicmd:: aggregate-address A.B.C.D/M summary-only |
c3c5a71f | 1129 | |
d1e7591e | 1130 | This command specifies an aggregate address. Aggregated routes will |
b91bf5bd | 1131 | not be announced. |
42fc5d26 | 1132 | |
01338ba1 RZ |
1133 | .. clicmd:: aggregate-address A.B.C.D/M matching-MED-only |
1134 | ||
1135 | Configure the aggregated address to only be created when the routes MED | |
1136 | match, otherwise no aggregated route will be created. | |
1137 | ||
8fbb9c95 RZ |
1138 | .. clicmd:: aggregate-address A.B.C.D/M suppress-map NAME |
1139 | ||
1140 | Similar to `summary-only`, but will only suppress more specific routes that | |
1141 | are matched by the selected route-map. | |
1142 | ||
ac2201bb | 1143 | |
03750f1e QY |
1144 | This configuration example sets up an ``aggregate-address`` under the ipv4 |
1145 | address-family. | |
5101fece | 1146 | |
1147 | .. code-block:: frr | |
1148 | ||
1149 | router bgp 1 | |
1150 | address-family ipv4 unicast | |
1151 | aggregate-address 10.0.0.0/8 | |
1152 | aggregate-address 20.0.0.0/8 as-set | |
1153 | aggregate-address 40.0.0.0/8 summary-only | |
ac2201bb | 1154 | aggregate-address 50.0.0.0/8 route-map aggr-rmap |
5101fece | 1155 | exit-address-family |
1156 | ||
1157 | ||
1158 | .. _bgp-route-aggregation-ipv6: | |
1159 | ||
1160 | Route Aggregation-IPv6 Address Family | |
1161 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
1162 | ||
5101fece | 1163 | .. clicmd:: aggregate-address X:X::X:X/M |
1164 | ||
1165 | This command specifies an aggregate address. | |
1166 | ||
ac2201bb DA |
1167 | .. clicmd:: aggregate-address X:X::X:X/M route-map NAME |
1168 | ||
1169 | Apply a route-map for an aggregated prefix. | |
1170 | ||
a87d2ef7 DA |
1171 | .. clicmd:: aggregate-address X:X::X:X/M origin <egp|igp|incomplete> |
1172 | ||
1173 | Override ORIGIN for an aggregated prefix. | |
1174 | ||
5101fece | 1175 | .. clicmd:: aggregate-address X:X::X:X/M as-set |
1176 | ||
1177 | This command specifies an aggregate address. Resulting routes include | |
1178 | AS set. | |
1179 | ||
5101fece | 1180 | .. clicmd:: aggregate-address X:X::X:X/M summary-only |
1181 | ||
1182 | This command specifies an aggregate address. Aggregated routes will | |
b91bf5bd | 1183 | not be announced. |
5101fece | 1184 | |
01338ba1 RZ |
1185 | .. clicmd:: aggregate-address X:X::X:X/M matching-MED-only |
1186 | ||
1187 | Configure the aggregated address to only be created when the routes MED | |
1188 | match, otherwise no aggregated route will be created. | |
1189 | ||
8fbb9c95 RZ |
1190 | .. clicmd:: aggregate-address X:X::X:X/M suppress-map NAME |
1191 | ||
1192 | Similar to `summary-only`, but will only suppress more specific routes that | |
1193 | are matched by the selected route-map. | |
01338ba1 | 1194 | |
5101fece | 1195 | |
03750f1e QY |
1196 | This configuration example sets up an ``aggregate-address`` under the ipv6 |
1197 | address-family. | |
5101fece | 1198 | |
1199 | .. code-block:: frr | |
1200 | ||
1201 | router bgp 1 | |
1202 | address-family ipv6 unicast | |
1203 | aggregate-address 10::0/64 | |
ac2201bb DA |
1204 | aggregate-address 20::0/64 as-set |
1205 | aggregate-address 40::0/64 summary-only | |
1206 | aggregate-address 50::0/64 route-map aggr-rmap | |
5101fece | 1207 | exit-address-family |
c3c5a71f | 1208 | |
03750f1e | 1209 | |
8fcedbd2 | 1210 | .. _bgp-redistribute-to-bgp: |
42fc5d26 | 1211 | |
8fcedbd2 QY |
1212 | Redistribution |
1213 | -------------- | |
42fc5d26 | 1214 | |
a874b986 QY |
1215 | Redistribution configuration should be placed under the ``address-family`` |
1216 | section for the specific AF to redistribute into. Protocol availability for | |
1217 | redistribution is determined by BGP AF; for example, you cannot redistribute | |
1218 | OSPFv3 into ``address-family ipv4 unicast`` as OSPFv3 supports IPv6. | |
1219 | ||
1220 | .. clicmd:: redistribute <babel|connected|eigrp|isis|kernel|openfabric|ospf|ospf6|rip|ripng|sharp|static|table> [metric (0-4294967295)] [route-map WORD] | |
1221 | ||
03750f1e | 1222 | Redistribute routes from other protocols into BGP. |
42fc5d26 | 1223 | |
245d354f DA |
1224 | .. clicmd:: redistribute vnc-direct |
1225 | ||
1226 | Redistribute VNC direct (not via zebra) routes to BGP process. | |
1227 | ||
d70583f7 D |
1228 | .. clicmd:: bgp update-delay MAX-DELAY |
1229 | ||
d70583f7 D |
1230 | .. clicmd:: bgp update-delay MAX-DELAY ESTABLISH-WAIT |
1231 | ||
1232 | This feature is used to enable read-only mode on BGP process restart or when | |
1233 | a BGP process is cleared using 'clear ip bgp \*'. Note that this command is | |
1234 | configured at the global level and applies to all bgp instances/vrfs. It | |
1235 | cannot be used at the same time as the "update-delay" command described below, | |
1236 | which is entered in each bgp instance/vrf desired to delay update installation | |
1237 | and advertisements. The global and per-vrf approaches to defining update-delay | |
1238 | are mutually exclusive. | |
1239 | ||
1240 | When applicable, read-only mode would begin as soon as the first peer reaches | |
1241 | Established status and a timer for max-delay seconds is started. During this | |
1242 | mode BGP doesn't run any best-path or generate any updates to its peers. This | |
1243 | mode continues until: | |
1244 | ||
1245 | 1. All the configured peers, except the shutdown peers, have sent explicit EOR | |
1246 | (End-Of-RIB) or an implicit-EOR. The first keep-alive after BGP has reached | |
1247 | Established is considered an implicit-EOR. | |
1248 | If the establish-wait optional value is given, then BGP will wait for | |
1249 | peers to reach established from the beginning of the update-delay till the | |
1250 | establish-wait period is over, i.e. the minimum set of established peers for | |
1251 | which EOR is expected would be peers established during the establish-wait | |
1252 | window, not necessarily all the configured neighbors. | |
1253 | 2. max-delay period is over. | |
1254 | ||
1255 | On hitting any of the above two conditions, BGP resumes the decision process | |
1256 | and generates updates to its peers. | |
1257 | ||
1258 | Default max-delay is 0, i.e. the feature is off by default. | |
1259 | ||
1260 | ||
c1a54c05 | 1261 | .. clicmd:: update-delay MAX-DELAY |
c3c5a71f | 1262 | |
c1a54c05 | 1263 | .. clicmd:: update-delay MAX-DELAY ESTABLISH-WAIT |
c3c5a71f | 1264 | |
c1a54c05 | 1265 | This feature is used to enable read-only mode on BGP process restart or when |
d70583f7 D |
1266 | a BGP process is cleared using 'clear ip bgp \*'. Note that this command is |
1267 | configured under the specific bgp instance/vrf that the feaure is enabled for. | |
1268 | It cannot be used at the same time as the global "bgp update-delay" described | |
1269 | above, which is entered at the global level and applies to all bgp instances. | |
1270 | The global and per-vrf approaches to defining update-delay are mutually | |
1271 | exclusive. | |
1272 | ||
1273 | When applicable, read-only mode would begin as soon as the first peer reaches | |
1274 | Established status and a timer for max-delay seconds is started. During this | |
1275 | mode BGP doesn't run any best-path or generate any updates to its peers. This | |
1276 | mode continues until: | |
42fc5d26 | 1277 | |
c1a54c05 QY |
1278 | 1. All the configured peers, except the shutdown peers, have sent explicit EOR |
1279 | (End-Of-RIB) or an implicit-EOR. The first keep-alive after BGP has reached | |
1280 | Established is considered an implicit-EOR. | |
1281 | If the establish-wait optional value is given, then BGP will wait for | |
d1e7591e | 1282 | peers to reach established from the beginning of the update-delay till the |
c1a54c05 QY |
1283 | establish-wait period is over, i.e. the minimum set of established peers for |
1284 | which EOR is expected would be peers established during the establish-wait | |
1285 | window, not necessarily all the configured neighbors. | |
1286 | 2. max-delay period is over. | |
42fc5d26 | 1287 | |
c1a54c05 QY |
1288 | On hitting any of the above two conditions, BGP resumes the decision process |
1289 | and generates updates to its peers. | |
42fc5d26 | 1290 | |
c1a54c05 | 1291 | Default max-delay is 0, i.e. the feature is off by default. |
c3c5a71f | 1292 | |
c1a54c05 | 1293 | .. clicmd:: table-map ROUTE-MAP-NAME |
42fc5d26 | 1294 | |
c1a54c05 QY |
1295 | This feature is used to apply a route-map on route updates from BGP to |
1296 | Zebra. All the applicable match operations are allowed, such as match on | |
1297 | prefix, next-hop, communities, etc. Set operations for this attach-point are | |
1298 | limited to metric and next-hop only. Any operation of this feature does not | |
1299 | affect BGPs internal RIB. | |
42fc5d26 | 1300 | |
c1a54c05 QY |
1301 | Supported for ipv4 and ipv6 address families. It works on multi-paths as |
1302 | well, however, metric setting is based on the best-path only. | |
42fc5d26 | 1303 | |
8fcedbd2 | 1304 | .. _bgp-peers: |
42fc5d26 | 1305 | |
8fcedbd2 QY |
1306 | Peers |
1307 | ----- | |
42fc5d26 | 1308 | |
8fcedbd2 | 1309 | .. _bgp-defining-peers: |
42fc5d26 | 1310 | |
8fcedbd2 QY |
1311 | Defining Peers |
1312 | ^^^^^^^^^^^^^^ | |
42fc5d26 | 1313 | |
c1a54c05 | 1314 | .. clicmd:: neighbor PEER remote-as ASN |
42fc5d26 | 1315 | |
c1a54c05 | 1316 | Creates a new neighbor whose remote-as is ASN. PEER can be an IPv4 address |
9eb95b3b | 1317 | or an IPv6 address or an interface to use for the connection. |
76bd1499 | 1318 | |
9eb95b3b QY |
1319 | .. code-block:: frr |
1320 | ||
1321 | router bgp 1 | |
1322 | neighbor 10.0.0.1 remote-as 2 | |
76bd1499 | 1323 | |
c1a54c05 | 1324 | In this case my router, in AS-1, is trying to peer with AS-2 at 10.0.0.1. |
76bd1499 | 1325 | |
c1a54c05 | 1326 | This command must be the first command used when configuring a neighbor. If |
9eb95b3b | 1327 | the remote-as is not specified, *bgpd* will complain like this: :: |
76bd1499 | 1328 | |
c1a54c05 | 1329 | can't find neighbor 10.0.0.1 |
c3c5a71f | 1330 | |
5413757f DS |
1331 | .. clicmd:: neighbor PEER remote-as internal |
1332 | ||
1333 | Create a peer as you would when you specify an ASN, except that if the | |
1334 | peers ASN is different than mine as specified under the :clicmd:`router bgp ASN` | |
1335 | command the connection will be denied. | |
1336 | ||
5413757f DS |
1337 | .. clicmd:: neighbor PEER remote-as external |
1338 | ||
1339 | Create a peer as you would when you specify an ASN, except that if the | |
1340 | peers ASN is the same as mine as specified under the :clicmd:`router bgp ASN` | |
1341 | command the connection will be denied. | |
42fc5d26 | 1342 | |
03750f1e | 1343 | .. clicmd:: bgp listen range <A.B.C.D/M|X:X::X:X/M> peer-group PGNAME |
d79e0e08 QY |
1344 | |
1345 | Accept connections from any peers in the specified prefix. Configuration | |
1346 | from the specified peer-group is used to configure these peers. | |
1347 | ||
1348 | .. note:: | |
1349 | ||
1350 | When using BGP listen ranges, if the associated peer group has TCP MD5 | |
1351 | authentication configured, your kernel must support this on prefixes. On | |
1352 | Linux, this support was added in kernel version 4.14. If your kernel does | |
1353 | not support this feature you will get a warning in the log file, and the | |
1354 | listen range will only accept connections from peers without MD5 configured. | |
1355 | ||
1356 | Additionally, we have observed that when using this option at scale (several | |
1357 | hundred peers) the kernel may hit its option memory limit. In this situation | |
1358 | you will see error messages like: | |
1359 | ||
1360 | ``bgpd: sockopt_tcp_signature: setsockopt(23): Cannot allocate memory`` | |
1361 | ||
1362 | In this case you need to increase the value of the sysctl | |
1363 | ``net.core.optmem_max`` to allow the kernel to allocate the necessary option | |
1364 | memory. | |
1365 | ||
5b1b6b8b PG |
1366 | .. clicmd:: bgp listen limit <1-65535> |
1367 | ||
1368 | Define the maximum number of peers accepted for one BGP instance. This | |
1369 | limit is set to 100 by default. Increasing this value will really be | |
1370 | possible if more file descriptors are available in the BGP process. This | |
1371 | value is defined by the underlying system (ulimit value), and can be | |
1372 | overriden by `--limit-fds`. More information is available in chapter | |
1373 | (:ref:`common-invocation-options`). | |
1374 | ||
03750f1e | 1375 | .. clicmd:: coalesce-time (0-4294967295) |
ced26d3d DS |
1376 | |
1377 | The time in milliseconds that BGP will delay before deciding what peers | |
1378 | can be put into an update-group together in order to generate a single | |
1379 | update for them. The default time is 1000. | |
91052810 | 1380 | |
8fcedbd2 | 1381 | .. _bgp-configuring-peers: |
42fc5d26 | 1382 | |
8fcedbd2 QY |
1383 | Configuring Peers |
1384 | ^^^^^^^^^^^^^^^^^ | |
42fc5d26 | 1385 | |
03750f1e | 1386 | .. clicmd:: neighbor PEER shutdown [message MSG...] [rtt (1-65535) [count (1-255)]] |
c3c5a71f | 1387 | |
c1a54c05 QY |
1388 | Shutdown the peer. We can delete the neighbor's configuration by |
1389 | ``no neighbor PEER remote-as ASN`` but all configuration of the neighbor | |
1390 | will be deleted. When you want to preserve the configuration, but want to | |
1391 | drop the BGP peer, use this syntax. | |
c3c5a71f | 1392 | |
70335e0a RZ |
1393 | Optionally you can specify a shutdown message `MSG`. |
1394 | ||
56c07345 | 1395 | Also, you can specify optionally ``rtt`` in milliseconds to automatically |
91052810 DA |
1396 | shutdown the peer if round-trip-time becomes higher than defined. |
1397 | ||
56c07345 | 1398 | Additional ``count`` parameter is the number of keepalive messages to count |
91052810 DA |
1399 | before shutdown the peer if round-trip-time becomes higher than defined. |
1400 | ||
03750f1e | 1401 | .. clicmd:: neighbor PEER disable-connected-check |
c3c5a71f | 1402 | |
c0868e8b QY |
1403 | Allow peerings between directly connected eBGP peers using loopback |
1404 | addresses. | |
c3c5a71f | 1405 | |
03750f1e | 1406 | .. clicmd:: neighbor PEER ebgp-multihop |
42fc5d26 | 1407 | |
164786a9 QY |
1408 | Specifying ``ebgp-multihop`` allows sessions with eBGP neighbors to |
1409 | establish when they are multiple hops away. When the neighbor is not | |
1410 | directly connected and this knob is not enabled, the session will not | |
1411 | establish. | |
1412 | ||
15e6881e DA |
1413 | If the peer's IP address is not in the RIB and is reachable via the |
1414 | default route, then you have to enable ``ip nht resolve-via-default``. | |
1415 | ||
03750f1e | 1416 | .. clicmd:: neighbor PEER description ... |
42fc5d26 | 1417 | |
c1a54c05 | 1418 | Set description of the peer. |
42fc5d26 | 1419 | |
03750f1e | 1420 | .. clicmd:: neighbor PEER version VERSION |
42fc5d26 | 1421 | |
4da7fda3 QY |
1422 | Set up the neighbor's BGP version. `version` can be `4`, `4+` or `4-`. BGP |
1423 | version `4` is the default value used for BGP peering. BGP version `4+` | |
1424 | means that the neighbor supports Multiprotocol Extensions for BGP-4. BGP | |
1425 | version `4-` is similar but the neighbor speaks the old Internet-Draft | |
1426 | revision 00's Multiprotocol Extensions for BGP-4. Some routing software is | |
1427 | still using this version. | |
42fc5d26 | 1428 | |
03750f1e | 1429 | .. clicmd:: neighbor PEER interface IFNAME |
42fc5d26 | 1430 | |
c1a54c05 QY |
1431 | When you connect to a BGP peer over an IPv6 link-local address, you have to |
1432 | specify the IFNAME of the interface used for the connection. To specify | |
1433 | IPv4 session addresses, see the ``neighbor PEER update-source`` command | |
1434 | below. | |
42fc5d26 | 1435 | |
c1a54c05 QY |
1436 | This command is deprecated and may be removed in a future release. Its use |
1437 | should be avoided. | |
42fc5d26 | 1438 | |
da4d6777 QY |
1439 | .. clicmd:: neighbor PEER interface remote-as <internal|external|ASN> |
1440 | ||
1441 | Configure an unnumbered BGP peer. ``PEER`` should be an interface name. The | |
1442 | session will be established via IPv6 link locals. Use ``internal`` for iBGP | |
1443 | and ``external`` for eBGP sessions, or specify an ASN if you wish. | |
1444 | ||
03750f1e | 1445 | .. clicmd:: neighbor PEER next-hop-self [all] |
42fc5d26 | 1446 | |
c1a54c05 QY |
1447 | This command specifies an announced route's nexthop as being equivalent to |
1448 | the address of the bgp router if it is learned via eBGP. If the optional | |
d1e7591e | 1449 | keyword `all` is specified the modification is done also for routes learned |
c1a54c05 | 1450 | via iBGP. |
42fc5d26 | 1451 | |
8b0d734b | 1452 | .. clicmd:: neighbor PEER attribute-unchanged [{as-path|next-hop|med}] |
1453 | ||
1454 | This command specifies attributes to be left unchanged for advertisements | |
1455 | sent to a peer. Use this to leave the next-hop unchanged in ipv6 | |
1456 | configurations, as the route-map directive to leave the next-hop unchanged | |
1457 | is only available for ipv4. | |
1458 | ||
03750f1e | 1459 | .. clicmd:: neighbor PEER update-source <IFNAME|ADDRESS> |
42fc5d26 | 1460 | |
c1a54c05 QY |
1461 | Specify the IPv4 source address to use for the :abbr:`BGP` session to this |
1462 | neighbour, may be specified as either an IPv4 address directly or as an | |
1463 | interface name (in which case the *zebra* daemon MUST be running in order | |
9eb95b3b QY |
1464 | for *bgpd* to be able to retrieve interface state). |
1465 | ||
1466 | .. code-block:: frr | |
42fc5d26 | 1467 | |
c1a54c05 QY |
1468 | router bgp 64555 |
1469 | neighbor foo update-source 192.168.0.1 | |
1470 | neighbor bar update-source lo0 | |
42fc5d26 | 1471 | |
42fc5d26 | 1472 | |
03750f1e | 1473 | .. clicmd:: neighbor PEER default-originate |
42fc5d26 | 1474 | |
4da7fda3 QY |
1475 | *bgpd*'s default is to not announce the default route (0.0.0.0/0) even if it |
1476 | is in routing table. When you want to announce default routes to the peer, | |
1477 | use this command. | |
42fc5d26 | 1478 | |
c1a54c05 | 1479 | .. clicmd:: neighbor PEER port PORT |
42fc5d26 | 1480 | |
03750f1e | 1481 | .. clicmd:: neighbor PEER password PASSWORD |
e7c105a7 DS |
1482 | |
1483 | Set a MD5 password to be used with the tcp socket that is being used | |
1484 | to connect to the remote peer. Please note if you are using this | |
1485 | command with a large number of peers on linux you should consider | |
1486 | modifying the `net.core.optmem_max` sysctl to a larger value to | |
1487 | avoid out of memory errors from the linux kernel. | |
1488 | ||
c1a54c05 | 1489 | .. clicmd:: neighbor PEER send-community |
42fc5d26 | 1490 | |
03750f1e | 1491 | .. clicmd:: neighbor PEER weight WEIGHT |
42fc5d26 | 1492 | |
c1a54c05 | 1493 | This command specifies a default `weight` value for the neighbor's routes. |
42fc5d26 | 1494 | |
03750f1e | 1495 | .. clicmd:: neighbor PEER maximum-prefix NUMBER [force] |
42fc5d26 | 1496 | |
886026c8 QY |
1497 | Sets a maximum number of prefixes we can receive from a given peer. If this |
1498 | number is exceeded, the BGP session will be destroyed. | |
1499 | ||
1500 | In practice, it is generally preferable to use a prefix-list to limit what | |
1501 | prefixes are received from the peer instead of using this knob. Tearing down | |
1502 | the BGP session when a limit is exceeded is far more destructive than merely | |
1503 | rejecting undesired prefixes. The prefix-list method is also much more | |
1504 | granular and offers much smarter matching criterion than number of received | |
1505 | prefixes, making it more suited to implementing policy. | |
1506 | ||
56c07345 | 1507 | If ``force`` is set, then ALL prefixes are counted for maximum instead of |
c1bcac1d DA |
1508 | accepted only. This is useful for cases where an inbound filter is applied, |
1509 | but you want maximum-prefix to act on ALL (including filtered) prefixes. This | |
1510 | option requires `soft-reconfiguration inbound` to be enabled for the peer. | |
1511 | ||
03750f1e | 1512 | .. clicmd:: neighbor PEER maximum-prefix-out NUMBER |
edf98aa3 DA |
1513 | |
1514 | Sets a maximum number of prefixes we can send to a given peer. | |
1515 | ||
f5399474 DA |
1516 | Since sent prefix count is managed by update-groups, this option |
1517 | creates a separate update-group for outgoing updates. | |
1518 | ||
03750f1e | 1519 | .. clicmd:: neighbor PEER local-as AS-NUMBER [no-prepend] [replace-as] |
42fc5d26 | 1520 | |
c1a54c05 QY |
1521 | Specify an alternate AS for this BGP process when interacting with the |
1522 | specified peer. With no modifiers, the specified local-as is prepended to | |
1523 | the received AS_PATH when receiving routing updates from the peer, and | |
1524 | prepended to the outgoing AS_PATH (after the process local AS) when | |
1525 | transmitting local routes to the peer. | |
42fc5d26 | 1526 | |
c1a54c05 QY |
1527 | If the no-prepend attribute is specified, then the supplied local-as is not |
1528 | prepended to the received AS_PATH. | |
c3c5a71f | 1529 | |
c1a54c05 QY |
1530 | If the replace-as attribute is specified, then only the supplied local-as is |
1531 | prepended to the AS_PATH when transmitting local-route updates to this peer. | |
c3c5a71f | 1532 | |
c1a54c05 | 1533 | Note that replace-as can only be specified if no-prepend is. |
c3c5a71f | 1534 | |
c1a54c05 | 1535 | This command is only allowed for eBGP peers. |
c3c5a71f | 1536 | |
03750f1e | 1537 | .. clicmd:: neighbor <A.B.C.D|X:X::X:X|WORD> as-override |
252c5590 RZ |
1538 | |
1539 | Override AS number of the originating router with the local AS number. | |
1540 | ||
1541 | Usually this configuration is used in PEs (Provider Edge) to replace | |
1542 | the incoming customer AS number so the connected CE (Customer Edge) | |
1543 | can use the same AS number as the other customer sites. This allows | |
1544 | customers of the provider network to use the same AS number across | |
1545 | their sites. | |
1546 | ||
1547 | This command is only allowed for eBGP peers. | |
1548 | ||
03750f1e | 1549 | .. clicmd:: neighbor <A.B.C.D|X:X::X:X|WORD> allowas-in [<(1-10)|origin>] |
ae1e0f32 RZ |
1550 | |
1551 | Accept incoming routes with AS path containing AS number with the same value | |
1552 | as the current system AS. | |
1553 | ||
1554 | This is used when you want to use the same AS number in your sites, but you | |
1555 | can't connect them directly. This is an alternative to | |
1556 | `neighbor WORD as-override`. | |
1557 | ||
1558 | The parameter `(1-10)` configures the amount of accepted occurences of the | |
1559 | system AS number in AS path. | |
1560 | ||
1561 | The parameter `origin` configures BGP to only accept routes originated with | |
1562 | the same AS number as the system. | |
1563 | ||
1564 | This command is only allowed for eBGP peers. | |
1565 | ||
03750f1e | 1566 | .. clicmd:: neighbor <A.B.C.D|X:X::X:X|WORD> addpath-tx-all-paths |
e03bf6fc RZ |
1567 | |
1568 | Configure BGP to send all known paths to neighbor in order to preserve multi | |
1569 | path capabilities inside a network. | |
1570 | ||
03750f1e | 1571 | .. clicmd:: neighbor <A.B.C.D|X:X::X:X|WORD> addpath-tx-bestpath-per-AS |
e03bf6fc RZ |
1572 | |
1573 | Configure BGP to send best known paths to neighbor in order to preserve multi | |
1574 | path capabilities inside a network. | |
1575 | ||
03750f1e | 1576 | .. clicmd:: neighbor PEER ttl-security hops NUMBER |
c3c5a71f | 1577 | |
c1a54c05 QY |
1578 | This command enforces Generalized TTL Security Mechanism (GTSM), as |
1579 | specified in RFC 5082. With this command, only neighbors that are the | |
1580 | specified number of hops away will be allowed to become neighbors. This | |
d1e7591e | 1581 | command is mutually exclusive with *ebgp-multihop*. |
42fc5d26 | 1582 | |
03750f1e | 1583 | .. clicmd:: neighbor PEER capability extended-nexthop |
19f2b5e8 DS |
1584 | |
1585 | Allow bgp to negotiate the extended-nexthop capability with it's peer. | |
1586 | If you are peering over a v6 LL address then this capability is turned | |
1587 | on automatically. If you are peering over a v6 Global Address then | |
1588 | turning on this command will allow BGP to install v4 routes with | |
1589 | v6 nexthops if you do not have v4 configured on interfaces. | |
1590 | ||
03750f1e | 1591 | .. clicmd:: bgp fast-external-failover |
eb938189 DS |
1592 | |
1593 | This command causes bgp to not take down ebgp peers immediately | |
1594 | when a link flaps. `bgp fast-external-failover` is the default | |
1595 | and will not be displayed as part of a `show run`. The no form | |
1596 | of the command turns off this ability. | |
1597 | ||
03750f1e | 1598 | .. clicmd:: bgp default ipv4-unicast |
bc132029 DS |
1599 | |
1600 | This command allows the user to specify that v4 peering is turned | |
1601 | on by default or not. This command defaults to on and is not displayed. | |
1602 | The `no bgp default ipv4-unicast` form of the command is displayed. | |
1603 | ||
2c853e5e DA |
1604 | .. clicmd:: bgp default ipv6-unicast |
1605 | ||
1606 | This command allows the user to specify that v6 peering is turned | |
1607 | on by default or not. This command defaults to off and is not displayed. | |
1608 | The `bgp default ipv6-unicast` form of the command is displayed. | |
1609 | ||
03750f1e | 1610 | .. clicmd:: bgp default show-hostname |
7d981695 DA |
1611 | |
1612 | This command shows the hostname of the peer in certain BGP commands | |
1613 | outputs. It's easier to troubleshoot if you have a number of BGP peers. | |
1614 | ||
03750f1e | 1615 | .. clicmd:: bgp default show-nexthop-hostname |
7d981695 DA |
1616 | |
1617 | This command shows the hostname of the next-hop in certain BGP commands | |
1618 | outputs. It's easier to troubleshoot if you have a number of BGP peers | |
1619 | and a number of routes to check. | |
1620 | ||
03750f1e | 1621 | .. clicmd:: neighbor PEER advertisement-interval (0-600) |
e10dda57 DS |
1622 | |
1623 | Setup the minimum route advertisement interval(mrai) for the | |
1624 | peer in question. This number is between 0 and 600 seconds, | |
1625 | with the default advertisement interval being 0. | |
1626 | ||
0c969c0f QY |
1627 | .. clicmd:: neighbor PEER timers (0-65535) (0-65535) |
1628 | ||
1629 | Set keepalive and hold timers for a neighbor. The first value is keepalive | |
1630 | and the second is hold time. | |
1631 | ||
1632 | .. clicmd:: neighbor PEER connect (1-65535) | |
1633 | ||
1634 | Set connect timer for a neighbor. The connect timer controls how long BGP | |
1635 | waits between connection attempts to a neighbor. | |
1636 | ||
03750f1e | 1637 | .. clicmd:: neighbor PEER timers delayopen (1-240) |
94abf9b4 DS |
1638 | |
1639 | This command allows the user enable the | |
1640 | `RFC 4271 <https://tools.ietf.org/html/rfc4271/>` DelayOpenTimer with the | |
1641 | specified interval or disable it with the negating command for the peer. By | |
1642 | default, the DelayOpenTimer is disabled. The timer interval may be set to a | |
1643 | duration of 1 to 240 seconds. | |
1644 | ||
4e853678 DS |
1645 | Displaying Information about Peers |
1646 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
1647 | ||
4e853678 DS |
1648 | .. clicmd:: show bgp <afi> <safi> neighbors WORD bestpath-routes [json] [wide] |
1649 | ||
1650 | For the given neighbor, WORD, that is specified list the routes selected | |
1651 | by BGP as having the best path. | |
1652 | ||
8fcedbd2 | 1653 | .. _bgp-peer-filtering: |
42fc5d26 | 1654 | |
8fcedbd2 QY |
1655 | Peer Filtering |
1656 | ^^^^^^^^^^^^^^ | |
42fc5d26 | 1657 | |
c1a54c05 | 1658 | .. clicmd:: neighbor PEER distribute-list NAME [in|out] |
42fc5d26 | 1659 | |
c1a54c05 QY |
1660 | This command specifies a distribute-list for the peer. `direct` is |
1661 | ``in`` or ``out``. | |
42fc5d26 | 1662 | |
29adcd50 | 1663 | .. clicmd:: neighbor PEER prefix-list NAME [in|out] |
42fc5d26 | 1664 | |
29adcd50 | 1665 | .. clicmd:: neighbor PEER filter-list NAME [in|out] |
42fc5d26 | 1666 | |
c1a54c05 | 1667 | .. clicmd:: neighbor PEER route-map NAME [in|out] |
42fc5d26 | 1668 | |
c1a54c05 | 1669 | Apply a route-map on the neighbor. `direct` must be `in` or `out`. |
42fc5d26 | 1670 | |
29adcd50 | 1671 | .. clicmd:: bgp route-reflector allow-outbound-policy |
42fc5d26 | 1672 | |
c1a54c05 QY |
1673 | By default, attribute modification via route-map policy out is not reflected |
1674 | on reflected routes. This option allows the modifications to be reflected as | |
1675 | well. Once enabled, it affects all reflected routes. | |
42fc5d26 | 1676 | |
03750f1e | 1677 | .. clicmd:: neighbor PEER sender-as-path-loop-detection |
583a9fd4 RZ |
1678 | |
1679 | Enable the detection of sender side AS path loops and filter the | |
1680 | bad routes before they are sent. | |
1681 | ||
1682 | This setting is disabled by default. | |
1683 | ||
0efdf0fe | 1684 | .. _bgp-peer-group: |
42fc5d26 | 1685 | |
8fcedbd2 QY |
1686 | Peer Groups |
1687 | ^^^^^^^^^^^ | |
42fc5d26 | 1688 | |
199ad5c4 LB |
1689 | Peer groups are used to help improve scaling by generating the same |
1690 | update information to all members of a peer group. Note that this means | |
1691 | that the routes generated by a member of a peer group will be sent back | |
1692 | to that originating peer with the originator identifier attribute set to | |
1693 | indicated the originating peer. All peers not associated with a | |
1694 | specific peer group are treated as belonging to a default peer group, | |
1695 | and will share updates. | |
1696 | ||
c1a54c05 | 1697 | .. clicmd:: neighbor WORD peer-group |
42fc5d26 | 1698 | |
c1a54c05 | 1699 | This command defines a new peer group. |
42fc5d26 | 1700 | |
d7b9898c | 1701 | .. clicmd:: neighbor PEER peer-group PGNAME |
c3c5a71f | 1702 | |
c1a54c05 | 1703 | This command bind specific peer to peer group WORD. |
42fc5d26 | 1704 | |
199ad5c4 LB |
1705 | .. clicmd:: neighbor PEER solo |
1706 | ||
1707 | This command is used to indicate that routes advertised by the peer | |
1708 | should not be reflected back to the peer. This command only is only | |
1709 | meaningful when there is a single peer defined in the peer-group. | |
1710 | ||
65c0fc12 DA |
1711 | .. clicmd:: show [ip] bgp peer-group [json] |
1712 | ||
1713 | This command displays configured BGP peer-groups. | |
1714 | ||
1715 | .. code-block:: frr | |
1716 | ||
1717 | exit1-debian-9# show bgp peer-group | |
1718 | ||
1719 | BGP peer-group test1, remote AS 65001 | |
1720 | Peer-group type is external | |
1721 | Configured address-families: IPv4 Unicast; IPv6 Unicast; | |
1722 | 1 IPv4 listen range(s) | |
1723 | 192.168.100.0/24 | |
1724 | 2 IPv6 listen range(s) | |
1725 | 2001:db8:1::/64 | |
1726 | 2001:db8:2::/64 | |
1727 | Peer-group members: | |
1728 | 192.168.200.1 Active | |
1729 | 2001:db8::1 Active | |
1730 | ||
1731 | BGP peer-group test2 | |
1732 | Peer-group type is external | |
1733 | Configured address-families: IPv4 Unicast; | |
1734 | ||
1735 | Optional ``json`` parameter is used to display JSON output. | |
1736 | ||
1737 | .. code-block:: frr | |
1738 | ||
1739 | { | |
1740 | "test1":{ | |
1741 | "remoteAs":65001, | |
1742 | "type":"external", | |
1743 | "addressFamiliesConfigured":[ | |
1744 | "IPv4 Unicast", | |
1745 | "IPv6 Unicast" | |
1746 | ], | |
1747 | "dynamicRanges":{ | |
1748 | "IPv4":{ | |
1749 | "count":1, | |
1750 | "ranges":[ | |
1751 | "192.168.100.0\/24" | |
1752 | ] | |
1753 | }, | |
1754 | "IPv6":{ | |
1755 | "count":2, | |
1756 | "ranges":[ | |
1757 | "2001:db8:1::\/64", | |
1758 | "2001:db8:2::\/64" | |
1759 | ] | |
1760 | } | |
1761 | }, | |
1762 | "members":{ | |
1763 | "192.168.200.1":{ | |
1764 | "status":"Active" | |
1765 | }, | |
1766 | "2001:db8::1":{ | |
1767 | "status":"Active" | |
1768 | } | |
1769 | } | |
1770 | }, | |
1771 | "test2":{ | |
1772 | "type":"external", | |
1773 | "addressFamiliesConfigured":[ | |
1774 | "IPv4 Unicast" | |
1775 | ] | |
1776 | } | |
1777 | } | |
1778 | ||
8fcedbd2 QY |
1779 | Capability Negotiation |
1780 | ^^^^^^^^^^^^^^^^^^^^^^ | |
42fc5d26 | 1781 | |
8fcedbd2 | 1782 | .. clicmd:: neighbor PEER strict-capability-match |
42fc5d26 | 1783 | |
c1a54c05 | 1784 | |
8fcedbd2 QY |
1785 | Strictly compares remote capabilities and local capabilities. If |
1786 | capabilities are different, send Unsupported Capability error then reset | |
1787 | connection. | |
42fc5d26 | 1788 | |
8fcedbd2 QY |
1789 | You may want to disable sending Capability Negotiation OPEN message optional |
1790 | parameter to the peer when remote peer does not implement Capability | |
1791 | Negotiation. Please use *dont-capability-negotiate* command to disable the | |
1792 | feature. | |
42fc5d26 | 1793 | |
03750f1e | 1794 | .. clicmd:: neighbor PEER dont-capability-negotiate |
42fc5d26 | 1795 | |
8fcedbd2 QY |
1796 | Suppress sending Capability Negotiation as OPEN message optional parameter |
1797 | to the peer. This command only affects the peer is configured other than | |
1798 | IPv4 unicast configuration. | |
42fc5d26 | 1799 | |
8fcedbd2 QY |
1800 | When remote peer does not have capability negotiation feature, remote peer |
1801 | will not send any capabilities at all. In that case, bgp configures the peer | |
1802 | with configured capabilities. | |
42fc5d26 | 1803 | |
8fcedbd2 QY |
1804 | You may prefer locally configured capabilities more than the negotiated |
1805 | capabilities even though remote peer sends capabilities. If the peer is | |
1806 | configured by *override-capability*, *bgpd* ignores received capabilities | |
1807 | then override negotiated capabilities with configured values. | |
42fc5d26 | 1808 | |
7cdc9530 DS |
1809 | Additionally the operator should be reminded that this feature fundamentally |
1810 | disables the ability to use widely deployed BGP features. BGP unnumbered, | |
1811 | hostname support, AS4, Addpath, Route Refresh, ORF, Dynamic Capabilities, | |
1812 | and graceful restart. | |
1813 | ||
8fcedbd2 | 1814 | .. clicmd:: neighbor PEER override-capability |
42fc5d26 | 1815 | |
c1a54c05 | 1816 | |
8fcedbd2 QY |
1817 | Override the result of Capability Negotiation with local configuration. |
1818 | Ignore remote peer's capability value. | |
42fc5d26 | 1819 | |
8fcedbd2 | 1820 | .. _bgp-as-path-access-lists: |
42fc5d26 | 1821 | |
8fcedbd2 QY |
1822 | AS Path Access Lists |
1823 | -------------------- | |
42fc5d26 QY |
1824 | |
1825 | AS path access list is user defined AS path. | |
1826 | ||
e6e62ee5 | 1827 | .. clicmd:: bgp as-path access-list WORD [seq (0-4294967295)] permit|deny LINE |
42fc5d26 | 1828 | |
c1a54c05 | 1829 | This command defines a new AS path access list. |
42fc5d26 | 1830 | |
42fc5d26 | 1831 | |
42fc5d26 | 1832 | |
125cec1a DA |
1833 | .. _bgp-bogon-filter-example: |
1834 | ||
1835 | Bogon ASN filter policy configuration example | |
1836 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
1837 | ||
1838 | .. code-block:: frr | |
1839 | ||
1840 | bgp as-path access-list 99 permit _0_ | |
1841 | bgp as-path access-list 99 permit _23456_ | |
1842 | bgp as-path access-list 99 permit _1310[0-6][0-9]_|_13107[0-1]_ | |
e6e62ee5 | 1843 | bgp as-path access-list 99 seq 20 permit ^65 |
125cec1a | 1844 | |
8fcedbd2 | 1845 | .. _bgp-using-as-path-in-route-map: |
42fc5d26 QY |
1846 | |
1847 | Using AS Path in Route Map | |
1848 | -------------------------- | |
1849 | ||
03750f1e | 1850 | .. clicmd:: match as-path WORD |
42fc5d26 | 1851 | |
eb1f303d DS |
1852 | For a given as-path, WORD, match it on the BGP as-path given for the prefix |
1853 | and if it matches do normal route-map actions. The no form of the command | |
1854 | removes this match from the route-map. | |
42fc5d26 | 1855 | |
03750f1e | 1856 | .. clicmd:: set as-path prepend AS-PATH |
42fc5d26 | 1857 | |
eb1f303d DS |
1858 | Prepend the given string of AS numbers to the AS_PATH of the BGP path's NLRI. |
1859 | The no form of this command removes this set operation from the route-map. | |
42fc5d26 | 1860 | |
03750f1e | 1861 | .. clicmd:: set as-path prepend last-as NUM |
c1a54c05 QY |
1862 | |
1863 | Prepend the existing last AS number (the leftmost ASN) to the AS_PATH. | |
eb1f303d | 1864 | The no form of this command removes this set operation from the route-map. |
42fc5d26 | 1865 | |
0efdf0fe | 1866 | .. _bgp-communities-attribute: |
42fc5d26 | 1867 | |
8fcedbd2 QY |
1868 | Communities Attribute |
1869 | --------------------- | |
42fc5d26 | 1870 | |
8fcedbd2 | 1871 | The BGP communities attribute is widely used for implementing policy routing. |
c1a54c05 QY |
1872 | Network operators can manipulate BGP communities attribute based on their |
1873 | network policy. BGP communities attribute is defined in :rfc:`1997` and | |
1874 | :rfc:`1998`. It is an optional transitive attribute, therefore local policy can | |
1875 | travel through different autonomous system. | |
1876 | ||
8fcedbd2 QY |
1877 | The communities attribute is a set of communities values. Each community value |
1878 | is 4 octet long. The following format is used to define the community value. | |
c1a54c05 | 1879 | |
8fcedbd2 | 1880 | ``AS:VAL`` |
c1a54c05 QY |
1881 | This format represents 4 octet communities value. ``AS`` is high order 2 |
1882 | octet in digit format. ``VAL`` is low order 2 octet in digit format. This | |
1883 | format is useful to define AS oriented policy value. For example, | |
1884 | ``7675:80`` can be used when AS 7675 wants to pass local policy value 80 to | |
1885 | neighboring peer. | |
1886 | ||
8fcedbd2 QY |
1887 | ``internet`` |
1888 | ``internet`` represents well-known communities value 0. | |
c1a54c05 | 1889 | |
cae770d3 C |
1890 | ``graceful-shutdown`` |
1891 | ``graceful-shutdown`` represents well-known communities value | |
1892 | ``GRACEFUL_SHUTDOWN`` ``0xFFFF0000`` ``65535:0``. :rfc:`8326` implements | |
1893 | the purpose Graceful BGP Session Shutdown to reduce the amount of | |
56f0bea7 | 1894 | lost traffic when taking BGP sessions down for maintenance. The use |
cae770d3 C |
1895 | of the community needs to be supported from your peers side to |
1896 | actually have any effect. | |
1897 | ||
1898 | ``accept-own`` | |
1899 | ``accept-own`` represents well-known communities value ``ACCEPT_OWN`` | |
1900 | ``0xFFFF0001`` ``65535:1``. :rfc:`7611` implements a way to signal | |
1901 | to a router to accept routes with a local nexthop address. This | |
1902 | can be the case when doing policing and having traffic having a | |
1903 | nexthop located in another VRF but still local interface to the | |
1904 | router. It is recommended to read the RFC for full details. | |
1905 | ||
1906 | ``route-filter-translated-v4`` | |
1907 | ``route-filter-translated-v4`` represents well-known communities value | |
1908 | ``ROUTE_FILTER_TRANSLATED_v4`` ``0xFFFF0002`` ``65535:2``. | |
1909 | ||
1910 | ``route-filter-v4`` | |
1911 | ``route-filter-v4`` represents well-known communities value | |
1912 | ``ROUTE_FILTER_v4`` ``0xFFFF0003`` ``65535:3``. | |
1913 | ||
1914 | ``route-filter-translated-v6`` | |
1915 | ``route-filter-translated-v6`` represents well-known communities value | |
1916 | ``ROUTE_FILTER_TRANSLATED_v6`` ``0xFFFF0004`` ``65535:4``. | |
1917 | ||
1918 | ``route-filter-v6`` | |
1919 | ``route-filter-v6`` represents well-known communities value | |
1920 | ``ROUTE_FILTER_v6`` ``0xFFFF0005`` ``65535:5``. | |
1921 | ||
1922 | ``llgr-stale`` | |
1923 | ``llgr-stale`` represents well-known communities value ``LLGR_STALE`` | |
1924 | ``0xFFFF0006`` ``65535:6``. | |
56f0bea7 | 1925 | Assigned and intended only for use with routers supporting the |
cae770d3 | 1926 | Long-lived Graceful Restart Capability as described in |
49606d58 | 1927 | [Draft-IETF-uttaro-idr-bgp-persistence]_. |
56f0bea7 | 1928 | Routers receiving routes with this community may (depending on |
cae770d3 C |
1929 | implementation) choose allow to reject or modify routes on the |
1930 | presence or absence of this community. | |
1931 | ||
1932 | ``no-llgr`` | |
1933 | ``no-llgr`` represents well-known communities value ``NO_LLGR`` | |
1934 | ``0xFFFF0007`` ``65535:7``. | |
56f0bea7 | 1935 | Assigned and intended only for use with routers supporting the |
cae770d3 | 1936 | Long-lived Graceful Restart Capability as described in |
49606d58 | 1937 | [Draft-IETF-uttaro-idr-bgp-persistence]_. |
56f0bea7 | 1938 | Routers receiving routes with this community may (depending on |
cae770d3 C |
1939 | implementation) choose allow to reject or modify routes on the |
1940 | presence or absence of this community. | |
1941 | ||
1942 | ``accept-own-nexthop`` | |
1943 | ``accept-own-nexthop`` represents well-known communities value | |
1944 | ``accept-own-nexthop`` ``0xFFFF0008`` ``65535:8``. | |
49606d58 | 1945 | [Draft-IETF-agrewal-idr-accept-own-nexthop]_ describes |
cae770d3 C |
1946 | how to tag and label VPN routes to be able to send traffic between VRFs |
1947 | via an internal layer 2 domain on the same PE device. Refer to | |
49606d58 | 1948 | [Draft-IETF-agrewal-idr-accept-own-nexthop]_ for full details. |
cae770d3 C |
1949 | |
1950 | ``blackhole`` | |
1951 | ``blackhole`` represents well-known communities value ``BLACKHOLE`` | |
1952 | ``0xFFFF029A`` ``65535:666``. :rfc:`7999` documents sending prefixes to | |
1953 | EBGP peers and upstream for the purpose of blackholing traffic. | |
1954 | Prefixes tagged with the this community should normally not be | |
10ae708b DA |
1955 | re-advertised from neighbors of the originating network. Upon receiving |
1956 | ``BLACKHOLE`` community from a BGP speaker, ``NO_ADVERTISE`` community | |
1957 | is added automatically. | |
cae770d3 | 1958 | |
8fcedbd2 | 1959 | ``no-export`` |
c1a54c05 QY |
1960 | ``no-export`` represents well-known communities value ``NO_EXPORT`` |
1961 | ``0xFFFFFF01``. All routes carry this value must not be advertised to | |
1962 | outside a BGP confederation boundary. If neighboring BGP peer is part of BGP | |
1963 | confederation, the peer is considered as inside a BGP confederation | |
1964 | boundary, so the route will be announced to the peer. | |
1965 | ||
8fcedbd2 | 1966 | ``no-advertise`` |
c1a54c05 QY |
1967 | ``no-advertise`` represents well-known communities value ``NO_ADVERTISE`` |
1968 | ``0xFFFFFF02``. All routes carry this value must not be advertise to other | |
1969 | BGP peers. | |
1970 | ||
8fcedbd2 | 1971 | ``local-AS`` |
c1a54c05 QY |
1972 | ``local-AS`` represents well-known communities value ``NO_EXPORT_SUBCONFED`` |
1973 | ``0xFFFFFF03``. All routes carry this value must not be advertised to | |
1974 | external BGP peers. Even if the neighboring router is part of confederation, | |
1975 | it is considered as external BGP peer, so the route will not be announced to | |
1976 | the peer. | |
1977 | ||
cae770d3 C |
1978 | ``no-peer`` |
1979 | ``no-peer`` represents well-known communities value ``NOPEER`` | |
1980 | ``0xFFFFFF04`` ``65535:65284``. :rfc:`3765` is used to communicate to | |
1981 | another network how the originating network want the prefix propagated. | |
1982 | ||
aa9eafa4 QY |
1983 | When the communities attribute is received duplicate community values in the |
1984 | attribute are ignored and value is sorted in numerical order. | |
42fc5d26 | 1985 | |
49606d58 PG |
1986 | .. [Draft-IETF-uttaro-idr-bgp-persistence] <https://tools.ietf.org/id/draft-uttaro-idr-bgp-persistence-04.txt> |
1987 | .. [Draft-IETF-agrewal-idr-accept-own-nexthop] <https://tools.ietf.org/id/draft-agrewal-idr-accept-own-nexthop-00.txt> | |
1988 | ||
0efdf0fe | 1989 | .. _bgp-community-lists: |
42fc5d26 | 1990 | |
8fcedbd2 QY |
1991 | Community Lists |
1992 | ^^^^^^^^^^^^^^^ | |
aa9eafa4 QY |
1993 | Community lists are user defined lists of community attribute values. These |
1994 | lists can be used for matching or manipulating the communities attribute in | |
1995 | UPDATE messages. | |
42fc5d26 | 1996 | |
aa9eafa4 | 1997 | There are two types of community list: |
c1a54c05 | 1998 | |
aa9eafa4 | 1999 | standard |
56f0bea7 | 2000 | This type accepts an explicit value for the attribute. |
aa9eafa4 QY |
2001 | |
2002 | expanded | |
2003 | This type accepts a regular expression. Because the regex must be | |
2004 | interpreted on each use expanded community lists are slower than standard | |
2005 | lists. | |
42fc5d26 | 2006 | |
a64e0ee5 | 2007 | .. clicmd:: bgp community-list standard NAME permit|deny COMMUNITY |
42fc5d26 | 2008 | |
aa9eafa4 QY |
2009 | This command defines a new standard community list. ``COMMUNITY`` is |
2010 | communities value. The ``COMMUNITY`` is compiled into community structure. | |
2011 | We can define multiple community list under same name. In that case match | |
2012 | will happen user defined order. Once the community list matches to | |
2013 | communities attribute in BGP updates it return permit or deny by the | |
2014 | community list definition. When there is no matched entry, deny will be | |
2015 | returned. When ``COMMUNITY`` is empty it matches to any routes. | |
42fc5d26 | 2016 | |
a64e0ee5 | 2017 | .. clicmd:: bgp community-list expanded NAME permit|deny COMMUNITY |
42fc5d26 | 2018 | |
aa9eafa4 QY |
2019 | This command defines a new expanded community list. ``COMMUNITY`` is a |
2020 | string expression of communities attribute. ``COMMUNITY`` can be a regular | |
2021 | expression (:ref:`bgp-regular-expressions`) to match the communities | |
47f47873 PG |
2022 | attribute in BGP updates. The expanded community is only used to filter, |
2023 | not `set` actions. | |
42fc5d26 | 2024 | |
aa9eafa4 QY |
2025 | .. deprecated:: 5.0 |
2026 | It is recommended to use the more explicit versions of this command. | |
42fc5d26 | 2027 | |
a64e0ee5 | 2028 | .. clicmd:: bgp community-list NAME permit|deny COMMUNITY |
aa9eafa4 QY |
2029 | |
2030 | When the community list type is not specified, the community list type is | |
2031 | automatically detected. If ``COMMUNITY`` can be compiled into communities | |
2032 | attribute, the community list is defined as a standard community list. | |
2033 | Otherwise it is defined as an expanded community list. This feature is left | |
2034 | for backward compatibility. Use of this feature is not recommended. | |
42fc5d26 | 2035 | |
03750f1e QY |
2036 | Note that all community lists share the same namespace, so it's not |
2037 | necessary to specify ``standard`` or ``expanded``; these modifiers are | |
2038 | purely aesthetic. | |
42fc5d26 | 2039 | |
36dc43aa | 2040 | .. clicmd:: show bgp community-list [NAME detail] |
42fc5d26 | 2041 | |
aa9eafa4 QY |
2042 | Displays community list information. When ``NAME`` is specified the |
2043 | specified community list's information is shown. | |
c3c5a71f | 2044 | |
c1a54c05 | 2045 | :: |
76bd1499 | 2046 | |
a64e0ee5 | 2047 | # show bgp community-list |
c1a54c05 QY |
2048 | Named Community standard list CLIST |
2049 | permit 7675:80 7675:100 no-export | |
2050 | deny internet | |
2051 | Named Community expanded list EXPAND | |
2052 | permit : | |
76bd1499 | 2053 | |
36dc43aa | 2054 | # show bgp community-list CLIST detail |
c1a54c05 QY |
2055 | Named Community standard list CLIST |
2056 | permit 7675:80 7675:100 no-export | |
2057 | deny internet | |
42fc5d26 | 2058 | |
42fc5d26 | 2059 | |
8fcedbd2 | 2060 | .. _bgp-numbered-community-lists: |
42fc5d26 | 2061 | |
8fcedbd2 QY |
2062 | Numbered Community Lists |
2063 | ^^^^^^^^^^^^^^^^^^^^^^^^ | |
42fc5d26 QY |
2064 | |
2065 | When number is used for BGP community list name, the number has | |
c3c5a71f QY |
2066 | special meanings. Community list number in the range from 1 and 99 is |
2067 | standard community list. Community list number in the range from 100 | |
2068 | to 199 is expanded community list. These community lists are called | |
2069 | as numbered community lists. On the other hand normal community lists | |
42fc5d26 QY |
2070 | is called as named community lists. |
2071 | ||
a64e0ee5 | 2072 | .. clicmd:: bgp community-list (1-99) permit|deny COMMUNITY |
42fc5d26 | 2073 | |
aa9eafa4 QY |
2074 | This command defines a new community list. The argument to (1-99) defines |
2075 | the list identifier. | |
42fc5d26 | 2076 | |
a64e0ee5 | 2077 | .. clicmd:: bgp community-list (100-199) permit|deny COMMUNITY |
42fc5d26 | 2078 | |
aa9eafa4 QY |
2079 | This command defines a new expanded community list. The argument to |
2080 | (100-199) defines the list identifier. | |
42fc5d26 | 2081 | |
6a89dd1e DA |
2082 | .. _bgp-community-alias: |
2083 | ||
2084 | Community alias | |
2085 | ^^^^^^^^^^^^^^^ | |
2086 | ||
2087 | BGP community aliases are useful to quickly identify what communities are set | |
2088 | for a specific prefix in a human-readable format. Especially handy for a huge | |
2089 | amount of communities. Accurately defined aliases can help you faster spot | |
2090 | things on the wire. | |
2091 | ||
2092 | .. clicmd:: bgp community alias NAME ALIAS | |
2093 | ||
2094 | This command creates an alias name for a community that will be used | |
2095 | later in various CLI outputs in a human-readable format. | |
2096 | ||
2097 | .. code-block:: frr | |
2098 | ||
2099 | ~# vtysh -c 'show run' | grep 'bgp community alias' | |
2100 | bgp community alias 65001:14 community-1 | |
2101 | bgp community alias 65001:123:1 lcommunity-1 | |
2102 | ||
2103 | ~# vtysh -c 'show ip bgp 172.16.16.1/32' | |
2104 | BGP routing table entry for 172.16.16.1/32, version 21 | |
2105 | Paths: (2 available, best #2, table default) | |
2106 | Advertised to non peer-group peers: | |
2107 | 65030 | |
2108 | 192.168.0.2 from 192.168.0.2 (172.16.16.1) | |
2109 | Origin incomplete, metric 0, valid, external, best (Neighbor IP) | |
2110 | Community: 65001:12 65001:13 community-1 65001:65534 | |
2111 | Large Community: lcommunity-1 65001:123:2 | |
2112 | Last update: Fri Apr 16 12:51:27 2021 | |
2113 | ||
9f977b2d DA |
2114 | .. clicmd:: show bgp [afi] [safi] [all] alias WORD [wide|json] |
2115 | ||
2116 | Display prefixes with matching BGP community alias. | |
2117 | ||
8fcedbd2 | 2118 | .. _bgp-using-communities-in-route-map: |
42fc5d26 | 2119 | |
8fcedbd2 QY |
2120 | Using Communities in Route Maps |
2121 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
42fc5d26 | 2122 | |
aa9eafa4 QY |
2123 | In :ref:`route-map` we can match on or set the BGP communities attribute. Using |
2124 | this feature network operator can implement their network policy based on BGP | |
2125 | communities attribute. | |
42fc5d26 | 2126 | |
b91bf5bd | 2127 | The following commands can be used in route maps: |
42fc5d26 | 2128 | |
aa9eafa4 | 2129 | .. clicmd:: match community WORD exact-match [exact-match] |
42fc5d26 | 2130 | |
c1a54c05 QY |
2131 | This command perform match to BGP updates using community list WORD. When |
2132 | the one of BGP communities value match to the one of communities value in | |
d1e7591e | 2133 | community list, it is match. When `exact-match` keyword is specified, match |
c1a54c05 QY |
2134 | happen only when BGP updates have completely same communities value |
2135 | specified in the community list. | |
42fc5d26 | 2136 | |
aa9eafa4 | 2137 | .. clicmd:: set community <none|COMMUNITY> additive |
42fc5d26 | 2138 | |
aa9eafa4 QY |
2139 | This command sets the community value in BGP updates. If the attribute is |
2140 | already configured, the newly provided value replaces the old one unless the | |
2141 | ``additive`` keyword is specified, in which case the new value is appended | |
2142 | to the existing value. | |
42fc5d26 | 2143 | |
aa9eafa4 QY |
2144 | If ``none`` is specified as the community value, the communities attribute |
2145 | is not sent. | |
42fc5d26 | 2146 | |
47f47873 PG |
2147 | It is not possible to set an expanded community list. |
2148 | ||
29adcd50 | 2149 | .. clicmd:: set comm-list WORD delete |
c1a54c05 | 2150 | |
aa9eafa4 QY |
2151 | This command remove communities value from BGP communities attribute. The |
2152 | ``word`` is community list name. When BGP route's communities value matches | |
2153 | to the community list ``word``, the communities value is removed. When all | |
2154 | of communities value is removed eventually, the BGP update's communities | |
2155 | attribute is completely removed. | |
42fc5d26 | 2156 | |
8fcedbd2 | 2157 | .. _bgp-communities-example: |
c1a54c05 | 2158 | |
8fcedbd2 QY |
2159 | Example Configuration |
2160 | ^^^^^^^^^^^^^^^^^^^^^ | |
9eb95b3b | 2161 | |
8fcedbd2 QY |
2162 | The following configuration is exemplary of the most typical usage of BGP |
2163 | communities attribute. In the example, AS 7675 provides an upstream Internet | |
2164 | connection to AS 100. When the following configuration exists in AS 7675, the | |
2165 | network operator of AS 100 can set local preference in AS 7675 network by | |
2166 | setting BGP communities attribute to the updates. | |
9eb95b3b QY |
2167 | |
2168 | .. code-block:: frr | |
c1a54c05 QY |
2169 | |
2170 | router bgp 7675 | |
2171 | neighbor 192.168.0.1 remote-as 100 | |
2172 | address-family ipv4 unicast | |
2173 | neighbor 192.168.0.1 route-map RMAP in | |
2174 | exit-address-family | |
2175 | ! | |
a64e0ee5 DA |
2176 | bgp community-list 70 permit 7675:70 |
2177 | bgp community-list 70 deny | |
2178 | bgp community-list 80 permit 7675:80 | |
2179 | bgp community-list 80 deny | |
2180 | bgp community-list 90 permit 7675:90 | |
2181 | bgp community-list 90 deny | |
c1a54c05 QY |
2182 | ! |
2183 | route-map RMAP permit 10 | |
2184 | match community 70 | |
2185 | set local-preference 70 | |
2186 | ! | |
2187 | route-map RMAP permit 20 | |
2188 | match community 80 | |
2189 | set local-preference 80 | |
2190 | ! | |
2191 | route-map RMAP permit 30 | |
2192 | match community 90 | |
2193 | set local-preference 90 | |
c3c5a71f | 2194 | |
42fc5d26 | 2195 | |
8fcedbd2 QY |
2196 | The following configuration announces ``10.0.0.0/8`` from AS 100 to AS 7675. |
2197 | The route has communities value ``7675:80`` so when above configuration exists | |
2198 | in AS 7675, the announced routes' local preference value will be set to 80. | |
9eb95b3b QY |
2199 | |
2200 | .. code-block:: frr | |
c1a54c05 QY |
2201 | |
2202 | router bgp 100 | |
2203 | network 10.0.0.0/8 | |
2204 | neighbor 192.168.0.2 remote-as 7675 | |
2205 | address-family ipv4 unicast | |
2206 | neighbor 192.168.0.2 route-map RMAP out | |
2207 | exit-address-family | |
2208 | ! | |
2209 | ip prefix-list PLIST permit 10.0.0.0/8 | |
2210 | ! | |
2211 | route-map RMAP permit 10 | |
2212 | match ip address prefix-list PLIST | |
2213 | set community 7675:80 | |
c3c5a71f | 2214 | |
42fc5d26 | 2215 | |
8fcedbd2 QY |
2216 | The following configuration is an example of BGP route filtering using |
2217 | communities attribute. This configuration only permit BGP routes which has BGP | |
2218 | communities value ``0:80`` or ``0:90``. The network operator can set special | |
2219 | internal communities value at BGP border router, then limit the BGP route | |
2220 | announcements into the internal network. | |
9eb95b3b QY |
2221 | |
2222 | .. code-block:: frr | |
42fc5d26 | 2223 | |
c1a54c05 QY |
2224 | router bgp 7675 |
2225 | neighbor 192.168.0.1 remote-as 100 | |
2226 | address-family ipv4 unicast | |
2227 | neighbor 192.168.0.1 route-map RMAP in | |
2228 | exit-address-family | |
2229 | ! | |
a64e0ee5 | 2230 | bgp community-list 1 permit 0:80 0:90 |
c1a54c05 QY |
2231 | ! |
2232 | route-map RMAP permit in | |
2233 | match community 1 | |
c3c5a71f | 2234 | |
42fc5d26 | 2235 | |
8fcedbd2 QY |
2236 | The following example filters BGP routes which have a community value of |
2237 | ``1:1``. When there is no match community-list returns ``deny``. To avoid | |
2238 | filtering all routes, a ``permit`` line is set at the end of the | |
2239 | community-list. | |
9eb95b3b QY |
2240 | |
2241 | .. code-block:: frr | |
42fc5d26 | 2242 | |
c1a54c05 QY |
2243 | router bgp 7675 |
2244 | neighbor 192.168.0.1 remote-as 100 | |
2245 | address-family ipv4 unicast | |
2246 | neighbor 192.168.0.1 route-map RMAP in | |
2247 | exit-address-family | |
2248 | ! | |
a64e0ee5 DA |
2249 | bgp community-list standard FILTER deny 1:1 |
2250 | bgp community-list standard FILTER permit | |
c1a54c05 QY |
2251 | ! |
2252 | route-map RMAP permit 10 | |
2253 | match community FILTER | |
c3c5a71f | 2254 | |
42fc5d26 | 2255 | |
8fcedbd2 QY |
2256 | The communities value keyword ``internet`` has special meanings in standard |
2257 | community lists. In the below example ``internet`` matches all BGP routes even | |
2258 | if the route does not have communities attribute at all. So community list | |
2259 | ``INTERNET`` is the same as ``FILTER`` in the previous example. | |
9eb95b3b QY |
2260 | |
2261 | .. code-block:: frr | |
42fc5d26 | 2262 | |
a64e0ee5 DA |
2263 | bgp community-list standard INTERNET deny 1:1 |
2264 | bgp community-list standard INTERNET permit internet | |
c3c5a71f | 2265 | |
42fc5d26 | 2266 | |
8fcedbd2 QY |
2267 | The following configuration is an example of communities value deletion. With |
2268 | this configuration the community values ``100:1`` and ``100:2`` are removed | |
2269 | from BGP updates. For communities value deletion, only ``permit`` | |
2270 | community-list is used. ``deny`` community-list is ignored. | |
9eb95b3b QY |
2271 | |
2272 | .. code-block:: frr | |
42fc5d26 | 2273 | |
c1a54c05 QY |
2274 | router bgp 7675 |
2275 | neighbor 192.168.0.1 remote-as 100 | |
2276 | address-family ipv4 unicast | |
2277 | neighbor 192.168.0.1 route-map RMAP in | |
2278 | exit-address-family | |
2279 | ! | |
a64e0ee5 | 2280 | bgp community-list standard DEL permit 100:1 100:2 |
c1a54c05 QY |
2281 | ! |
2282 | route-map RMAP permit 10 | |
2283 | set comm-list DEL delete | |
c3c5a71f | 2284 | |
42fc5d26 | 2285 | |
0efdf0fe | 2286 | .. _bgp-extended-communities-attribute: |
42fc5d26 | 2287 | |
8fcedbd2 QY |
2288 | Extended Communities Attribute |
2289 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
42fc5d26 | 2290 | |
c1a54c05 QY |
2291 | BGP extended communities attribute is introduced with MPLS VPN/BGP technology. |
2292 | MPLS VPN/BGP expands capability of network infrastructure to provide VPN | |
2293 | functionality. At the same time it requires a new framework for policy routing. | |
2294 | With BGP Extended Communities Attribute we can use Route Target or Site of | |
2295 | Origin for implementing network policy for MPLS VPN/BGP. | |
42fc5d26 | 2296 | |
c1a54c05 QY |
2297 | BGP Extended Communities Attribute is similar to BGP Communities Attribute. It |
2298 | is an optional transitive attribute. BGP Extended Communities Attribute can | |
2299 | carry multiple Extended Community value. Each Extended Community value is | |
2300 | eight octet length. | |
42fc5d26 | 2301 | |
c1a54c05 QY |
2302 | BGP Extended Communities Attribute provides an extended range compared with BGP |
2303 | Communities Attribute. Adding to that there is a type field in each value to | |
2304 | provides community space structure. | |
42fc5d26 | 2305 | |
c1a54c05 QY |
2306 | There are two format to define Extended Community value. One is AS based format |
2307 | the other is IP address based format. | |
42fc5d26 | 2308 | |
8fcedbd2 QY |
2309 | ``AS:VAL`` |
2310 | This is a format to define AS based Extended Community value. ``AS`` part | |
2311 | is 2 octets Global Administrator subfield in Extended Community value. | |
2312 | ``VAL`` part is 4 octets Local Administrator subfield. ``7675:100`` | |
2313 | represents AS 7675 policy value 100. | |
42fc5d26 | 2314 | |
8fcedbd2 | 2315 | ``IP-Address:VAL`` |
c1a54c05 | 2316 | This is a format to define IP address based Extended Community value. |
8fcedbd2 QY |
2317 | ``IP-Address`` part is 4 octets Global Administrator subfield. ``VAL`` part |
2318 | is 2 octets Local Administrator subfield. | |
42fc5d26 | 2319 | |
0efdf0fe | 2320 | .. _bgp-extended-community-lists: |
42fc5d26 | 2321 | |
8fcedbd2 QY |
2322 | Extended Community Lists |
2323 | ^^^^^^^^^^^^^^^^^^^^^^^^ | |
42fc5d26 | 2324 | |
a64e0ee5 | 2325 | .. clicmd:: bgp extcommunity-list standard NAME permit|deny EXTCOMMUNITY |
42fc5d26 | 2326 | |
4da7fda3 QY |
2327 | This command defines a new standard extcommunity-list. `extcommunity` is |
2328 | extended communities value. The `extcommunity` is compiled into extended | |
2329 | community structure. We can define multiple extcommunity-list under same | |
2330 | name. In that case match will happen user defined order. Once the | |
2331 | extcommunity-list matches to extended communities attribute in BGP updates | |
2332 | it return permit or deny based upon the extcommunity-list definition. When | |
2333 | there is no matched entry, deny will be returned. When `extcommunity` is | |
2334 | empty it matches to any routes. | |
42fc5d26 | 2335 | |
a64e0ee5 | 2336 | .. clicmd:: bgp extcommunity-list expanded NAME permit|deny LINE |
42fc5d26 | 2337 | |
4da7fda3 QY |
2338 | This command defines a new expanded extcommunity-list. `line` is a string |
2339 | expression of extended communities attribute. `line` can be a regular | |
2340 | expression (:ref:`bgp-regular-expressions`) to match an extended communities | |
2341 | attribute in BGP updates. | |
42fc5d26 | 2342 | |
03750f1e QY |
2343 | Note that all extended community lists shares a single name space, so it's |
2344 | not necessary to specify their type when creating or destroying them. | |
42fc5d26 | 2345 | |
03750f1e | 2346 | .. clicmd:: show bgp extcommunity-list [NAME detail] |
c1a54c05 | 2347 | |
4da7fda3 | 2348 | This command displays current extcommunity-list information. When `name` is |
03750f1e | 2349 | specified the community list's information is shown. |
c3c5a71f | 2350 | |
42fc5d26 | 2351 | |
0efdf0fe | 2352 | .. _bgp-extended-communities-in-route-map: |
42fc5d26 QY |
2353 | |
2354 | BGP Extended Communities in Route Map | |
8fcedbd2 | 2355 | """"""""""""""""""""""""""""""""""""" |
42fc5d26 | 2356 | |
29adcd50 | 2357 | .. clicmd:: match extcommunity WORD |
42fc5d26 | 2358 | |
29adcd50 | 2359 | .. clicmd:: set extcommunity rt EXTCOMMUNITY |
42fc5d26 | 2360 | |
c1a54c05 | 2361 | This command set Route Target value. |
42fc5d26 | 2362 | |
29adcd50 | 2363 | .. clicmd:: set extcommunity soo EXTCOMMUNITY |
c1a54c05 QY |
2364 | |
2365 | This command set Site of Origin value. | |
42fc5d26 | 2366 | |
ed647ed2 | 2367 | .. clicmd:: set extcommunity bandwidth <(1-25600) | cumulative | num-multipaths> [non-transitive] |
2368 | ||
2369 | This command sets the BGP link-bandwidth extended community for the prefix | |
2370 | (best path) for which it is applied. The link-bandwidth can be specified as | |
2371 | an ``explicit value`` (specified in Mbps), or the router can be told to use | |
2372 | the ``cumulative bandwidth`` of all multipaths for the prefix or to compute | |
2373 | it based on the ``number of multipaths``. The link bandwidth extended | |
2374 | community is encoded as ``transitive`` unless the set command explicitly | |
2375 | configures it as ``non-transitive``. | |
2376 | ||
2377 | .. seealso:: :ref:`wecmp_linkbw` | |
47f47873 PG |
2378 | |
2379 | Note that the extended expanded community is only used for `match` rule, not for | |
2380 | `set` actions. | |
2381 | ||
0efdf0fe | 2382 | .. _bgp-large-communities-attribute: |
42fc5d26 | 2383 | |
8fcedbd2 QY |
2384 | Large Communities Attribute |
2385 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
42fc5d26 QY |
2386 | |
2387 | The BGP Large Communities attribute was introduced in Feb 2017 with | |
c1a54c05 | 2388 | :rfc:`8092`. |
42fc5d26 | 2389 | |
8fcedbd2 QY |
2390 | The BGP Large Communities Attribute is similar to the BGP Communities Attribute |
2391 | except that it has 3 components instead of two and each of which are 4 octets | |
2392 | in length. Large Communities bring additional functionality and convenience | |
2393 | over traditional communities, specifically the fact that the ``GLOBAL`` part | |
2394 | below is now 4 octets wide allowing seamless use in networks using 4-byte ASNs. | |
2395 | ||
2396 | ``GLOBAL:LOCAL1:LOCAL2`` | |
2397 | This is the format to define Large Community values. Referencing :rfc:`8195` | |
2398 | the values are commonly referred to as follows: | |
2399 | ||
2400 | - The ``GLOBAL`` part is a 4 octet Global Administrator field, commonly used | |
2401 | as the operators AS number. | |
2402 | - The ``LOCAL1`` part is a 4 octet Local Data Part 1 subfield referred to as | |
2403 | a function. | |
2404 | - The ``LOCAL2`` part is a 4 octet Local Data Part 2 field and referred to | |
2405 | as the parameter subfield. | |
2406 | ||
2407 | As an example, ``65551:1:10`` represents AS 65551 function 1 and parameter | |
2408 | 10. The referenced RFC above gives some guidelines on recommended usage. | |
42fc5d26 | 2409 | |
0efdf0fe | 2410 | .. _bgp-large-community-lists: |
42fc5d26 | 2411 | |
8fcedbd2 QY |
2412 | Large Community Lists |
2413 | """"""""""""""""""""" | |
42fc5d26 QY |
2414 | |
2415 | Two types of large community lists are supported, namely `standard` and | |
2416 | `expanded`. | |
2417 | ||
a64e0ee5 | 2418 | .. clicmd:: bgp large-community-list standard NAME permit|deny LARGE-COMMUNITY |
42fc5d26 | 2419 | |
4da7fda3 QY |
2420 | This command defines a new standard large-community-list. `large-community` |
2421 | is the Large Community value. We can add multiple large communities under | |
2422 | same name. In that case the match will happen in the user defined order. | |
2423 | Once the large-community-list matches the Large Communities attribute in BGP | |
2424 | updates it will return permit or deny based upon the large-community-list | |
2425 | definition. When there is no matched entry, a deny will be returned. When | |
2426 | `large-community` is empty it matches any routes. | |
42fc5d26 | 2427 | |
a64e0ee5 | 2428 | .. clicmd:: bgp large-community-list expanded NAME permit|deny LINE |
42fc5d26 | 2429 | |
4da7fda3 QY |
2430 | This command defines a new expanded large-community-list. Where `line` is a |
2431 | string matching expression, it will be compared to the entire Large | |
2432 | Communities attribute as a string, with each large-community in order from | |
2433 | lowest to highest. `line` can also be a regular expression which matches | |
2434 | this Large Community attribute. | |
42fc5d26 | 2435 | |
03750f1e QY |
2436 | Note that all community lists share the same namespace, so it's not |
2437 | necessary to specify ``standard`` or ``expanded``; these modifiers are | |
2438 | purely aesthetic. | |
42fc5d26 | 2439 | |
a64e0ee5 | 2440 | .. clicmd:: show bgp large-community-list |
42fc5d26 | 2441 | |
36dc43aa | 2442 | .. clicmd:: show bgp large-community-list NAME detail |
42fc5d26 | 2443 | |
c1a54c05 QY |
2444 | This command display current large-community-list information. When |
2445 | `name` is specified the community list information is shown. | |
42fc5d26 | 2446 | |
29adcd50 | 2447 | .. clicmd:: show ip bgp large-community-info |
c1a54c05 QY |
2448 | |
2449 | This command displays the current large communities in use. | |
42fc5d26 | 2450 | |
0efdf0fe | 2451 | .. _bgp-large-communities-in-route-map: |
42fc5d26 | 2452 | |
8fcedbd2 QY |
2453 | Large Communities in Route Map |
2454 | """""""""""""""""""""""""""""" | |
42fc5d26 | 2455 | |
03ff9a14 | 2456 | .. clicmd:: match large-community LINE [exact-match] |
42fc5d26 | 2457 | |
4da7fda3 QY |
2458 | Where `line` can be a simple string to match, or a regular expression. It |
2459 | is very important to note that this match occurs on the entire | |
c1a54c05 | 2460 | large-community string as a whole, where each large-community is ordered |
03ff9a14 | 2461 | from lowest to highest. When `exact-match` keyword is specified, match |
2462 | happen only when BGP updates have completely same large communities value | |
2463 | specified in the large community list. | |
42fc5d26 | 2464 | |
29adcd50 | 2465 | .. clicmd:: set large-community LARGE-COMMUNITY |
42fc5d26 | 2466 | |
29adcd50 | 2467 | .. clicmd:: set large-community LARGE-COMMUNITY LARGE-COMMUNITY |
42fc5d26 | 2468 | |
29adcd50 | 2469 | .. clicmd:: set large-community LARGE-COMMUNITY additive |
c1a54c05 QY |
2470 | |
2471 | These commands are used for setting large-community values. The first | |
2472 | command will overwrite any large-communities currently present. | |
2473 | The second specifies two large-communities, which overwrites the current | |
2474 | large-community list. The third will add a large-community value without | |
2475 | overwriting other values. Multiple large-community values can be specified. | |
42fc5d26 | 2476 | |
47f47873 PG |
2477 | Note that the large expanded community is only used for `match` rule, not for |
2478 | `set` actions. | |
b572f826 | 2479 | |
c8a5e5e1 | 2480 | .. _bgp-l3vpn-vrfs: |
b572f826 | 2481 | |
c8a5e5e1 QY |
2482 | L3VPN VRFs |
2483 | ---------- | |
b572f826 | 2484 | |
c8a5e5e1 QY |
2485 | *bgpd* supports :abbr:`L3VPN (Layer 3 Virtual Private Networks)` :abbr:`VRFs |
2486 | (Virtual Routing and Forwarding)` for IPv4 :rfc:`4364` and IPv6 :rfc:`4659`. | |
2487 | L3VPN routes, and their associated VRF MPLS labels, can be distributed to VPN | |
2488 | SAFI neighbors in the *default*, i.e., non VRF, BGP instance. VRF MPLS labels | |
2489 | are reached using *core* MPLS labels which are distributed using LDP or BGP | |
2490 | labeled unicast. *bgpd* also supports inter-VRF route leaking. | |
b572f826 | 2491 | |
b572f826 | 2492 | |
c8a5e5e1 | 2493 | .. _bgp-vrf-route-leaking: |
8fcedbd2 QY |
2494 | |
2495 | VRF Route Leaking | |
c8a5e5e1 | 2496 | ----------------- |
8fcedbd2 QY |
2497 | |
2498 | BGP routes may be leaked (i.e. copied) between a unicast VRF RIB and the VPN | |
f90115c5 LB |
2499 | SAFI RIB of the default VRF for use in MPLS-based L3VPNs. Unicast routes may |
2500 | also be leaked between any VRFs (including the unicast RIB of the default BGP | |
2501 | instanced). A shortcut syntax is also available for specifying leaking from one | |
2502 | VRF to another VRF using the default instance's VPN RIB as the intemediary. A | |
2503 | common application of the VRF-VRF feature is to connect a customer's private | |
8fcedbd2 QY |
2504 | routing domain to a provider's VPN service. Leaking is configured from the |
2505 | point of view of an individual VRF: ``import`` refers to routes leaked from VPN | |
2506 | to a unicast VRF, whereas ``export`` refers to routes leaked from a unicast VRF | |
2507 | to VPN. | |
2508 | ||
2509 | Required parameters | |
c8a5e5e1 | 2510 | ^^^^^^^^^^^^^^^^^^^ |
b572f826 | 2511 | |
4da7fda3 QY |
2512 | Routes exported from a unicast VRF to the VPN RIB must be augmented by two |
2513 | parameters: | |
2514 | ||
2515 | - an :abbr:`RD (Route Distinguisher)` | |
2516 | - an :abbr:`RTLIST (Route-target List)` | |
2517 | ||
2518 | Configuration for these exported routes must, at a minimum, specify these two | |
2519 | parameters. | |
2520 | ||
2521 | Routes imported from the VPN RIB to a unicast VRF are selected according to | |
2522 | their RTLISTs. Routes whose RTLIST contains at least one route-target in | |
2523 | common with the configured import RTLIST are leaked. Configuration for these | |
2524 | imported routes must specify an RTLIST to be matched. | |
2525 | ||
2526 | The RD, which carries no semantic value, is intended to make the route unique | |
2527 | in the VPN RIB among all routes of its prefix that originate from all the | |
2528 | customers and sites that are attached to the provider's VPN service. | |
2529 | Accordingly, each site of each customer is typically assigned an RD that is | |
2530 | unique across the entire provider network. | |
2531 | ||
2532 | The RTLIST is a set of route-target extended community values whose purpose is | |
2533 | to specify route-leaking policy. Typically, a customer is assigned a single | |
2534 | route-target value for import and export to be used at all customer sites. This | |
2535 | configuration specifies a simple topology wherein a customer has a single | |
2536 | routing domain which is shared across all its sites. More complex routing | |
2537 | topologies are possible through use of additional route-targets to augment the | |
2538 | leaking of sets of routes in various ways. | |
b572f826 | 2539 | |
e967a1d0 DS |
2540 | When using the shortcut syntax for vrf-to-vrf leaking, the RD and RT are |
2541 | auto-derived. | |
fb3d9f3e | 2542 | |
8fcedbd2 | 2543 | General configuration |
c8a5e5e1 | 2544 | ^^^^^^^^^^^^^^^^^^^^^ |
b572f826 | 2545 | |
f90115c5 | 2546 | Configuration of route leaking between a unicast VRF RIB and the VPN SAFI RIB |
4da7fda3 QY |
2547 | of the default VRF is accomplished via commands in the context of a VRF |
2548 | address-family: | |
b572f826 | 2549 | |
b572f826 PZ |
2550 | .. clicmd:: rd vpn export AS:NN|IP:nn |
2551 | ||
4da7fda3 QY |
2552 | Specifies the route distinguisher to be added to a route exported from the |
2553 | current unicast VRF to VPN. | |
b572f826 | 2554 | |
b572f826 PZ |
2555 | .. clicmd:: rt vpn import|export|both RTLIST... |
2556 | ||
4da7fda3 QY |
2557 | Specifies the route-target list to be attached to a route (export) or the |
2558 | route-target list to match against (import) when exporting/importing between | |
2559 | the current unicast VRF and VPN. | |
b572f826 | 2560 | |
4da7fda3 QY |
2561 | The RTLIST is a space-separated list of route-targets, which are BGP |
2562 | extended community values as described in | |
b572f826 PZ |
2563 | :ref:`bgp-extended-communities-attribute`. |
2564 | ||
e70e9f8e | 2565 | .. clicmd:: label vpn export (0..1048575)|auto |
b572f826 | 2566 | |
8a2124f7 | 2567 | Enables an MPLS label to be attached to a route exported from the current |
2568 | unicast VRF to VPN. If the value specified is ``auto``, the label value is | |
2569 | automatically assigned from a pool maintained by the Zebra daemon. If Zebra | |
2570 | is not running, or if this command is not configured, automatic label | |
2571 | assignment will not complete, which will block corresponding route export. | |
b572f826 | 2572 | |
b572f826 PZ |
2573 | .. clicmd:: nexthop vpn export A.B.C.D|X:X::X:X |
2574 | ||
4da7fda3 QY |
2575 | Specifies an optional nexthop value to be assigned to a route exported from |
2576 | the current unicast VRF to VPN. If left unspecified, the nexthop will be set | |
2577 | to 0.0.0.0 or 0:0::0:0 (self). | |
b572f826 | 2578 | |
b572f826 PZ |
2579 | .. clicmd:: route-map vpn import|export MAP |
2580 | ||
4da7fda3 | 2581 | Specifies an optional route-map to be applied to routes imported or exported |
d1e7591e | 2582 | between the current unicast VRF and VPN. |
b572f826 | 2583 | |
b572f826 PZ |
2584 | .. clicmd:: import|export vpn |
2585 | ||
d1e7591e | 2586 | Enables import or export of routes between the current unicast VRF and VPN. |
b572f826 | 2587 | |
fb3d9f3e DS |
2588 | .. clicmd:: import vrf VRFNAME |
2589 | ||
e967a1d0 DS |
2590 | Shortcut syntax for specifying automatic leaking from vrf VRFNAME to |
2591 | the current VRF using the VPN RIB as intermediary. The RD and RT | |
2592 | are auto derived and should not be specified explicitly for either the | |
2593 | source or destination VRF's. | |
2594 | ||
2595 | This shortcut syntax mode is not compatible with the explicit | |
2596 | `import vpn` and `export vpn` statements for the two VRF's involved. | |
2597 | The CLI will disallow attempts to configure incompatible leaking | |
2598 | modes. | |
fb3d9f3e | 2599 | |
4ccd4033 HS |
2600 | .. _bgp-l3vpn-srv6: |
2601 | ||
2602 | L3VPN SRv6 | |
2603 | ---------- | |
2604 | ||
2605 | .. clicmd:: segment-routing srv6 | |
2606 | ||
2607 | Use SRv6 backend with BGP L3VPN, and go to its configuration node. | |
2608 | ||
2609 | .. clicmd:: locator NAME | |
2610 | ||
2611 | Specify the SRv6 locator to be used for SRv6 L3VPN. The Locator name must | |
2612 | be set in zebra, but user can set it in any order. | |
42fc5d26 | 2613 | |
b6c34e85 CS |
2614 | .. _bgp-evpn: |
2615 | ||
2616 | Ethernet Virtual Network - EVPN | |
2617 | ------------------------------- | |
2618 | ||
0a4e0034 JAG |
2619 | Note: When using EVPN features and if you have a large number of hosts, make |
2620 | sure to adjust the size of the arp neighbor cache to avoid neighbor table | |
2621 | overflow and/or excessive garbage collection. On Linux, the size of the table | |
2622 | and garbage collection frequency can be controlled via the following | |
2623 | sysctl configurations: | |
2624 | ||
2625 | .. code-block:: shell | |
2626 | ||
2627 | net.ipv4.neigh.default.gc_thresh1 | |
2628 | net.ipv4.neigh.default.gc_thresh2 | |
2629 | net.ipv4.neigh.default.gc_thresh3 | |
2630 | ||
2631 | net.ipv6.neigh.default.gc_thresh1 | |
2632 | net.ipv6.neigh.default.gc_thresh2 | |
2633 | net.ipv6.neigh.default.gc_thresh3 | |
2634 | ||
2635 | For more information, see ``man 7 arp``. | |
2636 | ||
b6c34e85 CS |
2637 | .. _bgp-evpn-advertise-pip: |
2638 | ||
2639 | EVPN advertise-PIP | |
2640 | ^^^^^^^^^^^^^^^^^^ | |
2641 | ||
2642 | In a EVPN symmetric routing MLAG deployment, all EVPN routes advertised | |
2643 | with anycast-IP as next-hop IP and anycast MAC as the Router MAC (RMAC - in | |
2644 | BGP EVPN Extended-Community). | |
2645 | EVPN picks up the next-hop IP from the VxLAN interface's local tunnel IP and | |
2646 | the RMAC is obtained from the MAC of the L3VNI's SVI interface. | |
2647 | Note: Next-hop IP is used for EVPN routes whether symmetric routing is | |
2648 | deployed or not but the RMAC is only relevant for symmetric routing scenario. | |
2649 | ||
2650 | Current behavior is not ideal for Prefix (type-5) and self (type-2) | |
2651 | routes. This is because the traffic from remote VTEPs routed sub optimally | |
2652 | if they land on the system where the route does not belong. | |
2653 | ||
2654 | The advertise-pip feature advertises Prefix (type-5) and self (type-2) | |
2655 | routes with system's individual (primary) IP as the next-hop and individual | |
2656 | (system) MAC as Router-MAC (RMAC), while leaving the behavior unchanged for | |
2657 | other EVPN routes. | |
2658 | ||
2659 | To support this feature there needs to have ability to co-exist a | |
2660 | (system-MAC, system-IP) pair with a (anycast-MAC, anycast-IP) pair with the | |
2661 | ability to terminate VxLAN-encapsulated packets received for either pair on | |
0a4e0034 | 2662 | the same L3VNI (i.e associated VLAN). This capability is needed per tenant |
b6c34e85 CS |
2663 | VRF instance. |
2664 | ||
0a4e0034 | 2665 | To derive the system-MAC and the anycast MAC, there must be a |
b6c34e85 CS |
2666 | separate/additional MAC-VLAN interface corresponding to L3VNI’s SVI. |
2667 | The SVI interface’s MAC address can be interpreted as system-MAC | |
2668 | and MAC-VLAN interface's MAC as anycast MAC. | |
2669 | ||
2670 | To derive system-IP and anycast-IP, the default BGP instance's router-id is used | |
2671 | as system-IP and the VxLAN interface’s local tunnel IP as the anycast-IP. | |
2672 | ||
2673 | User has an option to configure the system-IP and/or system-MAC value if the | |
2674 | auto derived value is not preferred. | |
2675 | ||
2676 | Note: By default, advertise-pip feature is enabled and user has an option to | |
0a4e0034 | 2677 | disable the feature via configuration CLI. Once the feature is disabled under |
b6c34e85 CS |
2678 | bgp vrf instance or MAC-VLAN interface is not configured, all the routes follow |
2679 | the same behavior of using same next-hop and RMAC values. | |
2680 | ||
03750f1e | 2681 | .. clicmd:: advertise-pip [ip <addr> [mac <addr>]] |
b6c34e85 CS |
2682 | |
2683 | Enables or disables advertise-pip feature, specifiy system-IP and/or system-MAC | |
2684 | parameters. | |
2685 | ||
a927f5bc JAG |
2686 | EVPN advertise-svi-ip |
2687 | ^^^^^^^^^^^^^^^^^^^^^ | |
0a4e0034 | 2688 | Typically, the SVI IP address is reused on VTEPs across multiple racks. However, |
a927f5bc | 2689 | if you have unique SVI IP addresses that you want to be reachable you can use the |
0a4e0034 JAG |
2690 | advertise-svi-ip option. This option advertises the SVI IP/MAC address as a type-2 |
2691 | route and eliminates the need for any flooding over VXLAN to reach the IP from a | |
2692 | remote VTEP. | |
2693 | ||
a927f5bc | 2694 | .. clicmd:: advertise-svi-ip |
0a4e0034 JAG |
2695 | |
2696 | Note that you should not enable both the advertise-svi-ip and the advertise-default-gw | |
2697 | at the same time. | |
2698 | ||
40f4507d AD |
2699 | .. _bgp-evpn-overlay-index-gateway-ip: |
2700 | ||
2701 | EVPN Overlay Index Gateway IP | |
2702 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
2703 | Draft https://tools.ietf.org/html/draft-ietf-bess-evpn-prefix-advertisement-11 | |
2704 | explains the use of overlay indexes for recursive route resolution for EVPN | |
2705 | type-5 route. | |
2706 | ||
2707 | We support gateway IP overlay index. | |
2708 | A gateway IP, advertised with EVPN prefix route, is used to find an EVPN MAC/IP | |
2709 | route with its IP field same as the gateway IP. This MAC/IP entry provides the | |
2710 | nexthop VTEP and the tunnel information required for the VxLAN encapsulation. | |
2711 | ||
2712 | Functionality: | |
2713 | ||
2714 | :: | |
2715 | ||
2716 | . +--------+ BGP +--------+ BGP +--------+ +--------+ | |
2717 | SN1 | | IPv4 | | EVPN | | | | | |
2718 | ======+ Host1 +------+ PE1 +------+ PE2 +------+ Host2 + | |
2719 | | | | | | | | | | |
2720 | +--------+ +--------+ +--------+ +--------+ | |
2721 | ||
2722 | Consider above topology where prefix SN1 is connected behind host1. Host1 | |
2723 | advertises SN1 to PE1 over BGP IPv4 session. PE1 advertises SN1 to PE2 using | |
2724 | EVPN type-5 route with host1 IP as the gateway IP. PE1 also advertises | |
2725 | Host1 MAC/IP as type-2 route which is used to resolve host1 gateway IP. | |
2726 | ||
2727 | PE2 receives this type-5 route and imports it into the vrf based on route | |
2728 | targets. BGP prefix imported into the vrf uses gateway IP as its BGP nexthop. | |
2729 | This route is installed into zebra if following conditions are satisfied: | |
7aa6fb2d | 2730 | |
40f4507d AD |
2731 | 1. Gateway IP nexthop is L3 reachable. |
2732 | 2. PE2 has received EVPN type-2 route with IP field set to gateway IP. | |
2733 | ||
2734 | Topology requirements: | |
7aa6fb2d | 2735 | |
40f4507d AD |
2736 | 1. This feature is supported for asymmetric routing model only. While |
2737 | sending packets to SN1, ingress PE (PE2) performs routing and | |
2738 | egress PE (PE1) performs only bridging. | |
2739 | 2. This feature supports only tratitional(non vlan-aware) bridge model. Bridge | |
2740 | interface associated with L2VNI is an L3 interface. i.e., this interface is | |
2741 | configured with an address in the L2VNI subnet. Note that the gateway IP | |
2742 | should also have an address in the same subnet. | |
2743 | 3. As this feature works in asymmetric routing model, all L2VNIs and corresponding | |
2744 | VxLAN and bridge interfaces should be present at all the PEs. | |
2745 | 4. L3VNI configuration is required to generate and import EVPN type-5 routes. | |
2746 | L3VNI VxLAN and bridge interfaces also should be present. | |
2747 | ||
2748 | A PE can use one of the following two mechanisms to advertise an EVPN type-5 | |
2749 | route with gateway IP. | |
2750 | ||
2751 | 1. CLI to add gateway IP while generating EVPN type-5 route from a BGP IPv4/IPv6 | |
2752 | prefix: | |
2753 | ||
2754 | .. index:: advertise <ipv4|ipv6> unicast [gateway-ip] | |
2755 | .. clicmd:: [no] advertise <ipv4|ipv6> unicast [gateway-ip] | |
2756 | ||
2757 | When this CLI is configured for a BGP vrf under L2VPN EVPN address family, EVPN | |
2758 | type-5 routes are generated for BGP prefixes in the vrf. Nexthop of the BGP | |
2759 | prefix becomes the gateway IP of the corresponding type-5 route. | |
2760 | ||
2761 | If the above command is configured without the "gateway-ip" keyword, type-5 | |
2762 | routes are generated without overlay index. | |
2763 | ||
2764 | 2. Add gateway IP to EVPN type-5 route using a route-map: | |
2765 | ||
2766 | .. index:: set evpn gateway-ip <ipv4|ipv6> <addr> | |
2767 | .. clicmd:: [no] set evpn gateway-ip <ipv4|ipv6> <addr> | |
2768 | ||
2769 | When route-map with above set clause is applied as outbound policy in BGP, it | |
2770 | will set the gateway-ip in EVPN type-5 NLRI. | |
2771 | ||
2772 | Example configuration: | |
2773 | ||
2774 | .. code-block:: frr | |
2775 | ||
2776 | router bgp 100 | |
2777 | neighbor 192.168.0.1 remote-as 101 | |
2778 | ! | |
2779 | address-family ipv4 l2vpn evpn | |
2780 | neighbor 192.168.0.1 route-map RMAP out | |
2781 | exit-address-family | |
2782 | ! | |
2783 | route-map RMAP permit 10 | |
2784 | set evpn gateway-ip 10.0.0.1 | |
2785 | set evpn gateway-ip 10::1 | |
2786 | ||
2787 | A PE that receives a type-5 route with gateway IP overlay index should have | |
2788 | "enable-resolve-overlay-index" configuration enabled to recursively resolve the | |
2789 | overlay index nexthop and install the prefix into zebra. | |
2790 | ||
2791 | .. index:: enable-resolve-overlay-index | |
2792 | .. clicmd:: [no] enable-resolve-overlay-index | |
2793 | ||
2794 | Example configuration: | |
2795 | ||
2796 | .. code-block:: frr | |
2797 | ||
2798 | router bgp 65001 | |
2799 | bgp router-id 192.168.100.1 | |
2800 | no bgp ebgp-requires-policy | |
2801 | neighbor 10.0.1.2 remote-as 65002 | |
2802 | ! | |
2803 | address-family l2vpn evpn | |
2804 | neighbor 10.0.1.2 activate | |
2805 | advertise-all-vni | |
2806 | enable-resolve-overlay-index | |
2807 | exit-address-family | |
2808 | ! | |
2809 | ||
77457939 AK |
2810 | EVPN Multihoming |
2811 | ^^^^^^^^^^^^^^^^ | |
2812 | ||
2813 | All-Active Multihoming is used for redundancy and load sharing. Servers | |
2814 | are attached to two or more PEs and the links are bonded (link-aggregation). | |
2815 | This group of server links is referred to as an Ethernet Segment. | |
2816 | ||
2817 | Ethernet Segments | |
2818 | """"""""""""""""" | |
2819 | An Ethernet Segment can be configured by specifying a system-MAC and a | |
2820 | local discriminatior against the bond interface on the PE (via zebra) - | |
2821 | ||
03750f1e | 2822 | .. clicmd:: evpn mh es-id (1-16777215) |
77457939 | 2823 | |
03750f1e | 2824 | .. clicmd:: evpn mh es-sys-mac X:X:X:X:X:X |
77457939 AK |
2825 | |
2826 | The sys-mac and local discriminator are used for generating a 10-byte, | |
2827 | Type-3 Ethernet Segment ID. | |
2828 | ||
2829 | Type-1 (EAS-per-ES and EAD-per-EVI) routes are used to advertise the locally | |
2830 | attached ESs and to learn off remote ESs in the network. Local Type-2/MAC-IP | |
2831 | routes are also advertised with a destination ESI allowing for MAC-IP syncing | |
2832 | between Ethernet Segment peers. | |
2833 | Reference: RFC 7432, RFC 8365 | |
2834 | ||
2835 | EVPN-MH is intended as a replacement for MLAG or Anycast VTEPs. In | |
2836 | multihoming each PE has an unique VTEP address which requires the introduction | |
2837 | of a new dataplane construct, MAC-ECMP. Here a MAC/FDB entry can point to a | |
2838 | list of remote PEs/VTEPs. | |
2839 | ||
2840 | BUM handling | |
2841 | """""""""""" | |
2842 | Type-4 (ESR) routes are used for Designated Forwarder (DF) election. DFs | |
2843 | forward BUM traffic received via the overlay network. This implementation | |
2844 | uses a preference based DF election specified by draft-ietf-bess-evpn-pref-df. | |
2845 | The DF preference is configurable per-ES (via zebra) - | |
2846 | ||
03750f1e | 2847 | .. clicmd:: evpn mh es-df-pref (1-16777215) |
77457939 AK |
2848 | |
2849 | BUM traffic is rxed via the overlay by all PEs attached to a server but | |
2850 | only the DF can forward the de-capsulated traffic to the access port. To | |
2851 | accomodate that non-DF filters are installed in the dataplane to drop | |
2852 | the traffic. | |
2853 | ||
2854 | Similarly traffic received from ES peers via the overlay cannot be forwarded | |
2855 | to the server. This is split-horizon-filtering with local bias. | |
2856 | ||
fe8293c3 AK |
2857 | Knobs for interop |
2858 | """"""""""""""""" | |
2859 | Some vendors do not send EAD-per-EVI routes. To interop with them we | |
2860 | need to relax the dependency on EAD-per-EVI routes and activate a remote | |
2861 | ES-PE based on just the EAD-per-ES route. | |
2862 | ||
2863 | Note that by default we advertise and expect EAD-per-EVI routes. | |
2864 | ||
03750f1e | 2865 | .. clicmd:: disable-ead-evi-rx |
fe8293c3 | 2866 | |
03750f1e | 2867 | .. clicmd:: disable-ead-evi-tx |
fe8293c3 | 2868 | |
77457939 AK |
2869 | Fast failover |
2870 | """"""""""""" | |
2871 | As the primary purpose of EVPN-MH is redundancy keeping the failover efficient | |
2872 | is a recurring theme in the implementation. Following sub-features have | |
2873 | been introduced for the express purpose of efficient ES failovers. | |
2874 | ||
2875 | - Layer-2 Nexthop Groups and MAC-ECMP via L2NHG. | |
2876 | ||
2877 | - Host routes (for symmetric IRB) via L3NHG. | |
2878 | On dataplanes that support layer3 nexthop groups the feature can be turned | |
2879 | on via the following BGP config - | |
2880 | ||
03750f1e | 2881 | .. clicmd:: use-es-l3nhg |
77457939 AK |
2882 | |
2883 | - Local ES (MAC/Neigh) failover via ES-redirect. | |
2884 | On dataplanes that do not have support for ES-redirect the feature can be | |
2885 | turned off via the following zebra config - | |
2886 | ||
03750f1e | 2887 | .. clicmd:: evpn mh redirect-off |
77457939 AK |
2888 | |
2889 | Uplink/Core tracking | |
2890 | """""""""""""""""""" | |
2891 | When all the underlay links go down the PE no longer has access to the VxLAN | |
2892 | +overlay. To prevent blackholing of traffic the server/ES links are | |
2893 | protodowned on the PE. A link can be setup for uplink tracking via the | |
2894 | following zebra configuration - | |
2895 | ||
03750f1e | 2896 | .. clicmd:: evpn mh uplink |
77457939 AK |
2897 | |
2898 | Proxy advertisements | |
2899 | """""""""""""""""""" | |
2900 | To handle hitless upgrades support for proxy advertisement has been added | |
2901 | as specified by draft-rbickhart-evpn-ip-mac-proxy-adv. This allows a PE | |
2902 | (say PE1) to proxy advertise a MAC-IP rxed from an ES peer (say PE2). When | |
2903 | the ES peer (PE2) goes down PE1 continues to advertise hosts learnt from PE2 | |
2904 | for a holdtime during which it attempts to establish local reachability of | |
2905 | the host. This holdtime is configurable via the following zebra commands - | |
2906 | ||
03750f1e | 2907 | .. clicmd:: evpn mh neigh-holdtime (0-86400) |
77457939 | 2908 | |
03750f1e | 2909 | .. clicmd:: evpn mh mac-holdtime (0-86400) |
77457939 AK |
2910 | |
2911 | Startup delay | |
2912 | """"""""""""" | |
2913 | When a switch is rebooted we wait for a brief period to allow the underlay | |
2914 | and EVPN network to converge before enabling the ESs. For this duration the | |
2915 | ES bonds are held protodown. The startup delay is configurable via the | |
2916 | following zebra command - | |
2917 | ||
03750f1e | 2918 | .. clicmd:: evpn mh startup-delay (0-3600) |
77457939 | 2919 | |
ee9d0f09 PG |
2920 | +Support with VRF network namespace backend |
2921 | +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
2922 | It is possible to separate overlay networks contained in VXLAN interfaces from | |
2923 | underlay networks by using VRFs. VRF-lite and VRF-netns backends can be used for | |
2924 | that. In the latter case, it is necessary to set both bridge and vxlan interface | |
2925 | in the same network namespace, as below example illustrates: | |
2926 | ||
2927 | .. code-block:: shell | |
2928 | ||
2929 | # linux shell | |
2930 | ip netns add vrf1 | |
2931 | ip link add name vxlan101 type vxlan id 101 dstport 4789 dev eth0 local 10.1.1.1 | |
2932 | ip link set dev vxlan101 netns vrf1 | |
2933 | ip netns exec vrf1 ip link set dev lo up | |
2934 | ip netns exec vrf1 brctl addbr bridge101 | |
2935 | ip netns exec vrf1 brctl addif bridge101 vxlan101 | |
2936 | ||
2937 | This makes it possible to separate not only layer 3 networks like VRF-lite networks. | |
2938 | Also, VRF netns based make possible to separate layer 2 networks on separate VRF | |
2939 | instances. | |
89b97c33 | 2940 | |
7f7940e6 MK |
2941 | .. _bgp-conditional-advertisement: |
2942 | ||
2943 | BGP Conditional Advertisement | |
2944 | ----------------------------- | |
2945 | The BGP conditional advertisement feature uses the ``non-exist-map`` or the | |
2946 | ``exist-map`` and the ``advertise-map`` keywords of the neighbor advertise-map | |
2947 | command in order to track routes by the route prefix. | |
2948 | ||
2949 | ``non-exist-map`` | |
2950 | 1. If a route prefix is not present in the output of non-exist-map command, | |
2951 | then advertise the route specified by the advertise-map command. | |
2952 | ||
2953 | 2. If a route prefix is present in the output of non-exist-map command, | |
2954 | then do not advertise the route specified by the addvertise-map command. | |
2955 | ||
2956 | ``exist-map`` | |
2957 | 1. If a route prefix is present in the output of exist-map command, | |
2958 | then advertise the route specified by the advertise-map command. | |
2959 | ||
2960 | 2. If a route prefix is not present in the output of exist-map command, | |
2961 | then do not advertise the route specified by the advertise-map command. | |
2962 | ||
2963 | This feature is useful when some prefixes are advertised to one of its peers | |
2964 | only if the information from the other peer is not present (due to failure in | |
2965 | peering session or partial reachability etc). | |
2966 | ||
2967 | The conditional BGP announcements are sent in addition to the normal | |
2968 | announcements that a BGP router sends to its peer. | |
2969 | ||
2970 | The conditional advertisement process is triggered by the BGP scanner process, | |
2971 | which runs every 60 seconds. This means that the maximum time for the conditional | |
2972 | advertisement to take effect is 60 seconds. The conditional advertisement can take | |
2973 | effect depending on when the tracked route is removed from the BGP table and | |
2974 | when the next instance of the BGP scanner occurs. | |
2975 | ||
03750f1e | 2976 | .. clicmd:: neighbor A.B.C.D advertise-map NAME [exist-map|non-exist-map] NAME |
7f7940e6 | 2977 | |
fa36596c | 2978 | This command enables BGP scanner process to monitor routes specified by |
7f7940e6 | 2979 | exist-map or non-exist-map command in BGP table and conditionally advertises |
fa36596c | 2980 | the routes specified by advertise-map command. |
7f7940e6 MK |
2981 | |
2982 | Sample Configuration | |
2983 | ^^^^^^^^^^^^^^^^^^^^^ | |
2984 | .. code-block:: frr | |
2985 | ||
fa36596c MK |
2986 | interface enp0s9 |
2987 | ip address 10.10.10.2/24 | |
2988 | ! | |
2989 | interface enp0s10 | |
2990 | ip address 10.10.20.2/24 | |
2991 | ! | |
7f7940e6 | 2992 | interface lo |
fa36596c | 2993 | ip address 203.0.113.1/32 |
7f7940e6 MK |
2994 | ! |
2995 | router bgp 2 | |
2996 | bgp log-neighbor-changes | |
2997 | no bgp ebgp-requires-policy | |
2998 | neighbor 10.10.10.1 remote-as 1 | |
2999 | neighbor 10.10.20.3 remote-as 3 | |
3000 | ! | |
3001 | address-family ipv4 unicast | |
7f7940e6 | 3002 | neighbor 10.10.10.1 soft-reconfiguration inbound |
7f7940e6 | 3003 | neighbor 10.10.20.3 soft-reconfiguration inbound |
fa36596c | 3004 | neighbor 10.10.20.3 advertise-map ADV-MAP non-exist-map EXIST-MAP |
7f7940e6 MK |
3005 | exit-address-family |
3006 | ! | |
fa36596c MK |
3007 | ip prefix-list DEFAULT seq 5 permit 192.0.2.5/32 |
3008 | ip prefix-list DEFAULT seq 10 permit 192.0.2.1/32 | |
3009 | ip prefix-list EXIST seq 5 permit 10.10.10.10/32 | |
3010 | ip prefix-list DEFAULT-ROUTE seq 5 permit 0.0.0.0/0 | |
3011 | ip prefix-list IP1 seq 5 permit 10.139.224.0/20 | |
3012 | ! | |
3013 | bgp community-list standard DC-ROUTES seq 5 permit 64952:3008 | |
3014 | bgp community-list standard DC-ROUTES seq 10 permit 64671:501 | |
3015 | bgp community-list standard DC-ROUTES seq 15 permit 64950:3009 | |
3016 | bgp community-list standard DEFAULT-ROUTE seq 5 permit 65013:200 | |
7f7940e6 | 3017 | ! |
fa36596c MK |
3018 | route-map ADV-MAP permit 10 |
3019 | match ip address prefix-list IP1 | |
7f7940e6 | 3020 | ! |
fa36596c MK |
3021 | route-map ADV-MAP permit 20 |
3022 | match community DC-ROUTES | |
3023 | ! | |
3024 | route-map EXIST-MAP permit 10 | |
3025 | match community DEFAULT-ROUTE | |
3026 | match ip address prefix-list DEFAULT-ROUTE | |
7f7940e6 MK |
3027 | ! |
3028 | ||
3029 | Sample Output | |
3030 | ^^^^^^^^^^^^^ | |
3031 | ||
fa36596c | 3032 | When default route is present in R2'2 BGP table, 10.139.224.0/20 and 192.0.2.1/32 are not advertised to R3. |
7f7940e6 MK |
3033 | |
3034 | .. code-block:: frr | |
3035 | ||
3036 | Router2# show ip bgp | |
fa36596c | 3037 | BGP table version is 20, local router ID is 203.0.113.1, vrf id 0 |
7f7940e6 MK |
3038 | Default local pref 100, local AS 2 |
3039 | Status codes: s suppressed, d damped, h history, * valid, > best, = multipath, | |
3040 | i internal, r RIB-failure, S Stale, R Removed | |
3041 | Nexthop codes: @NNN nexthop's vrf id, < announce-nh-self | |
3042 | Origin codes: i - IGP, e - EGP, ? - incomplete | |
0bcfc1a3 | 3043 | RPKI validation codes: V valid, I invalid, N Not found |
7f7940e6 | 3044 | |
fa36596c MK |
3045 | Network Next Hop Metric LocPrf Weight Path |
3046 | *> 0.0.0.0/0 10.10.10.1 0 0 1 i | |
3047 | *> 10.139.224.0/20 10.10.10.1 0 0 1 ? | |
3048 | *> 192.0.2.1/32 10.10.10.1 0 0 1 i | |
3049 | *> 192.0.2.5/32 10.10.10.1 0 0 1 i | |
7f7940e6 MK |
3050 | |
3051 | Displayed 4 routes and 4 total paths | |
fa36596c | 3052 | Router2# show ip bgp neighbors 10.10.20.3 |
7f7940e6 MK |
3053 | |
3054 | !--- Output suppressed. | |
3055 | ||
3056 | For address family: IPv4 Unicast | |
fa36596c | 3057 | Update group 7, subgroup 7 |
7f7940e6 MK |
3058 | Packet Queue length 0 |
3059 | Inbound soft reconfiguration allowed | |
3060 | Community attribute sent to this neighbor(all) | |
fa36596c MK |
3061 | Condition NON_EXIST, Condition-map *EXIST-MAP, Advertise-map *ADV-MAP, status: Withdraw |
3062 | 0 accepted prefixes | |
7f7940e6 MK |
3063 | |
3064 | !--- Output suppressed. | |
3065 | ||
fa36596c MK |
3066 | Router2# show ip bgp neighbors 10.10.20.3 advertised-routes |
3067 | BGP table version is 20, local router ID is 203.0.113.1, vrf id 0 | |
7f7940e6 MK |
3068 | Default local pref 100, local AS 2 |
3069 | Status codes: s suppressed, d damped, h history, * valid, > best, = multipath, | |
fa36596c | 3070 | i internal, r RIB-failure, S Stale, R Removed |
7f7940e6 MK |
3071 | Nexthop codes: @NNN nexthop's vrf id, < announce-nh-self |
3072 | Origin codes: i - IGP, e - EGP, ? - incomplete | |
0bcfc1a3 | 3073 | RPKI validation codes: V valid, I invalid, N Not found |
7f7940e6 | 3074 | |
fa36596c MK |
3075 | Network Next Hop Metric LocPrf Weight Path |
3076 | *> 0.0.0.0/0 0.0.0.0 0 1 i | |
3077 | *> 192.0.2.5/32 0.0.0.0 0 1 i | |
7f7940e6 | 3078 | |
fa36596c | 3079 | Total number of prefixes 2 |
7f7940e6 | 3080 | |
fa36596c | 3081 | When default route is not present in R2'2 BGP table, 10.139.224.0/20 and 192.0.2.1/32 are advertised to R3. |
7f7940e6 MK |
3082 | |
3083 | .. code-block:: frr | |
3084 | ||
3085 | Router2# show ip bgp | |
fa36596c | 3086 | BGP table version is 21, local router ID is 203.0.113.1, vrf id 0 |
7f7940e6 MK |
3087 | Default local pref 100, local AS 2 |
3088 | Status codes: s suppressed, d damped, h history, * valid, > best, = multipath, | |
3089 | i internal, r RIB-failure, S Stale, R Removed | |
3090 | Nexthop codes: @NNN nexthop's vrf id, < announce-nh-self | |
3091 | Origin codes: i - IGP, e - EGP, ? - incomplete | |
0bcfc1a3 | 3092 | RPKI validation codes: V valid, I invalid, N Not found |
7f7940e6 | 3093 | |
fa36596c MK |
3094 | Network Next Hop Metric LocPrf Weight Path |
3095 | *> 10.139.224.0/20 10.10.10.1 0 0 1 ? | |
3096 | *> 192.0.2.1/32 10.10.10.1 0 0 1 i | |
3097 | *> 192.0.2.5/32 10.10.10.1 0 0 1 i | |
7f7940e6 MK |
3098 | |
3099 | Displayed 3 routes and 3 total paths | |
7f7940e6 | 3100 | |
fa36596c | 3101 | Router2# show ip bgp neighbors 10.10.20.3 |
7f7940e6 MK |
3102 | |
3103 | !--- Output suppressed. | |
3104 | ||
3105 | For address family: IPv4 Unicast | |
fa36596c | 3106 | Update group 7, subgroup 7 |
7f7940e6 MK |
3107 | Packet Queue length 0 |
3108 | Inbound soft reconfiguration allowed | |
3109 | Community attribute sent to this neighbor(all) | |
fa36596c MK |
3110 | Condition NON_EXIST, Condition-map *EXIST-MAP, Advertise-map *ADV-MAP, status: Advertise |
3111 | 0 accepted prefixes | |
7f7940e6 MK |
3112 | |
3113 | !--- Output suppressed. | |
3114 | ||
fa36596c MK |
3115 | Router2# show ip bgp neighbors 10.10.20.3 advertised-routes |
3116 | BGP table version is 21, local router ID is 203.0.113.1, vrf id 0 | |
7f7940e6 MK |
3117 | Default local pref 100, local AS 2 |
3118 | Status codes: s suppressed, d damped, h history, * valid, > best, = multipath, | |
3119 | i internal, r RIB-failure, S Stale, R Removed | |
3120 | Nexthop codes: @NNN nexthop's vrf id, < announce-nh-self | |
3121 | Origin codes: i - IGP, e - EGP, ? - incomplete | |
0bcfc1a3 | 3122 | RPKI validation codes: V valid, I invalid, N Not found |
7f7940e6 | 3123 | |
fa36596c MK |
3124 | Network Next Hop Metric LocPrf Weight Path |
3125 | *> 10.139.224.0/20 0.0.0.0 0 1 ? | |
3126 | *> 192.0.2.1/32 0.0.0.0 0 1 i | |
3127 | *> 192.0.2.5/32 0.0.0.0 0 1 i | |
7f7940e6 MK |
3128 | |
3129 | Total number of prefixes 3 | |
fa36596c | 3130 | Router2# |
7f7940e6 | 3131 | |
8fcedbd2 QY |
3132 | .. _bgp-debugging: |
3133 | ||
3134 | Debugging | |
3135 | --------- | |
42fc5d26 | 3136 | |
29adcd50 | 3137 | .. clicmd:: show debug |
42fc5d26 | 3138 | |
8fcedbd2 | 3139 | Show all enabled debugs. |
42fc5d26 | 3140 | |
54422b46 DS |
3141 | .. clicmd:: show bgp listeners |
3142 | ||
3143 | Display Listen sockets and the vrf that created them. Useful for debugging of when | |
3144 | listen is not working and this is considered a developer debug statement. | |
3145 | ||
81313f43 RZ |
3146 | .. clicmd:: debug bgp bfd |
3147 | ||
3148 | Enable or disable debugging for BFD events. This will show BFD integration | |
3149 | library messages and BGP BFD integration messages that are mostly state | |
3150 | transitions and validation problems. | |
3151 | ||
03750f1e | 3152 | .. clicmd:: debug bgp neighbor-events |
42fc5d26 | 3153 | |
8fcedbd2 QY |
3154 | Enable or disable debugging for neighbor events. This provides general |
3155 | information on BGP events such as peer connection / disconnection, session | |
3156 | establishment / teardown, and capability negotiation. | |
42fc5d26 | 3157 | |
03750f1e | 3158 | .. clicmd:: debug bgp updates |
42fc5d26 | 3159 | |
8fcedbd2 QY |
3160 | Enable or disable debugging for BGP updates. This provides information on |
3161 | BGP UPDATE messages transmitted and received between local and remote | |
3162 | instances. | |
42fc5d26 | 3163 | |
03750f1e | 3164 | .. clicmd:: debug bgp keepalives |
42fc5d26 | 3165 | |
8fcedbd2 QY |
3166 | Enable or disable debugging for BGP keepalives. This provides information on |
3167 | BGP KEEPALIVE messages transmitted and received between local and remote | |
3168 | instances. | |
c1a54c05 | 3169 | |
03750f1e | 3170 | .. clicmd:: debug bgp bestpath <A.B.C.D/M|X:X::X:X/M> |
42fc5d26 | 3171 | |
8fcedbd2 | 3172 | Enable or disable debugging for bestpath selection on the specified prefix. |
42fc5d26 | 3173 | |
03750f1e | 3174 | .. clicmd:: debug bgp nht |
4da7fda3 | 3175 | |
8fcedbd2 | 3176 | Enable or disable debugging of BGP nexthop tracking. |
4da7fda3 | 3177 | |
03750f1e | 3178 | .. clicmd:: debug bgp update-groups |
4b44467c | 3179 | |
8fcedbd2 QY |
3180 | Enable or disable debugging of dynamic update groups. This provides general |
3181 | information on group creation, deletion, join and prune events. | |
4b44467c | 3182 | |
03750f1e | 3183 | .. clicmd:: debug bgp zebra |
42fc5d26 | 3184 | |
8fcedbd2 | 3185 | Enable or disable debugging of communications between *bgpd* and *zebra*. |
c3c5a71f | 3186 | |
8fcedbd2 QY |
3187 | Dumping Messages and Routing Tables |
3188 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
42fc5d26 | 3189 | |
8fcedbd2 | 3190 | .. clicmd:: dump bgp all PATH [INTERVAL] |
42fc5d26 | 3191 | |
8fcedbd2 | 3192 | .. clicmd:: dump bgp all-et PATH [INTERVAL] |
c3c5a71f | 3193 | |
42fc5d26 | 3194 | |
8fcedbd2 QY |
3195 | Dump all BGP packet and events to `path` file. |
3196 | If `interval` is set, a new file will be created for echo `interval` of | |
3197 | seconds. The path `path` can be set with date and time formatting | |
3198 | (strftime). The type ‘all-et’ enables support for Extended Timestamp Header | |
3199 | (:ref:`packet-binary-dump-format`). | |
c3c5a71f | 3200 | |
8fcedbd2 | 3201 | .. clicmd:: dump bgp updates PATH [INTERVAL] |
42fc5d26 | 3202 | |
8fcedbd2 | 3203 | .. clicmd:: dump bgp updates-et PATH [INTERVAL] |
42fc5d26 | 3204 | |
42fc5d26 | 3205 | |
8fcedbd2 QY |
3206 | Dump only BGP updates messages to `path` file. |
3207 | If `interval` is set, a new file will be created for echo `interval` of | |
3208 | seconds. The path `path` can be set with date and time formatting | |
3209 | (strftime). The type ‘updates-et’ enables support for Extended Timestamp | |
3210 | Header (:ref:`packet-binary-dump-format`). | |
42fc5d26 | 3211 | |
8fcedbd2 | 3212 | .. clicmd:: dump bgp routes-mrt PATH |
c3c5a71f | 3213 | |
8fcedbd2 | 3214 | .. clicmd:: dump bgp routes-mrt PATH INTERVAL |
42fc5d26 | 3215 | |
42fc5d26 | 3216 | |
8fcedbd2 QY |
3217 | Dump whole BGP routing table to `path`. This is heavy process. The path |
3218 | `path` can be set with date and time formatting (strftime). If `interval` is | |
3219 | set, a new file will be created for echo `interval` of seconds. | |
42fc5d26 | 3220 | |
8fcedbd2 | 3221 | Note: the interval variable can also be set using hours and minutes: 04h20m00. |
42fc5d26 | 3222 | |
c3c5a71f | 3223 | |
8fcedbd2 | 3224 | .. _bgp-other-commands: |
42fc5d26 | 3225 | |
8fcedbd2 QY |
3226 | Other BGP Commands |
3227 | ------------------ | |
42fc5d26 | 3228 | |
e312b6c6 QY |
3229 | The following are available in the top level *enable* mode: |
3230 | ||
dc912615 DS |
3231 | .. clicmd:: clear bgp \* |
3232 | ||
3233 | Clear all peers. | |
3234 | ||
8fcedbd2 | 3235 | .. clicmd:: clear bgp ipv4|ipv6 \* |
42fc5d26 | 3236 | |
dc912615 DS |
3237 | Clear all peers with this address-family activated. |
3238 | ||
dc912615 DS |
3239 | .. clicmd:: clear bgp ipv4|ipv6 unicast \* |
3240 | ||
3241 | Clear all peers with this address-family and sub-address-family activated. | |
42fc5d26 | 3242 | |
8fcedbd2 | 3243 | .. clicmd:: clear bgp ipv4|ipv6 PEER |
42fc5d26 | 3244 | |
dc912615 DS |
3245 | Clear peers with address of X.X.X.X and this address-family activated. |
3246 | ||
dc912615 DS |
3247 | .. clicmd:: clear bgp ipv4|ipv6 unicast PEER |
3248 | ||
3249 | Clear peer with address of X.X.X.X and this address-family and sub-address-family activated. | |
3250 | ||
dc912615 DS |
3251 | .. clicmd:: clear bgp ipv4|ipv6 PEER soft|in|out |
3252 | ||
3253 | Clear peer using soft reconfiguration in this address-family. | |
42fc5d26 | 3254 | |
dc912615 | 3255 | .. clicmd:: clear bgp ipv4|ipv6 unicast PEER soft|in|out |
42fc5d26 | 3256 | |
dc912615 | 3257 | Clear peer using soft reconfiguration in this address-family and sub-address-family. |
42fc5d26 | 3258 | |
e312b6c6 QY |
3259 | The following are available in the ``router bgp`` mode: |
3260 | ||
e312b6c6 QY |
3261 | .. clicmd:: write-quanta (1-64) |
3262 | ||
3263 | BGP message Tx I/O is vectored. This means that multiple packets are written | |
3264 | to the peer socket at the same time each I/O cycle, in order to minimize | |
3265 | system call overhead. This value controls how many are written at a time. | |
3266 | Under certain load conditions, reducing this value could make peer traffic | |
3267 | less 'bursty'. In practice, leave this settings on the default (64) unless | |
3268 | you truly know what you are doing. | |
3269 | ||
dad83b67 | 3270 | .. clicmd:: read-quanta (1-10) |
e312b6c6 QY |
3271 | |
3272 | Unlike Tx, BGP Rx traffic is not vectored. Packets are read off the wire one | |
3273 | at a time in a loop. This setting controls how many iterations the loop runs | |
3274 | for. As with write-quanta, it is best to leave this setting on the default. | |
42fc5d26 | 3275 | |
05bd726c | 3276 | The following command is available in ``config`` mode as well as in the |
3277 | ``router bgp`` mode: | |
3278 | ||
05bd726c | 3279 | .. clicmd:: bgp graceful-shutdown |
3280 | ||
3281 | The purpose of this command is to initiate BGP Graceful Shutdown which | |
3282 | is described in :rfc:`8326`. The use case for this is to minimize or | |
3283 | eliminate the amount of traffic loss in a network when a planned | |
3284 | maintenance activity such as software upgrade or hardware replacement | |
3285 | is to be performed on a router. The feature works by re-announcing | |
3286 | routes to eBGP peers with the GRACEFUL_SHUTDOWN community included. | |
3287 | Peers are then expected to treat such paths with the lowest preference. | |
3288 | This happens automatically on a receiver running FRR; with other | |
3289 | routing protocol stacks, an inbound policy may have to be configured. | |
3290 | In FRR, triggering graceful shutdown also results in announcing a | |
3291 | LOCAL_PREF of 0 to iBGP peers. | |
3292 | ||
3293 | Graceful shutdown can be configured per BGP instance or globally for | |
3294 | all of BGP. These two options are mutually exclusive. The no form of | |
3295 | the command causes graceful shutdown to be stopped, and routes will | |
3296 | be re-announced without the GRACEFUL_SHUTDOWN community and/or with | |
3297 | the usual LOCAL_PREF value. Note that if this option is saved to | |
3298 | the startup configuration, graceful shutdown will remain in effect | |
3299 | across restarts of *bgpd* and will need to be explicitly disabled. | |
3300 | ||
8fcedbd2 | 3301 | .. _bgp-displaying-bgp-information: |
42fc5d26 | 3302 | |
8fcedbd2 QY |
3303 | Displaying BGP Information |
3304 | ========================== | |
42fc5d26 | 3305 | |
e6f59415 PG |
3306 | The following four commands display the IPv6 and IPv4 routing tables, depending |
3307 | on whether or not the ``ip`` keyword is used. | |
3308 | Actually, :clicmd:`show ip bgp` command was used on older `Quagga` routing | |
3309 | daemon project, while :clicmd:`show bgp` command is the new format. The choice | |
3310 | has been done to keep old format with IPv4 routing table, while new format | |
3311 | displays IPv6 routing table. | |
3312 | ||
4c92d818 | 3313 | .. clicmd:: show ip bgp [all] [wide|json [detail]] |
42fc5d26 | 3314 | |
96f3485c | 3315 | .. clicmd:: show ip bgp A.B.C.D [json] |
c1a54c05 | 3316 | |
4c92d818 | 3317 | .. clicmd:: show bgp [all] [wide|json [detail]] |
e6f59415 | 3318 | |
96f3485c | 3319 | .. clicmd:: show bgp X:X::X:X [json] |
42fc5d26 | 3320 | |
8fcedbd2 | 3321 | These commands display BGP routes. When no route is specified, the default |
e6f59415 | 3322 | is to display all BGP routes. |
42fc5d26 | 3323 | |
8fcedbd2 | 3324 | :: |
c1a54c05 | 3325 | |
8fcedbd2 QY |
3326 | BGP table version is 0, local router ID is 10.1.1.1 |
3327 | Status codes: s suppressed, d damped, h history, * valid, > best, i - internal | |
3328 | Origin codes: i - IGP, e - EGP, ? - incomplete | |
42fc5d26 | 3329 | |
8fcedbd2 QY |
3330 | Network Next Hop Metric LocPrf Weight Path |
3331 | \*> 1.1.1.1/32 0.0.0.0 0 32768 i | |
42fc5d26 | 3332 | |
8fcedbd2 | 3333 | Total number of prefixes 1 |
4da7fda3 | 3334 | |
56c07345 | 3335 | If ``wide`` option is specified, then the prefix table's width is increased |
986b0fc3 DA |
3336 | to fully display the prefix and the nexthop. |
3337 | ||
3338 | This is especially handy dealing with IPv6 prefixes and | |
3339 | if :clicmd:`[no] bgp default show-nexthop-hostname` is enabled. | |
3340 | ||
56c07345 | 3341 | If ``all`` option is specified, ``ip`` keyword is ignored, show bgp all and |
96f3485c MK |
3342 | show ip bgp all commands display routes for all AFIs and SAFIs. |
3343 | ||
56c07345 | 3344 | If ``json`` option is specified, output is displayed in JSON format. |
96f3485c | 3345 | |
4c92d818 DA |
3346 | If ``detail`` option is specified after ``json``, more verbose JSON output |
3347 | will be displayed. | |
3348 | ||
e6f59415 PG |
3349 | Some other commands provide additional options for filtering the output. |
3350 | ||
e6f59415 | 3351 | .. clicmd:: show [ip] bgp regexp LINE |
42fc5d26 | 3352 | |
8fcedbd2 QY |
3353 | This command displays BGP routes using AS path regular expression |
3354 | (:ref:`bgp-regular-expressions`). | |
42fc5d26 | 3355 | |
28b25b6b | 3356 | .. clicmd:: show [ip] bgp [all] summary [wide] [json] |
42fc5d26 | 3357 | |
8fcedbd2 | 3358 | Show a bgp peer summary for the specified address family. |
42fc5d26 | 3359 | |
e6f59415 PG |
3360 | The old command structure :clicmd:`show ip bgp` may be removed in the future |
3361 | and should no longer be used. In order to reach the other BGP routing tables | |
3362 | other than the IPv6 routing table given by :clicmd:`show bgp`, the new command | |
3363 | structure is extended with :clicmd:`show bgp [afi] [safi]`. | |
3364 | ||
28b25b6b DA |
3365 | ``wide`` option gives more output like ``LocalAS`` and extended ``Desc`` to |
3366 | 64 characters. | |
3367 | ||
3368 | .. code-block:: frr | |
3369 | ||
3370 | exit1# show ip bgp summary wide | |
3371 | ||
6cac2fcc | 3372 | IPv4 Unicast Summary (VRF default): |
28b25b6b DA |
3373 | BGP router identifier 192.168.100.1, local AS number 65534 vrf-id 0 |
3374 | BGP table version 3 | |
3375 | RIB entries 5, using 920 bytes of memory | |
3376 | Peers 1, using 27 KiB of memory | |
3377 | ||
3378 | Neighbor V AS LocalAS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd PfxSnt Desc | |
3379 | 192.168.0.2 4 65030 123 15 22 0 0 0 00:07:00 0 1 us-east1-rs1.frrouting.org | |
3380 | ||
3381 | Total number of neighbors 1 | |
3382 | exit1# | |
3383 | ||
96f3485c | 3384 | .. clicmd:: show bgp [afi] [safi] [all] [wide|json] |
e6f59415 | 3385 | |
22bfb2a6 | 3386 | .. clicmd:: show bgp [<ipv4|ipv6> <unicast|multicast|vpn|labeled-unicast|flowspec> | l2vpn evpn] |
e6f59415 PG |
3387 | |
3388 | These commands display BGP routes for the specific routing table indicated by | |
3389 | the selected afi and the selected safi. If no afi and no safi value is given, | |
6cfd16ad | 3390 | the command falls back to the default IPv6 routing table. |
6cfd16ad | 3391 | |
6cfd16ad TA |
3392 | .. clicmd:: show bgp l2vpn evpn route [type <macip|2|multicast|3|es|4|prefix|5>] |
3393 | ||
22bfb2a6 | 3394 | EVPN prefixes can also be filtered by EVPN route type. |
e6f59415 | 3395 | |
96f3485c | 3396 | .. clicmd:: show bgp [afi] [safi] [all] summary [json] |
e6f59415 PG |
3397 | |
3398 | Show a bgp peer summary for the specified address family, and subsequent | |
3399 | address-family. | |
3400 | ||
96f3485c | 3401 | .. clicmd:: show bgp [afi] [safi] [all] summary failed [json] |
3577f1c5 DD |
3402 | |
3403 | Show a bgp peer summary for peers that are not succesfully exchanging routes | |
3404 | for the specified address family, and subsequent address-family. | |
3405 | ||
96f3485c | 3406 | .. clicmd:: show bgp [afi] [safi] [all] summary established [json] |
1c027267 DA |
3407 | |
3408 | Show a bgp peer summary for peers that are succesfully exchanging routes | |
3409 | for the specified address family, and subsequent address-family. | |
3410 | ||
8c1d4cd5 LS |
3411 | .. clicmd:: show bgp [afi] [safi] [all] summary neighbor [PEER] [json] |
3412 | ||
3413 | Show a bgp summary for the specified peer, address family, and | |
3414 | subsequent address-family. The neighbor filter can be used in combination | |
3415 | with the failed, established filters. | |
3416 | ||
3417 | .. clicmd:: show bgp [afi] [safi] [all] summary remote-as <internal|external|ASN> [json] | |
3418 | ||
3419 | Show a bgp peer summary for the specified remote-as ASN or type (``internal`` | |
3420 | for iBGP and ``external`` for eBGP sessions), address family, and subsequent | |
3421 | address-family. The remote-as filter can be used in combination with the | |
3422 | failed, established filters. | |
3423 | ||
96c81f66 LS |
3424 | .. clicmd:: show bgp [afi] [safi] [all] summary terse [json] |
3425 | ||
3426 | Shorten the output. Do not show the following information about the BGP | |
3427 | instances: the number of RIB entries, the table version and the used memory. | |
3428 | The ``terse`` option can be used in combination with the remote-as, neighbor, | |
3429 | failed and established filters, and with the ``wide`` option as well. | |
3430 | ||
22bfb2a6 | 3431 | .. clicmd:: show bgp [afi] [safi] [neighbor [PEER] [routes|advertised-routes|received-routes] [json] |
9eb95b3b | 3432 | |
e6f59415 PG |
3433 | This command shows information on a specific BGP peer of the relevant |
3434 | afi and safi selected. | |
c1a54c05 | 3435 | |
22bfb2a6 TA |
3436 | The ``routes`` keyword displays only routes in this address-family's BGP |
3437 | table that were received by this peer and accepted by inbound policy. | |
3438 | ||
3439 | The ``advertised-routes`` keyword displays only the routes in this | |
3440 | address-family's BGP table that were permitted by outbound policy and | |
3441 | advertised to to this peer. | |
3442 | ||
3443 | The ``received-routes`` keyword displays all routes belonging to this | |
3444 | address-family (prior to inbound policy) that were received by this peer. | |
3445 | ||
96f3485c | 3446 | .. clicmd:: show bgp [afi] [safi] [all] dampening dampened-paths [wide|json] |
42fc5d26 | 3447 | |
e6f59415 PG |
3448 | Display paths suppressed due to dampening of the selected afi and safi |
3449 | selected. | |
42fc5d26 | 3450 | |
96f3485c | 3451 | .. clicmd:: show bgp [afi] [safi] [all] dampening flap-statistics [wide|json] |
c1a54c05 | 3452 | |
e6f59415 | 3453 | Display flap statistics of routes of the selected afi and safi selected. |
42fc5d26 | 3454 | |
244e6cab DA |
3455 | .. clicmd:: show bgp [afi] [safi] [all] version (1-4294967295) [wide|json] |
3456 | ||
3457 | Display prefixes with matching version numbers. The version number and | |
3458 | above having prefixes will be listed here. | |
3459 | ||
3460 | It helps to identify which prefixes were installed at some point. | |
3461 | ||
3462 | Here is an example of how to check what prefixes were installed starting | |
3463 | with an arbitrary version:: | |
3464 | ||
3465 | .. code-block:: frr | |
3466 | ||
3467 | ~# vtysh -c 'show bgp ipv4 unicast json' | jq '.tableVersion' | |
3468 | 9 | |
3469 | ~# vtysh -c 'show ip bgp version 9 json' | jq -r '.routes | keys[]' | |
3470 | 192.168.3.0/24 | |
3471 | ~# vtysh -c 'show ip bgp version 8 json' | jq -r '.routes | keys[]' | |
3472 | 192.168.2.0/24 | |
3473 | 192.168.3.0/24 | |
3474 | ||
620e23e8 PG |
3475 | .. clicmd:: show bgp [afi] [safi] statistics |
3476 | ||
3477 | Display statistics of routes of the selected afi and safi. | |
3478 | ||
620e23e8 PG |
3479 | .. clicmd:: show bgp statistics-all |
3480 | ||
3481 | Display statistics of routes of all the afi and safi. | |
3482 | ||
96f3485c MK |
3483 | .. clicmd:: show [ip] bgp [afi] [safi] [all] cidr-only [wide|json] |
3484 | ||
3485 | Display routes with non-natural netmasks. | |
3486 | ||
96f3485c MK |
3487 | .. clicmd:: show [ip] bgp [afi] [safi] [all] neighbors A.B.C.D [advertised-routes|received-routes|filtered-routes] [json|wide] |
3488 | ||
3489 | Display the routes advertised to a BGP neighbor or received routes | |
3490 | from neighbor or filtered routes received from neighbor based on the | |
3491 | option specified. | |
3492 | ||
56c07345 | 3493 | If ``wide`` option is specified, then the prefix table's width is increased |
96f3485c MK |
3494 | to fully display the prefix and the nexthop. |
3495 | ||
3496 | This is especially handy dealing with IPv6 prefixes and | |
3497 | if :clicmd:`[no] bgp default show-nexthop-hostname` is enabled. | |
3498 | ||
56c07345 | 3499 | If ``all`` option is specified, ``ip`` keyword is ignored and, |
96f3485c | 3500 | routes displayed for all AFIs and SAFIs. |
56c07345 | 3501 | if afi is specified, with ``all`` option, routes will be displayed for |
96f3485c MK |
3502 | each SAFI in the selcted AFI |
3503 | ||
56c07345 | 3504 | If ``json`` option is specified, output is displayed in JSON format. |
96f3485c | 3505 | |
8fcedbd2 | 3506 | .. _bgp-display-routes-by-community: |
42fc5d26 | 3507 | |
8fcedbd2 QY |
3508 | Displaying Routes by Community Attribute |
3509 | ---------------------------------------- | |
42fc5d26 | 3510 | |
8fcedbd2 QY |
3511 | The following commands allow displaying routes based on their community |
3512 | attribute. | |
42fc5d26 | 3513 | |
96f3485c | 3514 | .. clicmd:: show [ip] bgp <ipv4|ipv6> [all] community [wide|json] |
42fc5d26 | 3515 | |
96f3485c | 3516 | .. clicmd:: show [ip] bgp <ipv4|ipv6> [all] community COMMUNITY [wide|json] |
42fc5d26 | 3517 | |
96f3485c | 3518 | .. clicmd:: show [ip] bgp <ipv4|ipv6> [all] community COMMUNITY exact-match [wide|json] |
76bd1499 | 3519 | |
8fcedbd2 QY |
3520 | These commands display BGP routes which have the community attribute. |
3521 | attribute. When ``COMMUNITY`` is specified, BGP routes that match that | |
3522 | community are displayed. When `exact-match` is specified, it display only | |
3523 | routes that have an exact match. | |
c3c5a71f | 3524 | |
8fcedbd2 | 3525 | .. clicmd:: show [ip] bgp <ipv4|ipv6> community-list WORD |
42fc5d26 | 3526 | |
8fcedbd2 | 3527 | .. clicmd:: show [ip] bgp <ipv4|ipv6> community-list WORD exact-match |
42fc5d26 | 3528 | |
8fcedbd2 QY |
3529 | These commands display BGP routes for the address family specified that |
3530 | match the specified community list. When `exact-match` is specified, it | |
3531 | displays only routes that have an exact match. | |
42fc5d26 | 3532 | |
56c07345 | 3533 | If ``wide`` option is specified, then the prefix table's width is increased |
96f3485c MK |
3534 | to fully display the prefix and the nexthop. |
3535 | ||
3536 | This is especially handy dealing with IPv6 prefixes and | |
3537 | if :clicmd:`[no] bgp default show-nexthop-hostname` is enabled. | |
3538 | ||
56c07345 | 3539 | If ``all`` option is specified, ``ip`` keyword is ignored and, |
96f3485c | 3540 | routes displayed for all AFIs and SAFIs. |
56c07345 | 3541 | if afi is specified, with ``all`` option, routes will be displayed for |
96f3485c MK |
3542 | each SAFI in the selcted AFI |
3543 | ||
56c07345 | 3544 | If ``json`` option is specified, output is displayed in JSON format. |
e3ea6503 | 3545 | |
e3ea6503 PR |
3546 | .. clicmd:: show bgp labelpool <chunks|inuse|ledger|requests|summary> [json] |
3547 | ||
3548 | These commands display information about the BGP labelpool used for | |
3549 | the association of MPLS labels with routes for L3VPN and Labeled Unicast | |
3550 | ||
3551 | If ``chunks`` option is specified, output shows the current list of label | |
3552 | chunks granted to BGP by Zebra, indicating the start and end label in | |
3553 | each chunk | |
3554 | ||
3555 | If ``inuse`` option is specified, output shows the current inuse list of | |
3556 | label to prefix mappings | |
3557 | ||
3558 | If ``ledger`` option is specified, output shows ledger list of all | |
3559 | label requests made per prefix | |
3560 | ||
3561 | If ``requests`` option is specified, output shows current list of label | |
3562 | requests which have not yet been fulfilled by the labelpool | |
3563 | ||
3564 | If ``summary`` option is specified, output is a summary of the counts for | |
3565 | the chunks, inuse, ledger and requests list along with the count of | |
3566 | outstanding chunk requests to Zebra and the nummber of zebra reconnects | |
3567 | that have happened | |
3568 | ||
3569 | If ``json`` option is specified, output is displayed in JSON format. | |
96f3485c | 3570 | |
36a206db | 3571 | .. _bgp-display-routes-by-lcommunity: |
3572 | ||
3573 | Displaying Routes by Large Community Attribute | |
3574 | ---------------------------------------------- | |
3575 | ||
ac2201bb | 3576 | The following commands allow displaying routes based on their |
36a206db | 3577 | large community attribute. |
3578 | ||
36a206db | 3579 | .. clicmd:: show [ip] bgp <ipv4|ipv6> large-community |
3580 | ||
36a206db | 3581 | .. clicmd:: show [ip] bgp <ipv4|ipv6> large-community LARGE-COMMUNITY |
3582 | ||
36a206db | 3583 | .. clicmd:: show [ip] bgp <ipv4|ipv6> large-community LARGE-COMMUNITY exact-match |
3584 | ||
36a206db | 3585 | .. clicmd:: show [ip] bgp <ipv4|ipv6> large-community LARGE-COMMUNITY json |
3586 | ||
3587 | These commands display BGP routes which have the large community attribute. | |
3588 | attribute. When ``LARGE-COMMUNITY`` is specified, BGP routes that match that | |
ac2201bb DA |
3589 | large community are displayed. When `exact-match` is specified, it display |
3590 | only routes that have an exact match. When `json` is specified, it display | |
36a206db | 3591 | routes in json format. |
3592 | ||
36a206db | 3593 | .. clicmd:: show [ip] bgp <ipv4|ipv6> large-community-list WORD |
3594 | ||
36a206db | 3595 | .. clicmd:: show [ip] bgp <ipv4|ipv6> large-community-list WORD exact-match |
3596 | ||
36a206db | 3597 | .. clicmd:: show [ip] bgp <ipv4|ipv6> large-community-list WORD json |
3598 | ||
3599 | These commands display BGP routes for the address family specified that | |
ac2201bb DA |
3600 | match the specified large community list. When `exact-match` is specified, |
3601 | it displays only routes that have an exact match. When `json` is specified, | |
36a206db | 3602 | it display routes in json format. |
3603 | ||
8fcedbd2 | 3604 | .. _bgp-display-routes-by-as-path: |
42fc5d26 | 3605 | |
36a206db | 3606 | |
8fcedbd2 QY |
3607 | Displaying Routes by AS Path |
3608 | ---------------------------- | |
42fc5d26 | 3609 | |
8fcedbd2 | 3610 | .. clicmd:: show bgp ipv4|ipv6 regexp LINE |
76bd1499 | 3611 | |
8fcedbd2 QY |
3612 | This commands displays BGP routes that matches a regular |
3613 | expression `line` (:ref:`bgp-regular-expressions`). | |
3614 | ||
e6f59415 | 3615 | .. clicmd:: show [ip] bgp ipv4 vpn |
8fcedbd2 | 3616 | |
e6f59415 | 3617 | .. clicmd:: show [ip] bgp ipv6 vpn |
8fcedbd2 QY |
3618 | |
3619 | Print active IPV4 or IPV6 routes advertised via the VPN SAFI. | |
3620 | ||
8fcedbd2 QY |
3621 | .. clicmd:: show bgp ipv4 vpn summary |
3622 | ||
8fcedbd2 QY |
3623 | .. clicmd:: show bgp ipv6 vpn summary |
3624 | ||
3625 | Print a summary of neighbor connections for the specified AFI/SAFI combination. | |
3626 | ||
22bfb2a6 TA |
3627 | Displaying Routes by Route Distinguisher |
3628 | ---------------------------------------- | |
3629 | ||
3630 | .. clicmd:: show bgp [<ipv4|ipv6> vpn | l2vpn evpn [route]] rd <all|RD> | |
3631 | ||
3632 | For L3VPN and EVPN address-families, routes can be displayed on a per-RD | |
3633 | (Route Distinguisher) basis or for all RD's. | |
3634 | ||
3635 | .. clicmd:: show bgp l2vpn evpn rd <all|RD> [overlay | tags] | |
3636 | ||
3637 | Use the ``overlay`` or ``tags`` keywords to display the overlay/tag | |
3638 | information about the EVPN prefixes in the selected Route Distinguisher. | |
3639 | ||
3640 | .. clicmd:: show bgp l2vpn evpn route rd <all|RD> mac <MAC> [ip <MAC>] [json] | |
3641 | ||
3642 | For EVPN Type 2 (macip) routes, a MAC address (and optionally an IP address) | |
3643 | can be supplied to the command to only display matching prefixes in the | |
3644 | specified RD. | |
3645 | ||
09d78f10 DS |
3646 | Displaying Update Group Information |
3647 | ----------------------------------- | |
3648 | ||
6c5be52a | 3649 | .. clicmd:: show bgp update-groups [advertise-queue|advertised-routes|packet-queue] |
09d78f10 DS |
3650 | |
3651 | Display Information about each individual update-group being used. | |
3652 | If SUBGROUP-ID is specified only display about that particular group. If | |
3653 | advertise-queue is specified the list of routes that need to be sent | |
3654 | to the peers in the update-group is displayed, advertised-routes means | |
a64e0ee5 | 3655 | the list of routes we have sent to the peers in the update-group and |
09d78f10 DS |
3656 | packet-queue specifies the list of packets in the queue to be sent. |
3657 | ||
6c5be52a | 3658 | .. clicmd:: show bgp update-groups statistics |
09d78f10 DS |
3659 | |
3660 | Display Information about update-group events in FRR. | |
8fcedbd2 | 3661 | |
4ccd4033 HS |
3662 | Segment-Routing IPv6 |
3663 | -------------------- | |
3664 | ||
3665 | .. clicmd:: show bgp segment-routing srv6 | |
3666 | ||
3667 | This command displays information about SRv6 L3VPN in bgpd. Specifically, | |
3668 | what kind of Locator is being used, and its Locator chunk information. | |
3669 | And the SID of the SRv6 Function that is actually managed on bgpd. | |
3670 | In the following example, bgpd is using a Locator named loc1, and two SRv6 | |
3671 | Functions are managed to perform VPNv6 VRF redirect for vrf10 and vrf20. | |
3672 | ||
3673 | :: | |
3674 | ||
3675 | router# show bgp segment-routing srv6 | |
3676 | locator_name: loc1 | |
3677 | locator_chunks: | |
3678 | - 2001:db8:1:1::/64 | |
3679 | functions: | |
3680 | - sid: 2001:db8:1:1::100 | |
3681 | locator: loc1 | |
3682 | - sid: 2001:db8:1:1::200 | |
3683 | locator: loc1 | |
3684 | bgps: | |
3685 | - name: default | |
3686 | vpn_policy[AFI_IP].tovpn_sid: none | |
3687 | vpn_policy[AFI_IP6].tovpn_sid: none | |
3688 | - name: vrf10 | |
3689 | vpn_policy[AFI_IP].tovpn_sid: none | |
3690 | vpn_policy[AFI_IP6].tovpn_sid: 2001:db8:1:1::100 | |
3691 | - name: vrf20 | |
3692 | vpn_policy[AFI_IP].tovpn_sid: none | |
3693 | vpn_policy[AFI_IP6].tovpn_sid: 2001:db8:1:1::200 | |
3694 | ||
3695 | ||
8fcedbd2 QY |
3696 | .. _bgp-route-reflector: |
3697 | ||
3698 | Route Reflector | |
3699 | =============== | |
3700 | ||
749afd7d RF |
3701 | BGP routers connected inside the same AS through BGP belong to an internal |
3702 | BGP session, or IBGP. In order to prevent routing table loops, IBGP does not | |
3703 | advertise IBGP-learned routes to other routers in the same session. As such, | |
3704 | IBGP requires a full mesh of all peers. For large networks, this quickly becomes | |
3705 | unscalable. Introducing route reflectors removes the need for the full-mesh. | |
8fcedbd2 | 3706 | |
749afd7d RF |
3707 | When route reflectors are configured, these will reflect the routes announced |
3708 | by the peers configured as clients. A route reflector client is configured | |
3709 | with: | |
8fcedbd2 | 3710 | |
8fcedbd2 QY |
3711 | .. clicmd:: neighbor PEER route-reflector-client |
3712 | ||
c3c5a71f | 3713 | |
749afd7d RF |
3714 | To avoid single points of failure, multiple route reflectors can be configured. |
3715 | ||
3716 | A cluster is a collection of route reflectors and their clients, and is used | |
3717 | by route reflectors to avoid looping. | |
3718 | ||
749afd7d | 3719 | .. clicmd:: bgp cluster-id A.B.C.D |
42fc5d26 | 3720 | |
03750f1e | 3721 | .. clicmd:: bgp no-rib |
8dad2243 DS |
3722 | |
3723 | To set and unset the BGP daemon ``-n`` / ``--no_kernel`` options during runtime | |
3724 | to disable BGP route installation to the RIB (Zebra), the ``[no] bgp no-rib`` | |
3725 | commands can be used; | |
3726 | ||
3727 | Please note that setting the option during runtime will withdraw all routes in | |
3728 | the daemons RIB from Zebra and unsetting it will announce all routes in the | |
3729 | daemons RIB to Zebra. If the option is passed as a command line argument when | |
3730 | starting the daemon and the configuration gets saved, the option will persist | |
3731 | unless removed from the configuration with the negating command prior to the | |
3732 | configuration write operation. | |
3733 | ||
03750f1e | 3734 | .. clicmd:: bgp send-extra-data zebra |
9a06c157 | 3735 | |
3165cca9 | 3736 | This Command turns off the ability of BGP to send extra data to zebra. |
9a06c157 DS |
3737 | In this case it's the AS-Path being used for the path. The default behavior |
3738 | in BGP is to send this data and to turn it off enter the no form of the command. | |
3739 | If extra data was sent to zebra, and this command is turned on there is no | |
3740 | effort to clean up this data in the rib. | |
3741 | ||
1cc55938 S |
3742 | .. _bgp-suppress-fib: |
3743 | ||
3744 | Suppressing routes not installed in FIB | |
3745 | ======================================= | |
3746 | ||
3747 | The FRR implementation of BGP advertises prefixes learnt from a peer to other | |
3748 | peers even if the routes do not get installed in the FIB. There can be | |
3749 | scenarios where the hardware tables in some of the routers (along the path from | |
3750 | the source to destination) is full which will result in all routes not getting | |
3751 | installed in the FIB. If these routes are advertised to the downstream routers | |
3752 | then traffic will start flowing and will be dropped at the intermediate router. | |
3753 | ||
3754 | The solution is to provide a configurable option to check for the FIB install | |
3755 | status of the prefixes and advertise to peers if the prefixes are successfully | |
3756 | installed in the FIB. The advertisement of the prefixes are suppressed if it is | |
3757 | not installed in FIB. | |
3758 | ||
3759 | The following conditions apply will apply when checking for route installation | |
3760 | status in FIB: | |
0ea5223c | 3761 | |
1cc55938 S |
3762 | 1. The advertisement or suppression of routes based on FIB install status |
3763 | applies only for newly learnt routes from peer (routes which are not in | |
3764 | BGP local RIB). | |
3765 | 2. If the route received from peer already exists in BGP local RIB and route | |
3766 | attributes have changed (best path changed), the old path is deleted and | |
3767 | new path is installed in FIB. The FIB install status will not have any | |
3768 | effect. Therefore only when the route is received first time the checks | |
3769 | apply. | |
3770 | 3. The feature will not apply for routes learnt through other means like | |
3771 | redistribution to bgp from other protocols. This is applicable only to | |
3772 | peer learnt routes. | |
3773 | 4. If a route is installed in FIB and then gets deleted from the dataplane, | |
3774 | then routes will not be withdrawn from peers. This will be considered as | |
3775 | dataplane issue. | |
3776 | 5. The feature will slightly increase the time required to advertise the routes | |
3777 | to peers since the route install status needs to be received from the FIB | |
3778 | 6. If routes are received by the peer before the configuration is applied, then | |
3779 | the bgp sessions need to be reset for the configuration to take effect. | |
3780 | 7. If the route which is already installed in dataplane is removed for some | |
3781 | reason, sending withdraw message to peers is not currently supported. | |
3782 | ||
03750f1e | 3783 | .. clicmd:: bgp suppress-fib-pending |
8dad2243 | 3784 | |
4f4ba68c DS |
3785 | This command is applicable at the global level and at an individual |
3786 | bgp level. If applied at the global level all bgp instances will | |
3787 | wait for fib installation before announcing routes and there is no | |
3788 | way to turn it off for a particular bgp vrf. | |
3789 | ||
0efdf0fe | 3790 | .. _routing-policy: |
42fc5d26 | 3791 | |
8fcedbd2 QY |
3792 | Routing Policy |
3793 | ============== | |
42fc5d26 | 3794 | |
4da7fda3 | 3795 | You can set different routing policy for a peer. For example, you can set |
9eb95b3b QY |
3796 | different filter for a peer. |
3797 | ||
3798 | .. code-block:: frr | |
c1a54c05 | 3799 | |
c1a54c05 QY |
3800 | ! |
3801 | router bgp 1 view 1 | |
3802 | neighbor 10.0.0.1 remote-as 2 | |
3803 | address-family ipv4 unicast | |
3804 | neighbor 10.0.0.1 distribute-list 1 in | |
3805 | exit-address-family | |
3806 | ! | |
3807 | router bgp 1 view 2 | |
3808 | neighbor 10.0.0.1 remote-as 2 | |
3809 | address-family ipv4 unicast | |
3810 | neighbor 10.0.0.1 distribute-list 2 in | |
3811 | exit-address-family | |
c3c5a71f | 3812 | |
4da7fda3 QY |
3813 | This means BGP update from a peer 10.0.0.1 goes to both BGP view 1 and view 2. |
3814 | When the update is inserted into view 1, distribute-list 1 is applied. On the | |
3815 | other hand, when the update is inserted into view 2, distribute-list 2 is | |
3816 | applied. | |
42fc5d26 | 3817 | |
42fc5d26 | 3818 | |
0efdf0fe | 3819 | .. _bgp-regular-expressions: |
42fc5d26 QY |
3820 | |
3821 | BGP Regular Expressions | |
3822 | ======================= | |
3823 | ||
8fcedbd2 QY |
3824 | BGP regular expressions are based on :t:`POSIX 1003.2` regular expressions. The |
3825 | following description is just a quick subset of the POSIX regular expressions. | |
42fc5d26 QY |
3826 | |
3827 | ||
8fcedbd2 | 3828 | .\* |
c1a54c05 | 3829 | Matches any single character. |
42fc5d26 | 3830 | |
8fcedbd2 | 3831 | \* |
c1a54c05 | 3832 | Matches 0 or more occurrences of pattern. |
42fc5d26 | 3833 | |
8fcedbd2 | 3834 | \+ |
c1a54c05 | 3835 | Matches 1 or more occurrences of pattern. |
42fc5d26 QY |
3836 | |
3837 | ? | |
c1a54c05 | 3838 | Match 0 or 1 occurrences of pattern. |
42fc5d26 QY |
3839 | |
3840 | ^ | |
c1a54c05 | 3841 | Matches the beginning of the line. |
42fc5d26 QY |
3842 | |
3843 | $ | |
c1a54c05 | 3844 | Matches the end of the line. |
42fc5d26 QY |
3845 | |
3846 | _ | |
8fcedbd2 QY |
3847 | The ``_`` character has special meanings in BGP regular expressions. It |
3848 | matches to space and comma , and AS set delimiter ``{`` and ``}`` and AS | |
3849 | confederation delimiter ``(`` and ``)``. And it also matches to the | |
3850 | beginning of the line and the end of the line. So ``_`` can be used for AS | |
3851 | value boundaries match. This character technically evaluates to | |
3852 | ``(^|[,{}()]|$)``. | |
42fc5d26 | 3853 | |
42fc5d26 | 3854 | |
c1a54c05 | 3855 | .. _bgp-configuration-examples: |
42fc5d26 | 3856 | |
8fcedbd2 QY |
3857 | Miscellaneous Configuration Examples |
3858 | ==================================== | |
42fc5d26 | 3859 | |
9eb95b3b QY |
3860 | Example of a session to an upstream, advertising only one prefix to it. |
3861 | ||
3862 | .. code-block:: frr | |
42fc5d26 | 3863 | |
c1a54c05 QY |
3864 | router bgp 64512 |
3865 | bgp router-id 10.236.87.1 | |
3866 | neighbor upstream peer-group | |
3867 | neighbor upstream remote-as 64515 | |
3868 | neighbor upstream capability dynamic | |
3869 | neighbor 10.1.1.1 peer-group upstream | |
3870 | neighbor 10.1.1.1 description ACME ISP | |
c3c5a71f | 3871 | |
c1a54c05 QY |
3872 | address-family ipv4 unicast |
3873 | network 10.236.87.0/24 | |
3874 | neighbor upstream prefix-list pl-allowed-adv out | |
3875 | exit-address-family | |
3876 | ! | |
3877 | ip prefix-list pl-allowed-adv seq 5 permit 82.195.133.0/25 | |
3878 | ip prefix-list pl-allowed-adv seq 10 deny any | |
42fc5d26 | 3879 | |
aa9eafa4 QY |
3880 | A more complex example including upstream, peer and customer sessions |
3881 | advertising global prefixes and NO_EXPORT prefixes and providing actions for | |
3882 | customer routes based on community values. Extensive use is made of route-maps | |
3883 | and the 'call' feature to support selective advertising of prefixes. This | |
3884 | example is intended as guidance only, it has NOT been tested and almost | |
3885 | certainly contains silly mistakes, if not serious flaws. | |
42fc5d26 | 3886 | |
9eb95b3b | 3887 | .. code-block:: frr |
42fc5d26 | 3888 | |
c1a54c05 QY |
3889 | router bgp 64512 |
3890 | bgp router-id 10.236.87.1 | |
3891 | neighbor upstream capability dynamic | |
3892 | neighbor cust capability dynamic | |
3893 | neighbor peer capability dynamic | |
3894 | neighbor 10.1.1.1 remote-as 64515 | |
3895 | neighbor 10.1.1.1 peer-group upstream | |
3896 | neighbor 10.2.1.1 remote-as 64516 | |
3897 | neighbor 10.2.1.1 peer-group upstream | |
3898 | neighbor 10.3.1.1 remote-as 64517 | |
3899 | neighbor 10.3.1.1 peer-group cust-default | |
3900 | neighbor 10.3.1.1 description customer1 | |
3901 | neighbor 10.4.1.1 remote-as 64518 | |
3902 | neighbor 10.4.1.1 peer-group cust | |
3903 | neighbor 10.4.1.1 description customer2 | |
3904 | neighbor 10.5.1.1 remote-as 64519 | |
3905 | neighbor 10.5.1.1 peer-group peer | |
3906 | neighbor 10.5.1.1 description peer AS 1 | |
3907 | neighbor 10.6.1.1 remote-as 64520 | |
3908 | neighbor 10.6.1.1 peer-group peer | |
3909 | neighbor 10.6.1.1 description peer AS 2 | |
3910 | ||
3911 | address-family ipv4 unicast | |
3912 | network 10.123.456.0/24 | |
3913 | network 10.123.456.128/25 route-map rm-no-export | |
3914 | neighbor upstream route-map rm-upstream-out out | |
3915 | neighbor cust route-map rm-cust-in in | |
3916 | neighbor cust route-map rm-cust-out out | |
3917 | neighbor cust send-community both | |
3918 | neighbor peer route-map rm-peer-in in | |
3919 | neighbor peer route-map rm-peer-out out | |
3920 | neighbor peer send-community both | |
3921 | neighbor 10.3.1.1 prefix-list pl-cust1-network in | |
3922 | neighbor 10.4.1.1 prefix-list pl-cust2-network in | |
3923 | neighbor 10.5.1.1 prefix-list pl-peer1-network in | |
3924 | neighbor 10.6.1.1 prefix-list pl-peer2-network in | |
3925 | exit-address-family | |
3926 | ! | |
3927 | ip prefix-list pl-default permit 0.0.0.0/0 | |
3928 | ! | |
3929 | ip prefix-list pl-upstream-peers permit 10.1.1.1/32 | |
3930 | ip prefix-list pl-upstream-peers permit 10.2.1.1/32 | |
3931 | ! | |
3932 | ip prefix-list pl-cust1-network permit 10.3.1.0/24 | |
3933 | ip prefix-list pl-cust1-network permit 10.3.2.0/24 | |
3934 | ! | |
3935 | ip prefix-list pl-cust2-network permit 10.4.1.0/24 | |
3936 | ! | |
3937 | ip prefix-list pl-peer1-network permit 10.5.1.0/24 | |
3938 | ip prefix-list pl-peer1-network permit 10.5.2.0/24 | |
3939 | ip prefix-list pl-peer1-network permit 192.168.0.0/24 | |
3940 | ! | |
3941 | ip prefix-list pl-peer2-network permit 10.6.1.0/24 | |
3942 | ip prefix-list pl-peer2-network permit 10.6.2.0/24 | |
3943 | ip prefix-list pl-peer2-network permit 192.168.1.0/24 | |
3944 | ip prefix-list pl-peer2-network permit 192.168.2.0/24 | |
3945 | ip prefix-list pl-peer2-network permit 172.16.1/24 | |
3946 | ! | |
e6e62ee5 CS |
3947 | bgp as-path access-list seq 5 asp-own-as permit ^$ |
3948 | bgp as-path access-list seq 10 asp-own-as permit _64512_ | |
c1a54c05 QY |
3949 | ! |
3950 | ! ################################################################# | |
3951 | ! Match communities we provide actions for, on routes receives from | |
3952 | ! customers. Communities values of <our-ASN>:X, with X, have actions: | |
3953 | ! | |
3954 | ! 100 - blackhole the prefix | |
3955 | ! 200 - set no_export | |
3956 | ! 300 - advertise only to other customers | |
3957 | ! 400 - advertise only to upstreams | |
3958 | ! 500 - set no_export when advertising to upstreams | |
3959 | ! 2X00 - set local_preference to X00 | |
3960 | ! | |
3961 | ! blackhole the prefix of the route | |
a64e0ee5 | 3962 | bgp community-list standard cm-blackhole permit 64512:100 |
c1a54c05 QY |
3963 | ! |
3964 | ! set no-export community before advertising | |
a64e0ee5 | 3965 | bgp community-list standard cm-set-no-export permit 64512:200 |
c1a54c05 QY |
3966 | ! |
3967 | ! advertise only to other customers | |
a64e0ee5 | 3968 | bgp community-list standard cm-cust-only permit 64512:300 |
c1a54c05 QY |
3969 | ! |
3970 | ! advertise only to upstreams | |
a64e0ee5 | 3971 | bgp community-list standard cm-upstream-only permit 64512:400 |
c1a54c05 QY |
3972 | ! |
3973 | ! advertise to upstreams with no-export | |
a64e0ee5 | 3974 | bgp community-list standard cm-upstream-noexport permit 64512:500 |
c1a54c05 QY |
3975 | ! |
3976 | ! set local-pref to least significant 3 digits of the community | |
a64e0ee5 DA |
3977 | bgp community-list standard cm-prefmod-100 permit 64512:2100 |
3978 | bgp community-list standard cm-prefmod-200 permit 64512:2200 | |
3979 | bgp community-list standard cm-prefmod-300 permit 64512:2300 | |
3980 | bgp community-list standard cm-prefmod-400 permit 64512:2400 | |
3981 | bgp community-list expanded cme-prefmod-range permit 64512:2... | |
c1a54c05 QY |
3982 | ! |
3983 | ! Informational communities | |
3984 | ! | |
3985 | ! 3000 - learned from upstream | |
3986 | ! 3100 - learned from customer | |
3987 | ! 3200 - learned from peer | |
3988 | ! | |
a64e0ee5 DA |
3989 | bgp community-list standard cm-learnt-upstream permit 64512:3000 |
3990 | bgp community-list standard cm-learnt-cust permit 64512:3100 | |
3991 | bgp community-list standard cm-learnt-peer permit 64512:3200 | |
c1a54c05 QY |
3992 | ! |
3993 | ! ################################################################### | |
3994 | ! Utility route-maps | |
3995 | ! | |
3996 | ! These utility route-maps generally should not used to permit/deny | |
3997 | ! routes, i.e. they do not have meaning as filters, and hence probably | |
3998 | ! should be used with 'on-match next'. These all finish with an empty | |
3999 | ! permit entry so as not interfere with processing in the caller. | |
4000 | ! | |
4001 | route-map rm-no-export permit 10 | |
4002 | set community additive no-export | |
4003 | route-map rm-no-export permit 20 | |
4004 | ! | |
4005 | route-map rm-blackhole permit 10 | |
f6aa36f5 | 4006 | description blackhole, up-pref and ensure it cannot escape this AS |
c1a54c05 QY |
4007 | set ip next-hop 127.0.0.1 |
4008 | set local-preference 10 | |
4009 | set community additive no-export | |
4010 | route-map rm-blackhole permit 20 | |
4011 | ! | |
4012 | ! Set local-pref as requested | |
4013 | route-map rm-prefmod permit 10 | |
4014 | match community cm-prefmod-100 | |
4015 | set local-preference 100 | |
4016 | route-map rm-prefmod permit 20 | |
4017 | match community cm-prefmod-200 | |
4018 | set local-preference 200 | |
4019 | route-map rm-prefmod permit 30 | |
4020 | match community cm-prefmod-300 | |
4021 | set local-preference 300 | |
4022 | route-map rm-prefmod permit 40 | |
4023 | match community cm-prefmod-400 | |
4024 | set local-preference 400 | |
4025 | route-map rm-prefmod permit 50 | |
4026 | ! | |
4027 | ! Community actions to take on receipt of route. | |
4028 | route-map rm-community-in permit 10 | |
4029 | description check for blackholing, no point continuing if it matches. | |
4030 | match community cm-blackhole | |
4031 | call rm-blackhole | |
4032 | route-map rm-community-in permit 20 | |
4033 | match community cm-set-no-export | |
4034 | call rm-no-export | |
4035 | on-match next | |
4036 | route-map rm-community-in permit 30 | |
4037 | match community cme-prefmod-range | |
4038 | call rm-prefmod | |
4039 | route-map rm-community-in permit 40 | |
4040 | ! | |
4041 | ! ##################################################################### | |
4042 | ! Community actions to take when advertising a route. | |
4043 | ! These are filtering route-maps, | |
4044 | ! | |
4045 | ! Deny customer routes to upstream with cust-only set. | |
4046 | route-map rm-community-filt-to-upstream deny 10 | |
4047 | match community cm-learnt-cust | |
4048 | match community cm-cust-only | |
4049 | route-map rm-community-filt-to-upstream permit 20 | |
4050 | ! | |
4051 | ! Deny customer routes to other customers with upstream-only set. | |
4052 | route-map rm-community-filt-to-cust deny 10 | |
4053 | match community cm-learnt-cust | |
4054 | match community cm-upstream-only | |
4055 | route-map rm-community-filt-to-cust permit 20 | |
4056 | ! | |
4057 | ! ################################################################### | |
4058 | ! The top-level route-maps applied to sessions. Further entries could | |
4059 | ! be added obviously.. | |
4060 | ! | |
4061 | ! Customers | |
4062 | route-map rm-cust-in permit 10 | |
4063 | call rm-community-in | |
4064 | on-match next | |
4065 | route-map rm-cust-in permit 20 | |
4066 | set community additive 64512:3100 | |
4067 | route-map rm-cust-in permit 30 | |
4068 | ! | |
4069 | route-map rm-cust-out permit 10 | |
4070 | call rm-community-filt-to-cust | |
4071 | on-match next | |
4072 | route-map rm-cust-out permit 20 | |
4073 | ! | |
4074 | ! Upstream transit ASes | |
4075 | route-map rm-upstream-out permit 10 | |
4076 | description filter customer prefixes which are marked cust-only | |
4077 | call rm-community-filt-to-upstream | |
4078 | on-match next | |
4079 | route-map rm-upstream-out permit 20 | |
4080 | description only customer routes are provided to upstreams/peers | |
4081 | match community cm-learnt-cust | |
4082 | ! | |
4083 | ! Peer ASes | |
4084 | ! outbound policy is same as for upstream | |
4085 | route-map rm-peer-out permit 10 | |
4086 | call rm-upstream-out | |
4087 | ! | |
4088 | route-map rm-peer-in permit 10 | |
4089 | set community additive 64512:3200 | |
c3c5a71f | 4090 | |
8fcedbd2 QY |
4091 | |
4092 | Example of how to set up a 6-Bone connection. | |
4093 | ||
4094 | .. code-block:: frr | |
4095 | ||
4096 | ! bgpd configuration | |
4097 | ! ================== | |
4098 | ! | |
4099 | ! MP-BGP configuration | |
4100 | ! | |
4101 | router bgp 7675 | |
4102 | bgp router-id 10.0.0.1 | |
4103 | neighbor 3ffe:1cfa:0:2:2a0:c9ff:fe9e:f56 remote-as `as-number` | |
4104 | ! | |
4105 | address-family ipv6 | |
4106 | network 3ffe:506::/32 | |
4107 | neighbor 3ffe:1cfa:0:2:2a0:c9ff:fe9e:f56 activate | |
4108 | neighbor 3ffe:1cfa:0:2:2a0:c9ff:fe9e:f56 route-map set-nexthop out | |
4109 | neighbor 3ffe:1cfa:0:2:2c0:4fff:fe68:a231 remote-as `as-number` | |
4110 | neighbor 3ffe:1cfa:0:2:2c0:4fff:fe68:a231 route-map set-nexthop out | |
4111 | exit-address-family | |
4112 | ! | |
4113 | ipv6 access-list all permit any | |
4114 | ! | |
4115 | ! Set output nexthop address. | |
4116 | ! | |
4117 | route-map set-nexthop permit 10 | |
4118 | match ipv6 address all | |
4119 | set ipv6 nexthop global 3ffe:1cfa:0:2:2c0:4fff:fe68:a225 | |
4120 | set ipv6 nexthop local fe80::2c0:4fff:fe68:a225 | |
4121 | ! | |
4122 | log file bgpd.log | |
4123 | ! | |
4124 | ||
4ab46701 AR |
4125 | .. _bgp-tcp-mss: |
4126 | ||
4127 | BGP tcp-mss support | |
4128 | =================== | |
4129 | TCP provides a mechanism for the user to specify the max segment size. | |
4130 | setsockopt API is used to set the max segment size for TCP session. We | |
4131 | can configure this as part of BGP neighbor configuration. | |
4132 | ||
4133 | This document explains how to avoid ICMP vulnerability issues by limiting | |
4134 | TCP max segment size when you are using MTU discovery. Using MTU discovery | |
4135 | on TCP paths is one method of avoiding BGP packet fragmentation. | |
4136 | ||
4137 | TCP negotiates a maximum segment size (MSS) value during session connection | |
4138 | establishment between two peers. The MSS value negotiated is primarily based | |
073b7664 DA |
4139 | on the maximum transmission unit (MTU) of the interfaces to which the |
4140 | communicating peers are directly connected. However, due to variations in | |
4141 | link MTU on the path taken by the TCP packets, some packets in the network | |
4ab46701 | 4142 | that are well within the MSS value might be fragmented when the packet size |
073b7664 | 4143 | exceeds the link's MTU. |
4ab46701 AR |
4144 | |
4145 | This feature is supported with TCP over IPv4 and TCP over IPv6. | |
4146 | ||
4147 | CLI Configuration: | |
4148 | ------------------ | |
4149 | Below configuration can be done in router bgp mode and allows the user to | |
4150 | configure the tcp-mss value per neighbor. The configuration gets applied | |
4151 | only after hard reset is performed on that neighbor. If we configure tcp-mss | |
4152 | on both the neighbors then both neighbors need to be reset. | |
4153 | ||
4154 | The configuration takes effect based on below rules, so there is a configured | |
4155 | tcp-mss and a synced tcp-mss value per TCP session. | |
4156 | ||
4157 | By default if the configuration is not done then the TCP max segment size is | |
4158 | set to the Maximum Transmission unit (MTU) – (IP/IP6 header size + TCP header | |
4159 | size + ethernet header). For IPv4 its MTU – (20 bytes IP header + 20 bytes TCP | |
4160 | header + 12 bytes ethernet header) and for IPv6 its MTU – (40 bytes IPv6 header | |
4161 | + 20 bytes TCP header + 12 bytes ethernet header). | |
4162 | ||
073b7664 | 4163 | If the config is done then it reduces 12-14 bytes for the ether header and |
4ab46701 AR |
4164 | uses it after synchronizing in TCP handshake. |
4165 | ||
4166 | .. clicmd:: neighbor <A.B.C.D|X:X::X:X|WORD> tcp-mss (1-65535) | |
4167 | ||
4168 | When tcp-mss is configured kernel reduces 12-14 bytes for ethernet header. | |
4169 | E.g. if tcp-mss is configured as 150 the synced value will be 138. | |
4170 | ||
4171 | Note: configured and synced value is different since TCP module will reduce | |
4172 | 12 bytes for ethernet header. | |
4173 | ||
4174 | Running config: | |
4175 | --------------- | |
4176 | ||
4177 | .. code-block:: frr | |
4178 | ||
073b7664 | 4179 | frr# show running-config |
4ab46701 AR |
4180 | Building configuration... |
4181 | ||
4182 | Current configuration: | |
4183 | ! | |
4184 | router bgp 100 | |
4185 | bgp router-id 192.0.2.1 | |
4186 | neighbor 198.51.100.2 remote-as 100 | |
4187 | neighbor 198.51.100.2 tcp-mss 150 => new entry | |
4188 | neighbor 2001:DB8::2 remote-as 100 | |
4189 | neighbor 2001:DB8::2 tcp-mss 400 => new entry | |
4190 | ||
4191 | Show command: | |
4192 | ------------- | |
4193 | ||
4194 | .. code-block:: frr | |
4195 | ||
073b7664 | 4196 | frr# show bgp neighbors 198.51.100.2 |
4ab46701 AR |
4197 | BGP neighbor is 198.51.100.2, remote AS 100, local AS 100, internal link |
4198 | Hostname: frr | |
4199 | BGP version 4, remote router ID 192.0.2.2, local router ID 192.0.2.1 | |
4200 | BGP state = Established, up for 02:15:28 | |
4201 | Last read 00:00:28, Last write 00:00:28 | |
4202 | Hold time is 180, keepalive interval is 60 seconds | |
4203 | Configured tcp-mss is 150, synced tcp-mss is 138 => new display | |
4204 | ||
4205 | .. code-block:: frr | |
4206 | ||
073b7664 | 4207 | frr# show bgp neighbors 2001:DB8::2 |
4ab46701 AR |
4208 | BGP neighbor is 2001:DB8::2, remote AS 100, local AS 100, internal link |
4209 | Hostname: frr | |
4210 | BGP version 4, remote router ID 192.0.2.2, local router ID 192.0.2.1 | |
4211 | BGP state = Established, up for 02:16:34 | |
4212 | Last read 00:00:34, Last write 00:00:34 | |
4213 | Hold time is 180, keepalive interval is 60 seconds | |
4214 | Configured tcp-mss is 400, synced tcp-mss is 388 => new display | |
4215 | ||
4216 | Show command json output: | |
4217 | ------------------------- | |
4218 | ||
4219 | .. code-block:: frr | |
4220 | ||
073b7664 | 4221 | frr# show bgp neighbors 2001:DB8::2 json |
4ab46701 AR |
4222 | { |
4223 | "2001:DB8::2":{ | |
4224 | "remoteAs":100, | |
4225 | "localAs":100, | |
4226 | "nbrInternalLink":true, | |
4227 | "hostname":"frr", | |
4228 | "bgpVersion":4, | |
4229 | "remoteRouterId":"192.0.2.2", | |
4230 | "localRouterId":"192.0.2.1", | |
4231 | "bgpState":"Established", | |
4232 | "bgpTimerUpMsec":8349000, | |
4233 | "bgpTimerUpString":"02:19:09", | |
4234 | "bgpTimerUpEstablishedEpoch":1613054251, | |
4235 | "bgpTimerLastRead":9000, | |
4236 | "bgpTimerLastWrite":9000, | |
4237 | "bgpInUpdateElapsedTimeMsecs":8347000, | |
4238 | "bgpTimerHoldTimeMsecs":180000, | |
4239 | "bgpTimerKeepAliveIntervalMsecs":60000, | |
4240 | "bgpTcpMssConfigured":400, => new entry | |
4241 | "bgpTcpMssSynced":388, => new entry | |
4242 | ||
4243 | .. code-block:: frr | |
4244 | ||
073b7664 | 4245 | frr# show bgp neighbors 198.51.100.2 json |
4ab46701 AR |
4246 | { |
4247 | "198.51.100.2":{ | |
4248 | "remoteAs":100, | |
4249 | "localAs":100, | |
4250 | "nbrInternalLink":true, | |
4251 | "hostname":"frr", | |
4252 | "bgpVersion":4, | |
4253 | "remoteRouterId":"192.0.2.2", | |
4254 | "localRouterId":"192.0.2.1", | |
4255 | "bgpState":"Established", | |
4256 | "bgpTimerUpMsec":8370000, | |
4257 | "bgpTimerUpString":"02:19:30", | |
4258 | "bgpTimerUpEstablishedEpoch":1613054251, | |
4259 | "bgpTimerLastRead":30000, | |
4260 | "bgpTimerLastWrite":30000, | |
4261 | "bgpInUpdateElapsedTimeMsecs":8368000, | |
4262 | "bgpTimerHoldTimeMsecs":180000, | |
4263 | "bgpTimerKeepAliveIntervalMsecs":60000, | |
4264 | "bgpTcpMssConfigured":150, => new entry | |
4265 | "bgpTcpMssSynced":138, => new entry | |
8fcedbd2 | 4266 | |
9e146a81 | 4267 | .. include:: routeserver.rst |
f3817860 QY |
4268 | |
4269 | .. include:: rpki.rst | |
c1a54c05 | 4270 | |
ed647ed2 | 4271 | .. include:: wecmp_linkbw.rst |
4272 | ||
00458d01 PG |
4273 | .. include:: flowspec.rst |
4274 | ||
d1e7591e | 4275 | .. [#med-transitivity-rant] For some set of objects to have an order, there *must* be some binary ordering relation that is defined for *every* combination of those objects, and that relation *must* be transitive. I.e.:, if the relation operator is <, and if a < b and b < c then that relation must carry over and it *must* be that a < c for the objects to have an order. The ordering relation may allow for equality, i.e. a < b and b < a may both be true and imply that a and b are equal in the order and not distinguished by it, in which case the set has a partial order. Otherwise, if there is an order, all the objects have a distinct place in the order and the set has a total order) |
c1a54c05 QY |
4276 | .. [bgp-route-osci-cond] McPherson, D. and Gill, V. and Walton, D., "Border Gateway Protocol (BGP) Persistent Route Oscillation Condition", IETF RFC3345 |
4277 | .. [stable-flexible-ibgp] Flavel, A. and M. Roughan, "Stable and flexible iBGP", ACM SIGCOMM 2009 | |
4278 | .. [ibgp-correctness] Griffin, T. and G. Wilfong, "On the correctness of IBGP configuration", ACM SIGCOMM 2002 |