eggnet's profile

New Contributor

 • 

1 Message

Closed

> 1% upload packet loss

Hello,

I have upload packet loss, approximately > 1% now, over a long interval. It is intermittent. It happened a few months ago and cleared up roughly around 7/31/2015. I had a number of Cox technicians out, none of them fixed it while on-site. But a few days after the last one was here, the errors went away.

The errors are back.

I know it is upload loss based on iperf results to a VM I host which I did not include.

In any case, I've included pingplotter stats which show no packet loss to my router, but packet loss to the default gateway and www.google.com at the same error rate.

Here are some logs from my modem, which is an SB6183:

Sun Mar 20 17:26:44 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:73:0a:13;CMTS-MAC=00:11:92:21:56:59;CM-QOS=1.1;CM-VER=3.0;
Sat Mar 19 08:18:36 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:ca:08:73:0a:13;CMTS-MAC=00:11:92:21:56:59;CM-QOS=1.1;CM-VER=3.0;
Sat Mar 19 08:17:53 2016 Notice (6) TLV-11 - unrecognized OID;CM-MAC=6c:ca:08:73:0a:13;CMTS-MAC=00:11:92:21:56:59;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=6c:ca:08:73:0a:13;CMTS-MAC=00:11:92:21:56:59;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv4
Wed Mar 09 01:27:54 2016 Critical (3) No Ranging Response received - T3 time-out
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:73:0a:13;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=6c:ca:08:73:0a:13;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

I'm pretty sure there is nothing wrong with my modem, router, or even my drop. I've already tried multiple routers for this incident. I've replaced, historically, my cable modem several times. But not for this incident.

Mid last year, a technician replaced my drop. Reasonably sure that is still good. The tap is in front of my house.

There was some maintenance in front of my house with the sidewalk, not sure if that is relevant.

In any case, I'd like to get this resolved ideally with less than the ~3 or 4 on sites required last time, the bulk of most of which were just me convincing the technicians that yes, there is in fact a problem and no, sending 50 pings one time with the windows command line tool showing no packet loss does not prove the line is clean. Intermittent problems are tough to see.

Just looking for the most efficient way to resolve.

Former Moderator

 • 

7.1K Messages

@eggnet

Would it be possible to try this test without the router to be thorough?

Recent Discussions

View More

Loading...