Time |
Priority |
Description |
Fri Mar 22 09:20:03 2024 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 22 09:10:46 2024 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 5; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 22 09:10:44 2024 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 22 09:10:16 2024 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 5; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 22 09:10:14 2024 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 22 09:08:47 2024 |
Critical (3) |
UCD invalid or channel unusable;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 22 09:08:46 2024 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 22 09:08:46 2024 |
Critical (3) |
UCD invalid or channel unusable;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 22 09:08:44 2024 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 22 09:08:44 2024 |
Critical (3) |
UCD invalid or channel unusable;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 22 09:08:42 2024 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 22 09:08:42 2024 |
Critical (3) |
UCD invalid or channel unusable;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 22 09:08:40 2024 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 22 09:08:40 2024 |
Critical (3) |
UCD invalid or channel unusable;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 22 09:08:38 2024 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 22 09:08:38 2024 |
Critical (3) |
UCD invalid or channel unusable;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 22 09:08:36 2024 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 22 09:08:36 2024 |
Critical (3) |
UCD invalid or channel unusable;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 22 09:08:35 2024 |
Critical (3) |
No Ranging Response received - T3 time-out;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 22 09:08:34 2024 |
Critical (3) |
UCD invalid or channel unusable;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 22 09:08:34 2024 |
Critical (3) |
No Ranging Response received - T3 time-out;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 22 09:08:33 2024 |
Critical (3) |
UCD invalid or channel unusable;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 22 09:08:31 2024 |
Critical (3) |
No Ranging Response received - T3 time-out;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 22 09:08:31 2024 |
Critical (3) |
UCD invalid or channel unusable;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 22 09:08:31 2024 |
Critical (3) |
No Ranging Response received - T3 time-out;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 22 09:08:30 2024 |
Critical (3) |
UCD invalid or channel unusable;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 22 09:08:29 2024 |
Critical (3) |
No Ranging Response received - T3 time-out;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 22 09:08:29 2024 |
Critical (3) |
UCD invalid or channel unusable;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 22 09:08:28 2024 |
Critical (3) |
No Ranging Response received - T3 time-out;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 22 09:08:28 2024 |
Critical (3) |
UCD invalid or channel unusable;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 22 09:08:28 2024 |
Critical (3) |
No Ranging Response received - T3 time-out;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 22 09:08:27 2024 |
Critical (3) |
UCD invalid or channel unusable;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 22 09:08:22 2024 |
Notice (6) |
DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 22 09:08:17 2024 |
Notice (6) |
TLV-11 - unrecognized OID;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established |
Notice (6) |
Honoring MDD; IP provisioning mode = IPv6 |
Time Not Established |
Critical (3) |
UCD invalid or channel unusable;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;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=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 22 09:07:08 2024 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Thu Mar 21 19:54:25 2024 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 5; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
Thu Mar 21 19:54:24 2024 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*;*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1; |
EG
Expert
•
106.9K Messages
8 months ago
The error log entries have been edited out of your post because they contain CM MAC and the CMTS MAC addresses. They are considered to be personal information. The posting of personally identifiable information is a violation of their forum guidelines. Please re-post them but you'll need to redact all of the CM MAC and CMTS MAC addresses.
While you are at it, please also copy all of the text in its entirety of the *Downstream Power Level*, the *Upstream Power Level*, and the *SNR* (Signal to Noise Ratio) numbers and paste them into your next post.
1
0
EG
Expert
•
106.9K Messages
8 months ago
Ok, so even though the signal status values were within specs at that snapshot in time, the error log entries confirm that something is going on. Perhaps there is intermittent noise ingress into the line(s) / an upstream channel / return path impairment somewhere.
There are other signal stat values 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 (The Digital Care Team) who are available to these boards. They will be able to poll the CMTS (Cable Modem Termination System) to check 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 check those upstream receive signal stats.
You should get a reply here in your topic. Good luck !
5
Damone17
Visitor
•
1 Message
2 months ago
I too have had these issues for years. Since 2018. Reported the problem, the dude comes out, says he will personally follow-up with me, then ghosts me. That was 2019. I've just learned to deal with it. However it appears that Comcast is monitoring these posts and summarily gets someone involved at a local level. Is it my turn for them to fix this issue once and for all? I guess we will see in time.
0
0
EG
Expert
•
106.9K Messages
2 months ago
@Damone17
Please create a new topic of your own here on this board detailing your issue. Thanks. The original poster has not returned. 6-month-old dead thread is now being closed.
For future reference, it is better to submit your own post as it creates a ticket to get help, and posting on someone else's older thread can delay getting help.
(edited)
0
0