Uppgrading 3750E stack without interuption

lars.levin · ‎03-20-2009

Is it possible to uppgrade IOS image on a 3750E stack and not restart the entire stack at the same time. What I want is to restart one member at the time and have full functionality at the other members. I got this message "Systems with incompatible software

have been added to the stack" and the switch will not enjoy the stack and do not do any traffic forwarding at the ethernet ports. And I can't administrate the switch by console port.

Laurent Aubert · ‎03-20-2009

Hi,

Hope the following link will help:

http://www.cisco.com/en/US/docs/switches/lan/catalyst3750e_3560e/software/release/12.2_44_se/configuration/guide/swstack.html#wp1189785

Laurent.

lars.levin · ‎03-20-2009

Hi,

Im sorry but I couldn't find anyting useful in that document. The big question is if it is possible to make the switch with never IOS to work whithout disconnect it from the stack.

Laurent Aubert · ‎03-20-2009

I think you have no choice but upgrading all the stack at the same time. Different version in the stack is not supported as the stack protocol version is different.

Use the archive download-sw command from the master:

http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/release/12.2_50_se/command/reference/cli1.html#wp2273183

If you do it from the master, the new software should be automatically copied to all the members of the stack:

http://www.cisco.com/en/US/docs/switches/lan/catalyst3750e_3560e/software/release/12.2_44_se/configuration/guide/swiosfs.html#wp1017927

Then reload all the stack

Laurent.

Leo Laohoo · ‎03-22-2009

Or you can reload one switch member at a time.

hobbe · ‎03-26-2009

As far as I know the general rule for this is NO You can not upgrade the switchstacks this way.

You can reload the different units as you wish, but if the software images are to different (minor vs major release) you will not get them to work in the stack.

That said answering your question we can now look for a workaround.

There might be some solutions that might help you such as reroute traffic using rapid spanning tree to a different stack.

or

you could use ports that are initially shutdown on another stack to reroute the traffic during the time the stack needs to shutdown.

This all depends on how the stack is connected and to what.

good luck