diff options
| author | Dinesh G Dutt <ddutt@cumulusnetworks.com> | 2016-07-06 06:50:23 -0700 |
|---|---|---|
| committer | Dinesh G Dutt <ddutt@cumulusnetworks.com> | 2016-07-06 14:51:29 -0700 |
| commit | 655f79c9d2352c4c57b883aad0da6cd4528f4dde (patch) | |
| tree | a25d557b2a496b286c492d156e03955b02c0713f /lib/command.c | |
| parent | ab5f8310801f1870a7c5c22e1595e4452c558ddb (diff) | |
Don't print 'neighbor activate' if its default for IPv4 unicast AFI/SAFI
Ticket: CM-11460
Reviewed By: CCR-4927
Testing Done:
Quagga's default "show running" model is to only print the non-default config.
Historically, IPv4 unicast has always had a default 'activate' model unless
its been configured otherwise. In 3.0, we introduced a print of the 'activate'
statement for IPv4 unicast independent of whether it was the default or not.
This causes quagga reload to break as the user doesn't configure 'activate' for
IPv4 unicast, and so any config changes will also not have it. However 'show
running' will display it, causing quagga reload to think that the AFI/SAFI has
been deactivated and bounce the sessions incorrectly.
This patch reverts to the original quagga behavior/model of not printing the
'activate' line for IPv4 unicast if its the default.
Diffstat (limited to 'lib/command.c')
0 files changed, 0 insertions, 0 deletions