3750G mixed stacking software upgrade

[networkexpert8469394]

We have below mentioned stack switch is in production with mix of ipbase and ipservice and am planning to upgrade it from 12.2(44) to 12.2(55). In this case please let me know which is the best practice to upgrade the stack without outage or with minimal impact. Do i need to upgrade the master first which is having "IPSERVICESK9-M" or i should upgrade the Member which running "IPBASEK9" for testing

Switch Ports Model SW Version SW Image
------ ----- ----- ---------- ----------
* 1 52 WS-C3750G-48TS 12.2(44)SE2 C3750-IPSERVICESK9-M
2 52 WS-C3750G-48TS 12.2(44)SE2 C3750-IPSERVICESK9-M
3 12 WS-C3750G-12S 12.2(44)SE2 C3750-IPBASEK9-M
4 12 WS-C3750G-12S 12.2(44)SE2 C3750-IPBASEK9-M
5 28 WS-C3750G-24PS 12.2(44)SE2 C3750-IPBASEK9-M

[Reza Sharifi]

Hi,

You would need to upgrade the whole stack from the master switch. Once you load the IOS to all switches(follow the link), you would need to reload the whole stack. The impact will be the time that it takes for the stack to reload, therefore this should be done in a maintenance window.

https://www.cisco.com/c/en/us/support/docs/switches/catalyst-3750-series-switches/64898-upgrade-3750-stack.html

HTH

[Leo Laohoo]

HOW, exactly, are you planning to do the upload?
Will you be copying the BIN file across or use the TAR file?

[networkexpert8469394]

Hi Leo, 

As we are going to use two IPSERVICES in C3750G-48TS and IPBASE in remaining switches (C3750G-12S & C3750G-24PS), i would like to know do need to proceed upgrade with WS-C3750G-48TS (Master) or any other member to check is this upgrade working fine or not. Because the switch is responding very slow and its taking long time to login as well.

* 1 52 WS-C3750G-48TS 12.2(44)SE2 C3750-IPSERVICESK9-M
2 52 WS-C3750G-48TS 12.2(44)SE2 C3750-IPSERVICESK9-M
3 12 WS-C3750G-12S 12.2(44)SE2 C3750-IPBASEK9-M
4 12 WS-C3750G-12S 12.2(44)SE2 C3750-IPBASEK9-M
5 28 WS-C3750G-24PS 12.2(44)SE2 C3750-IPBASEK9-M

[Joseph W. Doherty]

It cannot be done without some outage, as the switches will need to boot into the new code.

As to having a minimal impact, that would be having the correct IOS on all switches and reload the stack (and hope there are no problems).

You don't really want to mix IOS versions (okay to mix feature sets - as you have now) in the stack. I.e. don't try to test updating an individual member unit and rebooting it alone.

Your choices are to load the same image on all the switches, and then update those that need to be different (i.e. the different feature set), or individually load each switch member with the correct (i.e. feature set) image to begin with.

If the conversion from (44) to (55) doesn't require any firmware upgrades (I don't recall that it would, but check the release notes), actual outage time, barring any issues, should be about the normal reload time for the whole stack (somewhere in the 5 to 10 minute ballpark?).

[networkexpert8469394]

Hi Joseph,

Thank you so much for suggestion. I need small clarification on the upgrade part.

As per the plan i will be uploading the software based on the current service set as per the current setup ( 2 IPService + 3 IPBase) and finally have to reload the complete stack at same time. We should not reboot the individual switches right.

[Joseph W. Doherty]

Correct, you should reboot the stack as a stack.