Skip to main content
Question

Potential S33 Modem Disconnects

  • April 23, 2025
  • 1 reply
  • 37 views

Forum|alt.badge.img

I have an S33 modem and I am trying to identify if my internet outages are due to the modem, my provider, or the cable to the provider.  I saw a post stating that posting logs could help identify this.  When issue is present, the modem is not fully syncing with the provider and is showing a -26 to -37 dBmV for power for downstream.  When it functions the level is -12 to -15.  Part of log is below when issue is seen.

 

22/4/2025
20:01:50
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC={edit : personal information};CMTS-MAC={edit : personal information}=1.1;CM-VER=3.1;
22/4/2025
20:01:55
5 MDD message timeout;CM-MAC={edit : personal information};CMTS-MAC={edit : personal information};CM-VER=3.1;
22/4/2025
20:01:55
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC={edit : personal information};CMTS-MAC={edit : personal information};CM-VER=3.1;
22/4/2025
20:01:55
6 CM-STATUS message sent. Event Type Code: 2; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 37 38 39 40 41 42 43 44; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC={edit : personal information};CMTS-MAC={edit : personal information};CM-QOS
22/4/2025
20:02:02
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC={edit : personal information};CMTS-MAC={edit : personal information};CM-QOS=1.1;CM-VER=3.1;
22/4/2025
20:02:02
6 CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC={edit : personal information};CMTS-MAC={edit : personal information};CM-QOS=1.1;CM-VER=3.1;
22/4/2025
20:02:02
6 CM-STATUS message sent. Event Type Code: 2; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 37 38 39 40 41 42 43 44; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC={edit : personal information};CMTS-MAC={edit : personal information};CM-QOS
22/4/2025
20:02:03
5 MDD message timeout;CM-MAC={edit : personal information};CMTS-MAC={edit : personal information};CM-QOS=1.1;CM-VER=3.1;
22/4/2025
20:02:10
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC={edit : personal information};CMTS-MAC={edit : personal information};CM-QOS=1.1;CM-VER=3.1;
22/4/2025
20:02:10
6 CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC={edit : personal information};CMTS-MAC={edit : personal information};CM-QOS=1.1;CM-VER=3.1;
22/4/2025
20:02:17
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC={edit : personal information};CMTS-MAC={edit : personal information};CM-QOS=1.1;CM-VER=3.1;
22/4/2025
20:02:17
6 CM-STATUS message sent. Event Type Code: 1; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 37 38 39 40 41 42 43 44; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC={edit : personal information};CMTS-MAC=0{edit : personal information};CM-QOS
22/4/2025
20:02:32
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC={edit : personal information};CMTS-MAC=0{edit : personal information};CM-QOS=1.1;CM-VER=3.1;
22/4/2025
20:02:37
6 CM-STATUS message sent. Event Type Code: 5; Chan ID: 29 30 35; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC={edit : personal information};CMTS-MAC=0{edit : personal information};CM-QOS=1.1;CM-VER=3.1;
22/4/2025
20:02:37
6 CM-STATUS message sent. Event Type Code: 4; Chan ID: 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC={edit : personal information};CMTS-MAC={edit : personal information};CM-QOS=1.1;CM-VER=3.1;
22/4/2025
20:02:37
5 MDD message timeout;CM-MAC={edit : personal information};CMTS-MAC={edit : personal information};CM-QOS=1.1;CM-VER=3.1;
22/4/2025
20:02:44
6 CM-STATUS message sent. Event Type Code: 2; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 30 31 32 33 34 37 38 39 40 41 42 43 44; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC{edit : personal information};CMTS-MAC={edit : personal information};CM-QOS=1.
22/4/2025
20:02:52
6 CM-STATUS message sent. Event Type Code: 1; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 31 32 33 34 37 38 39 40 41 42 43 44; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC{edit : personal information};CMTS-MAC={edit : personal information};CM-QOS=1.
22/4/2025
20:02:52
6 CM-STATUS message sent. Event Type Code: 2; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 31 32 33 34 37 38 39 40 41 42 43 44; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC={edit : personal information};CMTS-MAC={edit : personal information};CM-QOS=1.1;C
22/4/2025
20:03:03
5 MDD message timeout;CM-MAC={edit : personal information};CMTS-MAC={edit : personal information};CM-QOS=1.1;CM-VER=3.1;
22/4/2025
20:03:03
6 CM-STATUS message sent. Event Type Code: 2; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 30 31 32 33 34 37 38 39 40 41 42 43 44; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC={edit : personal information};CMTS-MAC={edit : personal information};CM-QOS=1.
22/4/2025
20:03:07
6 CM-STATUS message sent. Event Type Code: 5; Chan ID: 29 35; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC={edit : personal information};CMTS-MAC{edit : personal information};CM-QOS=1.1;CM-VER=3.1;
22/4/2025
20:03:13
6 CM-STATUS message sent. Event Type Code: 2; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 30 31 32 33 34 37 38 39 40 41 42 43 44; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC={edit : personal information};CMTS-MAC={edit : personal information};CM-QOS=1.
22/4/2025
20:03:13
5 MDD message timeout;CM-MAC{edit : personal information};CMTS-MAC={edit : personal information};CM-QOS=1.1;CM-VER=3.1;
22/4/2025
20:03:21
3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC={edit : personal information};CMTS-MAC{edit : personal information};CM-QOS=1.1;CM-VER=3.1;
22/4/2025
20:03:21
3 No Ranging Response received - T3 time-out;CM-MAC={edit : personal information};CMTS-MAC{edit : personal information};CM-QOS=1.1;CM-VER=3.1;
22/4/2025
20:03:21
3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC={edit : personal information};CMTS-MAC={edit : personal information};CM-QOS=1.1;CM-VER=3.1;
22/4/2025
20:03:22
3 No Ranging Response received - T3 time-out;CM-MAC={edit : personal information}CMTS-MAC={edit : personal information};CM-QOS=1.1;CM-VER=3.1;
22/4/2025
20:03:23
6 CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 37 38 39 40 41 42 43 44 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC={edit : personal information};CMTS-MAC={edit : personal information};CM
22/4/2025
20:03:26
3 No Ranging Response received - T3 time-out;CM-MAC={edit : personal information};CMTS-MAC={edit : personal information};CM-QOS=1.1;CM-VER=3.1;
22/4/2025
20:03:26
3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC={edit : personal information};CMTS-MAC={edit : personal information};CM-QOS=1.1;CM-VER=3.1;
22/4/2025
20:03:29
3 No Ranging Response received - T3 time-out;CM-MAC={edit : personal information};CMTS-MAC={edit : personal information};CM-QOS=1.1;CM-VER=3.1;
22/4/2025
20:03:29
3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC={edit : personal information};CMTS-MAC={edit : personal information};CM-QOS=1.1;CM-VER=3.1;
22/4/2025
20:03:35
3 CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.2, 258MHz.
22/4/2025
20:03:35
3 CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.3, 1002MHz.
22/4/2025
20:03:35
3 CMSTATUS:US_Diplexer_Mode_Change_Ignored:TLV-21.1, 42MHz.
22/4/2025
20:03:40
6 Honoring MDD; IP provisioning mode = IPv6
22/4/2025
20:03:49
3 CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.2, 108MHz.
22/4/2025
20:03:49
3 CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.3, 1002MHz.
22/4/2025
20:03:49
3 CMSTATUS:US_Diplexer_Mode_Change:TLV-84.1, 5-42MHz.
22/4/2025
20:03:50
6 DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC={edit : personal information};CMTS-MAC={edit : personal information};CM-QOS=1.1;CM-VER=3.1;
22/4/2025
20:04:13
5 MDD message timeout;CM-MAC={edit : personal information};CMTS-MAC={edit : personal information};CM-QOS=1.1;CM-VER=3.1;
22/4/2025
20:04:14
6 CM-STATUS message sent. Event Type Code: 5; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 37 38 39 40 41 42 43 44; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC={edit : personal information};CMTS-MAC={edit : personal information};CM-
22/4/2025
20:04:23
6 CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC={edit : personal information};CMTS-MAC={edit : personal information};CM-QOS=1.1;CM-VER=3.1;

 

 
This topic has been closed for comments

1 reply

Forum|alt.badge.img+42

The modem itself is unlikely to cause an internet outage. The issue might be due to maintenance work in your area or poor signal reception from the service provider.

Event logs are typically related to the internet service provider.

If the modem is losing connection, it could be because it is not receiving a proper signal from the service provider.

For your reference, please find the link below to check the cable signals.

http://arris.force.com/consumers/articles/knowledge/S33-Cable-Signal-Levels

Cable signal levels are crucial for maintaining a stable and efficient internet connection. 

 

 

 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings