The crashinfo file should still be available.
Cisco routers operate on a Unix based file system, so navigation through the
router's filesystem is similar.
Cisco IOS creates a "crashinfo" file in the bootflash directory when a
router crashes (mid to higher end platforms).
To access this file, you would;
log into device in privliged mode
issue "cd bootflash:" command (don't forget the colon)
issue "dir" command to see if crashinfo file exists, if it does then you can
view it by issuing "more bootflash:crashinfo_xxxxxxxx-xxxxxx (where
x=numbers in your device's filename)
or you could send it to vendors for inspection as the following example:
UMC#copy bootflash:crashinfo_20020908-131806 tftp
UMC#cd system:
UMC#dir
Directory of system:/
2 dr-x 0 memory
1 -rw- 8624 running-config
16 dr-x 0 ucode
27 dr-x 0 vfiles
No space information available
UMC#cd bootflash:
UMC#dir
Directory of bootflash:/
1 -rw- 3857148 Aug 19 1999 07:18:41 rsp-boot-mz.111-28.CC.bin
2 -rw- 163474 Mar 15 2002 08:14:51 crashinfo_20020315-141451
3 -rw- 195202 Sep 08 2002 08:18:06 crashinfo_20020908-131806
7602176 bytes total (3385964 bytes free)
UMC#pwd
bootflash:/
I am suprised by the findings of your testing though, as I myself ran
extensive testing on a demo 3745 (NetIQ Chariot-70 + tests with various
scripts including HTTP and HTTPS, & IPERF for load testing) with the DS-3
and ATM IMA cards and did not run into the problem you described. I did
discover the chassis had a bad slot.
""Puckette, Larry (TIFPC)"" wrote in message
news:[EMAIL PROTECTED]
> Thanx all for the interest. We have vendor management support on this
> equipment and I haven't been able to into it due to changes over the
> weekend. So, I regrettably can't answer the question about 'crashinfo'.
But
> it sounds like a very interesting command that I was unaware of and will
> continue trying to get into the router to see.
>
> Larry Puckette
> Senior Network Analyst
> Temple Inland/Austin Data Center
> 512/434-1838
> [EMAIL PROTECTED]
>
> Where the only idol is money and power, there is no hope for integrity.
>
> -----Original Message-----
> From: MADMAN [mailto:[EMAIL PROTECTED]
> Sent: Monday, June 23, 2003 11:44 AM
> To: Puckette, Larry (TIFPC)
> Cc: [EMAIL PROTECTED]
> Subject: Re: 3745 stumper [7:71136]
>
>
> When it crashes are you generating a crashinfo file? do you see any
> error messages, tracebacks, etc...
>
> Dave
>
> Puckette, Larry (TIFPC) wrote:
> > Hi all, I don't normally have anything to actively contribute, so I just
> > lurk and learn. But, we have one now that may generate interesting
> > conversation. We are installing a new Internet access and have Cisco
3725
> > routers. The internal DSU has BNC connections to the DS3. We are using
PPP
> > protocol. While testing everything seems fine until approaching
> 200-300kbps.
> > The traffic is HTTP and HTTPS. The routers crash when the slightest
stress
> > of traffic. The symptoms are constant for both the primary and the
> secondary
> > routers. TFTP traffic through internal interfaces cause no problems,
only
> > traffic that is outbound through the DSUs towards the DS3. The IOS
> versions
> > have been upgraded to current and then downgraded to less current while
> > troubleshooting. Cisco is now looking into IOS problems, but I thought
I'd
> > throw this out there for all you GURUs and give you a chance at it too.
> >
> > Have a GREAT day and thanx tons for the forum.
> >
> > Larry Puckette
> > Senior Network Analyst
> > Temple Inland/Austin Data Center
> > 512/434-1838
> > [EMAIL PROTECTED]
> >
> > Where the only idol is money and power, there is no hope for integrity.
> --
> David Madland
> CCIE# 2016
> Sr. Network Engineer
> Qwest Communications
> 612-664-3367
>
> "Government can do something for the people only in proportion as it
> can do something to the people." -- Thomas Jefferson
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=71182&t=71136
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
