I performed an IOS upgrade on my 6513 with redundant 720 sup's. I was under the impression that when I forced a switch to the standby sup using the redundancy force-switchover that it would be seamless. But what really happened is that when it switched over, the whole unit basically reset. So all of the switchport line cards reset. It took about a minute to reset everything
Is that the expected behavior?
Also, when I performed the switch back to the original sup engine, there was no outage, it was seamless. So not sure why that was different.
Both sups were at same IOS level and were running in active/hot sso mode.
I think I might know what happened. The first step to the upgrade procedure is to do a hw-module-reset to the standby sup. Once this happens the standby is running the IOS code and the primary sup is running the older IOS code. I did not check this on mine but I would imagine I would be in a 'cold' state as far as the redundancy goes. So a switchover would take a minute or two. Once I upgraded the original primary they were both running same IOS ver and that second switchover was seamless becuase it was in a 'Hot' state.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.