proxmox-mirrors/mirror_frr
1
0
Fork 0
mirror of https://git.proxmox.com/git/mirror_frr synced 2025-07-27 11:44:16 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge pull request #4115 from Wojtek242/wojtek242/doc-overview-fix

Browse Source 
doc: replace old text with info about integrated configuration mode
This commit is contained in:
Donald Sharp 2019-04-09 22:29:06 -04:00 committed by GitHub
commit 6dc8dbf9bc
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
doc/user/overview.rst
View File

@ -107,14 +107,13 @@ An illustration of the large scale architecture is given below.
The multi-process architecture brings extensibility, modularity and The multi-process architecture brings extensibility, modularity and
maintainability. At the same time it also brings many configuration files and maintainability. All of the FRR daemons can be managed through a single
terminal interfaces. Each daemon has its own configuration file and terminal integrated user interface shell called *vtysh*. *vtysh* connects to each
interface. When you configure a static route, it must be done in the *Zebra* daemon through a UNIX domain socket and then works as a proxy for user input.
configuration file. When you configure BGP network it must be done in the In addition to a unified frontend, *vtysh* also provides the ability to
*bgpd* configuration file. This can become difficult to manage. To resolve the configure all the daemons using a single configuration file through the
problem, FRR provides integrated user interface shell called *vtysh*. *vtysh* integrated configuration mode avoiding the problem of having to maintain a
connects to each daemon with UNIX domain socket and then works as a proxy for separate configuration file for each daemon.
user input.
Supported Platforms Supported Platforms
=================== ===================