Merge pull request #8599 from Jafaral/old-doc

doc: remove obsolete Netlink discussion, fix svi cmd doc

2 files changed, 11 insertions, 17 deletions

diff --git a/doc/user/bgp.rst b/doc/user/bgp.rst
index fbcf2fb48..87710e98c 100644
--- a/doc/user/bgp.rst
+++ b/doc/user/bgp.rst
@@ -2634,15 +2634,15 @@ the same behavior of using same next-hop and RMAC values.
 Enables or disables advertise-pip feature, specifiy system-IP and/or system-MAC
 parameters.
 
-EVPN advertise-svi
-^^^^^^^^^^^^^^^^^^
+EVPN advertise-svi-ip
+^^^^^^^^^^^^^^^^^^^^^
 Typically, the SVI IP address is reused on VTEPs across multiple racks. However,
-if you have unique SVI IP addresses want those to be reachable you can enable the
+if you have unique SVI IP addresses that you want to be reachable you can use the
 advertise-svi-ip option. This option advertises the SVI IP/MAC address as a type-2
 route and eliminates the need for any flooding over VXLAN to reach the IP from a
 remote VTEP.
 
-.. clicmd:: advertise-svi
+.. clicmd:: advertise-svi-ip
 
 Note that you should not enable both the advertise-svi-ip and the advertise-default-gw
 at the same time.
diff --git a/doc/user/kernel.rst b/doc/user/kernel.rst
index 4c2c7a500..210ede7e9 100644
--- a/doc/user/kernel.rst
+++ b/doc/user/kernel.rst
@@ -6,6 +6,9 @@ Kernel Interface
 
 There are several different methods for reading kernel routing table
 information, updating kernel routing tables, and for looking up interfaces.
+FRR relies heavily on the Netlink (``man 7 netlink``) interface to
+communicate with the Kernel. However, other interfaces are still used
+in some parts of the code.
 
 - ioctl
      This method is a very traditional way for reading or writing kernel
@@ -27,16 +30,7 @@ information, updating kernel routing tables, and for looking up interfaces.
      kernel information.
 
 - routing socket / Netlink
-     On recent Linux kernels (2.0.x and 2.2.x), there is a kernel/user
-     communication support called `Netlink`. It makes asynchronous communication
-     between kernel and FRR possible, similar to a routing socket on BSD systems.
-
-     Before you use this feature, be sure to select (in kernel configuration) the
-     kernel/Netlink support option 'Kernel/User network link driver' and 'Routing
-     messages'.
-
-     Today, the :file:`/dev/route` special device file is obsolete.  Netlink
-     communication is done by reading/writing over Netlink socket.
-
-     After the kernel configuration, please reconfigure and rebuild FRR.  You can
-     use Netlink as a dynamic routing update channel between FRR and the kernel.
+     Netlink first appeard in Linux kernel 2.0. It makes asynchronous
+     communication between the kernel and FRR possible, similar to a routing
+     socket on BSD systems. Netlink communication is done by reading/writing
+     over Netlink socket.