Re: [j-nsp] What is your experience with the EX2200

[Christian Scholz]

Unfortunately no pattern yet - all areas have problems - but if I have to
name one that has very "hard" Problems it will be dot1x...
Thing is, that we installed a lot of them in production, they were just fine
but after a while we noticed, that whenever we changed the config (even
changing a single VLAN) the Device crashes - no pattern - no Clue. 
Core-Dump does not tell anything good.
JTAC is on this but didn't come up with a Solution yet - we replaced all of
them with the good old EX2200 and now the Production Network runs fine again
(Version 12.3R12-S6 I think).
We will test 17.4 or maybe even better 18.1 or 18.2 - the EX2300 needs to
become more mature before we trust it again.

By the way:
My earlier Mail was not meant to "bully" anyone - it was just my Opinion. I
love Juniper but the Software 15.1 is only a Joke - but enough said ;)



-Ursprüngliche Nachricht-
Von: Dan White [mailto:dwh...@olp.net] 
Gesendet: Montag, 11. Dezember 2017 16:53
An: Christian Scholz 
Cc: juniper-nsp@puck.nether.net
Betreff: Re: What is your experience with the EX2200

Thank you all for your feedback. This is invaluable advice as we don't have
much operational experience with Juniper switches to work with.

Christian,

Is there a common theme among the issues you've encountered? Are they
aligned with a particularly feature set?

On 12/09/17 20:29 +0100, Christian Scholz wrote:
>I would only buy the EX2300 if somebody points a Gun in my Face -
seriously!
>Anyone recommending a Device that purely relies on 15.1 Software does 
>not even closely know what he is talking about...
>
>The 2300 is a Joke so far - We have 7 PR's open and weekly Core-Dumps...
>Stick with the EX2200 since the EX2200 is not EOL and the EX2300 is 
>unusable until a fine Release (17.3 onwards) is available, fixing all 
>the critical things.
>15.1 is the new Windows Vista - unstable, unreliable and just a big 
>joke - never ever ever ever use a 15.X in Production until you want to 
>watch the World burn...
>
>Just my 2 cents...

--
Dan White
BTC Broadband
Network Admin Lead
Ph  918.366.0248 (direct)   main: (918)366-8000
Fax 918.366.6610email: dwh...@olp.net
http://www.btcbroadband.com


___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] What is your experience with the EX2200

[Chris Lee via juniper-nsp]

On Tue, Dec 12, 2017 at 2:29 AM, Kevin Day  wrote:

> The problems with the EX2300 I've seen:
>
> * The out-of-the-box version of Junos on them has a clock bug where it
> says its NTP synced, but the system clock gets advanced to 2038 and things
> go crazy. It's sometimes difficult to keep the switch running long enough
> to upgrade it.
>

Yep hit this bug several times but was hard to pinpoint an exact cause,
sometimes it seemed to be worse if I'd powered the switch up and left it
for a while before loading the initial config. After a while I found that
manually setting the time to within a few minutes of correct local time and
rebooting the switch that it would be enough to get the new image deployed.


> * It's also painfully slow to reboot, but not quite as bad as the EX2200.
>

Yeah was equally disappointed to see that boot times hadn't improved any
over the EX2200, in my experience both platforms take a full 5 minutes to
boot and start forwarding traffic.


> * Some old half-duplex devices don't negotiate with the EX2300, but work
> with the EX2200. It's improved with later builds, but not perfect.
>

We similarly had issues with old model Gallagher cardax controllers not
properly negotiating on the EX2300, they used to negotiate themselves to
10Mbps Half-Duplex on the old Cisco 3750 switches just fine, took a bit of
trial and error on the EX2300 configs to work out to just set the port to
10Mbps Full-Duplex with no auto-negotiate and no flow-control and they show
up as working at 10Mbps Full Duplex now.

>
> Overall neither switch has had bad enough issues that I'd shy away from
> them. The 2300 is definitely an upgrade that I'm happy with.
>

Agreed, although the need to purchase a "paper" licence for the 2300 just
to enable virtual-chassis when it was otherwise standard on the EX2200
seems to be a step backwards as well, I'm having to store a whole heap of
envelopes with the paper licence to apparently prove the right to use that
feature.
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] What is your experience with the EX2200

[Kevin Day]

I've got a few EX2200s and EX2300s and have been pretty happy with both. The 
complaint below is most likely due to the power going out *twice* before a 
successful boot is completed. What seems to happen is if power is lost, and 
while it's rebooting the switch loses power again, it assumes there's a problem 
with the primary partition and flips over to a backup image with no 
configuration. It's hard to tell that this happened though, and a pain to 
recover from. The reboot time is pretty excessive, which can also make people 
think it's broken so they try power cycling which increases this problem. I do 
have an EX3300 that seems to corrupt the filesystem on every power loss though, 
so it could be either.


