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

Forum Discussion

destrosed's avatar
destrosed
Aspirant
Nov 13, 2025
Solved

CAX30 cable connection status: poor

I'm not too familiar with how  routers work  and  what not. Is this issue on  my  end or  the ISP? How  would  you fix this  issue?               Frequency start Value This field bel...
not listed
destrosed's avatar
destrosed
Aspirant
Nov 13, 2025

Thank  you for the  response. I'm currently looking at my line and where they  went  into my house they spliced  a  RG6  coax cable to another  cable and hung it  above a rafter in t he  basement then pullled it  through to reach the upstairs.  Not sure if that's anything  to do  with  it but thank you so I  do have  a place to start.

 

 

 

 

 


My Router: CAX30

Firmware Version V2.2.4.2

 

Event Log

Clear Log Refresh

 
 
 
TimePriorityDescription
2025-11-13 07:47:50Error (4)DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-11-12 20:03:52Warning (5)REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-11-12 20:03:47Notice (6)DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2.;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-11-12 20:03:46Notice (6)TLV-11 - unrecognized OID;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-11-12 20:03:46Error (4)Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-11-12 20:03:46Error (4)Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-11-12 20:03:46Error (4)Missing BP Configuration Setting TLV Type: 17.7;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-11-12 20:03:46Error (4)Missing BP Configuration Setting TLV Type: 17.6;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-11-12 20:03:46Error (4)Missing BP Configuration Setting TLV Type: 17.5;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-11-12 20:03:46Error (4)Missing BP Configuration Setting TLV Type: 17.4;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-11-12 20:03:46Error (4)Missing BP Configuration Setting TLV Type: 17.3;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-11-12 20:03:46Error (4)Missing BP Configuration Setting TLV Type: 17.2;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-11-12 20:03:46Error (4)Missing BP Configuration Setting TLV Type: 17.1;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-11-12 20:03:46Warning (5)DHCP WARNING - Non-critical field invalid in response ;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:34Notice (6)Honoring MDD; IP provisioning mode = IPv4
1970-01-01 00:00:31Critical (3)No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:24Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:31Critical (3)No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:24Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2025-11-12 18:18:41Critical (3)No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:31Critical (3)No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:24Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:28Critical (3)No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:23Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2025-10-22 19:33:06Critical (3)No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-10-22 13:20:56Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-10-20 12:55:10Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-10-05 07:54:00Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-10-04 16:31:56Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-10-03 12:53:34Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-10-03 00:43:33Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-10-02 15:32:16Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-09-30 10:55:59Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-09-23 15:09:44Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-09-21 20:15:37Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-09-18 14:20:04Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-09-17 17:33:34Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-09-17 12:43:32Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-09-16 16:47:24Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
2025-09-15 14:36:31Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e0:46:ee:fb:3c:07;CMTS-MAC=00:01:5c:a5:ac:52;CM-QOS=1.1;CM-VER=3.1;
FURRYe38's avatar
FURRYe38
Guru - Experienced User
Nov 13, 2025

Ya you got lots of criticals and errors that the ISP needs to look at.