Re: [j-nsp] Juniper vs Arista

2018-08-15 Thread Mark Tinka
Let me make some noise about this in my region... Mark. On 16/Aug/18 07:29, Mark Tinka wrote: > Good man :-)! > > Mark. > > On 15/Aug/18 20:09, Jared Mauch wrote: >> Fixed. >> >> https://puck.nether.net/mailman/listinfo/arista-nsp >> >> >>> On Aug 14, 2018, at 2:34 AM, Mark Tinka wrote: >>> >>>

Re: [j-nsp] Juniper vs Arista

2018-08-15 Thread Mark Tinka
On 15/Aug/18 21:09, Pavel Lunin wrote: > I am not saying that JunosE to JUNOS BNG transition was a fail but I > honestly doubt that they reached the initial goals. It's the same hardware > now, however the BNG feature set is in fact a standalone subsystem in > Junos. I would only say thank you

Re: [j-nsp] Juniper vs Arista

2018-08-15 Thread Mark Tinka
Good man :-)! Mark. On 15/Aug/18 20:09, Jared Mauch wrote: > Fixed. > > https://puck.nether.net/mailman/listinfo/arista-nsp > > >> On Aug 14, 2018, at 2:34 AM, Mark Tinka wrote: >> >> On 14/Aug/18 08:26, Gert Doering wrote: >> >>> Mailman claims "there isn't yet", but if Jared would add one, I'd

Re: [j-nsp] Juniper vs Arista

2018-08-15 Thread Pavel Lunin
> > > > > Not sure, but from the first glance it doesn't look like they've > > gained > > more than they've lost with the JunosE to JUNOS BNG migration. > > I didn't miss JunosE any single day after we finished migration to MX. > MX platform is not ideal and has it's own quirks but I doubt that ide

Re: [j-nsp] Juniper vs Arista

2018-08-15 Thread Jared Mauch
Fixed. https://puck.nether.net/mailman/listinfo/arista-nsp > On Aug 14, 2018, at 2:34 AM, Mark Tinka wrote: > > On 14/Aug/18 08:26, Gert Doering wrote: > >> Mailman claims "there isn't yet", but if Jared would add one, I'd >> subscribe :-) >> >> >> https://puck.nether.net/mailman/listinfo/

Re: [j-nsp] Juniper vs Arista

2018-08-15 Thread Saku Ytti
On Wed, 15 Aug 2018 at 20:34, Andrey Kostin wrote: > Pavel Lunin писал 14.08.2018 05:06: > >> > > > Not sure, but from the first glance it doesn't look like they've > > gained > > more than they've lost with the JunosE to JUNOS BNG migration. > > I didn't miss JunosE any single day after we finis

Re: [j-nsp] Juniper vs Arista

2018-08-15 Thread Andrey Kostin
Pavel Lunin писал 14.08.2018 05:06: Not sure, but from the first glance it doesn't look like they've gained more than they've lost with the JunosE to JUNOS BNG migration. I didn't miss JunosE any single day after we finished migration to MX. MX platform is not ideal and has it's own quirks

Re: [j-nsp] Juniper vs Arista

2018-08-14 Thread Mark Tinka
On 14/Aug/18 12:22, Gert Doering wrote: > Which is sort of what stuck after our Arista POC: it's like IOS with > lots of useful enhancements, and without the annoying "I refuse to > do things, because I am right and you are wrong" attitude of JunOS. The t-shirt is going to print :-)... Mark.

Re: [j-nsp] Juniper vs Arista

2018-08-14 Thread Gert Doering
Hi, On Tue, Aug 14, 2018 at 10:37:31AM +0200, Sebastian Wiesinger wrote: > Do they have commit capability? Yes, optional. You either do "conf term" just like on IOS, or you do "conf session" which needs commit. Which is really really nice - if I do troubleshooting, I want a "interface foo / sh

Re: [j-nsp] Juniper vs Arista

2018-08-14 Thread adamv0025
> Of Saku Ytti > Sent: Tuesday, August 14, 2018 9:31 AM > > Perhaps in future it's all very small (<5 0M) net install image, then DEB/RPM > all packages via local proxy to have functioning install for specific target, with > specific forwarding engines. > Cisco is certainly on the right track wit

Re: [j-nsp] Juniper vs Arista

2018-08-14 Thread Pavel Lunin
> > > But if I'm honest, I don't put a lot of stock in this. If you remember, > this was Juniper's line back in the day, "One Junos to rule them all". > Well, things obviously took another turn when they introduced the MX and > EX platforms around 2007/2008. > Moreover, as we've discussed a few we

Re: [j-nsp] Juniper vs Arista

