[c-nsp] Both my borders crashed?
Shaun R.
mailinglists at unix-scripts.com
Wed May 28 13:16:31 EDT 2008
Thanks, ya the clock on border1 is fixed now, i though i had it syncing with
ntp.
What release would you recommend, IOS Upgrade Planner shows only T and XD
~Shaun
"Justin M. Streiner" <streiner at cluebyfour.org> wrote in message
news:Pine.LNX.4.64.0805280927570.13485 at whammy.cluebyfour.org...
> On Wed, 28 May 2008, Shaun R. wrote:
>
>> Both my border routers look to have crashed at the same time. Anybody
>> know
>> why from this error? If not how can i find out what happened? Both
>> routers
>> are 7206VXR-NPE-G2's
>>
>>
>> border2 uptime is 2 days, 19 hours, 20 minutes
>> System returned to ROM by error - a SegV exception, PC 0x13EF030 at
>> 05:05:00
>> UTC Sun May 25 2008
>> System image file is "bootflash:c7200p-advipservicesk9-mz.124-15.T1.bin"
>>
>> border1 uptime is 2 days, 19 hours, 19 minutes
>> System returned to ROM by error - a SegV exception, PC 0x13EF030 at
>> 07:51:26
>> UTC Fri Mar 30 2001
>> System image file is "bootflash:c7200p-advipservicesk9-mz.124-15.T1.bin"
>
> Could be a memory corruption (software) issue, access violation (some
> process trying to scribble into a register that it's not allowed to
> touch), scribbling into the wrong memory region, etc...
>
> If you want to find out what caused this, yor best bet is to go to the
> TAC. Considering both routers crashed with the same message, I'll bet
> it's a bug in that particular version of IOS. "T" train releases are
> where new features are intriduced and allowed to bake for awhile before
> being rolled into a mainline release. As such, they can be more bug-prone
> and my advice has always been not to use T train releases on production
> routers unless there is absolutely no other choice.
>
> It also looks like the clock on border1 is in need of an adjustment :)
>
> jms
> _______________________________________________
> cisco-nsp mailing list cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
More information about the cisco-nsp
mailing list