We're still running 10.0R3.10 on MX platform (MX480) and with an uptime of about 261 days and "no obvious issues" (notice I choose my words carefully there) is there a reason to upgrade or just sit back at this point? I realize this is a bit of a loaded question but today we have no issues that we're aware of.
The only minor issue we found (and couldn't replicate reliably) was a phantom BGP bug - remove a session and it still showed up in an active state. Clear the session and it would then disappear... Paul -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Richard A Steenbergen Sent: January-28-11 5:17 PM To: Keith Cc: Juniper-Nsp Subject: Re: [j-nsp] MX480 JunOS version. On Fri, Jan 28, 2011 at 02:03:54PM -0800, Keith wrote: > > Currently the box is running 10.2R1.8. It has a MIC-3D 20 port card, > MPC1, and RE-S-2000. Juniper just put out a tech bulletin this morning admitting the obvious, that 10.2R1/R2/R3 and 10.3R1 for Trio (MPC) cards are massively broken and shouldn't be used. Try 10.3R2, it's been mostly ok for us (not counting the bug we hit the other day where all the MPCs crashed in an endless loop after updating a prefix-list referenced in a firewall filter on them, but at least so far this seems rare :P). Alas 10.3R3 seems to be delayed, but you'll be far better off with 10.3R2 than you will with 10.2R1 in the config above. -- Richard A Steenbergen <[email protected]> http://www.e-gerbil.net/ras GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC) _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
