On 17/Jul/18 16:24, Richard McGovern wrote:
> Felt need to jump in here, and hopefully get some of the real facts straight.
> Prior to ELS CLI Juniper had basically 2 different CLI’s – one for EX
> Products and branch SRX one for MX and a like. M/MX CLI came first and used
> the
Agree. Can’t please everyone all the time.
Sent from my iPhone
> On Jul 17, 2018, at 10:34 AM, Mark Tinka wrote:
>
>
>
> On 17/Jul/18 16:24, Richard McGovern wrote:
>
>> Felt need to jump in here, and hopefully get some of the real facts
>> straight. Prior to ELS CLI Juniper had
On Tue, Jul 17, 2018 at 07:48:52AM +, M Abdeljawad via juniper-nsp wrote:
> Was checking portal for the Netscreen-Junos translation tool but was not
> there, is it obsoleted?
If I remember right, that tool was really Netscreen->JunOSe
So, an obsolete target that was nothing like what an SRX
QFX3500/3600 might have been the only platform where SW change introduced ELS
CLI, but as you mentioned they are EOL now. QFX5100, and all other QFX
platforms (outside of QFX3500/3600) supported ELS CLI only from day 1.
On 7/17/18, 12:43 PM, "Tobias Heister" wrote:
Hi,
On
There is a tool available via the Juniper Partner site that helps with
migrations from Netscreen to SRX.
/Per
> 17 juli 2018 kl. 15:54 skrev Doug McIntyre :
>
>> On Tue, Jul 17, 2018 at 07:48:52AM +, M Abdeljawad via juniper-nsp wrote:
>> Was checking portal for the Netscreen-Junos
Yes... Exactly.
I upgraded to 17.3R2 and was a total mess. And had to downgrade to 15.1X
train.
On Wed, Jul 4, 2018 at 11:31 AM Colton Conor wrote:
> Gustavo,
>
> We you say " Another problem was upgrading to the lastest Junos JTAC
> recommended that made the ACX5048 unusable... ( Junos was
On 17/Jul/18 21:41, Gert Doering wrote:
> (And no, you can't compare this to "this is like Cisco CatOS vs. Cisco IOS",
> because "that was a different operating system, where everything was totally
> different" - inside IOS for switches, such a silly and needless change has
> *never* happened)
Hi,
On Tue, Jul 17, 2018 at 04:46:37PM +, Richard McGovern wrote:
> QFX3500/3600 might have been the only platform where SW change introduced ELS
> CLI, but as you mentioned they are EOL now. QFX5100, and all other QFX
> platforms (outside of QFX3500/3600) supported ELS CLI only from day
Richard McGovern :
> Felt need to jump in here, and hopefully get some of the real facts
> straight. Prior to ELS CLI Juniper had basically 2 different CLI’s – one
> for EX Products and branch SRX one for MX and a like. M/MX CLI came first
> and used the terminology IRB and Bridge Domains.
From: Pavel Lunin
Date: Tuesday, July 17, 2018 at 6:17 PM
To: Richard McGovern
Cc: juniper-nsp
Subject: Re: [j-nsp] EX4550 and MX104
#1 – I do not make the news, I only report it. #2, it is impossible to keep
everyone happy all of the time. I have learned that over almost 40 years in
Mark Tinka :
>
>
> On 12/Jul/18 23:07, Pavel Lunin wrote:
>
> That's normal. Government and financial sectors always use the most
> outdated solutions because of bureaucracy, compliance, certifications and
> all those WTF reasons :)
>
>
> Probably with a big fat vendor (or vendor-partner) 10-year
On 17/Jul/18 10:30, Pavel Lunin wrote:
>
>
> Or because they just don't want to bother with the new Junos switching
> CLI for Broadcom-based models ;)
Well, looks like Juniper are horny for that moving forward, so the only
solution there is to move to another vendor :-).
Mark.
Hi
Was checking portal for the Netscreen-Junos translation tool but was not there,
is it obsoleted?
Thanks
RegardsMahmoud
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
On 17/Jul/18 11:24, Pavel Lunin wrote:
>
>
> Honestly, I don't feel like the new CLI model is broken. For me it
> rather looks like change everything just to change everything.
The new CLI, in itself, isn't broken. What it does is break the old CLI.
IOS to IOS XR is one thing. But even they
On Fri, Jul 13, 2018 at 12:35 AM Phil Shafer wrote:
>
> Martin T writes:
> >aren't you using grave accent("echo -e "\x60"") character? I was using
> >"echo -e "\x27"" character.
>
> Doh! I read apostrophe (even named the script apos.slax) but my
> brain turned into backtick.
>
> Yes, this looks
Felt need to jump in here, and hopefully get some of the real facts straight.
Prior to ELS CLI Juniper had basically 2 different CLI’s – one for EX Products
and branch SRX one for MX and a like. M/MX CLI came first and used the
terminology IRB and Bridge Domains. These products were designed
On Tue, Jul 17, 2018 at 10:52 AM, Mark Tinka wrote:
>
> Or because they just don't want to bother with the new Junos switching CLI
> for Broadcom-based models ;)
>
>
> Well, looks like Juniper are horny for that moving forward, so the only
> solution there is to move to another vendor :-).
>
Another cool thing with EVE-NG, it has got REST APIs which can be used in
CI/CD automated builds for things like testing and validation. Might be a
useful tool for NetDevOps :)
Ashvin
On Mon, Jul 16, 2018 at 7:06 PM Aaron Gould wrote:
> Cool, yeah, my gosh I like eve more than lsys at this
Hi,
On Tue, Jul 17, 2018 at 11:24:18AM +0200, Pavel Lunin wrote:
> Honestly, I don't feel like the new CLI model is broken. For me it rather
> looks like change everything just to change everything.
And that makes it "non-broken", why?
gert
--
"If was one thing all people took for granted, was
19 matches
Mail list logo
