Time |
Priority |
Description |
Sun Oct 27 05:18:12 2024 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 5; Chan ID: 193 194; 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; |
Sun Oct 27 05:18:03 2024 |
(Critical (3)) |
UCD invalid or channel unusable;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Sun Oct 27 05:17:59 2024 |
(Critical (3)) |
No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Sun Oct 27 05:17:58 2024 |
(Critical (3)) |
UCD invalid or channel unusable;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Sun Oct 27 05:17:58 2024 |
(Critical (3)) |
No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Sun Oct 27 05:17:57 2024 |
(Critical (3)) |
UCD invalid or channel unusable;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Sun Oct 27 05:17:53 2024 |
(Notice (6)) |
DS profile assignment change. DS Chan ID: 33; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Sun Oct 27 05:17:52 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; |
Sun Oct 27 05:17:47 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; |
Sun Oct 27 05:09:19 2024 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 5; Chan ID: 193 194; 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; |
Sun Oct 27 05:08:51 2024 |
(Critical (3)) |
UCD invalid or channel unusable;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Sun Oct 27 05:08:38 2024 |
(Critical (3)) |
No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Sun Oct 27 05:08:38 2024 |
(Critical (3)) |
UCD invalid or channel unusable;[Edited: "Personal Information"];CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Sun Oct 27 05:08:34 2024 |
(Critical (3)) |
No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Sun Oct 27 05:08:34 2024 |
(Critical (3)) |
UCD invalid or channel unusable;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Sun Oct 27 05:08:32 2024 |
(Critical (3)) |
No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Sun Oct 27 05:08:32 2024 |
(Critical (3)) |
UCD invalid or channel unusable;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Sun Oct 27 05:08:27 2024 |
(Notice (6)) |
DS profile assignment change. DS Chan ID: 33; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Sun Oct 27 05:08:25 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; |
Sun Oct 27 05:08:20 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; |
Sat Oct 26 09:40:24 2024 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 24; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Sat Oct 26 09:36:08 2024 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Sat Oct 26 09:33:49 2024 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 1; Chan ID: 35; 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; |
Sat Oct 26 09:33:25 2024 |
(Warning (5)) |
MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Sat Oct 26 09:33:18 2024 |
(Critical (3)) |
UCD invalid or channel unusable;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Sat Oct 26 09:13:18 2024 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 1; Chan ID: 35; 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; |
Sat Oct 26 09:12:49 2024 |
(Warning (5)) |
MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Sat Oct 26 08:52:42 2024 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 1; Chan ID: 35; 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; |
Sat Oct 26 08:52:35 2024 |
(Warning (5)) |
MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Sat Oct 26 08:52:33 2024 |
(Warning (5)) |
Dynamic Range Window violation |
Sat Oct 26 08:52:33 2024 |
(Warning (5)) |
RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Sat Oct 26 08:32:28 2024 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 1; Chan ID: 35; 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; |
Sat Oct 26 08:32:20 2024 |
(Warning (5)) |
MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Sat Oct 26 08:32:12 2024 |
(Critical (3)) |
UCD invalid or channel unusable;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
EG
Expert
•
107.1K Messages
27 days ago
The upstream power is way too high / out of spec. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.
In an effort to try to obtain better connectivity / more wiggle room, check to see if there are any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1002 MHz, bi-directional, and no gold colored garbage from Home Depot, Target, Wal-Mart, etc. Splitters should be swapped with known to be good / new ones to test.
Also check the coax cable for any damage such as cuts, nicks, abrasions, kinks, sharp bends, etc.
If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two-way splitter connected directly off of the drop from the street / pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.
Good luck with it !
1
0
EG
Expert
•
107.1K Messages
27 days ago
Quite welcome ! It could be local to you or farther up the line somewhere. If the upstream power is still that high then that needs to be addressed. Have you tried any of those tips ?
1
0
EG
Expert
•
107.1K Messages
27 days ago
Yes. If there is nothing more that can be done to improve the connection quality, then you'll need a tech visit as stated.
Bear in mind that if the premises facing techs can not find or fix a problem at your home, it is they who are responsible for escalating it up to their line / network / maintenance dept. techs. The problem may lie beyond your home in the local neighborhood infrastructure somewhere but it is their S.O.P. to start at the home. And if the problem is found to be on their side of the demarcation point, there will not be any charge.
Good luck ! Please post back here with how things turn out.
0
0
user_m145
Frequent Visitor
•
15 Messages
26 days ago
Just as a quick update to this, I work nights and all my testing and troubleshooting has been done during the night and early morning. Something I realized was that during the day (around 11am) the upstream is completely fine. Is there a representative from xfinity that can confirm whether this some kind of work or maintenance going on during the night that would cause this? I'm still scheduling a tech visit to check all the lines, but clearly something is happening at night that is causing upstream issues that isn't happening during the day time.
1
0