Mailing List Archive

On Tue, 8 Oct 2002, Basil Kruglov wrote:
> I'm trying to figure out what is the most stable and non buggy IOS today for
> the VXR platform, any ideas?
>
> I do know 12.0.22* isn't going to work well, and 12.0.21S4 which is stable
> but has a nasty bug, what about 12.0.21S or below, which one is the most
> stable ?

We haven't had any issues with 21S1 and 21S2. They have been deferred due
to a couple of major bugs, but those don't affect us.

--
Pekka Savola "Tell me of difficulties surmounted,
Netcore Oy not those you stumble over and fall"
Systems. Networks. Security. -- Robert Jordan: A Crown of Swords

Hello...

I'm running 12.0.22S on two 7206VXRs with no problems. Full BGP feeds
for all.


On Tue, 2002-10-08 at 04:00, Basil Kruglov wrote:
> I'm trying to figure out what is the most stable and non buggy IOS today for
> the VXR platform, any ideas?
>
> I do know 12.0.22* isn't going to work well, and 12.0.21S4 which is stable
> but has a nasty bug, what about 12.0.21S or below, which one is the most
> stable ?
>
> I would appreciate any input, both real life and lab tests results. Thanks,
>
> -Basil
> _______________________________________________
> 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/
--
Christopher McCrory
"The guy that keeps the servers running"

chrismcc@pricegrabber.com
http://www.pricegrabber.com

Let's face it, there's no Hollow Earth, no robots, and
no 'mute rays.' And even if there were, waxed paper is
no defense. I tried it. Only tinfoil works.

We have had good luck with 12.0(21)ST2 on some 7206s that we are running
(NPE300, NPE400, and NSE1). We have a good mix of Pas (ATM, FE, MCT3)
and are running full BGP and MPLS VPNs with no trouble so far.

Good luck,
Chad


-------------------------
Chad Skidmore
One Eighty Networks, Inc.
http://www.go180.net
509-688-8180


> -----Original Message-----
> From: Basil Kruglov [mailto:basil@cifnet.com]
> Posted At: Tuesday, October 08, 2002 4:01 AM
> Posted To: Cisco List
> Conversation: [nsp] IOS 12.0 S-train for VXR
> Subject: [nsp] IOS 12.0 S-train for VXR
>
>
> I'm trying to figure out what is the most stable and non
> buggy IOS today for the VXR platform, any ideas?
>
> I do know 12.0.22* isn't going to work well, and 12.0.21S4
> which is stable but has a nasty bug, what about 12.0.21S or
> below, which one is the most stable ?
>
> I would appreciate any input, both real life and lab tests
> results. Thanks,
>
> -Basil
> _______________________________________________
> 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/
>

Hi,

On Tue, Oct 08, 2002 at 02:36:52PM +0300, Pekka Savola wrote:
> We haven't had any issues with 21S1 and 21S2. They have been deferred due
> to a couple of major bugs, but those don't affect us.

21S1 works fine for me.

21S2 has issues with PA-E3/PA-T3s.

21S3 has broken interface counters.

gert
--
Gert Doering
Mobile communications ... right now writing from * Burgkirchen / Gendorf *

I have to say that 12.1 mainline, and 12.2T have been working quite well
for us on 7200 [VXR]s, with NSE-1's and NPE-300's.

The 7200's we have are generally swiss-army knife (IPv4, BGP, OSPF, EIGRP,
ISIS, PPPOE, PPP, HDLC, ATM, FR, CT3, CEF, CAR, Radius, TACACS) -- one or
two of ours do all of the above on a single box. The most loaded on has
about 250 ATM PVC's, 150 PPPOE sessions, and moves about 20 mbit/sec (not
lots of traffic, I know).

cust1.nwr>sho proc c
CPU utilization for five seconds: 13%/12%; one minute: 23%; five minutes: 25%

He is also a route-reflector client with 4 or 5 eBGP feeds.



On Tue, 8 Oct 2002, Pekka Savola wrote:

> On Tue, 8 Oct 2002, Basil Kruglov wrote:
> > I'm trying to figure out what is the most stable and non buggy IOS today for
> > the VXR platform, any ideas?
> >
> > I do know 12.0.22* isn't going to work well, and 12.0.21S4 which is stable
> > but has a nasty bug, what about 12.0.21S or below, which one is the most
> > stable ?
>
> We haven't had any issues with 21S1 and 21S2. They have been deferred due
> to a couple of major bugs, but those don't affect us.
>
> --
> Pekka Savola "Tell me of difficulties surmounted,
> Netcore Oy not those you stumble over and fall"
> Systems. Networks. Security. -- Robert Jordan: A Crown of Swords
>
> _______________________________________________
> 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/
>

-- Alex Rubenstein, AR97, K2AHR, alex@nac.net, latency, Al Reuben --
-- Net Access Corporation, 800-NET-ME-36, http://www.nac.net --

