New Contributor
•
15 Messages
T3 and T4 timeouts
My modem (SB 183) has been resetting several times a day for at least the past month.
Event log looks like this:
| Mon Jan 25 04:02:11 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Mon Jan 25 04:01:33 2016 | Critical (3) | No Ranging Response received - T3 time-out | Mon Jan 25 04:01:28 2016 | Notice (6) | TLV-11 - unrecognized OID;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;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:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.0;CM-VER=3.0; | Time Not Established | Notice (6) | Honoring MDD; IP provisioning mode = IPv4 | Mon Jan 25 04:00:50 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Mon Jan 25 03:58:40 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Mon Jan 25 03:58:01 2016 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Mon Jan 25 00:57:03 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Mon Jan 25 00:56:30 2016 | Critical (3) | No Ranging Response received - T3 time-out | Mon Jan 25 00:55:42 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Mon Jan 25 00:53:32 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Mon Jan 25 00:52:53 2016 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Mon Jan 25 00:14:47 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Mon Jan 25 00:13:22 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Mon Jan 25 00:11:12 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Sun Jan 24 07:00:37 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Sun Jan 24 01:57:38 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Sat Jan 23 06:02:38 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Sat Jan 23 01:06:05 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Sat Jan 23 01:02:21 2016 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Fri Jan 22 16:34:35 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Fri Jan 22 16:34:11 2016 | Critical (3) | No Ranging Response received - T3 time-out | Fri Jan 22 16:33:13 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Fri Jan 22 16:29:01 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Fri Jan 22 16:28:23 2016 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Fri Jan 22 09:33:15 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Fri Jan 22 09:32:35 2016 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Fri Jan 22 07:52:22 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Fri Jan 22 07:51:41 2016 | Critical (3) | No Ranging Response received - T3 time-out | Fri Jan 22 07:50:59 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Fri Jan 22 07:46:48 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Fri Jan 22 07:46:23 2016 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Fri Jan 22 04:15:21 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Fri Jan 22 01:07:27 2016 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Time Not Established | Critical (3) | DHCP FAILED - Request sent, No response;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.0;CM-VER=3.0; | Thu Jan 21 19:48:57 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Thu Jan 21 19:46:47 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Thu Jan 21 19:46:09 2016 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Thu Jan 21 10:23:56 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Thu Jan 21 10:22:36 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Thu Jan 21 10:18:25 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Thu Jan 21 10:17:52 2016 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Thu Jan 21 09:22:43 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Thu Jan 21 09:21:21 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Thu Jan 21 09:17:10 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Thu Jan 21 09:16:34 2016 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Thu Jan 21 08:53:15 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Thu Jan 21 08:49:10 2016 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Thu Jan 21 08:19:51 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Thu Jan 21 08:19:40 2016 | Critical (3) | No Ranging Response received - T3 time-out | Thu Jan 21 08:18:21 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Thu Jan 21 08:16:11 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Thu Jan 21 06:26:05 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Thu Jan 21 06:26:04 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Thu Jan 21 06:24:43 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Thu Jan 21 06:22:33 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Thu Jan 21 06:21:57 2016 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Thu Jan 21 05:30:42 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Thu Jan 21 00:19:11 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Thu Jan 21 00:18:38 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Thu Jan 21 00:18:29 2016 | Critical (3) | No Ranging Response received - T3 time-out | Thu Jan 21 00:17:39 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Thu Jan 21 00:15:29 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Thu Jan 21 00:14:58 2016 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Wed Jan 20 23:12:12 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Wed Jan 20 10:37:42 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Wed Jan 20 10:34:04 2016 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Wed Jan 20 09:29:28 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Wed Jan 20 09:28:05 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Wed Jan 20 09:23:51 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Wed Jan 20 09:23:06 2016 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Tue Jan 19 20:34:49 2016 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Tue Jan 19 20:29:12 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Tue Jan 19 20:29:12 2016 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Tue Jan 19 20:29:10 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Tue Jan 19 20:29:02 2016 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Tue Jan 19 20:16:59 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Tue Jan 19 20:16:59 2016 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Tue Jan 19 20:16:57 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Tue Jan 19 20:16:42 2016 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Tue Jan 19 20:16:37 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Tue Jan 19 20:16:35 2016 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Tue Jan 19 20:13:58 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Tue Jan 19 20:13:54 2016 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Tue Jan 19 20:12:58 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Tue Jan 19 20:12:54 2016 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Tue Jan 19 20:12:45 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Tue Jan 19 20:12:45 2016 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Tue Jan 19 20:12:44 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Tue Jan 19 20:12:39 2016 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Tue Jan 19 20:12:37 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Tue Jan 19 20:12:37 2016 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Tue Jan 19 20:10:20 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Tue Jan 19 20:10:20 2016 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Tue Jan 19 20:10:18 2016 | Critical (3) | SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Tue Jan 19 20:10:17 2016 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Tue Jan 19 20:08:58 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Tue Jan 19 20:08:52 2016 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; | Tue Jan 19 20:07:59 2016 | Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:e1:1a;CMTS-MAC=50:57:a8:89:72:9e;CM-QOS=1.1;CM-VER=3.0; |
||||||
Tecknowhelp
Valued Contributor II
•
2.8K Messages
10 years ago
T3 errors are usually caused by issues with the upstream, while T4 are usually caused by issues with the downstream. What are your signal levels?
PS. You probably want to edit out your CM-MAC address, since this is unique to your modem and should be kept private.
0
0
gm5
New Contributor
•
15 Messages
10 years ago
0
0
gm5
New Contributor
•
15 Messages
10 years ago
0
0
gm5
New Contributor
•
15 Messages
10 years ago
I edited the CM-MAC out of my 2nd post, but it won't let me edit the original post.
0
0
Tecknowhelp
Valued Contributor II
•
2.8K Messages
10 years ago
Signal levels look spot on. Not sure why you would be getting T3/T4 errors. Do you have the gateway connected directly to a normal electrical socket? Maybe a moderator can take a look and see something we can't.
0
0
gm5
New Contributor
•
15 Messages
10 years ago
It's plugged into a power strip.
0
0
Tecknowhelp
Valued Contributor II
•
2.8K Messages
10 years ago
I am just pulling at straws, but slight power disruptions (too slight for you to see) can cause disruption in the modem tuning into the cable signal. These disruption are caused by other devices on the strip needing power, causing the power to the other outlets to drop for a split second. That is why surge protectors with isolated outlets are best. Try connecting the power for the gateway directly into the wall and see if T3/T4 continue in logs.
0
0
gm5
New Contributor
•
15 Messages
10 years ago
I'll give it shot, but I've had the same set up for at least 3 years now, same surge protector/power strip with all the same things plugged into it. These timeouts started happening out of the blue. I had an SB 6121 and thought it might be the modem so I picked up a 6183. It got a little bit better but obviously still happening.
0
0
gm5
New Contributor
•
15 Messages
10 years ago
Also even when it's not dropping the connection is funky, sometimes I have to refresh a webpage 4 or 5 times before it will load.
0
0
gm5
New Contributor
•
15 Messages
10 years ago
Plugged it directly into the wall, no change. 2 T3 timeouts this morning according to the event log.
0
0
gm5
New Contributor
•
15 Messages
10 years ago
0
0
ChrisL
Former Moderator
•
7.1K Messages
10 years ago
Taking into consideration everything you've tried it may be time to see about getting a technician out to troubleshoot further.
0
0