Community Forum

Cannot maintain a solid connnection

Highlighted
Frequent Visitor

Cannot maintain a solid connnection

Switched to gigabit about 6 weeks ago. Got docsys 3.1 modem about a month ago. it will not maintain a steady internet connection.  For about a week I had rocking speeds, then it's been downhill from there.  Connects for anywhere from 1-3 hours before it just starts falling off..  Every 10 -15minutes  I get this error message in the modem:

Mon Aug 17 07:53:35 2020Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;

 

This is a netgear CM1200.  There are a acouple of line tech who have been in my neighborhood looking at the A/B node and found noise everywhere and have been cleaning it up.  It has been suggested that there might be something on my ethernet side of things causing the issue however I get that same error message with NOTHING else attache to modem and rebooting.  A residentail technician came out to my house and verified everything inside the house, even came in and put in a new splitter (replacing the old splitter that they put in when we first moved here).

Here's the whole log:

Time Priority Description
Mon Aug 17 07:53:35 2020Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 17 07:50:31 2020Warning (5)Dynamic Range Window violation
Mon Aug 17 07:50:31 2020Warning (5)RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 17 07:50:26 2020Critical (3)SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 17 07:50:26 2020Notice (6)DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 17 07:50:21 2020Notice (6)TLV-11 - unrecognized OID;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 16 18:15:16 2020Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 16 18:14:49 2020Notice (6)DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 16 18:14:44 2020Notice (6)TLV-11 - unrecognized OID;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6
Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 16 18:04:24 2020Notice (6)CM-STATUS message sent. Event Type Code: 22; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 16 18:04:24 2020Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 16 18:04:24 2020Notice (6)CM-STATUS message sent. Event Type Code: 8; Chan ID: 2 3 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 16 18:04:22 2020Notice (6)CM-STATUS message sent. Event Type Code: 23; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 16 18:04:22 2020Notice (6)CM-STATUS message sent. Event Type Code: 22; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 16 18:04:20 2020Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 16 18:04:07 2020Critical (3)No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 16 18:04:07 2020Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 16 18:03:59 2020Critical (3)No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 16 18:03:47 2020Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 16 18:03:43 2020Critical (3)No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 16 18:03:43 2020Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 16 18:03:41 2020Critical (3)No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 16 18:03:28 2020Critical (3)SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 16 18:03:27 2020Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 16 18:03:17 2020Critical (3)No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 16 18:03:17 2020Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 16 18:03:16 2020Critical (3)No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 16 18:03:16 2020Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 16 18:03:11 2020Warning (5)MDD message timeout;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 16 18:03:11 2020Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 16 18:03:06 2020Critical (3)No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 16 18:01:07 2020Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 16 18:01:01 2020Critical (3)No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 16 17:59:38 2020Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 16 17:59:38 2020Critical (3)Ranging Request Retries exhausted;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;

 