The problems with the EX2200 I've seen:

* The CPU and RAM are barely enough for some complex configurations. It's 
possible to have processes killed when running out of ram. SNMP requests can 
get lost easily while it's busy. Disk I/O feels worse than floppy speed, plan 
for very long downtimes to do an upgrade.
* Disk I/O is so slow, things like "request system snapshot" can timeout 
without completing.
* Older builds had problems where if the temperature sensor went below 0C (cold 
start in an unheated environment) it read the temperature as 255C and would 
immediately shut down because it thought it was on fire. (Really, see KB23253)
* The switch actually has a fair bit of smarts in dealing with very cold 
temperatures, but later builds (that fix the above point) occasionally will log 
"Triggering freezing circuitry..." panic then and get stuck in a reboot loop. 
(PR1183631)

The problems with the EX2300 I've seen:

* The out-of-the-box version of Junos on them has a clock bug where it says its 
NTP synced, but the system clock gets advanced to 2038 and things go crazy. 
It's sometimes difficult to keep the switch running long enough to upgrade it.
* It's also painfully slow to reboot, but not quite as bad as the EX2200.
* Some old half-duplex devices don't negotiate with the EX2300, but work with 
the EX2200. It's improved with later builds, but not perfect.


Overall neither switch has had bad enough issues that I'd shy away from them. 
The 2300 is definitely an upgrade that I'm happy with.


> On Dec 8, 2017, at 1:06 PM, Matt Freitag  > wrote:
>  - Sometimes when they lose power abruptly it corrupts the file system on
>  the primary partition. Best way I know of to solve this is a complete
>  reinstall of the OS on the routing engine.
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] What is your experience with the EX2200

[adamv0025]

Yeah vote with your valet,
I guess another option would be to ask vendor to throw in bug scrub on selected 
code version free of charge as part of the deal. 
Yeah you reminded me of the cisco live presentation by Aleks Vidakovic in 
Berlin - he mentioned some new platform for code testing highly efficient in 
catching most of the bugs (or something along those lines). 
So yeah fingers crossed.

adam

netconsultings.com
::carrier-class solutions for the telecommunications industry::

> -Original Message-
> From: Saku Ytti [mailto:s...@ytti.fi]
> Sent: Monday, December 11, 2017 3:43 PM
> To: aheb...@pubnix.net
> Cc: adamv0...@netconsultings.com; juniper-nsp@puck.nether.net
> Subject: Re: [j-nsp] What is your experience with the EX2200
> 
> Are we mandating that vendors test, are we monitoring that they do and
> that it is working?
> 
> We can add to RFP requirements about test driven development, we can ask
> quarterly reports about coverage and bugs opened in different phases of
> testing and by customers. I.e. we can create financial incentive to vendors to
> do proper testing.
> 
> As much as I'd like to bash vendors, most of them actually today (very
> different story 5 or even 3 years ago) have considerable investments on
> testing and reducing customer caught bugs. Lot of the work is only
> materialising on newer release trains. So I do see light at the end of the
> tunnel and I hope it's not the train.
> 
> 
> On 11 December 2017 at 17:37, Alain Hebert  wrote:
> > Well,
> >
> > At budget of $200k+ for 2 sites, I'm expecting more than having to
> > road test Lada's.
> >
> > -
> > Alain Hebertaheb...@pubnix.net
> > PubNIX Inc.
> > 50 boul. St-Charles
> > P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
> > Tel: 514-990-5911  http://www.pubnix.netFax: 514-990-9443
> >
> > On 12/11/17 10:34, adamv0...@netconsultings.com wrote:
> >>
> >> Smells like everyone's me3600 experience, The competition is fierce
> >> nowadays forcing release of new platforms without proper regression
> >> testing.
> >> Kind of makes sense right? Allows vendors to get to market on time
> >> while saving capex related to testing, Operators test internally
> >> anyways so why to bother right?
> >> Think about it, having market converge on set of use cases and code
> >> versions and basically test for you is always more efficient than you
> >> trying to come up with a test case for every possible combination of
> >> use cases and code versions.
> >>
> >> adam
> >>
> >> netconsultings.com
> >> ::carrier-class solutions for the telecommunications industry::
> >>
> >>> -Original Message-
> >>> From: juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] On
> >>> Behalf Of Alain Hebert
> >>> Sent: Monday, December 11, 2017 1:18 PM
> >>> To: juniper-nsp@puck.nether.net
> >>> Subject: Re: [j-nsp] What is your experience with the EX2200
> >>>
> >>>   Rofl, smell like my QFX5100 experience.
> >>>
> >>>   PS: And I think its more of a platform issue than a software issue.
> >>>
> >>> -
> >>> Alain Hebertaheb...@pubnix.net
> >>> PubNIX Inc.
> >>> 50 boul. St-Charles
> >>> P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
> >>> Tel: 514-990-5911  http://www.pubnix.netFax: 514-990-9443
> >>>
> >>> On 12/09/17 14:29, Christian Scholz wrote:
> >>>>
> >>>> I would only buy the EX2300 if somebody points a Gun in my Face -
> >>>
> >>> seriously!
> >>>>
> >>>> Anyone recommending a Device that purely relies on 15.1 Software
> >>>> does not even closely know what he is talking about...
> >>>>
> >>>> The 2300 is a Joke so far - We have 7 PR's open and weekly Core-
> Dumps...
> >>>> Stick with the EX2200 since the EX2200 is not EOL and the EX2300 is
> >>>> unusable until a fine Release (17.3 onwards) is available, fixing
> >>>> all the critical things.
> >>>> 15.1 is the new Windows Vista - unstable, unreliable and just a big
> >>>> joke - never ever ever ever use a 15.X in Production until you want
> >>>> to watch the World burn...
> >>>>
> >>>> Just my 2 cents...
> >>>>
> >>>>
> >>>> ___
> >>>> 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
> >>
> >>
> >
> > ___
> > juniper-nsp mailing list juniper-nsp@puck.nether.net
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
> 
> 
> 
> --
>   ++ytti

