3750X stack auto vs. manual upgrade

[lcaruso]

Hi,

Are there issues with the auto upgrade feature for 3750X stacks, either historically or currently?

Some people prefer to upgrade switch stacks manually by disconnectiong the stack cables and uprading code on each switch. 

I've done the manual procedure in the past and have not tried the auto upgrade (I have the procedure for the auto upgrade).

What I'm asking is for anyone to share their experience either good or bad with the auto upgrade to assess if this technique is sound.

Thanks.

[Reza Sharifi · Accepted solution]

Hi,

I upgraded 3 stacks of 3750X switches a couple of weeks ago using the .tar file with no issues at all. For a stack of 3 switches, it takes about 45 minutes, so you would need to be patient. Just load the .tar file on the flash of the master switch and run the archive command.

http://www.cisco.com/en/US/products/hw/switches/ps5023/products_configuration_example09186a00804799d7.shtml#maintask1

Good Luck

Reza

[lcaruso]

Thanks for your reply. Hope I won't need any luck.

[Reza Sharifi]

You should be just fine.  The USB port makes life really easy when you have a lots single switches to upgrade.  I have not idea why Cisco didn't add it long time ago while other vendors have been doing it

[Reza Sharifi]

Oh, BTW, the 3750X series switches come with a USB port.  So, no need for ftp, tftp, etc... Just load the IOS you want in to a flash drive and then insert it in to the USB slot. Copy from USB to flash and then run the archive command.

Cisco switches don't like every USB flash, once you insert it if the switch like it, it will let you know.

HTH

[Leo Laohoo · Accepted solution]

I've never heard of this kind of very manual form of IOS upgrade.

I've got about 90+ stacks of 3750/G/E/X in my network and it all boils down to the behaviour of the IOS I want to upgrade.

Let me explain:

I don't remember what IOS version it was but if you run the command "archive download-sw", the IOS won't like it:  CPU will spike and at the end, it will fail.

So I resort to the old method of "archive tar /x" on each stack member.

But if I was given a choice, "archive download-sw" is my preferred way of upgrading switches using the TAR file. 

[lcaruso]

Excellent reply!

I'll be doing the upgrade on

C3750E Software (C3750E-UNIVERSALK9-M), Version 12.2(55)SE1

Is that version anyway close to the version you had problems with?

How do I perform archive tar /x on each member's flash. I've not used that procedure.

Thanks much!

[Reza Sharifi · Accepted solution]

I have never used that command either, but here is step-by-step instructions: You load the file to flash1 for switch1, flash2 for switch2, flash3 for switch 3, etc....

http://www.cisco.com/en/US/products/hw/switches/ps5023/products_configuration_example09186a00804799d7.shtml#mupgrade

HTH

[Leo Laohoo · Accepted solution]

C3750E Software (C3750E-UNIVERSALK9-M), Version 12.2(55)SE1

Good G0d!  Please DO NOT use this.  Try 12.2(55)SE7 instead.

How do I perform archive tar /x on each member's flash. I've not used that procedure.

Take note that I only use this method as a "last resort".

Let's say you have three members in a stack.  So to upgrade the IOS on the first stack member, the command is:  archive tar /x tftp:///filename.tar flash1:

You wait for the entire download to complete and then you change "flash1:" to "flash2:" and so on.

The method "download-sw /destination X" is still superior, in my opinion.

NOTE:  I upgrade the IOS of my 3750 stacks about TWICE a year.  For my 2960S, I upgrade as often as I please.

[lcaruso]

Sorry I meant I was upgrading from that version to the latest SE7.

[Leo Laohoo]

I was upgrading from that version to the latest SE7.

Ok, that's COOL!

[lcaruso]

Now I know why some people prefer the manual method.

The .tar images only have the web based device manager, which we totally avoid for single devices.

The only way to use a .bin image which doesn't have the web manager is to break the stack, upgrade each switch as if it was standalone, then put it back together and use the priority commands to ensure each switch is in the correct order.

[Leo Laohoo · Accepted solution]

The only way to use a .bin image which doesn't have the web manager is to break the stack, upgrade each switch as if it was standalone,

I disagree.  This method of upgrade is very extreme and totally un-necessary.

Ok, so you want to upgrade the BIN file?  It's very, very easy.  Say you have three switches in a stack, so the commands are:

1.  copy tftp:///filename.bin flash1:

2.  copy tftp:///filename.bin flash2:

3.  copy tftp:///filename.bin flash3:

No need to break the stack.  Once the BIN file is copied across all members of the stack, optionally you can verify the MD5 hash, and then you reboot.  Easy!

[lcaruso]

Thanks for your reply. I finally found time to read the entire link that Reza Sharifi provided which says the same thing you mentioned about the manual .bin upgrade. Worked like a charm.

Someone showed me the break the stack method 2 years ago for a 2960S stack, and I had mistakenly been led to believe that was the only way to get it done for the .bin image.

Thanks once again to all that took the time and effort to reply.

[Leo Laohoo]

Thanks for your reply. I finally found time to read the entire link that Reza Sharifi provided which says the same thing you mentioned about the manual .bin upgrade. Worked like a charm.

Try Rolling Stock Upgrade (aka Rolling Stones).  It's alot groovie!

Someone showed me the break the stack method 2 years ago for a 2960S stack, and I had mistakenly been led to believe that was the only way to get it done for the .bin image.

Upgrade of the 2960S is far more simpler than the 3750 family.  The IOS is smart enough to determine how many switches in the stack and you dispense of the need to use the "/destination" option.