Also this is the connection information: (You can see I rebooted the modem about 11 minutes ago)

Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1LockedQAM2565549000000 Hz-2.2 dBmV42.3 dB00
2LockedQAM2562531000000 Hz-2.1 dBmV42.3 dB00
3LockedQAM2563537000000 Hz-2.2 dBmV42.2 dB00
4LockedQAM2564543000000 Hz-2.3 dBmV42.2 dB00
5LockedQAM2566555000000 Hz-2 dBmV42.3 dB00
6LockedQAM2567561000000 Hz-2.2 dBmV42.3 dB00
7LockedQAM2568567000000 Hz-2.2 dBmV42.3 dB00
8LockedQAM2569573000000 Hz-2.3 dBmV42.3 dB00
9LockedQAM25610579000000 Hz-2.4 dBmV42.2 dB00
10LockedQAM25611585000000 Hz-2.4 dBmV42.2 dB00
11LockedQAM25612591000000 Hz-2.4 dBmV42.2 dB00
12LockedQAM25613597000000 Hz-2.5 dBmV42.2 dB00
13LockedQAM25614603000000 Hz-2.5 dBmV42.1 dB00
14LockedQAM25615609000000 Hz-2.6 dBmV42.1 dB00
15LockedQAM25616615000000 Hz-2.8 dBmV42.1 dB00
16LockedQAM25617621000000 Hz-2.6 dBmV42.1 dB00
17LockedQAM25618627000000 Hz-2.6 dBmV42.1 dB00
18LockedQAM25619633000000 Hz-2.6 dBmV42.1 dB00
19LockedQAM25620639000000 Hz-2.7 dBmV42 dB00
20LockedQAM25621645000000 Hz-2.5 dBmV42.1 dB00
21LockedQAM25622651000000 Hz-2.3 dBmV42.2 dB00
22LockedQAM25623657000000 Hz-2.4 dBmV42.2 dB00
23LockedQAM25624663000000 Hz-2.6 dBmV42 dB00
24LockedQAM25625669000000 Hz-2.5 dBmV42.1 dB00
25LockedQAM25626675000000 Hz-2.4 dBmV41.2 dB00
26LockedQAM25627681000000 Hz-2.2 dBmV42.2 dB00
27LockedQAM25628687000000 Hz-2.3 dBmV42.2 dB00
28LockedQAM25629693000000 Hz-2.4 dBmV42.3 dB00
29LockedQAM25630699000000 Hz-2.2 dBmV42.4 dB00
30LockedQAM25631705000000 Hz-2.3 dBmV42.2 dB00
31LockedQAM25633711000000 Hz-2.6 dBmV42.1 dB00
32Not LockedUnknown00 Hz0.0 dBmV0.0 dB00
 
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1LockedATDMA15120 Ksym/sec35600000 Hz44.8 dBmV
2LockedATDMA25120 Ksym/sec29200000 Hz45 dBmV
3LockedATDMA35120 Ksym/sec22800000 Hz45 dBmV
4LockedATDMA45120 Ksym/sec16400000 Hz45 dBmV
5LockedATDMA91280 Ksym/sec39600000 Hz42.5 dBmV
6Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV
7Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV
8Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV
 
Downstream OFDM Channels
Channel Lock
Status
Modulation /
Profile ID
Channel
ID
Frequency Power SNR /
MER
Active Subcarrier
Number Range
Unerrored
Codewords
Correctable
Codewords
Uncorrectable
Codewords
1Locked0 ,1 ,2 ,337762000000 Hz-2.7 dBmV41.9 dB1108 ~ 298766102701357540
2Not Locked000 Hz0 dBmV0.0 dB0 ~ 4095000
 
Upstream OFDMA Channels
Channel Lock Status Modulation / Profile ID Channel ID Frequency Power
1Not Locked000 Hz0 dBmV
2Not Locked000 Hz0 dBmV
 
Extended Upstream Transmit Power
Enable Extended Upstream Transmit Power
 
Current System Time:Mon Aug 17 08:01:17 2020
System Up Time:00:11:34
 
 
 
 
 
Highlighted
Frequent Visitor

Re: Cannot maintain a solid connnection

Continuing with more information:

 

The line techs have been busting their tail 100%.  They ran a new trunk line to the pedestal because their meter found a potential damaged spot about 80 feet down the line.  After replacing that, they also went to the amplifier, and actually replaced the amplifier and still no success here. Frustrated as I work from home and have to reboot modem every couple hours at minimum to get ANY kind of connectivity.

Highlighted
New Poster

Re: Cannot maintain a solid connnection

Im having the same issue with the same exact modem, got my service at the same exact time. Its really upsetting that Xfinity refuses to acknowledge its an issue with their firmware. They told me to just wait for it to fix itself essentially online while offering no compensation on my bill. Ive had line techs and in home techs out here and they are all clueless. Tier 2 tech on the phone also cant do anything. Im at a loss. They told me to replace my modem over the phone, but the techs that were here said not to and its an issue on their end but they don't know how to fix it.

Highlighted
Frequent Visitor

Re: Cannot maintain a solid connnection