___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] What is your experience with the EX2200

[Dan White]

Thank you all for your feedback. This is invaluable advice as we don't have
much operational experience with Juniper switches to work with.

Christian,

Is there a common theme among the issues you've encountered? Are they
aligned with a particularly feature set?

On 12/09/17 20:29 +0100, Christian Scholz wrote:

I would only buy the EX2300 if somebody points a Gun in my Face - seriously!
Anyone recommending a Device that purely relies on 15.1 Software does not
even closely know what he is talking about...

The 2300 is a Joke so far - We have 7 PR's open and weekly Core-Dumps...
Stick with the EX2200 since the EX2200 is not EOL and the EX2300 is unusable
until a fine Release (17.3 onwards) is available, fixing all the critical
things.
15.1 is the new Windows Vista - unstable, unreliable and just a big joke -
never ever ever ever use a 15.X in Production until you want to watch the
World burn...

Just my 2 cents...


--
Dan White
BTC Broadband
Network Admin Lead
Ph  918.366.0248 (direct)   main: (918)366-8000
Fax 918.366.6610email: dwh...@olp.net
http://www.btcbroadband.com
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] What is your experience with the EX2200

[Saku Ytti]

Are we mandating that vendors test, are we monitoring that they do and
that it is working?

We can add to RFP requirements about test driven development, we can
ask quarterly reports about coverage and bugs opened in different
phases of testing and by customers. I.e. we can create financial
incentive to vendors to do proper testing.

As much as I'd like to bash vendors, most of them actually today (very
different story 5 or even 3 years ago) have considerable investments
on testing and reducing customer caught bugs. Lot of the work is only
materialising on newer release trains. So I do see light at the end of
the tunnel and I hope it's not the train.


