Newcomer

latency and thoughput issues

For a year now going round and round with this.

Trace route  510ms 100ms right to Spectrums local network

weekly basis T3 /T4 / MDD / TOD / Timing Synchronization failures

FTP tranfer 10 gig  5/6 hrs transfer speed in kb.

Zip File 948MB takes over 15mins. Should take appox 1 min to 2 tops.

During the day forget about it at night time increases delay in time.

Correctables and Un Correctables.

All new wiring in house / new wire to tap.

ultimate 200 service

Tv pixelates every night besides Spectrum wants increase their billing

Any suggestions

 

 

 

 

 

45 REPLIES
Expert

Re: latency and thoughput issues

Post some meaningfull data... signal level and error log pages, don't reset it, need to see real history

 

Highlighted
Expert

Re: latency and thoughput issues

"Zip File 948MB takes over 15mins. Should take appox 1 min to 2 tops."

 

uhhhh, nope, 948 MB is 9,480 mb and that will take at least 5 minutes if everythings good which yours is not....

 

Newcomer

Re: latency and thoughput issues

Performing traceroute to (24.25.5.60) from (71.77.140.xxx), 30 hops max, 1000 byte packets

 

01   71.77.128.1        20 ms  10 ms  10 ms

02   24.88.225.126      30 ms  30 ms  40 ms

03   24.25.39.14        20 ms  20 ms  20 ms

04   24.93.64.190       30 ms  20 ms  30 ms

05   24.93.64.119       10 ms  30 ms  24.93.64.117       10 ms

06   24.25.5.60         40 ms  520 ms  10 ms

Traceroute complete.

Performing traceroute to (24.25.5.60) from (71.77.140.xxx), 30 hops max, 1000 byte packets

01   71.77.128.1        20 ms  10 ms  10 ms
02   24.88.225.126      260 ms  30 ms  20 ms
03   24.25.39.14        30 ms  10 ms  10 ms
04   24.93.64.190       20 ms  30 ms  20 ms
05   24.93.64.119       40 ms  24.93.64.90        20 ms  10 ms
06   24.25.5.60         10 ms  20 ms  20 ms
Traceroute complete.

    Performing traceroute to (24.25.5.60) from (71.77.140.xxx), 30 hops max, 562 byte packets

01   71.77.128.1        10 ms  10 ms  20 ms
02   24.88.225.126      40 ms  70 ms  340 ms
03   24.25.39.14        30 ms  10 ms  30 ms
04   24.93.64.190       20 ms  20 ms  20 ms
05   24.93.64.103       30 ms  24.93.64.90        20 ms  20 ms

 

 

Time

Priority

Description

2018-1-16, 04:22:21

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

2018-1-16, 04:22:21

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

2018-1-16, 04:22:22

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

2018-1-16, 04:22:23

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

2018-1-16, 04:22:24

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

2018-1-16, 04:22:25

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

2018-1-16, 04:22:48

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

2018-1-16, 04:22:49

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

2018-1-16, 04:22:51

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

2018-1-16, 04:22:52

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

2018-1-16, 04:23:04

Critical (3)

No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.0;CM-VER=3.0;

2018-1-16, 04:33:16

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;

2018-1-16, 04:33:22

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;

2018-1-16, 04:33:39

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;

2018-1-16, 04:33:40

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;

2018-1-16, 04:33:40

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;

2018-1-16, 04:33:41

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;

2018-1-16, 04:33:43

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;

2018-1-16, 04:57:49

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;

2018-1-16, 04:58:42

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;

2018-1-16, 04:58:48

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;

2018-1-16, 04:59:04

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;

2018-1-16, 04:59:05

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;

2018-1-16, 04:59:08

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;

2018-1-16, 04:59:09

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;

2018-1-16, 04:59:11

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;

2018-1-16, 04:59:12

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;

2018-1-16, 04:59:12

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;

2018-1-16, 04:59:20

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

2018-1-16, 04:59:22

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

1970-1-1, 00:00:41

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

2018-1-16, 05:47:31

Critical (3)

REG RSP not received;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;

2018-1-16, 05:56:11

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;

1970-1-1, 00:00:38

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

