Hi Gert,

We looked into modular some time ago, but I don't imagine much has changed.

Patches were for as you say gaping security holes, not upgrades even of a point 
release.


-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of Gert Doering
Sent: 24 July 2009 08:27
To: Jeff Cartier
Cc: [email protected]
Subject: Re: [c-nsp] Questions about upgrading and image of a Modular IOS

Hi,

On Thu, Jul 23, 2009 at 09:04:40AM -0400, Jeff Cartier wrote:
> Just for peace of mind, and a good nights sleep :-)...I was hoping for
> some confirmation from the group if this is the correct way to upgrade
> the IOS (the boss is against patching the IOS).  So here are my steps...

How does Cisco currently deal with "modular IOS" upgrades and patches?

Are there patches available at all (and yes, where to find them)?  If yes, can 
these patches be used to upgrade from, say, SXI1 to SXI2, or will they only fix 
gaping security holes?  Are the rules for "what will be in a patch and what 
not" documented somewhere?

We're in the process of upgrading a few boxes from SXI1 to SXI2 due to BGP 
memory leaks.  Currently, this is "non-modular" code, but I wonder if 
modular+patches would bring me the fixed BGPD without having to do a full 
reload...

gert

--
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             [email protected]
fax: +49-89-35655025                        [email protected]

Checked by AVG - www.avg.com
Version: 8.5.392 / Virus Database: 270.13.20/2249 - Release Date: 07/21/09 
18:02:00

--

This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the sender. Any
offers or quotation of service are subject to formal specification.
Errors and omissions excepted.  Please note that any views or opinions
presented in this email are solely those of the author and do not
necessarily represent those of Lumison.
Finally, the recipient should check this email and any attachments for the
presence of viruses.  Lumison accept no liability for any
damage caused by any virus transmitted by this email.
_______________________________________________
cisco-nsp mailing list  [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Reply via email to