diff options
| author | Acee <aceelindem@gmail.com> | 2023-06-08 22:49:34 +0200 |
|---|---|---|
| committer | Acee <aceelindem@gmail.com> | 2023-06-28 19:03:48 +0200 |
| commit | e72549c8f6f7b25738f8d4c913db025a7906558e (patch) | |
| tree | 4bccfc18bd16b621f4c862255ad63f73161e0d7c /doc/user/ospfd.rst | |
| parent | Merge pull request #13596 from Pdoijode/pdoijode/ospf-intf-json-changes (diff) | |
| download | frr-e72549c8f6f7b25738f8d4c913db025a7906558e.tar.xz frr-e72549c8f6f7b25738f8d4c913db025a7906558e.zip | |
ospfd: Configurable interface-level 'capability opaque' support
Add support for "[no] ip ospf capbility opaque" at the interface
level with the default being capability opaque enabled. The command
"no ip ospf capability opaque" will disable opaque LSA database
exchange and flooding on the interface. A change in configuration
will result in the interface being flapped to update our options
for neighbors but no attempt will be made to purge existing LSAs
as in dense topologies, these may received by neighbors through
different interfaces.
Topotests are added to test both the configuration and the LSA
opaque flooding suppression.
Signed-off-by: Acee <aceelindem@gmail.com>
Diffstat (limited to 'doc/user/ospfd.rst')
| -rw-r--r-- | doc/user/ospfd.rst | 14 |
1 files changed, 13 insertions, 1 deletions
diff --git a/doc/user/ospfd.rst b/doc/user/ospfd.rst index 3430d8a28..232b1c393 100644 --- a/doc/user/ospfd.rst +++ b/doc/user/ospfd.rst @@ -912,7 +912,7 @@ Opaque LSA - *ospfd* supports Opaque LSA (:rfc:`2370`) as partial support for + *ospfd* supports Opaque LSA (:rfc:`5250`) as partial support for MPLS Traffic Engineering LSAs. The opaque-lsa capability must be enabled in the configuration. An alternate command could be "mpls-te on" (:ref:`ospf-traffic-engineering`). Note that FRR @@ -920,6 +920,18 @@ Opaque LSA extensions that are used with MPLS-TE; it does not support a complete RSVP-TE solution. +.. clicmd:: ip ospf capability opaque [A.B.C.D] + + Enable or disable OSPF LSA database exchange and flooding on an interface. + The default is that opaque capability is enabled as long as the opaque + capability is enabled with the :clicmd:`capability opaque` command at the + OSPF instance level (using the command above). Note that disabling opaque + LSA support on an interface will impact the applications using opaque LSAs + if the opaque LSAs are not received on other flooding paths by all the + OSPF routers using those applications. For example, OSPF Graceful Restart + uses opaque-link LSAs and disabling support on an interface will disable + graceful restart signaling on that interface. + .. clicmd:: show ip ospf [vrf <NAME|all>] database (opaque-link|opaque-area|opaque-external) .. clicmd:: show ip ospf [vrf <NAME|all>] database (opaque-link|opaque-area|opaque-external) LINK-STATE-ID |