[c-nsp] 7206VXR w/ Process Memory Parity Error
Jeff Kell
jeff-kell at utc.edu
Sun Mar 27 14:44:32 EST 2005
Reuben Farrelly wrote:
> At 09:51 p.m. 27/03/2005, Gert Doering wrote:
>>On Sat, Mar 26, 2005 at 11:11:55PM -0500, Jeff Kell wrote:
>>>I have a 7204VXR/NPE-300 that crashed three times in the last six weeks
>>>running 12.2(13)T12. Have upgraded to 12.2(15)T15 (with TAC blessing)
>>
>>I wonder why TAC recommended 12.2(15)T15 instead of going to 12.3(12) -
>>which should have many more bugfixes, and few new bugs...
>
> This seems to happen regularly, I too have seen other engineers
> recommended things by the TAC, like recently upgrade to 12.3(5a) when
> 12.3(5d) with some serious defects fixed, or even 12.3(11) was
> out. Occasionally I've even seen deferred releases being
> recommended. The mind boggles.
In production, it is an entirely different "leap of faith" to change a
release level (12.2 => 12.3) and a whole sea of possible problems that
could be introduced with "new" code/features. In my case, it was just
upgrading to the latest version of 12.2T without changing any other
variables.
Jeff
More information about the cisco-nsp
mailing list