somebodyelse's profile

somebodyelse

New Contributor

 • 

4 Messages

Closed

Another multiple disconnect issue

This getting to be more than irritating as it's been going on for literally years and since the boost in speed has gotten worse.

I keep getting disconnected. I'll let the current log speak as it is representative of a common disconnect.  Now the apartment has had the cable coming in replaced and all of the equipment check and it's all good. This issue seems to be local to the build ing I am in. Modem i9s an SB6180

2014-02-08 12:26:52 3-Critical SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within ti
2014-02-08 12:26:49 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
2014-02-08 12:26:47 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 12:26:43 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
2014-02-08 12:26:41 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 12:26:27 5-Warning MDD message timeout;CM-MAC=a4:7a:a4:fe:b1:2e;CMTS-MAC=00:12:d9:54:8f:ce;CM-QOS=1
2014-02-08 12:26:27 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 12:26:11 5-Warning MDD message timeout;CM-MAC=a4:7a:a4:fe:b1:2e;CMTS-MAC=00:12:d9:54:8f:ce;CM-QOS=1
2014-02-08 12:26:10 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 12:26:05 5-Warning MDD message timeout;CM-MAC=a4:7a:a4:fe:b1:2e;CMTS-MAC=00:12:d9:54:8f:ce;CM-QOS=1
2014-02-08 12:26:05 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 12:25:39 5-Warning MDD message timeout;CM-MAC=a4:7a:a4:fe:b1:2e;CMTS-MAC=00:12:d9:54:8f:ce;CM-QOS=1
2014-02-08 12:25:22 5-Warning Dynamic Range Window violation
2014-02-08 12:25:13 6-Notice TLV-11 - unrecognized OID;CM-MAC=a4:7a:a4:fe:b1:2e;CMTS-MAC=00:12:d9:54:8f:ce;CM
2014-02-08 12:25:13 5-Warning DHCP WARNING - Non-critical field invalid in response ;CM-MAC=a4:7a:a4:fe:b1:2e;
2014-02-08 12:24:53 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 12:24:52 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
2014-02-08 12:23:50 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 12:23:48 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
2014-02-08 12:23:30 6-Notice Ds Lock Failed - Reinitialize MAC...
2014-02-08 12:23:30 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 12:23:26 6-Notice Ds Lock Failed - Reinitialize MAC...
2014-02-08 12:22:57 6-Notice TLV-11 - unrecognized OID;CM-MAC=a4:7a:a4:fe:b1:2e;CMTS-MAC=00:12:d9:54:8f:ce;CM
1970-01-01 00:03:02 5-Warning ToD request sent - No Response received;CM-MAC=a4:7a:a4:fe:b1:2e;CMTS-MAC=00:12:
1970-01-01 00:02:57 5-Warning DHCP WARNING - Non-critical field invalid in response ;CM-MAC=a4:7a:a4:fe:b1:2e;
1970-01-01 00:02:39 3-Critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=
1970-01-01 00:02:26 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
1970-01-01 00:02:07 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
1970-01-01 00:02:07 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
1970-01-01 00:01:56 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
1970-01-01 00:01:54 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
1970-01-01 00:01:52 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
1970-01-01 00:01:22 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
1970-01-01 00:01:21 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
1970-01-01 00:01:20 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
1970-01-01 00:00:14 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 11:44:25 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
2014-02-08 11:44:22 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2014-02-08 11:43:58 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
2014-02-08 11:43:56 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 11:43:38 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
2014-02-08 11:43:34 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 11:43:32 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
2014-02-08 11:42:36 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2014-02-08 11:42:36 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
2014-02-08 11:42:21 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2014-02-08 11:42:21 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
2014-02-08 11:42:19 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 11:42:17 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
2014-02-08 11:42:13 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 11:42:11 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2014-02-08 11:42:11 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
2014-02-08 11:41:44 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 11:41:40 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
2014-02-08 11:41:38 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 11:41:34 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
2014-02-08 11:41:07 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 11:40:59 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
2014-02-08 11:40:34 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
2014-02-08 11:40:16 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
2014-02-08 11:39:29 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
2014-02-08 11:38:49 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
2014-02-08 11:38:47 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 11:38:38 3-Critical TFTP Request Retries exceeded, CM unable to register
2014-02-08 11:38:12 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2014-02-08 11:36:12 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 11:36:10 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
2014-02-08 11:36:08 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 11:36:02 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2014-02-08 11:36:02 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 11:35:54 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
2014-02-08 11:34:54 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 11:34:52 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
2014-02-08 11:34:48 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 11:34:46 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 11:27:52 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 11:27:48 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 11:27:44 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
2014-02-08 11:17:57 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 11:17:33 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 11:17:29 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 11:10:25 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 11:06:09 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2014-02-08 11:03:46 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 11:01:05 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2014-02-08 10:56:13 3-Critical TFTP Request Retries exceeded, CM unable to register
2014-02-08 10:55:49 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2014-02-08 10:52:13 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 10:43:32 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2014-02-08 10:36:57 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
2014-02-08 10:35:49 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 10:35:45 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
2014-02-08 10:35:39 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 10:35:37 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 10:20:24 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 10:09:41 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
2014-02-08 10:09:37 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 10:09:31 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 10:09:26 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-08 10:09:14 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
 
©2004 Motorola   All rights reserved.

 And this is just for today.

Will someone get this fixed please? or tell me what I need to do to fix it.I am tired of calling the tech support as most of them seem to be just script readers with no real knowledge of networking.

Discussions

 • 

Updated 

3.3K

5

0

0

E

EdwardH

Valued Contributor

 • 

755 Messages

The signal levels to the modem do not show issues but I am seeing the power related resets on its logs which seem to match there. When the connection drops are you seeing the lights change with the modem and is the power cord going through a power strip or direct to the wall?
---

0

0

S

somebodyelse

New Contributor

 • 

4 Messages

Hey Edward,

The lights don't always change when the issues happen, Most of the time the modem seems to remain connected at least via the lights.

As to the power strip question, yes the power supply was plugged into a strip. I moved it to a wall socket.

Lee

0

0

S

somebodyelse

New Contributor

 • 

4 Messages

TiffanyR

it seemed to worked fine last night and earlier this morning. But starting around 11:30 or so, the being dropped started again and has continued since. Modem rebooted its self twice, all other times, I was kicked, but the modems lights showed no interrupt.

Procedure Status Comment
Acquire Downstream Channel 813000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Configuration File OK 102001_vm2.0_d.cfg
Security Enabled BPI+

Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 121 813000000 Hz -7.0 dBmV 36.5 dB 854438 281631
2 Locked QAM256 122 819000000 Hz -7.3 dBmV 36.5 dB 681278 168853
3 Locked QAM256 123 825000000 Hz -7.1 dBmV 36.3 dB 509958 51840
4 Locked QAM256 124 831000000 Hz -7.3 dBmV 36.5 dB 534068 66109
5 Locked QAM256 129 861000000 Hz -5.8 dBmV 37.5 dB 280448 7512
6 Locked QAM256 130 867000000 Hz -6.0 dBmV 37.5 dB 261816 5926
7 Locked QAM256 131 873000000 Hz -6.3 dBmV 36.9 dB 256544 4785
8 Locked QAM256 132 879000000 Hz -6.2 dBmV 37.5 dB 1272122 381383

Correctables Uncorrectables
854438 281631



Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked TDMA and ATDMA 1 2560 Ksym/sec 29988000 Hz 46.7 dBmV
2 Locked TDMA and ATDMA 2 2560 Ksym/sec 33313000 Hz 46.7 dBmV
3 Locked TDMA and ATDMA 3 2560 Ksym/sec 36638000 Hz 46.7 dBmV
4 Locked TDMA and ATDMA 4 2560 Ksym/sec 39963000 Hz 46.7 dBmV

CM IP Address Duration Expires
10.156.33.222 D: 01 H: 00 M: 00 S: 00

Mon Feb 10 14:33:24 2014
2014-02-09 14:38:03 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2014-02-09 14:38:03 5-Warning MDD message timeout;CM-MAC=a4:7a:a4:fe:b1:2e;CMTS-MAC=00:12:d9:54:8f:ce;CM-QOS=1
2014-02-09 14:37:27 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2014-02-09 14:35:59 5-Warning MDD message timeout;CM-MAC=a4:7a:a4:fe:b1:2e;CMTS-MAC=00:12:d9:54:8f:ce;CM-QOS=1
2014-02-09 14:35:53 3-Critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=
2014-02-09 14:35:48 5-Warning MDD message timeout;CM-MAC=a4:7a:a4:fe:b1:2e;CMTS-MAC=00:12:d9:54:8f:ce;CM-QOS=1
2014-02-09 14:35:47 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
2014-02-09 14:35:46 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-09 14:35:42 5-Warning MDD message timeout;CM-MAC=a4:7a:a4:fe:b1:2e;CMTS-MAC=00:12:d9:54:8f:ce;CM-QOS=1
2014-02-09 14:35:42 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a
2014-02-09 14:33:33 5-Warning Dynamic Range Window violation
2014-02-09 14:33:25 6-Notice TLV-11 - unrecognized OID;CM-MAC=a4:7a:a4:fe:b1:2e;CMTS-MAC=00:12:d9:54:8f:ce;CM
2014-02-09 14:33:25 5-Warning DHCP WARNING - Non-critical field invalid in response ;CM-MAC=a4:7a:a4:fe:b1:2e;
2014-02-09 14:33:03 6-Notice T4 No Station Maint Timeout - Reinitialize MAC...
2014-02-09 14:33:03 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o

Any help is appreaceated.

0

0

H

Health_Edge

+5 more

Valued Contributor III

 • 

4.2K Messages

That is ALOT of uncorrectables. When was your last reboot? I ask because that gives me the length of time those uncorrectable are over. I also notice more uncorrectables on the channels with lower signal levels on the downstream. Your levels are also slightly out of spec.  Feel like a piece of the puzzle is missing.

"Now the apartment has had the cable coming in replaced and all of the equipment check and it's all good. This issue seems to be local to the build ing I am in."

Could you give more data on that? Is it a large building? What makes you think its a wiring problem in the building? Can you describe how the cable wire gets from the street to your modem?

0

0

S

somebodyelse

New Contributor

 • 

4 Messages

@ Heath

reboot ~11:30 that morning.

The comment about the apartment being rewired - I am in a small 8 unit complex and 4 of the units are in  single building that includes mine. Over literally multiple years this build has had issues with connectivity. the 2 other buildings don't seem to have issues.

Cox has sent their contractors out multiple times, and at least 3 of the apartments ( including the one I'm in) has had the cable to the apartment replaced and still issues persist.

I never said it was a building wiring problem, I was saying the building has been rewired, so that should not be the issue.

"local to the building..." meant that neighbors not in this particular building don't seem to have a problem

As far as from street to modem Street into a splitter box to cable to wall plate to modem.

0

0