Frequent Visitor
•
14 Messages
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 2020 | Critical (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 2020 | Critical (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 2020 | Warning (5) | Dynamic Range Window violation |
Mon Aug 17 07:50:31 2020 | Warning (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 2020 | Critical (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 2020 | Notice (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 2020 | Notice (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 Established | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
Time Not Established | Critical (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 Established | Critical (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 2020 | Critical (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 2020 | Notice (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 2020 | Notice (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 Established | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
Time Not Established | Critical (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 2020 | Notice (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 2020 | Notice (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 2020 | Notice (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 2020 | Notice (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 2020 | Notice (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 2020 | Critical (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 2020 | Critical (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 2020 | Critical (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 2020 | Critical (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 2020 | Critical (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 2020 | Critical (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 2020 | Critical (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 2020 | Critical (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 2020 | Critical (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 2020 | Critical (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 2020 | Critical (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 2020 | Critical (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 2020 | Critical (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 2020 | Critical (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 2020 | Warning (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 2020 | Critical (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 2020 | Critical (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 2020 | Critical (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 2020 | Critical (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 2020 | Critical (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 2020 | Critical (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 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Upstream Bonded Channels | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Downstream OFDM Channels | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Upstream OFDMA Channels | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
drbob2112
Frequent Visitor
•
14 Messages
5 years ago
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.
0
0
pugzinho
New Poster
•
3 Messages
5 years ago
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.
0
drbob2112
Frequent Visitor
•
14 Messages
5 years ago
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...
0
drbob2112
Frequent Visitor
•
14 Messages
5 years ago
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!!!
0
drbob2112
Frequent Visitor
•
14 Messages
5 years ago
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.
0
0
drbob2112
Frequent Visitor
•
14 Messages
5 years ago
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
0
0
PhoenixSeven
New Poster
•
1 Message
5 years ago
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.
0
0
drbob2112
Frequent Visitor
•
14 Messages
5 years ago
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
0
0