an error interrupt is usually a hw issue (tho' in rare cases it can be
a sw problem). in recent code (which you will have to be on if you
have a NPE-400 ;) ) we dump a fair bit of information in the crashinfo
file to help us diagnose the cause of the crash (is it a mis-seated/bad
pa, midplane, io controller, npe, etc). getting the crashinfo into the
hands of the TAC will help you diagnose the appropriate action to
take.
regards
.siva
On Tue, 1 May 2001, Gert Doering wrote:
> Hi,
>
> On Mon, Apr 30, 2001 at 10:58:31AM -0700, Karyn Ulriksen wrote:
> > interesting...
> >
> > one of my 7507s crashed for no apparent reason this morning... I wonder
> > if something is going on...
>
> Interesting indeed. One of my 7206VXR/NPE400s did also crash this
> morning, after working nicely for a couple of weeks.
>
> "show version" shows this:
>
> Cisco-M uptime is 22 hours, 53 minutes
> System returned to ROM by error - an Error Interrupt, PC 0x602F3E98 at 11:05:10 MEDST Mon Apr 30 2001
> System restarted at 11:06:16 MEDST Mon Apr 30 2001
> System image file is "disk1:c7200-k3p-mz.120-14.S3.bin"
>
> maybe something more generic?
>
> gert
>
> --
> Gert Doering
> Mobile communications ... right now writing from *@Bologna*
> ... mobile phone: +49 177 2160221 ... or mail me: gert@greenie.muc.de
>
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:36 EDT