Contributor
•
24 Messages
Modem logging errors
Whot do the following modem log entries indicate? Fault in the OFDM/OFDMA downstream channels?
Wed May 14 02:22:18 2025 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed May 14 02:20:18 2025 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Tue May 13 01:48:48 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;
Mon May 12 23:36:39 2025 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon May 12 23:34:38 2025 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon May 12 23:34:30 2025 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; 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;
Mon May 12 23:34:27 2025 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon May 12 15:48:46 2025 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; 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;
Mon May 12 15:46:46 2025 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon May 12 00:23:06 2025 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; 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;
Mon May 12 00:21:01 2025 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sun May 11 12:22:58 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;
Accepted Solution
EG
Expert
•
110.4K Messages
1 day ago
Those notices are for the OFDM channel, and a small amount is OK. Event type code 16, is the "Notice" of a loss of the FEC (Foward Error Correction) lock for an OFDM profile, and event type code 24 is the 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 cable modem.
If you're seeing this constantly, I'd suspect your Downstream OFDM channel might be marginal / noisy. But, since OFDM can have such an insane modulation order at higher profiles, this may have no noticeable effect on your normal usage. If you aren't suffering any loss or issues with downstream throughput, I wouldn't be too concerned.
0