On 11 December 2017 at 17:37, Alain Hebert  wrote:
> Well,
>
> At budget of $200k+ for 2 sites, I'm expecting more than having to road
> test Lada's.
>
> -
> Alain Hebertaheb...@pubnix.net
> PubNIX Inc.
> 50 boul. St-Charles
> P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
> Tel: 514-990-5911  http://www.pubnix.netFax: 514-990-9443
>
> On 12/11/17 10:34, adamv0...@netconsultings.com wrote:
>>
>> Smells like everyone's me3600 experience,
>> The competition is fierce nowadays forcing release of new platforms
>> without proper regression testing.
>> Kind of makes sense right? Allows vendors to get to market on time while
>> saving capex related to testing, Operators test internally anyways so why to
>> bother right?
>> Think about it, having market converge on set of use cases and code
>> versions and basically test for you is always more efficient than you trying
>> to come up with a test case for every possible combination of use cases and
>> code versions.
>>
>> adam
>>
>> netconsultings.com
>> ::carrier-class solutions for the telecommunications industry::
>>
>>> -Original Message-
>>> From: juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf
>>> Of Alain Hebert
>>> Sent: Monday, December 11, 2017 1:18 PM
>>> To: juniper-nsp@puck.nether.net
>>> Subject: Re: [j-nsp] What is your experience with the EX2200
>>>
>>>   Rofl, smell like my QFX5100 experience.
>>>
>>>   PS: And I think its more of a platform issue than a software issue.
>>>
>>> -
>>> Alain Hebertaheb...@pubnix.net
>>> PubNIX Inc.
>>> 50 boul. St-Charles
>>> P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
>>> Tel: 514-990-5911  http://www.pubnix.netFax: 514-990-9443
>>>
>>> On 12/09/17 14:29, Christian Scholz wrote:
>>>>
>>>> I would only buy the EX2300 if somebody points a Gun in my Face -
>>>
>>> seriously!
>>>>
>>>> Anyone recommending a Device that purely relies on 15.1 Software does
>>>> not even closely know what he is talking about...
>>>>
>>>> The 2300 is a Joke so far - We have 7 PR's open and weekly Core-Dumps...
>>>> Stick with the EX2200 since the EX2200 is not EOL and the EX2300 is
>>>> unusable until a fine Release (17.3 onwards) is available, fixing all
>>>> the critical things.
>>>> 15.1 is the new Windows Vista - unstable, unreliable and just a big
>>>> joke - never ever ever ever use a 15.X in Production until you want to
>>>> watch the World burn...
>>>>
>>>> Just my 2 cents...
>>>>
>>>>
>>>> ___
>>>> 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
>>
>>
>
> ___
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp



-- 
  ++ytti
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] What is your experience with the EX2200

[Alain Hebert]

    Well,

    At budget of $200k+ for 2 sites, I'm expecting more than having to 
road test Lada's.


-
Alain Hebertaheb...@pubnix.net
PubNIX Inc.
50 boul. St-Charles
P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
Tel: 514-990-5911  http://www.pubnix.netFax: 514-990-9443

On 12/11/17 10:34, adamv0...@netconsultings.com wrote:

Smells like everyone's me3600 experience,
The competition is fierce nowadays forcing release of new platforms without 
proper regression testing.
Kind of makes sense right? Allows vendors to get to market on time while saving 
capex related to testing, Operators test internally anyways so why to bother 
right?
Think about it, having market converge on set of use cases and code versions 
and basically test for you is always more efficient than you trying to come up 
with a test case for every possible combination of use cases and code versions.

adam

netconsultings.com
::carrier-class solutions for the telecommunications industry::


-Original Message-
From: juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf
Of Alain Hebert
Sent: Monday, December 11, 2017 1:18 PM
To: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] What is your experience with the EX2200

  Rofl, smell like my QFX5100 experience.

  PS: And I think its more of a platform issue than a software issue.

-
Alain Hebertaheb...@pubnix.net
PubNIX Inc.
50 boul. St-Charles
P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
Tel: 514-990-5911  http://www.pubnix.netFax: 514-990-9443

On 12/09/17 14:29, Christian Scholz wrote:

I would only buy the EX2300 if somebody points a Gun in my Face -

seriously!

Anyone recommending a Device that purely relies on 15.1 Software does
not even closely know what he is talking about...

The 2300 is a Joke so far - We have 7 PR's open and weekly Core-Dumps...
Stick with the EX2200 since the EX2200 is not EOL and the EX2300 is
unusable until a fine Release (17.3 onwards) is available, fixing all
the critical things.
15.1 is the new Windows Vista - unstable, unreliable and just a big
joke - never ever ever ever use a 15.X in Production until you want to
watch the World burn...

Just my 2 cents...


___
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




___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] What is your experience with the EX2200

[adamv0025]

Smells like everyone's me3600 experience,
The competition is fierce nowadays forcing release of new platforms without 
proper regression testing. 
Kind of makes sense right? Allows vendors to get to market on time while saving 
capex related to testing, Operators test internally anyways so why to bother 
right? 
Think about it, having market converge on set of use cases and code versions 
and basically test for you is always more efficient than you trying to come up 
with a test case for every possible combination of use cases and code versions. 

adam

netconsultings.com
::carrier-class solutions for the telecommunications industry::

