From 8943fc9f877cbee3301a8261ddd27b4b1f15f174 Mon Sep 17 00:00:00 2001 From: rebortg Date: Mon, 30 Nov 2020 20:53:36 +0100 Subject: arrange services and protocols --- docs/configuration/protocols/mpls.rst | 157 ++++++++++++++++++++++++++++++++++ 1 file changed, 157 insertions(+) create mode 100644 docs/configuration/protocols/mpls.rst (limited to 'docs/configuration/protocols/mpls.rst') diff --git a/docs/configuration/protocols/mpls.rst b/docs/configuration/protocols/mpls.rst new file mode 100644 index 00000000..82e99a17 --- /dev/null +++ b/docs/configuration/protocols/mpls.rst @@ -0,0 +1,157 @@ +.. _mpls: + +#################################### +MPLS (Multiprotocol Label Switching) +#################################### + +:abbr:`MPLS (Multi-Protocol Label Switching)` is a packet forwarding paradigm +which differs from regular IP forwarding. Instead of IP addresses being used to +make the decision on finding the exit interface, a router will instead use an +exact match on a 32 bit/4 byte header called the MPLS label. This label is +inserted between the ethernet (layer 2) header and the IP (layer 3) header. +One can statically or dynamically assign label allocations, but we will focus +on dynamic allocation of labels using some sort of label distribution protocol +(such as the aptly named Label Distribution Protocol / LDP, Resource Reservation +Protocol / RSVP, or Segment Routing through OSPF/ISIS). These protocols allow +for the creation of a unidirectional/unicast path called a labeled switched +path (initialized as LSP) throughout the network that operates very much like +a tunnel through the network. An easy way of thinking about how an MPLS LSP +actually forwards traffic throughout a network is to think of a GRE tunnel. +They are not the same in how they operate, but they are the same in how they +handle the tunneled packet. It would be good to think of MPLS as a tunneling +technology that can be used to transport many different types of packets, to +aid in traffic engineering by allowing one to specify paths throughout the +network (using RSVP or SR), and to generally allow for easier intra/inter +network transport of data packets. + +For more information on how MPLS label switching works, please go visit +`Wikipedia (MPLS)`_. + +.. note:: MPLS support in VyOS is not finished yet, and therefore its + functionality is limited. Currently there is no support for MPLS enabled VPN + services such as L3VPNs, L2VPNs, and mVPNs. RSVP support is also not present + as the underlying routing stack (FRR) does not implement it. Currently VyOS + can be configured as a label switched router (MPLS P router), in both + penultimate and ultimate hop popping operations. + +Label Distribution Protocol +=========================== + +The :abbr:`MPLS (Multi-Protocol Label Switching)` architecture does not assume +a single protocol to create MPLS paths. VyOS supports the Label Distribution +Protocol (LDP) as implemented by FRR, based on :rfc:`5036`. + +:abbr:`LDP (Label Distribution Protocol)` is a TCP based MPLS signaling protocol +that distributes labels creating MPLS label switched paths in a dynamic manner. +LDP is not a routing protocol, as it relies on other routing protocols for +forwarding decisions. LDP cannot bootstrap itself, and therefore relies on said +routing protocols for communication with other routers that use LDP. + +In order to allow for LDP on the local router to exchange label advertisements +with other routers, a TCP session will be established between automatically +discovered and statically assigned routers. LDP will try to establish a TCP +session to the **transport address** of other routers. Therefore for LDP to +function properly please make sure the transport address is shown in the +routing table and reachable to traffic at all times. + +It is highly recommended to use the same address for both the LDP router-id and +the discovery transport address, but for VyOS MPLS LDP to work both parameters +must be explicitly set in the configuration. + +Configuration Options +===================== + +.. cfgcmd:: set protocols mpls ldp interface + + Use this command to enable LDP, and enable MPLS processing on the interface you + define. + +.. cfgcmd:: set protocols mpls ldp router-id
+ + Use this command to configure the IP address used as the LDP router-id of the + local device. + +.. cfgcmd:: set protocols mpls ldp discovery transport-ipv4-address +.. cfgcmd:: set protocols mpls ldp discovery transport-ipv6-address + + Use this command to set the IPv4 or IPv6 transport-address used by LDP. + +.. cfgcmd:: set protocols mpls ldp neighbor password + + Use this command to configure authentication for LDP peers. Set the + IP address of the LDP peer and a password that should be shared in + order to become neighbors. + +.. cfgcmd:: set protocols mpls ldp discovery hello-interval +.. cfgcmd:: set protocols mpls ldp discovery hello-holdtime + + Use this command if you would like to set the discovery hello and hold time + parameters. + +.. cfgcmd:: set protocols mpls ldp discovery session-ipv4-holdtime +.. cfgcmd:: set protocols mpls ldp discovery session-ipv6-holdtime + + Use this command if you would like to set the TCP session hold time intervals. + +.. cfgcmd:: set protocols mpls ldp export ipv4 explicit-null +.. cfgcmd:: set protocols mpls ldp export ipv6 explicit-null + + Use this command if you would like for the router to advertise FECs with a label + of 0 for explicit null operations. + + +Sample configuration to setup LDP on VyOS +----------------------------------------- + +.. code-block:: none + + set protocols ospf area 0 network '192.168.255.252/32' <--- Routing for loopback + set protocols ospf area 0 network '192.168.0.5/32' <--- Routing for an interface connecting to the network + set protocols ospf parameters router-id '192.168.255.252' <--- Router ID setting for OSPF + set protocols mpls ldp discovery transport-ipv4-address '192.168.255.252' <--- Transport address for LDP for TCP sessions to connect to + set protocols mpls ldp interface 'eth1' <--- Enable MPLS and LDP for an interface connecting to network + set protocols mpls ldp interface 'lo' <--- Enable MPLS and LDP on loopback for future services connectivity + set protocols mpls ldp router-id '192.168.255.252' <--- Router ID setting for LDP + set interfaces ethernet eth1 address '192.168.0.5/31' <--- Interface IP for connecting to network + set interfaces loopback lo address '192.168.255.252/32' <--- Interface loopback IP for router ID and other uses + + +Operational Mode Commands +========================= + +When LDP is working, you will be able to see label information in the outcome +of ``show ip route``. Besides that information, there are also specific *show* +commands for LDP: + +Show +---- + +.. opcmd:: show mpls ldp binding + + Use this command to see the Label Information Base. + +.. opcmd:: show mpls ldp discovery + + Use this command to see discovery hello information + +.. opcmd:: show mpls ldp interface + + Use this command to see LDP interface information + +.. opcmd:: show mpls ldp neighbor + + Use this command to see LDP neighbor information + +.. opcmd:: show mpls ldp neighbor detail + + Use this command to see detailed LDP neighbor information + +Reset +----- + +.. opcmd:: reset mpls ldp neighbor + + Use this command to reset an LDP neighbor/TCP session that is established + + +.. _`Wikipedia (MPLS)`: https://en.wikipedia.org/wiki/Multiprotocol_Label_Switching -- cgit v1.2.3 From d6af3a609f478f4affd7b0d40ca9bd612db1dc64 Mon Sep 17 00:00:00 2001 From: Cheeze_It Date: Wed, 9 Dec 2020 12:41:04 -0700 Subject: mpls-conf: T915: Added documentation for LDP import and export Added examples for the new import and export functionality that LDP is now getting on vyos/vyos-1x#639 --- docs/configuration/protocols/mpls.rst | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) (limited to 'docs/configuration/protocols/mpls.rst') diff --git a/docs/configuration/protocols/mpls.rst b/docs/configuration/protocols/mpls.rst index 4451c5c3..1814cbb1 100644 --- a/docs/configuration/protocols/mpls.rst +++ b/docs/configuration/protocols/mpls.rst @@ -111,6 +111,22 @@ Configuration Options Use this command if you would like to set the TCP session hold time intervals. +.. cfgcmd:: set protocols mpls ldp import ipv4 import-filter filter-access-list +.. cfgcmd:: set protocols mpls ldp import ipv6 import-filter filter-access-list6 + + Use these commands to control the importing of forwarding equivalence classes + (FECs) for LDP from neighbors. This would be useful for example on only + accepting the labeled routes that are needed and not ones that are not + needed, such as accepting loopback interfaces and rejecting all others. + +.. cfgcmd:: set protocols mpls ldp export ipv4 export-filter filter-access-list +.. cfgcmd:: set protocols mpls ldp export ipv6 export-filter filter-access-list6 + + Use these commands to control the exporting of forwarding equivalence classes + (FECs) for LDP to neighbors. This would be useful for example on only + announcing the labeled routes that are needed and not ones that are not + needed, such as announcing loopback interfaces and no others. + .. cfgcmd:: set protocols mpls ldp export ipv4 explicit-null .. cfgcmd:: set protocols mpls ldp export ipv6 explicit-null -- cgit v1.2.3 From 52828ba38878810aef96450d4eab122dffeecf6d Mon Sep 17 00:00:00 2001 From: Christian Poessinger Date: Thu, 10 Dec 2020 18:20:57 +0100 Subject: mpls: use short description for headline --- docs/configuration/protocols/mpls.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/configuration/protocols/mpls.rst') diff --git a/docs/configuration/protocols/mpls.rst b/docs/configuration/protocols/mpls.rst index 1814cbb1..7d930016 100644 --- a/docs/configuration/protocols/mpls.rst +++ b/docs/configuration/protocols/mpls.rst @@ -1,8 +1,8 @@ .. _mpls: -#################################### -MPLS (Multiprotocol Label Switching) -#################################### +#### +MPLS +#### :abbr:`MPLS (Multi-Protocol Label Switching)` is a packet forwarding paradigm which differs from regular IP forwarding. Instead of IP addresses being used to -- cgit v1.2.3 From 42eb7c8ee7f2d8db588f3de85537a2a0e9c3e553 Mon Sep 17 00:00:00 2001 From: Christian Poessinger Date: Thu, 10 Dec 2020 18:21:09 +0100 Subject: mpls: use proper line break limit --- docs/configuration/protocols/mpls.rst | 100 +++++++++++++++++++--------------- 1 file changed, 57 insertions(+), 43 deletions(-) (limited to 'docs/configuration/protocols/mpls.rst') diff --git a/docs/configuration/protocols/mpls.rst b/docs/configuration/protocols/mpls.rst index 7d930016..863e7f62 100644 --- a/docs/configuration/protocols/mpls.rst +++ b/docs/configuration/protocols/mpls.rst @@ -58,26 +58,27 @@ It is highly recommended to use the same address for both the LDP router-id and the discovery transport address, but for VyOS MPLS LDP to work both parameters must be explicitly set in the configuration. -Another thing to keep in mind with LDP is that much like BGP, it is a protocol that -runs on top of TCP. It however does not have an ability to do something like a -refresh capability like BGPs route refresh capability. Therefore one might have -to reset the neighbor for a capability change or a configuration change to work. +Another thing to keep in mind with LDP is that much like BGP, it is a protocol +that runs on top of TCP. It however does not have an ability to do something +like a refresh capability like BGPs route refresh capability. Therefore one +might have to reset the neighbor for a capability change or a configuration +change to work. Configuration Options ===================== .. cfgcmd:: set protocols mpls ldp interface - Use this command to enable LDP, and enable MPLS processing on the interface you - define. + Use this command to enable LDP, and enable MPLS processing on the interface + you define. .. cfgcmd:: set protocols mpls ldp router-id
Use this command to configure the IP address used as the LDP router-id of the local device. -.. cfgcmd:: set protocols mpls ldp discovery transport-ipv4-address -.. cfgcmd:: set protocols mpls ldp discovery transport-ipv6-address +.. cfgcmd:: set protocols mpls ldp discovery transport-ipv4-address
+.. cfgcmd:: set protocols mpls ldp discovery transport-ipv6-address
Use this command to set the IPv4 or IPv6 transport-address used by LDP. @@ -85,18 +86,19 @@ Configuration Options Use this command to configure authentication for LDP peers. Set the IP address of the LDP peer and a password that should be shared in - order to become neighbors. - + order to become neighbors. + .. cfgcmd:: set protocols mpls ldp neighbor
session-holdtime - + Use this command to configure a specific session hold time for LDP peers. Set the IP address of the LDP peer and a session hold time that should be configured for it. You may have to reset the neighbor for this to work. - -.. cfgcmd:: set protocols mpls ldp neighbor
ttl-security + +.. cfgcmd:: set protocols mpls ldp neighbor
ttl-security + Use this command to enable, disable, or specify hop count for TTL security - for LDP peers. By default the value is set to 255 (or max TTL). + for LDP peers. By default the value is set to 255 (or max TTL). .. cfgcmd:: set protocols mpls ldp discovery hello-ipv4-interval .. cfgcmd:: set protocols mpls ldp discovery hello-ipv4-holdtime @@ -111,16 +113,20 @@ Configuration Options Use this command if you would like to set the TCP session hold time intervals. -.. cfgcmd:: set protocols mpls ldp import ipv4 import-filter filter-access-list -.. cfgcmd:: set protocols mpls ldp import ipv6 import-filter filter-access-list6 +.. cfgcmd:: set protocols mpls ldp import ipv4 import-filter filter-access-list + +.. cfgcmd:: set protocols mpls ldp import ipv6 import-filter filter-access-list6 + Use these commands to control the importing of forwarding equivalence classes (FECs) for LDP from neighbors. This would be useful for example on only accepting the labeled routes that are needed and not ones that are not needed, such as accepting loopback interfaces and rejecting all others. - -.. cfgcmd:: set protocols mpls ldp export ipv4 export-filter filter-access-list -.. cfgcmd:: set protocols mpls ldp export ipv6 export-filter filter-access-list6 + +.. cfgcmd:: set protocols mpls ldp export ipv4 export-filter filter-access-list + +.. cfgcmd:: set protocols mpls ldp export ipv6 export-filter filter-access-list6 + Use these commands to control the exporting of forwarding equivalence classes (FECs) for LDP to neighbors. This would be useful for example on only @@ -130,43 +136,51 @@ Configuration Options .. cfgcmd:: set protocols mpls ldp export ipv4 explicit-null .. cfgcmd:: set protocols mpls ldp export ipv6 explicit-null - Use this command if you would like for the router to advertise FECs with a label - of 0 for explicit null operations. - -.. cfgcmd:: set protocols mpls ldp allocation ipv4 access-list -.. cfgcmd:: set protocols mpls ldp allocation ipv6 access-list6 + Use this command if you would like for the router to advertise FECs with a + label of 0 for explicit null operations. + +.. cfgcmd:: set protocols mpls ldp allocation ipv4 access-list + +.. cfgcmd:: set protocols mpls ldp allocation ipv6 access-list6 + + + Use this command if you would like to control the local FEC allocations for + LDP. A good example would be for your local router to not allocate a label for + everything. Just a label for what it's useful. A good example would be just a + loopback label. - Use this command if you would like to control the local FEC allocations for LDP. A - good example would be for your local router to not allocate a label for everything. - Just a label for what it's useful. A good example would be just a loopback label. - .. cfgcmd:: set protocols mpls ldp parameters cisco-interop-tlv - Use this command to use a Cisco non-compliant format to send and interpret the - Dual-Stack capability TLV for IPv6 LDP communications. This is related to :rfc:`7552`. - + Use this command to use a Cisco non-compliant format to send and interpret + the Dual-Stack capability TLV for IPv6 LDP communications. This is related to + :rfc:`7552`. + .. cfgcmd:: set protocols mpls ldp parameters transport-prefer-ipv4 - Use this command to prefer IPv4 for TCP peer transport connection for LDP when - both an IPv4 and IPv6 LDP address are configured on the same interface. - + Use this command to prefer IPv4 for TCP peer transport connection for LDP + when both an IPv4 and IPv6 LDP address are configured on the same interface. + .. cfgcmd:: set protocols mpls ldp targeted-neighbor ipv4 enable .. cfgcmd:: set protocols mpls ldp targeted-neighbor ipv6 enable - Use this command to enable targeted LDP sessions to the local router. The router - will then respond to any sessions that are trying to connect to it that are not - a link local type of TCP connection. - + Use this command to enable targeted LDP sessions to the local router. The + router will then respond to any sessions that are trying to connect to it that + are not a link local type of TCP connection. + .. cfgcmd:: set protocols mpls ldp targeted-neighbor ipv4 address
.. cfgcmd:: set protocols mpls ldp targeted-neighbor ipv6 address
Use this command to enable the local router to try and connect with a targeted LDP session to another router. - -.. cfgcmd:: set protocols mpls ldp targeted-neighbor ipv4 hello-holdtime -.. cfgcmd:: set protocols mpls ldp targeted-neighbor ipv4 hello-interval -.. cfgcmd:: set protocols mpls ldp targeted-neighbor ipv6 hello-holdtime -.. cfgcmd:: set protocols mpls ldp targeted-neighbor ipv6 hello-interval + +.. cfgcmd:: set protocols mpls ldp targeted-neighbor ipv4 hello-holdtime + +.. cfgcmd:: set protocols mpls ldp targeted-neighbor ipv4 hello-interval + +.. cfgcmd:: set protocols mpls ldp targeted-neighbor ipv6 hello-holdtime + +.. cfgcmd:: set protocols mpls ldp targeted-neighbor ipv6 hello-interval + Use these commands if you would like to set the discovery hello and hold time parameters for the targeted LDP neighbors. -- cgit v1.2.3 From 7b04596343a1894a638ff1de030fb0a179980194 Mon Sep 17 00:00:00 2001 From: rebortg Date: Fri, 11 Dec 2020 22:41:24 +0100 Subject: protocols: fix lint errors --- docs/configuration/protocols/bfd.rst | 9 ++++++--- docs/configuration/protocols/igmp.rst | 12 ++++++++---- docs/configuration/protocols/isis.rst | 20 ++++++++++++-------- docs/configuration/protocols/mpls.rst | 4 ++++ docs/configuration/protocols/rpki.rst | 6 +++++- docs/configuration/protocols/static.rst | 24 ++++++++++++++++-------- 6 files changed, 51 insertions(+), 24 deletions(-) (limited to 'docs/configuration/protocols/mpls.rst') diff --git a/docs/configuration/protocols/bfd.rst b/docs/configuration/protocols/bfd.rst index b8fdf489..20ff3b8a 100644 --- a/docs/configuration/protocols/bfd.rst +++ b/docs/configuration/protocols/bfd.rst @@ -25,19 +25,22 @@ Configure BFD Allow this BFD peer to not be directly connected -.. cfgcmd:: set protocols bfd peer
source [address
| interface ] +.. cfgcmd:: set protocols bfd peer
source + [address
| interface ] Bind listener to specifid interface/address, mandatory for IPv6 .. cfgcmd:: set protocols bfd peer
interval echo-interval <10-60000> - The minimal echo receive transmission interval that this system is capable of handling + The minimal echo receive transmission interval that this system is + capable of handling .. cfgcmd:: set protocols bfd peer
interval multiplier <2-255> Remote transmission interval will be multiplied by this value -.. cfgcmd:: set protocols bfd peer
interval [receive | transmit] <10-60000> +.. cfgcmd:: set protocols bfd peer
interval + [receive | transmit] <10-60000> Interval in milliseconds diff --git a/docs/configuration/protocols/igmp.rst b/docs/configuration/protocols/igmp.rst index 9104b0c9..7109deb6 100644 --- a/docs/configuration/protocols/igmp.rst +++ b/docs/configuration/protocols/igmp.rst @@ -96,7 +96,8 @@ These are the commands for a basic setup. can communicate with PIM neighbors. -.. cfgcmd:: set protocols pim rp address
group +.. cfgcmd:: set protocols pim rp address
group + Use this comand to manually configure a Rendevouz Point for PIM so that join messages can be sent there. Set the Rendevouz Point address @@ -140,7 +141,8 @@ You can also tune multicast with the following commands. platforms cannot see data flowing in better than 30 second chunks. -.. cfgcmd:: set protocols igmp interface join source +.. cfgcmd:: set protocols igmp interface join + source Use this command to allow the selected interface join a multicast group defining the multicast address you want to join and the source @@ -153,7 +155,8 @@ You can also tune multicast with the following commands. host query interval (1-1800) in seconds that PIM will use. -.. cfgcmd:: set protocols igmp interface +.. cfgcmd:: set protocols igmp interface Use this command to configure in the selected interface the IGMP query response timeout value (10-250) in deciseconds. If a report is @@ -180,7 +183,8 @@ upstream interface, and one or more downstream interfaces. Configuration ============= -.. cfgcmd:: set protocols igmp-proxy interface role +.. cfgcmd:: set protocols igmp-proxy interface role + * **upstream:** The upstream network interface is the outgoing interface which is responsible for communicating to available multicast data sources. diff --git a/docs/configuration/protocols/isis.rst b/docs/configuration/protocols/isis.rst index 64cc2535..753637f9 100644 --- a/docs/configuration/protocols/isis.rst +++ b/docs/configuration/protocols/isis.rst @@ -6,12 +6,14 @@ IS-IS ##### -:abbr:`IS-IS (Intermediate System to Intermediate System)` is a link-state interior gateway routing protocol. -Like OSPF, IS-IS runs the Dijkstra shortest-path first (SPF) algorithm to create a database of the network’s -topology and, from that database, to determine the best (that is, shortest) path to a destination. -The routers exchange topology information with their nearest neighbors. -IS-IS runs directly on the data link layer (Layer 2). -IS-IS addresses are called :abbr:`NETs (Network Entity Titles)` and can be 8 to 20 bytes long, but are generally 10 bytes long. +:abbr:`IS-IS (Intermediate System to Intermediate System)` is a link-state +interior gateway routing protocol. Like OSPF, IS-IS runs the Dijkstra +shortest-path first (SPF) algorithm to create a database of the network’s +topology and, from that database, to determine the best (that is, shortest) +path to a destination. The routers exchange topology information with their +nearest neighbors. IS-IS runs directly on the data link layer (Layer 2). +IS-IS addresses are called :abbr:`NETs (Network Entity Titles)` and can be +8 to 20 bytes long, but are generally 10 bytes long. For example :abbr:`NET (Network Entity Title)` @@ -28,12 +30,14 @@ The IS-IS address consists of three parts: ``0001`` IS-IS area number (Area1) System identifier: - ``1921.6800.1002`` For system idetifier we recommend to use IP address or MAC address of the router. + ``1921.6800.1002`` For system idetifier we recommend to use IP address or + MAC address of the router. NET selector: ``00`` Must always be 00, to indicate "this system". -Simple IS-IS configuration using 2 nodes and redistributing connected interfaces. +Simple IS-IS configuration using 2 nodes and redistributing connected +interfaces. **Node 1:** diff --git a/docs/configuration/protocols/mpls.rst b/docs/configuration/protocols/mpls.rst index 863e7f62..3b59d8ea 100644 --- a/docs/configuration/protocols/mpls.rst +++ b/docs/configuration/protocols/mpls.rst @@ -240,4 +240,8 @@ Reset Use this command to reset an LDP neighbor/TCP session that is established +.. stop_vyoslinter + .. _`Wikipedia (MPLS)`: https://en.wikipedia.org/wiki/Multiprotocol_Label_Switching + +.. start_vyoslinter \ No newline at end of file diff --git a/docs/configuration/protocols/rpki.rst b/docs/configuration/protocols/rpki.rst index 9813b1b6..c3ff442b 100644 --- a/docs/configuration/protocols/rpki.rst +++ b/docs/configuration/protocols/rpki.rst @@ -100,6 +100,8 @@ Once your routers are configured to reject RPKI-invalid prefixes, you can test whether the configuration is working correctly using the `RIPE Labs RPKI Test`_ experimental tool. +.. stop_vyoslinter + .. _tweet by EvilMog: https://twitter.com/Evil_Mog/status/1230924170508169216 .. _Routinator: https://www.nlnetlabs.nl/projects/rpki/routinator/ .. _GoRTR: https://github.com/cloudflare/gortr @@ -110,4 +112,6 @@ Test`_ experimental tool. .. _RPKI analytics: https://www.nlnetlabs.nl/projects/rpki/rpki-analytics/ .. _RIPE Labs RPKI Test: https://sg-pub.ripe.net/jasper/rpki-web-test/ .. _excellent guide to RPKI: https://rpki.readthedocs.io/ -.. _help and operational guidance: https://rpki.readthedocs.io/en/latest/about/help.html +.. _help and operational guidance: https://rpki.readthedocs.io/en/latest/about/help.htm + +.. start_vyoslinter diff --git a/docs/configuration/protocols/static.rst b/docs/configuration/protocols/static.rst index 43b77c41..42c0c4b7 100644 --- a/docs/configuration/protocols/static.rst +++ b/docs/configuration/protocols/static.rst @@ -28,7 +28,8 @@ Static Routes Disable this IPv4 static route entry. -.. cfgcmd:: set protocols static route next-hop
distance +.. cfgcmd:: set protocols static route next-hop
+ distance Defines next-hop distance for this route, routes with smaller administrative distance are elected prior those with a higher distance. @@ -47,7 +48,8 @@ Static Routes Disable this IPv6 static route entry. -.. cfgcmd:: set protocols static route6 next-hop
distance +.. cfgcmd:: set protocols static route6 next-hop
+ distance Defines next-hop distance for this route, routes with smaller administrative distance are elected prior those with a higher distance. @@ -61,34 +63,40 @@ Static Routes Interface Routes ================ -.. cfgcmd:: set protocols static interface-route next-hop-interface +.. cfgcmd:: set protocols static interface-route next-hop-interface + Allows you to configure the next-hop interface for an interface-based IPv4 static route. `` will be the next-hop interface where trafic is routed for the given ``. -.. cfgcmd:: set protocols static interface-route next-hop-interface disable +.. cfgcmd:: set protocols static interface-route next-hop-interface + disable Disables interface-based IPv4 static route. -.. cfgcmd:: set protocols static interface-route next-hop-interface distance +.. cfgcmd:: set protocols static interface-route next-hop-interface + distance Defines next-hop distance for this route, routes with smaller administrative distance are elected prior those with a higher distance. Range is 1 to 255, default is 1. -.. cfgcmd:: set protocols static interface-route6 next-hop-interface +.. cfgcmd:: set protocols static interface-route6 next-hop-interface + Allows you to configure the next-hop interface for an interface-based IPv6 static route. `` will be the next-hop interface where trafic is routed for the given ``. -.. cfgcmd:: set protocols static interface-route6 next-hop-interface disable +.. cfgcmd:: set protocols static interface-route6 next-hop-interface + disable Disables interface-based IPv6 static route. -.. cfgcmd:: set protocols static interface-route6 next-hop-interface distance +.. cfgcmd:: set protocols static interface-route6 next-hop-interface + distance Defines next-hop distance for this route, routes with smaller administrative distance are elected prior those with a higher distance. -- cgit v1.2.3 From 0fc606aa74dba402e72ddb6c8abda3b2d0dffe0f Mon Sep 17 00:00:00 2001 From: Cheeze_It Date: Tue, 22 Dec 2020 11:16:50 -0700 Subject: mpls: T915: Added documentation for LDP ordered control Added the ordered control command in the documentation. Also added the RFC in which it is referred to as well. --- docs/configuration/protocols/mpls.rst | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'docs/configuration/protocols/mpls.rst') diff --git a/docs/configuration/protocols/mpls.rst b/docs/configuration/protocols/mpls.rst index 3b59d8ea..312a0df2 100644 --- a/docs/configuration/protocols/mpls.rst +++ b/docs/configuration/protocols/mpls.rst @@ -155,6 +155,12 @@ Configuration Options the Dual-Stack capability TLV for IPv6 LDP communications. This is related to :rfc:`7552`. +.. cfgcmd:: set protocols mpls ldp parameters ordered-control + + Use this command to use ordered label distribution control mode. FRR + by default uses independent label distribution control mode for label + distribution. This is related to :rfc:`5036`. + .. cfgcmd:: set protocols mpls ldp parameters transport-prefer-ipv4 Use this command to prefer IPv4 for TCP peer transport connection for LDP -- cgit v1.2.3