1970-1-1, 00:00:41

Notice (6)

WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INIT

1970-1-1, 00:00:41

Notice (6)

WiFi Interface [wl1] set to Channel 161 (Side-Band Channel:157) - Reason:INIT

1970-1-1, 00:00:47

Notice (6)

Overriding MDD IP initialization parameters; IP provisioning mode = IPv6

2018-1-17, 20:19:01

Error (4)

Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;

2018-1-17, 20:19:01

Error (4)

Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;

2018-1-17, 20:19:05

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;

Newcomer

Re: latency and thoughput issues

Performing traceroute to (24.25.5.60) from (71.77.140.xxx), 30 hops max, 562 byte packets

01   71.77.128.1        10 ms  10 ms  10 ms
02   24.88.225.126      220 ms  40 ms  110 ms
03   24.25.39.14        10 ms  40 ms  20 ms
04   24.93.64.190       20 ms  30 ms  20 ms
05   24.93.64.117       30 ms  24.93.64.119       20 ms  24.93.64.103       10 ms
06   24.25.5.60         10 ms  20 ms  10 ms
Traceroute complete.

 

 
 
 
Time Priority Description
2018-1-30, 11:13:10Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.0;CM-VER=3.0;
2018-1-30, 11:13:54Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2018-1-30, 11:13:54Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2018-1-30, 11:14:19Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2018-1-30, 11:14:19Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2018-1-30, 11:14:21Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2018-1-30, 11:14:21Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2018-1-30, 11:14:31Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2018-1-30, 11:14:44Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2018-1-30, 11:16:28Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
2018-1-30, 11:16:33Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
2018-1-30, 11:16:40Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
2018-1-30, 11:16:42Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
2018-1-30, 11:16:56Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
2018-1-30, 11:22:31Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
2018-1-30, 11:23:19Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
2018-1-30, 11:29:43Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
2018-2-2, 16:17:45Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
2018-2-2, 16:17:49Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
2018-2-2, 16:17:56Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
2018-2-2, 16:18:07Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
2018-2-2, 16:18:07Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
1970-1-1, 00:00:39Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2018-2-8, 14:34:38Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
2018-2-8, 14:34:44Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
2018-2-8, 14:35:03Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
2018-2-8, 14:35:04Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
2018-2-8, 14:35:04Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
2018-2-8, 14:35:05Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
2018-2-8, 14:35:07Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
2018-2-8, 14:35:08Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
2018-2-8, 14:35:09Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
2018-2-8, 14:35:16Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2018-2-8, 14:35:16Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:41Notice (6)WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:N/A) - Reason:INIT
1970-1-1, 00:00:41Notice (6)WiFi Interface [wl1] set to Channel 161 (Side-Band Channel:N/A) - Reason:INIT
1970-1-1, 00:00:41Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:02:27Notice (6)Overriding MDD IP initialization parameters; IP provisioning mode = IPv6
2018-2-8, 14:50:25Error (4)Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
2018-2-8, 14:50:25Error (4)Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
Newcomer

Re: latency and thoughput issues

2018-2-2, 16:17:45Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
2018-2-2, 16:17:48Warning (5)MDD message timeout;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
2018-2-2, 16:17:49Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
2018-2-2, 16:17:54Warning (5)MDD message timeout;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
2018-2-2, 16:17:56Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
2018-2-2, 16:18:07Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;
2018-2-2, 16:18:07Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:d9:8a:f8;CMTS-MAC=00:17:10:88:2d:c2;CM-QOS=1.1;CM-VER=3.0;

  

Newcomer

Re: latency and thoughput issues

After Modem rebooted today because of signal errors

