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 SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Contivity 1100 boot issue

Status
Not open for further replies.

PainOfDeath

Technical User
Feb 19, 2005
104
0
0
CA
Hello everyone,

I purchased a used Contivity 1100 (eBay) that does not successfully boot. It would get to the point just after the disk check and halt there. I booted the unit into recovery mode and was able to access the web-based tools but there did not seem to be a way to recover the firmware or boot loader directly. So based on what I found online and in the manual, I decided to format the disk using the utility. Obviously it still doesn't boot but it does give access to Nortel Boot tools, after a whole bunch of error messages.

Is there ANY way to get the unit to connect to an FTP server at this point and reload the firmware? Or is the unit bricked? Help!
 
If you can find the software for your unit, you can reload it via FTP from the recovery menu. You can download the software from Avayas support site assuming you have a support contract on the unit. You may be able to find it elsewhere if you get lucky. Typically they are zip files with a name such as 70_350_128bit_diskless.zip or something to that effect.
 
Thanks. I booted back into the recovery mode and was able to load version 4.85 onto the unit. However when I restarted it, I was greeted with the following:

Performing Check Disk on [/ide1/] ...
Copyright (c) 1993-1996 RST Software Industries Ltd. Israel. All rights reserved

ver: 2.6 FCS

Disk Check In Progress ...


total disk space (bytes) : 62,633,984
bytes in each allocation unit : 2,048
total allocation units on disk : 30,583
bad allocation units : 0
available bytes on disk : 48,896,000
available clusters on disk : 23,875
maximum available contiguous chain (bytes) : 48,896,000
available space fragmentation (%) : 0
clusters allocated : 6,708
Done Checking Disk.
Attempting to Load /ide1/system/bin/vxWorks...34608 + 5311576 + 107928
Starting at 0x2000000...

And then it just sits there. This is exactly what it did before the format, except before it said "Starting at 0x2800000..." and then did nothing.

Here is the log from the recovery mode:

