Re: [j-nsp] proposed changes to "clear bgp neighbor"
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 wrote: > > > *THWACK* THIS IS NOT WINDOWS. > > > > Maybe that was a bit harsh, but still, there's very few things more > > annoying than a CLI (well, any UI) that groans and moans and nannys > > when you're trying to get work done, stealing your context or focus to > > "warn" you about something "dangerous." Adding "all" as a requirement > > is so much more elegant, easier on the CLI developer too, keeps an > > accidental/bumped enter from bombing all BGP sessions just as clearly > > as a prompt that is almost certainly going to not be fully read anyway > > by a lot of admins. > > > > > > I'd also add support that there are many other commands in clear that > > might like this treatment (as mentioned by some others in the thread) > > Pffft...CLEARLY, you are all n00bs who deserve what you get for making > mistakes and typing too fast. I've never once accidentally typo'd > something, and say, sent an email too f > > ___ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] proposed changes to "clear bgp neighbor"
Just add a line "Reset all bgp sessions? [Y/N]" for confirmation. On Wed, Feb 26, 2014 at 1:24 PM, Eric Van Tol 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? > > Confusing comment, since this enhancement isn't about CLI inexperience. > It doesn't matter how long Junos has been around or how experienced > someone is, it's still too incredibly easy to hit 'Enter' too soon and > clear all your BGP neighbors by accident. > > I don't see a problem with adding the requirement 'all'. > > -evt > > ___ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] next-hop driving me crazy
Also, you can do "then next-hop discard" in your policy and you won't need the static route. On Fri, Apr 26, 2013 at 2:04 PM, Richard A Steenbergen wrote: > On Fri, Apr 26, 2013 at 11:14:39AM -0500, Eric Krichbaum wrote: > > Thanks everyone. The policy straight to discard works for me, just > annoyed > > me. I really didn't want to apply a knob (similar to the disable > connected > > check on cisco) to do it. Trying to make these policies the same has > proven > > an interesting exercise and at least now I am aware of the knobs to make > it > > do the other. > > It's technically a violation of the BGP spec to let the user arbitrarily > rewrite the next-hop of a eBGP non-multihop route to something other > than the directly connected interface, and the "correct" action when you > do it is to reject the route for having an invalid next-hop. > > Of course, over here in reality land that's complete nonsense. There are > perfectly legitimate reasons to do so, like the example you cited, but > it took a LONG time to get this past the guys who defend the theory > without regard to practice. You used to have to configure ebgp multihop > everywhere to get it to relax those rules, which carries its own > downsides like lack of "fast external failover" behavior. The commands > like "disable-connected-check" and "accept-remote-nexthop" were the > compromises between following the spec and satisfying the customer. ;) > > -- > Richard A Steenbergenhttp://www.e-gerbil.net/ras > GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC) > ___ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
