> 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?
For us, yes. Fully support the idea of requiring an "all" argument. Steinar Haug, AS 2116 _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp