NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

TheCoppola's avatar
TheCoppola
Aspirant
Apr 27, 2020
Solved

CM 500 constantly disconnecting - Lots of T3 and T4 & Dynamic Range Window Violation errors

Model:CM 500
IPS: Mediacom

Virmware: 1.01.04
There are times when it works fine for extended periods of time throughout the day, but all day everyday I'm dropping connection, both up/down stream indicator lights will go amber or shut off for a few seconds or both. It wasn’t always like this when I first got my CM 500 but this has become a constant occurrence that happens every day. When I check the logs I’m getting lots of T3 and T4 & Dynamic Range Window Violation errors. Already called Mediacom and they stated everything was fine on their end but I haven’t had a tech come out to my house yet, I assume that will be my next steps but wanted to get opinion first. Thanks

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel207000000 HzLocked
Connectivity StateOKOperational
Boot StateOKOperational
Configuration File  
SecurityEnabledBPI+
IP Provisioning ModeHonor MDDhonorMdd(4)
 
Provisioned Downstream and Upstream Throughput
Type Throughput
Downstream Provisioned Rate 
Upstream Provisioned Rate 
 
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1LockedQAM25616207000000 Hz10.4 dBmV41.7 dB1807613
2LockedQAM2561111000000 Hz13.9 dBmV44.6 dB117262337
3LockedQAM2562117000000 Hz13.9 dBmV43.8 dB99962325
4LockedQAM2563123000000 Hz13.7 dBmV43.7 dB70981534
5LockedQAM2564129000000 Hz13.6 dBmV43.9 dB67281023
6LockedQAM2565135000000 Hz13.6 dBmV43.5 dB65751175
7LockedQAM2566147000000 Hz13.4 dBmV43.4 dB39311134
8LockedQAM2567153000000 Hz13.2 dBmV44 dB33681028
9LockedQAM2568159000000 Hz13 dBmV44.1 dB2921822
10LockedQAM2569165000000 Hz13 dBmV44.1 dB2409765
11LockedQAM25610171000000 Hz13 dBmV43.6 dB1732392
12LockedQAM25611177000000 Hz12.8 dBmV43.3 dB1159454
13LockedQAM25612183000000 Hz12.4 dBmV42.9 dB1171396
14LockedQAM25613189000000 Hz12 dBmV42.6 dB1611506
15LockedQAM25614195000000 Hz11.4 dBmV42 dB2096467
16LockedQAM25615201000000 Hz11 dBmV41.3 dB1903611
 
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1LockedATDMA15120 Ksym/sec26400000 Hz43.4 dBmV
2LockedATDMA25120 Ksym/sec19600000 Hz43.4 dBmV
3LockedATDMA32560 Ksym/sec14800000 Hz38.4 dBmV
 
 
 
 
Time Priority Description
2020-4-27, 21:30:19Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:b9:8a:ac:a2:18;CMTS-MAC=94:d4:69:55:04:ef;CM-QOS=1.1;CM-VER=3.0;
2020-4-27, 21:30:21Warning (5)Dynamic Range Window violation
2020-4-27, 21:30:22Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:b9:8a:ac:a2:18;CMTS-MAC=94:d4:69:55:04:ef;CM-QOS=1.1;CM-VER=3.0;
2020-4-27, 21:30:22Warning (5)Dynamic Range Window violation
2020-4-27, 21:30:25Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:b9:8a:ac:a2:18;CMTS-MAC=94:d4:69:55:04:ef;CM-QOS=1.1;CM-VER=3.0;
2020-4-27, 21:30:26Warning (5)Dynamic Range Window violation
2020-4-27, 21:30:26Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:b9:8a:ac:a2:18;CMTS-MAC=94:d4:69:55:04:ef;CM-QOS=1.1;CM-VER=3.0;
2020-4-27, 21:30:28Warning (5)Dynamic Range Window violation
2020-4-27, 21:30:28Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:b9:8a:ac:a2:18;CMTS-MAC=94:d4:69:55:04:ef;CM-QOS=1.1;CM-VER=3.0;
2020-4-27, 21:30:28Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:b9:8a:ac:a2:18;CMTS-MAC=94:d4:69:55:04:ef;CM-QOS=1.1;CM-VER=3.0;
2020-4-27, 21:30:36Critical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:b9:8a:ac:a2:18;CMTS-MAC=94:d4:69:55:04:ef;CM-QOS=1.0;CM-VER=3.0;
2020-4-27, 21:30:47Notice (6)Honoring MDD; IP provisioning mode = IPv4
2020-4-27, 21:30:50Warning (5)DHCP WARNING - Non-critical field invalid in response ;CM-MAC=b0:b9:8a:ac:a2:18;CMTS-MAC=94:d4:69:55:04:ef;CM-QOS=1.1;CM-VER=3.0;
2020-4-27, 21:31:39Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:b9:8a:ac:a2:18;CMTS-MAC=94:d4:69:55:04:ef;CM-QOS=1.1;CM-VER=3.0;
2020-4-27, 21:32:08Warning (5)Dynamic Range Window violation
2020-4-27, 21:37:02Critical (3)Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:b9:8a:ac:a2:18;CMTS-MAC=94:d4:69:55:04:ef;CM-QOS=1.1;CM-VER=3.0;
2020-4-27, 21:37:06Warning (5)Dynamic Range Window violation
2020-4-27, 21:37:22Critical (3)Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:b9:8a:ac:a2:18;CMTS-MAC=94:d4:69:55:04:ef;CM-QOS=1.1;CM-VER=3.0;
2020-4-27, 21:37:26Warning (5)Dynamic Range Window violation
2020-4-27, 21:37:29Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:b9:8a:ac:a2:18;CMTS-MAC=94:d4:69:55:04:ef;CM-QOS=1.1;CM-VER=3.0;
2020-4-27, 21:37:29Warning (5)Dynamic Range Window violation
2020-4-27, 21:37:33Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:b9:8a:ac:a2:18;CMTS-MAC=94:d4:69:55:04:ef;CM-QOS=1.1;CM-VER=3.0;
2020-4-27, 21:37:34Warning (5)Dynamic Range Window violation
2020-4-27, 21:37:35Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:b9:8a:ac:a2:18;CMTS-MAC=94:d4:69:55:04:ef;CM-QOS=1.1;CM-VER=3.0;
2020-4-27, 21:37:43Critical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:b9:8a:ac:a2:18;CMTS-MAC=94:d4:69:55:04:ef;CM-QOS=1.0;CM-VER=3.0;
2020-4-27, 21:38:11Notice (6)Honoring MDD; IP provisioning mode = IPv4
2020-4-27, 21:38:14Warning (5)DHCP WARNING - Non-critical field invalid in response ;CM-MAC=b0:b9:8a:ac:a2:18;CMTS-MAC=94:d4:69:55:04:ef;CM-QOS=1.1;CM-VER=3.0;
2020-4-27, 21:38:16Warning (5)Dynamic Range Window violation
2020-4-27, 21:39:03Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:b9:8a:ac:a2:18;CMTS-MAC=94:d4:69:55:04:ef;CM-QOS=1.1;CM-VER=3.0;
2020-4-27, 21:39:06Warning (5)Dynamic Range Window violation
2020-4-27, 21:48:26Critical (3)Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:b9:8a:ac:a2:18;CMTS-MAC=94:d4:69:55:04:ef;CM-QOS=1.1;CM-VER=3.0;
2020-4-27, 21:48:29Warning (5)Dynamic Range Window violation
2020-4-27, 21:48:58Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:b9:8a:ac:a2:18;CMTS-MAC=94:d4:69:55:04:ef;CM-QOS=1.1;CM-VER=3.0;
2020-4-27, 21:48:59Warning (5)Dynamic Range Window violation
2020-4-27, 22:23:22Critical (3)Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:b9:8a:ac:a2:18;CMTS-MAC=94:d4:69:55:04:ef;CM-QOS=1.1;CM-VER=3.0;
2020-4-27, 22:23:27Warning (5)Dynamic Range Window violation
2020-4-27, 22:23:55Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:b9:8a:ac:a2:18;CMTS-MAC=94:d4:69:55:04:ef;CM-QOS=1.1;CM-VER=3.0;
2020-4-27, 22:23:57Warning (5)Dynamic Range Window violation
2020-4-27, 22:30:49Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:b9:8a:ac:a2:18;CMTS-MAC=94:d4:69:55:04:ef;CM-QOS=1.1;CM-VER=3.0;
2020-4-27, 22:31:05Warning (5)Dynamic Range Window violation
  • FURRYe38's avatar
    FURRYe38
    Apr 28, 2020

    Have the ISP check the signal and line quality UP to the modem. 
    Be sure there are no coax cable line splitters in the between the modem and ISP service box. 
    Be sure your using good quality RG6 coax cable up to the modem. 

2 Replies

  • FURRYe38's avatar
    FURRYe38
    Guru - Experienced User
    Apr 28, 2020

    Have the ISP check the signal and line quality UP to the modem. 
    Be sure there are no coax cable line splitters in the between the modem and ISP service box. 
    Be sure your using good quality RG6 coax cable up to the modem. 

    • TheCoppola's avatar
      TheCoppola
      Aspirant
      May 05, 2020

      Thanks for the feedback. I ended up calling my ISP and a tech came on site. They made some changes in preparation for 1gb speesds in my area back around October 2019 when this problem first started. He stated that I had an old coaxal splitters from their box on the street to the d-mark outside my house which was for the old signal. Still getting a little noise on their end but its down the line and he placed a ticket with their field guys. Over all its been much better but could be even better once they clear that noise down the line (if they find it).