FRR configuration and persistence

[Keith Willowhawk]

As my team is exploring evpn on SONiC, we're running into some issues with configuring BGP through FRR.

(if this isn't the right sub-group, please gently point me in the right direction)

Problem 1:

Configure FRR through something other than vtysh.  In order to automate switch deployments, and be able to uniformly and consistently configure FRR, it would be nice if we could inject things into the Redis dB, or at worst, add things to the config_db.json and reload it, that'd be great.  Is there any current method to configure frr/bgp better than vtysh?

Problem 2:

Get the config to persist into the confib_db.json (or somewhere else).  Right now, not all BGP configuration items (like "advertise-vni-all" for example) seem to make it into the config_db.json (I can only see BGP _NEIGHBOR, and are instead written to the bgpd.conf file, but that file doesn't seem to be ingested if the FRR docker container is restarted...

Any guidance is appreciated, thank you!

--Keith

[Ben Gale]

Keith,

The below (code) was just merged - does this help?

- HLD: https://github.com/Azure/SONiC/pull/544

- Code: https://github.com/Azure/sonic-buildimage/pull/5142

Thanks,

Ben

--
You received this message because you are subscribed to the Google Groups "sonic-evpn-workgroup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonic-evpn-workg...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonic-evpn-workgroup/c90811f4-2a1e-47cc-9e75-ff49fcfed9c7n%40googlegroups.com.

This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it.