mirror of
https://git.proxmox.com/git/mirror_frr
synced 2025-10-31 09:04:27 +00:00
1c84efe4fa
Features added in this commit: 1. Bringup/shutdown new management daemon 'mgmtd' along with FRR. 2. Support for Startup, Candidate and Running DBs. 3. Lock/Unlock DS feature using pthread lock. 4. Load config from a JSON file onto candidate DS. 5. Save config to a JSON file from running/candidate DS. 6. Dump candidate or running DS contents on the terminal or a file in JSON/XML format. 7. Maintaining commit history (Full rollback support to be added in future commits). 8. Addition of debug commands. Co-authored-by: Yash Ranjan <ranjany@vmware.com> Co-authored-by: Abhinay Ramesh <rabhinay@vmware.com> Co-authored-by: Ujwal P <ujwalp@vmware.com> Signed-off-by: Pushpasis Sarkar <pushpasis@gmail.com>
127 lines
4.0 KiB
Plaintext
127 lines
4.0 KiB
Plaintext
# This file tells the frr package which daemons to start.
|
|
#
|
|
# Sample configurations for these daemons can be found in
|
|
# /usr/share/doc/frr/examples/.
|
|
#
|
|
# ATTENTION:
|
|
#
|
|
# When activating a daemon for the first time, a config file, even if it is
|
|
# empty, has to be present *and* be owned by the user and group "frr", else
|
|
# the daemon will not be started by /etc/init.d/frr. The permissions should
|
|
# be u=rw,g=r,o=.
|
|
# When using "vtysh" such a config file is also needed. It should be owned by
|
|
# group "frrvty" and set to ug=rw,o= though. Check /etc/pam.d/frr, too.
|
|
#
|
|
# The watchfrr, zebra and staticd daemons are always started.
|
|
#
|
|
bgpd=no
|
|
ospfd=no
|
|
ospf6d=no
|
|
ripd=no
|
|
ripngd=no
|
|
isisd=no
|
|
pimd=no
|
|
pim6d=no
|
|
ldpd=no
|
|
nhrpd=no
|
|
eigrpd=no
|
|
babeld=no
|
|
sharpd=no
|
|
pbrd=no
|
|
bfdd=no
|
|
fabricd=no
|
|
vrrpd=no
|
|
pathd=no
|
|
|
|
#
|
|
# If this option is set the /etc/init.d/frr script automatically loads
|
|
# the config via "vtysh -b" when the servers are started.
|
|
# Check /etc/pam.d/frr if you intend to use "vtysh"!
|
|
#
|
|
vtysh_enable=yes
|
|
zebra_options=" -A 127.0.0.1 -s 90000000"
|
|
mgmtd_options=" -A 127.0.0.1"
|
|
bgpd_options=" -A 127.0.0.1"
|
|
ospfd_options=" -A 127.0.0.1"
|
|
ospf6d_options=" -A ::1"
|
|
ripd_options=" -A 127.0.0.1"
|
|
ripngd_options=" -A ::1"
|
|
isisd_options=" -A 127.0.0.1"
|
|
pimd_options=" -A 127.0.0.1"
|
|
pim6d_options=" -A ::1"
|
|
ldpd_options=" -A 127.0.0.1"
|
|
nhrpd_options=" -A 127.0.0.1"
|
|
eigrpd_options=" -A 127.0.0.1"
|
|
babeld_options=" -A 127.0.0.1"
|
|
sharpd_options=" -A 127.0.0.1"
|
|
pbrd_options=" -A 127.0.0.1"
|
|
staticd_options="-A 127.0.0.1"
|
|
bfdd_options=" -A 127.0.0.1"
|
|
fabricd_options="-A 127.0.0.1"
|
|
vrrpd_options=" -A 127.0.0.1"
|
|
pathd_options=" -A 127.0.0.1"
|
|
|
|
|
|
# If you want to pass a common option to all daemons, you can use the
|
|
# "frr_global_options" variable.
|
|
#
|
|
#frr_global_options=""
|
|
|
|
|
|
# The list of daemons to watch is automatically generated by the init script.
|
|
# This variable can be used to pass options to watchfrr that will be passed
|
|
# prior to the daemon list.
|
|
#
|
|
# To make watchfrr create/join the specified netns, add the the "--netns"
|
|
# option here. It will only have an effect in /etc/frr/<somename>/daemons, and
|
|
# you need to start FRR with "/usr/lib/frr/frrinit.sh start <somename>".
|
|
#
|
|
#watchfrr_options=""
|
|
|
|
|
|
# configuration profile
|
|
#
|
|
#frr_profile="traditional"
|
|
#frr_profile="datacenter"
|
|
|
|
|
|
# This is the maximum number of FD's that will be available. Upon startup this
|
|
# is read by the control files and ulimit is called. Uncomment and use a
|
|
# reasonable value for your setup if you are expecting a large number of peers
|
|
# in say BGP.
|
|
#
|
|
#MAX_FDS=1024
|
|
|
|
# Uncomment this option if you want to run FRR as a non-root user. Note that
|
|
# you should know what you are doing since most of the daemons need root
|
|
# to work. This could be useful if you want to run FRR in a container
|
|
# for instance.
|
|
# FRR_NO_ROOT="yes"
|
|
|
|
# For any daemon, you can specify a "wrap" command to start instead of starting
|
|
# the daemon directly. This will simply be prepended to the daemon invocation.
|
|
# These variables have the form daemon_wrap, where 'daemon' is the name of the
|
|
# daemon (the same pattern as the daemon_options variables).
|
|
#
|
|
# Note that when daemons are started, they are told to daemonize with the `-d`
|
|
# option. This has several implications. For one, the init script expects that
|
|
# when it invokes a daemon, the invocation returns immediately. If you add a
|
|
# wrap command here, it must comply with this expectation and daemonize as
|
|
# well, or the init script will never return. Furthermore, because daemons are
|
|
# themselves daemonized with -d, you must ensure that your wrapper command is
|
|
# capable of following child processes after a fork() if you need it to do so.
|
|
#
|
|
# If your desired wrapper does not support daemonization, you can wrap it with
|
|
# a utility program that daemonizes programs, such as 'daemonize'. An example
|
|
# of this might look like:
|
|
#
|
|
# bgpd_wrap="/usr/bin/daemonize /usr/bin/mywrapper"
|
|
#
|
|
# This is particularly useful for programs which record processes but lack
|
|
# daemonization options, such as perf and rr.
|
|
#
|
|
# If you wish to wrap all daemons in the same way, you may set the "all_wrap"
|
|
# variable.
|
|
#
|
|
#all_wrap=""
|