Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Conitivity 600 loops reboot after NAT Traversal Change

Status
Not open for further replies.

msobkowi

IS-IT--Management
Oct 3, 2006
50
CA
So we have a Contivity 600 that just started to loop rebooting due to a "Software Exception Detected..."
It started right after I rebooted the system when I changed the NAT traversal setting for my BASE group. One on occasion I got an error referring to the FWPOLICY.txt file located in system/config.
I'm totally lost and need the VPN back up asap.
If I try to boot into recovery mode, I will say booting into recovery mode, but then 10 seconds later, cycles the system and reboots again.
I have direct access to the file system and I am wondering if I can delete or modify any files which can trick the system of being in a clean or fresh state.
The boot image version is V04_80 which I am going to assume is fairly out-dated, but have never had any problems until now.

Thanks
Here is a capture from a session:

General Software Celeron Embedded BIOS (tm) Version 4.3
Copyright (C) 2000 General Software, Inc.

Nortel Networks - Contivity 600

00000640K Low Memory Passed
00129024K Ext Memory Passed
Wait.....

(C) 2000 General Software, Inc.
Celeron-4.3-6E69-624E

VxLd 1.2 .......................................................................
................................................................................
...................................

Nortel Networks System Boot

Nortel Networks Extranet Access Switch
Copyright (c) 1999-2003 Nortel Networks, Inc.
Boot Image Version: V04_80
Creation date: Jul 31 2003, 17:13:08

auto-booting...

done.

Performing Check Disk on [/ide0/] ...
Copyright (c) 1993-1996 RST Software Industries Ltd. All rights reserved
ver: 2.6 FCS

Disk Check In Progress ...


total disk space (bytes) : 2,146,631,680
bytes in each allocation unit : 32,768
total allocation units on disk : 65,510
bad allocation units : 0
available bytes on disk : 1,973,616,640
available clusters on disk : 60,230
maximum available contiguous chain (bytes) : 1,973,551,104
available space fragmentation (%) : 1
clusters allocated : 5,280
Done Checking Disk.
Attempting to Load /ide0/system/bin/vxWorks...12718080 + 2208816 + 386964
Starting at 0xc00000...



Welcome to the Contivity Secure IP Services Gateway
Copyright (c) 1999-2003 Nortel Networks, Inc.

Version: V04_80.124
Creation date: Aug 6 2003, 16:57:14

Date: 07/18/2
Unit Serial Number: <hidden value>


Please enter the administrator's user name:

Nortel Networks, Inc.

CoreDump Kernel Version: V04_80.124
Creation date: Aug 6 2003, 18:36:37
Base Level: BL124



Software Exception Detected.
/ide0// - disk check in progress ...

/ide0// - Volume is OK

total # of clusters: 65,512
# of free clusters: 60,230
# of bad clusters: 0
total free space: 1,882 Mb
max contigous free space: 1,973,551,104 bytes
# of files: 1,833
# of folders: 79
total bytes in files: 128,535 Kb
# of lost chains: 0
total bytes in lost chains: 0
Cleaning Up Version '/ide0/system/core/CORE011.GZ'
Writing memory content 0x0 to 0x7eff000 to /ide0/system/core/CORE013.GZ ...
################################################################################
################################################################################
############################################
################################################################################
################################################################################
########
Done
CoreDump Kernel Task Completed.
Rebooting ...



Please note that this is only 2-5 minutes into a fresh startup and this loops repeatedly.

Mathew



 
The issue is being caused with your software which looks like the box is core dumping!!

You will need to do the following.. Either have Nortel Tech support look at the core file... with wihich they will tell you to upgrade.. Or just upgrade to the V05_05.3XX code or above..

The NAT T setting should not cause your box to core...
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top