Contributor
•
16 Messages
Started Unicast Maintenance Ranging, No Response received, T3 time-out
I have been having problems with our internet for about 2 weeks now with multiple connection losses a day and high packet loss via tracert 8.8.8.8. with the 2nd hop ongoing timing out. Been back and forth with xfinity support which is your typical customer support 101. Unplug this, reset that, let me send a signal to check the modem health......I had a tech come out to the house, he checked the lines at the pole, outside the house, and inside the house and said everything looked good. Im assuming there wasnt a problem at that given time. I have a CM1200 modem with a ubiquiti home network, all brand new. I finally logged into my modem and found these error messages......Does anything look off with the streams or channels? Thanks in advance!
Thu Dec 03 16:38:03 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:42:a0:e8;CMTS-MAC=00:01:5c:86:b8:6a;CM-QOS=1.1;CM-VER=3.1; |
Wed Dec 02 18:47:48 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:42:a0:e8;CMTS-MAC=00:01:5c:86:b8:6a;CM-QOS=1.1;CM-VER=3.1; |
Wed Dec 02 18:47:33 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:42:a0:e8;CMTS-MAC=00:01:5c:86:b8:6a;CM-QOS=1.1;CM-VER=3.1; |
Wed Dec 02 18:47:26 2020 | Notice (6) | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:42:a0:e8;CMTS-MAC=00:01:5c:86:b8:6a;CM-QOS=1.1;CM-VER=3.1; |
Wed Dec 02 18:47:20 2020 | Notice (6) | TLV-11 - unrecognized OID;CM-MAC=08:36:c9:42:a0:e8;CMTS-MAC=00:01:5c:86:b8:6a;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:42:a0:e8;CMTS-MAC=00:01:5c:86:b8:6a;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:42:a0:e8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Wed Dec 02 18:05:18 2020 | Notice (6) | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:42:a0:e8;CMTS-MAC=00:01:5c:86:b8:6a;CM-QOS=1.1;CM-VER=3.1; |
Wed Dec 02 18:05:13 2020 | Notice (6) | TLV-11 - unrecognized OID;CM-MAC=08:36:c9:42:a0:e8;CMTS-MAC=00:01:5c:86:b8:6a;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:42:a0:e8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Wed Dec 02 17:57:17 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:42:a0:e8;CMTS-MAC=00:01:5c:86:b8:6a;CM-QOS=1.1;CM-VER=3.1; |
Wed Dec 02 17:57:03 2020 | Notice (6) | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:42:a0:e8;CMTS-MAC=00:01:5c:86:b8:6a;CM-QOS=1.1;CM-VER=3.1; |
Wed Dec 02 17:56:57 2020 | Notice (6) | TLV-11 - unrecognized OID;CM-MAC=08:36:c9:42:a0:e8;CMTS-MAC=00:01:5c:86:b8:6a;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:42:a0:e8;CMTS-MAC=00:01:5c:86:b8:6a;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:42:a0:e8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Wed Dec 02 17:54:17 2020 | Notice (6) | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:42:a0:e8;CMTS-MAC=00:01:5c:86:b8:6a;CM-QOS=1.1;CM-VER=3.1; |
Wed Dec 02 17:54:12 2020 | Notice (6) | TLV-11 - unrecognized OID;CM-MAC=08:36:c9:42:a0:e8;CMTS-MAC=00:01:5c:86:b8:6a;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:42:a0:e8;CMTS-MAC=00:00:00:00:00:00;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:42:a0:e8;CMTS-MAC=00:01:5c:86:b8:6a;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:42:a0:e8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Wed Dec 02 17:24:16 2020 | Warning (5) | Dynamic Range Window violation |
Wed Dec 02 17:24:16 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:42:a0:e8;CMTS-MAC=00:01:5c:86:b8:6a;CM-QOS=1.1;CM-VER=3.1; |
Wed Dec 02 17:24:16 2020 | Warning (5) | Dynamic Range Window violation |
Wed Dec 02 17:24:16 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:42:a0:e8;CMTS-MAC=00:01:5c:86:b8:6a;CM-QOS=1.1;CM-VER=3.1; |
Wed Dec 02 17:24:11 2020 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=08:36:c9:42:a0:e8;CMTS-MAC=00:01:5c:86:b8:6a;CM-QOS=1.1;CM-VER=3.1; |
Wed Dec 02 17:24:11 2020 | Notice (6) | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:42:a0:e8;CMTS-MAC=00:01:5c:86:b8:6a;CM-QOS=1.1;CM-VER=3.1; |
Wed Dec 02 17:24:06 2020 | Notice (6) | TLV-11 - unrecognized OID;CM-MAC=08:36:c9:42:a0:e8;CMTS-MAC=00:01:5c:86:b8:6a;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:42:a0:e8;CMTS-MAC=00:01:5c:86:b8:6a;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:42:a0:e8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Wed Dec 02 16:46:31 2020 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=08:36:c9:42:a0:e8;CMTS-MAC=00:01:5c:86:b8:6a;CM-QOS=1.1;CM-VER=3.1; |
Wed Dec 02 16:46:31 2020 | Notice (6) | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:42:a0:e8;CMTS-MAC=00:01:5c:86:b8:6a;CM-QOS=1.1;CM-VER=3.1; |
Wed Dec 02 16:46:26 2020 | Notice (6) | TLV-11 - unrecognized OID;CM-MAC=08:36:c9:42:a0:e8;CMTS-MAC=00:01:5c:86:b8:6a;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:42:a0:e8;CMTS-MAC=00:01:5c:86:b8:6a;CM-QOS=1.1;CM-VER=3.1; |
Downstream Bonded Channels | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Upstream Bonded Channels | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Downstream OFDM Channels | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Upstream OFDMA Channels | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Tymtaker
Contributor
•
16 Messages
5 years ago
Just had a Tech out this morning to check the lines and signal levels. He said everything was good and that he was going to mark this as a "NSA" and try to esclate it to the pole/line crew to check the area. Does anyone have any ideas? Ive seen and read lots of people having this same problem but rarely see a thread on this forum with a confirmed fix / solution.
0
0
Tymtaker
Contributor
•
16 Messages
5 years ago
No one has any thoughts / ideas?
0
0
EG
Expert
•
111.7K Messages
5 years ago
Even though the signal stats looked o/k at that snapshot in time, the error log entries confirm that something is going on. Perhaps there is noise ingress into the line(s) somewhere.
There are other signal stat figures that can't be read by the modem. They are the "Upstream Rx Power" (Upstream Receive Power Level), the "Upstream SNR Ch." (Upstream Signal To Noise Ratio), and the "Upstream ICFR" (In Channel Frequency Response). These are as equally important in diagnosing connectivity issues as are the modem's stats.
I'm going to escalate your issue to the Comcast corporate employees that are available to these boards. They can check the CMTS (Cable Modem Termination System) for any real time degradation and / or error reports, see your node / cable plant and modem health, and see whether or not everything is in the green zone. They can also see a history plot for the modem and poll for those upstream receive signal stats.
You should get a reply here in your topic. Good luck !
0
0
Tymtaker
Contributor
•
16 Messages
5 years ago
So im trying an xfinity modem free for one month (xb7) to see if I still have the same problems since they keep insisting its my netgear modem. The funny thing is, I researched on the event logs on their modems and how xfinity disabled that feature for people awhile back. Now when I log into the xfinity modem, I cant see any information. So how am I suppose to monitor this issue ive been having?! Good thing is, my Ubiquiti home network still lists all the errors that I have. Still having a TON of high TCP issues and low bandwidth. Anyone else having the same issues?!
0
pmerillat
New Poster
•
1 Message
5 years ago
Having the same issue with a Motorola MB8600. Started yesterday, did an hour of troubleshooting with them. Claimed no issues in the area., suggested I get a rental from them. An hour later notification of an outage/maintenance in the area. Seven hours later the problem was resolved, now back again today. Contacted support to let them know, wanted to spend another hour of my life to tell me no issues again. SMH.
0
0
CCMorgan
Gold Problem Solver
•
3.3K Messages
5 years ago
Hi there, Tymtaker. We can step in and take a look at what might be causing the problems. We know how frustrating timeouts can be! To get started, please send me a PM with your first and last name. We can go from there.
0
Tymtaker
Contributor
•
16 Messages
5 years ago
Message has been sent.
0
0
CCMorgan
Gold Problem Solver
•
3.3K Messages
5 years ago
I just got your private message, Tymtaker. Thanks so much for your patience. I will respond shortly!
0
0
Tymtaker
Contributor
•
16 Messages
5 years ago
Let us all know what your results are!
0
0
Jdsmitty10
Frequent Visitor
•
6 Messages
5 years ago
0
0
Tymtaker
Contributor
•
16 Messages
5 years ago
Its still worth a shot. Just remember when you get the x7 modem, you wont be able to track / monitor any of the errors since xfinity disabled that feature. Which is a big no no IMO.
2
0