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

Morgan McLean wrx230 at gmail.com
Fri Feb 28 19:24:06 EST 2014


Anybody chalking this up to cli inexperience, is inexperienced lol.
Everybody makes mistakes.

Supported by me.

Morgan


On Fri, Feb 28, 2014 at 1:20 PM, Alex D. <listensammler at gmx.de> wrote:

> +1
>
> I fully support this change.
>
> Regards,
> Alex
>
> Am 26.02.2014 16:36, 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
>>
>>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>



-- 
Thanks,
Morgan


More information about the juniper-nsp mailing list