Catalyst C3560-24PS-S - Upgrade path

[uadmin]

Hello,

I'm looking for some direction on upgrading this platform, it is currently on IOS 12.2(35) SE5.

Curious if this requires multiple upgrades and what version I should upgrade to? (I'm assuming 15.X)

Thank you.

[Mark Elsen]

  - @uadmin      Check the release notes of the targeted version you are trying to upgrade too, and
                         look for 'upgrade' with find in the browser (look for info's concerning upgrade paths)
                         Current recommended release :
                             https://software.cisco.com/download/home/282979305/type/280805680/release/15.2.4E10

  M.

[uadmin]

So the link you have posted takes me here:

Only thing I can see that's helpful in this screen are the Release notes, but there is nothing showing upgrade path details or even how to start an upgrade.

From the blue links on the right, I understand I can not download anything without a valid entitlement, is that correct?

[Joseph W. Doherty]

---

@uadmin wrote:

From the blue links on the right, I understand I can not download anything without a valid entitlement, is that correct?

---

Correct.

I believe the 3650 series is end-of-life.  Cisco withdraws EoL software.  So, the "official" upgrade path is newer hardware.

[Leo Laohoo · Accepted solution]

The final firmware for the "classic" 3560 is 12.2(55)SE.

[uadmin]

Ok, how did you determine that? I mean, what document outlines that?

2. Is there any benefit to upgrading from 12.2 to 12.5(55)SE ?

[Leo Laohoo]

---

@uadmin wrote:
Ok, how did you determine that? I mean, what document outlines that?

---

Cisco's official stand is:  3560 has exceeded end-of-life and all files, including firmware, have been removed from public access. 

My alternative response is neither incorrect nor wrong.  If you do not trust my response, it is not my loss.  

---

@uadmin wrote:
Is there any benefit to upgrading from 12.2 to 12.5(55)SE ?

---

Not my call.  Not my decision. 

However, I will say this:  12.2(55)SE train, as well as 15.0(2)SE train, are universally known to be the most stable firmware released (second only to SXI/SXJ).  No other releases can match their stability (both short- and long term).  

[uadmin]

"My alternative response is neither incorrect nor wrong.  If you do not trust my response, it is not my loss."

Never said it was incorrect or wrong but usually this information is written somewhere, like an Inter-operability guide, so it isn't a matter if I trust you or don't trust you, I would like to learn where to obtain this information, unless it has been removed and publicly not found anywhere. 

[Leo Laohoo]

---

@uadmin wrote:
I would like to learn where to obtain this information

---

From Cisco is going to maintain the official stance of "3560 is end-of-life".  

[Joseph W. Doherty]

BTW, note Leo has a typo, he meant 12.2(55)SE, which is seen on the actual referenced page (and as he also correctly uses in his later replies).

A possible point of confusion is the referenced device is a 3560V2, which isn't exactly the same model series as the original 3560/3560G models.  However Leo has noticed/discovered some (all?) of the V2 model's IOSs appear to work in the original 3560 series, and their software is still available (although you still, I believe, need entitled [e.g. maintenance contract] access to download the software).

Understand, I believe Cisco wouldn't suggest this upgrade path, or support any issues arising from using it.  However, the 3560 is already no longer supported, so the only major risk is the newer IOS causes issues you don't currently have.

Also, BTW, usually in Cisco's posted end-of-life/support documentation, they will recommend replacements.

Lastly, it may be worth knowing Leo has years of experience working within a large network using lots of Cisco switches.  I.e. you might consider him a SME (subject matter expert) for your kind of switch questions.

[Leo Laohoo]

---

@Joseph W. Doherty wrote:

note Leo has a typo, he meant 12.2(55)SE

---

Ooopsie!  I have made necessary correction.  Thanks, @Joseph W. Doherty and thanks for the kind words.