New Member
•
1 Message
Connection drops and t3 errors
Time Priority Description Thu Apr 05 14:42:34 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:48:db:40;CMTS-MAC=28:52:61:f1:74:ed;CM-QOS=1.1;CM-VER=3.0; Thu Apr 05 14:42:36 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=00:40:36:48:db:40;CMTS-MAC=28:52:61:f1:74:ed;CM-QOS=1.1;CM-VER=3.0; Thu Apr 05 14:42:39 2018 Warning (5) MDD message timeout;CM-MAC=00:40:36:48:db:40;CMTS-MAC=28:52:61:f1:74:ed;CM-QOS=1.1;CM-VER=3.0; Thu Apr 05 14:42:46 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:48:db:40;CMTS-MAC=28:52:61:f1:74:ed;CM-QOS=1.1;CM-VER=3.0; Thu Apr 05 14:42:47 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=00:40:36:48:db:40;CMTS-MAC=28:52:61:f1:74:ed;CM-QOS=1.1;CM-VER=3.0; Thu Apr 05 14:42:50 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:48:db:40;CMTS-MAC=28:52:61:f1:74:ed;CM-QOS=1.1;CM-VER=3.0; Thu Apr 05 14:42:50 2018 Warning (5) MDD message timeout;CM-MAC=00:40:36:48:db:40;CMTS-MAC=28:52:61:f1:74:ed;CM-QOS=1.1;CM-VER=3.0; Thu Apr 05 14:42:51 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=00:40:36:48:db:40;CMTS-MAC=28:52:61:f1:74:ed;CM-QOS=1.1;CM-VER=3.0; Thu Apr 05 14:43:01 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:48:db:40;CMTS-MAC=28:52:61:f1:74:ed;CM-QOS=1.1;CM-VER=3.0; Thu Apr 05 14:43:01 2018 Warning (5) MDD message timeout;CM-MAC=00:40:36:48:db:40;CMTS-MAC=28:52:61:f1:74:ed;CM-QOS=1.1;CM-VER=3.0; Thu Apr 05 14:43:13 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:48:db:40;CMTS-MAC=28:52:61:f1:74:ed;CM-QOS=1.1;CM-VER=3.0; Thu Apr 05 14:43:16 2018 Warning (5) MDD message timeout;CM-MAC=00:40:36:48:db:40;CMTS-MAC=28:52:61:f1:74:ed;CM-QOS=1.1;CM-VER=3.0; Thu Apr 05 14:43:41 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:48:db:40;CMTS-MAC=28:52:61:f1:74:ed;CM-QOS=1.1;CM-VER=3.0; Thu Apr 05 14:43:41 2018 Warning (5) MDD message timeout;CM-MAC=00:40:36:48:db:40;CMTS-MAC=28:52:61:f1:74:ed;CM-QOS=1.1;CM-VER=3.0; Fri Apr 06 00:52:18 2018 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:48:db:40;CMTS-MAC=28:52:61:f1:74:ed;CM-QOS=1.1;CM-VER=3.0; Fri Apr 06 00:52:30 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:48:db:40;CMTS-MAC=28:52:61:f1:74:ed;CM-QOS=1.1;CM-VER=3.0; Fri Apr 06 00:52:38 2018 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:48:db:40;CMTS-MAC=28:52:61:f1:74:ed;CM-QOS=1.1;CM-VER=3.0; Fri Apr 06 00:53:10 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:48:db:40;CMTS-MAC=28:52:61:f1:74:ed;CM-QOS=1.1;CM-VER=3.0; Fri Apr 06 00:53:38 2018 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:48:db:40;CMTS-MAC=28:52:61:f1:74:ed;CM-QOS=1.1;CM-VER=3.0; Fri Apr 06 00:53:50 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:48:db:40;CMTS-MAC=28:52:61:f1:74:ed;CM-QOS=1.1;CM-VER=3.0; Fri Apr 06 00:53:58 2018 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:48:db:40;CMTS-MAC=28:52:61:f1:74:ed;CM-QOS=1.1;CM-VER=3.0; Fri Apr 06 00:54:30 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:48:db:40;CMTS-MAC=28:52:61:f1:74:ed;CM-QOS=1.1;CM-VER=3.0; Fri Apr 06 00:54:57 2018 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:48:db:40;CMTS-MAC=28:52:61:f1:74:ed;CM-QOS=1.1;CM-VER=3.0; Fri Apr 06 00:55:10 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:48:db:40;CMTS-MAC=28:52:61:f1:74:ed;CM-QOS=1.1;CM-VER=3.0; Fri Apr 06 00:55:17 2018 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:48:db:40;CMTS-MAC=28:52:61:f1:74:ed;CM-QOS=1.1;CM-VER=3.0; Fri Apr 06 00:55:50 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:48:db:40;CMTS-MAC=28:52:61:f1:74:ed;CM-QOS=1.1;CM-VER=3.0; Fri Apr 06 00:56:17 2018 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:48:db:40;CMTS-MAC=28:52:61:f1:74:ed;CM-QOS=1.1;CM-VER=3.0; Fri Apr 06 00:56:30 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:48:db:40;CMTS-MAC=28:52:61:f1:74:ed;CM-QOS=1.1;CM-VER=3.0; Fri Apr 06 00:56:37 2018 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:48:db:40;CMTS-MAC=28:52:61:f1:74:ed;CM-QOS=1.1;CM-VER=3.0; Fri Apr 06 00:57:10 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:48:db:40;CMTS-MAC=28:52:61:f1:74:ed;CM-QOS=1.1;CM-VER=3.0; Fri Apr 06 00:57:28 2018 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:48:db:40;CMTS-MAC=28:52:61:f1:74:ed;CM-QOS=1.1;CM-VER=3.0;
I have been getting 1~3 connection drops recently throughout the day. I haven't had this problem before and I have tried everything I could think of from changing settings, checking wiring and reseting/factory restoring the router. The router is a MG7540 and its about 4 months old. I have uploaded a recent log of t3 errors.
user_Phil
Advocate
•
1.1K Messages
7 years ago
Hi Aes and welcome to the business forums.
I can certainly review your services and check for any issues. Please private message me your first and last name, the name of your business, the full address, and the phone number associated with your account.
0
0
losvigils
Visitor
•
2 Messages
6 years ago
I am getting the same type of issues and errors in modem sys log, any possiblity of you helping me out too?
0
0
CC_Gina
Gold Problem solver
•
421 Messages
6 years ago
Hi losvigils! I just responded to your other forum post with some ideas to start out with and instructions on how to send a private message if those ideas don't work 🙂
0
0