Hi I have good experiences with ISSU to upgrade IOS to SRB4 to SRD1 or SRD3. I have made the procedure a few times without problems. The messages about missing ifindex values, IDB failures and other is normal while the procedure. I just found a BUG ID when I some problems while upgrade from IOS SRD3 to SRE version. The workaround for the BUG ID does not work too, the bug will be fixed in IOS SRD4 that will be avaliable in next month. I have a doubt for other people that make this procedure. We need in the begining of the procedure to remove the efsu: no service image-version efsu
Do we need to add again the command "service image-version efsu" ? In the procedure does not show if we need to add again the command line or not. Regards, ________________________________ De: Randy McAnally <[email protected]> Para: Phil Mayers <[email protected]> Cc: "[email protected]" <[email protected]> Enviadas: Sexta-feira, 12 de Fevereiro de 2010 13:41:51 Assunto: Re: [c-nsp] ISSU on SXF -> SXI Thanks for verifying my suspicions... ISSU just seemed 'too good to be true'. RPR mode upgrade it is... -- Randy ---------- Original Message ----------- From: Phil Mayers <[email protected]> To: N/A Cc: "[email protected]" <[email protected]> Sent: Fri, 12 Feb 2010 15:06:36 +0000 Subject: Re: [c-nsp] ISSU on SXF -> SXI > On 12/02/10 14:47, Rob Shakir wrote: > > > > This seems quite accurate to me. > > > > Our experience of ISSU has been terrible. We've found multiple bugs > > related to it, and have found that -- in general -- we're much better > > off in terms of service disruption with a "classic" upgrade (upgrade > > secondary, reload peer, force failover, etc). > > > > Cisco advised us that it is unlikely that ISSU on 7600/6500 will meet > > our requirements, and hence we are better off doing classic upgrades. > > We've taken their advice, and will not be trying it again. I think > > As it happens I just did a "half-test" on one of our boxes where I > did the "issu loadversion" so that I could see what it told me about > outage times - and all kinds of horrific messages started spraying > onto the console about missing ifindex values, IDB failures and so forth. > > I quickly did an "issu abortversion" > > Bah. Thanks a lot Cisco... > > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ ------- End of Original Message ------- _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ____________________________________________________________________________________ Veja quais são os assuntos do momento no Yahoo! +Buscados http://br.maisbuscados.yahoo.com _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
