Start a New Discussion

Start a New Discussion

Orbi WiFi 7 RBE973
Reply

Re: Netgear CAX30

taellinglin
Aspirant
Aspirant
‎2022-11-08 10:48 AM
‎2022-11-08 10:48 AM

Netgear CAX30

I am looking in Event Logs and see errors. I have to restart the router and my server every 24 hours sometimes...it work all day and then stop working. Here is my Logs, can you help me fix these issues?:

 

2022-11-08 12:39:09Notice (6)DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2.;CM-MAC=34:98:b5:2b:2d:08;CMTS-MAC=00:01:5c:68:20:54;CM-QOS=1.1;CM-VER=3.1;
2022-11-08 12:39:08Notice (6)TLV-11 - unrecognized OID;CM-MAC=34:98:b5:2b:2d:08;CMTS-MAC=00:01:5c:68:20:54;CM-QOS=1.1;CM-VER=3.1;
2022-11-08 12:39:08Error (4)Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=34:98:b5:2b:2d:08;CMTS-MAC=00:01:5c:68:20:54;CM-QOS=1.1;CM-VER=3.1;
2022-11-08 12:39:08Error (4)Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=34:98:b5:2b:2d:08;CMTS-MAC=00:01:5c:68:20:54;CM-QOS=1.1;CM-VER=3.1;
2022-11-08 12:39:08Error (4)Missing BP Configuration Setting TLV Type: 17.3;CM-MAC=34:98:b5:2b:2d:08;CMTS-MAC=00:01:5c:68:20:54;CM-QOS=1.1;CM-VER=3.1;
2022-11-08 12:39:08Warning (5)DHCP WARNING - Non-critical field invalid in response ;CM-MAC=34:98:b5:2b:2d:08;CMTS-MAC=00:01:5c:68:20:54;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:33Notice (6)Overriding MDD IP initialization parameters; IP provisioning mode = IPv4
1970-01-01 00:00:30Critical (3)No Ranging Response received - T3 time-out;CM-MAC=34:98:b5:2b:2d:08;CMTS-MAC=00:01:5c:68:20:54;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=34:98:b5:2b:2d:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:30Critical (3)No Ranging Response received - T3 time-out;CM-MAC=34:98:b5:2b:2d:08;CMTS-MAC=00:01:5c:68:20:54;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=34:98:b5:2b:2d:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:30Critical (3)No Ranging Response received - T3 time-out;CM-MAC=34:98:b5:2b:2d:08;CMTS-MAC=00:01:5c:68:20:54;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=34:98:b5:2b:2d:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:29Critical (3)No Ranging Response received - T3 time-out;CM-MAC=34:98:b5:2b:2d:08;CMTS-MAC=00:01:5c:68:20:54;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=34:98:b5:2b:2d:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:34Critical (3)No Ranging Response received - T3 time-out;CM-MAC=34:98:b5:2b:2d:08;CMTS-MAC=00:01:5c:68:20:54;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:29Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=34:98:b5:2b:2d:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2022-11-05 10:09:46Critical (3)Resetting the cable modem due to docsDevResetNow
1970-01-01 00:00:30Critical (3)No Ranging Response received - T3 time-out;CM-MAC=34:98:b5:2b:2d:08;CMTS-MAC=00:01:5c:68:20:54;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=34:98:b5:2b:2d:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2022-11-05 09:52:46Critical (3)Resetting the cable modem due to docsDevResetNow
2022-11-05 10:40:26Critical (3)DHCP FAILED - Discover sent, no offer received;CM-MAC=34:98:b5:2b:2d:08;CMTS-MAC=00:01:5c:68:20:54;CM-QOS=1.1;CM-VER=3.1;
2022-11-05 10:40:14Critical (3)No Ranging Response received - T3 time-out;CM-MAC=34:98:b5:2b:2d:08;CMTS-MAC=00:01:5c:68:20:54;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:02:29Critical (3)No Ranging Response received - T3 time-out;CM-MAC=34:98:b5:2b:2d:08;CMTS-MAC=00:01:5c:68:20:54;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:25Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=34:98:b5:2b:2d:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

Message 1 of 5
0 Kudos
Reply
plemans
Guru Guru
Guru
‎2022-11-08 11:10 AM
‎2022-11-08 11:10 AM

Re: Netgear CAX30

got a screensnip of the cable connections page? 

That helps too. 

 

Start with removing any amplifiers, signal attenuators, or splitters from the coax.
From there check the line for kinks, damage, moisture in the line.
Check the connectors for improperly made ends, foil touching the copper coax line, loose connections, bad/old/cheap connectors, or corroded connections. Replace them if you do.
If you can, simply connect the modem right where the coax comes into the home. This prevents wiring in the home from being the issue. And some ISP’s charge if the wiring issue is in the home. So this helps prevent this.

Message 2 of 5
0 Kudos
Reply
taellinglin
Aspirant
Aspirant
‎2022-11-08 11:18 AM
‎2022-11-08 11:18 AM

Re: Netgear CAX30

All of my connections to the router, Ethernet, and modem are clean and secure...I think it's a settings I need to change.

Here is the Cable Connections Page:

taellinglin_0-1667935029351.pngtaellinglin_1-1667935055748.pngtaellinglin_2-1667935077283.png

taellinglin_3-1667935104742.png

 

 

Message 3 of 5
0 Kudos
Reply
taellinglin
Aspirant
Aspirant
‎2022-11-09 11:05 AM
‎2022-11-09 11:05 AM

Re: Netgear CAX30

Does this mean I have to call my ISP to come look at the utility box or is there something I can configure on my router to fix?

Message 4 of 5
0 Kudos
Reply
plemans
Guru Guru
Guru
‎2022-11-09 01:14 PM
‎2022-11-09 01:14 PM

Re: Netgear CAX30

Your cable connections page looks pretty rock solid but your event log is showing issues. 

Message 5 of 5
0 Kudos
Reply
Top Contributors
See All
Discussion stats
  • 4 replies
  • ‎2022-11-08 10:48 AM
  • 669 views
  • 0 kudos
  • 2 in conversation
Announcements

Orbi 770 Series