08-27-2008 06:16 PM - edited 03-03-2019 11:18 PM
I upgraded a few 3845's from 12.4(12) to 12.4(15)T5. A few upgrades show that the Gig0/0 interface that has a LX SFP in it does not come up. Regardless if you bounce or reseat. We downgraded the code back to the original and the link comes up. Can't find any bugs, and cases have not proven to be successful. You do see log messages of the GBIC being inserted and removed. I have found some doc on cisco being stricter on the supported SFP's. Has anyone seen similar issues? Even seen this on 3750 switches.
08-28-2008 01:46 AM
Did you try without the "T" (or New Features/Hardware Support)?
If you just need to fix some bugs/vulnerabilities you don't need the "T".
Although the "T" also fix some bugs/vulnerabilities but it added New Features/Hardware Support and this may introduce new bug/vulnerability and/or incompatibility - since it is created by humans.
See this link for more info about migration strategy http://www.cisco.com/warp/public/620/1.html
08-28-2008 05:44 AM
The reason for this upgrade is we have requirements to support new features and hardware that require the T train code. Can anyone find an issue with unsupported SFP's in the T train code where the unsupported SFP's worked in 12.4(12) mainline? The only thing I can find is that in these instances we are using unsupported SFP's.
11-19-2008 09:56 AM
I'm sure you have figured this out by now, however I did come across your post today. And we ran accross this after a 3750 upgrade. We were using 3rd party SFP's and the vendor had coded them with the same serial number. The new image recognized that and they wouldn't work (However they worked fine prior to the upgrade)
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide