[c-nsp] 12.2(25)S on NPEG1

Mon Jan 31 19:33:34 EST 2005

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi David -

I'll be sure to relay the date as soon as I have it.

Clay

On Tue, Feb 01, 2005 at 10:25:19AM +1000, David J. Hughes wrote:
> 
> Hi,
> 
> A "fixed" 12.2(18)S would be fine for me.  I appreciate you don't have 
> a schedule at the moment but is there any way you can get us a firm 
> date on that release?  We need to make decisions on where to go as a 
> result of these PSIRT related issues.
> 
> 
> David
> ...
> 
> 
> On 01/02/2005, at 10:20 AM, Clayton Kossmeyer wrote:
> 
> >-----BEGIN PGP SIGNED MESSAGE-----
> >Hash: SHA1
> >
> >
> >Hi Folks -
> >
> >Not sure what release you were running on, nor where you'd like to go,
> >but we do have a 12.2(18)Sx rebuild scheduled that will address all
> >the recent PSIRT advisories and may not suffer from some of the
> >problems you've seen on 25S.  No date yet on when it will be
> >available.
> >
> >Regards,
> >
> >Clay
> >
> >On Mon, Jan 31, 2005 at 04:26:58PM -0700, james edwards wrote:
> >>I too am on hold on upgrading several 7206 NEP-300 and 400's to 
> >>12.2(25)Sx,
> >>till
> >>I have some word from cisco. I would like to go the S2, for the RPF 
> >>bug fix.
> >>
> >>James H. Edwards
> >>Routing and Security Administrator
> >>At the Santa Fe Office: Internet at Cyber Mesa
> >>jamesh at cybermesa.com  noc at cybermesa.com
> >>http://www.cybermesa.com/ContactCM
> >>(505) 795-7101
> >>
> >>
> >>----- Original Message -----
> >>From: "David J. Hughes" <bambi at hughes.com.au>
> >>To: "'cisco-nsp'" <cisco-nsp at puck.nether.net>
> >>Sent: Monday, January 31, 2005 4:08 PM
> >>Subject: Re: [c-nsp] 12.2(25)S on NPEG1
> >>
> >>
> >>>
> >>>Has there been any further info on this?  I've been planning on 
> >>>taking
> >>>our G1s to 12.2(25)S but this has thrown a spanner in the works.  Has
> >>>there been any word from TAC on this to anyone?
> >>>
> >>>
> >>>David
> >>>...
> >>>
> >>>
> >>>On 28/01/2005, at 8:41 PM, Santiago Felipe Perez wrote:
> >>>
> >>>>Hi,is there any bug explaining this behaviour or any answer from 
> >>>>TAC to
> >>>>solve this problem?, because Cisco suggest to go to this release
> >>>>12.2(25)S2
> >>>>to solve the problem  "Cisco Security Advisory: Cisco IOS Misformed
> >>>>BGPPacketCauses Reload",when the IOS installed is any release of 
> >>>>12.2S.
> >>>>
> >>>>Any suggest?
> >>>>
> >>>>
> >>>>-----Mensaje original-----
> >>>>De: cisco-nsp-bounces at puck.nether.net
> >>>>[mailto:cisco-nsp-bounces at puck.nether.net] En nombre de Marcus
> >>>>Stoegbauer
> >>>>Enviado el: martes, 25 de enero de 2005 15:24
> >>>>Para: cisco-nsp at puck.nether.net
> >>>>Asunto: Re: [c-nsp] 12.2(25)S on NPEG1
> >>>>
> >>>>On Tuesday 25 January 2005 13:39, nishal goburdhan wrote:
> >>>>>we've upgraded a few G1s to 25Sx and noticed that periodically, the
> >>>>>router disables 'ip route-cache' across all interfaces.
> >>>>>
> >>>>>'sh ip int' reveals:
> >>>>>  IP fast switching is enabled
> >>>>>  IP Flow switching is disabled
> >>>>>  IP CEF switching is disabled
> >>>>>
> >>>>>Cisco 7206VXR (NPE-G1) processor (revision A) with 983040K/65536K
> >>>>>bytes of memory. System image file is
> >>>>>"disk2:c7200-k91p-mz.122-25.S2.bin"
> >>>>>
> >>>>>...same has also occured on 12.2(25)S.
> >>>>>
> >>>>>has anyone else noticed this?
> >>>>
> >>>>Yep, that happened here on nearly all of our routers, with NPE-G1 
> >>>>and
> >>>>also
> >>>>with NPE-400.
> >>>>We only did minor changes to the configuration (removing a
> >>>>subinterface,
> >>>>removing an area from OSPF and so on), and suddenly all interfaces 
> >>>>had
> >>>>"no
> >>>>ip route-cache" and "no ip route-cache cef" set.
> >>>>Interesting enough, it doesn't happen all the time: On two routers 
> >>>>with
> >>>>exactly the same configuration, hardware and software versions, we
> >>>>changed
> >>>>the same things in the config, router1 had "no ip route-cache" set 
> >>>>on
> >>>>the
> >>>>interfaces, router2 not.
> >>>>
> >>>>The problem with "clear access-list counter" happened here, too. I'm
> >>>>currently waiting for Cisco to see that it really is a bug ("Please 
> >>>>use
> >>>>clear access-list instead of clear ip access-list" and "Please 
> >>>>update
> >>>>to the
> >>>>latest release" isn't very good advice when we're already running
> >>>>12.2(25)S2
> >>>>and I only left out the "clear access-list" lines in the bug report 
> >>>>to
> >>>>simplify it ...).
> >>>>
> >>>>   Marcus
> >>>>_______________________________________________
> >>>>cisco-nsp mailing list  cisco-nsp at puck.nether.net
> >>>>https://puck.nether.net/mailman/listinfo/cisco-nsp
> >>>>archive at http://puck.nether.net/pipermail/cisco-nsp/
> >>>>
> >>>>_______________________________________________
> >>>>cisco-nsp mailing list  cisco-nsp at puck.nether.net
> >>>>https://puck.nether.net/mailman/listinfo/cisco-nsp
> >>>>archive at http://puck.nether.net/pipermail/cisco-nsp/
> >>>>
> >>>
> >>>_______________________________________________
> >>>cisco-nsp mailing list  cisco-nsp at puck.nether.net
> >>>https://puck.nether.net/mailman/listinfo/cisco-nsp
> >>>archive at http://puck.nether.net/pipermail/cisco-nsp/
> >>
> >>_______________________________________________
> >>cisco-nsp mailing list  cisco-nsp at puck.nether.net
> >>https://puck.nether.net/mailman/listinfo/cisco-nsp
> >>archive at http://puck.nether.net/pipermail/cisco-nsp/
> >-----BEGIN PGP SIGNATURE-----
> >Version: GnuPG v1.2.3 (SunOS)
> >
> >iD8DBQFB/stCEHa/Ybuq8nARAh9VAJ91paUlT6g9zbGtL9JG34NnPwhMcgCdGSIb
> >FQfBpibwCqw238rXSh1KB9E=
> >=MbsF
> >-----END PGP SIGNATURE-----
> >
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (SunOS)

iD8DBQFB/s5aEHa/Ybuq8nARAr4LAJ9SrPCcG+1hsb3S+dfDpm+Nq9fPzACeIZ6m
S3RyZPfKTjPNYu5rtkJvv7Q=
=7Rxc
-----END PGP SIGNATURE-----