New Poster
•
3 Messages
T3 & T4 Timeouts - Near Constant Disconnects
Two technicians have been to the property to attempt to fix the issue but have were unsuccesful. I would like to escalate to the advanced fix team but have been unable to do so.
I am experiencing frequent disconnects rendering my home network useless for long extended periods of time. Here is the most recent router event log:
Time | Priority | Description |
2021-02-20, 12:40:31 | Warning (5) | MDD message timeout;CM-MAC=bc:a5:11:d5:f7:44;CMTS-MAC=58:97:bd:2d:f5:5b;CM-QOS=1.1;CM-VER=3.1; |
2021-02-20, 12:40:13 | Warning (5) | Dynamic Range Window violation |
2021-02-20, 12:39:58 | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
2021-02-20, 12:39:48 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=bc:a5:11:d5:f7:44;CMTS-MAC=58:97:bd:2d:f5:5b;CM-QOS=1.1;CM-VER=3.1; |
2021-02-20, 12:39:39 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:a5:11:d5:f7:44;CMTS-MAC=58:97:bd:2d:f5:5b;CM-QOS=1.1;CM-VER=3.1; |
2021-02-20, 12:39:23 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:a5:11:d5:f7:44;CMTS-MAC=58:97:bd:2d:f5:5b;CM-QOS=1.1;CM-VER=3.1; |
2021-02-20, 12:39:22 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:a5:11:d5:f7:44;CMTS-MAC=58:97:bd:2d:f5:5b;CM-QOS=1.1;CM-VER=3.1; |
2021-02-20, 12:38:57 | Warning (5) | MDD message timeout;CM-MAC=bc:a5:11:d5:f7:44;CMTS-MAC=58:97:bd:2d:f5:5b;CM-QOS=1.1;CM-VER=3.1; |
2021-02-20, 12:38:55 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=bc:a5:11:d5:f7:44;CMTS-MAC=58:97:bd:2d:f5:5b;CM-QOS=1.1;CM-VER=3.1; |
2021-02-20, 12:37:51 | Warning (5) | MDD message timeout;CM-MAC=bc:a5:11:d5:f7:44;CMTS-MAC=58:97:bd:2d:f5:5b;CM-QOS=1.1;CM-VER=3.1; |
2021-02-20, 12:36:58 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:d5:f7:44;CMTS-MAC=58:97:bd:2d:f5:5b;CM-QOS=1.1;CM-VER=3.1; |
2021-02-20, 12:36:57 | Warning (5) | MDD message timeout;CM-MAC=bc:a5:11:d5:f7:44;CMTS-MAC=58:97:bd:2d:f5:5b;CM-QOS=1.1;CM-VER=3.1; |
2021-02-20, 12:36:51 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:d5:f7:44;CMTS-MAC=58:97:bd:2d:f5:5b;CM-QOS=1.1;CM-VER=3.1; |
2021-02-20, 12:36:49 | Warning (5) | MDD message timeout;CM-MAC=bc:a5:11:d5:f7:44;CMTS-MAC=58:97:bd:2d:f5:5b;CM-QOS=1.1;CM-VER=3.1; |
2021-02-20, 12:36:43 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:d5:f7:44;CMTS-MAC=58:97:bd:2d:f5:5b;CM-QOS=1.1;CM-VER=3.1; |
2021-02-20, 12:36:41 | Warning (5) | MDD message timeout;CM-MAC=bc:a5:11:d5:f7:44;CMTS-MAC=58:97:bd:2d:f5:5b;CM-QOS=1.1;CM-VER=3.1; |
2021-02-20, 12:36:40 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:d5:f7:44;CMTS-MAC=58:97:bd:2d:f5:5b;CM-QOS=1.1;CM-VER=3.1; |
2021-02-20, 12:36:39 | Warning (5) | MDD message timeout;CM-MAC=bc:a5:11:d5:f7:44;CMTS-MAC=58:97:bd:2d:f5:5b;CM-QOS=1.1;CM-VER=3.1; |
2021-02-20, 12:36:37 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:d5:f7:44;CMTS-MAC=58:97:bd:2d:f5:5b;CM-QOS=1.1;CM-VER=3.1; |
2021-02-20, 12:36:20 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=bc:a5:11:d5:f7:44;CMTS-MAC=58:97:bd:2d:f5:5b;CM-QOS=1.1;CM-VER=3.1; |
2021-02-20, 12:29:57 | Warning (5) | MDD message timeout;CM-MAC=bc:a5:11:d5:f7:44;CMTS-MAC=58:97:bd:2d:f5:5b;CM-QOS=1.1;CM-VER=3.1; |
2021-02-20, 12:24:13 | Warning (5) | Dynamic Range Window violation |
2021-02-20, 12:23:59 | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
2021-02-20, 12:23:43 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:a5:11:d5:f7:44;CMTS-MAC=58:97:bd:2d:f5:5b;CM-QOS=1.1;CM-VER=3.1; |
2021-02-20, 12:23:38 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:a5:11:d5:f7:44;CMTS-MAC=58:97:bd:2d:f5:5b;CM-QOS=1.1;CM-VER=3.1; |
2021-02-20, 12:23:37 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:a5:11:d5:f7:44;CMTS-MAC=58:97:bd:2d:f5:5b;CM-QOS=1.1;CM-VER=3.1; |
2021-02-20, 12:23:32 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:a5:11:d5:f7:44;CMTS-MAC=58:97:bd:2d:f5:5b;CM-QOS=1.1;CM-VER=3.1; |
2021-02-20, 12:23:32 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:a5:11:d5:f7:44;CMTS-MAC=58:97:bd:2d:f5:5b;CM-QOS=1.1;CM-VER=3.1; |
2021-02-20, 12:23:24 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:a5:11:d5:f7:44;CMTS-MAC=58:97:bd:2d:f5:5b;CM-QOS=1.1;CM-VER=3.1; |
2021-02-20, 12:23:23 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:a5:11:d5:f7:44;CMTS-MAC=58:97:bd:2d:f5:5b;CM-QOS=1.1;CM-VER=3.1; |
2021-02-20, 12:23:20 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:a5:11:d5:f7:44;CMTS-MAC=58:97:bd:2d:f5:5b;CM-QOS=1.1;CM-VER=3.1; |
2021-02-20, 12:23:16 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:a5:11:d5:f7:44;CMTS-MAC=58:97:bd:2d:f5:5b;CM-QOS=1.1;CM-VER=3.1; |
2021-02-20, 12:23:06 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:a5:11:d5:f7:44;CMTS-MAC=58:97:bd:2d:f5:5b;CM-QOS=1.1;CM-VER=3.1; |
2021-02-20, 12:23:03 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:a5:11:d5:f7:44;CMTS-MAC=58:97:bd:2d:f5:5b;CM-QOS=1.1;CM-VER=3.1; |
2021-02-20, 12:23:02 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:a5:11:d5:f7:44;CMTS-MAC=58:97:bd:2d:f5:5b;CM-QOS=1.1;CM-VER=3.1; |
2021-02-20, 12:23:00 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:a5:11:d5:f7:44;CMTS-MAC=58:97:bd:2d:f5:5b;CM-QOS=1.1;CM-VER=3.1; |
2021-02-20, 12:22:46 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:a5:11:d5:f7:44;CMTS-MAC=58:97:bd:2d:f5:5b;CM-QOS=1.1;CM-VER=3.1; |
2021-02-20, 12:22:44 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:a5:11:d5:f7:44;CMTS-MAC=58:97:bd:2d:f5:5b;CM-QOS=1.1;CM-VER=3.1; |
2021-02-20, 12:22:30 | Warning (5) | MDD message timeout;CM-MAC=bc:a5:11:d5:f7:44;CMTS-MAC=58:97:bd:2d:f5:5b;CM-QOS=1.1;CM-VER=3.1; |
2021-02-20, 12:22:30 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:a5:11:d5:f7:44;CMTS-MAC=58:97:bd:2d:f5:5b;CM-QOS=1.1;CM-VER=3.1; |
|
|
CCAndrew
Gold Problem Solver
•
25.9K Messages
4 years ago
0
0
jmil1
New Poster
•
3 Messages
4 years ago
@CCAndrew
The modem/router is a Netgear C7800 purchased last August. Currently hooked up directly to the line coming from the outdoor box with no splitters. Had 0 network issues for the first 4 months of being in this home, but have been plagued with issues since.
Technician 1 came to the house and inspected the current setup and ruled out the possibility of splitters causing an issue. Confirmed that their were no issues with the router setup, and replaced the line from the box to the house "just in case".
Technician 2 came to the house and did the same inspection as Technician 1 and came to the same conclusion. He replaced the coax cable from the wall to the cable box in the living room claiming that it could be causing signal interference. I will note that we have had 0 issues with T.V. services. He said he checked for errors at the box on the street and found nothing.
Neither commented on the issues I was seeing the in the event logs I posted above.
Updating these tables in the brief moment the network is back:
0
0
CCAndrew
Gold Problem Solver
•
25.9K Messages
4 years ago
0
0
jmil1
New Poster
•
3 Messages
4 years ago
@CC
TV service is indeed X1.
I have not tried a 2nd modem but I am hesitant to believe it is the root of the problem with the above mentioned errors and seeing the solutions to others who have experienced similar issues.
0
0
CCAndrew
Gold Problem Solver
•
25.9K Messages
4 years ago
0
0