On Tue, Oct 08, 2002 at 04:52:49PM +0200, Gert Doering wrote:
> Hi,
>
> On Tue, Oct 08, 2002 at 02:36:52PM +0300, Pekka Savola wrote:
> > We haven't had any issues with 21S1 and 21S2. They have been deferred due
> > to a couple of major bugs, but those don't affect us.
>
> 21S1 works fine for me.
>
> 21S2 has issues with PA-E3/PA-T3s.

Gert, do you have the bugid for this? This was on the 7500 only
from what i understand.

> 21S3 has broken interface counters.

Someone mentioned they had problems with 22S and 22S1, what
did they see? I've run 22S S1 and later on 7200s with no problems
that i've noticed.. (although i'm not closely watching snmp data for
example).

- jared

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

Hi,

On Tue, Oct 08, 2002 at 12:37:55PM -0400, Jared Mauch wrote:
> > 21S2 has issues with PA-E3/PA-T3s.
>
> Gert, do you have the bugid for this? This was on the 7500 only
> from what i understand.

I have no bugid, and I haven't seen this myself (sorry).

I didn't test this image at all, as a colleague told me that he had an E3
not coming up at all with this IOS version on his 7200. So it is not only
a 7500.

It's definitely fixed in 21S3 (or S4?) - I tried a later image, and my
E3s came up just fine, just the interface counters stopped working.

> > 21S3 has broken interface counters.
>
> Someone mentioned they had problems with 22S and 22S1, what
> did they see? I've run 22S S1 and later on 7200s with no problems
> that i've noticed.. (although i'm not closely watching snmp data for
> example).

Could you do a rough check of "show int" counters vs. "5 minute
average"? Like "it's showing 5000 packets per second, and after
10 seconds, the output packet counter indeed goes up by 50.000"? The
problems in 21S3 have been *very* obvious.

thanks,

gert

--
Gert Doering
Mobile communications ... right now writing from * a train back to Munich *

On Tue, 2002-10-08 at 11:37, Jared Mauch wrote:
> On Tue, Oct 08, 2002 at 04:52:49PM +0200, Gert Doering wrote:
> > Hi,
> >
> > On Tue, Oct 08, 2002 at 02:36:52PM +0300, Pekka Savola wrote:
> > > We haven't had any issues with 21S1 and 21S2. They have been deferred due
> > > to a couple of major bugs, but those don't affect us.
> >
> > 21S1 works fine for me.
> >
> > 21S2 has issues with PA-E3/PA-T3s.
>
> Gert, do you have the bugid for this? This was on the 7500 only
> from what i understand.
>
> > 21S3 has broken interface counters.
>
> Someone mentioned they had problems with 22S and 22S1, what
> did they see? I've run 22S S1 and later on 7200s with no problems
> that i've noticed.. (although i'm not closely watching snmp data for
> example).
22S has issues on VIP-based interfaces on 75xx.

I can't get any good info from show int, but MRTG does show the info via
SNMP.

According to contacts at TAC it is NOT fixed in 22S1.

LER

--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: ler@lerctr.org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749

> Someone mentioned they had problems with 22S and 22S1, what
> did they see? I've run 22S S1 and later on 7200s with no problems
> that i've noticed.. (although i'm not closely watching snmp data for
> example).

We had 7500 fail to boot due to process stack exhaustion, both 22S and 22S1.
The problem was identified and patched, we run special build of 21S with
this specific fix successfully for 3 days now. Bug ID is CSCdx87818.

SY,
--
CCNP, CCDP (R&S) Dmitri E. Kalintsev
CDPlayer@irc Network Architect @ connect.com.au
dek @ connect.com.au phone: +61 3 8687 5954 fax: 8414 3115
http://-UNAVAIL- UIN:7150410 cell: +61 414 821 382

On Tue, Oct 08, 2002 at 08:58:38PM +0200, Gert Doering wrote:
> Hi,
>
> On Tue, Oct 08, 2002 at 12:37:55PM -0400, Jared Mauch wrote:
> > > 21S2 has issues with PA-E3/PA-T3s.
> >
> > Gert, do you have the bugid for this? This was on the 7500 only
> > from what i understand.
>
> I have no bugid, and I haven't seen this myself (sorry).
>
> I didn't test this image at all, as a colleague told me that he had an E3
> not coming up at all with this IOS version on his 7200. So it is not only
> a 7500.
>
> It's definitely fixed in 21S3 (or S4?) - I tried a later image, and my
> E3s came up just fine, just the interface counters stopped working.

CSCin13850

> > > 21S3 has broken interface counters.
> >
> > Someone mentioned they had problems with 22S and 22S1, what
> > did they see? I've run 22S S1 and later on 7200s with no problems
> > that i've noticed.. (although i'm not closely watching snmp data for
> > example).
>
> Could you do a rough check of "show int" counters vs. "5 minute
> average"? Like "it's showing 5000 packets per second, and after
> 10 seconds, the output packet counter indeed goes up by 50.000"? The
> problems in 21S3 have been *very* obvious.

- Jared

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