[c-nsp] 7206VXR w/ Process Memory Parity Error

[Reuben Farrelly]

At 09:51 p.m. 27/03/2005, Gert Doering wrote:
>Hi,
>
>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
> > with a "Software forced crash" (Block overrun, corrupted redzone)
> > running 12.2(13)T12.  Have upgraded to 12.2(15)T15 (with TAC blessing)
> > and so far so good.
>
>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.

I would have expected it all revolved around engineers pushing to the 
latest GD release , or failing that, the latest LD for a platform, 
and avoid the ED's unless absolutely necessary.  Although I see 
branch/ED releases such as 12.3(2)XA and 12.3(4)XD shipped in brand 
new routers nearly all the time, so <shrug> to be honest, I really 
can't quite figure out what the thinking behind this all is.

What is cisco's official position on this aspect of software releases?

reuben