> -Original Message-
> From: juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf
> Of Alain Hebert
> Sent: Monday, December 11, 2017 1:18 PM
> To: juniper-nsp@puck.nether.net
> Subject: Re: [j-nsp] What is your experience with the EX2200
> 
>  Rofl, smell like my QFX5100 experience.
> 
>  PS: And I think its more of a platform issue than a software issue.
> 
> -
> Alain Hebertaheb...@pubnix.net
> PubNIX Inc.
> 50 boul. St-Charles
> P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
> Tel: 514-990-5911  http://www.pubnix.netFax: 514-990-9443
> 
> On 12/09/17 14:29, Christian Scholz wrote:
> > I would only buy the EX2300 if somebody points a Gun in my Face -
> seriously!
> > Anyone recommending a Device that purely relies on 15.1 Software does
> > not even closely know what he is talking about...
> >
> > The 2300 is a Joke so far - We have 7 PR's open and weekly Core-Dumps...
> > Stick with the EX2200 since the EX2200 is not EOL and the EX2300 is
> > unusable until a fine Release (17.3 onwards) is available, fixing all
> > the critical things.
> > 15.1 is the new Windows Vista - unstable, unreliable and just a big
> > joke - never ever ever ever use a 15.X in Production until you want to
> > watch the World burn...
> >
> > Just my 2 cents...
> >
> >
> > ___
> > 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

___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] What is your experience with the EX2200

[Matt Freitag]

Also since it was mentioned earlier and I forgot to mention it, I'm running
simple MAC auth 802.1x on 83 EX2200's and the only issue is the captive
portal functionality in Junos 12 is pretty terrible but it's been that way
for years. If you need good captive portal go to the EX2300.

Matt Freitag
Network Engineer
Information Technology
Michigan Technological University
(906) 487-3696 <%28906%29%20487-3696>
https://www.mtu.edu/
https://www.mtu.edu/it

On Mon, Dec 11, 2017 at 8:17 AM, Alain Hebert  wrote:

> Rofl, smell like my QFX5100 experience.
>
> PS: And I think its more of a platform issue than a software issue.
>
> -
> Alain Hebertaheb...@pubnix.net
> PubNIX Inc.
> 50 boul. St-Charles
> 
> P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
> Tel: 514-990-5911  http://www.pubnix.netFax: 514-990-9443
>
>
> On 12/09/17 14:29, Christian Scholz wrote:
>
>> I would only buy the EX2300 if somebody points a Gun in my Face -
>> seriously!
>> Anyone recommending a Device that purely relies on 15.1 Software does not
>> even closely know what he is talking about...
>>
>> The 2300 is a Joke so far - We have 7 PR's open and weekly Core-Dumps...
>> Stick with the EX2200 since the EX2200 is not EOL and the EX2300 is
>> unusable
>> until a fine Release (17.3 onwards) is available, fixing all the critical
>> things.
>> 15.1 is the new Windows Vista - unstable, unreliable and just a big joke -
>> never ever ever ever use a 15.X in Production until you want to watch the
>> World burn...
>>
>> Just my 2 cents...
>>
>>
>> ___
>> 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
>
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] What is your experience with the EX2200

[Alain Hebert]

    Rofl, smell like my QFX5100 experience.

    PS: And I think its more of a platform issue than a software issue.

-
Alain Hebertaheb...@pubnix.net
PubNIX Inc.
50 boul. St-Charles
P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
Tel: 514-990-5911  http://www.pubnix.netFax: 514-990-9443

On 12/09/17 14:29, Christian Scholz wrote:

I would only buy the EX2300 if somebody points a Gun in my Face - seriously!
Anyone recommending a Device that purely relies on 15.1 Software does not
even closely know what he is talking about...

The 2300 is a Joke so far - We have 7 PR's open and weekly Core-Dumps...
Stick with the EX2200 since the EX2200 is not EOL and the EX2300 is unusable
until a fine Release (17.3 onwards) is available, fixing all the critical
things.
15.1 is the new Windows Vista - unstable, unreliable and just a big joke -
never ever ever ever use a 15.X in Production until you want to watch the
World burn...

Just my 2 cents...


___
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] What is your experience with the EX2200

[Nathan Ward]

I’d prefer to buy the EX2300, but it doesn’t have PVLAN support presently, 
which in our management network is a hard requirement. EX2200 does the job 
brilliantly for now though!

