Loss of Connectivity / Modem Dying or Dead

cableguy3 · 07-07-2008, 13:08

Over the last week I have been getting slow or no connection on my Broadband connection. I originally thought maybe it was a simple loose connection etc but looking at my Modem logs I had a few errors such as ToD Failed. Some of the errors look to be related to it not keeping time etc and possibly a forced update from VM to the modem which was not for its model type.

I have ordered a new modem to be safe and as I had this one for about 7 years so a new one is probably a good idea.

Check out the logs from the modem after a hard reset:

************ 4-Error D4.3 ToD request sent - No Response received
************ 7-Information M569.1 Exiting standby mode
************ 7-Information H501.6 HFC: TRC SYNC Recovery OK
************ 3-Critical H501.4 HFC: LOST TRC SYNC- trying to recover
************ 7-Information H501.12 HFC: FEC LOCK recovery OK
************ 7-Information H501.15 HFC:FEC LOCK recovery OK
************ 3-Critical H501.16 HFC: FEC LOCK recovery failed
************ 3-Critical T5.0 SYNC Timing Synchronization failure - Loss of Sync
************ 7-Information H501.6 HFC: TRC SYNC Recovery OK
************ 3-Critical H501.4 HFC: LOST TRC SYNC- trying to recover
************ 7-Information H501.12 HFC: FEC LOCK recovery OK
************ 7-Information H501.15 HFC:FEC LOCK recovery OK
************ 3-Critical T5.0 SYNC Timing Synchronization failure - Loss of Sync
************ 7-Information H501.6 HFC: TRC SYNC Recovery OK
************ 3-Critical H501.4 HFC: LOST TRC SYNC- trying to recover
************ 7-Information H501.12 HFC: FEC LOCK recovery OK
************ 7-Information H501.15 HFC:FEC LOCK recovery OK
************ 3-Critical T5.0 SYNC Timing Synchronization failure - Loss of Sync
************ 4-Error D4.3 ToD request sent - No Response received
************ 7-Information M569.1 Exiting standby mode
************ 4-Error D4.3 ToD request sent - No Response received
************ 8-Debug F504.1 Bridge Ethernet Hook. Failed to learn CPE MAC Address.
************ 4-Error F507.5 MAC Filters. Add MAC Address can't add entry. Table is full.
************ 4-Error D4.3 ToD request sent - No Response received
************ 7-Information M569.1 Exiting standby mode
************ 4-Error D4.3 ToD request sent - No Response received
************ 4-Error X501.35 Unit Update Failed.
************ 8-Debug F502.1 Bridge Forwarding Enabled.
************ 4-Error E107.0 SW Upgrade Failed after download - Incompatible SW file
************ 4-Error X501.28 Unit Update - Not updating. This image is not for this platform.
************ 8-Debug M579.3 CM Cert Upgrade Disabled. Motorola CM certificate present
************ 8-Debug F502.2 Bridge Forwarding Disabled.
************ 7-Information X500.0 Attempting Unit Update
************ 6-Notice E102.0 SW Download INIT - Via Config file cm-20480-768
************ 8-Debug I503.0 Cable Modem is OPERATIONAL
************ 8-Debug F502.1 Bridge Forwarding Enabled.
************ 8-Debug F502.3 Bridge Learning Enabled.
************ 8-Debug B918.0 Baseline Privacy is skipped
************ 6-Notice I401.0 TLV-11 - unrecognized OID
************ 6-Notice D501.10 TFTP, Unknown SNMP 30 11 06 0C 2B 06 01 04 01 8B 15 4D 01 03 08 00
************ 6-Notice I401.0 TLV-11 - unrecognized OID
************ 6-Notice D501.10 TFTP, Unknown SNMP 30 15 06 10 2B 06 01 04 01 A2 3D 02 63 01 01 02
************ 6-Notice I401.0 TLV-11 - unrecognized OID
************ 6-Notice D501.10 TFTP, Unknown SNMP 30 11 06 0C 2B 06 01 04 01 8B 15 4D 01 03 02 00
************ 7-Information X519.8 Unit Update - MMFMMD - SCD flags
************ 8-Debug I500.1 DOCSIS 1.0 Registration Completed
************ 7-Information I500.4 Attempting DOCSIS 1.0 Registration
************ 7-Information D509.0 Retrieved TFTP Config File SUCCESS
************ 7-Information D507.1 Retrieved Time....... FAILED
************ 5-Warning D4.1 ToD request sent - No Response received
************ 7-Information D511.0 Retrieved DHCP .......... SUCCESS
************ 5-Warning D3.0 DHCP WARNING - Non-critical field invalid in response
************ 4-Error D530.8 DHCP - Invalid Log Server IP Address.
************ 4-Error D530.6 DHCP - Invalid Time Offset.
************ 5-Warning D520.2 DHCP Attempt# 3 BkOff: 5s Tot DSC:3 OFF:1 REQ:1 ACK:1
************ 3-Critical D1.0 DHCP FAILED - Discover sent, no offer received
************ 5-Warning D520.2 DHCP Attempt# 1 BkOff: 4s Tot DSC:1 OFF:0 REQ:0 ACK:0
************ 3-Critical D1.0 DHCP FAILED - Discover sent, no offer received
************ 7-Information D0.0 DHCP CM Net Configuration download and Time of Day
************ 7-Information T500.0 Acquired Upstream .......... SUCCESS
************ 8-Debug T503.1 Acquire US with status OK, powerLevel 54, tempSid 961
************ 8-Debug T505.0 Acquired Upstream with status OK
************ 7-Information T501.0 Acquired Downstream (331000000 Hz)........ SUCCESS
************ 8-Debug T509.0 Acquired DS with status OK, DS Freq 331000000, US Id 4
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 307000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 299000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 291000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 283000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 275000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 267000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 259000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 251000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 243000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 235000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 227000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 219000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 211000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 203000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 195000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 187000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 179000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 171000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 163000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 155000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 147000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 139000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 131000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 123000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 115000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 107000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 99000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 91000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 857000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 849000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 841000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 833000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 825000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 817000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 809000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 801000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 793000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 785000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 777000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 769000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 761000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 753000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 745000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 737000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 729000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 721000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 713000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 705000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 697000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 689000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 681000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 673000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 665000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 657000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing

sstainer · 07-07-2008, 13:15

blimey thats a large error log as u said best bet is new modem suspect its on it last legs tbh, but could be wrong

cableguy3 · 07-07-2008, 13:28

yep, I reckon it is dead or dying.

07-07-2008, 21:24

Quote:

Originally Posted by cableguy3

yep, I reckon it is dead or dying.

I usually say ignore modem logs but yours is one of the few that you cannot ignore.

TOD on most Virgin modems no longer works.

What modem is that by the way, is it a Motorola.

r00t · 07-07-2008, 21:28

Quote:

Originally Posted by whydoIneedatech

What modem is that by the way, is it a Motorola.

8-Debug M579.3 CM Cert Upgrade Disabled. Motorola CM certificate present

I'd say Motorola

07-07-2008, 21:30

Quote:

Originally Posted by r00t

8-Debug M579.3 CM Cert Upgrade Disabled. Motorola CM certificate present

I'd say Motorola

Methinks I did not look closely