[j-nsp] upgrading from old code

[Jared Mauch]

On Mon, Sep 19, 2011 at 07:06:49PM -0400, Dave Diller wrote:
> I'm going to stage it in the lab to see what happens, but any signposts along the way would be appreciated :-)

	It should work just fine.  Biggest problems will be if there are any
configuration directives that went away, etc..

	Everyone has a backup of their router configs in RANCID or something
else, right? :)

	I've seen a few cases where the config won't commit based on some
directive.  Obviously the solution is to test and identify what may not
work.

	If the question is regarding "will the software install & work?"
that answer is Yes.  Is the process supported by Juniper?  No.  They will
not fix bugs in the upgrade process as it relates to this.  I've not yet
heard an updated story about going from one EEOL to another EEOL release
as in the past that was actually 'too-many-versions', but I hope this was
addressed by now.

	- Jared

-- 
Jared Mauch  | pgp key available via finger from jared at puck.nether.net
clue++;      | http://puck.nether.net/~jared/  My statements are only mine.