Time | Priority | Description |
Fri Dec 11 09:10:54 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 11 09:10:32 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 11 09:10:23 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 11 09:10:17 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 11 09:09:30 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 11 09:07:13 2020 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 11 09:07:10 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 11 09:06:54 2020 | Warning (5) | MDD message timeout;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 11 09:06:24 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 11 09:06:04 2020 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 11 09:06:03 2020 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 11 09:05:46 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 11 09:05:46 2020 | Warning (5) | MDD message timeout;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 11 09:04:46 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 11 09:02:33 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 11 09:00:53 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 11 09:00:19 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 30 36 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;C |
Fri Dec 11 09:00:02 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 18; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 11 09:00:01 2020 | Warning (5) | MDD message timeout;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 11 08:58:24 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 11 08:56:45 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 30 36 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;C |
Fri Dec 11 08:56:14 2020 | Warning (5) | MDD message timeout;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 11 08:55:59 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 11 08:55:30 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 11 08:54:51 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 11 08:54:37 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 11 08:54:09 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 11 08:53:42 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 11 08:53:22 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 30 36 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;C |
Fri Dec 11 08:53:17 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 11 08:52:52 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 30 36 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;C |
Fri Dec 11 08:52:27 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 11 08:52:22 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 30 36 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;C |
Fri Dec 11 08:52:03 2020 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 11 08:52:01 2020 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 11 08:51:39 2020 | Warning (5) | MDD message timeout;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 11 08:50:13 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 11 08:49:59 2020 | Warning (5) | MDD message timeout;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 11 08:48:48 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 11 08:48:33 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:9f:59:d0;CMTS-MAC=00:01:5c:a8:a0:9f;CM-QOS=1.1;CM-VER=3.1; |
BruceW
Gold Problem Solver
•
26.5K Messages
5 years ago
The downstream SNR values are borderline/too low, and the error counts are too high.
If you want to troubleshoot this yourself, please see Internet Troubleshooting Tips. If you can't find the problem or you'd rather have Comcast take care of it, call them at the phone number on your bill or 1-800-Comcast, or use one of the options on https://www.xfinity.com/support/contact-us/. Insist they send a tech out to identify the cause and correct it.
If the tech finds bad coax, splitters, amplifiers, or connections in your home (even if Comcast originally supplied them) you'll probably have to pay for the visit unless you have their Service Protection Plan (https://www.xfinity.com/support/articles/service-protection-plan, closed to customers that don't already have it). If the trouble is due to a faulty Comcast rental device or anything outside your home you shouldn't be charged.
0
EG
Expert
•
111.4K Messages
5 years ago
FWIW, the signals must be clean and noise free in order to be able to use an amp or it will make things even worse ! *Garbage in = even more garbage out* !
Perhaps there is noise leaking it to the lines somewhere ? It may not be at your premises. Perhaps you should get a tech out to investigate, Good luck !
0
azarco92
New Poster
•
3 Messages
5 years ago
so have another tech come out and insist that they escalte the ticket if it isn't an issue within my home?
0
0
azarco92
New Poster
•
3 Messages
5 years ago
I had 2 Techs come out already and each charge me 70 bucks. I'm already out 140 dollars with no resolution. I tried all the self troubleshooting and i still can't manage to get the SNR and the uncorrectibles in check.
0
0
EG
Expert
•
111.4K Messages
5 years ago
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 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.
Good luck !
0