Time |
Priority |
Description |
Wed Jul 26 11:20:08 2023 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 11:16:52 2023 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 11:14:10 2023 |
(Critical (3)) |
UCD invalid or channel unusable;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 11:14:08 2023 |
(Critical (3)) |
No Ranging Response received - T3 time-out;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 11:14:07 2023 |
(Critical (3)) |
UCD invalid or channel unusable;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 11:12:11 2023 |
(Critical (3)) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 11:04:09 2023 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 11:03:43 2023 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 11:03:40 2023 |
(Critical (3)) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 08:05:41 2023 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 08:00:24 2023 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 07:43:08 2023 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 07:37:53 2023 |
(Critical (3)) |
UCD invalid or channel unusable;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 07:36:53 2023 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 07:36:40 2023 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 07:34:01 2023 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 07:27:21 2023 |
(Critical (3)) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 07:00:15 2023 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 06:58:56 2023 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 06:22:20 2023 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 06:17:01 2023 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 06:13:40 2023 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 06:10:14 2023 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 05:43:40 2023 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 05:38:52 2023 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 05:35:19 2023 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 05:31:32 2023 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 05:15:20 2023 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 05:14:50 2023 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 05:02:09 2023 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 04:56:07 2023 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 04:46:41 2023 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 04:41:25 2023 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 04:16:16 2023 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 04:14:27 2023 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 04:02:13 2023 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 03:56:48 2023 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 03:40:35 2023 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 03:39:06 2023 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 26 03:28:21 2023 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1; |
EG
Expert
•
110.8K Messages
2 years ago
Please also copy all of the text in its entirety of the *Downstream Power Levels*, the *SNR's* (Signal to Noise Ratios), and the *Upstream Power Level* numbers and paste them into your next post.
0
0
user_7998f9
3 Messages
2 years ago
Sorry! Thought I had included them in the first post. Here they are:
Number Range
Codewords
Codewords
Codewords
1
0
EG
Expert
•
110.8K Messages
2 years ago
The downstream and the upstream power levels are borderline to out of spec, and they may be intermittently fluctuating even farther 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 there 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-1000 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 you'll need to get the techs re-involved until things get fixed properly.
Good luck with it !
0
0
user_7998f9
3 Messages
2 years ago
Thanks so much for your tips and advice - I really appreciate it.
I checked and we only have a single splitter coming in from the street and there aren’t any other splitters. All the cables are in good shape and there aren’t any kinks or sharp bends. I checked all the fittings, took them apart and cleaned the center wire and retightened them all. However, we have still been having outages today. Here are today’s stats:
Number Range
Codewords
Codewords
Codewords
1
0
EG
Expert
•
110.8K Messages
2 years ago
@user_7998f9
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 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 !
0
0