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

Forum Discussion

Infosec_stoic's avatar
Infosec_stoic
Aspirant
Mar 22, 2021

Ping Spikes and dropped packets

Hey guys! So this started about 4-5 days ago where my nighthawk C7000V2 (Firmware V1.03.01) would intermittently have massive packet spikes and dropped packets. This isn't just with gaming . Since I...
plemans's avatar
plemans
Guru - Experienced User
Mar 23, 2021

do you have a screen snip of the cable connections page and event logs? 

that helps us check the connection back to the isp. 

they're great at saying "its not our line". 

And it might not be. 

Check you coax line for kinks, bad/old/loose connectors, moisture in the line, etc. 

Also, if you have any splitters, amplifiers, or attenuators, remove them from the line. preferable, directly connect the c7000 to where the coax comes into the home to prevent the wiring in the home from being the issue. 

  • Infosec_stoic's avatar
    Infosec_stoic
    Aspirant
    Mar 23, 2021

    Hello! thank you for getting back to me.

     

    I went ahead and I checked the coax connection to the C7000V2. I even double checked the outside cable line to make sure that there wasn't any damage to the outside box. Doesn't appear to be anything out of the ordinary. I just have the one coaxial connection directly to the modem/router no other splitters, amplifiers, or attenuators.

     

    Here's the output from the event logs below kind of a bummer they don't have a export option so a copy and paste will have to do.

    Time

    		PriorityDescription
    2021-3-23, 09:01:12Warning (5)MDD message timeout;CM-MAC=44:a5:6e:83:05:48;CMTS-MAC=00:27:90:0c:d0:7c;CM-QOS=1.1;CM-VER=3.0;
    2021-3-22, 13:55:59Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:83:05:48;CMTS-MAC=00:27:90:0c:d0:7c;CM-QOS=1.1;CM-VER=3.0;
    2021-3-22, 13:55:20Error (4)Improper Configuration File CVC Format
    2021-3-22, 13:55:12Notice (6)TLV-11 - unrecognized OID;CM-MAC=44:a5:6e:83:05:48;CMTS-MAC=00:27:90:0c:d0:7c;CM-QOS=1.1;CM-VER=3.0;
    2021-3-22, 13:55:10Warning (5)DHCP WARNING - Non-critical field invalid in response ;CM-MAC=44:a5:6e:83:05:48;CMTS-MAC=00:27:90:0c:d0:7c;CM-QOS=1.1;CM-VER=3.0;
    2021-3-22, 13:55:02Notice (6)Honoring MDD; IP provisioning mode = IPv4
    2021-3-22, 13:55:01Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:a5:6e:83:05:48;CMTS-MAC=00:27:90:0c:d0:7c;CM-QOS=1.0;CM-VER=3.0;
    2021-3-22, 13:54:43Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=44:a5:6e:83:05:48;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
    2021-3-22, 13:54:42Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=44:a5:6e:83:05:48;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
    2021-3-22, 13:54:41Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:83:05:48;CMTS-MAC=00:27:90:0c:d0:7c;CM-QOS=1.1;CM-VER=3.0;
    2021-3-22, 13:54:18Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=44:a5:6e:83:05:48;CMTS-MAC=00:27:90:0c:d0:7c;CM-QOS=1.1;CM-VER=3.0;
    2021-3-22, 13:54:16Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:83:05:48;CMTS-MAC=00:27:90:0c:d0:7c;CM-QOS=1.1;CM-VER=3.0;
    2021-3-22, 13:54:00Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=44:a5:6e:83:05:48;CMTS-MAC=00:27:90:0c:d0:7c;CM-QOS=1.1;CM-VER=3.0;
    2021-3-22, 13:53:58Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=44:a5:6e:83:05:48;CMTS-MAC=00:27:90:0c:d0:7c;CM-QOS=1.1;CM-VER=3.0;
    2021-3-22, 13:53:57Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:83:05:48;CMTS-MAC=00:27:90:0c:d0:7c;CM-QOS=1.1;CM-VER=3.0;
    2021-3-22, 13:53:37Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=44:a5:6e:83:05:48;CMTS-MAC=00:27:90:0c:d0:7c;CM-QOS=1.1;CM-VER=3.0;
    2021-3-22, 13:53:36Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:83:05:48;CMTS-MAC=00:27:90:0c:d0:7c;CM-QOS=1.1;CM-VER=3.0;
    2021-3-22, 13:53:35Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=44:a5:6e:83:05:48;CMTS-MAC=00:27:90:0c:d0:7c;CM-QOS=1.1;CM-VER=3.0;
    2021-3-22, 13:53:33Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=44:a5:6e:83:05:48;CMTS-MAC=00:27:90:0c:d0:7c;CM-QOS=1.1;CM-VER=3.0;
    2021-3-22, 13:52:44Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=44:a5:6e:83:05:48;CMTS-MAC=00:27:90:0c:d0:7c;CM-QOS=1.1;CM-VER=3.0;
    2021-3-22, 13:52:42Warning (5)MDD message timeout;CM-MAC=44:a5:6e:83:05:48;CMTS-MAC=00:27:90:0c:d0:7c;CM-QOS=1.1;CM-VER=3.0;
    2021-3-22, 13:52:40Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=44:a5:6e:83:05:48;CMTS-MAC=00:27:90:0c:d0:7c;CM-QOS=1.1;CM-VER=3.0;
    2021-3-21, 23:17:41Notice (6)WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
    2021-3-21, 23:08:33Notice (6)WiFi Interface [wl0] set to Channel 4 (Side-Band Channel:N/A) - Reason:INTERFERENCE
    2021-3-21, 23:08:32Notice (6)WiFi Interface [wl1] set to Channel 157 (Side-Band Channel:N/A) - Reason:INTERFERENCE
    2021-3-21, 23:08:28Notice (6)WiFi Interface [wl0] set to Channel 4 (Side-Band Channel:8) - Reason:GUI
    2021-3-21, 23:07:13Notice (6)WiFi Interface [wl1] set to Channel 149 (Side-Band Channel:N/A) - Reason:INTERFERENCE
    2021-3-21, 23:07:13Notice (6)WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE
    2021-3-21, 23:07:09Notice (6)WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:7) - Reason:GUI
    2021-3-21, 19:19:09Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:83:05:48;CMTS-MAC=00:27:90:0c:d0:7c;CM-QOS=1.1;CM-VER=3.0;
    2021-3-21, 19:18:28Error (4)Improper Configuration File CVC Format
    2021-3-21, 19:18:21Notice (6)TLV-11 - unrecognized OID;CM-MAC=44:a5:6e:83:05:48;CMTS-MAC=00:27:90:0c:d0:7c;CM-QOS=1.1;CM-VER=3.0;
    1970-1-1, 00:00:49Warning (5)DHCP WARNING - Non-critical field invalid in response ;CM-MAC=44:a5:6e:83:05:48;CMTS-MAC=00:27:90:0c:d0:7c;CM-QOS=1.0;CM-VER=3.0;
    1970-1-1, 00:00:47Notice (6)Honoring MDD; IP provisioning mode = IPv4
    1970-1-1, 00:00:40Notice (6)WiFi Interface [wl1] set to Channel 153 (Side-Band Channel:N/A) - Reason:INIT
    1970-1-1, 00:00:40Notice (6)WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INIT
    1970-1-1, 00:00:37Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=44:a5:6e:83:05:48;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
    2021-3-21, 23:55:08Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:a5:6e:83:05:48;CMTS-MAC=00:27:90:0c:d0:7c;CM-QOS=1.1;CM-VER=3.0;
    2021-3-21, 23:53:07Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:a5:6e:83:05:48;CMTS-MAC=00:27:90:0c:d0:7c;CM-QOS=1.1;CM-VER=3.0;
    2021-3-21, 23:51:28Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:a5:6e:83:05:48;CMTS-MAC=00:27:90:0c:d0:7c;CM-QOS=1.1;CM-VER=3.0;

     

     

    Here's the screenshot of the connection page:

     

    really appreciate the help.

     

    Is there any documentation to help better understand the logs?

  • Infosec_stoic's avatar
    Infosec_stoic
    Aspirant
    Mar 23, 2021

    Sorry no idea why It didn't post the screenshot.

    • plemans's avatar
      plemans
      Guru - Experienced User
      Mar 24, 2021

      Your power levels are out of spec (to high) and you have errors in your line. 

      check your line. You might actually need a signal attenuator or splitter in line to drop power to get it in spec .

      Otherwise your isp will need to check the line

      • Infosec_stoic's avatar
        Infosec_stoic
        Aspirant
        Mar 24, 2021

        Awesome! 

         

        Out of curiosity, could you help me understand how you came to that conclusion? What are the power levels normally supposed to be at? How where you able to verify the errors? 

         

        Sorry for all the questions :) Networking isnt a strongpoint of mine, but I aim to get better!  

         

        Thanks again for the help!