Sorry I miss typed in my original message On 9/11/2015 4:10 PM, Alexis Rosen wrote: > On Sep 11, 2015, at 3:37 PM, Lou Berger <[email protected]> wrote: >> On 09/11/2015 02:35 PM, Alexis Rosen wrote: >>> On Sep 11, 2015, at 8:25 AM, Michael H Lambert <[email protected]> wrote: >>>> 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. >> 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 I meant to say:
address-family <safi><afi> no neighbor 127.0.0.116 activate #for deactivate no neighbor 127.0.0.116 #for remove neighbor <safi><afi> exit-address-family > Hm. That's somewhat counterintuitive. The obvious option, if somewhat > inconsistent with standard usage, would be: > > address-family <safi><afi> > no neighbor 127.0.0.116 activate #for deactivate > delete neighbor 127.0.0.116 #for remove neighbor <safi><afi> > exit-address-family > > Alternatively, "no neighbor XXXX" could mean to delete either the afi/safi > config or the entire config, depending on current scope. Assuming quagga can > handle that, I think I'd favor it. The 'no neighbor 127.0.0.116' syntax is currently used to remove base (a non-safi) peer. Lou > /a _______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