> On 10/12/2017, at 9:10 AM, Saku Ytti  wrote:
> 
> Hey Christian,
> 
> It's not just your two cents when you state anyone recommending them
> do not know what they are talking about.
> 
> Your information is highly anecdotal, we can take any company, any
> product and we can find consumers who are extremely satisfied and
> consumers who believe it's the worst option on the market. Often times
> these consumers extrapolate too far, in both directions.
> 
> Higher quality of data would measure PR count of EX2200 to EX2300 in
> same period of life cycle. Why I personally would not invest on
> EX2200, unless I can find really cheap gray ones, is simply because
> this whole Marvell => Broadcom operation is rather large undertaking
> and affects almost whole EX platform. Marvell is decidedly dead
> platform in JNPR, and my concern, as customer, would be that my vendor
> has decreased incentive to fix issues I have, because they can get
> better ROI of engineering hours spent on Broadcom platforms.
> 
> I fully believe that you have major issues on the platform, but how
> widely your experience translates to other networks is not obvious. I
> also fully believe EX2200 is more mature platform. It is trade-off you
> must do after your lab the solutions, if you can get the latest
> generation hardware working, of course you should invest on it, for
> the longer amortisation times. If you cannot get it working, and no
> other vendor is available, then buying dying platform can be
> justified.
> For what it is worth, I have no problems on EX2300 in simple L2 switch
> scenario. I do not doubt that there are features and feature
> combinations which are fragile.
> 
> 
> 
> On 9 December 2017 at 21:29, Christian Scholz  wrote:
>> I would only buy the EX2300 if somebody points a Gun in my Face - seriously!
>> Anyone recommending a Device that purely relies on 15.1 Software does not
>> even closely know what he is talking about...
>> 
>> The 2300 is a Joke so far - We have 7 PR's open and weekly Core-Dumps...
>> Stick with the EX2200 since the EX2200 is not EOL and the EX2300 is unusable
>> until a fine Release (17.3 onwards) is available, fixing all the critical
>> things.
>> 15.1 is the new Windows Vista - unstable, unreliable and just a big joke -
>> never ever ever ever use a 15.X in Production until you want to watch the
>> World burn...
>> 
>> Just my 2 cents...
>> 
>> 
>> ___
>> juniper-nsp mailing list juniper-nsp@puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
> 
> 
> 
> -- 
>  ++ytti
> ___
> 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] What is your experience with the EX2200

[Saku Ytti]

Hey Christian,

It's not just your two cents when you state anyone recommending them
do not know what they are talking about.

Your information is highly anecdotal, we can take any company, any
product and we can find consumers who are extremely satisfied and
consumers who believe it's the worst option on the market. Often times
these consumers extrapolate too far, in both directions.

Higher quality of data would measure PR count of EX2200 to EX2300 in
same period of life cycle. Why I personally would not invest on
EX2200, unless I can find really cheap gray ones, is simply because
this whole Marvell => Broadcom operation is rather large undertaking
and affects almost whole EX platform. Marvell is decidedly dead
platform in JNPR, and my concern, as customer, would be that my vendor
has decreased incentive to fix issues I have, because they can get
better ROI of engineering hours spent on Broadcom platforms.

I fully believe that you have major issues on the platform, but how
widely your experience translates to other networks is not obvious. I
also fully believe EX2200 is more mature platform. It is trade-off you
must do after your lab the solutions, if you can get the latest
generation hardware working, of course you should invest on it, for
the longer amortisation times. If you cannot get it working, and no
other vendor is available, then buying dying platform can be
justified.
For what it is worth, I have no problems on EX2300 in simple L2 switch
scenario. I do not doubt that there are features and feature
combinations which are fragile.



On 9 December 2017 at 21:29, Christian Scholz  wrote:
> I would only buy the EX2300 if somebody points a Gun in my Face - seriously!
> Anyone recommending a Device that purely relies on 15.1 Software does not
> even closely know what he is talking about...
>
> The 2300 is a Joke so far - We have 7 PR's open and weekly Core-Dumps...
> Stick with the EX2200 since the EX2200 is not EOL and the EX2300 is unusable
> until a fine Release (17.3 onwards) is available, fixing all the critical
> things.
> 15.1 is the new Windows Vista - unstable, unreliable and just a big joke -
> never ever ever ever use a 15.X in Production until you want to watch the
> World burn...
>
> Just my 2 cents...
>
>
> ___
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp



-- 
  ++ytti
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] What is your experience with the EX2200

[Emille Blanc]

We've got a half dozen EX2300 and EX2300-C's in production, and no issues for 
us with those so far.
EX2200's have been fine for us less a pair of 2200-C's that managed to go out 
the door with 15.x JunOS. But as someone stated in this thread earlier, there 
are known issues attempting this on the fanless compact form factor switch. We 
rolled them back to 12.x and they've been as solid as the rest since.
We're only using L2 features on both platforms though, less a few niche cases 
or temporary L3 config for network diagnosis purposes.
So can't provide much in the way of feedback on L3 features that OP is 
interested in.
Overall, we're quite happy with both platforms, and usually only bring in a 
2300 over a 2200 if we need the SFP+ cages for 10gig uplinks.

Our typical feature use;
TACACS+
802.1ad tunnels and VLAN mapping
802.1q VLAN push/pop
802.1p marking
VSTP
LACP / Aggregated ether / port channel

