Forum Discussion

Rigbly1's avatar
Rigbly1
New Contributor
5 years ago

Dynamic Range Violation

Arris says this is COX, Cox says all is well. Whats the deal...someone is not right and the event log is logging issues with the connection...so who is it?

Date Time Event ID Event Level Description
05/19/2020 07:37 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
05/19/2020 07:36 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
05/19/2020 03:53 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
05/19/2020 03:53 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
05/19/2020 02:04 2436694061 5 "Dynamic Range Window violation"
05/19/2020 02:04 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
05/19/2020 02:04 2436694061 5 "Dynamic Range Window violation"
05/19/2020 02:04 82001200 5 "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
05/19/2020 02:04 67061600 6 "DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
05/19/2020 02:04 73040100 6 "TLV-11 - unrecognized OID;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
05/19/2020 02:04 68000300 5 "DHCP WARNING - Non-critical field invalid in response ;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:46 68000100 3 "DHCP FAILED - Discover sent, no offer received;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:45 2436694066 6 "Honoring MDD; IP provisioning mode = IPv4"
01/01/1970 00:45 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:44 82000400 3 "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:44 68000100 3 "DHCP FAILED - Discover sent, no offer received;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:43 2436694066 6 "Honoring MDD; IP provisioning mode = IPv4"
01/01/1970 00:42 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:41 82000900 5 "B-INIT-RNG Failure - Retries exceeded;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:41 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:40 82000900 5 "B-INIT-RNG Failure - Retries exceeded;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:40 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:39 82000900 5 "B-INIT-RNG Failure - Retries exceeded;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:39 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:38 82000900 5 "B-INIT-RNG Failure - Retries exceeded;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:38 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:36 82000900 5 "B-INIT-RNG Failure - Retries exceeded;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:36 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:34 82000900 5 "B-INIT-RNG Failure - Retries exceeded;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:34 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:33 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:32 82000900 5 "B-INIT-RNG Failure - Retries exceeded;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:32 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:31 82000900 5 "B-INIT-RNG Failure - Retries exceeded;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:31 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:30 82000900 5 "B-INIT-RNG Failure - Retries exceeded;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:30 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:28 82000900 5 "B-INIT-RNG Failure - Retries exceeded;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:28 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:27 82000900 5 "B-INIT-RNG Failure - Retries exceeded;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:27 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:26 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
05/19/2020 01:06 82000400 3 "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
05/19/2020 01:06 82000100 3 "No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
05/19/2020 01:05 82000400 3 "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
05/19/2020 01:05 82000100 3 "No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
05/19/2020 01:05 82000400 3 "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
05/19/2020 01:05 82000100 3 "No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
05/19/2020 01:05 82000400 3 "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
05/18/2020 14:08 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
connection issues
Gigablast Issues SB8200

1 Reply

Sort By
  • Dave9's avatar
    Dave9
    Contributor III
    5 years ago

    I think it's normal to see one or two Dynamic Range Violation errors when you first reset the modem and it's figuring out the right upstream power levels. For a while I was getting 10 or more of these per day, and Cox sent out a tech to replace a bad exterior cable and bad amplifier on the pole. After that I didn't get any of those errors for a week, but as of today I'm getting 4 or 5 per hour. Based on the meaning of the error I don't think it's normal, but I only seem to get a momentary upstream glitch when it happens so maybe it's not a high priority to fix.

    The T3 and T4 timeouts can be more of a problem. I've had those before and they always caused major downtime. As you probably know, anything you see in the cable modem status or event logs can't be caused by your computer, router, or Ethernet cable. Errors in the log are caused by your modem, interior coax cable, exterior cable, or Cox network equipment. If you've checked your modem and interior coax cable you probably need one of the forum moderators to look at your account.