From 5c54512ecc1ee6c4dd0dc0ebc17c57e457bed514 Mon Sep 17 00:00:00 2001 From: Igor Ryzhov Date: Tue, 29 Jun 2021 12:50:10 +0300 Subject: [PATCH] doc: remove "no" from clicmd directives Signed-off-by: Igor Ryzhov --- doc/user/bgp.rst | 6 +++--- doc/user/ospf6d.rst | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/user/bgp.rst b/doc/user/bgp.rst index fe01725b61..73899b08fe 100644 --- a/doc/user/bgp.rst +++ b/doc/user/bgp.rst @@ -2751,7 +2751,7 @@ route with gateway IP. 1. CLI to add gateway IP while generating EVPN type-5 route from a BGP IPv4/IPv6 prefix: -.. clicmd:: [no] advertise unicast [gateway-ip] +.. clicmd:: advertise unicast [gateway-ip] When this CLI is configured for a BGP vrf under L2VPN EVPN address family, EVPN type-5 routes are generated for BGP prefixes in the vrf. Nexthop of the BGP @@ -2762,7 +2762,7 @@ routes are generated without overlay index. 2. Add gateway IP to EVPN type-5 route using a route-map: -.. clicmd:: [no] set evpn gateway-ip +.. clicmd:: set evpn gateway-ip When route-map with above set clause is applied as outbound policy in BGP, it will set the gateway-ip in EVPN type-5 NLRI. @@ -2786,7 +2786,7 @@ A PE that receives a type-5 route with gateway IP overlay index should have "enable-resolve-overlay-index" configuration enabled to recursively resolve the overlay index nexthop and install the prefix into zebra. -.. clicmd:: [no] enable-resolve-overlay-index +.. clicmd:: enable-resolve-overlay-index Example configuration: diff --git a/doc/user/ospf6d.rst b/doc/user/ospf6d.rst index af838cfd60..e99c46f5d4 100644 --- a/doc/user/ospf6d.rst +++ b/doc/user/ospf6d.rst @@ -83,7 +83,7 @@ OSPF6 router OSPF6 area ========== -.. clicmd:: [no] area A.B.C.D nssa +.. clicmd:: area A.B.C.D nssa NSSA Support in OSPFv3 ======================= -- 2.39.5