Mailing List Archive

We're running 12.0(19)S2/S3 on our 7500s and 7206s without problems.

On the 12000s, basic IP routing (no ACLs) on 12.0(19)SX was pretty good. We're
having a lot of line card crashes and tag switching problems with 12.0(21)S2/3.
Mainly on the Engine 2, E3, and E4+ line cards.

12.0(22)S has a lot of new features from the ST series. I would recommend
caution and wait for 22S1 or 22S2.

http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/relnote/7000fam/rn120s.htm

On Wed, Jul 24, 2002 at 08:39:38AM -0700, Steven W. Raymond wrote:
> Have heard about generally good results from 12.0(21)Sx. Cisco seems to
> have recently introduced 12.0(22)S and one of the main selling points is
> improved route processor backup failover durations. I also note that
> the RSP16 and VIP6-80s seem to first be supported with 12.0(22)S.
> While all these new features may be neat, am more interested in
> demonstrated stability than features.
> Can anyone with experience with either offer their opinions of the code?
> Thank you
> _______________________________________________
> cisco-nsp mailing list real_name)s@puck.nether.net
> http://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/

--
=========================================================================
Clinton Work clinton@scripty.com
Calgary, Alberta

I am using 12.0(21)S3 with great success on 75xx 72xx and gsr
based routers.

Also, beware of the merge and possibly related problems.

Even our ANS engineer did not understand that
12.0(21)S3 != 12.0(22)S as far as bgp goes. 22S has bgp_reorg
where 12.0(21)Sx has the 'legacy' BGP support.

- jared

On Wed, Jul 24, 2002 at 11:04:32AM -0600, Clinton Work wrote:
>
> We're running 12.0(19)S2/S3 on our 7500s and 7206s without problems.
>
> On the 12000s, basic IP routing (no ACLs) on 12.0(19)SX was pretty good. We're
> having a lot of line card crashes and tag switching problems with 12.0(21)S2/3.
> Mainly on the Engine 2, E3, and E4+ line cards.
>
> 12.0(22)S has a lot of new features from the ST series. I would recommend
> caution and wait for 22S1 or 22S2.
>
> http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/relnote/7000fam/rn120s.htm
>
> On Wed, Jul 24, 2002 at 08:39:38AM -0700, Steven W. Raymond wrote:
> > Have heard about generally good results from 12.0(21)Sx. Cisco seems to
> > have recently introduced 12.0(22)S and one of the main selling points is
> > improved route processor backup failover durations. I also note that
> > the RSP16 and VIP6-80s seem to first be supported with 12.0(22)S.
> > While all these new features may be neat, am more interested in
> > demonstrated stability than features.
> > Can anyone with experience with either offer their opinions of the code?
> > Thank you
> > _______________________________________________
> > cisco-nsp mailing list real_name)s@puck.nether.net
> > http://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
>
> --
> =========================================================================
> Clinton Work clinton@scripty.com
> Calgary, Alberta
> _______________________________________________
> cisco-nsp mailing list real_name)s@puck.nether.net
> http://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/

--
Jared Mauch | pgp key available via finger from jared@puck.nether.net
clue++; | http://puck.nether.net/~jared/ My statements are only mine.

Jared Mauch wrote:
>
> I am using 12.0(21)S3 with great success on 75xx 72xx and gsr
> based routers.

Excellent. That's what I wanted to hear.

> Also, beware of the merge and possibly related problems.

Er, you mean the S & ST train merge? Besides that listed below, any
other big gotchas?

>
> Even our ANS engineer did not understand that
> 12.0(21)S3 != 12.0(22)S as far as bgp goes. 22S has bgp_reorg
> where 12.0(21)Sx has the 'legacy' BGP support.
>
> - jared

Thanks for the input!

> I am using 12.0(21)S3 with great success on 75xx 72xx and gsr
> based routers.

We're using 12.0(21)S3 with success on most of our 7500s, but we have
one 7507 where a PA-E3 (on a VIP4-50) stopped working when we tried to
to upgrade from 12.0(19)S2 to 12.0(21)S3. Had to revert to 12.0(19)S2.

Steinar Haug, Nethelp consulting, sthaug@nethelp.no

Hi,

On Wed, Jul 24, 2002 at 08:13:48PM +0200, sthaug@nethelp.no wrote:
> > I am using 12.0(21)S3 with great success on 75xx 72xx and gsr
> > based routers.
>
> We're using 12.0(21)S3 with success on most of our 7500s, but we have
> one 7507 where a PA-E3 (on a VIP4-50) stopped working when we tried to
> to upgrade from 12.0(19)S2 to 12.0(21)S3. Had to revert to 12.0(19)S2.

I can second this - this happened to a colleague (who is not (yet)
subscribed to this list) as well. 7500 with VIP2-40, PA-E3, stopped
working in 12.0(21)S3.

I have no further details what variant of "not working" was observed.

Correlating this with CSCin01252 - "Microcode fix for PA-E3", integrated
in 12.0(21.3)S - I see a certain connection, though...

gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany gert@greenie.muc.de
fax: +49-89-35655025 gert.doering@physik.tu-muenchen.de

> > We're using 12.0(21)S3 with success on most of our 7500s, but we have
> > one 7507 where a PA-E3 (on a VIP4-50) stopped working when we tried to
> > to upgrade from 12.0(19)S2 to 12.0(21)S3. Had to revert to 12.0(19)S2.
>
> I can second this - this happened to a colleague (who is not (yet)
> subscribed to this list) as well. 7500 with VIP2-40, PA-E3, stopped
> working in 12.0(21)S3.
>
> I have no further details what variant of "not working" was observed.

In our case: Input errors (frame, abort), line protocol never comes up.

Steinar Haug, Nethelp consulting, sthaug@nethelp.no

> > We're using 12.0(21)S3 with success on most of our 7500s, but we have
> > one 7507 where a PA-E3 (on a VIP4-50) stopped working when we tried to
> > to upgrade from 12.0(19)S2 to 12.0(21)S3. Had to revert to 12.0(19)S2.
>
> I can second this - this happened to a colleague (who is not (yet)
> subscribed to this list) as well. 7500 with VIP2-40, PA-E3, stopped
> working in 12.0(21)S3.
>
> I have no further details what variant of "not working" was observed.
>
> Correlating this with CSCin01252 - "Microcode fix for PA-E3", integrated
> in 12.0(21.3)S - I see a certain connection, though...

CSCin13850 looks like a closer fit to my problem. It is supposedly
resolved, but no info on which version.

Steinar Haug, Nethelp consulting, sthaug@nethelp.no