SanJoseNerd
Premium
join:2002-07-24
San Jose, CA
| Possible DSL failure in 3220H
I need help diagnosing a possible problem with my 3220H. It was working fine, then I had to unplug the phone cord for a moment. When I plugged it back in, it never synced again. (Tried all the usual stuff, rebooted, etc.)
The thing is, it looks to me that the Cayman isn't even trying to sync. When I power on, the DSL and Status lights each blink twice -- and that's it. I'm wondering if the DSL chipset has died.
The home screen says "Waiting for DSL". Below is the entire log. As you see, after "Starting operational code", nothing happens.
What's your opinion -- do I need a new Cayman?
---------
Message Log:
00:00:00:00 L3 LIC: Granting licenses for legacy software features
00:00:00:00 L3 BR: No wireless hardware detected
00:00:00:00 L4 BR: Using saved configuration options
00:00:00:00 L4 GDB: PowerPC gdbnub debugger is not installed
00:00:00:00 L4 BR: Cayman OS version 6.3.0 (build R2)
00:00:00:00 L4 BR: Cayman-DSL1744229 (Cayman-DSL, rev 1), PID 0829
00:00:00:00 L4 BR: last install status: code flash successfully programmed
00:00:00:00 L4 BR: memory sizes - 1536K Flash, 4096K RAM
00:00:00:00 L4 BR: free memory: 1077998 bytes, starting at 0x2f8d02
00:00:00:00 L4 BR: restart not in response to admin command
00:00:00:00 L4 BR: bootFlags: 0x0, running in RAM
00:00:00:00 L4 BR: image 0 booted from flash
00:00:00:00 L4 BR: this image was started by the Boot PROM
00:00:00:00 L3 BR: Starting kernel
00:00:00:00 L4 ED: Initializing Ethernet Device 1, Type QUICC
00:00:00:00 L4 ED: Initializing Ethernet Device 2, Type RFC1483
00:00:00:00 L4 KS: Reclaiming 73900 bytes of proxim driver code
00:00:00:00 L4 KS: Reclaiming 27608 bytes of 80211 driver code
00:00:00:00 L4 KS: Reclaiming 38672 bytes of 80211 firmware
00:00:00:00 L3 AAL5: initializing service
00:00:00:01 L4 ATM: Waiting for PHY layer to come up
00:00:00:01 L3 POE: Disabling PPP over Ethernet service (not in use)
00:00:00:01 L3 BRDG: Bridge not enabled.
00:00:00:01 L4 IP: Routing between WAN ports is disabled
00:00:00:01 L4 IP: IPSec client pass through is enabled
00:00:00:01 L4 IP: Address mapping enabled on interface ENET (ether/vcc1)
00:00:00:01 L3 IP: Adding default gateway at IP address XX.XXX.XXX.XXX
00:00:00:01 L3 IP: Initialization complete
00:00:00:01 L3 IP: (10BT-LAN) Ethernet Physical Link Active
00:00:00:01 L3 IP: (ether/vcc1) Ethernet Physical Link Down
00:00:00:01 L3 IP: (10BT-LAN) IP Protocol Up
00:00:00:01 L3 BS: No download configuration files required.
00:00:00:01 L3 RIP: initializing
00:00:00:01 L3 DHCP: Initializing Service
00:00:00:01 L3 DHCP: Setup Server On UDP Port 67
00:00:00:01 L3 DHCP: Setup Client On UDP Port 68
00:00:00:01 L3 DNS: initializing service
00:00:00:01 L3 HTTP: Start AllegroTaskInit
00:00:00:01 L3 HTTP: AllegroTaskInit succeeds
00:00:00:01 L3 IPSec: initializing service
00:00:00:01 L3 IPSec: No feature key available - service disabled
00:00:00:01 L3 FW: initializing service
00:00:00:01 L3 FW: No feature key available - basic firewall service disabled
00:00:00:01 L3 SNMP: initializing service over UDP
00:00:00:01 L3 DIA: Diagnostics service initializing
00:00:00:01 L4 All services initialized, starting Scheduler
00:00:00:03 L3 DHCP: Startup NVRAM Lease table is ok
00:00:00:05 L4 DSL: Init Code Started
00:00:00:05 L4 DSL: Starting Operational Code
00:00:00:38 L4 HTTP: "Admin" completed login from 192.168.1.1 |
|
LBB
Premium,MVM
join:2001-06-14
Bama | Did you plug it back into the same phone jack after the move?
LB |
|
SanJoseNerd
Premium
join:2002-07-24
San Jose, CA
| said by LBB  :
Did you plug it back into the same phone jack after the move?
LB
Yes.
Update: After about 3 hours, it suddenly started syncing again. Right now it's working fine. I'll keep my fingers crossed that it was just some weird temporary hiccup and that it will keep working. |
|
LBB
Premium,MVM
join:2001-06-14
Bama | reply to SanJoseNerd
Cool, don't you just love it when things fixes itself!
LB |
|