We are getting closer....the line techs have been working feverishly on our entire neighborhood.  They have troubleshot SEVERAL noisy nodes in the area (including my own) and thru a couple weeks of the process of elimination, tonight we are trying a final test and things seem sto be working so far... we will see...

Highlighted
Frequent Visitor

Re: Cannot maintain a solid connnection

Well you aren't going to believe this....

Last night I tried 2 last ditch efforts. The first was to take the modem cable coming in and run it thru my UPs which hasa opto isolater that will run as 4gb speeds thinking that was take the noise off the line - however I found out later the opto isolater is only engaged under surge setting.  so i put it back to normal. ON A WHIM, I took my modem, laid it on it's side with the back pointing at the wirelss router (in this case it's a Netgear blackhawk R7000 but I will test with my archer 6000 later today)
Solid connectoin ALL night. No unicast errors. comcast had set up trending with YETI and noticed that the line was solid all night with NO alerts...

Might be on to something here... I find it hard to believe that something like this (the CM1200 from  netgear has NO shielding from wifi (it has no built in wifi).

More to come!!!

Highlighted
New Poster

Re: Cannot maintain a solid connnection

Hello, I'm having the same issue and I'm using the same modem, although my wireless router is a Netgear RAX200. Called Xfinity a number of times and I get the same diagnosis. Curious to see if this works.

Highlighted
Frequent Visitor

Re: Cannot maintain a solid connnection

I was very fortunate that the line tech (not the resi tech) gave my his phone number to contact him...we talkedthis morning and he's going to cut me a cable long enough to put the modem in another room so I can leave it standing up (also with 3 walls in between to block more wifi).

I am honestly astonished that this has solved hte problem so far...and astonished that a $220 modem doesn't have wifi rejection on it to stop it from happening in the first place...but, here we are!!!

I, as well as the line techs I'm talking to, would be interested if your works better this way too

Highlighted
Frequent Visitor

Re: Cannot maintain a solid connnection

Here are my logs since yesterday afternoon. You can see the "TIME NOT ESTABLISHED" is when I last rebooted and the follow up notes from 18:53 (6:53PM which is actally an hour off of real time) so at 8PM last night I rebooted the modem after flopping it on its side.  You can see all the unicast ranging errors below - they were hapening about every 5-15 minutes. have not had ONE error since the reboot ad laying on its side.  Every time that happened, 3 channels would stop monitoring, until it got down to a single channel running.

Time Priority Description
Wed Aug 19 18:53:58 2020Notice (6)DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 19 18:53:53 2020Notice (6)TLV-11 - unrecognized OID;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 19 18:47:47 2020Notice (6)DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 19 18:47:41 2020Notice (6)TLV-11 - unrecognized OID;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 19 18:40:54 2020Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 19 18:40:50 2020Notice (6)CM-STATUS message sent. Event Type Code: 23; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 19 18:40:46 2020Notice (6)CM-STATUS message sent. Event Type Code: 22; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 19 18:40:22 2020Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 19 18:39:25 2020Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 19 18:39:11 2020Warning (5)MDD message timeout;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 19 18:39:10 2020Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 19 18:39:04 2020Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 19 18:38:08 2020Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 19 17:23:44 2020Notice (6)DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 19 17:23:39 2020Notice (6)TLV-11 - unrecognized OID;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6
Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 19 17:21:22 2020Notice (6)DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 19 17:21:17 2020Notice (6)TLV-11 - unrecognized OID;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 19 16:43:09 2020Notice (6)DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 19 16:43:04 2020Notice (6)TLV-11 - unrecognized OID;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 19 15:30:58 2020Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:3f:87:18;CMTS-MAC=00:01:5c:a9:ba:5e;CM-QOS=1.1;CM-VER=3.1;



Highlighted
Frequent Visitor

Re: Cannot maintain a solid connnection

3 full days later,and my internet connection is rock solid....I am still finding it hard to believe that simply putting my modem on its side was the solution -

Going to test later this week by setting it up how it WAS and seeing if the errors come back