diff options
| author | Don Slice <dslice@cumulusnetworks.com> | 2017-12-06 09:00:48 -0800 |
|---|---|---|
| committer | Don Slice <dslice@cumulusnetworks.com> | 2017-12-06 09:00:48 -0800 |
| commit | 3ea48364e15638686467defc34896fac6638627f (patch) | |
| tree | 2f79d481fe3164ee8d37d46b18a768f3f7c2bc2b /lib/ringbuf.c | |
| parent | 17473b9a4589054ce2b3c81e4f2f32e7573d75c3 (diff) | |
zebra: do not display ipv6 ra commands created by bgpd
If the frr.conf file contains bgp unnumbered peering but the associated
interfaces do not have the commands "no ipv6 nd suppress-ra" and
"ipv6 nd ra-interval 10" configured, when frr-reload.py is issued the
interface commands are removed from the running config, causing peers to
got down and stay down after a link flap. This situation can occur if
the frr.conf file is created manually or via automation (like ansible)
but a subsequent "wr mem" has not been performed.
This fix changes the behavior so that the interface ipv6 nd ra commands
created by bgp are not displayed. Therefore, when the above condition
occurs, there is no difference between the running and stored configs
and peers work fine.
Ticket: CM-18702
Signed-off-by: Don Slice <dslice@cumulusnetworks.com>
Reviewed-by: CCR-7004
Testing-done: Manual testing successful. L3-smoke has no new failures
Diffstat (limited to 'lib/ringbuf.c')
0 files changed, 0 insertions, 0 deletions
