| Time |
Priority |
Description |
| Sun Mar 31 08:52:49 2024 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1; |
| Sun Mar 31 05:55:24 2024 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; |
| Sun Mar 31 05:54:55 2024 |
Warning (5) |
MDD message timeout;CM-MAC=[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1; |
| Sun Mar 31 05:46:09 2024 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1; |
| Sun Mar 31 04:21:55 2024 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; |
| Sun Mar 31 04:21:26 2024 |
Warning (5) |
MDD message timeout;CM-MAC=[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1; |
| Sun Mar 31 04:21:21 2024 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1; |
| Sun Mar 31 04:18:54 2024 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; |
| Sun Mar 31 04:18:25 2024 |
Warning (5) |
MDD message timeout;CM-MAC=[Edited: Personal Information];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; |
| Sun Mar 31 04:18:19 2024 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: Personal Information];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; |
| Sun Mar 31 00:48:01 2024 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; |
| Sun Mar 31 00:47:50 2024 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1; |
| Sun Mar 31 00:47:31 2024 |
Warning (5) |
MDD message timeout;CM-MAC=[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1; |
| Sun Mar 31 00:46:40 2024 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1; |
| Sat Mar 30 20:17:55 2024 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1; |
| Sat Mar 30 20:17:26 2024 |
Warning (5) |
MDD message timeout;CM-MAC=[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1; |
| Sat Mar 30 20:02:21 2024 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1; |
| Sat Mar 30 19:14:26 2024 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; |
| Sat Mar 30 19:14:00 2024 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: Personal Information];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; |
| Sat Mar 30 19:13:53 2024 |
Warning (5) |
MDD message timeout;CM-MAC=[Edited: Personal Information];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; |
| Sat Mar 30 18:55:18 2024 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: Personal Information];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; |
| Sat Mar 30 18:53:00 2024 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; |
| Sat Mar 30 18:52:31 2024 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: Personal Information];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; |
| Sat Mar 30 18:52:31 2024 |
Warning (5) |
MDD message timeout;CM-MAC=[Edited: Personal Information];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; |
| Sat Mar 30 18:52:29 2024 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1; |
| Sat Mar 30 18:52:27 2024 |
Warning (5) |
MDD message timeout;CM-MAC=[Edited: Personal Information];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; |
| Sat Mar 30 18:48:46 2024 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1; |
| Sat Mar 30 18:13:57 2024 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; |
| Sat Mar 30 18:13:28 2024 |
Warning (5) |
MDD message timeout;CM-QOS=1.1;CM-VER=3.1; |
| Sat Mar 30 17:57:26 2024 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; |
| Sat Mar 30 17:56:57 2024 |
Warning (5) |
MDD message timeout;CM-QOS=1.1;CM-VER=3.1; |
| Sat Mar 30 17:56:55 2024 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1; |
| Sat Mar 30 16:13:56 2024 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; |
| Sat Mar 30 16:13:26 2024 |
Warning (5) |
MDD message timeout;CM-QOS=1.1;CM-VER=3.1; |
| Sat Mar 30 16:13:25 2024 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: Personal Information];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; |
| Sat Mar 30 16:13:25 2024 |
Warning (5) |
MDD message timeout;CM-MAC=[Edited: Personal Information];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1; |
| Sat Mar 30 16:13:25 2024 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1; |
| Sat Mar 30 14:31:25 2024 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; |
| Sat Mar 30 14:30:56 2024 |
Warning (5) |
MDD message timeout;CM-QOS=1.1;CM-VER=3.1; |
| Sat Mar 30 14:30:52 2024 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1; |
Accepted Solution
XfinityPaula
Official Employee
•
1.2K Messages
9 months ago
@user_nvc75f Hello, thanks for reaching out for help on our Forums! I'm sorry to hear that you have had these hiccups in connections. I know first hand how a small interruption can cause a big headache. You are with the right team for help to troubleshoot and resolve the issues.
@EG Thank you for assisting us. You mentioned all the things to check to help with the signal issue and even the timeouts, but if those checks and changes don't result well we can set up a repair appointment.
@user_nvc75f Please let us know if any of these steps help out. If not we will set up a time for a repair technician to help us out.
2
EG
Expert
•
107.6K Messages
9 months ago
@user_nvc75f
Please redact all of the CM MAC and the CMTS MAC addresses from your error log entries for your privacy. They are considered to be personal information. The posting of personally identifiable information is a violation of their forum guidelines. The forum bot will not allow your post to be seen publically. It flagged your post as "Private".
(edited)
0
0
EG
Expert
•
107.6K Messages
9 months ago
@user_nvc75f
This may or may not be the root cause of the problem (YMMV) but it should be addressed regardless.
The upstream power is on the high side / marginal and it may be intermittently fluctuating even higher to out of spec levels. 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 !
0
0