Time |
Priority |
Description |
Fri Jan 12 12:22:50 2024 |
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 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 12:21:21 2024 |
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=;CMTS-MAC=0;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 12:18:20 2024 |
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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 12:17:37 2024 |
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 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 12:17:32 2024 |
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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 12:17:27 2024 |
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 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 12:17:27 2024 |
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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 12:17:22 2024 |
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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 12:17:22 2024 |
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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 11:51:54 2024 |
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 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 11:51:54 2024 |
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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 11:45:14 2024 |
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 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 11:45:14 2024 |
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=;CMTS-MAC=CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 11:38:34 2024 |
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 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 11:38:34 2024 |
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=CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 11:31:57 2024 |
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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 11:31:04 2024 |
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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 10:37:07 2024 |
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=CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 10:33:16 2024 |
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 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 10:30:27 2024 |
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=;CMTS-MAC=CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 10:26:36 2024 |
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 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 10:23:47 2024 |
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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 10:19:56 2024 |
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 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 10:18:00 2024 |
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; |
Fri Jan 12 10:17:29 2024 |
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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 10:17:26 2024 |
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=;CMTS-MAC=CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 10:17:24 2024 |
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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 10:17:21 2024 |
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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 10:17:19 2024 |
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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 10:17:16 2024 |
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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 10:14:46 2024 |
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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 09:58:48 2024 |
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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 09:39:18 2024 |
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=;CMTS-MAC=0;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 09:24:00 2024 |
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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 08:59:45 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; |
Fri Jan 12 08:48:16 2024 |
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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 08:25:00 2024 |
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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 08:10:26 2024 |
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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 08:10:14 2024 |
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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 12 08:06:18 2024 |
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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
EG
Expert
•
110.4K Messages
1 year ago
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".
0
0
EG
Expert
•
110.4K Messages
1 year ago
That said. The downstream power is on the low / weak side and it may be intermittently fluctuating even lower out of spec. And the upstream power is 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
•
110.4K Messages
1 year ago
Please post back with how it goes, thanks.
1
0
EG
Expert
•
110.4K Messages
1 year ago
Sounds good ! Hope that was it ! Best of luck !
0
0