Time |
Priority |
Description |
Fri Apr 29 14:42:04 2022 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=xx:Xx:XX:XX:XX:XX;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Fri Apr 29 14:41:38 2022 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Fri Apr 29 14:26:42 2022 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Fri Apr 29 14:25:47 2022 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=vREDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Fri Apr 29 14:00:55 2022 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Fri Apr 29 14:00:18 2022 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Fri Apr 29 13:59:47 2022 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Fri Apr 29 13:59:36 2022 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Fri Apr 29 13:07:30 2022 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Fri Apr 29 13:06:55 2022 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Fri Apr 29 12:33:42 2022 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Fri Apr 29 12:33:19 2022 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Fri Apr 29 12:08:03 2022 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Fri Apr 29 12:07:35 2022 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Fri Apr 29 12:07:19 2022 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Fri Apr 29 12:06:56 2022 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Fri Apr 29 12:06:49 2022 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED47;CM-QOS=1.1;CM-VER=3.1; |
Fri Apr 29 10:58:48 2022 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Fri Apr 29 10:58:01 2022 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Fri Apr 29 10:45:32 2022 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Fri Apr 29 10:44:53 2022 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTEDCMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Fri Apr 29 10:37:44 2022 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTEDCMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Fri Apr 29 10:37:18 2022 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Fri Apr 29 10:37:04 2022 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Fri Apr 29 10:36:33 2022 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Fri Apr 29 10:36:04 2022 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Fri Apr 29 10:35:34 2022 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Fri Apr 29 10:22:01 2022 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Fri Apr 29 10:21:08 2022 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Fri Apr 29 10:15:19 2022 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED CM-QOS=1.1;CM-VER=3.1; |
Fri Apr 29 10:14:53 2022 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTEDCMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Fri Apr 29 09:37:05 2022 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Fri Apr 29 09:36:37 2022 |
(Notice (6)) |
CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Fri Apr 29 06:31:16 2022 |
(Critical (3)) |
No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Fri Apr 29 06:31:10 2022 |
(Critical (3)) |
SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Fri Apr 29 06:31:10 2022 |
(Notice (6)) |
DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Fri Apr 29 06:31:06 2022 |
(Notice (6)) |
TLV-11 - unrecognized OID;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established |
(Notice (6)) |
Honoring MDD; IP provisioning mode = IPv6 |
Time Not Established |
(Critical (3)) |
No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established |
(Critical (3)) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Accepted Solution
EG
Expert
•
110.1K Messages
3 years ago
@user_cc17b5 That error code is particular to DOCSIS 3.1 and OFDM channel profiles.
It means the OFDM channel is constantly failing FEC (Forward Error Correction) lock on one of the OFDM profiles. Event type code 16, is the loss of FEC lock for an OFDM profile. In this case (typical) the highest profile 3 is the one going impaired.
Event type code 24 is FEC recovery on that profile.
The CMTS (Cable Modem Termination System) can be configured with multiple OFDM profiles which have different modulation schemes applied to the OFDM subcarriers.
When the CMTS gets the code 16 event, it can dynamically downgrade the active profile for that CM.
If you're seeing this constantly I suspect your Downstream OFDM channel might be marginal. But, since OFDM can have such an insane modulation order at higher profiles, this can have no noticeable effect on your normal usage.
If you aren't suffering any packet-loss or issues with downstream throughput, I wouldn't be too concerned.
Live with it a while now and see. Hope things hold up for you ! Good luck !
2
0
EG
Expert
•
110.1K Messages
3 years ago
Please redact all of the CM MAC and the CMTS MAC addresses in your error log entries for your privacy. They are considered to be personal information. 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".
That said. The upstream power is too high and it may be intermittently fluctuating even higher to out of spec levels. The downstream power is on the weak side as well. 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 Radio Shack, Home Depot, Target, 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, 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.1K Messages
3 years ago
You have to redact those MAC addresses as I stated, otherwise no one can see your post.
0
0
user_cc17b5
Visitor
•
14 Messages
3 years ago
EG, I reviewed again and found you were right. Now I have it all redacted. Error type code 16 is FEC errors were over limit on one of the assigned downstream OFDM profiles of a channel. What is that and how do we fix it.
0
0
EG
Expert
•
110.1K Messages
3 years ago
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 !
1
0
EG
Expert
•
110.1K Messages
3 years ago
@user_cc17b5
Sure. Please circle back here with how things turn out.
9
0
user_cc17b5
Visitor
•
14 Messages
3 years ago
Will do. Thanks. I have printed all error logs. modem just did a reset for a T3 error. I see lower power and snr after the reboot. HMMMM. A clue!!!!
0
0
user_cc17b5
Visitor
•
14 Messages
3 years ago
Installed the RRA1-10 return amp. Upstream power is way lower and speeds are way up.
Status
Profile ID
ID
MER
Number Range
Codewords
Codewords
Codewords
0
0