[nsp] 12.0(22)S - avoid it

[George Boulescu]

> Unfortunately I heard about 12.0(22)S actually is 12.0(22)ST after I have
> upgraded our core routers to 12.0(22)S, this was intended to solve the
> dCAR on dot1q interfaces bug. A 7576 crashed 14 hours after
> upgrade right in the middle of peak time with output stuck and cbus
> complex on FE interface. We have reverted back to 12.0(21)S3.

We are running a 7507 with 12.0(22)S for 3 weeks, 3 days, 5 hours, 43
minutes now ...
2 full feeds and 5 other sessions with 5 routers in the european IX-es.
1 VIP4-80 w/ 256/64 with a PA-A3-OC3 and a GEIP+.

So far, the only problems we've got were because the GEIP+ has only 64M of
DRAM, wich is really a BIG problem, as the DCEF ussualy crashes and
doesn't come back...

First we didn't wanted to run 12.0(22)S, but it was the only S-whatever
release which worked with our GEIP+. In all other versions as soon as we
enabled any kind of multicast (ospf for example) on the interface, it
goes to line protocol down and stays like that until we remove the cables
and put them back ... strange thing isn't it ? :(


> I am very suprised that Cisco has decided to merge 12.0ST train into S
> train without telling people exactly what they have done since stability
> is supposed to be the top priority for S-train and people upgrade to the
> latest version to avoid known bugs and hoping to improve stability.

Cisco said that the S series will be continued only by 12.0.21Sx
updates... I don't really know if this is for marketing reasons, as 12.2S
probably will soon be available ... (or am I mistaking ?)

-- 

George Boulescu
Senior Network Engineer
RoEduNet Bucharest NOC
CCAI, CCNA