Awww, that's funny! ("I don't know which new features I need, but if you
don't know 12.0, you can't tell me which features I need, so let's call it a
wash....see ya later, Mr. 'Old Tech 11.2'") Adding to that, instead of just
upgrading the routers that NEED the new features (for me, usually at the
access level because of the advances in bandwidth grooming features), some
shops (understandably) want uniform levels of code, which I find a bit
overrated. Consistency in sections and versions...yes. Consistency to weed
out major bugs and broken code? definitely. Consistency for consistency's
sake? Well...ummm...errr...ahhh....just document it really well and upgrade
if/when you find the need.
----- Original Message -----
From: "Chuck Larrieu"
To: "EA Louie" ;
Sent: Saturday, September 15, 2001 5:38 PM
Subject: RE: FW: Why Cisco and not ...........!!! [7:19933]
> This is an interesting point, and one worth discussing a bit further.
>
> I can still recall an interview during the course of which the interviewer
> questioned my qualification in part because my experience was with IOS
11.2.
> He stated that they used IOS 12.0 ( newly released at the time. ) I asked
> why, and he said "because we need the new features" I had the temerity to
> ask which ones. There was no answer. The interview went down hill from
> there.
>
> Some folks are upgrade freaks. My own opinion is that in a heavy duty
> production environment the only reason should upgrade is if the upgrade
> fixes an identifiable problem. These days, the latest IOS is not
necessarily
> the best IOS.
>
> Chuck
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> EA Louie
> Sent: Friday, September 14, 2001 2:22 PM
> To: [EMAIL PROTECTED]
> Subject: Re: FW: Why Cisco and not ...........!!! [7:19933]
>
>
> > ya know, I am a fan of if it ain't broke, don't fix it, but dude....Do
you
>
> Me too. and if I never have to mess with the routers because they're
doing
> their job, then why upgrade or futz with them, especially a core router?
I
> love to tinker just like everyone else, but the great thing about a
> production network is that if everything IS running, then I can let it be
> and work on some of the other stuff that's important (like my lab studies
> ;-) If I don't need no new features, then I don't upgrade until I do.
>
> I once had a boss who had to have THE LATEST version of code on our
network
> and would make us schedule IOS upgrades regularly, even when we complained
> that there was no value-add to the upgrade. I guess that's the OTHER
> extreme...and then we'd have a relatively short amount of time to
configure
> the 'new features' of the code into our network (I really learned to hate
> frame-relay traffic shaping).
>
> > never want the fixes and features of newer code? Just curious...
> Especialy
> > with Cisco NAT in it's infant stages...
> >
> > -Patrick
>
>
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=20110&t=19933
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
