Cisco 2960x ios versions

[edmar99]

Hello every,

I'm new to this so forgive if this is a stupid question. We have a couple of cisco 2960x in production and we need to add a new switch from the stack. The switches that are stacked right now are:

Switch Ports Model SW Version SW Image
------ ----- ----- ---------- ----------
* 1 52 WS-C2960X-48FPD-L 15.0(2)EX5 C2960X-UNIVERSALK9-M
  2 52 WS-C2960X-48FPD-L 15.0(2)EX5 C2960X-UNIVERSALK9-M

Our new switch has: 

Switch Ports Model SW Version SW Image
------ ----- ----- ---------- ----------
* 1 52 WS-C2960X-48FPD-L 15.2(2)E6 C2960X-UNIVERSALK9-M

Can I grab the image off the flash from the switches that are in production and use it to copy it over to my new switch so the ios images match when I proceed to stack our new switch?

Thanks in advance!

[Leo Laohoo]

---

@edmar99 wrote:

Can I grab the image off the flash from the switches that are in production and use it to copy it over to my new switch so the ios images match when I proceed to stack our new switch?

---

Yes and no.  

Yes, it can be done but it's not easy.  

Before going down this journey, kindly make sure that by doing so won't render the new unit to a state where it'll make things worst.  

Read the Release Notes of the version the new unit will be going to.  Pay close attention to whether or not the new unit, particularly the specific model, is even supported in EX5.

Don't forget/ignore to read the entire list of OPEN Caveats and see if these known bugs (and security vulnerabilities) apply to your network or not.  

Just be aware that the "EX" range is an interim version of IOS.  It is not and was never meant to be used in long-term production run. 

[edmar99]

Hi Leo,

Thanks for your help! So would you suggest copying the ios image from the new switch and upgrade the image on our old switches using the "EX"ios version? I copied the c2960x-universalk9-mz.152-2.E6.bin file on to a tftp server. Can I use this image on our old switches?

Switch#dir flash:c2960x-universalk9-mz.152-2.E6
Directory of flash:/c2960x-universalk9-mz.152-2.E6/

3 -rwx 786 Jul 24 2017 18:20:11 +00:00 info
4 -rwx 21279744 Jul 24 2017 18:20:11 +00:00 c2960x-universalk9-mz.152-2.E6.bin
5 drwx 6144 Jul 24 2017 18:27:30 +00:00 html

122185728 bytes total (95052800 bytes free)

[Leo Laohoo]

---

@edmar99 wrote:

So would you suggest copying the ios image from the new switch and upgrade the image on our old switches using the "EX"ios version? I copied the c2960x-universalk9-mz.152-2.E6.bin file on to a tftp server. Can I use this image on our old switches? 

---

Personally, I would never use or recommend anyone to use this method, ie copy the BIN file from one switch and into another switch.  Only people who don't have a valid Service Contract (to download the IOS from the Cisco website) will resort to this method.  

The reason is because there is no darn way to check whether or not the file is corrupt or not.  During the copy process (from the switch or to the switch) is an absence of verifying.  

If one got the TAR file and then the operator use the "archive download-sw" automated script, this process will tell anyone that the file has been unpacked to the target switch and a quick verification was done to ensure everything is OK.  

[edmar99]

I see... So we'll have get the tar file. I don't have a Service Contract account because we bought our switch from a third party vendor (not cisco). I'm assuming we'll have to contact our vendor to see if they can get the .tar file for us. We'll probably need to get the c2960x-universalk9-mz.152-2.E6.tar file and upgrade our old switches, then add our new switch to the stack. Does that sound right? I'm assuming the cisco 2960x models are all compatible with the "EX" version.

[Leo Laohoo · Accepted solution]

---

@edmar99 wrote:

We'll probably need to get the c2960x-universalk9-mz.152-2.E6.tar file and upgrade our old switches, then add our new switch to the stack. 

---

Errr ... No.  If you want to run 15.2(2)E6, then the entire stack will also need to be upgraded. 

If the new switch is running 15.2(2)E6 and the existing stack is running a totally different IOS version, then the new switch will not be able to join the stack.  The existing stack will simply refuse to let the new stack join and the new switch will be running in stand-alone.  

Another thing, remember to POWER OFF the new switch before connecting the stacking cable.  If the new switch has power and even a single stacking cable gets connected, the entire stack will reboot.  This behaviour is not a bug but is as designed.

[edmar99 · Accepted solution]

Okay thanks!.. Just to summarize what I'll have to do:

1. Get the15.2(2)E6.tar file from vendor (this is the iOS version the new switch is running on).

2. Upgrade the stack's iOS from 15.0(2)EX5 to15.2(2)E6 so the stack matches the new switch's iOS.

3. After the switches are running the same iOS versions, power off the new switch.

4. Connect the stacking cable.

5. Power on the new switch and it should join the stack.

Does that sound right?

And again thanks a lot for your help! You've been extremely helpful.

[Leo Laohoo · Accepted solution]

Yes, that is the correct procedure.