[j-nsp] What's the latest code you're running on a mx?

[Richard A Steenbergen]

On Fri, Apr 30, 2010 at 09:55:23AM +0200, Bj?rn Tore wrote:
> We're running 10.0R2.10 on MX. Works quite well.

We just tested 10.0R3 on MX and it was a giant hot steaming mess. Among
other problems, they broke "| last" in cli, isis overload timeout no
longer functions (would never time out, stayed overloaded forever), and
there was some as yet undetermined issue with RSVP/call admission where
LSPs could not transit through the 10.0R3 device even though there was
plenty of bandwidth available and no policy preventing it. We ended up
downgrading back to 9.6S5 (which instantly solved all of the above),
where the biggest problem we've had so far is a chassisd bug which
causes this false warning every time you commit:

chassisd[1305]: %DAEMON-3-UI_CONFIGURATION_ERROR: Process: chassisd, 
path: [edit groups BASE-FORWARDING forwarding-options hash-key family], 
statement: inet6, Could not retrieve the route-accounting setting

Which would just be annoying/log filling, if not for the fact that
netconf interprets it as a hard error and rolls back the remotely
triggered commit. 

Considering you need 10.1 to run the new MX Trio cards, and 10.2 to make
them interoperate with older DPCs in the same chassis, I expect a lot of
people are going to be very unhappy very soon when they're forced to
upgrade. :)

-- 
Richard A Steenbergen <ras at e-gerbil.net>       http://www.e-gerbil.net/ras
GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)