Re: Ping Spikes and dropped packets

Infosec_stoic · ‎2021-03-22

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 work in IT (on the information security side) I do a lot of work from home. As of right now some of my work has begun to suffer due to these high packet spikes and dropped packets (especially with security based applications like splunk). I'm constantly cutting out in meetings or I'm just dropping out altogether. Typically, I can normally fix most networking issues myself. However, this one seems to baffle me since I've never seen packet spikes like this. The packet spikes seem to occur every couple second’s ranging anywhere from 7 to 8 milliseconds all the way up to 2000 milliseconds and the occasional loss. The losses occur more frequently when I am involved in a virtual meetings, listening to music/videos, and gaming. not sure if this is an issue with the router/modem or my ISP. Ive contacted the ISP and they report no outages but im still not convinced (its a local power/water/and internet company) I have yet to try a factory reset on the device however I wanted to reach out and see if there was a solution prior to doing this. I will provide ping logs both wired and Wireless. Let me know if you need and thing else.

Wireless:

Reply from 192.168.0.1: bytes=32 time=8ms TTL=64

Reply from 192.168.0.1: bytes=32 time=18ms TTL=64

Reply from 192.168.0.1: bytes=32 time=10ms TTL=64

Reply from 192.168.0.1: bytes=32 time=63ms TTL=64

Reply from 192.168.0.1: bytes=32 time=1876ms TTL=64

Reply from 192.168.0.1: bytes=32 time=64ms TTL=64

Reply from 192.168.0.1: bytes=32 time=9ms TTL=64

Reply from 192.168.0.1: bytes=32 time=12ms TTL=64

Reply from 192.168.0.1: bytes=32 time=9ms TTL=64

Reply from 192.168.0.1: bytes=32 time=10ms TTL=64

Reply from 192.168.0.1: bytes=32 time=25ms TTL=64

Reply from 192.168.0.1: bytes=32 time=8ms TTL=64

Reply from 192.168.0.1: bytes=32 time=15ms TTL=64

Request timed out.

Reply from 192.168.0.1: bytes=32 time=1155ms TTL=64

Reply from 192.168.0.1: bytes=32 time=29ms TTL=64

Reply from 192.168.0.1: bytes=32 time=8ms TTL=64

Reply from 192.168.0.1: bytes=32 time=9ms TTL=64

Reply from 192.168.0.1: bytes=32 time=11ms TTL=64

Ping statistics for 192.168.0.1:

Packets: Sent = 120, Received = 119, Lost = 1 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 5ms, Maximum = 1925ms, Average = 130ms

Wired:

Reply from 192.168.0.1: bytes=32 time=8ms TTL=64

Reply from 192.168.0.1: bytes=32 time=18ms TTL=64

Reply from 192.168.0.1: bytes=32 time=1894ms TTL=64

Reply from 192.168.0.1: bytes=32 time=36ms TTL=64

Reply from 192.168.0.1: bytes=32 time=7ms TTL=64

Reply from 192.168.0.1: bytes=32 time=8ms TTL=64

Reply from 192.168.0.1: bytes=32 time=7ms TTL=64

Reply from 192.168.0.1: bytes=32 time=8ms TTL=64

Reply from 192.168.0.1: bytes=32 time=15ms TTL=64

Reply from 192.168.0.1: bytes=32 time=9ms TTL=64

Reply from 192.168.0.1: bytes=32 time=8ms TTL=64

Reply from 192.168.0.1: bytes=32 time=7ms TTL=64

Reply from 192.168.0.1: bytes=32 time=9ms TTL=64

Reply from 192.168.0.1: bytes=32 time=1923ms TTL=64

Reply from 192.168.0.1: bytes=32 time=69ms TTL=64

Reply from 192.168.0.1: bytes=32 time=7ms TTL=64

Reply from 192.168.0.1: bytes=32 time=6ms TTL=64

Reply from 192.168.0.1: bytes=32 time=8ms TTL=64

Reply from 192.168.0.1: bytes=32 time=7ms TTL=64

Reply from 192.168.0.1: bytes=32 time=6ms TTL=64

Reply from 192.168.0.1: bytes=32 time=7ms TTL=64

Reply from 192.168.0.1: bytes=32 time=6ms TTL=64

Reply from 192.168.0.1: bytes=32 time=7ms TTL=64

Reply from 192.168.0.1: bytes=32 time=1988ms TTL=64

Reply from 192.168.0.1: bytes=32 time=15ms TTL=64

Ping statistics for 192.168.0.1:

Packets: Sent = 120, Received = 120, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 6ms, Maximum = 1988ms, Average = 129ms

plemans · ‎2021-03-23

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 · ‎2021-03-23

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	Priority	Description
2021-3-23, 09:01:12	Warning (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:59	Critical (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:20	Error (4)	Improper Configuration File CVC Format
2021-3-22, 13:55:12	Notice (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:10	Warning (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:02	Notice (6)	Honoring MDD; IP provisioning mode = IPv4
2021-3-22, 13:55:01	Critical (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:43	Critical (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:42	Critical (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:41	Critical (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:18	Critical (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:16	Critical (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:00	Critical (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:58	Critical (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:57	Critical (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:37	Critical (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:36	Critical (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:35	Critical (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:33	Critical (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:44	Critical (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:42	Warning (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:40	Critical (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:41	Notice (6)	WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2021-3-21, 23:08:33	Notice (6)	WiFi Interface [wl0] set to Channel 4 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2021-3-21, 23:08:32	Notice (6)	WiFi Interface [wl1] set to Channel 157 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2021-3-21, 23:08:28	Notice (6)	WiFi Interface [wl0] set to Channel 4 (Side-Band Channel:8) - Reason:GUI
2021-3-21, 23:07:13	Notice (6)	WiFi Interface [wl1] set to Channel 149 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2021-3-21, 23:07:13	Notice (6)	WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2021-3-21, 23:07:09	Notice (6)	WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:7) - Reason:GUI
2021-3-21, 19:19:09	Critical (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:28	Error (4)	Improper Configuration File CVC Format
2021-3-21, 19:18:21	Notice (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:49	Warning (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:47	Notice (6)	Honoring MDD; IP provisioning mode = IPv4
1970-1-1, 00:00:40	Notice (6)	WiFi Interface [wl1] set to Channel 153 (Side-Band Channel:N/A) - Reason:INIT
1970-1-1, 00:00:40	Notice (6)	WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INIT
1970-1-1, 00:00:37	Critical (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:08	Critical (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:07	Critical (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:28	Critical (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 · ‎2021-03-23

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

plemans · ‎2021-03-24

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 · ‎2021-03-24

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!

plemans · ‎2021-03-24

Optimal power levels should be from -7.5dbmv to 7.5dbmv. You're quite high.

Also, the correctables/uncorrectables are the errors.

Plus you have channels that aren't locking. So it tends to indicate issues. with your power levels high, that's where I'd start.