2018-08-14 Thread Tobias Heister
On 14.08.2018 08:34, Mark Tinka wrote: On 14/Aug/18 08:26, Gert Doering wrote: Mailman claims "there isn't yet", but if Jared would add one, I'd subscribe :-) https://puck.nether.net/mailman/listinfo/ As would I... +1 -- regards Tobias ___ juni

Re: [j-nsp] Juniper vs Arista

2018-08-14 Thread Saku Ytti
On Tue, 14 Aug 2018 at 11:38, Sebastian Wiesinger wrote: > Do they have commit capability? Yes, and it works. In IOS-XR commit doesn't inherently work, because of how it's designed. In JunOS commit inherently works. In IOS-XR BGP team owns commit for BGP config, tunnel team owns commit for GRE,

Re: [j-nsp] Juniper vs Arista

2018-08-14 Thread Mark Tinka
On 14/Aug/18 10:37, Sebastian Wiesinger wrote: > Do they have commit capability? https://eos.arista.com/config-sessions-tips/ Mark. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] Juniper vs Arista

2018-08-14 Thread Mark Tinka
On 14/Aug/18 10:30, Saku Ytti wrote: > I know what you mean, but 'code is Cisco-like' may not be read as > positive by every recipient. I think you more accurately mean 'CLI is > like classic IOS'. This... as in, "it's not much to learn". Very different under the hood, obviously, but on top, i

Re: [j-nsp] Juniper vs Arista

2018-08-14 Thread Sebastian Wiesinger
* Saku Ytti [2018-08-14 10:31]: > On Tue, 14 Aug 2018 at 09:35, Mark Tinka wrote: > > > The Arista code is so Cisco-like, and in our use-case, has done > > everything as advertised in the manuals and in the "Arista Warrior" > > O'Reilly publication. So we haven't had to struggle... but then agai

Re: [j-nsp] Juniper vs Arista

2018-08-14 Thread Saku Ytti
On Tue, 14 Aug 2018 at 09:35, Mark Tinka wrote: > The Arista code is so Cisco-like, and in our use-case, has done > everything as advertised in the manuals and in the "Arista Warrior" > O'Reilly publication. So we haven't had to struggle... but then again, > our deployment is very simple - Layer

Re: [j-nsp] Juniper vs Arista

2018-08-13 Thread Mark Tinka
On 14/Aug/18 08:26, Gert Doering wrote: > Mailman claims "there isn't yet", but if Jared would add one, I'd > subscribe :-) > > https://puck.nether.net/mailman/listinfo/ As would I... The Arista code is so Cisco-like, and in our use-case, has done everything as advertised in the manuals and in

Re: [j-nsp] Juniper vs Arista

2018-08-13 Thread Gert Doering
Hi, On Tue, Aug 14, 2018 at 08:20:59AM +0200, Mark Tinka wrote: > On 14/Aug/18 03:41, Jared Mauch wrote: > > > I believe there???s also arista-nsp on here.. > I checked last year and couldn't find anything. Do you have a link? Mailman claims "there isn't yet", but if Jared would add one, I'd sub

Re: [j-nsp] Juniper vs Arista

2018-08-13 Thread Mark Tinka
On 14/Aug/18 03:41, Jared Mauch wrote: > Personally I really like Arista but also like JunOS based on my use case. What we can be certain of is that the small companies become big successful ones, grow, and then have to sacrifice a bit of their earlier principles to maintain the new lifestyle.

Re: [j-nsp] Juniper vs Arista

2018-08-13 Thread Mark Tinka
On 14/Aug/18 03:08, Colton Conor wrote: > We have used Juniper for a long time across various lines. What I have > noticed is on the JTAC recommend version website piratically all of their > product lines are running on different code trains. They all run Junos yes, > but they all have differen

Re: [j-nsp] Juniper vs Arista

2018-08-13 Thread Gert Doering
Hi, On Mon, Aug 13, 2018 at 08:08:29PM -0500, Colton Conor wrote: > Arista's sales engineering are claiming that their entire product line runs > EOS, and there is a single firmware file for all products. Does anyone know > if that is true, and how that compares to the way Juniper does things? Th

Re: [j-nsp] Juniper vs Arista

2018-08-13 Thread Jared Mauch
> On Aug 13, 2018, at 9:08 PM, Colton Conor wrote: > > We have used Juniper for a long time across various lines. What I have > noticed is on the JTAC recommend version website piratically all of their > product lines are running on different code trains. They all run Junos yes, > but they all

[j-nsp] Juniper vs Arista

2018-08-13 Thread Colton Conor
We have used Juniper for a long time across various lines. What I have noticed is on the JTAC recommend version website piratically all of their product lines are running on different code trains. They all run Junos yes, but they all have different features. It seems like Juniper has a different so