that with 6dB att. attached to back of modem

 

Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1LockedQAM25624597000000 Hz-1.6 dBmV37.9 dB10952954
2LockedQAM25610513000000 Hz-0.6 dBmV39.2 dB210
3LockedQAM25611519000000 Hz-0.8 dBmV39 dB260
4LockedQAM25612525000000 Hz-0.7 dBmV39 dB300
5LockedQAM25613531000000 Hz-0.7 dBmV39 dB280
6LockedQAM25614537000000 Hz-0.7 dBmV39 dB260
7LockedQAM25615543000000 Hz-1.1 dBmV38.7 dB270
8LockedQAM25616549000000 Hz-1.2 dBmV38.7 dB257
9LockedQAM25617555000000 Hz-1.6 dBmV38.4 dB250
10LockedQAM25618561000000 Hz-1.7 dBmV38.3 dB230
11LockedQAM25619567000000 Hz-1.9 dBmV38.3 dB300
12LockedQAM25620573000000 Hz-2 dBmV38.1 dB300
13LockedQAM25621579000000 Hz-2.2 dBmV37.9 dB280
14LockedQAM25622585000000 Hz-2.2 dBmV37.7 dB320
15LockedQAM25623591000000 Hz-1.7 dBmV38 dB220
16LockedQAM2569507000000 Hz-0.6 dBmV38.7 dB230
17LockedQAM25625603000000 Hz-1.1 dBmV39 dB310
18LockedQAM25626609000000 Hz-1 dBmV39 dB310
19LockedQAM25627615000000 Hz-0.6 dBmV39 dB310
20LockedQAM25628621000000 Hz0 dBmV39.5 dB310
21LockedQAM25629627000000 Hz0.2 dBmV39.4 dB290
22LockedQAM25630633000000 Hz0.3 dBmV39.9 dB320
23LockedQAM25631639000000 Hz0.6 dBmV39.9 dB293
24LockedQAM25632645000000 Hz0.7 dBmV39.9 dB310
 
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1LockedATDMA65120 Ksym/sec24000000 Hz45.5 dBmV
2LockedTDMA52560 Ksym/sec19200000 Hz44.3 dBmV
3LockedATDMA75120 Ksym/sec30400000 Hz46.8 dBmV
4LockedATDMA85120 Ksym/sec36800000 Hz47 dBmV
5Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV
6Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV
7Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV
8Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV
Newcomer

Re: latency and thoughput issues

Performing traceroute to (24.25.5.60) from (71.77.140.xxx), 30 hops max, 1000 byte packets

 

01   71.77.128.1        10 ms  10 ms  10 ms

02   24.88.225.126      220 ms  60 ms  60 ms

03   24.25.39.14        90 ms  50 ms  20 ms

04   24.93.64.190       40 ms  30 ms  70 ms

05   24.93.64.117       10 ms  24.93.64.103       20 ms  24.93.64.117       20 ms

06   24.93.64.117       20 ms  24.25.5.60         10 ms  10 ms

Traceroute complete.

Performing traceroute to (24.25.5.60) from (71.77.140.xxx), 30 hops max, 1000 byte packets

 

01   71.77.128.1        10 ms  20 ms  10 ms

02   24.88.225.126      300 ms  30 ms  30 ms

03   24.25.39.14        10 ms  30 ms  110 ms

04   24.93.64.190       90 ms  30 ms  30 ms

05   24.93.64.117       40 ms  24.93.64.90        10 ms  24.93.64.117       20 ms

06   24.25.5.60         10 ms  10 ms  30 ms

Traceroute complete.

Performing traceroute to (24.25.5.60) from (71.77.140.xxx), 30 hops max, 1000 byte packets

 

01   71.77.128.1        20 ms  10 ms  10 ms

02   24.88.225.126      30 ms  30 ms  40 ms

03   24.25.39.14        20 ms  20 ms  20 ms

04   24.93.64.190       30 ms  20 ms  30 ms

05   24.93.64.119       10 ms  30 ms  24.93.64.117       10 ms

06   24.25.5.60         40 ms  520 ms  10 ms

Traceroute complete.

Newcomer

Re: latency and thoughput issues

Even 5 mins is better then 15+ mins

10 min traffic jam.

Major utilization issue  not getting even close to advertized speeds

 

 

Expert

Re: latency and thoughput issues

You have a corroded or loose connection somewhere that's allowing broadcast TV ch 35 in.

All connections need be a tad more than finger tight, check backsides of wall plates.

The 6 dB attenuator is not needed.

1LockedQAM25624597000000 Hz-1.6 dBmV37.9 dB10952954

Since 597 is getting trashed and it's the modems home channel, and has more uncorrecteds than correcteds, that's your problem.

What's your zip code?