vegas50000's profile

New Contributor

 • 

74 Messages

Closed

Packet loss correlating with massive jump of Uncorrectable codewords

This issue started about a week ago.  I noticed weird dropouts/lag bursts and then saw a crazy high number of uncorrectable codewords in the SB6183 (modem) status page.

So I began actively monitoring to document the issue (screenshots below).  Should I schedule a technician now or ride out the storm?  I am currently on the Ultimate internet plan with the Cox Service Protection Plan.



Before



After

Packet Loss


New Contributor

 • 

74 Messages

Since this forum can't handle images well, please click on them to see what I'm referring too.

Valued Contributor II

 • 

2.8K Messages

First, FYI, reason images don't fit is there is a max size that can be handled. I think it's 400x500. Not a big deal though.

Second, how comes tracert is missing hop 1 data?

Last, your upstream is on the low side. May be prone to intermid. interference. I needed a filter on my modem because the connection was direct from the street and my signal was TOO high.  What do the logs say?

New Contributor

 • 

74 Messages

Here is another incident:

Before:

After:

Packet Loss:

Valued Contributor II

 • 

2.8K Messages

Again, why is tracert missing first hop? In the first part it shows some latency spikes but then doesn't include it in graph. Need to isolate if issue is modem>router or modem>cox.

Also, can you please post the logs? Specifically from around the time the packet test showed the most packet loss. 

New Contributor

 • 

74 Messages

It's not missing the 1st hop - it's not shown because there is nothing to show except a flat line.  There is no issue with the connection between my computer and router.  It's plugged in with an ethernet cable, end of story.

The logs show nothing at the time of the connection issue.

Event Log

The table below contains the log of events that the SB6183 has detected. This log can be important to the service provider to help diagnose and correct problems, if any should occur.

TimePriorityDescription
Sun Apr 24 11:22:17 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:ca:08:71:9c:b7;CMTS-MAC=70:ca:9b:a7:92:a0;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 24 11:21:36 2016 Notice (6) TLV-11 - unrecognized OID;CM-MAC=6c:ca:08:71:9c:b7;CMTS-MAC=70:ca:9b:a7:92:a0;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:71:9c:b7;CMTS-MAC=70:ca:9b:a7:92:a0;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv4
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Time Not Established Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=6c:ca:08:71:9c:b7;CMTS-MAC=70:ca:9b:a7:92:a0;CM-QOS=1.0;CM-VER=3.0;
Tue Apr 19 13:35:07 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:71:9c:b7;CMTS-MAC=70:ca:9b:a7:92:a0;CM-QOS=1.1;CM-VER=3.0;
Tue Apr 19 13:35:01 2016 Critical (3) SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=6c:ca:08:71:9c:b7;CMTS-MAC=70:ca:9b:a7:92:a0;CM-QOS=1.1;CM-VER=3.0;
Tue Apr 19 13:31:00 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=6c:ca:08:71:9c:b7;CMTS-MAC=70:ca:9b:a7:92:a0;CM-QOS=1.1;CM-VER=3.0;
Tue Apr 19 10:40:03 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=6c:ca:08:71:9c:b7;CMTS-MAC=70:ca:9b:a7:92:a0;CM-QOS=1.1;CM-VER=3.0;
Tue Apr 19 10:35:54 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;CMTS-MAC=70:ca:9b:a7:92:a0;CM-QOS=1.1;CM-VER=3.0;
Tue Apr 19 10:35:53 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=6c:ca:08:71:9c:b7;CMTS-MAC=70:ca:9b:a7:92:a0;CM-QOS=1.1;CM-VER=3.0;
Thu Apr 14 22:45:02 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:ca:08:71:9c:b7;CMTS-MAC=70:ca:9b:a7:92:a0;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Wed Apr 13 18:04:39 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:71:9c:b7;CMTS-MAC=70:ca:9b:a7:92:a0;CM-QOS=1.1;CM-VER=3.0;
Tue Apr 05 03:25:09 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:ca:08:71:9c:b7;CMTS-MAC=70:ca:9b:a7:92:a0;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Tue Apr 05 01:50:43 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:ca:08:71:9c:b7;CMTS-MAC=70:ca:9b:a7:92:a0;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=6c:ca:08:71:9c:b7;CMTS-MAC=70:ca:9b:a7:92:a0;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Fri Apr 01 14:01:40 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;CMTS-MAC=70:ca:9b:a7:92:a0;CM-QOS=1.1;CM-VER=3.0;
Thu Mar 24 00:55:32 2016 Critical (3) SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=6c:ca:08:71:9c:b7;CMTS-MAC=70:ca:9b:a7:92:a0;CM-QOS=1.1;CM-VER=3.0;
Mon Mar 14 00:45:50 2016 Critical (3) No Ranging Response received - T3 time-out
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Time Not Established Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:ca:08:71:9c:b7;CMTS-MAC=70:ca:9b:a7:92:a0;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=6c:ca:08:71:9c:b7;CMTS-MAC=70:ca:9b:a7:92:a0;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=6c:ca:08:71:9c:b7;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 QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;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:71:9c:b7;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 QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;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:71:9c:b7;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 QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;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:71:9c:b7;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 QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;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:71:9c:b7;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 QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;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:71:9c:b7;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 QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;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:71:9c:b7;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 QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;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:71:9c:b7;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 QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;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:71:9c:b7;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 QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;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:71:9c:b7;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 QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;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:71:9c:b7;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 QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;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:71:9c:b7;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 QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;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:71:9c:b7;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 QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;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:71:9c:b7;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 QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;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:71:9c:b7;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 QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;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:71:9c:b7;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 QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;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:71:9c:b7;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 QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;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:71:9c:b7;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 QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;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:71:9c:b7;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 QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;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:71:9c:b7;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 QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;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:71:9c:b7;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 QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;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:71:9c:b7;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 QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;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:71:9c:b7;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 QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;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:71:9c:b7;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 QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;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:71:9c:b7;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 QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;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:71:9c:b7;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 QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;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:71:9c:b7;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 QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;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:71:9c:b7;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 QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;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:71:9c:b7;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 QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;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:71:9c:b7;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 QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;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:71:9c:b7;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 QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;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:71:9c:b7;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 QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;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:71:9c:b7;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 QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;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:71:9c:b7;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 QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;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:71:9c:b7;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 QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;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:71:9c:b7;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 QAM/QPSK symbol timing;;CM-MAC=6c:ca:08:71:9c:b7;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:71:9c:b7;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

New Contributor

 • 

74 Messages

No packet loss on my LAN:

Valued Contributor II

 • 

2.8K Messages

vegas50000 said:
It's not missing the 1st hop - it's not shown because there is nothing to show except a flat line.

Then how come it showed in the test above? I didn't think there was a problem on your network, I was asking why the data was missing. Since the new image shows everything good, consider it moot.

The logs are interesting. The first thing I see are T3 errors through out the log. Those aren't good, but they don't tell much about the problem. Next, and most importantly I see T4 errors, without the usual T3 errors next to them, and MDD messaging. This makes me think the channel ID's are being juggled to maximize throughput, which you sometimes see when the node is congested. When the channels change, they probably occur uncorrectables. This is all guess work, so take it with a grain of salt.

Moderator

 • 

4.3K Messages

Hi Vegas50000,

Your upstream modem levels aren't where I'd like them to be. I suggest we schedule a service call so an on-site tech can resolve this for you! Send an email to cox.help@cox.com with a link to this page, your full name, and address. We can get a service call scheduled for you.

New Contributor

 • 

74 Messages

Becky said:
Hi Vegas50000,

Your upstream modem levels aren't where I'd like them to be. I suggest we schedule a service call so an on-site tech can resolve this for you! Send an email to cox.help@cox.com with a link to this page, your full name, and address. We can get a service call scheduled for you.

Thanks for checking!  I have sent an email to setup a service call.

New Contributor

 • 

74 Messages

The connection issues persist - here is another example where the modem errors due to a bad signal on Cox's end, which in turn causes packet loss.  Any chance we could get the maintenance guys working on this?



Former Moderator

 • 

7.1K Messages

@vegas50000

I looked from our end however I'm simply not seeing any loss from us to the modem.  Can you see if you can duplicate these results without the router attached?

New Contributor

 • 

74 Messages

Packet loss and errors continue:

Valued Contributor II

 • 

2.8K Messages

Your still getting packet loss inside your 192.168.1.1 network. Also, I thought you said hop 1 is left out because its nothing but a straight line.... why does the new test now include it.. and its not a straight line? 

New Contributor

 • 

74 Messages

Tecknowhelp said:

Your still getting packet loss inside your 192.168.1.1 network. Also, I thought you said hop 1 is left out because its nothing but a straight line.... why does the new test now include it.. and its not a straight line? 

Please don't comment if you don't know what you're talking about.  Packet loss is indicated by a red line on the graph.  There is no packet loss shown for hop 1.  

New Contributor

 • 

74 Messages

1 day of uptime and the errors are piling up again.  So far two technican calls have not resolved the issue.  Should I call once a week until this is resolved?

Related Content

  • Closed

    0

    0

  • Closed

    4

    0

  • Closed

    2

    0

  • Closed

    3

    0

  • Closed

    0

    0

Recent Discussions

View More

Loading...