[j-nsp] JUNOS 10.4S6 for EX8200 - PR/676826

Jackson Jacobson jackson.j.jacobson at gmail.com
Wed Aug 31 00:03:17 EDT 2011


So what kind of internal evaluation process do you guys (or gals) put new
versions of code through before production deployment?  How do you simulate
the production traffic? Is your process pretty reliable?

Always curious,
j.j.j.
On Aug 30, 2011 8:34 PM, "Dale Shaw" <dale.shaw+j-nsp at gmail.com> wrote:
> Hi,
>
> On Wed, Aug 31, 2011 at 1:28 PM, Jackson Jacobson
> <jackson.j.jacobson at gmail.com> wrote:
>> I am curious about what version of junos people on the list run. If
you're
>> sticking way behind, why?
>>
>> j.j.j.
>
> Diff'rent strokes for diff'rent folks!
>
> We run 10.0S1 on our EX-series boxes (apart from EX2200s and EX4500s
> which have higher minimum release requirements) because 10.0S1 fixed
> most of the horrible bugs we encountered with the original code we
> ran; 10.0R2.
>
> We're now moving to 10.4 on EX-series because of the dual-root
> partitioning / resilient filesystem changes introduced in 10.4R3
> (although I must say I am a bit underwhelmed by the implementation of
> this!) Within 10.4, based on the premise that between releases, the
> only changes are bug fixes, it seems "newer is better".
>
> On our J and SRX boxes, we're running 10.0R4 due to the security
> evaluation status of that specific release. We'll move to 10.4 on
> these platforms once 10.4 has been evaluated (est. late 2011).
>
> Cheers,
> Dale


More information about the juniper-nsp mailing list