On 09/11/2015 02:35 PM, Alexis Rosen wrote: > On Sep 11, 2015, at 8:25 AM, Michael H Lambert <[email protected]> wrote: >>> On 11 Sep 2015, at 06:34, Paul Jakma <[email protected]> wrote: >>> >>> Yeah, be nice to have 1 way to delete the per-AFI/SAFI config, and another >>> to disable the neighbour in that AFI/SAFI, but keep config. >>> >>> What would be the sanest way to add such commands, or options to existing >>> commands? >> >> For deleting the per-AFI/SAFI config, how about just >> >> no neighbor <addr> address-family <afi> <safi> >> >> (eg, "no neighbor 1::1 address-family ipv6 multicast"). > > +1 > > That's exactly what I was thinking. > > /a > _______________________________________________ > Quagga-dev mailing list > [email protected] > https://lists.quagga.net/mailman/listinfo/quagga-dev >
This is inconsistent with the current afi/safi config: address-family vpnv4 neighbor 127.0.0.115 activate neighbor 127.0.0.115 route-reflector-client neighbor 127.0.0.116 activate neighbor 127.0.0.116 route-reflector-client exit-address-family ! of course right now a 'no neighbor 127.0.0.116 activate' will delete all neighbor information. This too is inconsistent with the base neighbor config. So for consistency I propose: address-family <safi><afi> no neighbor 127.0.0.116 activate #for deactivate no neighbor 127.0.0.116 delete #for remove neighbor <safi><afi> exit-address-family Lou _______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
