[j-nsp] upgrading M120 directly from 8.5 to 9.3

Brad Fleming bdfleming at kanren.net
Mon Jan 11 15:41:46 EST 2010

My experience is to always test the upgrade on a spare device;  
especially if its an "unsupported" upgrade path. A similar chassis  
running the same config will help determine what parts of the config  
are likely to change. If possible, I'd suggest attaching your spare  
device to your in-service network and make sure services will continue  
to work. I know this all seems like a huge pain, but if you're  
anything like me you only upgrade software every couple years (unless  
there's a major problem).

If you don't have spare gear available, I'd suggest opening a TAC case  
and asking for an official, supported upgrade path using software  
that's available today. That way if something goes wrong, you already  
have a ticket open with the basic info.
Brad Fleming

On Jan 11, 2010, at 1:59 PM, Chuck Anderson wrote:

> Juniper recommends not upgrading more than 3 releases, but 8.5 to 9.3
> would be a 4-release upgrade (9.0 - 9.1 - 9.2 - 9.3).  Has anyone done
> this with success?  It seems strange to me that Juniper wouldn't test
> and support an upgrade from one E-EOL release to another without
> having to jump through a non-E-EOL release, and in fact a release that
> has actually reached EOL.
> 8.5 reaches EOL on 2011-05-15
> 9.2 has reached EOL as of 2009-11-15
> How is one supposed to upgrade in a supported manner once 9.2 is
> removed from the web site?  Luckily, it is still there now.  But if I
> have a problem with 9.2 during this intermediate upgrade step, Juniper
> won't support it because it is EOL?  Seems like someone didn't think
> this through very well.
> I'd like to avoid the pain and just go directly from 8.5 to 9.3.  What
> are your experiences?
> Thanks.
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp

More information about the juniper-nsp mailing list