From: juniper-nsp [juniper-nsp-boun...@puck.nether.net] On Behalf Of Christian 
Scholz [c...@ip4.de]
Sent: Saturday, December 09, 2017 11:29 AM
To: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] What is your experience with the EX2200

I would only buy the EX2300 if somebody points a Gun in my Face - seriously!
Anyone recommending a Device that purely relies on 15.1 Software does not
even closely know what he is talking about...

The 2300 is a Joke so far - We have 7 PR's open and weekly Core-Dumps...
Stick with the EX2200 since the EX2200 is not EOL and the EX2300 is unusable
until a fine Release (17.3 onwards) is available, fixing all the critical
things.
15.1 is the new Windows Vista - unstable, unreliable and just a big joke -
never ever ever ever use a 15.X in Production until you want to watch the
World burn...

Just my 2 cents...


___
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] What is your experience with the EX2200

[Christian Scholz]

I would only buy the EX2300 if somebody points a Gun in my Face - seriously!
Anyone recommending a Device that purely relies on 15.1 Software does not
even closely know what he is talking about...

The 2300 is a Joke so far - We have 7 PR's open and weekly Core-Dumps...
Stick with the EX2200 since the EX2200 is not EOL and the EX2300 is unusable
until a fine Release (17.3 onwards) is available, fixing all the critical
things.
15.1 is the new Windows Vista - unstable, unreliable and just a big joke -
never ever ever ever use a 15.X in Production until you want to watch the
World burn...

Just my 2 cents...


___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] What is your experience with the EX2200

[Wojciech Owczarek]

As some have said, EX2300 is the current platform. I am using EX2200C. Pretty 
much the only feature wise decent cheap(ish) fanless switch in existence if you 
ask me. As a L2 switch, no issues, POE works fine. No BGP support, because 
please buy a higher model, but other than that, OSPF, PIM, routing instances, 
fw filters, IPv6, VRRP, GRE tunnels, all working fine. GRE broken in routing 
instances though on latest JunOS for it. This is as far as I've gone with 
protocol support. Solid box. Feels no different to 3200/4200 bar spec and 
features obviously. Did not check dot1x or DHCP helpers which may be of use for 
branch or campus.

Thanks,
Wojciech

  Original Message  
From: dwh...@olp.net
Sent: 8 December 2017 5:41 p.m.
To: juniper-nsp@puck.nether.net
Subject: [j-nsp] What is your experience with the EX2200

We're considering purchasing these switches for our branch offices. Our
needs include PoE, and basic routing functionality. What's been your
experience with these switches?

-- 
Dan White
BTC Broadband
Network Admin Lead
Ph  918.366.0248 (direct)   main: (918)366-8000
Fax 918.366.6610    email: dwh...@olp.net
http://www.btcbroadband.com
___
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] What is your experience with the EX2200

[Joel Dahl]

I have deployed around 200 EX2200-48P. All running 12.3R12. Only doing some
simple stuff, vlans, static routing. I have no real complaints - they have
been rock solid in our setup. Juniper told me some time ago that it was a
platform on the way out, but I haven't seen any EOL dates yet.

-- 
Joel

On Fri, Dec 08, 2017 at 11:41:15AM -0600, Dan White wrote:
> We're considering purchasing these switches for our branch offices. Our
> needs include PoE, and basic routing functionality. What's been your
> experience with these switches?
> 
> -- 
> Dan White
> BTC Broadband
> Network Admin Lead
> Ph  918.366.0248 (direct)   main: (918)366-8000
> Fax 918.366.6610email: dwh...@olp.net
> http://www.btcbroadband.com
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] What is your experience with the EX2200

[Chuck Anderson]

The most current supported software on EX2200 is 12.3R12--there were
some issues with insufficient flash space for 15.1, so they rolled
back the recommended release to 12.3R12.

They are fairly solid boxes, although I do notice occasional STP
issues on them (Root Bridge changes, Loop Protect activating),
probably when the CPU gets busy and misses some STP BPDUs.  I haven't
seen this issue with our EX4200s.  Luckily it isn't service impacting
in our deployment, since we don't have any redundant links (loops) and
it recovers quickly.

