Switching

Cisco stack: version mismatch

René Jorissen on December 15, 2010 5 Comments • Tags: #archive #cisco #copy-sw #mismatch #stack #version

When adding a new switch to an existing stack, the new switch should have the same software image as the existing stack member switches. If the new switch has different software, the switch isn’t capable of joining the stack.

Switch/Stack Mac Address : 588d.0918.3100
H/W   Current
Switch#  Role   Mac Address     Priority Version  State
———————————————————-
*1       Master 588d.0918.3100     15     1       Ready
2       Member c471.fe99.b580     1      2       Version Mismatch

There are different ways to upgrade the new switch to the correct software image. The hard way is unplugging the new switch from the stack, upgrade the switch separately and add the switch to the stack again. A more easy way is using the archive copy-sw command. This command allows you to copy the software from a specific member switch to the new switch.

The example below copies the software from switch 1 to the destiniation switch 2.

sw-stack#archive copy-sw /destination-system 2 1
System software to be uploaded:
System Type:             0x00000002
archiving c3750e-universalk9-mz.122-53.SE2 (directory)
Stacking Version Number: 1.43

System Type:             0x00000002
Ios Image File Size:   0x00DA7200
Total Image File Size: 0x01076600
Minimum Dram required: 0x08000000
Image Suffix:          universalk9-122-53.SE2
Image Directory:       c3750e-universalk9-mz.122-53.SE2
Image Name:            c3750e-universalk9-mz.122-53.SE2.bin
Image Feature:         IP|LAYER_3|PLUS|SSH|3DES|MIN_DRAM_MEG=128

Old image for switch 2: flash2:/c3750e-universalk9-mz.122-53.SE1
Old image will be deleted after download.

Extracting images from archive into flash on switch 2…

Installing (renaming): `flash2:/update/c3750e-universalk9-mz.122-53.SE2′ –> flash2:/c3750e-universalk9-mz.122-53.SE2′
New software image installed in flash2:/c3750e-universalk9-mz.122-53.SE2
Removing old image: flash2:/c3750e-universalk9-mz.122-53.SE

All software images installed.

sw-stack#reload slot 2

This is by far the easiest way to upgrade the new switch to the correct software image. Another method is using the copy command.

sw-stack#copy image-file.bin flash2:

sw-stack#config t

sw-stack(config)#boot system switch 2 flash:/image-file.bin

sw-stack(config)#exit

sw-stack#wr mem

sw-stack#reload slot 2

This method is very useful if you are using an image without the html web features.

The following two tabs change content below.

René Jorissen

Co-owner and Solution Specialist at 4IP Solutions
René Jorissen works as Solution Specialist for 4IP in the Netherlands. Network Infrastructures are the primary focus. René works with equipment of multiple vendors, like Cisco, Aruba Networks, FortiNet, HP Networking, Juniper Networks, RSA SecurID, AeroHive, Microsoft and many more. René is Aruba Certified Edge Expert (ACEX #26), Aruba Certified Mobility Expert (ACMX #438), Aruba Certified ClearPass Expert (ACCX #725), Aruba Certified Design Expert (ACDX #760), CCNP R&S, FCNSP and Certified Ethical Hacker (CEF) certified. You can follow René on Twitter and LinkedIn.

Latest posts by René Jorissen (see all)

  1. Sainath says:

    This didn’t work for me with both methods. Are there any limitations to these methods? I tried with a 2960x switch stack.

  2. Mike T. says:

    Same here with 2960X stack. Neither method worked. I could copy the file to the destination switch, but when it would reload, it booted from the original boot file and not the newest image file like I had told it to boot from. I ended up disconnecting the switch from the stack and issuing the “boot system…” command and reloading. Has to be something different with this command.

  3. Ryan R says:

    If a switch is in a mismatch state, you can’t execute file copy to it from the good switch. Your best bet is a flash drive then copy flash:/filename usbflash0: (note if you type “dir all” you will see the filesystem name of the USB drive). Next, console into the mismatch switch and copy the image back to its flash, issue the “boot system flash:/imagename command and reload the switch. It will come back up as soon as its done rebooting. Be patient, if there is a microcode update it will take up to 15 minutes for the switch to come back online.

  4. Alan says:

    It worked great for me! I had no problem copying the image from the stack master to the new switch that was in version mismatch. Previously I would upgrade the IOS on a switch located in Mexico from a TFTP server in the US and that was misery. It was necessary to console to the new switch and edit the boot system.

  5. Patrick Paalman says:

    GVD handig.. had net een 9300 stack met dit issue :)

Leave a comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.