]>
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 | |
c0868e8b QY |
34 | Specify a specific IP address for bgpd to listen on, rather than its default |
35 | of ``0.0.0.0`` / ``::``. This can be useful to constrain bgpd to an internal | |
36 | address, or to run multiple bgpd processes on one host. | |
42fc5d26 | 37 | |
8fcedbd2 | 38 | .. _bgp-basic-concepts: |
42fc5d26 | 39 | |
8fcedbd2 QY |
40 | Basic Concepts |
41 | ============== | |
42fc5d26 | 42 | |
8fcedbd2 | 43 | .. _bgp-autonomous-systems: |
c3c5a71f | 44 | |
8fcedbd2 QY |
45 | Autonomous Systems |
46 | ------------------ | |
42fc5d26 | 47 | |
c0868e8b QY |
48 | From :rfc:`1930`: |
49 | ||
50 | An AS is a connected group of one or more IP prefixes run by one or more | |
51 | network operators which has a SINGLE and CLEARLY DEFINED routing policy. | |
52 | ||
53 | Each AS has an identifying number associated with it called an :abbr:`ASN | |
54 | (Autonomous System Number)`. This is a two octet value ranging in value from 1 | |
55 | to 65535. The AS numbers 64512 through 65535 are defined as private AS numbers. | |
56 | Private AS numbers must not be advertised on the global Internet. | |
57 | ||
58 | The :abbr:`ASN (Autonomous System Number)` is one of the essential elements of | |
8fcedbd2 | 59 | BGP. BGP is a distance vector routing protocol, and the AS-Path framework |
c0868e8b | 60 | provides distance vector metric and loop detection to BGP. |
42fc5d26 | 61 | |
c0868e8b | 62 | .. seealso:: :rfc:`1930` |
42fc5d26 | 63 | |
8fcedbd2 | 64 | .. _bgp-address-families: |
42fc5d26 | 65 | |
8fcedbd2 QY |
66 | Address Families |
67 | ---------------- | |
42fc5d26 | 68 | |
c0868e8b QY |
69 | Multiprotocol extensions enable BGP to carry routing information for multiple |
70 | network layer protocols. BGP supports an Address Family Identifier (AFI) for | |
71 | IPv4 and IPv6. Support is also provided for multiple sets of per-AFI | |
72 | information via the BGP Subsequent Address Family Identifier (SAFI). FRR | |
73 | supports SAFIs for unicast information, labeled information (:rfc:`3107` and | |
74 | :rfc:`8277`), and Layer 3 VPN information (:rfc:`4364` and :rfc:`4659`). | |
c3c5a71f | 75 | |
8fcedbd2 | 76 | .. _bgp-route-selection: |
42fc5d26 | 77 | |
8fcedbd2 QY |
78 | Route Selection |
79 | --------------- | |
42fc5d26 | 80 | |
8fcedbd2 QY |
81 | The route selection process used by FRR's BGP implementation uses the following |
82 | decision criterion, starting at the top of the list and going towards the | |
83 | bottom until one of the factors can be used. | |
42fc5d26 | 84 | |
8fcedbd2 | 85 | 1. **Weight check** |
42fc5d26 | 86 | |
c1a54c05 | 87 | Prefer higher local weight routes to lower routes. |
42fc5d26 | 88 | |
8fcedbd2 QY |
89 | 2. **Local preference check** |
90 | ||
c1a54c05 | 91 | Prefer higher local preference routes to lower. |
42fc5d26 | 92 | |
8fcedbd2 QY |
93 | 3. **Local route check** |
94 | ||
c1a54c05 | 95 | Prefer local routes (statics, aggregates, redistributed) to received routes. |
42fc5d26 | 96 | |
8fcedbd2 QY |
97 | 4. **AS path length check** |
98 | ||
c1a54c05 | 99 | Prefer shortest hop-count AS_PATHs. |
42fc5d26 | 100 | |
8fcedbd2 QY |
101 | 5. **Origin check** |
102 | ||
c1a54c05 QY |
103 | Prefer the lowest origin type route. That is, prefer IGP origin routes to |
104 | EGP, to Incomplete routes. | |
42fc5d26 | 105 | |
8fcedbd2 QY |
106 | 6. **MED check** |
107 | ||
c1a54c05 | 108 | Where routes with a MED were received from the same AS, prefer the route |
0efdf0fe | 109 | with the lowest MED. :ref:`bgp-med`. |
42fc5d26 | 110 | |
8fcedbd2 QY |
111 | 7. **External check** |
112 | ||
c1a54c05 QY |
113 | Prefer the route received from an external, eBGP peer over routes received |
114 | from other types of peers. | |
42fc5d26 | 115 | |
8fcedbd2 QY |
116 | 8. **IGP cost check** |
117 | ||
c1a54c05 | 118 | Prefer the route with the lower IGP cost. |
42fc5d26 | 119 | |
8fcedbd2 QY |
120 | 9. **Multi-path check** |
121 | ||
c1a54c05 QY |
122 | If multi-pathing is enabled, then check whether the routes not yet |
123 | distinguished in preference may be considered equal. If | |
9e146a81 | 124 | :clicmd:`bgp bestpath as-path multipath-relax` is set, all such routes are |
c1a54c05 QY |
125 | considered equal, otherwise routes received via iBGP with identical AS_PATHs |
126 | or routes received from eBGP neighbours in the same AS are considered equal. | |
42fc5d26 | 127 | |
8fcedbd2 QY |
128 | 10. **Already-selected external check** |
129 | ||
07738543 QY |
130 | Where both routes were received from eBGP peers, then prefer the route |
131 | which is already selected. Note that this check is not applied if | |
132 | :clicmd:`bgp bestpath compare-routerid` is configured. This check can | |
133 | prevent some cases of oscillation. | |
134 | ||
8fcedbd2 QY |
135 | 11. **Router-ID check** |
136 | ||
07738543 QY |
137 | Prefer the route with the lowest `router-ID`. If the route has an |
138 | `ORIGINATOR_ID` attribute, through iBGP reflection, then that router ID is | |
139 | used, otherwise the `router-ID` of the peer the route was received from is | |
140 | used. | |
141 | ||
8fcedbd2 QY |
142 | 12. **Cluster-List length check** |
143 | ||
07738543 QY |
144 | The route with the shortest cluster-list length is used. The cluster-list |
145 | reflects the iBGP reflection path the route has taken. | |
146 | ||
8fcedbd2 QY |
147 | 13. **Peer address** |
148 | ||
07738543 QY |
149 | Prefer the route received from the peer with the higher transport layer |
150 | address, as a last-resort tie-breaker. | |
42fc5d26 | 151 | |
8fcedbd2 QY |
152 | .. _bgp-capability-negotiation: |
153 | ||
154 | Capability Negotiation | |
155 | ---------------------- | |
156 | ||
157 | When adding IPv6 routing information exchange feature to BGP. There were some | |
158 | proposals. :abbr:`IETF (Internet Engineering Task Force)` | |
159 | :abbr:`IDR (Inter Domain Routing)` adopted a proposal called Multiprotocol | |
160 | Extension for BGP. The specification is described in :rfc:`2283`. The protocol | |
161 | does not define new protocols. It defines new attributes to existing BGP. When | |
162 | it is used exchanging IPv6 routing information it is called BGP-4+. When it is | |
163 | used for exchanging multicast routing information it is called MBGP. | |
164 | ||
165 | *bgpd* supports Multiprotocol Extension for BGP. So if a remote peer supports | |
166 | the protocol, *bgpd* can exchange IPv6 and/or multicast routing information. | |
167 | ||
168 | Traditional BGP did not have the feature to detect a remote peer's | |
169 | capabilities, e.g. whether it can handle prefix types other than IPv4 unicast | |
170 | routes. This was a big problem using Multiprotocol Extension for BGP in an | |
171 | operational network. :rfc:`2842` adopted a feature called Capability | |
172 | Negotiation. *bgpd* use this Capability Negotiation to detect the remote peer's | |
173 | capabilities. If a peer is only configured as an IPv4 unicast neighbor, *bgpd* | |
174 | does not send these Capability Negotiation packets (at least not unless other | |
175 | optional BGP features require capability negotiation). | |
176 | ||
177 | By default, FRR will bring up peering with minimal common capability for the | |
178 | both sides. For example, if the local router has unicast and multicast | |
179 | capabilities and the remote router only has unicast capability the local router | |
180 | will establish the connection with unicast only capability. When there are no | |
181 | common capabilities, FRR sends Unsupported Capability error and then resets the | |
182 | connection. | |
183 | ||
8fcedbd2 QY |
184 | .. _bgp-router-configuration: |
185 | ||
186 | BGP Router Configuration | |
187 | ======================== | |
188 | ||
189 | ASN and Router ID | |
190 | ----------------- | |
191 | ||
192 | First of all you must configure BGP router with the :clicmd:`router bgp ASN` | |
193 | command. The AS number is an identifier for the autonomous system. The BGP | |
194 | protocol uses the AS number for detecting whether the BGP connection is | |
195 | internal or external. | |
196 | ||
197 | .. index:: router bgp ASN | |
198 | .. clicmd:: router bgp ASN | |
199 | ||
200 | Enable a BGP protocol process with the specified ASN. After | |
201 | this statement you can input any `BGP Commands`. | |
202 | ||
203 | .. index:: no router bgp ASN | |
204 | .. clicmd:: no router bgp ASN | |
205 | ||
206 | Destroy a BGP protocol process with the specified ASN. | |
207 | ||
208 | .. index:: bgp router-id A.B.C.D | |
209 | .. clicmd:: bgp router-id A.B.C.D | |
210 | ||
211 | This command specifies the router-ID. If *bgpd* connects to *zebra* it gets | |
212 | interface and address information. In that case default router ID value is | |
213 | selected as the largest IP Address of the interfaces. When `router zebra` is | |
214 | not enabled *bgpd* can't get interface information so `router-id` is set to | |
215 | 0.0.0.0. So please set router-id by hand. | |
216 | ||
c8a5e5e1 QY |
217 | |
218 | .. _bgp-multiple-autonomous-systems: | |
219 | ||
220 | Multiple Autonomous Systems | |
221 | --------------------------- | |
222 | ||
223 | FRR's BGP implementation is capable of running multiple autonomous systems at | |
224 | once. Each configured AS corresponds to a :ref:`zebra-vrf`. In the past, to get | |
225 | the same functionality the network administrator had to run a new *bgpd* | |
226 | process; using VRFs allows multiple autonomous systems to be handled in a | |
227 | single process. | |
228 | ||
229 | When using multiple autonomous systems, all router config blocks after the | |
230 | first one must specify a VRF to be the target of BGP's route selection. This | |
231 | VRF must be unique within respect to all other VRFs being used for the same | |
232 | purpose, i.e. two different autonomous systems cannot use the same VRF. | |
233 | However, the same AS can be used with different VRFs. | |
234 | ||
235 | .. note:: | |
236 | ||
237 | The separated nature of VRFs makes it possible to peer a single *bgpd* | |
edde3ce9 QY |
238 | process to itself, on one machine. Note that this can be done fully within |
239 | BGP without a corresponding VRF in the kernel or Zebra, which enables some | |
240 | practical use cases such as :ref:`route reflectors <bgp-route-reflector>` | |
241 | and route servers. | |
c8a5e5e1 QY |
242 | |
243 | Configuration of additional autonomous systems, or of a router that targets a | |
244 | specific VRF, is accomplished with the following command: | |
245 | ||
246 | .. index:: router bgp ASN vrf VRFNAME | |
247 | .. clicmd:: router bgp ASN vrf VRFNAME | |
248 | ||
249 | ``VRFNAME`` is matched against VRFs configured in the kernel. When ``vrf | |
250 | VRFNAME`` is not specified, the BGP protocol process belongs to the default | |
251 | VRF. | |
252 | ||
253 | An example configuration with multiple autonomous systems might look like this: | |
254 | ||
255 | .. code-block:: frr | |
256 | ||
257 | router bgp 1 | |
258 | neighbor 10.0.0.1 remote-as 20 | |
259 | neighbor 10.0.0.2 remote-as 30 | |
260 | ! | |
261 | router bgp 2 vrf blue | |
262 | neighbor 10.0.0.3 remote-as 40 | |
263 | neighbor 10.0.0.4 remote-as 50 | |
264 | ! | |
265 | router bgp 3 vrf red | |
266 | neighbor 10.0.0.5 remote-as 60 | |
267 | neighbor 10.0.0.6 remote-as 70 | |
268 | ... | |
269 | ||
c8a5e5e1 QY |
270 | .. seealso:: :ref:`bgp-vrf-route-leaking` |
271 | .. seealso:: :ref:`zebra-vrf` | |
272 | ||
273 | ||
274 | .. _bgp-views: | |
275 | ||
276 | Views | |
277 | ----- | |
278 | ||
279 | In addition to supporting multiple autonomous systems, FRR's BGP implementation | |
280 | also supports *views*. | |
281 | ||
282 | BGP views are almost the same as normal BGP processes, except that routes | |
195c7461 QY |
283 | selected by BGP are not installed into the kernel routing table. Each BGP view |
284 | provides an independent set of routing information which is only distributed | |
285 | via BGP. Multiple views can be supported, and BGP view information is always | |
286 | independent from other routing protocols and Zebra/kernel routes. BGP views use | |
287 | the core instance (i.e., default VRF) for communication with peers. | |
edde3ce9 | 288 | |
c8a5e5e1 QY |
289 | .. index:: router bgp AS-NUMBER view NAME |
290 | .. clicmd:: router bgp AS-NUMBER view NAME | |
291 | ||
292 | Make a new BGP view. You can use an arbitrary word for the ``NAME``. Routes | |
293 | selected by the view are not installed into the kernel routing table. | |
294 | ||
295 | With this command, you can setup Route Server like below. | |
296 | ||
297 | .. code-block:: frr | |
298 | ||
299 | ! | |
300 | router bgp 1 view 1 | |
301 | neighbor 10.0.0.1 remote-as 2 | |
302 | neighbor 10.0.0.2 remote-as 3 | |
303 | ! | |
304 | router bgp 2 view 2 | |
305 | neighbor 10.0.0.3 remote-as 4 | |
306 | neighbor 10.0.0.4 remote-as 5 | |
307 | ||
308 | .. index:: show [ip] bgp view NAME | |
309 | .. clicmd:: show [ip] bgp view NAME | |
310 | ||
311 | Display the routing table of BGP view ``NAME``. | |
312 | ||
313 | ||
8fcedbd2 QY |
314 | Route Selection |
315 | --------------- | |
c3c5a71f | 316 | |
c1a54c05 | 317 | .. index:: bgp bestpath as-path confed |
29adcd50 | 318 | .. clicmd:: bgp bestpath as-path confed |
42fc5d26 | 319 | |
c1a54c05 QY |
320 | This command specifies that the length of confederation path sets and |
321 | sequences should should be taken into account during the BGP best path | |
322 | decision process. | |
42fc5d26 | 323 | |
c3c5a71f | 324 | .. index:: bgp bestpath as-path multipath-relax |
29adcd50 | 325 | .. clicmd:: bgp bestpath as-path multipath-relax |
42fc5d26 | 326 | |
c1a54c05 QY |
327 | This command specifies that BGP decision process should consider paths |
328 | of equal AS_PATH length candidates for multipath computation. Without | |
329 | the knob, the entire AS_PATH must match for multipath computation. | |
c3c5a71f | 330 | |
29adcd50 | 331 | .. clicmd:: bgp bestpath compare-routerid |
42fc5d26 | 332 | |
c1a54c05 QY |
333 | Ensure that when comparing routes where both are equal on most metrics, |
334 | including local-pref, AS_PATH length, IGP cost, MED, that the tie is broken | |
335 | based on router-ID. | |
42fc5d26 | 336 | |
c1a54c05 QY |
337 | If this option is enabled, then the already-selected check, where |
338 | already selected eBGP routes are preferred, is skipped. | |
42fc5d26 | 339 | |
c1a54c05 QY |
340 | If a route has an `ORIGINATOR_ID` attribute because it has been reflected, |
341 | that `ORIGINATOR_ID` will be used. Otherwise, the router-ID of the peer the | |
342 | route was received from will be used. | |
42fc5d26 | 343 | |
c1a54c05 QY |
344 | The advantage of this is that the route-selection (at this point) will be |
345 | more deterministic. The disadvantage is that a few or even one lowest-ID | |
d1e7591e | 346 | router may attract all traffic to otherwise-equal paths because of this |
c1a54c05 QY |
347 | check. It may increase the possibility of MED or IGP oscillation, unless |
348 | other measures were taken to avoid these. The exact behaviour will be | |
349 | sensitive to the iBGP and reflection topology. | |
42fc5d26 | 350 | |
8fcedbd2 QY |
351 | .. _bgp-distance: |
352 | ||
353 | Administrative Distance Metrics | |
354 | ------------------------------- | |
355 | ||
356 | .. index:: distance bgp (1-255) (1-255) (1-255) | |
357 | .. clicmd:: distance bgp (1-255) (1-255) (1-255) | |
358 | ||
359 | This command change distance value of BGP. The arguments are the distance | |
360 | values for for external routes, internal routes and local routes | |
361 | respectively. | |
362 | ||
363 | .. index:: distance (1-255) A.B.C.D/M | |
364 | .. clicmd:: distance (1-255) A.B.C.D/M | |
365 | ||
366 | .. index:: distance (1-255) A.B.C.D/M WORD | |
367 | .. clicmd:: distance (1-255) A.B.C.D/M WORD | |
368 | ||
369 | Sets the administrative distance for a particular route. | |
42fc5d26 | 370 | |
0efdf0fe | 371 | .. _bgp-route-flap-dampening: |
42fc5d26 | 372 | |
8fcedbd2 QY |
373 | Route Flap Dampening |
374 | -------------------- | |
42fc5d26 | 375 | |
c1a54c05 QY |
376 | .. clicmd:: bgp dampening (1-45) (1-20000) (1-20000) (1-255) |
377 | ||
c1a54c05 | 378 | This command enables BGP route-flap dampening and specifies dampening parameters. |
42fc5d26 | 379 | |
c1a54c05 QY |
380 | half-life |
381 | Half-life time for the penalty | |
42fc5d26 | 382 | |
c1a54c05 QY |
383 | reuse-threshold |
384 | Value to start reusing a route | |
42fc5d26 | 385 | |
c1a54c05 QY |
386 | suppress-threshold |
387 | Value to start suppressing a route | |
42fc5d26 | 388 | |
c1a54c05 QY |
389 | max-suppress |
390 | Maximum duration to suppress a stable route | |
42fc5d26 | 391 | |
c1a54c05 QY |
392 | The route-flap damping algorithm is compatible with :rfc:`2439`. The use of |
393 | this command is not recommended nowadays. | |
42fc5d26 | 394 | |
c1a54c05 | 395 | .. seealso:: |
8fcedbd2 | 396 | https://www.ripe.net/publications/docs/ripe-378 |
42fc5d26 | 397 | |
0efdf0fe | 398 | .. _bgp-med: |
42fc5d26 | 399 | |
8fcedbd2 QY |
400 | Multi-Exit Discriminator |
401 | ------------------------ | |
42fc5d26 | 402 | |
8fcedbd2 | 403 | The BGP :abbr:`MED (Multi-Exit Discriminator)` attribute has properties which |
c1a54c05 QY |
404 | can cause subtle convergence problems in BGP. These properties and problems |
405 | have proven to be hard to understand, at least historically, and may still not | |
406 | be widely understood. The following attempts to collect together and present | |
407 | what is known about MED, to help operators and FRR users in designing and | |
408 | configuring their networks. | |
42fc5d26 | 409 | |
07a17e6d QY |
410 | The BGP :abbr:`MED` attribute is intended to allow one AS to indicate its |
411 | preferences for its ingress points to another AS. The MED attribute will not be | |
412 | propagated on to another AS by the receiving AS - it is 'non-transitive' in the | |
413 | BGP sense. | |
42fc5d26 | 414 | |
c1a54c05 QY |
415 | E.g., if AS X and AS Y have 2 different BGP peering points, then AS X might set |
416 | a MED of 100 on routes advertised at one and a MED of 200 at the other. When AS | |
417 | Y selects between otherwise equal routes to or via AS X, AS Y should prefer to | |
418 | take the path via the lower MED peering of 100 with AS X. Setting the MED | |
419 | allows an AS to influence the routing taken to it within another, neighbouring | |
420 | AS. | |
42fc5d26 QY |
421 | |
422 | In this use of MED it is not really meaningful to compare the MED value on | |
c1a54c05 QY |
423 | routes where the next AS on the paths differs. E.g., if AS Y also had a route |
424 | for some destination via AS Z in addition to the routes from AS X, and AS Z had | |
425 | also set a MED, it wouldn't make sense for AS Y to compare AS Z's MED values to | |
426 | those of AS X. The MED values have been set by different administrators, with | |
427 | different frames of reference. | |
42fc5d26 QY |
428 | |
429 | The default behaviour of BGP therefore is to not compare MED values across | |
dc1046f7 | 430 | routes received from different neighbouring ASes. In FRR this is done by |
c1a54c05 QY |
431 | comparing the neighbouring, left-most AS in the received AS_PATHs of the routes |
432 | and only comparing MED if those are the same. | |
433 | ||
434 | Unfortunately, this behaviour of MED, of sometimes being compared across routes | |
435 | and sometimes not, depending on the properties of those other routes, means MED | |
436 | can cause the order of preference over all the routes to be undefined. That is, | |
437 | given routes A, B, and C, if A is preferred to B, and B is preferred to C, then | |
438 | a well-defined order should mean the preference is transitive (in the sense of | |
013f9762 | 439 | orders [#med-transitivity-rant]_) and that A would be preferred to C. |
42fc5d26 | 440 | |
c3c5a71f QY |
441 | However, when MED is involved this need not be the case. With MED it is |
442 | possible that C is actually preferred over A. So A is preferred to B, B is | |
443 | preferred to C, but C is preferred to A. This can be true even where BGP | |
c1a54c05 QY |
444 | defines a deterministic 'most preferred' route out of the full set of A,B,C. |
445 | With MED, for any given set of routes there may be a deterministically | |
446 | preferred route, but there need not be any way to arrange them into any order | |
447 | of preference. With unmodified MED, the order of preference of routes literally | |
448 | becomes undefined. | |
42fc5d26 | 449 | |
c3c5a71f | 450 | That MED can induce non-transitive preferences over routes can cause issues. |
c1a54c05 QY |
451 | Firstly, it may be perceived to cause routing table churn locally at speakers; |
452 | secondly, and more seriously, it may cause routing instability in iBGP | |
453 | topologies, where sets of speakers continually oscillate between different | |
454 | paths. | |
42fc5d26 | 455 | |
c3c5a71f | 456 | The first issue arises from how speakers often implement routing decisions. |
c1a54c05 QY |
457 | Though BGP defines a selection process that will deterministically select the |
458 | same route as best at any given speaker, even with MED, that process requires | |
459 | evaluating all routes together. For performance and ease of implementation | |
460 | reasons, many implementations evaluate route preferences in a pair-wise fashion | |
461 | instead. Given there is no well-defined order when MED is involved, the best | |
462 | route that will be chosen becomes subject to implementation details, such as | |
463 | the order the routes are stored in. That may be (locally) non-deterministic, | |
464 | e.g.: it may be the order the routes were received in. | |
42fc5d26 QY |
465 | |
466 | This indeterminism may be considered undesirable, though it need not cause | |
c1a54c05 QY |
467 | problems. It may mean additional routing churn is perceived, as sometimes more |
468 | updates may be produced than at other times in reaction to some event . | |
42fc5d26 QY |
469 | |
470 | This first issue can be fixed with a more deterministic route selection that | |
c3c5a71f | 471 | ensures routes are ordered by the neighbouring AS during selection. |
9e146a81 | 472 | :clicmd:`bgp deterministic-med`. This may reduce the number of updates as routes |
c1a54c05 QY |
473 | are received, and may in some cases reduce routing churn. Though, it could |
474 | equally deterministically produce the largest possible set of updates in | |
475 | response to the most common sequence of received updates. | |
42fc5d26 QY |
476 | |
477 | A deterministic order of evaluation tends to imply an additional overhead of | |
c3c5a71f | 478 | sorting over any set of n routes to a destination. The implementation of |
dc1046f7 | 479 | deterministic MED in FRR scales significantly worse than most sorting |
c1a54c05 QY |
480 | algorithms at present, with the number of paths to a given destination. That |
481 | number is often low enough to not cause any issues, but where there are many | |
482 | paths, the deterministic comparison may quickly become increasingly expensive | |
483 | in terms of CPU. | |
484 | ||
485 | Deterministic local evaluation can *not* fix the second, more major, issue of | |
486 | MED however. Which is that the non-transitive preference of routes MED can | |
487 | cause may lead to routing instability or oscillation across multiple speakers | |
488 | in iBGP topologies. This can occur with full-mesh iBGP, but is particularly | |
489 | problematic in non-full-mesh iBGP topologies that further reduce the routing | |
490 | information known to each speaker. This has primarily been documented with iBGP | |
749afd7d RF |
491 | :ref:`route-reflection <bgp-route-reflector>` topologies. However, any |
492 | route-hiding technologies potentially could also exacerbate oscillation with MED. | |
c1a54c05 QY |
493 | |
494 | This second issue occurs where speakers each have only a subset of routes, and | |
495 | there are cycles in the preferences between different combinations of routes - | |
496 | as the undefined order of preference of MED allows - and the routes are | |
497 | distributed in a way that causes the BGP speakers to 'chase' those cycles. This | |
498 | can occur even if all speakers use a deterministic order of evaluation in route | |
499 | selection. | |
500 | ||
501 | E.g., speaker 4 in AS A might receive a route from speaker 2 in AS X, and from | |
502 | speaker 3 in AS Y; while speaker 5 in AS A might receive that route from | |
503 | speaker 1 in AS Y. AS Y might set a MED of 200 at speaker 1, and 100 at speaker | |
504 | 3. I.e, using ASN:ID:MED to label the speakers: | |
42fc5d26 QY |
505 | |
506 | :: | |
507 | ||
c1a54c05 QY |
508 | . |
509 | /---------------\\ | |
42fc5d26 | 510 | X:2------|--A:4-------A:5--|-Y:1:200 |
c1a54c05 QY |
511 | Y:3:100--|-/ | |
512 | \\---------------/ | |
c3c5a71f | 513 | |
42fc5d26 | 514 | |
42fc5d26 | 515 | |
c1a54c05 QY |
516 | Assuming all other metrics are equal (AS_PATH, ORIGIN, 0 IGP costs), then based |
517 | on the RFC4271 decision process speaker 4 will choose X:2 over Y:3:100, based | |
518 | on the lower ID of 2. Speaker 4 advertises X:2 to speaker 5. Speaker 5 will | |
519 | continue to prefer Y:1:200 based on the ID, and advertise this to speaker 4. | |
520 | Speaker 4 will now have the full set of routes, and the Y:1:200 it receives | |
521 | from 5 will beat X:2, but when speaker 4 compares Y:1:200 to Y:3:100 the MED | |
522 | check now becomes active as the ASes match, and now Y:3:100 is preferred. | |
523 | Speaker 4 therefore now advertises Y:3:100 to 5, which will also agrees that | |
524 | Y:3:100 is preferred to Y:1:200, and so withdraws the latter route from 4. | |
525 | Speaker 4 now has only X:2 and Y:3:100, and X:2 beats Y:3:100, and so speaker 4 | |
526 | implicitly updates its route to speaker 5 to X:2. Speaker 5 sees that Y:1:200 | |
527 | beats X:2 based on the ID, and advertises Y:1:200 to speaker 4, and the cycle | |
528 | continues. | |
42fc5d26 QY |
529 | |
530 | The root cause is the lack of a clear order of preference caused by how MED | |
531 | sometimes is and sometimes is not compared, leading to this cycle in the | |
532 | preferences between the routes: | |
533 | ||
534 | :: | |
535 | ||
c1a54c05 QY |
536 | . |
537 | /---> X:2 ---beats---> Y:3:100 --\\ | |
538 | | | | |
539 | | | | |
540 | \\---beats--- Y:1:200 <---beats---/ | |
c3c5a71f | 541 | |
42fc5d26 | 542 | |
42fc5d26 QY |
543 | |
544 | This particular type of oscillation in full-mesh iBGP topologies can be | |
545 | avoided by speakers preferring already selected, external routes rather than | |
c1a54c05 QY |
546 | choosing to update to new a route based on a post-MED metric (e.g. router-ID), |
547 | at the cost of a non-deterministic selection process. FRR implements this, as | |
548 | do many other implementations, so long as it is not overridden by setting | |
9e146a81 | 549 | :clicmd:`bgp bestpath compare-routerid`, and see also |
8fcedbd2 | 550 | :ref:`bgp-route-selection`. |
42fc5d26 QY |
551 | |
552 | However, more complex and insidious cycles of oscillation are possible with | |
c3c5a71f | 553 | iBGP route-reflection, which are not so easily avoided. These have been |
c1a54c05 QY |
554 | documented in various places. See, e.g.: |
555 | ||
556 | - [bgp-route-osci-cond]_ | |
557 | - [stable-flexible-ibgp]_ | |
558 | - [ibgp-correctness]_ | |
559 | ||
560 | for concrete examples and further references. | |
561 | ||
562 | There is as of this writing *no* known way to use MED for its original purpose; | |
563 | *and* reduce routing information in iBGP topologies; *and* be sure to avoid the | |
564 | instability problems of MED due the non-transitive routing preferences it can | |
565 | induce; in general on arbitrary networks. | |
566 | ||
567 | There may be iBGP topology specific ways to reduce the instability risks, even | |
568 | while using MED, e.g.: by constraining the reflection topology and by tuning | |
013f9762 | 569 | IGP costs between route-reflector clusters, see :rfc:`3345` for details. In the |
c1a54c05 QY |
570 | near future, the Add-Path extension to BGP may also solve MED oscillation while |
571 | still allowing MED to be used as intended, by distributing "best-paths per | |
572 | neighbour AS". This would be at the cost of distributing at least as many | |
573 | routes to all speakers as a full-mesh iBGP would, if not more, while also | |
574 | imposing similar CPU overheads as the "Deterministic MED" feature at each | |
575 | Add-Path reflector. | |
42fc5d26 QY |
576 | |
577 | More generally, the instability problems that MED can introduce on more | |
578 | complex, non-full-mesh, iBGP topologies may be avoided either by: | |
579 | ||
013f9762 | 580 | - Setting :clicmd:`bgp always-compare-med`, however this allows MED to be compared |
42fc5d26 QY |
581 | across values set by different neighbour ASes, which may not produce |
582 | coherent desirable results, of itself. | |
4b44467c | 583 | - Effectively ignoring MED by setting MED to the same value (e.g.: 0) using |
013f9762 QY |
584 | :clicmd:`set metric METRIC` on all received routes, in combination with |
585 | setting :clicmd:`bgp always-compare-med` on all speakers. This is the simplest | |
42fc5d26 QY |
586 | and most performant way to avoid MED oscillation issues, where an AS is happy |
587 | not to allow neighbours to inject this problematic metric. | |
588 | ||
42fc5d26 QY |
589 | As MED is evaluated after the AS_PATH length check, another possible use for |
590 | MED is for intra-AS steering of routes with equal AS_PATH length, as an | |
c1a54c05 QY |
591 | extension of the last case above. As MED is evaluated before IGP metric, this |
592 | can allow cold-potato routing to be implemented to send traffic to preferred | |
593 | hand-offs with neighbours, rather than the closest hand-off according to the | |
594 | IGP metric. | |
595 | ||
596 | Note that even if action is taken to address the MED non-transitivity issues, | |
597 | other oscillations may still be possible. E.g., on IGP cost if iBGP and IGP | |
598 | topologies are at cross-purposes with each other - see the Flavel and Roughan | |
599 | paper above for an example. Hence the guideline that the iBGP topology should | |
600 | follow the IGP topology. | |
601 | ||
c3c5a71f | 602 | .. index:: bgp deterministic-med |
29adcd50 | 603 | .. clicmd:: bgp deterministic-med |
42fc5d26 | 604 | |
c1a54c05 QY |
605 | Carry out route-selection in way that produces deterministic answers |
606 | locally, even in the face of MED and the lack of a well-defined order of | |
607 | preference it can induce on routes. Without this option the preferred route | |
608 | with MED may be determined largely by the order that routes were received | |
609 | in. | |
42fc5d26 | 610 | |
c1a54c05 QY |
611 | Setting this option will have a performance cost that may be noticeable when |
612 | there are many routes for each destination. Currently in FRR it is | |
613 | implemented in a way that scales poorly as the number of routes per | |
614 | destination increases. | |
42fc5d26 | 615 | |
c1a54c05 | 616 | The default is that this option is not set. |
42fc5d26 QY |
617 | |
618 | Note that there are other sources of indeterminism in the route selection | |
619 | process, specifically, the preference for older and already selected routes | |
8fcedbd2 | 620 | from eBGP peers, :ref:`bgp-route-selection`. |
42fc5d26 | 621 | |
c3c5a71f | 622 | .. index:: bgp always-compare-med |
29adcd50 | 623 | .. clicmd:: bgp always-compare-med |
42fc5d26 | 624 | |
c1a54c05 QY |
625 | Always compare the MED on routes, even when they were received from |
626 | different neighbouring ASes. Setting this option makes the order of | |
627 | preference of routes more defined, and should eliminate MED induced | |
628 | oscillations. | |
42fc5d26 | 629 | |
c1a54c05 | 630 | If using this option, it may also be desirable to use |
9e146a81 | 631 | :clicmd:`set metric METRIC` to set MED to 0 on routes received from external |
c1a54c05 | 632 | neighbours. |
42fc5d26 | 633 | |
9e146a81 QY |
634 | This option can be used, together with :clicmd:`set metric METRIC` to use |
635 | MED as an intra-AS metric to steer equal-length AS_PATH routes to, e.g., | |
636 | desired exit points. | |
42fc5d26 | 637 | |
0efdf0fe | 638 | .. _bgp-network: |
42fc5d26 | 639 | |
8fcedbd2 QY |
640 | Networks |
641 | -------- | |
42fc5d26 | 642 | |
c1a54c05 QY |
643 | .. index:: network A.B.C.D/M |
644 | .. clicmd:: network A.B.C.D/M | |
42fc5d26 | 645 | |
9eb95b3b | 646 | This command adds the announcement network. |
c3c5a71f | 647 | |
9eb95b3b QY |
648 | .. code-block:: frr |
649 | ||
650 | router bgp 1 | |
651 | address-family ipv4 unicast | |
652 | network 10.0.0.0/8 | |
653 | exit-address-family | |
42fc5d26 | 654 | |
c1a54c05 QY |
655 | This configuration example says that network 10.0.0.0/8 will be |
656 | announced to all neighbors. Some vendors' routers don't advertise | |
657 | routes if they aren't present in their IGP routing tables; `bgpd` | |
658 | doesn't care about IGP routes when announcing its routes. | |
c3c5a71f | 659 | |
c1a54c05 QY |
660 | .. index:: no network A.B.C.D/M |
661 | .. clicmd:: no network A.B.C.D/M | |
42fc5d26 | 662 | |
8fcedbd2 | 663 | .. _bgp-route-aggregation: |
42fc5d26 QY |
664 | |
665 | Route Aggregation | |
666 | ----------------- | |
667 | ||
5101fece | 668 | .. _bgp-route-aggregation-ipv4: |
669 | ||
670 | Route Aggregation-IPv4 Address Family | |
671 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
672 | ||
c1a54c05 QY |
673 | .. index:: aggregate-address A.B.C.D/M |
674 | .. clicmd:: aggregate-address A.B.C.D/M | |
c3c5a71f | 675 | |
c1a54c05 | 676 | This command specifies an aggregate address. |
42fc5d26 | 677 | |
c1a54c05 QY |
678 | .. index:: aggregate-address A.B.C.D/M as-set |
679 | .. clicmd:: aggregate-address A.B.C.D/M as-set | |
42fc5d26 | 680 | |
c1a54c05 QY |
681 | This command specifies an aggregate address. Resulting routes include |
682 | AS set. | |
42fc5d26 | 683 | |
c1a54c05 QY |
684 | .. index:: aggregate-address A.B.C.D/M summary-only |
685 | .. clicmd:: aggregate-address A.B.C.D/M summary-only | |
c3c5a71f | 686 | |
d1e7591e | 687 | This command specifies an aggregate address. Aggregated routes will |
c1a54c05 | 688 | not be announce. |
42fc5d26 | 689 | |
c1a54c05 QY |
690 | .. index:: no aggregate-address A.B.C.D/M |
691 | .. clicmd:: no aggregate-address A.B.C.D/M | |
5101fece | 692 | |
693 | This command removes an aggregate address. | |
694 | ||
695 | ||
696 | This configuration example setup the aggregate-address under | |
697 | ipv4 address-family. | |
698 | ||
699 | .. code-block:: frr | |
700 | ||
701 | router bgp 1 | |
702 | address-family ipv4 unicast | |
703 | aggregate-address 10.0.0.0/8 | |
704 | aggregate-address 20.0.0.0/8 as-set | |
705 | aggregate-address 40.0.0.0/8 summary-only | |
706 | exit-address-family | |
707 | ||
708 | ||
709 | .. _bgp-route-aggregation-ipv6: | |
710 | ||
711 | Route Aggregation-IPv6 Address Family | |
712 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
713 | ||
714 | .. index:: aggregate-address X:X::X:X/M | |
715 | .. clicmd:: aggregate-address X:X::X:X/M | |
716 | ||
717 | This command specifies an aggregate address. | |
718 | ||
719 | .. index:: aggregate-address X:X::X:X/M as-set | |
720 | .. clicmd:: aggregate-address X:X::X:X/M as-set | |
721 | ||
722 | This command specifies an aggregate address. Resulting routes include | |
723 | AS set. | |
724 | ||
725 | .. index:: aggregate-address X:X::X:X/M summary-only | |
726 | .. clicmd:: aggregate-address X:X::X:X/M summary-only | |
727 | ||
728 | This command specifies an aggregate address. Aggregated routes will | |
729 | not be announce. | |
730 | ||
731 | .. index:: no aggregate-address X:X::X:X/M | |
732 | .. clicmd:: no aggregate-address X:X::X:X/M | |
733 | ||
734 | This command removes an aggregate address. | |
735 | ||
736 | ||
737 | This configuration example setup the aggregate-address under | |
738 | ipv4 address-family. | |
739 | ||
740 | .. code-block:: frr | |
741 | ||
742 | router bgp 1 | |
743 | address-family ipv6 unicast | |
744 | aggregate-address 10::0/64 | |
745 | aggregate-address 20::0/64 as-set | |
746 | aggregate-address 40::0/64 summary-only | |
747 | exit-address-family | |
c3c5a71f | 748 | |
8fcedbd2 | 749 | .. _bgp-redistribute-to-bgp: |
42fc5d26 | 750 | |
8fcedbd2 QY |
751 | Redistribution |
752 | -------------- | |
42fc5d26 | 753 | |
c3c5a71f | 754 | .. index:: redistribute kernel |
29adcd50 | 755 | .. clicmd:: redistribute kernel |
42fc5d26 | 756 | |
c1a54c05 | 757 | Redistribute kernel route to BGP process. |
42fc5d26 | 758 | |
c3c5a71f | 759 | .. index:: redistribute static |
29adcd50 | 760 | .. clicmd:: redistribute static |
42fc5d26 | 761 | |
c1a54c05 | 762 | Redistribute static route to BGP process. |
42fc5d26 | 763 | |
c3c5a71f | 764 | .. index:: redistribute connected |
29adcd50 | 765 | .. clicmd:: redistribute connected |
42fc5d26 | 766 | |
c1a54c05 | 767 | Redistribute connected route to BGP process. |
42fc5d26 | 768 | |
c3c5a71f | 769 | .. index:: redistribute rip |
29adcd50 | 770 | .. clicmd:: redistribute rip |
42fc5d26 | 771 | |
c1a54c05 | 772 | Redistribute RIP route to BGP process. |
42fc5d26 | 773 | |
c3c5a71f | 774 | .. index:: redistribute ospf |
29adcd50 | 775 | .. clicmd:: redistribute ospf |
42fc5d26 | 776 | |
c1a54c05 | 777 | Redistribute OSPF route to BGP process. |
42fc5d26 | 778 | |
c3c5a71f | 779 | .. index:: redistribute vpn |
29adcd50 | 780 | .. clicmd:: redistribute vpn |
42fc5d26 | 781 | |
c1a54c05 | 782 | Redistribute VNC routes to BGP process. |
42fc5d26 | 783 | |
c1a54c05 QY |
784 | .. index:: update-delay MAX-DELAY |
785 | .. clicmd:: update-delay MAX-DELAY | |
c3c5a71f | 786 | |
c1a54c05 QY |
787 | .. index:: update-delay MAX-DELAY ESTABLISH-WAIT |
788 | .. clicmd:: update-delay MAX-DELAY ESTABLISH-WAIT | |
c3c5a71f | 789 | |
c1a54c05 QY |
790 | This feature is used to enable read-only mode on BGP process restart or when |
791 | BGP process is cleared using 'clear ip bgp \*'. When applicable, read-only | |
792 | mode would begin as soon as the first peer reaches Established status and a | |
793 | timer for max-delay seconds is started. | |
42fc5d26 | 794 | |
c1a54c05 QY |
795 | During this mode BGP doesn't run any best-path or generate any updates to its |
796 | peers. This mode continues until: | |
42fc5d26 | 797 | |
c1a54c05 QY |
798 | 1. All the configured peers, except the shutdown peers, have sent explicit EOR |
799 | (End-Of-RIB) or an implicit-EOR. The first keep-alive after BGP has reached | |
800 | Established is considered an implicit-EOR. | |
801 | If the establish-wait optional value is given, then BGP will wait for | |
d1e7591e | 802 | peers to reach established from the beginning of the update-delay till the |
c1a54c05 QY |
803 | establish-wait period is over, i.e. the minimum set of established peers for |
804 | which EOR is expected would be peers established during the establish-wait | |
805 | window, not necessarily all the configured neighbors. | |
806 | 2. max-delay period is over. | |
42fc5d26 | 807 | |
c1a54c05 QY |
808 | On hitting any of the above two conditions, BGP resumes the decision process |
809 | and generates updates to its peers. | |
42fc5d26 | 810 | |
c1a54c05 | 811 | Default max-delay is 0, i.e. the feature is off by default. |
c3c5a71f | 812 | |
c1a54c05 QY |
813 | .. index:: table-map ROUTE-MAP-NAME |
814 | .. clicmd:: table-map ROUTE-MAP-NAME | |
42fc5d26 | 815 | |
c1a54c05 QY |
816 | This feature is used to apply a route-map on route updates from BGP to |
817 | Zebra. All the applicable match operations are allowed, such as match on | |
818 | prefix, next-hop, communities, etc. Set operations for this attach-point are | |
819 | limited to metric and next-hop only. Any operation of this feature does not | |
820 | affect BGPs internal RIB. | |
42fc5d26 | 821 | |
c1a54c05 QY |
822 | Supported for ipv4 and ipv6 address families. It works on multi-paths as |
823 | well, however, metric setting is based on the best-path only. | |
42fc5d26 | 824 | |
8fcedbd2 | 825 | .. _bgp-peers: |
42fc5d26 | 826 | |
8fcedbd2 QY |
827 | Peers |
828 | ----- | |
42fc5d26 | 829 | |
8fcedbd2 | 830 | .. _bgp-defining-peers: |
42fc5d26 | 831 | |
8fcedbd2 QY |
832 | Defining Peers |
833 | ^^^^^^^^^^^^^^ | |
42fc5d26 | 834 | |
c1a54c05 QY |
835 | .. index:: neighbor PEER remote-as ASN |
836 | .. clicmd:: neighbor PEER remote-as ASN | |
42fc5d26 | 837 | |
c1a54c05 | 838 | Creates a new neighbor whose remote-as is ASN. PEER can be an IPv4 address |
9eb95b3b | 839 | or an IPv6 address or an interface to use for the connection. |
76bd1499 | 840 | |
9eb95b3b QY |
841 | .. code-block:: frr |
842 | ||
843 | router bgp 1 | |
844 | neighbor 10.0.0.1 remote-as 2 | |
76bd1499 | 845 | |
c1a54c05 | 846 | In this case my router, in AS-1, is trying to peer with AS-2 at 10.0.0.1. |
76bd1499 | 847 | |
c1a54c05 | 848 | This command must be the first command used when configuring a neighbor. If |
9eb95b3b | 849 | the remote-as is not specified, *bgpd* will complain like this: :: |
76bd1499 | 850 | |
c1a54c05 | 851 | can't find neighbor 10.0.0.1 |
c3c5a71f | 852 | |
5413757f DS |
853 | .. index:: neighbor PEER remote-as internal |
854 | .. clicmd:: neighbor PEER remote-as internal | |
855 | ||
856 | Create a peer as you would when you specify an ASN, except that if the | |
857 | peers ASN is different than mine as specified under the :clicmd:`router bgp ASN` | |
858 | command the connection will be denied. | |
859 | ||
860 | .. index:: neighbor PEER remote-as external | |
861 | .. clicmd:: neighbor PEER remote-as external | |
862 | ||
863 | Create a peer as you would when you specify an ASN, except that if the | |
864 | peers ASN is the same as mine as specified under the :clicmd:`router bgp ASN` | |
865 | command the connection will be denied. | |
42fc5d26 | 866 | |
d7b9898c DA |
867 | .. index:: [no] bgp listen range <A.B.C.D/M|X:X::X:X/M> peer-group PGNAME |
868 | .. clicmd:: [no] bgp listen range <A.B.C.D/M|X:X::X:X/M> peer-group PGNAME | |
d79e0e08 QY |
869 | |
870 | Accept connections from any peers in the specified prefix. Configuration | |
871 | from the specified peer-group is used to configure these peers. | |
872 | ||
873 | .. note:: | |
874 | ||
875 | When using BGP listen ranges, if the associated peer group has TCP MD5 | |
876 | authentication configured, your kernel must support this on prefixes. On | |
877 | Linux, this support was added in kernel version 4.14. If your kernel does | |
878 | not support this feature you will get a warning in the log file, and the | |
879 | listen range will only accept connections from peers without MD5 configured. | |
880 | ||
881 | Additionally, we have observed that when using this option at scale (several | |
882 | hundred peers) the kernel may hit its option memory limit. In this situation | |
883 | you will see error messages like: | |
884 | ||
885 | ``bgpd: sockopt_tcp_signature: setsockopt(23): Cannot allocate memory`` | |
886 | ||
887 | In this case you need to increase the value of the sysctl | |
888 | ``net.core.optmem_max`` to allow the kernel to allocate the necessary option | |
889 | memory. | |
890 | ||
8fcedbd2 | 891 | .. _bgp-configuring-peers: |
42fc5d26 | 892 | |
8fcedbd2 QY |
893 | Configuring Peers |
894 | ^^^^^^^^^^^^^^^^^ | |
42fc5d26 | 895 | |
c0868e8b QY |
896 | .. index:: [no] neighbor PEER shutdown |
897 | .. clicmd:: [no] neighbor PEER shutdown | |
c3c5a71f | 898 | |
c1a54c05 QY |
899 | Shutdown the peer. We can delete the neighbor's configuration by |
900 | ``no neighbor PEER remote-as ASN`` but all configuration of the neighbor | |
901 | will be deleted. When you want to preserve the configuration, but want to | |
902 | drop the BGP peer, use this syntax. | |
c3c5a71f | 903 | |
c0868e8b QY |
904 | .. index:: [no] neighbor PEER disable-connected-check |
905 | .. clicmd:: [no] neighbor PEER disable-connected-check | |
c3c5a71f | 906 | |
c0868e8b QY |
907 | Allow peerings between directly connected eBGP peers using loopback |
908 | addresses. | |
c3c5a71f | 909 | |
c0868e8b QY |
910 | .. index:: [no] neighbor PEER ebgp-multihop |
911 | .. clicmd:: [no] neighbor PEER ebgp-multihop | |
42fc5d26 | 912 | |
c0868e8b QY |
913 | .. index:: [no] neighbor PEER description ... |
914 | .. clicmd:: [no] neighbor PEER description ... | |
42fc5d26 | 915 | |
c1a54c05 | 916 | Set description of the peer. |
42fc5d26 | 917 | |
c0868e8b QY |
918 | .. index:: [no] neighbor PEER version VERSION |
919 | .. clicmd:: [no] neighbor PEER version VERSION | |
42fc5d26 | 920 | |
4da7fda3 QY |
921 | Set up the neighbor's BGP version. `version` can be `4`, `4+` or `4-`. BGP |
922 | version `4` is the default value used for BGP peering. BGP version `4+` | |
923 | means that the neighbor supports Multiprotocol Extensions for BGP-4. BGP | |
924 | version `4-` is similar but the neighbor speaks the old Internet-Draft | |
925 | revision 00's Multiprotocol Extensions for BGP-4. Some routing software is | |
926 | still using this version. | |
42fc5d26 | 927 | |
c0868e8b QY |
928 | .. index:: [no] neighbor PEER interface IFNAME |
929 | .. clicmd:: [no] neighbor PEER interface IFNAME | |
42fc5d26 | 930 | |
c1a54c05 QY |
931 | When you connect to a BGP peer over an IPv6 link-local address, you have to |
932 | specify the IFNAME of the interface used for the connection. To specify | |
933 | IPv4 session addresses, see the ``neighbor PEER update-source`` command | |
934 | below. | |
42fc5d26 | 935 | |
c1a54c05 QY |
936 | This command is deprecated and may be removed in a future release. Its use |
937 | should be avoided. | |
42fc5d26 | 938 | |
c0868e8b QY |
939 | .. index:: [no] neighbor PEER next-hop-self [all] |
940 | .. clicmd:: [no] neighbor PEER next-hop-self [all] | |
42fc5d26 | 941 | |
c1a54c05 QY |
942 | This command specifies an announced route's nexthop as being equivalent to |
943 | the address of the bgp router if it is learned via eBGP. If the optional | |
d1e7591e | 944 | keyword `all` is specified the modification is done also for routes learned |
c1a54c05 | 945 | via iBGP. |
42fc5d26 | 946 | |
c0868e8b QY |
947 | .. index:: [no] neighbor PEER update-source <IFNAME|ADDRESS> |
948 | .. clicmd:: [no] neighbor PEER update-source <IFNAME|ADDRESS> | |
42fc5d26 | 949 | |
c1a54c05 QY |
950 | Specify the IPv4 source address to use for the :abbr:`BGP` session to this |
951 | neighbour, may be specified as either an IPv4 address directly or as an | |
952 | interface name (in which case the *zebra* daemon MUST be running in order | |
9eb95b3b QY |
953 | for *bgpd* to be able to retrieve interface state). |
954 | ||
955 | .. code-block:: frr | |
42fc5d26 | 956 | |
c1a54c05 QY |
957 | router bgp 64555 |
958 | neighbor foo update-source 192.168.0.1 | |
959 | neighbor bar update-source lo0 | |
42fc5d26 | 960 | |
42fc5d26 | 961 | |
c0868e8b QY |
962 | .. index:: [no] neighbor PEER default-originate |
963 | .. clicmd:: [no] neighbor PEER default-originate | |
42fc5d26 | 964 | |
4da7fda3 QY |
965 | *bgpd*'s default is to not announce the default route (0.0.0.0/0) even if it |
966 | is in routing table. When you want to announce default routes to the peer, | |
967 | use this command. | |
42fc5d26 | 968 | |
c1a54c05 QY |
969 | .. index:: neighbor PEER port PORT |
970 | .. clicmd:: neighbor PEER port PORT | |
42fc5d26 | 971 | |
c1a54c05 QY |
972 | .. index:: neighbor PEER send-community |
973 | .. clicmd:: neighbor PEER send-community | |
42fc5d26 | 974 | |
c0868e8b QY |
975 | .. index:: [no] neighbor PEER weight WEIGHT |
976 | .. clicmd:: [no] neighbor PEER weight WEIGHT | |
42fc5d26 | 977 | |
c1a54c05 | 978 | This command specifies a default `weight` value for the neighbor's routes. |
42fc5d26 | 979 | |
c0868e8b QY |
980 | .. index:: [no] neighbor PEER maximum-prefix NUMBER |
981 | .. clicmd:: [no] neighbor PEER maximum-prefix NUMBER | |
42fc5d26 | 982 | |
886026c8 QY |
983 | Sets a maximum number of prefixes we can receive from a given peer. If this |
984 | number is exceeded, the BGP session will be destroyed. | |
985 | ||
986 | In practice, it is generally preferable to use a prefix-list to limit what | |
987 | prefixes are received from the peer instead of using this knob. Tearing down | |
988 | the BGP session when a limit is exceeded is far more destructive than merely | |
989 | rejecting undesired prefixes. The prefix-list method is also much more | |
990 | granular and offers much smarter matching criterion than number of received | |
991 | prefixes, making it more suited to implementing policy. | |
992 | ||
993 | .. index:: [no] neighbor PEER local-as AS-NUMBER [no-prepend] [replace-as] | |
994 | .. clicmd:: [no] neighbor PEER local-as AS-NUMBER [no-prepend] [replace-as] | |
42fc5d26 | 995 | |
c1a54c05 QY |
996 | Specify an alternate AS for this BGP process when interacting with the |
997 | specified peer. With no modifiers, the specified local-as is prepended to | |
998 | the received AS_PATH when receiving routing updates from the peer, and | |
999 | prepended to the outgoing AS_PATH (after the process local AS) when | |
1000 | transmitting local routes to the peer. | |
42fc5d26 | 1001 | |
c1a54c05 QY |
1002 | If the no-prepend attribute is specified, then the supplied local-as is not |
1003 | prepended to the received AS_PATH. | |
c3c5a71f | 1004 | |
c1a54c05 QY |
1005 | If the replace-as attribute is specified, then only the supplied local-as is |
1006 | prepended to the AS_PATH when transmitting local-route updates to this peer. | |
c3c5a71f | 1007 | |
c1a54c05 | 1008 | Note that replace-as can only be specified if no-prepend is. |
c3c5a71f | 1009 | |
c1a54c05 | 1010 | This command is only allowed for eBGP peers. |
c3c5a71f | 1011 | |
c0868e8b QY |
1012 | .. index:: [no] neighbor PEER ttl-security hops NUMBER |
1013 | .. clicmd:: [no] neighbor PEER ttl-security hops NUMBER | |
c3c5a71f | 1014 | |
c1a54c05 QY |
1015 | This command enforces Generalized TTL Security Mechanism (GTSM), as |
1016 | specified in RFC 5082. With this command, only neighbors that are the | |
1017 | specified number of hops away will be allowed to become neighbors. This | |
d1e7591e | 1018 | command is mutually exclusive with *ebgp-multihop*. |
42fc5d26 | 1019 | |
19f2b5e8 DS |
1020 | .. index:: [no] neighbor PEER capability extended-nexthop |
1021 | .. clicmd:: [no] neighbor PEER capability extended-nexthop | |
1022 | ||
1023 | Allow bgp to negotiate the extended-nexthop capability with it's peer. | |
1024 | If you are peering over a v6 LL address then this capability is turned | |
1025 | on automatically. If you are peering over a v6 Global Address then | |
1026 | turning on this command will allow BGP to install v4 routes with | |
1027 | v6 nexthops if you do not have v4 configured on interfaces. | |
1028 | ||
eb938189 DS |
1029 | .. index:: [no] bgp fast-external-failover |
1030 | .. clicmd:: [no] bgp fast-external-failover | |
1031 | ||
1032 | This command causes bgp to not take down ebgp peers immediately | |
1033 | when a link flaps. `bgp fast-external-failover` is the default | |
1034 | and will not be displayed as part of a `show run`. The no form | |
1035 | of the command turns off this ability. | |
1036 | ||
bc132029 DS |
1037 | .. index:: [no] bgp default ipv4-unicast |
1038 | .. clicmd:: [no] bgp default ipv4-unicast | |
1039 | ||
1040 | This command allows the user to specify that v4 peering is turned | |
1041 | on by default or not. This command defaults to on and is not displayed. | |
1042 | The `no bgp default ipv4-unicast` form of the command is displayed. | |
1043 | ||
8fcedbd2 | 1044 | .. _bgp-peer-filtering: |
42fc5d26 | 1045 | |
8fcedbd2 QY |
1046 | Peer Filtering |
1047 | ^^^^^^^^^^^^^^ | |
42fc5d26 | 1048 | |
c1a54c05 QY |
1049 | .. index:: neighbor PEER distribute-list NAME [in|out] |
1050 | .. clicmd:: neighbor PEER distribute-list NAME [in|out] | |
42fc5d26 | 1051 | |
c1a54c05 QY |
1052 | This command specifies a distribute-list for the peer. `direct` is |
1053 | ``in`` or ``out``. | |
42fc5d26 | 1054 | |
c3c5a71f | 1055 | .. index:: neighbor PEER prefix-list NAME [in|out] |
29adcd50 | 1056 | .. clicmd:: neighbor PEER prefix-list NAME [in|out] |
42fc5d26 | 1057 | |
c1a54c05 | 1058 | .. index:: neighbor PEER filter-list NAME [in|out] |
29adcd50 | 1059 | .. clicmd:: neighbor PEER filter-list NAME [in|out] |
42fc5d26 | 1060 | |
c1a54c05 QY |
1061 | .. index:: neighbor PEER route-map NAME [in|out] |
1062 | .. clicmd:: neighbor PEER route-map NAME [in|out] | |
42fc5d26 | 1063 | |
c1a54c05 | 1064 | Apply a route-map on the neighbor. `direct` must be `in` or `out`. |
42fc5d26 | 1065 | |
c3c5a71f | 1066 | .. index:: bgp route-reflector allow-outbound-policy |
29adcd50 | 1067 | .. clicmd:: bgp route-reflector allow-outbound-policy |
42fc5d26 | 1068 | |
c1a54c05 QY |
1069 | By default, attribute modification via route-map policy out is not reflected |
1070 | on reflected routes. This option allows the modifications to be reflected as | |
1071 | well. Once enabled, it affects all reflected routes. | |
42fc5d26 | 1072 | |
0efdf0fe | 1073 | .. _bgp-peer-group: |
42fc5d26 | 1074 | |
8fcedbd2 QY |
1075 | Peer Groups |
1076 | ^^^^^^^^^^^ | |
42fc5d26 | 1077 | |
199ad5c4 LB |
1078 | Peer groups are used to help improve scaling by generating the same |
1079 | update information to all members of a peer group. Note that this means | |
1080 | that the routes generated by a member of a peer group will be sent back | |
1081 | to that originating peer with the originator identifier attribute set to | |
1082 | indicated the originating peer. All peers not associated with a | |
1083 | specific peer group are treated as belonging to a default peer group, | |
1084 | and will share updates. | |
1085 | ||
c1a54c05 QY |
1086 | .. index:: neighbor WORD peer-group |
1087 | .. clicmd:: neighbor WORD peer-group | |
42fc5d26 | 1088 | |
c1a54c05 | 1089 | This command defines a new peer group. |
42fc5d26 | 1090 | |
d7b9898c DA |
1091 | .. index:: neighbor PEER peer-group PGNAME |
1092 | .. clicmd:: neighbor PEER peer-group PGNAME | |
c3c5a71f | 1093 | |
c1a54c05 | 1094 | This command bind specific peer to peer group WORD. |
42fc5d26 | 1095 | |
199ad5c4 LB |
1096 | .. index:: neighbor PEER solo |
1097 | .. clicmd:: neighbor PEER solo | |
1098 | ||
1099 | This command is used to indicate that routes advertised by the peer | |
1100 | should not be reflected back to the peer. This command only is only | |
1101 | meaningful when there is a single peer defined in the peer-group. | |
1102 | ||
8fcedbd2 QY |
1103 | Capability Negotiation |
1104 | ^^^^^^^^^^^^^^^^^^^^^^ | |
42fc5d26 | 1105 | |
8fcedbd2 QY |
1106 | .. index:: neighbor PEER strict-capability-match |
1107 | .. clicmd:: neighbor PEER strict-capability-match | |
42fc5d26 | 1108 | |
8fcedbd2 QY |
1109 | .. index:: no neighbor PEER strict-capability-match |
1110 | .. clicmd:: no neighbor PEER strict-capability-match | |
c1a54c05 | 1111 | |
8fcedbd2 QY |
1112 | Strictly compares remote capabilities and local capabilities. If |
1113 | capabilities are different, send Unsupported Capability error then reset | |
1114 | connection. | |
42fc5d26 | 1115 | |
8fcedbd2 QY |
1116 | You may want to disable sending Capability Negotiation OPEN message optional |
1117 | parameter to the peer when remote peer does not implement Capability | |
1118 | Negotiation. Please use *dont-capability-negotiate* command to disable the | |
1119 | feature. | |
42fc5d26 | 1120 | |
8fcedbd2 QY |
1121 | .. index:: neighbor PEER dont-capability-negotiate |
1122 | .. clicmd:: neighbor PEER dont-capability-negotiate | |
42fc5d26 | 1123 | |
8fcedbd2 QY |
1124 | .. index:: no neighbor PEER dont-capability-negotiate |
1125 | .. clicmd:: no neighbor PEER dont-capability-negotiate | |
42fc5d26 | 1126 | |
8fcedbd2 QY |
1127 | Suppress sending Capability Negotiation as OPEN message optional parameter |
1128 | to the peer. This command only affects the peer is configured other than | |
1129 | IPv4 unicast configuration. | |
42fc5d26 | 1130 | |
8fcedbd2 QY |
1131 | When remote peer does not have capability negotiation feature, remote peer |
1132 | will not send any capabilities at all. In that case, bgp configures the peer | |
1133 | with configured capabilities. | |
42fc5d26 | 1134 | |
8fcedbd2 QY |
1135 | You may prefer locally configured capabilities more than the negotiated |
1136 | capabilities even though remote peer sends capabilities. If the peer is | |
1137 | configured by *override-capability*, *bgpd* ignores received capabilities | |
1138 | then override negotiated capabilities with configured values. | |
42fc5d26 | 1139 | |
8fcedbd2 QY |
1140 | .. index:: neighbor PEER override-capability |
1141 | .. clicmd:: neighbor PEER override-capability | |
42fc5d26 | 1142 | |
8fcedbd2 QY |
1143 | .. index:: no neighbor PEER override-capability |
1144 | .. clicmd:: no neighbor PEER override-capability | |
c1a54c05 | 1145 | |
8fcedbd2 QY |
1146 | Override the result of Capability Negotiation with local configuration. |
1147 | Ignore remote peer's capability value. | |
42fc5d26 | 1148 | |
8fcedbd2 | 1149 | .. _bgp-as-path-access-lists: |
42fc5d26 | 1150 | |
8fcedbd2 QY |
1151 | AS Path Access Lists |
1152 | -------------------- | |
42fc5d26 QY |
1153 | |
1154 | AS path access list is user defined AS path. | |
1155 | ||
c3c5a71f | 1156 | .. index:: ip as-path access-list WORD permit|deny LINE |
29adcd50 | 1157 | .. clicmd:: ip as-path access-list WORD permit|deny LINE |
42fc5d26 | 1158 | |
c1a54c05 | 1159 | This command defines a new AS path access list. |
42fc5d26 | 1160 | |
c1a54c05 | 1161 | .. index:: no ip as-path access-list WORD |
29adcd50 | 1162 | .. clicmd:: no ip as-path access-list WORD |
42fc5d26 | 1163 | |
c1a54c05 | 1164 | .. index:: no ip as-path access-list WORD permit|deny LINE |
29adcd50 | 1165 | .. clicmd:: no ip as-path access-list WORD permit|deny LINE |
42fc5d26 | 1166 | |
8fcedbd2 | 1167 | .. _bgp-using-as-path-in-route-map: |
42fc5d26 QY |
1168 | |
1169 | Using AS Path in Route Map | |
1170 | -------------------------- | |
1171 | ||
c3c5a71f | 1172 | .. index:: match as-path WORD |
29adcd50 | 1173 | .. clicmd:: match as-path WORD |
42fc5d26 | 1174 | |
42fc5d26 | 1175 | |
c1a54c05 | 1176 | .. index:: set as-path prepend AS-PATH |
29adcd50 | 1177 | .. clicmd:: set as-path prepend AS-PATH |
42fc5d26 | 1178 | |
c1a54c05 | 1179 | Prepend the given string of AS numbers to the AS_PATH. |
42fc5d26 | 1180 | |
c1a54c05 | 1181 | .. index:: set as-path prepend last-as NUM |
29adcd50 | 1182 | .. clicmd:: set as-path prepend last-as NUM |
c1a54c05 QY |
1183 | |
1184 | Prepend the existing last AS number (the leftmost ASN) to the AS_PATH. | |
42fc5d26 | 1185 | |
0efdf0fe | 1186 | .. _bgp-communities-attribute: |
42fc5d26 | 1187 | |
8fcedbd2 QY |
1188 | Communities Attribute |
1189 | --------------------- | |
42fc5d26 | 1190 | |
8fcedbd2 | 1191 | The BGP communities attribute is widely used for implementing policy routing. |
c1a54c05 QY |
1192 | Network operators can manipulate BGP communities attribute based on their |
1193 | network policy. BGP communities attribute is defined in :rfc:`1997` and | |
1194 | :rfc:`1998`. It is an optional transitive attribute, therefore local policy can | |
1195 | travel through different autonomous system. | |
1196 | ||
8fcedbd2 QY |
1197 | The communities attribute is a set of communities values. Each community value |
1198 | is 4 octet long. The following format is used to define the community value. | |
c1a54c05 | 1199 | |
8fcedbd2 | 1200 | ``AS:VAL`` |
c1a54c05 QY |
1201 | This format represents 4 octet communities value. ``AS`` is high order 2 |
1202 | octet in digit format. ``VAL`` is low order 2 octet in digit format. This | |
1203 | format is useful to define AS oriented policy value. For example, | |
1204 | ``7675:80`` can be used when AS 7675 wants to pass local policy value 80 to | |
1205 | neighboring peer. | |
1206 | ||
8fcedbd2 QY |
1207 | ``internet`` |
1208 | ``internet`` represents well-known communities value 0. | |
c1a54c05 | 1209 | |
cae770d3 C |
1210 | ``graceful-shutdown`` |
1211 | ``graceful-shutdown`` represents well-known communities value | |
1212 | ``GRACEFUL_SHUTDOWN`` ``0xFFFF0000`` ``65535:0``. :rfc:`8326` implements | |
1213 | the purpose Graceful BGP Session Shutdown to reduce the amount of | |
56f0bea7 | 1214 | lost traffic when taking BGP sessions down for maintenance. The use |
cae770d3 C |
1215 | of the community needs to be supported from your peers side to |
1216 | actually have any effect. | |
1217 | ||
1218 | ``accept-own`` | |
1219 | ``accept-own`` represents well-known communities value ``ACCEPT_OWN`` | |
1220 | ``0xFFFF0001`` ``65535:1``. :rfc:`7611` implements a way to signal | |
1221 | to a router to accept routes with a local nexthop address. This | |
1222 | can be the case when doing policing and having traffic having a | |
1223 | nexthop located in another VRF but still local interface to the | |
1224 | router. It is recommended to read the RFC for full details. | |
1225 | ||
1226 | ``route-filter-translated-v4`` | |
1227 | ``route-filter-translated-v4`` represents well-known communities value | |
1228 | ``ROUTE_FILTER_TRANSLATED_v4`` ``0xFFFF0002`` ``65535:2``. | |
1229 | ||
1230 | ``route-filter-v4`` | |
1231 | ``route-filter-v4`` represents well-known communities value | |
1232 | ``ROUTE_FILTER_v4`` ``0xFFFF0003`` ``65535:3``. | |
1233 | ||
1234 | ``route-filter-translated-v6`` | |
1235 | ``route-filter-translated-v6`` represents well-known communities value | |
1236 | ``ROUTE_FILTER_TRANSLATED_v6`` ``0xFFFF0004`` ``65535:4``. | |
1237 | ||
1238 | ``route-filter-v6`` | |
1239 | ``route-filter-v6`` represents well-known communities value | |
1240 | ``ROUTE_FILTER_v6`` ``0xFFFF0005`` ``65535:5``. | |
1241 | ||
1242 | ``llgr-stale`` | |
1243 | ``llgr-stale`` represents well-known communities value ``LLGR_STALE`` | |
1244 | ``0xFFFF0006`` ``65535:6``. | |
56f0bea7 | 1245 | Assigned and intended only for use with routers supporting the |
cae770d3 | 1246 | Long-lived Graceful Restart Capability as described in |
49606d58 | 1247 | [Draft-IETF-uttaro-idr-bgp-persistence]_. |
56f0bea7 | 1248 | Routers receiving routes with this community may (depending on |
cae770d3 C |
1249 | implementation) choose allow to reject or modify routes on the |
1250 | presence or absence of this community. | |
1251 | ||
1252 | ``no-llgr`` | |
1253 | ``no-llgr`` represents well-known communities value ``NO_LLGR`` | |
1254 | ``0xFFFF0007`` ``65535:7``. | |
56f0bea7 | 1255 | Assigned and intended only for use with routers supporting the |
cae770d3 | 1256 | Long-lived Graceful Restart Capability as described in |
49606d58 | 1257 | [Draft-IETF-uttaro-idr-bgp-persistence]_. |
56f0bea7 | 1258 | Routers receiving routes with this community may (depending on |
cae770d3 C |
1259 | implementation) choose allow to reject or modify routes on the |
1260 | presence or absence of this community. | |
1261 | ||
1262 | ``accept-own-nexthop`` | |
1263 | ``accept-own-nexthop`` represents well-known communities value | |
1264 | ``accept-own-nexthop`` ``0xFFFF0008`` ``65535:8``. | |
49606d58 | 1265 | [Draft-IETF-agrewal-idr-accept-own-nexthop]_ describes |
cae770d3 C |
1266 | how to tag and label VPN routes to be able to send traffic between VRFs |
1267 | via an internal layer 2 domain on the same PE device. Refer to | |
49606d58 | 1268 | [Draft-IETF-agrewal-idr-accept-own-nexthop]_ for full details. |
cae770d3 C |
1269 | |
1270 | ``blackhole`` | |
1271 | ``blackhole`` represents well-known communities value ``BLACKHOLE`` | |
1272 | ``0xFFFF029A`` ``65535:666``. :rfc:`7999` documents sending prefixes to | |
1273 | EBGP peers and upstream for the purpose of blackholing traffic. | |
1274 | Prefixes tagged with the this community should normally not be | |
1275 | re-advertised from neighbors of the originating network. It is | |
1276 | recommended upon receiving prefixes tagged with this community to | |
1277 | add ``NO_EXPORT`` and ``NO_ADVERTISE``. | |
1278 | ||
8fcedbd2 | 1279 | ``no-export`` |
c1a54c05 QY |
1280 | ``no-export`` represents well-known communities value ``NO_EXPORT`` |
1281 | ``0xFFFFFF01``. All routes carry this value must not be advertised to | |
1282 | outside a BGP confederation boundary. If neighboring BGP peer is part of BGP | |
1283 | confederation, the peer is considered as inside a BGP confederation | |
1284 | boundary, so the route will be announced to the peer. | |
1285 | ||
8fcedbd2 | 1286 | ``no-advertise`` |
c1a54c05 QY |
1287 | ``no-advertise`` represents well-known communities value ``NO_ADVERTISE`` |
1288 | ``0xFFFFFF02``. All routes carry this value must not be advertise to other | |
1289 | BGP peers. | |
1290 | ||
8fcedbd2 | 1291 | ``local-AS`` |
c1a54c05 QY |
1292 | ``local-AS`` represents well-known communities value ``NO_EXPORT_SUBCONFED`` |
1293 | ``0xFFFFFF03``. All routes carry this value must not be advertised to | |
1294 | external BGP peers. Even if the neighboring router is part of confederation, | |
1295 | it is considered as external BGP peer, so the route will not be announced to | |
1296 | the peer. | |
1297 | ||
cae770d3 C |
1298 | ``no-peer`` |
1299 | ``no-peer`` represents well-known communities value ``NOPEER`` | |
1300 | ``0xFFFFFF04`` ``65535:65284``. :rfc:`3765` is used to communicate to | |
1301 | another network how the originating network want the prefix propagated. | |
1302 | ||
aa9eafa4 QY |
1303 | When the communities attribute is received duplicate community values in the |
1304 | attribute are ignored and value is sorted in numerical order. | |
42fc5d26 | 1305 | |
49606d58 PG |
1306 | .. [Draft-IETF-uttaro-idr-bgp-persistence] <https://tools.ietf.org/id/draft-uttaro-idr-bgp-persistence-04.txt> |
1307 | .. [Draft-IETF-agrewal-idr-accept-own-nexthop] <https://tools.ietf.org/id/draft-agrewal-idr-accept-own-nexthop-00.txt> | |
1308 | ||
0efdf0fe | 1309 | .. _bgp-community-lists: |
42fc5d26 | 1310 | |
8fcedbd2 QY |
1311 | Community Lists |
1312 | ^^^^^^^^^^^^^^^ | |
aa9eafa4 QY |
1313 | Community lists are user defined lists of community attribute values. These |
1314 | lists can be used for matching or manipulating the communities attribute in | |
1315 | UPDATE messages. | |
42fc5d26 | 1316 | |
aa9eafa4 | 1317 | There are two types of community list: |
c1a54c05 | 1318 | |
aa9eafa4 | 1319 | standard |
56f0bea7 | 1320 | This type accepts an explicit value for the attribute. |
aa9eafa4 QY |
1321 | |
1322 | expanded | |
1323 | This type accepts a regular expression. Because the regex must be | |
1324 | interpreted on each use expanded community lists are slower than standard | |
1325 | lists. | |
42fc5d26 | 1326 | |
c3c5a71f | 1327 | .. index:: ip community-list standard NAME permit|deny COMMUNITY |
29adcd50 | 1328 | .. clicmd:: ip community-list standard NAME permit|deny COMMUNITY |
42fc5d26 | 1329 | |
aa9eafa4 QY |
1330 | This command defines a new standard community list. ``COMMUNITY`` is |
1331 | communities value. The ``COMMUNITY`` is compiled into community structure. | |
1332 | We can define multiple community list under same name. In that case match | |
1333 | will happen user defined order. Once the community list matches to | |
1334 | communities attribute in BGP updates it return permit or deny by the | |
1335 | community list definition. When there is no matched entry, deny will be | |
1336 | returned. When ``COMMUNITY`` is empty it matches to any routes. | |
42fc5d26 | 1337 | |
aa9eafa4 QY |
1338 | .. index:: ip community-list expanded NAME permit|deny COMMUNITY |
1339 | .. clicmd:: ip community-list expanded NAME permit|deny COMMUNITY | |
42fc5d26 | 1340 | |
aa9eafa4 QY |
1341 | This command defines a new expanded community list. ``COMMUNITY`` is a |
1342 | string expression of communities attribute. ``COMMUNITY`` can be a regular | |
1343 | expression (:ref:`bgp-regular-expressions`) to match the communities | |
47f47873 PG |
1344 | attribute in BGP updates. The expanded community is only used to filter, |
1345 | not `set` actions. | |
42fc5d26 | 1346 | |
aa9eafa4 QY |
1347 | .. deprecated:: 5.0 |
1348 | It is recommended to use the more explicit versions of this command. | |
42fc5d26 | 1349 | |
aa9eafa4 QY |
1350 | .. index:: ip community-list NAME permit|deny COMMUNITY |
1351 | .. clicmd:: ip community-list NAME permit|deny COMMUNITY | |
1352 | ||
1353 | When the community list type is not specified, the community list type is | |
1354 | automatically detected. If ``COMMUNITY`` can be compiled into communities | |
1355 | attribute, the community list is defined as a standard community list. | |
1356 | Otherwise it is defined as an expanded community list. This feature is left | |
1357 | for backward compatibility. Use of this feature is not recommended. | |
42fc5d26 | 1358 | |
42fc5d26 | 1359 | |
aa9eafa4 QY |
1360 | .. index:: no ip community-list [standard|expanded] NAME |
1361 | .. clicmd:: no ip community-list [standard|expanded] NAME | |
42fc5d26 | 1362 | |
aa9eafa4 QY |
1363 | Deletes the community list specified by ``NAME``. All community lists share |
1364 | the same namespace, so it's not necessary to specify ``standard`` or | |
1365 | ``expanded``; these modifiers are purely aesthetic. | |
42fc5d26 | 1366 | |
aa9eafa4 QY |
1367 | .. index:: show ip community-list [NAME] |
1368 | .. clicmd:: show ip community-list [NAME] | |
42fc5d26 | 1369 | |
aa9eafa4 QY |
1370 | Displays community list information. When ``NAME`` is specified the |
1371 | specified community list's information is shown. | |
c3c5a71f | 1372 | |
c1a54c05 | 1373 | :: |
76bd1499 | 1374 | |
c1a54c05 QY |
1375 | # show ip community-list |
1376 | Named Community standard list CLIST | |
1377 | permit 7675:80 7675:100 no-export | |
1378 | deny internet | |
1379 | Named Community expanded list EXPAND | |
1380 | permit : | |
76bd1499 | 1381 | |
c1a54c05 QY |
1382 | # show ip community-list CLIST |
1383 | Named Community standard list CLIST | |
1384 | permit 7675:80 7675:100 no-export | |
1385 | deny internet | |
42fc5d26 | 1386 | |
42fc5d26 | 1387 | |
8fcedbd2 | 1388 | .. _bgp-numbered-community-lists: |
42fc5d26 | 1389 | |
8fcedbd2 QY |
1390 | Numbered Community Lists |
1391 | ^^^^^^^^^^^^^^^^^^^^^^^^ | |
42fc5d26 QY |
1392 | |
1393 | When number is used for BGP community list name, the number has | |
c3c5a71f QY |
1394 | special meanings. Community list number in the range from 1 and 99 is |
1395 | standard community list. Community list number in the range from 100 | |
1396 | to 199 is expanded community list. These community lists are called | |
1397 | as numbered community lists. On the other hand normal community lists | |
42fc5d26 QY |
1398 | is called as named community lists. |
1399 | ||
29adcd50 | 1400 | .. index:: ip community-list (1-99) permit|deny COMMUNITY |
29adcd50 | 1401 | .. clicmd:: ip community-list (1-99) permit|deny COMMUNITY |
42fc5d26 | 1402 | |
aa9eafa4 QY |
1403 | This command defines a new community list. The argument to (1-99) defines |
1404 | the list identifier. | |
42fc5d26 | 1405 | |
c1a54c05 | 1406 | .. index:: ip community-list (100-199) permit|deny COMMUNITY |
29adcd50 | 1407 | .. clicmd:: ip community-list (100-199) permit|deny COMMUNITY |
42fc5d26 | 1408 | |
aa9eafa4 QY |
1409 | This command defines a new expanded community list. The argument to |
1410 | (100-199) defines the list identifier. | |
42fc5d26 | 1411 | |
8fcedbd2 | 1412 | .. _bgp-using-communities-in-route-map: |
42fc5d26 | 1413 | |
8fcedbd2 QY |
1414 | Using Communities in Route Maps |
1415 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
42fc5d26 | 1416 | |
aa9eafa4 QY |
1417 | In :ref:`route-map` we can match on or set the BGP communities attribute. Using |
1418 | this feature network operator can implement their network policy based on BGP | |
1419 | communities attribute. | |
42fc5d26 | 1420 | |
aa9eafa4 | 1421 | The ollowing commands can be used in route maps: |
42fc5d26 | 1422 | |
aa9eafa4 QY |
1423 | .. index:: match community WORD exact-match [exact-match] |
1424 | .. clicmd:: match community WORD exact-match [exact-match] | |
42fc5d26 | 1425 | |
c1a54c05 QY |
1426 | This command perform match to BGP updates using community list WORD. When |
1427 | the one of BGP communities value match to the one of communities value in | |
d1e7591e | 1428 | community list, it is match. When `exact-match` keyword is specified, match |
c1a54c05 QY |
1429 | happen only when BGP updates have completely same communities value |
1430 | specified in the community list. | |
42fc5d26 | 1431 | |
aa9eafa4 QY |
1432 | .. index:: set community <none|COMMUNITY> additive |
1433 | .. clicmd:: set community <none|COMMUNITY> additive | |
42fc5d26 | 1434 | |
aa9eafa4 QY |
1435 | This command sets the community value in BGP updates. If the attribute is |
1436 | already configured, the newly provided value replaces the old one unless the | |
1437 | ``additive`` keyword is specified, in which case the new value is appended | |
1438 | to the existing value. | |
42fc5d26 | 1439 | |
aa9eafa4 QY |
1440 | If ``none`` is specified as the community value, the communities attribute |
1441 | is not sent. | |
42fc5d26 | 1442 | |
47f47873 PG |
1443 | It is not possible to set an expanded community list. |
1444 | ||
c1a54c05 | 1445 | .. index:: set comm-list WORD delete |
29adcd50 | 1446 | .. clicmd:: set comm-list WORD delete |
c1a54c05 | 1447 | |
aa9eafa4 QY |
1448 | This command remove communities value from BGP communities attribute. The |
1449 | ``word`` is community list name. When BGP route's communities value matches | |
1450 | to the community list ``word``, the communities value is removed. When all | |
1451 | of communities value is removed eventually, the BGP update's communities | |
1452 | attribute is completely removed. | |
42fc5d26 | 1453 | |
8fcedbd2 | 1454 | .. _bgp-communities-example: |
c1a54c05 | 1455 | |
8fcedbd2 QY |
1456 | Example Configuration |
1457 | ^^^^^^^^^^^^^^^^^^^^^ | |
9eb95b3b | 1458 | |
8fcedbd2 QY |
1459 | The following configuration is exemplary of the most typical usage of BGP |
1460 | communities attribute. In the example, AS 7675 provides an upstream Internet | |
1461 | connection to AS 100. When the following configuration exists in AS 7675, the | |
1462 | network operator of AS 100 can set local preference in AS 7675 network by | |
1463 | setting BGP communities attribute to the updates. | |
9eb95b3b QY |
1464 | |
1465 | .. code-block:: frr | |
c1a54c05 QY |
1466 | |
1467 | router bgp 7675 | |
1468 | neighbor 192.168.0.1 remote-as 100 | |
1469 | address-family ipv4 unicast | |
1470 | neighbor 192.168.0.1 route-map RMAP in | |
1471 | exit-address-family | |
1472 | ! | |
1473 | ip community-list 70 permit 7675:70 | |
1474 | ip community-list 70 deny | |
1475 | ip community-list 80 permit 7675:80 | |
1476 | ip community-list 80 deny | |
1477 | ip community-list 90 permit 7675:90 | |
1478 | ip community-list 90 deny | |
1479 | ! | |
1480 | route-map RMAP permit 10 | |
1481 | match community 70 | |
1482 | set local-preference 70 | |
1483 | ! | |
1484 | route-map RMAP permit 20 | |
1485 | match community 80 | |
1486 | set local-preference 80 | |
1487 | ! | |
1488 | route-map RMAP permit 30 | |
1489 | match community 90 | |
1490 | set local-preference 90 | |
c3c5a71f | 1491 | |
42fc5d26 | 1492 | |
8fcedbd2 QY |
1493 | The following configuration announces ``10.0.0.0/8`` from AS 100 to AS 7675. |
1494 | The route has communities value ``7675:80`` so when above configuration exists | |
1495 | in AS 7675, the announced routes' local preference value will be set to 80. | |
9eb95b3b QY |
1496 | |
1497 | .. code-block:: frr | |
c1a54c05 QY |
1498 | |
1499 | router bgp 100 | |
1500 | network 10.0.0.0/8 | |
1501 | neighbor 192.168.0.2 remote-as 7675 | |
1502 | address-family ipv4 unicast | |
1503 | neighbor 192.168.0.2 route-map RMAP out | |
1504 | exit-address-family | |
1505 | ! | |
1506 | ip prefix-list PLIST permit 10.0.0.0/8 | |
1507 | ! | |
1508 | route-map RMAP permit 10 | |
1509 | match ip address prefix-list PLIST | |
1510 | set community 7675:80 | |
c3c5a71f | 1511 | |
42fc5d26 | 1512 | |
8fcedbd2 QY |
1513 | The following configuration is an example of BGP route filtering using |
1514 | communities attribute. This configuration only permit BGP routes which has BGP | |
1515 | communities value ``0:80`` or ``0:90``. The network operator can set special | |
1516 | internal communities value at BGP border router, then limit the BGP route | |
1517 | announcements into the internal network. | |
9eb95b3b QY |
1518 | |
1519 | .. code-block:: frr | |
42fc5d26 | 1520 | |
c1a54c05 QY |
1521 | router bgp 7675 |
1522 | neighbor 192.168.0.1 remote-as 100 | |
1523 | address-family ipv4 unicast | |
1524 | neighbor 192.168.0.1 route-map RMAP in | |
1525 | exit-address-family | |
1526 | ! | |
1527 | ip community-list 1 permit 0:80 0:90 | |
1528 | ! | |
1529 | route-map RMAP permit in | |
1530 | match community 1 | |
c3c5a71f | 1531 | |
42fc5d26 | 1532 | |
8fcedbd2 QY |
1533 | The following example filters BGP routes which have a community value of |
1534 | ``1:1``. When there is no match community-list returns ``deny``. To avoid | |
1535 | filtering all routes, a ``permit`` line is set at the end of the | |
1536 | community-list. | |
9eb95b3b QY |
1537 | |
1538 | .. code-block:: frr | |
42fc5d26 | 1539 | |
c1a54c05 QY |
1540 | router bgp 7675 |
1541 | neighbor 192.168.0.1 remote-as 100 | |
1542 | address-family ipv4 unicast | |
1543 | neighbor 192.168.0.1 route-map RMAP in | |
1544 | exit-address-family | |
1545 | ! | |
1546 | ip community-list standard FILTER deny 1:1 | |
1547 | ip community-list standard FILTER permit | |
1548 | ! | |
1549 | route-map RMAP permit 10 | |
1550 | match community FILTER | |
c3c5a71f | 1551 | |
42fc5d26 | 1552 | |
8fcedbd2 QY |
1553 | The communities value keyword ``internet`` has special meanings in standard |
1554 | community lists. In the below example ``internet`` matches all BGP routes even | |
1555 | if the route does not have communities attribute at all. So community list | |
1556 | ``INTERNET`` is the same as ``FILTER`` in the previous example. | |
9eb95b3b QY |
1557 | |
1558 | .. code-block:: frr | |
42fc5d26 | 1559 | |
c1a54c05 QY |
1560 | ip community-list standard INTERNET deny 1:1 |
1561 | ip community-list standard INTERNET permit internet | |
c3c5a71f | 1562 | |
42fc5d26 | 1563 | |
8fcedbd2 QY |
1564 | The following configuration is an example of communities value deletion. With |
1565 | this configuration the community values ``100:1`` and ``100:2`` are removed | |
1566 | from BGP updates. For communities value deletion, only ``permit`` | |
1567 | community-list is used. ``deny`` community-list is ignored. | |
9eb95b3b QY |
1568 | |
1569 | .. code-block:: frr | |
42fc5d26 | 1570 | |
c1a54c05 QY |
1571 | router bgp 7675 |
1572 | neighbor 192.168.0.1 remote-as 100 | |
1573 | address-family ipv4 unicast | |
1574 | neighbor 192.168.0.1 route-map RMAP in | |
1575 | exit-address-family | |
1576 | ! | |
1577 | ip community-list standard DEL permit 100:1 100:2 | |
1578 | ! | |
1579 | route-map RMAP permit 10 | |
1580 | set comm-list DEL delete | |
c3c5a71f | 1581 | |
42fc5d26 | 1582 | |
0efdf0fe | 1583 | .. _bgp-extended-communities-attribute: |
42fc5d26 | 1584 | |
8fcedbd2 QY |
1585 | Extended Communities Attribute |
1586 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
42fc5d26 | 1587 | |
c1a54c05 QY |
1588 | BGP extended communities attribute is introduced with MPLS VPN/BGP technology. |
1589 | MPLS VPN/BGP expands capability of network infrastructure to provide VPN | |
1590 | functionality. At the same time it requires a new framework for policy routing. | |
1591 | With BGP Extended Communities Attribute we can use Route Target or Site of | |
1592 | Origin for implementing network policy for MPLS VPN/BGP. | |
42fc5d26 | 1593 | |
c1a54c05 QY |
1594 | BGP Extended Communities Attribute is similar to BGP Communities Attribute. It |
1595 | is an optional transitive attribute. BGP Extended Communities Attribute can | |
1596 | carry multiple Extended Community value. Each Extended Community value is | |
1597 | eight octet length. | |
42fc5d26 | 1598 | |
c1a54c05 QY |
1599 | BGP Extended Communities Attribute provides an extended range compared with BGP |
1600 | Communities Attribute. Adding to that there is a type field in each value to | |
1601 | provides community space structure. | |
42fc5d26 | 1602 | |
c1a54c05 QY |
1603 | There are two format to define Extended Community value. One is AS based format |
1604 | the other is IP address based format. | |
42fc5d26 | 1605 | |
8fcedbd2 QY |
1606 | ``AS:VAL`` |
1607 | This is a format to define AS based Extended Community value. ``AS`` part | |
1608 | is 2 octets Global Administrator subfield in Extended Community value. | |
1609 | ``VAL`` part is 4 octets Local Administrator subfield. ``7675:100`` | |
1610 | represents AS 7675 policy value 100. | |
42fc5d26 | 1611 | |
8fcedbd2 | 1612 | ``IP-Address:VAL`` |
c1a54c05 | 1613 | This is a format to define IP address based Extended Community value. |
8fcedbd2 QY |
1614 | ``IP-Address`` part is 4 octets Global Administrator subfield. ``VAL`` part |
1615 | is 2 octets Local Administrator subfield. | |
42fc5d26 | 1616 | |
0efdf0fe | 1617 | .. _bgp-extended-community-lists: |
42fc5d26 | 1618 | |
8fcedbd2 QY |
1619 | Extended Community Lists |
1620 | ^^^^^^^^^^^^^^^^^^^^^^^^ | |
42fc5d26 | 1621 | |
c3c5a71f | 1622 | .. index:: ip extcommunity-list standard NAME permit|deny EXTCOMMUNITY |
29adcd50 | 1623 | .. clicmd:: ip extcommunity-list standard NAME permit|deny EXTCOMMUNITY |
42fc5d26 | 1624 | |
4da7fda3 QY |
1625 | This command defines a new standard extcommunity-list. `extcommunity` is |
1626 | extended communities value. The `extcommunity` is compiled into extended | |
1627 | community structure. We can define multiple extcommunity-list under same | |
1628 | name. In that case match will happen user defined order. Once the | |
1629 | extcommunity-list matches to extended communities attribute in BGP updates | |
1630 | it return permit or deny based upon the extcommunity-list definition. When | |
1631 | there is no matched entry, deny will be returned. When `extcommunity` is | |
1632 | empty it matches to any routes. | |
42fc5d26 | 1633 | |
c1a54c05 | 1634 | .. index:: ip extcommunity-list expanded NAME permit|deny LINE |
29adcd50 | 1635 | .. clicmd:: ip extcommunity-list expanded NAME permit|deny LINE |
42fc5d26 | 1636 | |
4da7fda3 QY |
1637 | This command defines a new expanded extcommunity-list. `line` is a string |
1638 | expression of extended communities attribute. `line` can be a regular | |
1639 | expression (:ref:`bgp-regular-expressions`) to match an extended communities | |
1640 | attribute in BGP updates. | |
42fc5d26 | 1641 | |
c1a54c05 | 1642 | .. index:: no ip extcommunity-list NAME |
29adcd50 | 1643 | .. clicmd:: no ip extcommunity-list NAME |
42fc5d26 | 1644 | |
c1a54c05 | 1645 | .. index:: no ip extcommunity-list standard NAME |
29adcd50 | 1646 | .. clicmd:: no ip extcommunity-list standard NAME |
42fc5d26 | 1647 | |
c1a54c05 | 1648 | .. index:: no ip extcommunity-list expanded NAME |
29adcd50 | 1649 | .. clicmd:: no ip extcommunity-list expanded NAME |
42fc5d26 | 1650 | |
4da7fda3 QY |
1651 | These commands delete extended community lists specified by `name`. All of |
1652 | extended community lists shares a single name space. So extended community | |
d1e7591e | 1653 | lists can be removed simply specifying the name. |
42fc5d26 | 1654 | |
c1a54c05 | 1655 | .. index:: show ip extcommunity-list |
29adcd50 | 1656 | .. clicmd:: show ip extcommunity-list |
42fc5d26 | 1657 | |
c1a54c05 | 1658 | .. index:: show ip extcommunity-list NAME |
29adcd50 | 1659 | .. clicmd:: show ip extcommunity-list NAME |
c1a54c05 | 1660 | |
4da7fda3 | 1661 | This command displays current extcommunity-list information. When `name` is |
9eb95b3b | 1662 | specified the community list's information is shown.:: |
42fc5d26 | 1663 | |
9eb95b3b | 1664 | # show ip extcommunity-list |
c3c5a71f | 1665 | |
42fc5d26 | 1666 | |
0efdf0fe | 1667 | .. _bgp-extended-communities-in-route-map: |
42fc5d26 QY |
1668 | |
1669 | BGP Extended Communities in Route Map | |
8fcedbd2 | 1670 | """"""""""""""""""""""""""""""""""""" |
42fc5d26 | 1671 | |
c3c5a71f | 1672 | .. index:: match extcommunity WORD |
29adcd50 | 1673 | .. clicmd:: match extcommunity WORD |
42fc5d26 | 1674 | |
c1a54c05 | 1675 | .. index:: set extcommunity rt EXTCOMMUNITY |
29adcd50 | 1676 | .. clicmd:: set extcommunity rt EXTCOMMUNITY |
42fc5d26 | 1677 | |
c1a54c05 | 1678 | This command set Route Target value. |
42fc5d26 | 1679 | |
c1a54c05 | 1680 | .. index:: set extcommunity soo EXTCOMMUNITY |
29adcd50 | 1681 | .. clicmd:: set extcommunity soo EXTCOMMUNITY |
c1a54c05 QY |
1682 | |
1683 | This command set Site of Origin value. | |
42fc5d26 | 1684 | |
47f47873 PG |
1685 | |
1686 | Note that the extended expanded community is only used for `match` rule, not for | |
1687 | `set` actions. | |
1688 | ||
0efdf0fe | 1689 | .. _bgp-large-communities-attribute: |
42fc5d26 | 1690 | |
8fcedbd2 QY |
1691 | Large Communities Attribute |
1692 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
42fc5d26 QY |
1693 | |
1694 | The BGP Large Communities attribute was introduced in Feb 2017 with | |
c1a54c05 | 1695 | :rfc:`8092`. |
42fc5d26 | 1696 | |
8fcedbd2 QY |
1697 | The BGP Large Communities Attribute is similar to the BGP Communities Attribute |
1698 | except that it has 3 components instead of two and each of which are 4 octets | |
1699 | in length. Large Communities bring additional functionality and convenience | |
1700 | over traditional communities, specifically the fact that the ``GLOBAL`` part | |
1701 | below is now 4 octets wide allowing seamless use in networks using 4-byte ASNs. | |
1702 | ||
1703 | ``GLOBAL:LOCAL1:LOCAL2`` | |
1704 | This is the format to define Large Community values. Referencing :rfc:`8195` | |
1705 | the values are commonly referred to as follows: | |
1706 | ||
1707 | - The ``GLOBAL`` part is a 4 octet Global Administrator field, commonly used | |
1708 | as the operators AS number. | |
1709 | - The ``LOCAL1`` part is a 4 octet Local Data Part 1 subfield referred to as | |
1710 | a function. | |
1711 | - The ``LOCAL2`` part is a 4 octet Local Data Part 2 field and referred to | |
1712 | as the parameter subfield. | |
1713 | ||
1714 | As an example, ``65551:1:10`` represents AS 65551 function 1 and parameter | |
1715 | 10. The referenced RFC above gives some guidelines on recommended usage. | |
42fc5d26 | 1716 | |
0efdf0fe | 1717 | .. _bgp-large-community-lists: |
42fc5d26 | 1718 | |
8fcedbd2 QY |
1719 | Large Community Lists |
1720 | """"""""""""""""""""" | |
42fc5d26 QY |
1721 | |
1722 | Two types of large community lists are supported, namely `standard` and | |
1723 | `expanded`. | |
1724 | ||
c3c5a71f | 1725 | .. index:: ip large-community-list standard NAME permit|deny LARGE-COMMUNITY |
29adcd50 | 1726 | .. clicmd:: ip large-community-list standard NAME permit|deny LARGE-COMMUNITY |
42fc5d26 | 1727 | |
4da7fda3 QY |
1728 | This command defines a new standard large-community-list. `large-community` |
1729 | is the Large Community value. We can add multiple large communities under | |
1730 | same name. In that case the match will happen in the user defined order. | |
1731 | Once the large-community-list matches the Large Communities attribute in BGP | |
1732 | updates it will return permit or deny based upon the large-community-list | |
1733 | definition. When there is no matched entry, a deny will be returned. When | |
1734 | `large-community` is empty it matches any routes. | |
42fc5d26 | 1735 | |
c1a54c05 | 1736 | .. index:: ip large-community-list expanded NAME permit|deny LINE |
29adcd50 | 1737 | .. clicmd:: ip large-community-list expanded NAME permit|deny LINE |
42fc5d26 | 1738 | |
4da7fda3 QY |
1739 | This command defines a new expanded large-community-list. Where `line` is a |
1740 | string matching expression, it will be compared to the entire Large | |
1741 | Communities attribute as a string, with each large-community in order from | |
1742 | lowest to highest. `line` can also be a regular expression which matches | |
1743 | this Large Community attribute. | |
42fc5d26 | 1744 | |
c1a54c05 | 1745 | .. index:: no ip large-community-list NAME |
29adcd50 | 1746 | .. clicmd:: no ip large-community-list NAME |
42fc5d26 | 1747 | |
c1a54c05 | 1748 | .. index:: no ip large-community-list standard NAME |
29adcd50 | 1749 | .. clicmd:: no ip large-community-list standard NAME |
42fc5d26 | 1750 | |
c1a54c05 | 1751 | .. index:: no ip large-community-list expanded NAME |
29adcd50 | 1752 | .. clicmd:: no ip large-community-list expanded NAME |
42fc5d26 | 1753 | |
4da7fda3 QY |
1754 | These commands delete Large Community lists specified by `name`. All Large |
1755 | Community lists share a single namespace. This means Large Community lists | |
1756 | can be removed by simply specifying the name. | |
42fc5d26 | 1757 | |
c1a54c05 | 1758 | .. index:: show ip large-community-list |
29adcd50 | 1759 | .. clicmd:: show ip large-community-list |
42fc5d26 | 1760 | |
c1a54c05 | 1761 | .. index:: show ip large-community-list NAME |
29adcd50 | 1762 | .. clicmd:: show ip large-community-list NAME |
42fc5d26 | 1763 | |
c1a54c05 QY |
1764 | This command display current large-community-list information. When |
1765 | `name` is specified the community list information is shown. | |
42fc5d26 | 1766 | |
c1a54c05 | 1767 | .. index:: show ip bgp large-community-info |
29adcd50 | 1768 | .. clicmd:: show ip bgp large-community-info |
c1a54c05 QY |
1769 | |
1770 | This command displays the current large communities in use. | |
42fc5d26 | 1771 | |
0efdf0fe | 1772 | .. _bgp-large-communities-in-route-map: |
42fc5d26 | 1773 | |
8fcedbd2 QY |
1774 | Large Communities in Route Map |
1775 | """""""""""""""""""""""""""""" | |
42fc5d26 | 1776 | |
03ff9a14 | 1777 | .. index:: match large-community LINE [exact-match] |
1778 | .. clicmd:: match large-community LINE [exact-match] | |
42fc5d26 | 1779 | |
4da7fda3 QY |
1780 | Where `line` can be a simple string to match, or a regular expression. It |
1781 | is very important to note that this match occurs on the entire | |
c1a54c05 | 1782 | large-community string as a whole, where each large-community is ordered |
03ff9a14 | 1783 | from lowest to highest. When `exact-match` keyword is specified, match |
1784 | happen only when BGP updates have completely same large communities value | |
1785 | specified in the large community list. | |
42fc5d26 | 1786 | |
c1a54c05 | 1787 | .. index:: set large-community LARGE-COMMUNITY |
29adcd50 | 1788 | .. clicmd:: set large-community LARGE-COMMUNITY |
42fc5d26 | 1789 | |
c1a54c05 | 1790 | .. index:: set large-community LARGE-COMMUNITY LARGE-COMMUNITY |
29adcd50 | 1791 | .. clicmd:: set large-community LARGE-COMMUNITY LARGE-COMMUNITY |
42fc5d26 | 1792 | |
c1a54c05 | 1793 | .. index:: set large-community LARGE-COMMUNITY additive |
29adcd50 | 1794 | .. clicmd:: set large-community LARGE-COMMUNITY additive |
c1a54c05 QY |
1795 | |
1796 | These commands are used for setting large-community values. The first | |
1797 | command will overwrite any large-communities currently present. | |
1798 | The second specifies two large-communities, which overwrites the current | |
1799 | large-community list. The third will add a large-community value without | |
1800 | overwriting other values. Multiple large-community values can be specified. | |
42fc5d26 | 1801 | |
47f47873 PG |
1802 | Note that the large expanded community is only used for `match` rule, not for |
1803 | `set` actions. | |
b572f826 | 1804 | |
c8a5e5e1 | 1805 | .. _bgp-l3vpn-vrfs: |
b572f826 | 1806 | |
c8a5e5e1 QY |
1807 | L3VPN VRFs |
1808 | ---------- | |
b572f826 | 1809 | |
c8a5e5e1 QY |
1810 | *bgpd* supports :abbr:`L3VPN (Layer 3 Virtual Private Networks)` :abbr:`VRFs |
1811 | (Virtual Routing and Forwarding)` for IPv4 :rfc:`4364` and IPv6 :rfc:`4659`. | |
1812 | L3VPN routes, and their associated VRF MPLS labels, can be distributed to VPN | |
1813 | SAFI neighbors in the *default*, i.e., non VRF, BGP instance. VRF MPLS labels | |
1814 | are reached using *core* MPLS labels which are distributed using LDP or BGP | |
1815 | labeled unicast. *bgpd* also supports inter-VRF route leaking. | |
b572f826 | 1816 | |
b572f826 | 1817 | |
c8a5e5e1 | 1818 | .. _bgp-vrf-route-leaking: |
8fcedbd2 QY |
1819 | |
1820 | VRF Route Leaking | |
c8a5e5e1 | 1821 | ----------------- |
8fcedbd2 QY |
1822 | |
1823 | BGP routes may be leaked (i.e. copied) between a unicast VRF RIB and the VPN | |
f90115c5 LB |
1824 | SAFI RIB of the default VRF for use in MPLS-based L3VPNs. Unicast routes may |
1825 | also be leaked between any VRFs (including the unicast RIB of the default BGP | |
1826 | instanced). A shortcut syntax is also available for specifying leaking from one | |
1827 | VRF to another VRF using the default instance's VPN RIB as the intemediary. A | |
1828 | common application of the VRF-VRF feature is to connect a customer's private | |
8fcedbd2 QY |
1829 | routing domain to a provider's VPN service. Leaking is configured from the |
1830 | point of view of an individual VRF: ``import`` refers to routes leaked from VPN | |
1831 | to a unicast VRF, whereas ``export`` refers to routes leaked from a unicast VRF | |
1832 | to VPN. | |
1833 | ||
1834 | Required parameters | |
c8a5e5e1 | 1835 | ^^^^^^^^^^^^^^^^^^^ |
b572f826 | 1836 | |
4da7fda3 QY |
1837 | Routes exported from a unicast VRF to the VPN RIB must be augmented by two |
1838 | parameters: | |
1839 | ||
1840 | - an :abbr:`RD (Route Distinguisher)` | |
1841 | - an :abbr:`RTLIST (Route-target List)` | |
1842 | ||
1843 | Configuration for these exported routes must, at a minimum, specify these two | |
1844 | parameters. | |
1845 | ||
1846 | Routes imported from the VPN RIB to a unicast VRF are selected according to | |
1847 | their RTLISTs. Routes whose RTLIST contains at least one route-target in | |
1848 | common with the configured import RTLIST are leaked. Configuration for these | |
1849 | imported routes must specify an RTLIST to be matched. | |
1850 | ||
1851 | The RD, which carries no semantic value, is intended to make the route unique | |
1852 | in the VPN RIB among all routes of its prefix that originate from all the | |
1853 | customers and sites that are attached to the provider's VPN service. | |
1854 | Accordingly, each site of each customer is typically assigned an RD that is | |
1855 | unique across the entire provider network. | |
1856 | ||
1857 | The RTLIST is a set of route-target extended community values whose purpose is | |
1858 | to specify route-leaking policy. Typically, a customer is assigned a single | |
1859 | route-target value for import and export to be used at all customer sites. This | |
1860 | configuration specifies a simple topology wherein a customer has a single | |
1861 | routing domain which is shared across all its sites. More complex routing | |
1862 | topologies are possible through use of additional route-targets to augment the | |
1863 | leaking of sets of routes in various ways. | |
b572f826 | 1864 | |
e967a1d0 DS |
1865 | When using the shortcut syntax for vrf-to-vrf leaking, the RD and RT are |
1866 | auto-derived. | |
fb3d9f3e | 1867 | |
8fcedbd2 | 1868 | General configuration |
c8a5e5e1 | 1869 | ^^^^^^^^^^^^^^^^^^^^^ |
b572f826 | 1870 | |
f90115c5 | 1871 | Configuration of route leaking between a unicast VRF RIB and the VPN SAFI RIB |
4da7fda3 QY |
1872 | of the default VRF is accomplished via commands in the context of a VRF |
1873 | address-family: | |
b572f826 PZ |
1874 | |
1875 | .. index:: rd vpn export AS:NN|IP:nn | |
1876 | .. clicmd:: rd vpn export AS:NN|IP:nn | |
1877 | ||
4da7fda3 QY |
1878 | Specifies the route distinguisher to be added to a route exported from the |
1879 | current unicast VRF to VPN. | |
b572f826 PZ |
1880 | |
1881 | .. index:: no rd vpn export [AS:NN|IP:nn] | |
1882 | .. clicmd:: no rd vpn export [AS:NN|IP:nn] | |
1883 | ||
1884 | Deletes any previously-configured export route distinguisher. | |
1885 | ||
1886 | .. index:: rt vpn import|export|both RTLIST... | |
1887 | .. clicmd:: rt vpn import|export|both RTLIST... | |
1888 | ||
4da7fda3 QY |
1889 | Specifies the route-target list to be attached to a route (export) or the |
1890 | route-target list to match against (import) when exporting/importing between | |
1891 | the current unicast VRF and VPN. | |
b572f826 | 1892 | |
4da7fda3 QY |
1893 | The RTLIST is a space-separated list of route-targets, which are BGP |
1894 | extended community values as described in | |
b572f826 PZ |
1895 | :ref:`bgp-extended-communities-attribute`. |
1896 | ||
1897 | .. index:: no rt vpn import|export|both [RTLIST...] | |
1898 | .. clicmd:: no rt vpn import|export|both [RTLIST...] | |
1899 | ||
1900 | Deletes any previously-configured import or export route-target list. | |
1901 | ||
e70e9f8e PZ |
1902 | .. index:: label vpn export (0..1048575)|auto |
1903 | .. clicmd:: label vpn export (0..1048575)|auto | |
b572f826 | 1904 | |
8a2124f7 | 1905 | Enables an MPLS label to be attached to a route exported from the current |
1906 | unicast VRF to VPN. If the value specified is ``auto``, the label value is | |
1907 | automatically assigned from a pool maintained by the Zebra daemon. If Zebra | |
1908 | is not running, or if this command is not configured, automatic label | |
1909 | assignment will not complete, which will block corresponding route export. | |
b572f826 | 1910 | |
e70e9f8e PZ |
1911 | .. index:: no label vpn export [(0..1048575)|auto] |
1912 | .. clicmd:: no label vpn export [(0..1048575)|auto] | |
b572f826 PZ |
1913 | |
1914 | Deletes any previously-configured export label. | |
1915 | ||
1916 | .. index:: nexthop vpn export A.B.C.D|X:X::X:X | |
1917 | .. clicmd:: nexthop vpn export A.B.C.D|X:X::X:X | |
1918 | ||
4da7fda3 QY |
1919 | Specifies an optional nexthop value to be assigned to a route exported from |
1920 | the current unicast VRF to VPN. If left unspecified, the nexthop will be set | |
1921 | to 0.0.0.0 or 0:0::0:0 (self). | |
b572f826 PZ |
1922 | |
1923 | .. index:: no nexthop vpn export [A.B.C.D|X:X::X:X] | |
1924 | .. clicmd:: no nexthop vpn export [A.B.C.D|X:X::X:X] | |
1925 | ||
1926 | Deletes any previously-configured export nexthop. | |
1927 | ||
1928 | .. index:: route-map vpn import|export MAP | |
1929 | .. clicmd:: route-map vpn import|export MAP | |
1930 | ||
4da7fda3 | 1931 | Specifies an optional route-map to be applied to routes imported or exported |
d1e7591e | 1932 | between the current unicast VRF and VPN. |
b572f826 PZ |
1933 | |
1934 | .. index:: no route-map vpn import|export [MAP] | |
1935 | .. clicmd:: no route-map vpn import|export [MAP] | |
1936 | ||
1937 | Deletes any previously-configured import or export route-map. | |
1938 | ||
1939 | .. index:: import|export vpn | |
1940 | .. clicmd:: import|export vpn | |
1941 | ||
d1e7591e | 1942 | Enables import or export of routes between the current unicast VRF and VPN. |
b572f826 PZ |
1943 | |
1944 | .. index:: no import|export vpn | |
1945 | .. clicmd:: no import|export vpn | |
1946 | ||
d1e7591e | 1947 | Disables import or export of routes between the current unicast VRF and VPN. |
b572f826 | 1948 | |
fb3d9f3e DS |
1949 | .. index:: import vrf VRFNAME |
1950 | .. clicmd:: import vrf VRFNAME | |
1951 | ||
e967a1d0 DS |
1952 | Shortcut syntax for specifying automatic leaking from vrf VRFNAME to |
1953 | the current VRF using the VPN RIB as intermediary. The RD and RT | |
1954 | are auto derived and should not be specified explicitly for either the | |
1955 | source or destination VRF's. | |
1956 | ||
1957 | This shortcut syntax mode is not compatible with the explicit | |
1958 | `import vpn` and `export vpn` statements for the two VRF's involved. | |
1959 | The CLI will disallow attempts to configure incompatible leaking | |
1960 | modes. | |
fb3d9f3e DS |
1961 | |
1962 | .. index:: no import vrf VRFNAME | |
1963 | .. clicmd:: no import vrf VRFNAME | |
1964 | ||
e967a1d0 DS |
1965 | Disables automatic leaking from vrf VRFNAME to the current VRF using |
1966 | the VPN RIB as intermediary. | |
b572f826 | 1967 | |
42fc5d26 | 1968 | |
8fcedbd2 | 1969 | .. _bgp-cisco-compatibility: |
42fc5d26 | 1970 | |
8fcedbd2 QY |
1971 | Cisco Compatibility |
1972 | ------------------- | |
42fc5d26 | 1973 | |
8fcedbd2 QY |
1974 | FRR has commands that change some configuration syntax and default behavior to |
1975 | behave more closely to Cisco conventions. These are deprecated and will be | |
1976 | removed in a future version of FRR. | |
42fc5d26 | 1977 | |
8fcedbd2 QY |
1978 | .. deprecated:: 5.0 |
1979 | Please transition to using the FRR specific syntax for your configuration. | |
42fc5d26 | 1980 | |
8fcedbd2 QY |
1981 | .. index:: bgp config-type cisco |
1982 | .. clicmd:: bgp config-type cisco | |
42fc5d26 | 1983 | |
8fcedbd2 | 1984 | Cisco compatible BGP configuration output. |
42fc5d26 | 1985 | |
8fcedbd2 | 1986 | When this configuration line is specified: |
c1a54c05 | 1987 | |
8fcedbd2 QY |
1988 | - ``no synchronization`` is displayed. This command does nothing and is for |
1989 | display purposes only. | |
1990 | - ``no auto-summary`` is displayed. | |
1991 | - The ``network`` and ``aggregate-address`` arguments are displayed as: | |
42fc5d26 | 1992 | |
8fcedbd2 | 1993 | :: |
42fc5d26 | 1994 | |
8fcedbd2 | 1995 | A.B.C.D M.M.M.M |
42fc5d26 | 1996 | |
8fcedbd2 QY |
1997 | FRR: network 10.0.0.0/8 |
1998 | Cisco: network 10.0.0.0 | |
42fc5d26 | 1999 | |
8fcedbd2 QY |
2000 | FRR: aggregate-address 192.168.0.0/24 |
2001 | Cisco: aggregate-address 192.168.0.0 255.255.255.0 | |
42fc5d26 | 2002 | |
8fcedbd2 QY |
2003 | Community attribute handling is also different. If no configuration is |
2004 | specified community attribute and extended community attribute are sent to | |
2005 | the neighbor. If a user manually disables the feature, the community | |
2006 | attribute is not sent to the neighbor. When ``bgp config-type cisco`` is | |
2007 | specified, the community attribute is not sent to the neighbor by default. | |
2008 | To send the community attribute user has to specify | |
2009 | :clicmd:`neighbor A.B.C.D send-community` like so: | |
42fc5d26 | 2010 | |
8fcedbd2 | 2011 | .. code-block:: frr |
42fc5d26 | 2012 | |
8fcedbd2 QY |
2013 | ! |
2014 | router bgp 1 | |
2015 | neighbor 10.0.0.1 remote-as 1 | |
2016 | address-family ipv4 unicast | |
2017 | no neighbor 10.0.0.1 send-community | |
2018 | exit-address-family | |
2019 | ! | |
2020 | router bgp 1 | |
2021 | neighbor 10.0.0.1 remote-as 1 | |
2022 | address-family ipv4 unicast | |
2023 | neighbor 10.0.0.1 send-community | |
2024 | exit-address-family | |
2025 | ! | |
42fc5d26 | 2026 | |
8fcedbd2 QY |
2027 | .. deprecated:: 5.0 |
2028 | Please transition to using the FRR specific syntax for your configuration. | |
2029 | ||
2030 | .. index:: bgp config-type zebra | |
2031 | .. clicmd:: bgp config-type zebra | |
2032 | ||
2033 | FRR style BGP configuration. This is the default. | |
2034 | ||
2035 | .. _bgp-debugging: | |
2036 | ||
2037 | Debugging | |
2038 | --------- | |
42fc5d26 | 2039 | |
c1a54c05 | 2040 | .. index:: show debug |
29adcd50 | 2041 | .. clicmd:: show debug |
42fc5d26 | 2042 | |
8fcedbd2 | 2043 | Show all enabled debugs. |
42fc5d26 | 2044 | |
53b758f3 PG |
2045 | .. index:: [no] debug bgp neighbor-events |
2046 | .. clicmd:: [no] debug bgp neighbor-events | |
42fc5d26 | 2047 | |
8fcedbd2 QY |
2048 | Enable or disable debugging for neighbor events. This provides general |
2049 | information on BGP events such as peer connection / disconnection, session | |
2050 | establishment / teardown, and capability negotiation. | |
42fc5d26 | 2051 | |
53b758f3 PG |
2052 | .. index:: [no] debug bgp updates |
2053 | .. clicmd:: [no] debug bgp updates | |
42fc5d26 | 2054 | |
8fcedbd2 QY |
2055 | Enable or disable debugging for BGP updates. This provides information on |
2056 | BGP UPDATE messages transmitted and received between local and remote | |
2057 | instances. | |
42fc5d26 | 2058 | |
53b758f3 PG |
2059 | .. index:: [no] debug bgp keepalives |
2060 | .. clicmd:: [no] debug bgp keepalives | |
42fc5d26 | 2061 | |
8fcedbd2 QY |
2062 | Enable or disable debugging for BGP keepalives. This provides information on |
2063 | BGP KEEPALIVE messages transmitted and received between local and remote | |
2064 | instances. | |
c1a54c05 | 2065 | |
8fcedbd2 QY |
2066 | .. index:: [no] debug bgp bestpath <A.B.C.D/M|X:X::X:X/M> |
2067 | .. clicmd:: [no] debug bgp bestpath <A.B.C.D/M|X:X::X:X/M> | |
42fc5d26 | 2068 | |
8fcedbd2 | 2069 | Enable or disable debugging for bestpath selection on the specified prefix. |
42fc5d26 | 2070 | |
8fcedbd2 QY |
2071 | .. index:: [no] debug bgp nht |
2072 | .. clicmd:: [no] debug bgp nht | |
4da7fda3 | 2073 | |
8fcedbd2 | 2074 | Enable or disable debugging of BGP nexthop tracking. |
4da7fda3 | 2075 | |
8fcedbd2 QY |
2076 | .. index:: [no] debug bgp update-groups |
2077 | .. clicmd:: [no] debug bgp update-groups | |
4b44467c | 2078 | |
8fcedbd2 QY |
2079 | Enable or disable debugging of dynamic update groups. This provides general |
2080 | information on group creation, deletion, join and prune events. | |
4b44467c | 2081 | |
8fcedbd2 QY |
2082 | .. index:: [no] debug bgp zebra |
2083 | .. clicmd:: [no] debug bgp zebra | |
42fc5d26 | 2084 | |
8fcedbd2 | 2085 | Enable or disable debugging of communications between *bgpd* and *zebra*. |
c3c5a71f | 2086 | |
8fcedbd2 QY |
2087 | Dumping Messages and Routing Tables |
2088 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
42fc5d26 | 2089 | |
8fcedbd2 QY |
2090 | .. index:: dump bgp all PATH [INTERVAL] |
2091 | .. clicmd:: dump bgp all PATH [INTERVAL] | |
42fc5d26 | 2092 | |
8fcedbd2 QY |
2093 | .. index:: dump bgp all-et PATH [INTERVAL] |
2094 | .. clicmd:: dump bgp all-et PATH [INTERVAL] | |
c3c5a71f | 2095 | |
8fcedbd2 QY |
2096 | .. index:: no dump bgp all [PATH] [INTERVAL] |
2097 | .. clicmd:: no dump bgp all [PATH] [INTERVAL] | |
42fc5d26 | 2098 | |
8fcedbd2 QY |
2099 | Dump all BGP packet and events to `path` file. |
2100 | If `interval` is set, a new file will be created for echo `interval` of | |
2101 | seconds. The path `path` can be set with date and time formatting | |
2102 | (strftime). The type ‘all-et’ enables support for Extended Timestamp Header | |
2103 | (:ref:`packet-binary-dump-format`). | |
c3c5a71f | 2104 | |
8fcedbd2 QY |
2105 | .. index:: dump bgp updates PATH [INTERVAL] |
2106 | .. clicmd:: dump bgp updates PATH [INTERVAL] | |
42fc5d26 | 2107 | |
8fcedbd2 QY |
2108 | .. index:: dump bgp updates-et PATH [INTERVAL] |
2109 | .. clicmd:: dump bgp updates-et PATH [INTERVAL] | |
42fc5d26 | 2110 | |
8fcedbd2 QY |
2111 | .. index:: no dump bgp updates [PATH] [INTERVAL] |
2112 | .. clicmd:: no dump bgp updates [PATH] [INTERVAL] | |
42fc5d26 | 2113 | |
8fcedbd2 QY |
2114 | Dump only BGP updates messages to `path` file. |
2115 | If `interval` is set, a new file will be created for echo `interval` of | |
2116 | seconds. The path `path` can be set with date and time formatting | |
2117 | (strftime). The type ‘updates-et’ enables support for Extended Timestamp | |
2118 | Header (:ref:`packet-binary-dump-format`). | |
42fc5d26 | 2119 | |
8fcedbd2 QY |
2120 | .. index:: dump bgp routes-mrt PATH |
2121 | .. clicmd:: dump bgp routes-mrt PATH | |
c3c5a71f | 2122 | |
8fcedbd2 QY |
2123 | .. index:: dump bgp routes-mrt PATH INTERVAL |
2124 | .. clicmd:: dump bgp routes-mrt PATH INTERVAL | |
42fc5d26 | 2125 | |
8fcedbd2 QY |
2126 | .. index:: no dump bgp route-mrt [PATH] [INTERVAL] |
2127 | .. clicmd:: no dump bgp route-mrt [PATH] [INTERVAL] | |
42fc5d26 | 2128 | |
8fcedbd2 QY |
2129 | Dump whole BGP routing table to `path`. This is heavy process. The path |
2130 | `path` can be set with date and time formatting (strftime). If `interval` is | |
2131 | set, a new file will be created for echo `interval` of seconds. | |
42fc5d26 | 2132 | |
8fcedbd2 | 2133 | Note: the interval variable can also be set using hours and minutes: 04h20m00. |
42fc5d26 | 2134 | |
c3c5a71f | 2135 | |
8fcedbd2 | 2136 | .. _bgp-other-commands: |
42fc5d26 | 2137 | |
8fcedbd2 QY |
2138 | Other BGP Commands |
2139 | ------------------ | |
42fc5d26 | 2140 | |
8fcedbd2 QY |
2141 | .. index:: clear bgp ipv4|ipv6 \* |
2142 | .. clicmd:: clear bgp ipv4|ipv6 \* | |
42fc5d26 | 2143 | |
8fcedbd2 | 2144 | Clear all address family peers. |
42fc5d26 | 2145 | |
8fcedbd2 QY |
2146 | .. index:: clear bgp ipv4|ipv6 PEER |
2147 | .. clicmd:: clear bgp ipv4|ipv6 PEER | |
42fc5d26 | 2148 | |
8fcedbd2 | 2149 | Clear peers which have addresses of X.X.X.X |
42fc5d26 | 2150 | |
8fcedbd2 QY |
2151 | .. index:: clear bgp ipv4|ipv6 PEER soft in |
2152 | .. clicmd:: clear bgp ipv4|ipv6 PEER soft in | |
42fc5d26 | 2153 | |
8fcedbd2 | 2154 | Clear peer using soft reconfiguration. |
42fc5d26 | 2155 | |
42fc5d26 | 2156 | |
8fcedbd2 | 2157 | .. _bgp-displaying-bgp-information: |
42fc5d26 | 2158 | |
8fcedbd2 QY |
2159 | Displaying BGP Information |
2160 | ========================== | |
42fc5d26 | 2161 | |
e6f59415 PG |
2162 | The following four commands display the IPv6 and IPv4 routing tables, depending |
2163 | on whether or not the ``ip`` keyword is used. | |
2164 | Actually, :clicmd:`show ip bgp` command was used on older `Quagga` routing | |
2165 | daemon project, while :clicmd:`show bgp` command is the new format. The choice | |
2166 | has been done to keep old format with IPv4 routing table, while new format | |
2167 | displays IPv6 routing table. | |
2168 | ||
8fcedbd2 QY |
2169 | .. index:: show ip bgp |
2170 | .. clicmd:: show ip bgp | |
42fc5d26 | 2171 | |
8fcedbd2 QY |
2172 | .. index:: show ip bgp A.B.C.D |
2173 | .. clicmd:: show ip bgp A.B.C.D | |
c1a54c05 | 2174 | |
e6f59415 PG |
2175 | .. index:: show bgp |
2176 | .. clicmd:: show bgp | |
2177 | ||
2178 | .. index:: show bgp X:X::X:X | |
2179 | .. clicmd:: show bgp X:X::X:X | |
42fc5d26 | 2180 | |
8fcedbd2 | 2181 | These commands display BGP routes. When no route is specified, the default |
e6f59415 | 2182 | is to display all BGP routes. |
42fc5d26 | 2183 | |
8fcedbd2 | 2184 | :: |
c1a54c05 | 2185 | |
8fcedbd2 QY |
2186 | BGP table version is 0, local router ID is 10.1.1.1 |
2187 | Status codes: s suppressed, d damped, h history, * valid, > best, i - internal | |
2188 | Origin codes: i - IGP, e - EGP, ? - incomplete | |
42fc5d26 | 2189 | |
8fcedbd2 QY |
2190 | Network Next Hop Metric LocPrf Weight Path |
2191 | \*> 1.1.1.1/32 0.0.0.0 0 32768 i | |
42fc5d26 | 2192 | |
8fcedbd2 | 2193 | Total number of prefixes 1 |
4da7fda3 | 2194 | |
e6f59415 PG |
2195 | Some other commands provide additional options for filtering the output. |
2196 | ||
2197 | .. index:: show [ip] bgp regexp LINE | |
2198 | .. clicmd:: show [ip] bgp regexp LINE | |
42fc5d26 | 2199 | |
8fcedbd2 QY |
2200 | This command displays BGP routes using AS path regular expression |
2201 | (:ref:`bgp-regular-expressions`). | |
42fc5d26 | 2202 | |
e6f59415 PG |
2203 | .. index:: show [ip] bgp summary |
2204 | .. clicmd:: show [ip] bgp summary | |
42fc5d26 | 2205 | |
8fcedbd2 | 2206 | Show a bgp peer summary for the specified address family. |
42fc5d26 | 2207 | |
e6f59415 PG |
2208 | The old command structure :clicmd:`show ip bgp` may be removed in the future |
2209 | and should no longer be used. In order to reach the other BGP routing tables | |
2210 | other than the IPv6 routing table given by :clicmd:`show bgp`, the new command | |
2211 | structure is extended with :clicmd:`show bgp [afi] [safi]`. | |
2212 | ||
2213 | .. index:: show bgp [afi] [safi] | |
2214 | .. clicmd:: show bgp [afi] [safi] | |
2215 | ||
2216 | .. index:: show bgp <ipv4|ipv6> <unicast|multicast|vpn|labeled-unicast> | |
2217 | .. clicmd:: show bgp <ipv4|ipv6> <unicast|multicast|vpn|labeled-unicast> | |
2218 | ||
2219 | These commands display BGP routes for the specific routing table indicated by | |
2220 | the selected afi and the selected safi. If no afi and no safi value is given, | |
2221 | the command falls back to the default IPv6 routing table | |
2222 | ||
2223 | .. index:: show bgp [afi] [safi] summary | |
2224 | .. clicmd:: show bgp [afi] [safi] summary | |
2225 | ||
2226 | Show a bgp peer summary for the specified address family, and subsequent | |
2227 | address-family. | |
2228 | ||
2229 | .. index:: show bgp [afi] [safi] neighbor [PEER] | |
2230 | .. clicmd:: show bgp [afi] [safi] neighbor [PEER] | |
9eb95b3b | 2231 | |
e6f59415 PG |
2232 | This command shows information on a specific BGP peer of the relevant |
2233 | afi and safi selected. | |
c1a54c05 | 2234 | |
e6f59415 PG |
2235 | .. index:: show bgp [afi] [safi] dampening dampened-paths |
2236 | .. clicmd:: show bgp [afi] [safi] dampening dampened-paths | |
42fc5d26 | 2237 | |
e6f59415 PG |
2238 | Display paths suppressed due to dampening of the selected afi and safi |
2239 | selected. | |
42fc5d26 | 2240 | |
e6f59415 PG |
2241 | .. index:: show bgp [afi] [safi] dampening flap-statistics |
2242 | .. clicmd:: show bgp [afi] [safi] dampening flap-statistics | |
c1a54c05 | 2243 | |
e6f59415 | 2244 | Display flap statistics of routes of the selected afi and safi selected. |
42fc5d26 | 2245 | |
8fcedbd2 | 2246 | .. _bgp-display-routes-by-community: |
42fc5d26 | 2247 | |
8fcedbd2 QY |
2248 | Displaying Routes by Community Attribute |
2249 | ---------------------------------------- | |
42fc5d26 | 2250 | |
8fcedbd2 QY |
2251 | The following commands allow displaying routes based on their community |
2252 | attribute. | |
42fc5d26 | 2253 | |
8fcedbd2 QY |
2254 | .. index:: show [ip] bgp <ipv4|ipv6> community |
2255 | .. clicmd:: show [ip] bgp <ipv4|ipv6> community | |
42fc5d26 | 2256 | |
8fcedbd2 QY |
2257 | .. index:: show [ip] bgp <ipv4|ipv6> community COMMUNITY |
2258 | .. clicmd:: show [ip] bgp <ipv4|ipv6> community COMMUNITY | |
42fc5d26 | 2259 | |
8fcedbd2 QY |
2260 | .. index:: show [ip] bgp <ipv4|ipv6> community COMMUNITY exact-match |
2261 | .. clicmd:: show [ip] bgp <ipv4|ipv6> community COMMUNITY exact-match | |
76bd1499 | 2262 | |
8fcedbd2 QY |
2263 | These commands display BGP routes which have the community attribute. |
2264 | attribute. When ``COMMUNITY`` is specified, BGP routes that match that | |
2265 | community are displayed. When `exact-match` is specified, it display only | |
2266 | routes that have an exact match. | |
c3c5a71f | 2267 | |
8fcedbd2 QY |
2268 | .. index:: show [ip] bgp <ipv4|ipv6> community-list WORD |
2269 | .. clicmd:: show [ip] bgp <ipv4|ipv6> community-list WORD | |
42fc5d26 | 2270 | |
8fcedbd2 QY |
2271 | .. index:: show [ip] bgp <ipv4|ipv6> community-list WORD exact-match |
2272 | .. clicmd:: show [ip] bgp <ipv4|ipv6> community-list WORD exact-match | |
42fc5d26 | 2273 | |
8fcedbd2 QY |
2274 | These commands display BGP routes for the address family specified that |
2275 | match the specified community list. When `exact-match` is specified, it | |
2276 | displays only routes that have an exact match. | |
42fc5d26 | 2277 | |
36a206db | 2278 | .. _bgp-display-routes-by-lcommunity: |
2279 | ||
2280 | Displaying Routes by Large Community Attribute | |
2281 | ---------------------------------------------- | |
2282 | ||
2283 | The following commands allow displaying routes based on their | |
2284 | large community attribute. | |
2285 | ||
2286 | .. index:: show [ip] bgp <ipv4|ipv6> large-community | |
2287 | .. clicmd:: show [ip] bgp <ipv4|ipv6> large-community | |
2288 | ||
2289 | .. index:: show [ip] bgp <ipv4|ipv6> large-community LARGE-COMMUNITY | |
2290 | .. clicmd:: show [ip] bgp <ipv4|ipv6> large-community LARGE-COMMUNITY | |
2291 | ||
2292 | .. index:: show [ip] bgp <ipv4|ipv6> large-community LARGE-COMMUNITY exact-match | |
2293 | .. clicmd:: show [ip] bgp <ipv4|ipv6> large-community LARGE-COMMUNITY exact-match | |
2294 | ||
2295 | .. index:: show [ip] bgp <ipv4|ipv6> large-community LARGE-COMMUNITY json | |
2296 | .. clicmd:: show [ip] bgp <ipv4|ipv6> large-community LARGE-COMMUNITY json | |
2297 | ||
2298 | These commands display BGP routes which have the large community attribute. | |
2299 | attribute. When ``LARGE-COMMUNITY`` is specified, BGP routes that match that | |
2300 | large community are displayed. When `exact-match` is specified, it display | |
2301 | only routes that have an exact match. When `json` is specified, it display | |
2302 | routes in json format. | |
2303 | ||
2304 | .. index:: show [ip] bgp <ipv4|ipv6> large-community-list WORD | |
2305 | .. clicmd:: show [ip] bgp <ipv4|ipv6> large-community-list WORD | |
2306 | ||
2307 | .. index:: show [ip] bgp <ipv4|ipv6> large-community-list WORD exact-match | |
2308 | .. clicmd:: show [ip] bgp <ipv4|ipv6> large-community-list WORD exact-match | |
2309 | ||
2310 | .. index:: show [ip] bgp <ipv4|ipv6> large-community-list WORD json | |
2311 | .. clicmd:: show [ip] bgp <ipv4|ipv6> large-community-list WORD json | |
2312 | ||
2313 | These commands display BGP routes for the address family specified that | |
2314 | match the specified large community list. When `exact-match` is specified, | |
2315 | it displays only routes that have an exact match. When `json` is specified, | |
2316 | it display routes in json format. | |
2317 | ||
8fcedbd2 | 2318 | .. _bgp-display-routes-by-as-path: |
42fc5d26 | 2319 | |
36a206db | 2320 | |
8fcedbd2 QY |
2321 | Displaying Routes by AS Path |
2322 | ---------------------------- | |
42fc5d26 | 2323 | |
8fcedbd2 QY |
2324 | .. index:: show bgp ipv4|ipv6 regexp LINE |
2325 | .. clicmd:: show bgp ipv4|ipv6 regexp LINE | |
76bd1499 | 2326 | |
8fcedbd2 QY |
2327 | This commands displays BGP routes that matches a regular |
2328 | expression `line` (:ref:`bgp-regular-expressions`). | |
2329 | ||
e6f59415 PG |
2330 | .. index:: show [ip] bgp ipv4 vpn |
2331 | .. clicmd:: show [ip] bgp ipv4 vpn | |
8fcedbd2 | 2332 | |
e6f59415 PG |
2333 | .. index:: show [ip] bgp ipv6 vpn |
2334 | .. clicmd:: show [ip] bgp ipv6 vpn | |
8fcedbd2 QY |
2335 | |
2336 | Print active IPV4 or IPV6 routes advertised via the VPN SAFI. | |
2337 | ||
2338 | .. index:: show bgp ipv4 vpn summary | |
2339 | .. clicmd:: show bgp ipv4 vpn summary | |
2340 | ||
2341 | .. index:: show bgp ipv6 vpn summary | |
2342 | .. clicmd:: show bgp ipv6 vpn summary | |
2343 | ||
2344 | Print a summary of neighbor connections for the specified AFI/SAFI combination. | |
2345 | ||
2346 | ||
2347 | .. _bgp-route-reflector: | |
2348 | ||
2349 | Route Reflector | |
2350 | =============== | |
2351 | ||
749afd7d RF |
2352 | BGP routers connected inside the same AS through BGP belong to an internal |
2353 | BGP session, or IBGP. In order to prevent routing table loops, IBGP does not | |
2354 | advertise IBGP-learned routes to other routers in the same session. As such, | |
2355 | IBGP requires a full mesh of all peers. For large networks, this quickly becomes | |
2356 | unscalable. Introducing route reflectors removes the need for the full-mesh. | |
8fcedbd2 | 2357 | |
749afd7d RF |
2358 | When route reflectors are configured, these will reflect the routes announced |
2359 | by the peers configured as clients. A route reflector client is configured | |
2360 | with: | |
8fcedbd2 QY |
2361 | |
2362 | .. index:: neighbor PEER route-reflector-client | |
2363 | .. clicmd:: neighbor PEER route-reflector-client | |
2364 | ||
2365 | .. index:: no neighbor PEER route-reflector-client | |
2366 | .. clicmd:: no neighbor PEER route-reflector-client | |
c3c5a71f | 2367 | |
749afd7d RF |
2368 | To avoid single points of failure, multiple route reflectors can be configured. |
2369 | ||
2370 | A cluster is a collection of route reflectors and their clients, and is used | |
2371 | by route reflectors to avoid looping. | |
2372 | ||
2373 | .. index:: bgp cluster-id A.B.C.D | |
2374 | .. clicmd:: bgp cluster-id A.B.C.D | |
42fc5d26 | 2375 | |
0efdf0fe | 2376 | .. _routing-policy: |
42fc5d26 | 2377 | |
8fcedbd2 QY |
2378 | Routing Policy |
2379 | ============== | |
42fc5d26 | 2380 | |
4da7fda3 | 2381 | You can set different routing policy for a peer. For example, you can set |
9eb95b3b QY |
2382 | different filter for a peer. |
2383 | ||
2384 | .. code-block:: frr | |
c1a54c05 | 2385 | |
c1a54c05 QY |
2386 | ! |
2387 | router bgp 1 view 1 | |
2388 | neighbor 10.0.0.1 remote-as 2 | |
2389 | address-family ipv4 unicast | |
2390 | neighbor 10.0.0.1 distribute-list 1 in | |
2391 | exit-address-family | |
2392 | ! | |
2393 | router bgp 1 view 2 | |
2394 | neighbor 10.0.0.1 remote-as 2 | |
2395 | address-family ipv4 unicast | |
2396 | neighbor 10.0.0.1 distribute-list 2 in | |
2397 | exit-address-family | |
c3c5a71f | 2398 | |
4da7fda3 QY |
2399 | This means BGP update from a peer 10.0.0.1 goes to both BGP view 1 and view 2. |
2400 | When the update is inserted into view 1, distribute-list 1 is applied. On the | |
2401 | other hand, when the update is inserted into view 2, distribute-list 2 is | |
2402 | applied. | |
42fc5d26 | 2403 | |
42fc5d26 | 2404 | |
0efdf0fe | 2405 | .. _bgp-regular-expressions: |
42fc5d26 QY |
2406 | |
2407 | BGP Regular Expressions | |
2408 | ======================= | |
2409 | ||
8fcedbd2 QY |
2410 | BGP regular expressions are based on :t:`POSIX 1003.2` regular expressions. The |
2411 | following description is just a quick subset of the POSIX regular expressions. | |
42fc5d26 QY |
2412 | |
2413 | ||
8fcedbd2 | 2414 | .\* |
c1a54c05 | 2415 | Matches any single character. |
42fc5d26 | 2416 | |
8fcedbd2 | 2417 | \* |
c1a54c05 | 2418 | Matches 0 or more occurrences of pattern. |
42fc5d26 | 2419 | |
8fcedbd2 | 2420 | \+ |
c1a54c05 | 2421 | Matches 1 or more occurrences of pattern. |
42fc5d26 QY |
2422 | |
2423 | ? | |
c1a54c05 | 2424 | Match 0 or 1 occurrences of pattern. |
42fc5d26 QY |
2425 | |
2426 | ^ | |
c1a54c05 | 2427 | Matches the beginning of the line. |
42fc5d26 QY |
2428 | |
2429 | $ | |
c1a54c05 | 2430 | Matches the end of the line. |
42fc5d26 QY |
2431 | |
2432 | _ | |
8fcedbd2 QY |
2433 | The ``_`` character has special meanings in BGP regular expressions. It |
2434 | matches to space and comma , and AS set delimiter ``{`` and ``}`` and AS | |
2435 | confederation delimiter ``(`` and ``)``. And it also matches to the | |
2436 | beginning of the line and the end of the line. So ``_`` can be used for AS | |
2437 | value boundaries match. This character technically evaluates to | |
2438 | ``(^|[,{}()]|$)``. | |
42fc5d26 | 2439 | |
42fc5d26 | 2440 | |
c1a54c05 | 2441 | .. _bgp-configuration-examples: |
42fc5d26 | 2442 | |
8fcedbd2 QY |
2443 | Miscellaneous Configuration Examples |
2444 | ==================================== | |
42fc5d26 | 2445 | |
9eb95b3b QY |
2446 | Example of a session to an upstream, advertising only one prefix to it. |
2447 | ||
2448 | .. code-block:: frr | |
42fc5d26 | 2449 | |
c1a54c05 QY |
2450 | router bgp 64512 |
2451 | bgp router-id 10.236.87.1 | |
2452 | neighbor upstream peer-group | |
2453 | neighbor upstream remote-as 64515 | |
2454 | neighbor upstream capability dynamic | |
2455 | neighbor 10.1.1.1 peer-group upstream | |
2456 | neighbor 10.1.1.1 description ACME ISP | |
c3c5a71f | 2457 | |
c1a54c05 QY |
2458 | address-family ipv4 unicast |
2459 | network 10.236.87.0/24 | |
2460 | neighbor upstream prefix-list pl-allowed-adv out | |
2461 | exit-address-family | |
2462 | ! | |
2463 | ip prefix-list pl-allowed-adv seq 5 permit 82.195.133.0/25 | |
2464 | ip prefix-list pl-allowed-adv seq 10 deny any | |
42fc5d26 | 2465 | |
aa9eafa4 QY |
2466 | A more complex example including upstream, peer and customer sessions |
2467 | advertising global prefixes and NO_EXPORT prefixes and providing actions for | |
2468 | customer routes based on community values. Extensive use is made of route-maps | |
2469 | and the 'call' feature to support selective advertising of prefixes. This | |
2470 | example is intended as guidance only, it has NOT been tested and almost | |
2471 | certainly contains silly mistakes, if not serious flaws. | |
42fc5d26 | 2472 | |
9eb95b3b | 2473 | .. code-block:: frr |
42fc5d26 | 2474 | |
c1a54c05 QY |
2475 | router bgp 64512 |
2476 | bgp router-id 10.236.87.1 | |
2477 | neighbor upstream capability dynamic | |
2478 | neighbor cust capability dynamic | |
2479 | neighbor peer capability dynamic | |
2480 | neighbor 10.1.1.1 remote-as 64515 | |
2481 | neighbor 10.1.1.1 peer-group upstream | |
2482 | neighbor 10.2.1.1 remote-as 64516 | |
2483 | neighbor 10.2.1.1 peer-group upstream | |
2484 | neighbor 10.3.1.1 remote-as 64517 | |
2485 | neighbor 10.3.1.1 peer-group cust-default | |
2486 | neighbor 10.3.1.1 description customer1 | |
2487 | neighbor 10.4.1.1 remote-as 64518 | |
2488 | neighbor 10.4.1.1 peer-group cust | |
2489 | neighbor 10.4.1.1 description customer2 | |
2490 | neighbor 10.5.1.1 remote-as 64519 | |
2491 | neighbor 10.5.1.1 peer-group peer | |
2492 | neighbor 10.5.1.1 description peer AS 1 | |
2493 | neighbor 10.6.1.1 remote-as 64520 | |
2494 | neighbor 10.6.1.1 peer-group peer | |
2495 | neighbor 10.6.1.1 description peer AS 2 | |
2496 | ||
2497 | address-family ipv4 unicast | |
2498 | network 10.123.456.0/24 | |
2499 | network 10.123.456.128/25 route-map rm-no-export | |
2500 | neighbor upstream route-map rm-upstream-out out | |
2501 | neighbor cust route-map rm-cust-in in | |
2502 | neighbor cust route-map rm-cust-out out | |
2503 | neighbor cust send-community both | |
2504 | neighbor peer route-map rm-peer-in in | |
2505 | neighbor peer route-map rm-peer-out out | |
2506 | neighbor peer send-community both | |
2507 | neighbor 10.3.1.1 prefix-list pl-cust1-network in | |
2508 | neighbor 10.4.1.1 prefix-list pl-cust2-network in | |
2509 | neighbor 10.5.1.1 prefix-list pl-peer1-network in | |
2510 | neighbor 10.6.1.1 prefix-list pl-peer2-network in | |
2511 | exit-address-family | |
2512 | ! | |
2513 | ip prefix-list pl-default permit 0.0.0.0/0 | |
2514 | ! | |
2515 | ip prefix-list pl-upstream-peers permit 10.1.1.1/32 | |
2516 | ip prefix-list pl-upstream-peers permit 10.2.1.1/32 | |
2517 | ! | |
2518 | ip prefix-list pl-cust1-network permit 10.3.1.0/24 | |
2519 | ip prefix-list pl-cust1-network permit 10.3.2.0/24 | |
2520 | ! | |
2521 | ip prefix-list pl-cust2-network permit 10.4.1.0/24 | |
2522 | ! | |
2523 | ip prefix-list pl-peer1-network permit 10.5.1.0/24 | |
2524 | ip prefix-list pl-peer1-network permit 10.5.2.0/24 | |
2525 | ip prefix-list pl-peer1-network permit 192.168.0.0/24 | |
2526 | ! | |
2527 | ip prefix-list pl-peer2-network permit 10.6.1.0/24 | |
2528 | ip prefix-list pl-peer2-network permit 10.6.2.0/24 | |
2529 | ip prefix-list pl-peer2-network permit 192.168.1.0/24 | |
2530 | ip prefix-list pl-peer2-network permit 192.168.2.0/24 | |
2531 | ip prefix-list pl-peer2-network permit 172.16.1/24 | |
2532 | ! | |
2533 | ip as-path access-list asp-own-as permit ^$ | |
2534 | ip as-path access-list asp-own-as permit _64512_ | |
2535 | ! | |
2536 | ! ################################################################# | |
2537 | ! Match communities we provide actions for, on routes receives from | |
2538 | ! customers. Communities values of <our-ASN>:X, with X, have actions: | |
2539 | ! | |
2540 | ! 100 - blackhole the prefix | |
2541 | ! 200 - set no_export | |
2542 | ! 300 - advertise only to other customers | |
2543 | ! 400 - advertise only to upstreams | |
2544 | ! 500 - set no_export when advertising to upstreams | |
2545 | ! 2X00 - set local_preference to X00 | |
2546 | ! | |
2547 | ! blackhole the prefix of the route | |
2548 | ip community-list standard cm-blackhole permit 64512:100 | |
2549 | ! | |
2550 | ! set no-export community before advertising | |
2551 | ip community-list standard cm-set-no-export permit 64512:200 | |
2552 | ! | |
2553 | ! advertise only to other customers | |
2554 | ip community-list standard cm-cust-only permit 64512:300 | |
2555 | ! | |
2556 | ! advertise only to upstreams | |
2557 | ip community-list standard cm-upstream-only permit 64512:400 | |
2558 | ! | |
2559 | ! advertise to upstreams with no-export | |
2560 | ip community-list standard cm-upstream-noexport permit 64512:500 | |
2561 | ! | |
2562 | ! set local-pref to least significant 3 digits of the community | |
2563 | ip community-list standard cm-prefmod-100 permit 64512:2100 | |
2564 | ip community-list standard cm-prefmod-200 permit 64512:2200 | |
2565 | ip community-list standard cm-prefmod-300 permit 64512:2300 | |
2566 | ip community-list standard cm-prefmod-400 permit 64512:2400 | |
2567 | ip community-list expanded cme-prefmod-range permit 64512:2... | |
2568 | ! | |
2569 | ! Informational communities | |
2570 | ! | |
2571 | ! 3000 - learned from upstream | |
2572 | ! 3100 - learned from customer | |
2573 | ! 3200 - learned from peer | |
2574 | ! | |
2575 | ip community-list standard cm-learnt-upstream permit 64512:3000 | |
2576 | ip community-list standard cm-learnt-cust permit 64512:3100 | |
2577 | ip community-list standard cm-learnt-peer permit 64512:3200 | |
2578 | ! | |
2579 | ! ################################################################### | |
2580 | ! Utility route-maps | |
2581 | ! | |
2582 | ! These utility route-maps generally should not used to permit/deny | |
2583 | ! routes, i.e. they do not have meaning as filters, and hence probably | |
2584 | ! should be used with 'on-match next'. These all finish with an empty | |
2585 | ! permit entry so as not interfere with processing in the caller. | |
2586 | ! | |
2587 | route-map rm-no-export permit 10 | |
2588 | set community additive no-export | |
2589 | route-map rm-no-export permit 20 | |
2590 | ! | |
2591 | route-map rm-blackhole permit 10 | |
f6aa36f5 | 2592 | description blackhole, up-pref and ensure it cannot escape this AS |
c1a54c05 QY |
2593 | set ip next-hop 127.0.0.1 |
2594 | set local-preference 10 | |
2595 | set community additive no-export | |
2596 | route-map rm-blackhole permit 20 | |
2597 | ! | |
2598 | ! Set local-pref as requested | |
2599 | route-map rm-prefmod permit 10 | |
2600 | match community cm-prefmod-100 | |
2601 | set local-preference 100 | |
2602 | route-map rm-prefmod permit 20 | |
2603 | match community cm-prefmod-200 | |
2604 | set local-preference 200 | |
2605 | route-map rm-prefmod permit 30 | |
2606 | match community cm-prefmod-300 | |
2607 | set local-preference 300 | |
2608 | route-map rm-prefmod permit 40 | |
2609 | match community cm-prefmod-400 | |
2610 | set local-preference 400 | |
2611 | route-map rm-prefmod permit 50 | |
2612 | ! | |
2613 | ! Community actions to take on receipt of route. | |
2614 | route-map rm-community-in permit 10 | |
2615 | description check for blackholing, no point continuing if it matches. | |
2616 | match community cm-blackhole | |
2617 | call rm-blackhole | |
2618 | route-map rm-community-in permit 20 | |
2619 | match community cm-set-no-export | |
2620 | call rm-no-export | |
2621 | on-match next | |
2622 | route-map rm-community-in permit 30 | |
2623 | match community cme-prefmod-range | |
2624 | call rm-prefmod | |
2625 | route-map rm-community-in permit 40 | |
2626 | ! | |
2627 | ! ##################################################################### | |
2628 | ! Community actions to take when advertising a route. | |
2629 | ! These are filtering route-maps, | |
2630 | ! | |
2631 | ! Deny customer routes to upstream with cust-only set. | |
2632 | route-map rm-community-filt-to-upstream deny 10 | |
2633 | match community cm-learnt-cust | |
2634 | match community cm-cust-only | |
2635 | route-map rm-community-filt-to-upstream permit 20 | |
2636 | ! | |
2637 | ! Deny customer routes to other customers with upstream-only set. | |
2638 | route-map rm-community-filt-to-cust deny 10 | |
2639 | match community cm-learnt-cust | |
2640 | match community cm-upstream-only | |
2641 | route-map rm-community-filt-to-cust permit 20 | |
2642 | ! | |
2643 | ! ################################################################### | |
2644 | ! The top-level route-maps applied to sessions. Further entries could | |
2645 | ! be added obviously.. | |
2646 | ! | |
2647 | ! Customers | |
2648 | route-map rm-cust-in permit 10 | |
2649 | call rm-community-in | |
2650 | on-match next | |
2651 | route-map rm-cust-in permit 20 | |
2652 | set community additive 64512:3100 | |
2653 | route-map rm-cust-in permit 30 | |
2654 | ! | |
2655 | route-map rm-cust-out permit 10 | |
2656 | call rm-community-filt-to-cust | |
2657 | on-match next | |
2658 | route-map rm-cust-out permit 20 | |
2659 | ! | |
2660 | ! Upstream transit ASes | |
2661 | route-map rm-upstream-out permit 10 | |
2662 | description filter customer prefixes which are marked cust-only | |
2663 | call rm-community-filt-to-upstream | |
2664 | on-match next | |
2665 | route-map rm-upstream-out permit 20 | |
2666 | description only customer routes are provided to upstreams/peers | |
2667 | match community cm-learnt-cust | |
2668 | ! | |
2669 | ! Peer ASes | |
2670 | ! outbound policy is same as for upstream | |
2671 | route-map rm-peer-out permit 10 | |
2672 | call rm-upstream-out | |
2673 | ! | |
2674 | route-map rm-peer-in permit 10 | |
2675 | set community additive 64512:3200 | |
c3c5a71f | 2676 | |
8fcedbd2 QY |
2677 | |
2678 | Example of how to set up a 6-Bone connection. | |
2679 | ||
2680 | .. code-block:: frr | |
2681 | ||
2682 | ! bgpd configuration | |
2683 | ! ================== | |
2684 | ! | |
2685 | ! MP-BGP configuration | |
2686 | ! | |
2687 | router bgp 7675 | |
2688 | bgp router-id 10.0.0.1 | |
2689 | neighbor 3ffe:1cfa:0:2:2a0:c9ff:fe9e:f56 remote-as `as-number` | |
2690 | ! | |
2691 | address-family ipv6 | |
2692 | network 3ffe:506::/32 | |
2693 | neighbor 3ffe:1cfa:0:2:2a0:c9ff:fe9e:f56 activate | |
2694 | neighbor 3ffe:1cfa:0:2:2a0:c9ff:fe9e:f56 route-map set-nexthop out | |
2695 | neighbor 3ffe:1cfa:0:2:2c0:4fff:fe68:a231 remote-as `as-number` | |
2696 | neighbor 3ffe:1cfa:0:2:2c0:4fff:fe68:a231 route-map set-nexthop out | |
2697 | exit-address-family | |
2698 | ! | |
2699 | ipv6 access-list all permit any | |
2700 | ! | |
2701 | ! Set output nexthop address. | |
2702 | ! | |
2703 | route-map set-nexthop permit 10 | |
2704 | match ipv6 address all | |
2705 | set ipv6 nexthop global 3ffe:1cfa:0:2:2c0:4fff:fe68:a225 | |
2706 | set ipv6 nexthop local fe80::2c0:4fff:fe68:a225 | |
2707 | ! | |
2708 | log file bgpd.log | |
2709 | ! | |
2710 | ||
2711 | ||
9e146a81 | 2712 | .. include:: routeserver.rst |
f3817860 QY |
2713 | |
2714 | .. include:: rpki.rst | |
c1a54c05 | 2715 | |
00458d01 PG |
2716 | .. include:: flowspec.rst |
2717 | ||
d1e7591e | 2718 | .. [#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 |
2719 | .. [bgp-route-osci-cond] McPherson, D. and Gill, V. and Walton, D., "Border Gateway Protocol (BGP) Persistent Route Oscillation Condition", IETF RFC3345 |
2720 | .. [stable-flexible-ibgp] Flavel, A. and M. Roughan, "Stable and flexible iBGP", ACM SIGCOMM 2009 | |
2721 | .. [ibgp-correctness] Griffin, T. and G. Wilfong, "On the correctness of IBGP configuration", ACM SIGCOMM 2002 |