summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMark Stapp <mjs.ietf@gmail.com>2023-07-21 08:59:50 -0400
committerGitHub <noreply@github.com>2023-07-21 08:59:50 -0400
commit90f1e4e01781ffdba13a65577329e6380d96cee5 (patch)
tree6ab25148fcf3a9dd4b450f4f53e21a883a07a93e
parent3a58764e3a7a5912187d5d062e06044bc1cd7044 (diff)
parent01ec8c260a843502bccedba990d803b3959c35ec (diff)
Merge pull request #14065 from opensourcerouting/bfd-label-doc
doc: remove BFD label command references
-rw-r--r--doc/user/bfd.rst12
1 files changed, 1 insertions, 11 deletions
diff --git a/doc/user/bfd.rst b/doc/user/bfd.rst
index 776726f193..6c57822510 100644
--- a/doc/user/bfd.rst
+++ b/doc/user/bfd.rst
@@ -225,12 +225,6 @@ BFD peers and profiles share the same BFD session configuration commands.
BFD Peer Specific Commands
--------------------------
-.. clicmd:: label WORD
-
- Labels a peer with the provided word. This word can be referenced
- later on other daemons to refer to a specific peer.
-
-
.. clicmd:: profile BFDPROF
Configure peer to use the profile configurations.
@@ -443,7 +437,6 @@ Here is an example of BFD configuration:
bfd
peer 192.168.0.1
- label home-peer
no shutdown
!
!
@@ -457,7 +450,7 @@ Here is an example of BFD configuration:
!
Peers can be identified by its address (use ``multihop`` when you need
-to specify a multi hop peer) or can be specified manually by a label.
+to specify a multi hop peer).
Here are the available peer configurations:
@@ -500,7 +493,6 @@ Here are the available peer configurations:
! configure a peer with every option possible
peer 192.168.0.4
- label peer-label
detect-multiplier 50
receive-interval 60000
transmit-interval 3000
@@ -548,7 +540,6 @@ You can inspect the current BFD peer status with the following commands:
Echo receive interval: 50ms
peer 192.168.1.1
- label: router3-peer
ID: 2
Remote ID: 2
Status: up
@@ -571,7 +562,6 @@ You can inspect the current BFD peer status with the following commands:
frr# show bfd peer 192.168.1.1
BFD Peer:
peer 192.168.1.1
- label: router3-peer
ID: 2
Remote ID: 2
Status: up