Community Forum

Supposed to have 15 up, but during day it's more like 1-3 up tons Ranging Response issues

Highlighted
Regular Visitor

Supposed to have 15 up, but during day it's more like 1-3 up tons Ranging Response issues

I have connected my Netgear CM1000 directly at the point of entry. No other connections. Just a cable directly to the MPOE grounding block.  Connections look great and tight.  Upload speeds range from 0.x to 3.x during day. Loads of upload related issues in event log.

 

<tabindex=-1>Downstream Bonded Channels</tabindex=-1>
ChannelLock StatusModulationChannel IDFrequencyPowerSNR / MERUnerrored CodewordsCorrectable CodewordsUncorrectable Codewords
1LockedQAM25628537000000 Hz4.7 dBmV40.1 dB1634716261350
2LockedQAM2568411000000 Hz6.8 dBmV41.5 dB161752665430
3LockedQAM2569417000000 Hz6.6 dBmV41.3 dB161753197700
4LockedQAM25610423000000 Hz7.0 dBmV41.5 dB161753551320
5LockedQAM25611429000000 Hz6.6 dBmV41.3 dB161753838900
6LockedQAM25612435000000 Hz6.3 dBmV41.2 dB161754280120
7LockedQAM25613441000000 Hz6.5 dBmV41.2 dB161754492520
8LockedQAM25614447000000 Hz6.5 dBmV41.2 dB161755045410
9LockedQAM25615453000000 Hz6.4 dBmV41.0 dB161756136710
10LockedQAM25616459000000 Hz6.4 dBmV40.9 dB161756290950
11LockedQAM25617465000000 Hz6.6 dBmV41.1 dB161757102340
12LockedQAM25618471000000 Hz6.6 dBmV40.8 dB1617573601110
13LockedQAM25619477000000 Hz7.0 dBmV41.0 dB161757629480
14LockedQAM25620483000000 Hz7.2 dBmV41.1 dB1617579990110
15LockedQAM25621489000000 Hz7.1 dBmV41.1 dB161758281370
16LockedQAM25622495000000 Hz6.9 dBmV40.9 dB161758646050
17LockedQAM25623507000000 Hz6.1 dBmV39.7 dB1617614196110
18LockedQAM25624513000000 Hz5.8 dBmV40.3 dB1617621586100
19LockedQAM25625519000000 Hz5.5 dBmV40.6 dB1617623570170
20LockedQAM25626525000000 Hz5.3 dBmV40.3 dB1617625709200
21LockedQAM25627531000000 Hz5.1 dBmV40.3 dB1617630924260
22LockedQAM25629543000000 Hz4.4 dBmV40.0 dB1617636248300
23LockedQAM25630549000000 Hz4.3 dBmV40.0 dB1617640338420
24LockedQAM25631555000000 Hz4.1 dBmV39.9 dB1617641854480
25LockedQAM25632561000000 Hz4.1 dBmV39.9 dB1617647023410
26LockedQAM25633567000000 Hz4.3 dBmV39.9 dB1617651060510
27LockedQAM25634573000000 Hz4.1 dBmV39.9 dB1617652149680
28LockedQAM25635579000000 Hz3.6 dBmV39.7 dB1617656621690
29LockedQAM25636585000000 Hz4.1 dBmV39.8 dB1617663367920
30LockedQAM25637591000000 Hz4.2 dBmV39.8 dB16176622501000
31LockedQAM25638597000000 Hz4.0 dBmV39.7 dB16176655211120
32Not LockedUnknown00 Hz0.0 dBmV0.0 dB000

<tabindex=-1>Upstream Bonded Channels (Partial Service)</tabindex=-1>
ChannelLock StatusModulationChannel IDFrequencyPower
1LockedATDMA117300000 Hz46.8 dBmV
2LockedATDMA223700000 Hz40.0 dBmV
3LockedATDMA330300000 Hz45.8 dBmV
4LockedATDMA436700000 Hz43.8 dBmV
5LockedATDMA541200000 Hz41.5 dBmV
6Not LockedUnknown00 Hz0.0 dBmV
7Not LockedUnknown00 Hz0.0 dBmV
8Not LockedUnknown00 Hz0.0 dBmV

 

TimePriorityDescription
2020-09-14, 09:12:53Critical (3)No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 09:12:52Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 09:12:52Critical (3)Ranging Request Retries exhausted;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 09:08:07Critical (3)No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 09:08:06Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 09:08:06Critical (3)Ranging Request Retries exhausted;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 09:07:07Critical (3)No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 09:07:06Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 09:07:06Critical (3)Ranging Request Retries exhausted;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 09:02:23Critical (3)No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 09:02:22Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 09:02:22Critical (3)Ranging Request Retries exhausted;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 09:01:37Critical (3)No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 09:01:35Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 09:01:35Critical (3)Ranging Request Retries exhausted;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 08:56:58Critical (3)No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 08:56:56Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 08:56:56Critical (3)Ranging Request Retries exhausted;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 08:56:39Critical (3)No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 08:56:38Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 08:56:38Critical (3)Ranging Request Retries exhausted;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 08:51:14Critical (3)No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 08:51:12Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 08:51:12Critical (3)Ranging Request Retries exhausted;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 08:50:51Critical (3)No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 08:50:50Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 08:50:50Critical (3)Ranging Request Retries exhausted;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 08:45:33Critical (3)No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 08:45:31Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 08:45:31Critical (3)Ranging Request Retries exhausted;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 08:44:26Critical (3)No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 08:44:25Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 08:44:25Critical (3)Ranging Request Retries exhausted;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 08:41:11Critical (3)No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 08:41:09Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 08:41:09Critical (3)Ranging Request Retries exhausted;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 08:36:54Critical (3)No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 08:36:52Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
2020-09-14, 08:36:52Critical (3)Ranging Request Retries exhausted;CM-MAC=38:94:ed:73:39:e8;CMTS-MAC=00:01:5c:72:52:6d;CM-QOS=1.1;CM-VER=3.1;
 

 

 

Highlighted
Expert

Re: Supposed to have 15 up, but during day it's more like 1-3 up tons Ranging Response issues

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 !



I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Highlighted
Regular Visitor

Re: Supposed to have 15 up, but during day it's more like 1-3 up tons Ranging Response issues

thanks! i really appreciate it!!!

Highlighted
Expert

Re: Supposed to have 15 up, but during day it's more like 1-3 up tons Ranging Response issues

Quite welcome !



I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Highlighted
Official Employee

Re: Supposed to have 15 up, but during day it's more like 1-3 up tons Ranging Response issues

Hi, rwcmick. Thanks for posting here in the Xfinity Forums! We appreciate you being here.

 

I'd like to take a look at some diagnostics on your modem on our end to see what is going on and what we might need to do to fix it. Please send me a PM with your first and last name and we will go from there!

 

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


I am an Official Comcast Employee.
Official Employees are from multiple teams within Comcast: CARE, Product, Leadership. We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Highlighted
Regular Visitor

Re: Supposed to have 15 up, but during day it's more like 1-3 up tons Ranging Response issues

Thanks. I have PM'd you.