There's no bug free code, we all know and understand but in recent past I've
seen more code related problem then ever.
SH
-----Original Message-----
From: Stephen Sprunk [mailto:ssprunk@cisco.com]
Sent: Thursday, May 23, 2002 12:09 PM
To: Ryan O'Connell; Steve Francis; cisco-nsp@puck.nether.net
Subject: Re: [nsp] Re[2]: Which IOS
Have any suggestions for improvement on our code recommendation process?
I'm a
team lead in Advanced Services :)
S
| | Stephen Sprunk, K5SSS, CCIE #3723
:|: :|: Network Design Consultant, AS
:|||: :|||: Richardson, Texas, USA
.:|||||||:..:|||||||:. Email: ssprunk@cisco.com
----- Original Message -----
From: "Ryan O'Connell" <ryan-nsp@complicity.co.uk>
To: "Steve Francis" <sfrancis@expertcity.com>; <cisco-nsp@puck.nether.net>
Sent: Thursday, 23 May, 2002 02:52
Subject: [nsp] Re[2]: Which IOS
> On Wed, 22 May 2002 11:55:01 -0700 Steve Francis <sfrancis@expertcity.com>
wrote:
> > So how does a person select the most stable IOS image at any given time?
> >
> > I typically deploy the latest release in the most conservative code
> > train that supports the hardware/features.
>
> This is what most people do I believe - if you have an Advanced Services
> contract with Cisco you can get them to prepare a report recommending a
> code release but they just look at the latest version and most suited code
> train for your requested feature set and compile a list of known bugs
> affecting features you request. It's a useful report to have for a large
> scale deployment however, if there are minor bugs that you're not too
> bothered about at least you know the workarounds in advance.
>
> If you don't hit a serious bug, it's best not to upgrade - we've had one
> potential customer request that we always run the latest or latest-but-one
> release of software on our network gear - we told them no way. It takes
too
> much time and you can cause a lot of downtime introducing new bugs into
the
> network this way.
>
> There's a minor routing table bug in the version of IOS I use on our
Leased
> Line routers, but we've not upgraded even he routers it affects - we know
> a workaround, we'd rather not have different IOSes on different routers
> performing the same function and I'd rather not risk introducing some new
> bug that we don't have a workaround for into the network!
>
> --
> Ryan O'Connell - CCIE #8174
> <ryan@complicity.co.uk> - http://www.complicity.co.uk
>
> I'm not losing my mind, no I'm not changing my lines,
> I'm just learning new things with the passage of time
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:11:57 EDT