It is my understanding that ISSU will be supported for the same feature set in the same dev line.
IE - Will work going from SXI to SXI3 but will not work going from SXI to SXJ. (I know J doesn't exist yet). Is this how everyone else understands ISSU? Any other known restrictions? Jason -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Phil Mayers Sent: Friday, February 12, 2010 3:57 AM To: [email protected] Subject: Re: [c-nsp] ISSU on SXF -> SXI On 02/11/2010 07:48 PM, Randy McAnally wrote: > Thanks for that information. > > What is the 'least problematic' method, step by step, to upgrade from SXF to > SXI since I have dual sups? I can handle a single reboot but don't want to > whack any config or cause the sups to lose redundancy or need multiple or > extended downtimes. Load the firmware onto both sup, change the boot statement, reload the standby sup and it will come up in RPR mode. Force a switchover, the new sup will finish booting & reload the linecards. We do this for almost all our software upgrades, and the outage it typically in the region of 90 seconds. There's nothing special in this regard about going to SXI - this is how we did it. It's worth noting that AFAICT ISSU requires the linecards to have sufficient RAM to pre-load the new IOS image, and many standard linecards e.g. 6748-SFP/DFC-3B do not, and will therefore not do a "fast" ISSU. It's also relevant that for ISSU the old and new images have to be "compatible" and I have my doubts how often that will be the case... _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ *** NOTICE--The attached communication contains privileged and confidential information. If you are not the intended recipient, DO NOT read, copy, or disseminate this communication. Non-intended recipients are hereby placed on notice that any unauthorized disclosure, duplication, distribution, or taking of any action in reliance on the contents of these materials is expressly prohibited. If you have received this communication in error, please delete this information in its entirety and contact the Amedisys Privacy Hotline at 1-866-518-6684. Also, please immediately notify the sender via e-mail that you have received this communication in error. *** _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
