Article View: comp.dcom.sys.cisco
Article #799.0(1) stability
From: Tom_Karolyshyn
Date: Tue, 04 Aug 1992 14:15
Date: Tue, 04 Aug 1992 14:15
75 lines
3158 bytes
3158 bytes
X-Ceo_Options: Document CEO document contents: > > Cc: cisco@spot.colorado.edu > Subject: Re: 9.0(1) ARP corruption? > In-Reply-To: vsg%tron!plaza.dnet@uunet.UU.NET's message of 17 Jul 92 > Date: Mon, 20 Jul 92 11:33:48 PDT > From: Paul Traina <pst@cisco.com> > > I know about this bug, it's CSCdi05156. I have a fix, but we've been > somewhat concerned about it being destabilizing (basicly, I got fed up > with all of the stupid arp bugs and sat down and re-wrote the entire > arp filtering and classification mechanism from scratch). > > I can give you a "special cut" of 9.0(1) with my fixes if you're > willing to netboot it. Send me the output of show version. > > Paul > ---------------------------------------------------------------------------- > > Date: Wed, 15 Jul 92 19:01:19 -0400 > From: tron!plaza::vsg@uunet.UU.NET (Marty Adkins, (W) ESG Distributed > To: "tac@cisco.com"@uunet.UU.NET > Cc: "cisco@spot.colorado.edu"@uunet.UU.NET, VSG@uunet.UU.NET > Subject: AGS+ 9.0(1) mutates into MOP SysID packet blaster > > Three days ago, one of our AGS+ units running 9.0(1) suddenly > self-transformed > into a terrific packet generator. It began transmitting its MOP SysID > ------------------------------------------------------------------------------ > > Date: Sat, 1 Aug 92 11:00:28 -0400 > From: tron!plaza::vsg@uunet.UU.NET (Distributed Systems/VAX Support - MS > To: "tac@cisco.com"@uunet.UU.NET > Cc: NETWORK@ECLUS.dnet, FLACH.G.A@EMAILdnet, SYSTEM@EM7501.dnet, > VSG@uunet.UU.NET, "cisco@spot.colorado.edu"@uunet.UU.NET > Subject: 9.0(1) bridge-group output-address-list problem when topology > changes > > Hello, > We seem to be having a problem with the bridge-group output-address-list > filters under Version 9.0(1) and 9.0(1.10) on our AGS+. Here is a sketch of > ----------------------------------------------------------------------------- We've got a new AGS+ with CSC/4 ready to install into our critical network environment (whose isn't critical...). I'm looking forward to the increased speed, Flash EEPROM (excitement builds...). It was shipped with 9.0(1) software (excitement comes to a grinding halt...). After reading the trouble reports about 9.0(1) (see above), should I even bother bringing this AGS/4 on-line? Yes, we are heavily into TCP/IP (ARP) and bridging. Unfortunately, and this is a classic case, it seems that lately I have to *really* question whether to "take a chance" on a new software release. However, new features and growth force us to move ahead. But that's a whole 'nother topic. What are my options? In the case of this AGS/4, I believe my options are limited to 9.0 software. Or are they? Where do I go from here? Thanks Tom Tom Karolyshyn Data General Corp Westboro, MA 01580 508-870-7936
Technical Details
Message-ID:
<9208041515.AC00045@adam.WEBO.DG.COM>Path:
arc1-ca.pugleaf.net!sparky!uunet!elroy.jpl.nasa.gov!ames!agate!boulder!recnewsShow Full Headers
Complete Article Headers
Newsgroups: comp.dcom.sys.cisco Path: arc1-ca.pugleaf.net!sparky!uunet!elroy.jpl.nasa.gov!ames!agate!boulder!recnews From: Tom_Karolyshyn@dgc.mceo.dg.com Subject: 9.0(1) stability Message-ID: <9208041515.AC00045@adam.WEBO.DG.COM> Sender: news@colorado.edu Date: 4 Aug 92 10:15:18 edt Lines: 76