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

[Joerg Staedele]

Hi there,

yes, please make "all" mandatory. We had copy/paste in the past where there was a CRLF before the IP of a neighbor and that killed all neighbors.

Regards,
 Joerg

-----Ursprüngliche Nachricht-----
Von: juniper-nsp [mailto:juniper-nsp-bounces at puck.nether.net] Im Auftrag von Phil Shafer
Gesendet: Mittwoch, 26. Februar 2014 16:37
An: Juniper for Network Service Providers
Betreff: [j-nsp] proposed changes to "clear bgp neighbor"

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