What breaks in an upgrade to 12.2(55)?

[deanwebb]

General question, looking for any Cisco features that break or have a significant change between a particular IOS version and 12.2(55). We've got some old gear out there and I want to know if insisting on an upgrade to 12.2(55) for it will introduce any nasty gotchas that are known to you all. I know that there can be the problem of having to wait for the outage window, but that's not a technical issue. Just want to check on what happens when we say "All you switches... go to 12.2(55)! MOVE! GOGOGOGO! DOO EET NAO!"

[wintermute000]

12.2.55 was one of the go to IOSes for 3750s in my old MSP as it was one of the last ones available on the 12.x train.

the other 'gold' standard was 12.2.58SE.

IIRC 12.2.55 actually is newer in terms of the last released IOS. BUt 12.2.58 is a newer more feature rich train.

Just for the the v15 upgrade, but factor in the 45 minute ASIC reprogramming (do not pull the power unless you want a brick)

[deanwebb]

I know IOS 15 is the scary one, but I'm pretty sure that 12.2.55 is a smooth upgrade, esp. from 12.2.35.

[wintermute000]

I know IOS 15 is the scary one, but I'm pretty sure that 12.2.55 is a smooth upgrade, esp. from 12.2.35.

I wouldn't give it a second thought beyond skimming the readme if going from 12.2 to another 12.2

[icecream-guy]

12.2(55) is the gold standard for the 12.x train.
12.2(58) was buggy as hell when it came out. I don't know if they fixed it but I still stay away.

one issues when moving the 12.2(55) with tacacs configured, takes about 1-2 minutes for the switch to come up and the tacacs stuff to load before you can even log into the switch (even with a local account).

15.x the licensing all changed from 12.2 to 15.x, Cisco was more forgiving in the 12.2 code, you if you were taking advantage of the forgiving nature, say running a BGP image on a base licensed switch, when you upgrade to 15.x you will lose that feature if you don't have a license installed, you'll have to get a temp license from Cisco and pony up for the new license to continue to run BGP.  and the device is EOL you are SOL

Most people I know are just staying on 12.2 until they units go EOL. which most of the 3560 & 3750 switches are already

[mlan]

I agree with all the comments so far, and still have a large deployment of 3560/3750 running 12.2(55).  I also do not remember any showstopper breakage or bug when upgrading from previous 12.x versions.

[shortstop20]

We have ~700 switches on campus. 2960G, 2960S, 3560G, 3560E, 3750E, 3750X, 3850.

My experience has been that 12.2(55) is a solid release.

15.0 is good for SOME models, like 2960S and 3750X.

15.0 locked us out of SSH on several of our 2960G, memory leak. 

[config t]

We have ~700 switches on campus. 2960G, 2960S, 3560G, 3560E, 3750E, 3750X, 3850.

My experience has been that 12.2(55) is a solid release.

15.0 is good for SOME models, like 2960S and 3750X.

15.0 locked us out of SSH on several of our 2960G, memory leak. 

And I thought I was hot stuff when I was administering a campus of 300+ devices..

[deanwebb]

We have ~700 switches on campus. 2960G, 2960S, 3560G, 3560E, 3750E, 3750X, 3850.

My experience has been that 12.2(55) is a solid release.

15.0 is good for SOME models, like 2960S and 3750X.

15.0 locked us out of SSH on several of our 2960G, memory leak. 

And I thought I was hot stuff when I was administering a campus of 300+ devices..

We have 4500 switches, globally, and rising as we phase out a previous vendor's NoOps control of our network.