Quick question, I'm not sure if this is applicable, but I am having some
confusion of what versions of code to upgrade to, and a call to the TAC
didn't help. All apologies if this is off topic at all.
We are currently running 12.2(8)T5 on several of our 2600 series routers
and according to the advisory, we should upgrade to 12.2(8)T10 to get
the fix. I downloaded 12.2(8)T10, and the date is June 16th. ?? What
gives, that seems really old for a rebuild.
The same thing with 12.2(15)T5, the date is June 25th. Am I downloading
the right code?
I don't want to reboot every router on our network 2 times.
TIA.
Steve Rude
* steve@skyriver.net (Steve Rude) [Fri 18 Jul 2003, 01:08 CEST]:
Quick question, I'm not sure if this is applicable, but I am having some
confusion of what versions of code to upgrade to, and a call to the TAC
didn't help. All apologies if this is off topic at all.
We are currently running 12.2(8)T5 on several of our 2600 series routers
and according to the advisory, we should upgrade to 12.2(8)T10 to get
the fix. I downloaded 12.2(8)T10, and the date is June 16th. ?? What
gives, that seems really old for a rebuild.
Discussion on cisco-nsp (where your question is much more applicable) is
that Cisco has known about this bug for a while and has been building
images before going public, so yeah, that could work.
The same thing with 12.2(15)T5, the date is June 25th. Am I downloading
the right code?
According to the advisory you are.
You write that calling the TAC didn't help. Did you ask them "Does
12.2(15)T5 contain the fix for this bug?" and were they unable to answer
that? That sounds... improbable.
-- Niels.
Quick question, I'm not sure if this is applicable, but I am having some
confusion of what versions of code to upgrade to, and a call to the TAC
didn't help. All apologies if this is off topic at all.
We are currently running 12.2(8)T5 on several of our 2600 series routers
and according to the advisory, we should upgrade to 12.2(8)T10 to get
the fix. I downloaded 12.2(8)T10, and the date is June 16th. ?? What
gives, that seems really old for a rebuild.
For those of you that haven't figured it out yet, this
bug has been around for a long time. They probally found
it and then said "since nothing is going on, we found this
ourselves, we'll code the fix, test it, and then tell everyone
about it."
This means that some of the "CCO Stalkers" that watch
for new software and test/play with it will not have a problem.
Their devices will be in good shape.
The same thing with 12.2(15)T5, the date is June 25th. Am I downloading
the right code?
I'd go off what they say is fixed. it was probally
someones more than full time job to go around to each grou of people
that ever built some weird software train at one time and say "here's
the bugid, you need to provide customers a fix".
I don't want to reboot every router on our network 2 times.
I would contact the TAC to ask any questions you have. Cisco
has been historically kind when this type of thing comes out and gives
software updates out to people that do not have contracts to insure
that they don't have a bad customer experience.
I know the chart is hard to read because the product people
need hardware support for their new thing they're shipping and are
so impatient to ship it that they create these shortlived
software trains that get the new hardware support they need.
- Jared