Upstream packet loss and jitter
Hey Guys, Non-stop packetloss all day.
Cox is saying everything is okay, I have been graphing/monitoring the loss for months.
What resolutions do we have besides switching ISPs? Are there any ...
Forum Discussion
I do see some uncorrectables normally. but on a single channel or 2.
That means noise is leaking into the line on those frequencies. Might be "acceptable" under Cox minimum standards, but it's not normal.
After the reboot 4~ hours ago. There are no uncorrectables or corrected, but still packet loss.
That means the large number of uncorrectables you saw before was probably the result of overnight maintenance. The good news is that you probably don't have a major noise ingress problem, but that bad news is that it's a more complicated problem to solve. Hopefully Cox can figure it out.
Uncorrectables are back in the thousands. More events.
After days of emailing/dealing with COX help/support we have got no where. They will not even admit seeing the issue in the ping plotters. Showing the packet loss starting and going to the end, across multiple external endpoints.
Ive also started to ping plotter only internal routes to cox. 10.x.128.1 etc. and they all have the same packet loss at the same time as the external routes drop.
Tue Jul 06 03:01:09 2021 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 03:02:16 2021 5 RCS Partial Service;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 04:19:26 2021 3 No Ranging Response received - T3 time-out;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 04:49:00 2021 5 RCS Partial Service;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 08:46:14 2021 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 08:46:16 2021 5 RCS Partial Service;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 08:55:21 2021 3 No Ranging Response received - T3 time-out;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 08:56:08 2021 5 RCS Partial Service;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 10:52:29 2021 5 Lost MDD Timeout;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 10:58:00 2021 5 RCS Partial Service;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 03:01:09 2021 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 03:02:16 2021 5 RCS Partial Service;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 04:19:26 2021 3 No Ranging Response received - T3 time-out;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 04:49:00 2021 5 RCS Partial Service;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 08:46:14 2021 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 08:46:16 2021 5 RCS Partial Service;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 08:55:21 2021 3 No Ranging Response received - T3 time-out;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 08:56:08 2021 5 RCS Partial Service;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 10:52:29 2021 5 Lost MDD Timeout;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 10:58:00 2021 5 RCS Partial Service;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0;
