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

Saku Ytti saku at ytti.fi
Mon Dec 11 10:42:42 EST 2017


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 <ahebert at pubnix.net> wrote:
>     Well,
>
>     At budget of $200k+ for 2 sites, I'm expecting more than having to road
> test Lada's.
>
> -----
> Alain Hebert                                ahebert at pubnix.net
> PubNIX Inc.
> 50 boul. St-Charles
> P.O. Box 26770     Beaconsfield, Quebec     H9W 6G7
> Tel: 514-990-5911  http://www.pubnix.net    Fax: 514-990-9443
>
> On 12/11/17 10:34, adamv0025 at 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-bounces at puck.nether.net] On Behalf
>>> Of Alain Hebert
>>> Sent: Monday, December 11, 2017 1:18 PM
>>> To: juniper-nsp at 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 Hebert                                ahebert at pubnix.net
>>> PubNIX Inc.
>>> 50 boul. St-Charles
>>> P.O. Box 26770     Beaconsfield, Quebec     H9W 6G7
>>> Tel: 514-990-5911  http://www.pubnix.net    Fax: 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 at puck.nether.net
>>>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>>>
>>> _______________________________________________
>>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>
>>
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp



-- 
  ++ytti


More information about the juniper-nsp mailing list