mirrors/bird
mirrors/bird
0
0
Fork 0
mirror of https://gitlab.nic.cz/labs/bird.git synced 2024-12-31 06:01:52 +00:00
Code Releases Activity

Doc: Minor fixes

Browse Source
This commit is contained in:
Ondrej Zajicek 2023-10-06 18:52:02 +02:00
parent c5c3a22bcc
commit 23f94b1368
1 changed files with 12 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
doc/bird.sgml
View File

@ -1116,7 +1116,11 @@ protocol bgp from {
<p>The MPLS domain definition is mandatory for a MPLS router. All MPLS channels <p>The MPLS domain definition is mandatory for a MPLS router. All MPLS channels
and MPLS-aware protocols are associated with some MPLS domain (although usually and MPLS-aware protocols are associated with some MPLS domain (although usually
implicitly with the sole one). In the MPLS domain definition you can configure implicitly with the sole one). In the MPLS domain definition you can configure
details of MPLS label allocation. Currently, there is just one option: details of MPLS label allocation. Currently, there is just one option,
<cf/label range/.
<p>Note that the MPLS subsystem is experimental, it is likely that there will be
some backward-incompatible changes in the future.
<descrip> <descrip>
<tag><label id="mpls-domain-label-range">label range <m/name/ { start <m/number/; length <m/number/; [<m/.../] }</tag> <tag><label id="mpls-domain-label-range">label range <m/name/ { start <m/number/; length <m/number/; [<m/.../] }</tag>
@ -3621,10 +3625,9 @@ future. It is not ready for production usage and therefore it is not compiled
by default and have to be enabled during installation by the configure option by default and have to be enabled during installation by the configure option
<tt/--with-protocols=/. <tt/--with-protocols=/.
<p>The implementation is limited to monitor protocol state changes and routes <p>The implementation supports monitoring protocol state changes, pre-policy
in <ref id="bgp-import-table" name="BGP import tables"> (not regular routing routes (in <ref id="bgp-import-table" name="BGP import tables">) and post-policy
tables), therefore import table must be enabled in BGP protocols. All BGP routes (in regular routing tables). All BGP protocols are monitored automatically.
protocols are monitored automatically.
<sect1>Example <sect1>Example
<label id="bmp-exam"> <label id="bmp-exam">
@ -3634,8 +3637,11 @@ protocol bmp {
# The monitoring station to connect to # The monitoring station to connect to
station address ip 198.51.100.10 port 1790; station address ip 198.51.100.10 port 1790;
# required option # Monitor received routes (in import table)
monitoring rib in pre_policy; monitoring rib in pre_policy;
# Monitor accepted routes (passed import filters)
monitoring rib in post_policy;
} }
</code> </code>