It's an IOS Switch, so can't you just 'write erase' and reload, or does this
not remove the VLAN database?
Scott
-----Original Message-----
From: George Robbins [mailto:grr@netaxs.com]
Sent: Friday, April 20, 2001 9:25 PM
To: cisco-nsp@puck.nether.net; kulriksen@vitalstream.com
Cc: list@inet-access.net
Subject: Re: [nsp] Factory reset for Catalyst 2900
I think it's of the "hold button while power cycling" flavor -
details can be found by going to the cisco web-site and searching
for "recovering lost passwords".
George
> Subject: [nsp] Factory reset for Catalyst 2900
>
> okay. I give. How do you reset a 2900XL to factory defaults?
>
>
> ---------------------------------------------------------------------
> Best regards,
>
> Karyn Ulriksen
> Network Operations Manager
> PublicHost, A VitalStream Company
> 1 Jenner, Suite 100
> Irvine, California 92618 USA
> Phone: (949) 743-2000
> email: kulriksen@vitalstream.com
> URL: http://www.vitalstream.com
> ===========================================
>
> From cisco-nsp-request@puck.nether.net Fri Apr 20 20:58:23 2001
> Date: Fri, 20 Apr 2001 18:27:14 -0400
> X-From_: kulriksen@vitalstream.com Fri Apr 20 18:27:14 2001
> Received-Date: Fri, 20 Apr 2001 18:27:13 -0400
> From: Karyn Ulriksen <kulriksen@vitalstream.com>
> To: cisco-nsp@puck.nether.net
> Cc: list@inet-access.net
> Old-Date: Fri, 20 Apr 2001 15:27:04 -0700
> MIME-Version: 1.0
> X-Mailer: Internet Mail Service (5.5.2448.0)
> Content-Type: text/plain;
> charset="iso-8859-1"
> Old-X-Envelope-To: cisco-nsp
> Resent-From: jared@puck.nether.net
> Resent-Date: Fri, 20 Apr 2001 20:55:29 -0400
> Resent-To: cisco-nsp@puck.nether.net
> Subject: [nsp] Factory reset for Catalyst 2900
> X-Mailing-List: <cisco-nsp@puck.nether.net> archive/latest/6125
> X-Loop: cisco-nsp@puck.nether.net
> Precedence: list
> Resent-Sender: cisco-nsp-request@puck.nether.net
>
> okay. I give. How do you reset a 2900XL to factory defaults?
>
>
> ---------------------------------------------------------------------
> Best regards,
>
> Karyn Ulriksen
> Network Operations Manager
> PublicHost, A VitalStream Company
> 1 Jenner, Suite 100
> Irvine, California 92618 USA
> Phone: (949) 743-2000
> email: kulriksen@vitalstream.com
> URL: http://www.vitalstream.com
> ===========================================
>
From tatsuya@kivex.cuõÅ;Mo
Received: from someone claiming to be
kds1.kivex.com (kds1.kivex.com [208.213.150.16])
by puck.nuõÅ;r.
for <cisco-nsp@puck.nether.net>; Mon, 23 Apr 2001 12:06:39 -0400
(envelopeuõÅ;m
Received-Date: Mon, 23 Apr 2001 12:06:39 -0400
Received: from kds1 (kds1 [208.213.150.16])
by kds1.kivuõÅ;om
for <cisco-nsp@puck.nether.net>; Mon, 23 Apr 2001 11:55:59 -0400 (EDT)
Date: Mon, 23uõÅ; 2
From: Tatsuya Kawasaki <tatsuya@kivex.com>
X-Sender: tatsuya@kds1
To: cisco-nsp@puck.nether.net
MuõÅ;ge
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
SubjectuõÅ;sp
I got the following errors..
System Bootstrap, Version 11.0(10c), SOFTWARE
Copyright (c) 1986-19uõÅ;y
2500 processor with 2048 Kbytes of main memory
Local Timeout (control reg=0x118) Error, address: 0x2130002 auõÅ;10
(PC)
System Bootstrap, Version 11.0(10c), SOFTWARE
Copyright (c) 1986-1996 by cisco Systems
2500 processor with 204uõÅ;yt
Any idea how to fix it?
I can break the loop but I can not get into ROM mode.
TIA,
Tatsuya
/_/_/_uõÅ;/_
Tatsuya Kawasaki
Allegiance Telecom
Unlock the Power of the Internet
http://www\ìÅ;ex
PhMne 301
/_/_/_/_/_/_/_/_/_/_/_/_uõÅ;/_
From jared@puck.nethuõÅ;et
Received: (from jared@localhost)
by puck.nether.net (8.11.1/8.9.3) id f3NGuCf19943
for cisco-ŸìÅ;pu
Resent-Message-Id: <200104231656.f3NGuCf19943@puck.nuõÅ;r.
ReCeived: (from slist@localhost)
by puck.nether.net (8.11.1/8.9.3) id f3N7TnO04653
for jared; Mon, 23 Apr 2001 03:2uõÅ; -
(Envelope-from cisco-nsp-request@puck.nether.net)
Date: Mon, 23 Apr 2001 03:29:49 -0400
X-From_: Stefan.Simko@KPNQweuõÅ;om
Received: from someone claiming to be
prg.traveller.cz (prg.traveller.cz [193.85.2.2])
by puuõÅ;et
for <cisco-nsp@puck.nether.net>; Mon, 23 Apr 2001 03:29:48 -0400
(enveuõÅ;-f
Received-Date: Mon, 23 Apr 2001 03:29:48 -0400
Received: from LTP004187 (st
By prg.traveller.cz (EUnet.1022902037-17/pukvis) with ESMTP id f3N7TeT3
From: Stefan Simko <Stefan.Simko@KPNQwest.com>
X-Mailer: The Bat! (v1.49) Personal
RuõÅ;-T
Organization: KPNQwest
X-Priority: 3 (Normal)
Message-ID: <1942248072.20010418uõÅ;59
To: "Jeremie Meyer" <jmeyer@easynet.fr>
CC: cisco-nsp@puck.nether.net
Subject: Re: [nsp] CEF
In-reply-To: <uõÅ;01
References: <F121b6KZmcK8r6beUzm0000313d@hotmail.com>
<118b01c0c751$0a3ea550$c000000a@JMuõÅ;>
Content-Type: text/plain; charset=Windows-1250
Content-Transfer-Encoding: 8bit
X-Diagnostic: Not on the uõÅ;pt
X
Envelope-To: cisco-nsp
Resent-From: jared@puck.nether.net
Resent-Date: Mon, 23 Apr 2001 12:56:12 -0400
Resent-To: uõÅ;o-
> Is there some cases where CEF should not be used ?
> After all, CEF is not enabeld by default.
> uõÅ;se
> Thanks
> Jérémie
Hi,
one such situation is when you need more features thauõÅ;ll
e.G. my situation was Multilink PPP, CEF, when CEF had to go
off.I think there are some issues with CEF and RTP as weuõÅ;an
certain IOS releases, is CEF and policy routing.
the situatuõÅ;wi
sufficient and dCEF starts to fail, which is a big problem, so you
have tuõÅ;ca
configuration. the indication of this situation is the
message uõÅ; d
I believe others will provide you with another situations, when CEF
must go off.
Stefan
uõÅ;
S
From jared@puck.nethuõÅ;et
Received: (from jared@localhost)
by puck.nether.net (8.11.1/8.9.3) id f3NHZ0U23924
for cisco-uõÅ;pu
(envelope-from jared)
Resent-Message-Id: <200104231735.f3NHZ0U23924@puck.nuõÅ;r.
ReCeived: (from slist@localhost)
by puck.nether.net (8.11.1/8.9.3) id f3NHYI823878
for jared; Mon, 23 Apr 2001 13:3uõÅ; -
(Envelope-from cisco-nsp-request@puck.nether.net)
Date: Mon, 23 Apr 2001 13:34:18 -0400
X-From_: Damon.Pegg@Carrier1ŸìÅ;
carrier1.net (root@carrier1.net [212.4.193.68])
by puck.uõÅ;er
for <cisco-nsp@puck.nether.net>; Mon, 23 Apr 2001 13:34:17 -0400
(envelopuõÅ;om
Received-Date: Mon, 23 Apr 2001 13:34:17 -0400
Received: from gblon1s07.carrier1.com ([10.1.9.21uõÅ;by
Mon, 23 Apr 2001 18:34:27 +0100 (BST)
Received: by GBLON1S07 with IntuõÅ;t
id <JHSRG7M4>; Mon, 23 Apr 2001 18:34:14 +0100
Message-ID: <83189BAB0F57D411A1C400508B6AADBD03uõÅ;8E
From: Pegg Damon <Damon.Pegg@Carrier1.com>
To: "'Stefan Simko'" <Stefan.Simko@KPNQwest.com>, cisco-nsp@puck.neuõÅ;.n
SubjEct: RE: [nsp] CEF
Old-Date: Mon, 23 Apr 2001 18:34:07 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5uõÅ;3.
ConTent-Type: text/plain;
charset="windows-1250"
Content-Transfer-Encoding: quoted-printable
X-Diagno
X-Envelope-To: cisco-nsp
Resent-From: jared@puck.nether.net
Resent-Date
Resent-To:uõÅ;co
haha - there are several times to make your berth around cef wider than =
a
cockney on Stella.
FirsuõÅ; i
issue.
These can't be rammed past the 128 mark and cef eats a wuõÅ; l
memory
(and I mean a whole lot) if these beasts are running a cumbersome IGP
and/or full BGP tables. What you sauõÅ;n
if
your hitting peak cpu on a NPE-200 (or -225) 128Mb (or less) 7206, you =
may
find your buõÅ;r
puppies can
go to 512Mb memory and take the solid NPE300, 400 and the neuõÅ;E
Second on my list of dos and don'ts - watch your IOS. Some of the =
early 12
train is horrid with cef. PeruuõÅ;he
what do
you run?
Channelised circuits and CEF can be problematical, especially E1. 750uõÅ;ri
128
DRAM, in style, and channelised have caused probluõÅ;in
In general, CEF does wonders for your cpu util but at heavy memory =
cost. It
rocks when it works but be careuõÅ;be
of the
bugs it throws at you are far from obvious. Personally I run it on =
some
7xxx,uõÅ;
Damon,
Carrier1
> -----Original Message-----
> From: SteuõÅ;Si
> Sent: 23 April 2001 17:56
> To: cisco-nsp@puck.nether.net
> Cc: cisco-nsp@puck.neuõÅ;.n
> SuBject: Re: [nsp] CEF
>=20
>=20
> > Is there some cases where CEF should not be used ?
>=20
> > After all, CEF is nouõÅ;ab
>=20
> > We use 7507, 7206, 7206 VXR, ATM-OC3/E3/FE PAs.
>=20
> > Thanks
>=20
> > J=E9r=E9mie
>=20
>=20
> uõÅ;>
> e.g. my situation was Multilink PPP, CEF, when CEF had tŸìÅ;
>
> another situation, which is now solved, but you can hit it uõÅ;
>
>=20
> the situation with 7500 routers may occur when VIP memory is not
uõÅ;ff
> have to locally disable CEF until you upgrade the memory uõÅ;ha
tHe
> configuration. the indication of this situation is the
> message "FIB disabled..." in your logfiles.
>=20
>=20uõÅ; b
> must go off.
>=20
>=20
> Stefan
>=20
> ---
> Stefan SimuõÅ;KP
>=20
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:35 EDT