So, just to follow up, we had a TAC case open for this. The ISSU method (eFSU) we were using is only supported when staying within the train you're on. See https://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/SX_SY_EFSU_Compatibility_Matrix.xlsx . You'd think IOS would warn you were trying to use a method that wasn't compatible, but it seems to just result in what we saw. It's still a mystery on what method we've got to use to minimize downtime on our upgrade. I assume there is a good documented method for quad sups, and changing major version numbers.
Chuck On Mon, Apr 22, 2019 at 11:21 AM Garrett Skjelstad <[email protected]> wrote: > We had similar issues. The best way we found to correct it was to do > individual module resets just prior to running ISSU. > > After "hw-module reset"-ing all the supers, one at a time, we were able to > ISSU without issue. > > On Mon, Apr 22, 2019, 05:50 Chuck Church <[email protected]> wrote: > >> All, >> >> Ran into an issue with using FSU on a quad-sup 6800 VSS pair with >> Sup6T. We're going from 15.3(1)SY2 to 15.5(1)SY2. It appears after the >> standby sup upgrade starts (after the issu loadversion command is done), a >> 3 minute timer is expiring and causing an automatic abort. From the logs: >> >> Apr 21 2019 05:52:34.856: %ISSU_PROCESS-SW1-6-LOADVERSION_INFO: >> Standby-ICS >> has gone offline, wait for reboot >> >> Apr 21 2019 05:55:34.866: %ISSU_PROCESS-SW1-3-ABORT: Starting abort >> sequence, reason: LOADVERSION: Standby-ICS has not come back online >> >> Now we could see via the console cable that the standby would eventually >> boot up. Due to the version changes there was an FPGA upgrade done and I >> believe a second boot of it. Thus more than the 3 minute timer I'm >> hitting. Anyone seen this before and/or know what to do? >> >> Thanks, >> >> Chuck >> _______________________________________________ >> cisco-nsp mailing list [email protected] >> https://puck.nether.net/mailman/listinfo/cisco-nsp >> archive at http://puck.nether.net/pipermail/cisco-nsp/ >> > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
