Yeah. ISSU isn't were it should be. Some SMU's require a reload depending on what componets are touched.
On Sun, Nov 8, 2009 at 19:55, William McCall <[email protected]>wrote: > *shrug* I recalled incorrectly. I was under the impression that some > of the minor releases were capable of in-service upgrade. However, it > looks like it just applies to SMUs. And even then, the SMUs might take > out the box. > > On Sun, Nov 8, 2009 at 6:22 PM, Aaron <[email protected]> wrote: > > There isn't a version that you can do that. > > > > Aaron > > > > On Sun, Nov 8, 2009 at 16:01, Eduard Gheorghiu <[email protected]> > > wrote: > >> > >> William, can you give an example of two XR versions that you can migrate > >> between without reloading the whole box? I would like to try it in the > lab > >> in order to see how it is done. > >> Thanks, > >> Eduard > >> > >> On Nov 8, 2009 8:41 PM, "William McCall" <[email protected]> > wrote: > >> > >> There will be downtime if you go directly with these versions. Check > >> with your SE or TAC. IIRC, they should have a list of versions to go > >> through to do a nice graceful (albeit, with some minor disruptions) > >> upgrade. > >> > >> > >> -- > >> William McCall, CCIE #25044 > >> > >> On Sun, Nov 8, 2009 at 7:49 AM, Jason Alex <[email protected]> wrote: > > > >> Dear All, > Ki... > >> _______________________________________________ > >> cisco-nsp mailing list [email protected] > >> https://puck.nether.net/mailman/listinfo/cisco-nsp > >> archive at http://puck.nether.net/pipermail/cisco-nsp/ > > > > > > > > -- > William McCall, CCIE #25044 > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
