[j-nsp] 10.3 on MX960 with MPC only?

[Jonathan Lassoff]

Agreed. To me, it seems to me that the overall quality of JunOS has slipped
since 10.x, however recovering from most problems on JunOS is at least
possible.

In classic IOS, even a small bug or memory leak can quickly turn into a
major catastrophe (no memory management/supervision and a single binary
image). On Juniper platforms, one can usually kill and restart the affected
daemon while the PFEs still chug along.

I hope Juniper takes some time to get their release quality back up to the
par we've come to expect from them over the years.

Cheers,
Jof

On Aug 30, 2010 6:21 PM, "Chris Evans" <chrisccnpspam2 at gmail.com> wrote:
I have real concerns with juniper.  We are primarily a Cisco shop and are
using juniper devices here and there.  I have to honestly say, anymore Cisco
code is way more stable than Junos. I'm always finding major bugs in junos,
yet any Cisco bugs we are finding are usually cornercase ones.

The latest junos bug I've found is that with the mx platform igmp snooping
doesn't work at all in 10.0 and other train releases. In 10.3 all mulicast
is broken when using irb interfaces.  Seriously is no one testing?

I hope they get their act together soon....

On Aug 30, 2010 7:57 PM, "Richard A Steenbergen" <ras at e-gerbil.net> wrote:

> On Mon, Aug 30, 2010 a...
> > In fact, yes! 10.3 is primarily...

> The story I've heard is that they put the brakes on almost all new
> feature development for 10.3 ...
> > similar to 8.5. Perhap...

> Don't get your hopes up, I don't think there has been any significant
> progress made on the route...
> juniper-nsp mailing list juniper-nsp at puck.nether.net...

>
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.n...