* Phil Shafer p...@juniper.net [2014-02-26 16:42]:
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
+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
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. listensamm...@gmx.de wrote:
+1
I fully support this change.
Regards,
Alex
Am 26.02.2014 16:36, schrieb Phil Shafer:
Juniper
Another vote for the 'all' function for all 'clear' commands. BGP, IS-IS etc
On 27 February 2014 04:36, Phil Shafer p...@juniper.net wrote:
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
Le 26/02/2014 22:10, sth...@nethelp.no a écrit :
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
+1 on the change
Tammy
AS36811
Sent from my iPhone
On Feb 27, 2014, at 1:23, Michael Hallgren m.hallg...@free.fr wrote:
Le 26/02/2014 22:10, sth...@nethelp.no a écrit :
We've been asked to make a change the clear bgp neighbor command
to make the neighbor or all argument mandatory. The
+1, fully support to hv this feature in JunOS. It is not a matter of rookie
or non rookie problem, but is to keep the network stable n running well.
On 26 Feb 2014 23:41, Phil Shafer p...@juniper.net wrote:
Juniper users,
We've been asked to make a change the clear bgp neighbor command
to
Saku Ytti writes:
But I'm generally against downward-compatibility, it hurts innovation and
creates codebase complexity creep (i.e. bugs). I'm all for regularly exploding
everything.
In JunOS case, between major version, you could state that all bets are off
with backward compatibility and fix
On 28/02/14 00:48, Phil Shafer wrote:
Sorry if I'm venturing toward shameless self promotion here, but
this really is an area we try to work at. That's part of the
movation for asking if this one specific case is sufficiently
irritating to break our own rules.
But it's not one specific case
On Fri, Feb 28, 2014 at 01:17:38AM +1100, Julien Goodwin wrote:
On 28/02/14 00:48, Phil Shafer wrote:
Sorry if I'm venturing toward shameless self promotion here, but
this really is an area we try to work at. That's part of the
movation for asking if this one specific case is sufficiently
On Wed, Feb 26, 2014 at 11:29 AM, Jerry Dent effinjd...@gmail.com wrote:
Just add a line Reset all bgp sessions? [Y/N] for confirmation.
*THWACK* THIS IS NOT WINDOWS.
--
Genius might be described as a supreme capacity for getting its possessors
into trouble of all kinds.
-- Samuel Butler
On Wed, Feb 26, 2014 at 10:36:39AM -0500, Phil Shafer wrote:
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
On Thu, Feb 27, 2014 at 8:39 AM, Michael Loftis mlof...@wgops.com wrote:
On Wed, Feb 26, 2014 at 11:29 AM, Jerry Dent effinjd...@gmail.com wrote:
Just add a line Reset all bgp sessions? [Y/N] for confirmation.
*THWACK* THIS IS NOT WINDOWS.
Maybe that was a bit harsh, but still, there's very
ast.
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
You'd only get the confirmation if you didn't type the word 'all'. I don't
get this superiority complex. Most gear has a message like this when you
reboot it. Haven't seen anyone complain about that.
On Thu, Feb 27, 2014 at 11:58 AM, Eric Van Tol e...@atlantech.net wrote:
*THWACK* THIS IS
Le 27/02/2014 18:58, Eric Van Tol a écrit :
ast.
:-)
mh
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
___
juniper-nsp mailing list
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
Hi,
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.
1. Would it be possible to
Jerzy Pawlus writes:
1. Would it be possible to clear bgp neighbor command do nothing?
after applying above change.
We could have it say something like Oh no you didn't!, but
I'd rather use the CLI completion to get users to see that
something more is needed.
2. You can add an option
it's a nice-to-have, maybe? but this sounds more like an opportunity for
you to sell some JNCIA courses. i mean, how long has junos been around now?
On Wed, Feb 26, 2014 at 10:36 AM, Phil Shafer p...@juniper.net wrote:
Juniper users,
We've been asked to make a change the clear bgp neighbor
ryanL writes:
it's a nice-to-have, maybe? but this sounds more like an opportunity for
you to sell some JNCIA courses. i mean, how long has junos been around now?
Not selling anything; just trying to solve a problem multiple
customers have reported and escalated. I'm a software developer,
Just add a line Reset all bgp sessions? [Y/N] for confirmation.
On Wed, Feb 26, 2014 at 1:24 PM, Eric Van Tol e...@atlantech.net wrote:
it's a nice-to-have, maybe? but this sounds more like an opportunity for
you to sell some JNCIA courses. i mean, how long has junos been around
now?
it's a nice-to-have, maybe? but this sounds more like an opportunity for
you to sell some JNCIA courses. i mean, how long has junos been around
now?
Confusing comment, since this enhancement isn't about CLI inexperience. It
doesn't matter how long Junos has been around or how experienced
+1 to include the “all” option.
In fact, coming from the IOS world, it amused me when I discovered that there
was no “*” or “all” option to clear all neighbors.
El 26/02/2014, a las 20:24, Eric Van Tol e...@atlantech.net escribió:
it's a nice-to-have, maybe? but this sounds more like an
yeah, i'm not slagging. just seems like poor training for newbie noc
engineers or something. this is a pretty rookie error, in my view, but i've
been around almost as long as you have ;-)
On Wed, Feb 26, 2014 at 1:44 PM, Phil Shafer p...@juniper.net wrote:
ryanL writes:
it's a nice-to-have,
+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
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
On Wed, 26 Feb 2014, ryanL wrote:
yeah, i'm not slagging. just seems like poor training for newbie noc
engineers or something. this is a pretty rookie error, in my view, but i've
been around almost as long as you have ;-)
I've been doing BGP work for nearly 20 years, and Juniper for more than
that sounds exactly like CLI inexperience to me. in any case, i did state
that it would be a nice to have.
On Wed, Feb 26, 2014 at 2:24 PM, Eric Van Tol e...@atlantech.net wrote:
it's a nice-to-have, maybe? but this sounds more like an opportunity for
you to sell some JNCIA courses. i mean,
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
I don't chime in much on the threads but in this case I'm with you, fat fingers
can kill and the idiot do u really want to do this Y/N isn't a bad idea either.
You do this long enough you guys that haven't had an oops moment eventually
will.
Sent from my iPhone
On Feb 26, 2014, at 4:29 PM,
+1 to the 'all' requirement -- and then further include another question
as suggested like 'Reset all BGP sessions? [Y/N]'
That, in my opinion, is the most sane way to go about it.
On 2/27/2014 ?? 05:37, Jonas Frey (Probe Networks) wrote:
+1 for the all requirement
Am Mittwoch, den
Thu, Feb 27, 2014 at 10:30:29AM +0900, Paul S.:
+1 to the 'all' requirement -- and then further include another question
as suggested like 'Reset all BGP sessions? [Y/N]'
Please - if you're dumb enough to enter a command that you do not understand
on a production device, you deserve what you
On 2/27/2014 午前 10:38, heasley wrote:
Thu, Feb 27, 2014 at 10:30:29AM +0900, Paul S.:
+1 to the 'all' requirement -- and then further include another question
as suggested like 'Reset all BGP sessions? [Y/N]'
Please - if you're dumb enough to enter a command that you do not understand
on a
On Thu, 27 Feb 2014, heasley wrote:
Thu, Feb 27, 2014 at 10:30:29AM +0900, Paul S.:
+1 to the 'all' requirement -- and then further include another question
as suggested like 'Reset all BGP sessions? [Y/N]'
Please - if you're dumb enough to enter a command that you do not understand
on a
On Wednesday, February 26, 2014 09:24:21 PM Eric Van Tol
wrote:
I don't see a problem with adding the requirement 'all'.
I support this as well.
Mark.
signature.asc
Description: This is a digitally signed message part.
___
juniper-nsp mailing list
On Wednesday, February 26, 2014 09:25:00 PM ryanL wrote:
yeah, i'm not slagging. just seems like poor training for
newbie noc engineers or something. this is a pretty
rookie error, in my view, but i've been around almost as
long as you have ;-)
I suppose the idea is to keep the network
For me is ok too.
Massimo
2014-02-27 8:07 GMT+01:00 Mark Tinka mark.ti...@seacom.mu:
On Wednesday, February 26, 2014 09:24:21 PM Eric Van Tol
wrote:
I don't see a problem with adding the requirement 'all'.
I support this as well.
Mark.
___
On (2014-02-26 10:36 -0500), Phil Shafer wrote:
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
39 matches
Mail list logo