05/06/1983 06:06:16 0 CtxtReclaim [01] Created.
05/06/1983 06:06:16 0 Reclaim [01] Created.
05/06/1983 06:06:16 0 PaceJob{0} [00] Created.
05/06/1983 06:06:16 0 IP Redirector [13] IpPubTableInit() Public Address Table initialized
05/06/1983 06:06:16 0 FEI Driver [00] Enabling Broadcom switch.
05/06/1983 06:06:16 0 FEI Driver [01] Setting Devloc for unit 0 to 0x100
05/06/1983 06:06:16 0 FEI Driver [03] Attaching driver for card 0
05/06/1983 06:06:16 0 IP Redirector [00] IpPubTabGarbColInit: timer created.
05/06/1983 06:06:16 0 IP Redirector [00] IpPubTabGarbColInit:timer_connect() succeeded.
05/06/1983 06:06:17 0 FEI Driver [03] auto NEGOTIATION STARTS: speed: 0 duplex: 0
05/06/1983 06:06:18 0 FEI Driver [03] Auto negotiate completed 782d
05/06/1983 06:06:18 0 FEI Driver [03] Fei unit 0 status REG = 782d
05/06/1983 06:06:18 0 FEI Driver [03] auto NEGOTIATION STARTS: speed: 2000 duplex: 100
05/06/1983 06:06:20 0 FEI Driver [03] Auto negotiate completed 782d
05/06/1983 06:06:20 0 FEI Driver [00] MDI Id REG2 = 0x2a8, Id REG3 = 0x154
05/06/1983 06:06:20 0 FEI Driver [03] Intel 82555, model 21, rev 4
05/06/1983 06:06:20 0 FEI Driver [03] Speed: 100MBS, Mode: full duplex
05/06/1983 06:06:20 0 FEI Driver [00] feiReset: unit 0 taskId 0x7efee68
05/06/1983 06:06:20 0 FEI Driver [01] Setting Devloc for unit 0 to 100
05/06/1983 06:06:20 0 FEI Driver [01] Setting Devloc for unit 1 to 0x101
05/06/1983 06:06:20 0 FEI Driver [03] Attaching driver for card 1
05/06/1983 06:06:21 0 FEI Driver [03] auto NEGOTIATION STARTS: speed: 0 duplex: 0
05/06/1983 06:06:25 0 FEI Driver [03] auto NEGOTIATION STARTS: speed: 0 duplex: 0
05/06/1983 06:06:29 0 FEI Driver [03] auto NEGOTIATION STARTS: speed: 0 duplex: 0
05/06/1983 06:06:33 0 FEI Driver [01] LINK FAILS, Check line connection
05/06/1983 06:06:33 0 FEI Driver [00] feiReset: unit 1 taskId 0x7efee68
05/06/1983 06:06:33 0 FEI Driver [01] Setting Devloc for unit 1 to 101
05/06/1983 06:06:33 0 FEI Driver [00] No interface object for unit 0 devLoc 0x100 in cfg file
05/06/1983 06:06:33 0 Interface [13] No inbound filter for interface (devLoc=0x100). Using default filter
05/06/1983 06:06:33 0 Interface [10] IntfFilter: rule[1] FILTER 1 deny IP any any
05/06/1983 06:06:33 0 Interface [10] IntfFilter: rule[2]
05/06/1983 06:06:33 0 Interface [13] No outbound filter for interface (devLoc=0x100). Using default filter.
05/06/1983 06:06:33 0 Interface [10] IntfFilter: rule[1] FILTER 1 deny IP any any
05/06/1983 06:06:33 0 Interface [10] IntfFilter: rule[2]
05/06/1983 06:06:33 0 FEI Driver [00] Creating interface for unit 0, System Board result=0
05/06/1983 06:06:33 0 FEI Driver [12] No IP address configured for unit 0 devLoc 0x100 in cfg file
05/06/1983 06:06:33 0 FEI Driver [00] Unit fei0 devLoc 0x100, private IP addr 0.0.0.0, netmask 0x0, IPX addr 0, IPX frame/enabled 400
05/06/1983 06:06:33 0 Ethernet [01] Created Ethernet context object for card 0
05/06/1983 06:06:33 0 FEI Driver [00] No interface object for unit 1 devLoc 0x101 in cfg file
05/06/1983 06:06:33 0 Interface [13] No inbound filter for interface (devLoc=0x101). Using default filter
05/06/1983 06:06:33 0 Interface [10] IntfFilter: rule[1] FILTER 1 deny IP any any
05/06/1983 06:06:33 0 Interface [10] IntfFilter: rule[2]
05/06/1983 06:06:33 0 Interface [13] No outbound filter for interface (devLoc=0x101). Using default filter.
05/06/1983 06:06:33 0 Interface [10] IntfFilter: rule[1] FILTER 1 deny IP any any
05/06/1983 06:06:33 0 Interface [10] IntfFilter: rule[2]
05/06/1983 06:06:33 0 FEI Driver [00] Creating interface for unit 1, Slot 1 Interface 1 result=0
05/06/1983 06:06:33 0 FEI Driver [12] No IP address configured for unit 1 devLoc 0x101 in cfg file
05/06/1983 06:06:33 0 FEI Driver [00] Unit fei1 devLoc 0x101, public IP addr 0.0.0.0, netmask 0x0, IPX addr 0, IPX frame/enabled 400
05/06/1983 06:06:33 0 Ethernet [01] Created Ethernet context object for card 1
05/06/1983 06:06:33 0 tRootTask [35] SysInit completed.
05/06/1983 06:06:33 0 tRootTask [35] ********************************************
05/06/1983 06:06:33 0 IPvfy.07becb50{Prv} [00] destructor called 0x7becb50
05/06/1983 06:06:33 0 Ethernet [13] Interface disabled on card 0
05/06/1983 06:06:33 0 Ethernet [13] Interface disabled on card 0
05/06/1983 06:06:33 0 FEI Driver [00] feiSetIfFlags: unit 0 linkup 1
05/06/1983 06:06:33 0 Ethernet [00] IpAddrChange: adding dev fei0 ip 192.168.1.2 subnet 255.255.255.0 result 0 OK
05/06/1983 06:06:33 0 Ethernet [00] IpAddrChange: New IPV dev fei0 ip 192.168.1.2 subnet 255.255.255.0 result OK
05/06/1983 06:06:33 0 IP Redirector [10] IntfAddrReg(192.168.1.2 255.255.255.0 0x7b76ec8 1500 1 1)
05/06/1983 06:06:33 0 IP Redirector [11] IntfAddrReg(192.168.1.2, 255.255.255.0): deleting old rt 0x7d00088 flags 0x101 pr 0 prio 0
05/06/1983 06:06:33 0 IP Redirector [10] IntfAddrReg(192.168.1.2 255.255.255.255 0x7bec7c0 1836 1 1)
05/06/1983 06:06:33 0 Ethernet [13] Interface enabled on card 0
05/06/1983 06:06:33 0 NocDynIP [12] CancelTimer: timer_cancel failed.
05/06/1983 06:07:13 0 tSerialConfig [37] Couldn't find name in tree 'BootObject.BootMode'
05/06/1983 06:07:35 0 tSerialConfig [37] Invalid IP address:

Anything else I can try?
 
Update: I resolved the problem by removing the add-on card that was included with the router (I did not require it anyway). The system now boots normally!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top