Router: Asus RT-N66U (latest firmware)
Modem: TP-LINK TC-7620 (DOCSIS 3.0)
VoIP: ARRIS TM822G
ISP/Connection Type: Suddenlink Cable (400mbps dwn / 30mbps up).
Devices Connected: We have 20 items in total connected to our router. 15 on the 2.4GHz . 3 on 5GHz. And 2 that are wired. I've attempted to plug directly into the router with the same issue. 5 computers are connected to our router. (1 work, 3 personal). Other devices are ipad / iphone / android / roku / nvidia sheid / smart plugs & lights
Last week, after tornadic weather activity in our area, our internet was down for two days. In talking with Suddenlink's technical support, they had me power-cycle all of my network devices, direct connect a laptop via cat5 ethernet to the TP-LINK modem to run speed tests (0mbps), and finally reset the TP-LINK modem, after which it would no longer obtain internet.
Suddenlink dispatched a technician and then called staying they were seeing a signal issue throughout our area, that they would be able to resolove the issue from outside our home. The internet did come back up eventually that afternoon. Speed tests showed normal.
The following day, web browsing (egde, chrome, firefox) were all extremely slow. Speed tests did not reflect slowness on download, but upload was .01mbps. Resetting devices did not result in and increased performance. I have no hubs / switches. Plugging directly into the modem and running a ping -t 8.8.8.8 - packet were dropping.
I contacted Suddenlink & they tried to sell me their rentable modem to resolve the issue. I asked for a technician. The tech came yesterday said our signal was great into the house and stable at ~400mbps. He said that if it were too high or too low, it could cause the packet loss issues. He said he's been seeing other DOCSIS 3.0 modems having this issue after the weather outage. He said because of the newer faster internet speeds with new channels that my 3.0 router doesn't support - it's causing the issue and that I would need to buy a 3.1 DOCSYS modem to resolve the issue.
TP LINK support said to buy a new modem.
Looking at the Error log on our Router I'm seeing a lot of errors. Posted the log below.
Downstream Bonded Channels
Upstream Bonded Channels
Modem: TP-LINK TC-7620 (DOCSIS 3.0)
VoIP: ARRIS TM822G
ISP/Connection Type: Suddenlink Cable (400mbps dwn / 30mbps up).
Devices Connected: We have 20 items in total connected to our router. 15 on the 2.4GHz . 3 on 5GHz. And 2 that are wired. I've attempted to plug directly into the router with the same issue. 5 computers are connected to our router. (1 work, 3 personal). Other devices are ipad / iphone / android / roku / nvidia sheid / smart plugs & lights
Last week, after tornadic weather activity in our area, our internet was down for two days. In talking with Suddenlink's technical support, they had me power-cycle all of my network devices, direct connect a laptop via cat5 ethernet to the TP-LINK modem to run speed tests (0mbps), and finally reset the TP-LINK modem, after which it would no longer obtain internet.
Suddenlink dispatched a technician and then called staying they were seeing a signal issue throughout our area, that they would be able to resolove the issue from outside our home. The internet did come back up eventually that afternoon. Speed tests showed normal.
The following day, web browsing (egde, chrome, firefox) were all extremely slow. Speed tests did not reflect slowness on download, but upload was .01mbps. Resetting devices did not result in and increased performance. I have no hubs / switches. Plugging directly into the modem and running a ping -t 8.8.8.8 - packet were dropping.
I contacted Suddenlink & they tried to sell me their rentable modem to resolve the issue. I asked for a technician. The tech came yesterday said our signal was great into the house and stable at ~400mbps. He said that if it were too high or too low, it could cause the packet loss issues. He said he's been seeing other DOCSIS 3.0 modems having this issue after the weather outage. He said because of the newer faster internet speeds with new channels that my 3.0 router doesn't support - it's causing the issue and that I would need to buy a 3.1 DOCSYS modem to resolve the issue.
TP LINK support said to buy a new modem.
Looking at the Error log on our Router I'm seeing a lot of errors. Posted the log below.
Time | Priority | Description |
---|---|---|
Wed Mar 30 19:40:38 2022 | Warning (5) | MDD message timeout;CM-MAC=98🇩🇪d0:86:74:b8;CMTS-MAC=00:01:5c:b8:80:79;CM-QOS=1.1;CM-VER=3.0; |
Wed Mar 30 14:57:22 2022 | Notice (6) | TLV-11 - unrecognized OID;CM-MAC=98🇩🇪d0:86:74:b8;CMTS-MAC=00:01:5c:b8:80:79;CM-QOS=1.1;CM-VER=3.0; |
Wed Mar 30 14:57:21 2022 | Error (4) | Primary address failed, secondary active;CM-MAC=98🇩🇪d0:86:74:b8;CMTS-MAC=00:01:5c:b8:80:79;CM-QOS=1.1;CM-VER=3.0; |
Wed Mar 30 14:57:21 2022 | Warning (5) | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=98🇩🇪d0:86:74:b8;CMTS-MAC=00:01:5c:b8:80:79;CM-QOS=1.1;CM-VER=... |
Wed Mar 30 14:58:37 2022 | Critical (3) | DHCP failed - RS sent, no RA received;CM-MAC=98🇩🇪d0:86:74:b8;CMTS-MAC=00:01:5c:b8:80:79;CM-QOS=1.0;CM-VER=3.0; |
Wed Mar 30 14:58:20 2022 | Notice (6) | Honoring MDD; IP provisioning mode = APM |
Wed Mar 30 14:58:10 2022 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=98🇩🇪d0:86:74:b8;CMTS-MAC=00:00:00:00:00:00;CM-QO... |
Wed Mar 30 14:58:10 2022 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=98🇩🇪d0:86:74:b8;CMTS-MAC=00:00:00:00... |
Wed Mar 30 14:55:40 2022 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=98🇩🇪d0:86:74:b8;CMTS-MAC=00:00:00:00:00:00;CM-QO... |
Wed Mar 30 14:55:39 2022 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=98... |
Wed Mar 30 14:55:39 2022 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=98🇩🇪d0:86:74:b8;CMTS-MAC=00:01:5c:b8... |
Wed Mar 30 14:55:15 2022 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=98... |
Wed Mar 30 14:55:15 2022 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=98🇩🇪d0:86:74:b8;CMTS-MAC=00:01:5c:b8... |
Wed Mar 30 14:54:46 2022 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=98... |
Wed Mar 30 14:54:46 2022 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=98🇩🇪d0:86:74:b8;CMTS-MAC=00:01:5c:b8... |
Wed Mar 30 14:54:44 2022 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=98... |
Wed Mar 30 14:54:44 2022 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=98🇩🇪d0:86:74:b8;CMTS-MAC=00:01:5c:b8... |
Wed Mar 30 14:52:13 2022 | Warning (5) | MDD message timeout;CM-MAC=98🇩🇪d0:86:74:b8;CMTS-MAC=00:01:5c:b8:80:79;CM-QOS=1.1;CM-VER=3.0; |
Wed Mar 30 14:52:13 2022 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=98🇩🇪d0:86:74:b8;CMTS-MAC=00:01:5c:b8... |
Wed Mar 30 14:52:06 2022 | Warning (5) | MDD message timeout;CM-MAC=98🇩🇪d0:86:74:b8;CMTS-MAC=00:01:5c:b8:80:79;CM-QOS=1.1;CM-VER=3.0; |
Wed Mar 30 14:52:06 2022 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=98🇩🇪d0:86:74:b8;CMTS-MAC=00:01:5c:b8... |
Tue Mar 29 10:23:03 2022 | Error (4) | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=98🇩🇪d0:86:74:b8;CMTS-MAC=00:01:5c:b8:80:79;CM-QOS=1.1;CM-VE... |
Sun Mar 27 22:26:00 2022 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=98🇩🇪d0:86:74:b8;CMTS-MAC=00:01:5c:b8:80:79;... |
Sun Mar 27 22:25:53 2022 | Warning (5) | MDD message timeout;CM-MAC=98🇩🇪d0:86:74:b8;CMTS-MAC=00:01:5c:b8:80:79;CM-QOS=1.1;CM-VER=3.0; |
Sun Mar 27 22:25:36 2022 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=98🇩🇪d0:86:74:b8;CMTS-MAC=00:01:5c:b8:80:79;... |
Sun Mar 27 22:25:32 2022 | Warning (5) | MDD message timeout;CM-MAC=98🇩🇪d0:86:74:b8;CMTS-MAC=00:01:5c:b8:80:79;CM-QOS=1.1;CM-VER=3.0; |
Sat Mar 26 12:14:26 2022 | Error (4) | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=98🇩🇪d0:86:74:b8;CMTS-MAC=00:01:5c:b8:80:79;CM-QOS=1.1;CM-VE... |
Wed Mar 23 16:29:19 2022 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=98🇩🇪d0:86:74:b8;CMTS-MAC=00:01:5c:b8:80:79;CM-QO... |
Wed Mar 23 16:29:17 2022 | Warning (5) | MDD message timeout;CM-MAC=98🇩🇪d0:86:74:b8;CMTS-MAC=00:01:5c:b8:80:79;CM-QOS=1.1;CM-VER=3.0; |
Wed Mar 23 16:29:17 2022 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=98🇩🇪d0:86:74:b8;CMTS-MAC=00:01:5c:b8:80:79;CM-QO... |
Wed Mar 23 16:28:42 2022 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=98🇩🇪d0:86:74:b8;CMTS-MAC=00:01:5c:b8... |
Wed Mar 23 16:28:40 2022 | Warning (5) | MDD message timeout;CM-MAC=98🇩🇪d0:86:74:b8;CMTS-MAC=00:01:5c:b8:80:79;CM-QOS=1.1;CM-VER=3.0; |
Procedure | Status | Comment |
---|---|---|
Acquire Downstream Channel | 567000000 Hz | Locked |
Connectivity State | OK | Operational |
Boot State | OK | Operational |
Configuration File | OK | ^1/77FB7FF4/TYPE=RES/COS=194/IP=2 |
Security | Enabled | BPI+ |
Channel | Status | Modulation | Channel ID | Frequency | Power | SNR |
---|---|---|---|---|---|---|
1 | Locked | QAM256 | 2 | 567000000 Hz | -1.8 dBmV | 39.5 dB |
2 | Locked | QAM256 | 1 | 561000000 Hz | -2.4 dBmV | 39.3 dB |
3 | Locked | QAM256 | 3 | 573000000 Hz | -1.6 dBmV | 39.5 dB |
4 | Locked | QAM256 | 5 | 585000000 Hz | -0.9 dBmV | 39.2 dB |
5 | Locked | QAM256 | 6 | 591000000 Hz | -0.5 dBmV | 39.5 dB |
6 | Locked | QAM256 | 7 | 597000000 Hz | -0.2 dBmV | 39.6 dB |
7 | Locked | QAM256 | 8 | 603000000 Hz | 0.0 dBmV | 39.6 dB |
8 | Locked | QAM256 | 9 | 609000000 Hz | 0.3 dBmV | 39.7 dB |
9 | Locked | QAM256 | 17 | 657000000 Hz | 0.6 dBmV | 39.4 dB |
10 | Locked | QAM256 | 18 | 663000000 Hz | 0.6 dBmV | 39.4 dB |
11 | Locked | QAM256 | 20 | 675000000 Hz | 0.7 dBmV | 39.2 dB |
12 | Locked | QAM256 | 21 | 681000000 Hz | 0.6 dBmV | 39.3 dB |
13 | Locked | QAM256 | 22 | 687000000 Hz | 0.8 dBmV | 39.4 dB |
14 | Locked | QAM256 | 23 | 693000000 Hz | 0.6 dBmV | 39.4 dB |
15 | Locked | QAM256 | 24 | 699000000 Hz | 0.5 dBmV | 39.3 dB |
16 | Locked | QAM256 | 25 | 705000000 Hz | 0.5 dBmV | 39.3 dB |
Channel | Status | Channel Type | Channel ID | Symbol Rate | Frequency | Power |
---|---|---|---|---|---|---|
1 | Locked | ATDMA | 13 | 5120 ksym/sec | 37800000 Hz | 48.0 dBmV |
2 | Locked | ATDMA | 16 | 5120 ksym/sec | 17400000 Hz | 47.0 dBmV |
3 | Locked | ATDMA | 15 | 5120 ksym/sec | 24200000 Hz | 47.3 dBmV |
4 | Locked | ATDMA | 14 | 5120 ksym/sec | 31000000 Hz | 47.5 dBmV |
Last edited: