We are planning to upgrade two of our Catalyst 6500 switches to version 15.1(2)SY1 Advanced IP Services.
The switches have dual supervisors and are currently running version 12.2(33)SXI11, but we have faced some issues and also would also like to enable some new features (e.g. BFD). The switches are running a fairly simple configuration with OSPF, MPLS and MP-BGP with about 30 VRFs.
Are you aware of any major issues with 15.1(2)SY1 and would discourage the planned upgrade? I am aware that the version was only released in December, but since there are many bug fixes I thought this version might be better than e.g. 15.1(2)SY.
In my recent experience, I have gone from try new s/w to why do i need it mode. My question as this a fairly new IOS, what would happen if you do not upgrade to this latest IOS?
What are the risks you are running by staying within 12.2.33 train? Remember, it will be a big jump and you never know if 15.1(2) breaks the things that you have fixed over a period of time.
What if you plan to do this upgrade in next 6 month? What will you loose out by keeping an eye on this train and keep on checking the release notes for patched release as to what other have gone through before you put it on the boxes.
I dont want to sound too conservative but if I were you, I would not upgrade the latest and bleeding edge version on production boxes with prior testing in a lab scenario.
The reason that we want to upgrade is that we have an issue that has caused traffic black holing through the secondary supervisor. TAC has not yet been able to identify the issue, even when we have reproduced the problem. (Currently we have the 10 Gbps uplinks on the secondary seupervisor disabled).
We are currently running the modular version (vz) of the code and we have been advised by TAC that it is not commonly used. Therefore we want to upgrade at least to the "normal" (mz) version. As I mentioned, there are also some interesting features in the 15.1SY that we would like to use, but given your advice we might stick to the 12.2(33) train.
Which version would you recommend when we move to the non-modular version? Stay on 12.2(33)SXI11 or perhaps upgrade to 12.2(33)SXI12 or 12.2(33)SXJ6?
One reason to move to the 15.1 release train may be if the following is true:
December 1, 2013:
The last date that Cisco Engineering may release any final software maintenance releases or bug fixes on 12.2(33)SXJ . After this date, Cisco Engineering will no longer develop, repair, maintain, or test the product software. Support will be on a follow on release in IOS 15.X train.
We replaced all (~ x20) our Sup720 (SXI4a) with Sup2T during late 2012 & running with Advance Enterprise 15.0(1)SY image. We did not have any issues with that code & still many of our distribution switches running on that code.
Then we upgraded two core switches with 15.1(1)SY mid last year another two core switches to 15.1(2)SY late last year to accomodate WS-X6904-40G. With both of these new code we had couple of bugs still not proper fix
CSCue58955: sup2t: LC file systems are not destroyed in Active upon reset
"%SNMP-3-INPUT_QFULL_ERR: Packet dropped
There is workaround for this, but that will impact netflow data if you are using that.
For me 15.0(1)SY, is much better for Enterprise environment (based on my experience) compare to the two latest. But due to certain limitation we have to go for this newer codes whether you like it or not.
These bugs may be not related to you if you are not runing Sup2T, anyway just thought to share this experience
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.