I will have to look into this and do some more testing on the lab. Looks like I may have pushed the limits to much with the lab.:) At this point right now I am not positive as to what is causing the crash.
Regards, Tyson Scott - CCIE #13513 R&S and Security Technical Instructor - IPexpert, Inc. Telephone: +1.810.326.1444 Cell: +1.248.504.7309 Fax: +1.810.454.0130 Mailto: [email protected] Join our free online support and peer group communities: http://www.IPexpert.com/communities IPexpert - The Global Leader in Self-Study, Classroom-Based, Video On Demand and Audio Certification Training Tools for the Cisco CCIE R&S Lab, CCIE Security Lab, CCIE Service Provider Lab , CCIE Voice Lab and CCIE Storage Lab Certifications. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Stuart Hare Sent: Saturday, June 27, 2009 3:18 AM To: Johan Bornman Cc: <[email protected]> Subject: Re: [OSL | CCIE_Security] Router crashed This is to do with the scripts that run to load the lab if u check show version it tells u that the config register will be correct after reload. Hence when the router crashes due to the software failure the register does not get changed and u end up in The wizard. Just do a quick reload at the beggining of ur session or before it crashes to resolve this. Sent from my iPhone On 27 Jun 2009, at 07:54, "Johan Bornman" <[email protected]> wrote: > Dave, > > Would saving the config have helped here? The initial config loaded > by the > IPexpert scripts have also disappeared. > > Johan > > -----Original Message----- > From: Dave Craddock [mailto:[email protected]] > Sent: 27 June 2009 08:32 > To: Johan Bornman; [email protected] > Subject: RE: [OSL | CCIE_Security] Router crashed > > Hi john > To me that sounds like one of two things? > Either the config register is set to no load the startup or you > havn't been > saving at regular intervals. I always do a copy run flash as well as > a copy > run start so if the router crashes you can do a copy flash start/run > and get > back to where you were quickly. > As for the proctor he would have to reload and then mabye you would > get some > extra time but not a lot and if this happens as say 7 hours in you > are up > the creak without a paddle as they saw as there would be little > chance of > you getting the full config back on if you havn't saved it to the > flash that > is > > > > dave > > -----Original Message----- > From: Johan Bornman <[email protected]> > Sent: 27 June 2009 06:39 > To: [email protected] <[email protected] > > > Subject: [OSL | CCIE_Security] Router crashed > > Hi, > > > > Was doing Lab2A task 2.16. The router and I must have been in the > same state > of mind with this task. The router crashed. Just wanted to make you > (IPExpert) aware. > > > > The router then rebooted and started with: > > > > Would you like to enter the initial configuration dialog? [yes/no]: > > % Please answer 'yes' or 'no'. > > > > What will happen if this happens in the exam? Will I get time credit > and the > procotor has to repair (Load initial config, etc) > > > > See crash info below. > > > > Rgds > > > > Johan > > > > Crash info: > > > > %ALIGN-1-FATAL: Illegal access to a low address 06:44:48 UTC Sat Jun > 27 2009 > > addr=0x1, pc=0x642246F0 , ra=0x63C53F7C , sp=0x68E92AE8 > > > > %ALIGN-1-FATAL: Illegal access to a low address 06:44:48 UTC Sat Jun > 27 2009 > > addr=0x1, pc=0x642246F0 , ra=0x63C53F7C , sp=0x68E92AE8 > > > > > > 06:44:48 UTC Sat Jun 27 2009: TLB (store) exception, CPU signal 10, > PC = > 0x642246F0 > > > > > > > > -------------------------------------------------------------------- > > Possible software fault. Upon reccurence, please collect > > crashinfo, "show tech" and contact Cisco Technical Support. > > -------------------------------------------------------------------- > > > > > > -Traceback= 0x642246F0 0x63C53F7C 0x63DCBF9C 0x6201AA04 0x6201ACF0 > 0x62006B60 0x620012B8 0x61FFA668 0x62006A3C 0x62006BC8 0x62019744 > 0x62014FE0 > 0x620154A8 > > $0 : 00000000, AT : 67210000, v0 : 00000001, v1 : 00000001 > > a0 : 00000001, a1 : 00000000, a2 : 000000B0, a3 : 00000000 > > t0 : 0000002C, t1 : 00000000, t2 : 00000001, t3 : 676D0000 > > t4 : 00000000, t5 : 00000000, t6 : 00000000, t7 : 00000002 > > s0 : 00000001, s1 : 7112CC24, s2 : 00000006, s3 : 68E92B48 > > s4 : 00000000, s5 : 00000001, s6 : 66E10000, s7 : 660A0000 > > t8 : 675C7CF0, t9 : 67180000, k0 : 6934AD9C, k1 : 633D8AE0 > > gp : 6721E3E0, sp : 68E92AE8, s8 : 00000002, ra : 63C53F7C > > EPC : 642246F0, ErrorEPC : BFC05CFC, SREG : 3400FF03 > > MDLO : 0012BBE0, MDHI : 00000000, BadVaddr : 00000001 > > DATA_START : 0x64265E80 > > Cause 0000000C (Code 0x3): TLB (store) exception > > > > Writing crashinfo to flash:crashinfo_20090627-064448 > > > > 06:44:48 UTC Sat Jun 27 2009: TLB (store) exception, CPU signal 10, > PC = > 0x642246F0 > > > > > > > > -------------------------------------------------------------------- > > Possible software fault. Upon reccurence, please collect > > crashinfo, "show tech" and contact Cisco Technical Support. > > -------------------------------------------------------------------- > > > > > > -Traceback= 0x642246F0 0x63C53F7C 0x63DCBF9C 0x6201AA04 0x6201ACF0 > 0x62006B60 0x620012B8 0x61FFA668 0x62006A3C 0x62006BC8 0x62019744 > 0x62014FE0 > 0x620154A8 > > $0 : 00000000, AT : 67210000, v0 : 00000001, v1 : 00000001 > > a0 : 00000001, a1 : 00000000, a2 : 000000B0, a3 : 00000000 > > t0 : 0000002C, t1 : 00000000, t2 : 00000001, t3 : 676D0000 > > t4 : 00000000, t5 : 00000000, t6 : 00000000, t7 : 00000002 > > s0 : 00000001, s1 : 7112CC24, s2 : 00000006, s3 : 68E92B48 > > s4 : 00000000, s5 : 00000001, s6 : 66E10000, s7 : 660A0000 > > t8 : 675C7CF0, t9 : 67180000, k0 : 6934AD9C, k1 : 633D8AE0 > > gp : 6721E3E0, sp : 68E92AE8, s8 : 00000002, ra : 63C53F7C > > EPC : 642246F0, ErrorEPC : BFC05CFC, SREG : 3400FF03 > > MDLO : 0012BBE0, MDHI : 00000000, BadVaddr : 00000001 > > DATA_START : 0x64265E80 > > Cause 0000000C (Code 0x3): TLB (store) exception > > > > -Traceback= 0x642246F0 0x63C53F7C 0x63DCBF9C 0x6201AA04 0x6201ACF0 > 0x62006B60 0x620012B8 0x61FFA668 0x62006A3C 0x62006BC8 0x62019744 > 0x62014FE0 > 0x620154A8 > > > > > > === Flushing messages (06:44:49 UTC Sat Jun 27 2009) === > > > > Queued messages: > > L2 ECC Counter = 0000000000000000 > > Memory and IO Err Counter = 0000000000000000 > > > > Bus Watcher Counters > > cor_l2cache_data_ecc_count = 0 > > bad_l2cache_data_ecc_count = 0 > > cor_l2cache_tag_ecc_count = 0 > > bad_l2cache_tag_ecc_count = 0 > > cor_memory_data_ecc_count = 0 > > bad_memory_data_ecc_count = 0 > > bus_errors = 0 > > > > CPU temp is 48 > > Temp1 temp is 24 > > Temp2 temp is 22 > > > > Internal voltage is 3316 > > Remote voltage1 is 5153 > > Remote voltage2 is 2525 > > Remote voltage3 is 1203 > > > >
