|
Time |
|
Priority |
|
Description |
|
12:00:47 Fri Jan 10 2025 |
|
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; |
|
12:00:48 Fri Jan 10 2025 |
|
Notice (6) |
|
CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
|
12:01:14 Fri Jan 10 2025 |
|
Notice (6) |
|
CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
|
12:06:18 Fri Jan 10 2025 |
|
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; |
|
12:07:08 Fri Jan 10 2025 |
|
Notice (6) |
|
CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
|
12:14:20 Fri Jan 10 2025 |
|
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; |
|
12:17:11 Fri Jan 10 2025 |
|
Notice (6) |
|
CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
|
12:23:06 Fri Jan 10 2025 |
|
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; |
|
12:23:34 Fri Jan 10 2025 |
|
Notice (6) |
|
CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
|
12:26:27 Fri Jan 10 2025 |
|
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; |
|
12:27:45 Fri Jan 10 2025 |
|
Notice (6) |
|
CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
|
12:28:18 Fri Jan 10 2025 |
|
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; |
|
12:29:43 Fri Jan 10 2025 |
|
Notice (6) |
|
CM-STATUS message sent. Event Type Code: 16; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
|
12:29:48 Fri Jan 10 2025 |
|
Critical (3) |
|
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
|
12:29:48 Fri Jan 10 2025 |
|
Notice (6) |
|
CM-STATUS message sent. Event Type Code: 16; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
|
12:29:53 Fri Jan 10 2025 |
|
Critical (3) |
|
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
|
12:29:54 Fri Jan 10 2025 |
|
Notice (6) |
|
CM-STATUS message sent. Event Type Code: 16; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
|
12:30:19 Fri Jan 10 2025 |
|
Critical (3) |
|
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
|
12:31:14 Fri Jan 10 2025 |
|
Notice (6) |
|
CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
|
12:31:15 Fri Jan 10 2025 |
|
Critical (3) |
|
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
|
12:31:17 Fri Jan 10 2025 |
|
Critical (3) |
|
No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
|
12:31:19 Fri Jan 10 2025 |
|
Critical (3) |
|
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
|
12:31:28 Fri Jan 10 2025 |
|
Critical (3) |
|
UCD invalid or channel unusable;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
|
12:31:38 Fri Jan 10 2025 |
|
Critical (3) |
|
No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
|
12:31:56 Fri Jan 10 2025 |
|
Critical (3) |
|
UCD invalid or channel unusable;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
|
12:32:05 Fri Jan 10 2025 |
|
Critical (3) |
|
No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
|
12:32:22 Fri Jan 10 2025 |
|
Critical (3) |
|
UCD invalid or channel unusable;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
|
12:34:39 Fri Jan 10 2025 |
|
Critical (3) |
|
No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
|
12:35:27 Fri Jan 10 2025 |
|
Notice (6) |
|
Honoring MDD; IP provisioning mode = IPv6 |
|
12:35:36 Fri Jan 10 2025 |
|
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; |
|
12:35:37 Fri Jan 10 2025 |
|
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; |
|
12:35:44 Fri Jan 10 2025 |
|
Critical (3) |
|
UCD invalid or channel unusable;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
EG
Expert
•
108.3K Messages
25 days ago
@breslau
Your post with that pic of the error log entries was marked as being "Private" by the forum bot because it contains 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 delete that pic only.
What you can do instead is to copy all of the text (instead of using an image) and paste it into your next post here, but you'll need to redact all of the CM MAC and CMTS MAC addresses. The bot will not allow your post to be seen publicly.
1
0
EG
Expert
•
108.3K Messages
25 days ago
OK thanks. Your post is public again. 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
breslau
4 Messages
25 days ago
Here is the connection status page with the requested information. Thank you.
0
0
EG
Expert
•
108.3K Messages
25 days ago
This may or may not be the root cause of the problem (YMMV) but it should be addressed regardless. First.
The downstream power is a bit on the low / weak side and the upstream power is a bit on the high side, and they may be intermittently fluctuating even farther 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.
2
0
EG
Expert
•
108.3K Messages
25 days ago
If you are using a multi-room DVR system or using a MoCA network system / MoCA adapters, then you need to have that POE filter in line.
It may not help but if you really want to change out that coax, Amphenol and Belden make good quality coax cable ! Use RG6 tri or quad shield. You may want to get a tech out if you don't have the tools or training to install the connectors / fittings.
(edited)
0
0