12-29-2012 12:32 PM - edited 03-07-2019 10:49 AM
Hello,
It seems my 2960s and 3560s switches have enough flash space and memory to support the 15.0 IOS shoudl I be ok to jump to this from 12.2(35)?
Thanks
12-29-2012 02:39 PM
Upgrade to 12.2(55)SE6 instead. Avoid 12.2(58)SE and 15.0(1)SE because of un-resolved CPU bugs. Avoid 15.0(2)SE as well.
12-30-2012 08:25 AM
Which CPU bugs are you referring to exactly? Because I upgraded a 2960S last week to 15.0.2-SE and it wouldn't boot anymore (Unexpected exception to CPUvector 2000). I RMA'ed the unit, the new one had no problems with the iOS 15 firmware.
12-30-2012 09:40 AM
Took the plunge and upgraded the 2 x 2960s and 2x 3560s to 15.0.2-SE and all seems good.
12-30-2012 02:12 PM
I believe CPU vector 2000 is a hardware issue.
The 15.0(2)SE1 is scheduled for release December 2012 but I think it's been pushed back.
Took the plunge and upgraded the 2 x 2960s and 2x 3560s to 15.0.2-SE
Try doing a TDR. You'll get a surprise.
(Heck, I've even posted the TDR bug on my blog.)
12-30-2012 03:11 PM
What run the copper test on either model of switch?
12-30-2012 03:17 PM
5, 10 and 20 metres.
12-31-2012 07:15 AM
What is the exact syntax for that?
12-31-2012 03:05 PM
Which bit? To run a TDR?
1. Command: test cable tdr interface
2. Depending on the switch model, wait for 5 to 7 seconds (3560, 4500 and 6500 takes 60 seconds); and
3. Command: sh cable tdr interface
01-07-2013 12:53 AM
Hi,
I ran the test cable tdr interface fa 0/1 on a trunk link and all was fine, this was on a 2960. The CPU didn't flat line, did I do something wrong? Or is it a hit and miss bug?
Thanks
01-07-2013 01:45 AM
Hi Andy,
Do a "sh interface Fa0/1" (TIP: Look at the status of your protocol) and/or "sh interface status". Look what stands out.
Next, try a different length of cable. Compare the the results. Those are the bugs that we've so far found.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: