From: David Lonnie (david.lonnie@gmail.com)
Date: Tue Jun 03 2008 - 21:19:01 ART
Router1#*write core*
Remote host [172.25.1.3]? *<enter>*
Base name of core files to write [Router1-core]? *<enter>*
Writing Router1-coreiomem
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Writing Router1-core
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Router1#
When we display these files on the server, you can see that their combined
sizes are 48 MB:
Freebsd% *ls -la*
drwxr-xr-x 3 ijbrown ijbrown 512 Feb 1 13:50 ./
drwxr-xr-x 5 root wheel 512 Feb 4 2002 ../
-rw-r--r-- 1 ijbrown ijbrown 46137344 Feb 1 13:54 Router1-core
-rw-r--r-- 1 ijbrown ijbrown 4194304 Feb 1 13:52 Router1-coreiomem
Freebsd%
On Wed, Jun 4, 2008 at 8:04 AM, Joseph Brunner <joe@affirmedsystems.com>
wrote:
> Configure ospf with neighbors on broadcast networks in buggy versions of
> 12.2
>
> Check it...
>
> (from an earlier GS post of mine)
>
>
> You all realize we work with the "Microsoft" of the networking world. (does
> JNPR have these ridiculous problems?, or is JUNOS a little more stable)
>
>
>
>
>
> Rack1R5#conf t
>
> Enter configuration commands, one per line. End with CNTL/Z.
>
> Rack1R5(config)#router ospf 1
>
> Rack1R5(config-router)#net 191.2.125.5 0.0.0.0 area 0
>
> Rack1R5(config-router)#nei 192.2.125.2
>
>
>
> %ALIGN-1-FATAL: Illegal access to a low address 02:56:04 UTC Fri Aug 10
> 2007
>
> addr=0x184, pc=0x609CAD90 , ra=0x609CAD78 , sp=0x6420D4A0
>
>
>
> %ALIGN-1-FATAL: Illegal access to a low address 02:56:04 UTC Fri Aug 10
> 2007
>
> addr=0x184, pc=0x609CAD90 , ra=0x609CAD78 , sp=0x6420D4A0
>
>
>
>
>
> 02:56:05 UTC Fri Aug 10 2007: TLB (store) exception, CPU signal 10, PC =
> 0x609CAD90
>
>
>
>
>
>
>
> --------------------------------------------------------------------
>
> Possible software fault. Upon reccurence, please collect
>
> crashinfo, "show tech" and contact Cisco Technical Support.
>
> --------------------------------------------------------------------
>
>
>
>
>
> -Traceback= 0x609CAD90 0x609BFA60 0x60733E4C 0x604000C8 0x6041BEC4
> 0x604BC1BC 0x604BC1A0
>
> $0 : 00000000, AT : 63E20000, v0 : 00000000, v1 : 00000000
>
> a0 : 64F5B054, a1 : 00000000, a2 : 603C0B2C, a3 : 00250F18
>
> t0 : 00000000, t1 : 00002710, t2 : 00000000, t3 : 00000001
>
> t4 : 0003B4B5, t5 : 00000000, t6 : 00000000, t7 : 00000000
>
> s0 : 64F5AF6C, s1 : 00000000, s2 : 00000000, s3 : 00000000
>
> s4 : 00000001, s5 : 64314F20, s6 : 6481972C, s7 : 00000000
>
> t8 : 00250F10, t9 : 00250F18, k0 : 3041F001, k1 : 30410000
>
> gp : 63E23600, sp : 6420D4A0, s8 : 64F0AC3C, ra : 609CAD78
>
> EPC : 609CAD90, ErrorEPC : BFC04560, SREG : 3401FF03
>
> MDLO : 00000000, MDHI : 00000000, BadVaddr : 00000184
>
> Cause 0000000C (Code 0x3): TLB (store) exception
>
>
>
> No fault history 0xFFFFFFFF. Need 11.1 (2) or higher ROM
>
>
>
> Writing crashinfo to flash:crashinfo_20070810-025605
>
>
>
> 02:56:05 UTC Fri Aug 10 2007: TLB (store) exception, CPU signal 10, PC =
> 0x609CAD90
>
>
>
>
>
>
>
> --------------------------------------------------------------------
>
> Possible software fault. Upon reccurence, please collect
>
> crashinfo, "show tech" and contact Cisco Technical Support.
>
> --------------------------------------------------------------------
>
>
>
>
>
> -Traceback= 0x609CAD90 0x609BFA60 0x60733E4C 0x604000C8 0x6041BEC4
> 0x604BC1BC 0x604BC1A0
>
> $0 : 00000000, AT : 63E20000, v0 : 00000000, v1 : 00000000
>
> a0 : 64F5B054, a1 : 00000000, a2 : 603C0B2C, a3 : 00250F18
>
> t0 : 00000000, t1 : 00002710, t2 : 00000000, t3 : 00000001
>
> t4 : 0003B4B5, t5 : 00000000, t6 : 00000000, t7 : 00000000
>
> s0 : 64F5AF6C, s1 : 00000000, s2 : 00000000, s3 : 00000000
>
> s4 : 00000001, s5 : 64314F20, s6 : 6481972C, s7 : 00000000
>
> t8 : 00250F10, t9 : 00250F18, k0 : 3041F001, k1 : 30410000
>
> gp : 63E23600, sp : 6420D4A0, s8 : 64F0AC3C, ra : 609CAD78
>
> EPC : 609CAD90, ErrorEPC : BFC04560, SREG : 3401FF03
>
> MDLO : 00000000, MDHI : 00000000, BadVaddr : 00000184
>
> Cause 0000000C (Code 0x3): TLB (store) exception
>
>
>
> -Traceback= 0x609CAD90 0x609BFA60 0x60733E4C 0x604000C8 0x6041BEC4
> 0x604BC1BC 0x604BC1A0
>
>
>
>
>
> === Flushing messages (02:56:05 UTC Fri Aug 10 2007) ===
>
>
>
> Queued messages
>
> *** System received a Bus Error exception ***
>
> signal= 0xa, code= 0xc, context= 0x6405b4fc
>
> PC = 0x604fc82c, Cause = 0x20, Status Reg = 0x34018002
>
>
>
> System Bootstrap, Version 11.1(20)AA2, EARLY DEPLOYMENT RELEASE SOFTWARE
> (fc1)
>
> Copyright (c) 1999 by cisco Systems, Inc.
>
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> 2008ccie@live.com
> Sent: Tuesday, June 03, 2008 7:55 PM
> To: ccielab@groupstudy.com
> Subject: how to crash a router?
>
> Hi experts
> how to crash a router?
> because I am studying about "crash dump" in IOS feature
> how to I check the crash dump working properly?
> Regards
>
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Tue Jul 01 2008 - 06:23:20 ART