Tymtaker's profile

Frequent Visitor

 • 

16 Messages

Thu, Dec 3, 2020 1:00 PM

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 2020Critical (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 2020Notice (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 2020Critical (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 2020Notice (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 2020Notice (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 EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6
Time Not EstablishedCritical (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 EstablishedCritical (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 2020Notice (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 2020Notice (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 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: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 2020Notice (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 2020Notice (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 2020Notice (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 EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6
Time Not EstablishedCritical (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 EstablishedCritical (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 2020Notice (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 2020Notice (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 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:42:a0:e8;CMTS-MAC=00:00:00:00:00:00;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:42:a0:e8;CMTS-MAC=00:01:5c:86:b8:6a;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: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 2020Warning (5)Dynamic Range Window violation
Wed Dec 02 17:24:16 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: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 2020Warning (5)Dynamic Range Window violation
Wed Dec 02 17:24:16 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: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 2020Critical (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 2020Notice (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 2020Notice (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 EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6
Time Not EstablishedCritical (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 EstablishedCritical (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 2020Critical (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 2020Notice (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 2020Notice (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 EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6
Time Not EstablishedCritical (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
ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectablesUncorrectables
1LockedQAM2565507000000 Hz1.4 dBmV41.2 dB00
2LockedQAM2562489000000 Hz1 dBmV40.9 dB00
3LockedQAM2563495000000 Hz1 dBmV41 dB00
4LockedQAM2564501000000 Hz1.1 dBmV41.1 dB00
5LockedQAM2566513000000 Hz1.4 dBmV41.1 dB00
6LockedQAM2567519000000 Hz1.5 dBmV41.1 dB00
7LockedQAM2568525000000 Hz1.5 dBmV41 dB00
8LockedQAM2569531000000 Hz1.5 dBmV41 dB00
9LockedQAM25610537000000 Hz1.6 dBmV41.1 dB00
10LockedQAM25611543000000 Hz1.6 dBmV41.1 dB00
11LockedQAM25612549000000 Hz1.5 dBmV41.1 dB00
12LockedQAM25613555000000 Hz1.5 dBmV41 dB00
13LockedQAM25614561000000 Hz1.4 dBmV40.9 dB00
14LockedQAM25615567000000 Hz1.4 dBmV41 dB00
15LockedQAM25616573000000 Hz1.4 dBmV41 dB00
16LockedQAM25617579000000 Hz1.5 dBmV40.9 dB00
17LockedQAM25618585000000 Hz1.4 dBmV40.9 dB00
18LockedQAM25619591000000 Hz1.4 dBmV40.7 dB00
19LockedQAM25620597000000 Hz1.5 dBmV40.7 dB00
20LockedQAM25621603000000 Hz1.4 dBmV40.6 dB00
21LockedQAM25622609000000 Hz1.2 dBmV40.4 dB00
22LockedQAM25623615000000 Hz1.1 dBmV40.3 dB00
23LockedQAM25624621000000 Hz1.3 dBmV40.3 dB00
24LockedQAM25626627000000 Hz1.2 dBmV40.3 dB00
25LockedQAM25627633000000 Hz1.3 dBmV40.4 dB00
26LockedQAM25628639000000 Hz1.1 dBmV40.3 dB00
27LockedQAM25629645000000 Hz1.3 dBmV40.4 dB00
28LockedQAM25630651000000 Hz1.2 dBmV40.3 dB00
29LockedQAM25631657000000 Hz1.2 dBmV40.3 dB00
30LockedQAM25632663000000 Hz1.3 dBmV40.4 dB00
31LockedQAM25633669000000 Hz1.3 dBmV40.4 dB00
32Not LockedUnknown00 Hz0.0 dBmV0.0 dB00
 
Upstream Bonded Channels
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedATDMA15120 Ksym/sec35600000 Hz45.8 dBmV
2LockedATDMA25120 Ksym/sec29200000 Hz45.3 dBmV
3LockedATDMA35120 Ksym/sec22800000 Hz44.5 dBmV
4LockedATDMA45120 Ksym/sec16400000 Hz44.3 dBmV
5Not LockedUnknown00 Ksym/sec0 Hz0.0 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
ChannelLock
Status
Modulation /
Profile ID
Channel
ID
FrequencyPowerSNR /
MER
Active Subcarrier
Number Range
Unerrored
Codewords
Correctable
Codewords
Uncorrectable
Codewords
1Locked0 ,1 ,2 ,337690000000 Hz2.2 dBmV40.1 dB1228 ~ 28675892418213539705440
2Not Locked000 Hz0 dBmV0.0 dB0 ~ 4095000
 
Upstream OFDMA Channels
ChannelLock StatusModulation / Profile IDChannel IDFrequencyPower
1Not Locked000 Hz0 dBmV
2Not Locked000 Hz0 dBmV

 

 

Responses

Tymtaker

Frequent Visitor

 • 

16 Messages

7 m 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. 

Tymtaker

Frequent Visitor

 • 

16 Messages

7 m ago

No one has any thoughts / ideas?

EG

Expert

 • 

87.2K Messages

7 m 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 !

Tymtaker

Frequent Visitor

 • 

16 Messages

7 m 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?!

New Poster

 • 

1 Message

7 m 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.

Official Employee

 • 

2.5K Messages

7 m 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.

 
To send a private message, please click my name "ComcastMorgan" then select "Send a Message" on the right side.  
 
Thanks!
 
Tymtaker

Frequent Visitor

 • 

16 Messages

7 m ago

Message has been sent. 

Official Employee

 • 

2.5K Messages

7 m ago

I just got your private message, Tymtaker. Thanks so much for your patience. I will respond shortly!

Tymtaker

Frequent Visitor

 • 

16 Messages

6 m ago

Let us all know what your results are! 

Frequent Visitor

 • 

6 Messages

6 m ago

Figures the day after I order the xb7 I had zero errors all day... had them for weeks. Xb7 set to arrive today. Do I go through the trouble of hooking it up or not lol. I guess we will see how today’s homeschooling zooms go 🤷‍♂️
Tymtaker

Frequent Visitor

 • 

16 Messages

6 m 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. 

Visitor

 • 

1 Message

Tymtaker,  Was anything resolved with your query.  I am now getting the very same event log entries. on my Netgear device. C7800.

EG

Expert

 • 

87.2K Messages

@annw89 

Please create a new topic of your own here on this board detailing your issue. Thanks. 5-month-old dead thread now being closed.

New to the Community?

Start Here