On Fri, Dec 08, 2017 at 02:06:26PM -0500, Matt Freitag wrote:
> For some reason I also thought the EX2200 EOL date was coming up in a year
> or two but cannot find any sources to prove that.
> 
> My only complaints about the box:
> 
>- Sometimes when they lose power abruptly it corrupts the file system on
>the primary partition. Best way I know of to solve this is a complete
>reinstall of the OS on the routing engine.
>   - This does not affect forwarding at all since the actual packet
>   forwarding happens on a different unit of the box. You'll only see this
>   when you try to SSH to it, for example, and it rejects your attempts by
>   closing your connection.
>- It takes these things a few seconds to commit their config, but I
>think the routing engine runs on an 800MHz CPU and 512MB of RAM. They're
>also quite slow to SSH to, again due to the lack of CPU and memory.
> 
> Otherwise the EX2200 is a really solid platform, but as Saku said Juniper
> moved to the EX2300 a long time ago.
> 
> Matt Freitag
> Network Engineer
> Information Technology
> Michigan Technological University
> (906) 487-3696 <%28906%29%20487-3696>
> https://www.mtu.edu/
> https://www.mtu.edu/it
> 
> On Fri, Dec 8, 2017 at 1:54 PM, Saku Ytti  wrote:
> 
> > Only buy EX2200 if you're buying gray and get them really cheap.
> > Juniper has long since moved to entirely different platform EX2300.
> >
> > On 8 December 2017 at 19:41, Dan White  wrote:
> > > We're considering purchasing these switches for our branch offices. Our
> > > needs include PoE, and basic routing functionality. What's been your
> > > experience with these switches?
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] What is your experience with the EX2200

[Matt Freitag]

For some reason I also thought the EX2200 EOL date was coming up in a year
or two but cannot find any sources to prove that.

My only complaints about the box:

   - Sometimes when they lose power abruptly it corrupts the file system on
   the primary partition. Best way I know of to solve this is a complete
   reinstall of the OS on the routing engine.
  - This does not affect forwarding at all since the actual packet
  forwarding happens on a different unit of the box. You'll only see this
  when you try to SSH to it, for example, and it rejects your attempts by
  closing your connection.
   - It takes these things a few seconds to commit their config, but I
   think the routing engine runs on an 800MHz CPU and 512MB of RAM. They're
   also quite slow to SSH to, again due to the lack of CPU and memory.

Otherwise the EX2200 is a really solid platform, but as Saku said Juniper
moved to the EX2300 a long time ago.

Matt Freitag
Network Engineer
Information Technology
Michigan Technological University
(906) 487-3696 <%28906%29%20487-3696>
https://www.mtu.edu/
https://www.mtu.edu/it

On Fri, Dec 8, 2017 at 1:54 PM, Saku Ytti  wrote:

> Only buy EX2200 if you're buying gray and get them really cheap.
> Juniper has long since moved to entirely different platform EX2300.
>
> On 8 December 2017 at 19:41, Dan White  wrote:
> > We're considering purchasing these switches for our branch offices. Our
> > needs include PoE, and basic routing functionality. What's been your
> > experience with these switches?
> >
> > --
> > Dan White
> > BTC Broadband
> > Network Admin Lead
> > Ph  918.366.0248 (direct)   main: (918)366-8000
> > Fax 918.366.6610email: dwh...@olp.net
> > http://www.btcbroadband.com
> > ___
> > juniper-nsp mailing list juniper-nsp@puck.nether.net
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
>
>
>
> --
>   ++ytti
> ___
> 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] What is your experience with the EX2200

[Saku Ytti]

Only buy EX2200 if you're buying gray and get them really cheap.
Juniper has long since moved to entirely different platform EX2300.

On 8 December 2017 at 19:41, Dan White  wrote:
> We're considering purchasing these switches for our branch offices. Our
> needs include PoE, and basic routing functionality. What's been your
> experience with these switches?
>
> --
> Dan White
> BTC Broadband
> Network Admin Lead
> Ph  918.366.0248 (direct)   main: (918)366-8000
> Fax 918.366.6610email: dwh...@olp.net
> http://www.btcbroadband.com
> ___
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp



-- 
  ++ytti
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] What is your experience with the EX2200

[Tim St. Pierre]

I have a DC model that has well over 1000 days of uptime, not a single 
issue.


I do a lot of vLAN, some IGMP snooping, and use the SFP ports.  I 
haven't done any routing with it as of yet, but it's a great switch for 
simple needs.




On 2017-12-08 12:41 PM, Dan White wrote:

We're considering purchasing these switches for our branch offices. Our
needs include PoE, and basic routing functionality. What's been your
experience with these switches?



--

--
Tim St. Pierre
System Operator
Communicate Freely
289-225-1220 x5101

___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

[j-nsp] What is your experience with the EX2200

[Dan White]

We're considering purchasing these switches for our branch offices. Our
needs include PoE, and basic routing functionality. What's been your
experience with these switches?

--
Dan White
BTC Broadband
Network Admin Lead
Ph  918.366.0248 (direct)   main: (918)366-8000
Fax 918.366.6610email: dwh...@olp.net
http://www.btcbroadband.com
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp