Quantcast
Channel: Basic Internet Connectivity And Modem Help topics
Viewing all articles
Browse latest Browse all 12065

Constant connection drops for 2 days

$
0
0

My internet and phone access have generally been rock solid for the past few years. However, since being upgraded freom 25mbpbs to 105mbps service earlier this week, I've noticed continually degrading service - the first night it was fine, but since the night before last I lose internet and phone service several times an hour. Since this morning my modem has been rebooting constantly as well. The first page of logs in the modem (TC8305C) looks like this:

 

Fri Apr 04 10:23:30 2014Warning (5) MDD message timeout;CM-MAC=88:f7:c7:31:4f:8d;CMTS-MAC=00:01:5c:31:4b:c4;CM-QOS=1.1;CM-VER=3.0;
Fri Apr 04 10:20:04 2014Notice (6) TLV-11 - unrecognized OID;CM-MAC=88:f7:c7:31:4f:8d;CMTS-MAC=00:01:5c:31:4b:c4;CM-QOS=1.1;CM-VER=3.0;
Fri Apr 04 10:19:54 2014Notice (6) Honoring MDD; IP provisioning mode = IPv6
Fri Apr 04 10:19:44 2014Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=88:f7:c7:31:4f:8d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Apr 04 10:19:35 2014Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=88:f7:c7:31:4f:8d;CMTS-MAC=00:01:5c:31:4b:c4;CM-QOS=1.1;CM-VER=3.0;
Fri Apr 04 10:19:35 2014Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=88:f7:c7:31:4f:8d;CMTS-MAC=00:01:5c:31:4b:c4;CM-QOS=1.1;CM-VER=3.0;
Fri Apr 04 10:19:28 2014Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=88:f7:c7:31:4f:8d;CMTS-MAC=00:01:5c:31:4b:c4;CM-QOS=1.1;CM-VER=3.0;
Fri Apr 04 10:19:28 2014Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=88:f7:c7:31:4f:8d;CMTS-MAC=00:01:5c:31:4b:c4;CM-QOS=1.1;CM-VER=3.0;
Fri Apr 04 10:19:05 2014Warning (5) MDD message timeout;CM-MAC=88:f7:c7:31:4f:8d;CMTS-MAC=00:01:5c:31:4b:c4;CM-QOS=1.1;CM-VER=3.0;
Fri Apr 04 10:19:02 2014Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=88:f7:c7:31:4f:8d;CMTS-MAC=00:01:5c:31:4b:c4;CM-QOS=1.1;CM-VER=3.0;
Fri Apr 04 10:18:45 2014Warning (5) MDD message timeout;CM-MAC=88:f7:c7:31:4f:8d;CMTS-MAC=00:01:5c:31:4b:c4;CM-QOS=1.1;CM-VER=3.0;
Fri Apr 04 10:18:35 2014Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=88:f7:c7:31:4f:8d;CMTS-MAC=00:01:5c:31:4b:c4;CM-QOS=1.1;CM-VER=3.0;
Fri Apr 04 10:18:23 2014Warning (5) MDD message timeout;CM-MAC=88:f7:c7:31:4f:8d;CMTS-MAC=00:01:5c:31:4b:c4;CM-QOS=1.1;CM-VER=3.0;
Fri Apr 04 10:18:09 2014Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=88:f7:c7:31:4f:8d;CMTS-MAC=00:01:5c:31:4b:c4;CM-QOS=1.1;CM-VER=3.0;
Fri Apr 04 10:14:16 2014Warning (5) MDD message timeout;CM-MAC=88:f7:c7:31:4f:8d;CMTS-MAC=00:01:5c:31:4b:c4;CM-QOS=1.1;CM-VER=3.0;
Fri Apr 04 10:13:48 2014Notice (6) TLV-11 - unrecognized OID;CM-MAC=88:f7:c7:31:4f:8d;CMTS-MAC=00:01:5c:31:4b:c4;CM-QOS=1.1;CM-VER=3.0;
Fri Apr 04 10:13:32 2014Notice (6) Honoring MDD; IP provisioning mode = IPv6
Fri Apr 04 10:13:20 2014Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=88:f7:c7:31:4f:8d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Apr 04 10:13:10 2014Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=88:f7:c7:31:4f:8d;CMTS-MAC=00:01:5c:31:4b:c4;CM-QOS=1.1;CM-VER=3.0;
Fri Apr 04 10:13:10 2014Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=88:f7:c7:31:4f:8d;CMTS-MAC=00:01:5c:31:4b:c4;CM-QOS=1.1;CM-VER=3.0;
Fri Apr 04 10:13:08 2014Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=88:f7:c7:31:4f:8d;CMTS-MAC=00:01:5c:31:4b:c4;CM-QOS=1.1;CM-VER=3.0;
Fri Apr 04 10:13:08 2014Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=88:f7:c7:31:4f:8d;CMTS-MAC=00:01:5c:31:4b:c4;CM-QOS=1.1;CM-VER=3.0;
Fri Apr 04 10:13:02 2014Warning (5) MDD message timeout;CM-MAC=88:f7:c7:31:4f:8d;CMTS-MAC=00:01:5c:31:4b:c4;CM-QOS=1.1;CM-VER=3.0;
Fri Apr 04 10:13:02 2014Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=88:f7:c7:31:4f:8d;CMTS-MAC=00:01:5c:31:4b:c4;CM-QOS=1.1;CM-VER=3.0;
Fri Apr 04 10:13:01 2014Warning (5) MDD message timeout;CM-MAC=88:f7:c7:31:4f:8d;CMTS-MAC=00:01:5c:31:4b:c4;CM-QOS=1.1;CM-VER=3.0;

 

And the signal strength looks like this:

 

Downstream Channel Bonding ValueIndexLock StatusFrequencySNRPowerModulation

12345678
LockedLockedLockedLockedLockedLockedLockedLocked
597 MHz573 MHz579 MHz585 MHz591 MHz603 MHz609 MHz615 MHz
28.4 dB32.4 dB31.9 dB31.1 dB30.7 dB0.0 dB0.0 dB0.0 dB
-18.2 dBmV-13.9 dBmV-14.4 dBmV-15.2 dBmV-15.8 dBmV3.3 dBmV-21.6 dBmV-21.5 dBmV
256QAM256QAM256QAM256QAM256QAMunknownunknownunknown
Upstream Channel Bonding ValueIndexLock StatusFrequencySymbol RatePower LevelModulationChannel ID
1234
LockedLockedLockedNot locked
21 MHz34 MHz27 MHz 
5120 Ksym/sec5120 Ksym/sec5120 Ksym/sec 
44.3 dBmV44.3 dBmV44.3 dBmV 
ATDMAATDMAATDMA 
121011 

 

Thoughts? Is this some wider service issue or is my signal quality not up to a reliable connection at 105mbps? It tests great... when it works.


Viewing all articles
Browse latest Browse all 12065

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>