summaryrefslogtreecommitdiff
path: root/docs/configuration/protocols
diff options
context:
space:
mode:
Diffstat (limited to 'docs/configuration/protocols')
-rw-r--r--docs/configuration/protocols/static.rst35
1 files changed, 20 insertions, 15 deletions
diff --git a/docs/configuration/protocols/static.rst b/docs/configuration/protocols/static.rst
index 3e3eb47b..e9016abc 100644
--- a/docs/configuration/protocols/static.rst
+++ b/docs/configuration/protocols/static.rst
@@ -70,10 +70,12 @@ IPv4 BFD
Configure a static route for `<subnet>` using gateway `<address>` and use the
gateway address as BFD peer destination address.
-.. cfgcmd:: set protocols static route <subnet> next-hop <address> bfd profile <profile>
+.. cfgcmd:: set protocols static route <subnet> next-hop <address>
+ bfd profile <profile>
- Configure a static route for `<subnet>` using gateway `<address>` and use the
- gateway address as BFD peer destination address with BFD profile `<profile>`.
+ Configure a static route for `<subnet>` using gateway `<address>`
+ and use the gateway address as BFD peer destination address with
+ BFD profile `<profile>`.
.. cfgcmd:: set protocols static route <subnet> next-hop <address> bfd multi-hop
source-address <source-address>
@@ -153,10 +155,12 @@ IPv6 Unicast Routes
.. note:: Routes with a distance of 255 are effectively disabled and not
installed into the kernel.
-.. cfgcmd:: set protocols static route6 <subnet> next-hop <address> segments <segments>
+.. cfgcmd:: set protocols static route6 <subnet> next-hop <address>
+ segments <segments>
- It is possible to specify a static route for ipv6 prefixes using an SRv6 segments
- instruction. The `/` separator can be used to specify multiple segment instructions.
+ It is possible to specify a static route for ipv6 prefixes using
+ an SRv6 segments instruction. The `/` separator can be used to
+ specify multiple segment instructions.
Example:
@@ -202,8 +206,9 @@ IPv6 Interface Routes
.. cfgcmd:: set protocols static route6 <subnet> interface
<interface> segments <segments>
- It is possible to specify a static route for ipv6 prefixes using an SRv6 segments
- instruction. The `/` separator can be used to specify multiple segment instructions.
+ It is possible to specify a static route for ipv6 prefixes using
+ an SRv6 segments instruction. The `/` separator can be used to
+ specify multiple segment instructions.
Example:
@@ -219,13 +224,15 @@ IPv6 BFD
Configure a static route for `<subnet>` using gateway `<address>` and use the
gateway address as BFD peer destination address.
-.. cfgcmd:: set protocols static route6 <subnet> next-hop <address> bfd profile <profile>
+.. cfgcmd:: set protocols static route6 <subnet> next-hop <address>
+ bfd profile <profile>
- Configure a static route for `<subnet>` using gateway `<address>` and use the
- gateway address as BFD peer destination address with BFD profile `<profile>`.
+ Configure a static route for `<subnet>` using gateway `<address>`
+ and use the gateway address as BFD peer destination address with
+ BFD profile `<profile>`.
-.. cfgcmd:: set protocols static route6 <subnet> next-hop <address> bfd multi-hop
- source-address <source>
+.. cfgcmd:: set protocols static route6 <subnet> next-hop <address>
+ bfd multi-hop source-address <source>
Configure a static route for `<subnet>` using gateway `<address>` and use the
gateway address as BFD peer destination address with source address
@@ -271,7 +278,5 @@ IPv6 Blackhole Routes
Alternate Routing Tables
************************
-TBD
-
Alternate routing tables are used with policy based routing by utilizing
:ref:`vrf`.