[j-nsp] proposed changes to "clear bgp neighbor"

[Jonas Frey (Probe Networks)]

+1 for the "all" requirement

Am Mittwoch, den 26.02.2014, 10:36 -0500 schrieb Phil Shafer:
> Juniper users,
> 
> We've been asked to make a change the "clear bgp neighbor" command
> to make the neighbor or "all" argument mandatory.  The root cause
> is the severe impact of "clear bgp neighbor" and the increasing
> accidental use of this command without a specific neighbor.
> 
> In general, we avoid changing commands to add mandatory arguments,
> but my feeling is that the impact and severity of this specific
> command makes this an acceptable occasion for such a change.
> 
> I'm looking for feedback about this change.  My working assumption
> is that "clear bgp neighbor" is a sufficiently rare command and
> would not be used in automation/scripts, so the impact of making
> the neighbor/all argument mandatory would be minimal.  Is this
> assumption accurate?
> 
> Thanks,
>  Phil
> 
> [I've set reply-to to myself to avoid impacting the list]
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <https://puck.nether.net/pipermail/juniper-nsp/attachments/20140226/ad7a1719/attachment.sig>