doc: Add --v6-with-v4-nexthops documentation

Signed-off-by: Donald Sharp <sharpd@nvidia.com>

diff --git a/doc/user/bgp.rst b/doc/user/bgp.rst
index ad8f913355dab3138e4c044c267fb4e10da4c89c..09173ab2f55505160fbd6b10681bd509bd41e991 100644 (file)
--- a/doc/user/bgp.rst
+++ b/doc/user/bgp.rst
@@ -86,6 +86,15 @@ be specified (:ref:`common-invocation-options`).
    be done to see if this is helping or not at the scale you are running
    at.
 
+.. option:: --v6-with-v4-nexthops
+
+   Allow BGP to peer in the V6 afi, when the interface only has v4 addresses.
+   This allows bgp to install the v6 routes with a v6 nexthop that has the
+   v4 address encoded in the nexthop.  Zebra's equivalent option currently
+   overrides the bgp setting.  This setting is only really usable when
+   the operator has turned off communication to zebra and is running bgpd
+   as a complete standalone process.
+
 LABEL MANAGER
 -------------
 

diff --git a/doc/user/zebra.rst b/doc/user/zebra.rst
index d7e768b710298241ec7e52a97d2b6da93dbddadf..32de3e908f10e1e25eb5d34a53a41217835a9e94 100644 (file)
--- a/doc/user/zebra.rst
+++ b/doc/user/zebra.rst
@@ -87,6 +87,13 @@ Besides the common invocation options (:ref:`common-invocation-options`), the
    Allow zebra to modify the default receive buffer size to SIZE
    in bytes.  Under \*BSD only the -s option is available.
 
+.. option:: --v6-with-v4-nexthops
+
+   Signal to zebra that v6 routes with v4 nexthops are accepted
+   by the underlying dataplane.  This will be communicated to
+   the upper level daemons that can install v6 routes with v4
+   nexthops.
+
 .. _interface-commands:
 
 Configuration Addresses behaviour