proxmox-mirrors/mirror_frr
1
0
Fork 0
mirror of https://git.proxmox.com/git/mirror_frr synced 2025-08-14 23:53:28 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

doc: sync ospf-sr docs from master

Browse Source 
7666589034

Signed-off-by: Quentin Young <qlyoung@cumulusnetworks.com>
This commit is contained in:
Quentin Young 2018-03-06 10:50:30 -05:00
parent e207a4b589
commit e3e3afffc9
No known key found for this signature in database
GPG Key ID: DAF48E0F57E0834F
2 changed files with 44 additions and 27 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
doc/developer/ospf-sr.rst
View File

@ -5,6 +5,26 @@ This is an EXPERIMENTAL support of draft
`draft-ietf-ospf-segment-routing-extensions-24`. `draft-ietf-ospf-segment-routing-extensions-24`.
DON'T use it for production network. DON'T use it for production network.
Supported Features
------------------
* Automatic computation of Primary and Backup Adjacency SID with
Cisco experimental remote IP address
* SRGB configuration
* Prefix configuration for Node SID with optional NO-PHP flag (Linux
kernel support both mode)
* Node MSD configuration (with Linux Kernel >= 4.10 a maximum of 32 labels
could be stack)
* Automatic provisioning of MPLS table
* Static route configuration with label stack up to 32 labels
Interoperability
----------------
* Tested on various topology including point-to-point and LAN interfaces
in a mix of Free Range Routing instance and Cisco IOS-XR 6.0.x
* Check OSPF LSA conformity with latest wireshark release 2.5.0-rc
Implementation details Implementation details
---------------------- ----------------------
@ -248,9 +268,6 @@ Known limitations
* MPLS table are not flush at startup. Thus, restarting zebra process is * MPLS table are not flush at startup. Thus, restarting zebra process is
mandatory to remove old MPLS entries in the data plane after a crash of mandatory to remove old MPLS entries in the data plane after a crash of
ospfd daemon ospfd daemon
* Due to a bug in OSPF Opaque, LSA are not flood when enable Segment Routing
through CLI once OSPFd started. You must configure Segment Routing within
configuration file before launching OSPFd
* With NO Penultimate Hop Popping, it is not possible to express a Segment * With NO Penultimate Hop Popping, it is not possible to express a Segment
Path with an Adjacency SID due to the impossibility for the Linux Kernel to Path with an Adjacency SID due to the impossibility for the Linux Kernel to
perform double POP instruction. perform double POP instruction.
@ -266,4 +283,3 @@ This work has been performed in the framework of the H2020-ICT-2014
project 5GEx (Grant Agreement no. 671636), which is partially funded project 5GEx (Grant Agreement no. 671636), which is partially funded
by the European Commission. by the European Commission.

7
doc/user/ospfd.rst
View File

@ -1033,11 +1033,12 @@ This is an EXPERIMENTAL support of Segment Routing as per draft
currently supported. The 'no-php-flag' means NO Penultimate Hop Popping that currently supported. The 'no-php-flag' means NO Penultimate Hop Popping that
allows SR node to request to its neighbor to not pop the label. allows SR node to request to its neighbor to not pop the label.
.. index:: show ip ospf database segment-routing <adv-router ADVROUTER|self-originate> .. index:: show ip ospf database segment-routing <adv-router ADVROUTER|self-originate> [json]
.. clicmd:: show ip ospf database segment-routing <adv-router ADVROUTER|self-originate> .. clicmd:: show ip ospf database segment-routing <adv-router ADVROUTER|self-originate> [json]
Show Segment Routing Data Base, all SR nodes, specific advertized router or Show Segment Routing Data Base, all SR nodes, specific advertized router or
self router. self router. Optional JSON output can be obtained by appending 'json' to the
end of the command.
Debugging OSPF Debugging OSPF
============== ==============