New Contributor
•
12 Messages
Packet Loss and Latency Spikes
This is not the first time this is happened (it happens periodically), but I am having issues with packet loss and disconnects between my modem and the ISP (hop 2). They are intermittent and very annoying. I pay $75 a month for fast internet, and I am the only person who uses it, yet I have constant problems. I had these issues with the old Cox-issed Cisco modem and my current Surfboard SB6183. Same issues with three different routers as well (Apple AirPort Extreme, Netgear Nighthawk X6, Linksys WRT1900AC). It has to be on Cox's end, but I get zero help when I call in and talk to support. They always ask me stupid questions (have you reset the modem, have you checked your router, have you tried connecting directly to the modem via ethernet, etc.) and say everything looks fine on their end. I had a tech out last month and he pulled a filter/splitter off and replaced it and said things were fixed. I was at work when he came and my housemate said that he was here for about 10 minutes. Below is a screenshot of Pingplotter, the status page of my modem, and the event log of my modem.
http://i.imgur.com/1Gnp1a5.png
| Startup Procedure | ||
|---|---|---|
| Procedure | Status | Comment |
| Acquire Downstream Channel | Locked | |
| Connectivity State | OK | Operational |
| Boot State | OK | Operational |
| Configuration File | OK | |
| Security | Enabled | BPI+ |
| DOCSIS Network Access Enabled | Allowed | |
| Downstream Bonded Channels | ||||||||
|---|---|---|---|---|---|---|---|---|
| Channel | Lock Status | Modulation | Channel ID | Frequency | Power | SNR | Corrected | Uncorrectables |
| 1 | Locked | QAM256 | 73 | 813000000 Hz | 8.7 dBmV | 40.2 dB | 9 | 65 |
| 2 | Locked | QAM256 | 74 | 819000000 Hz | 9.1 dBmV | 40.3 dB | 23 | 48 |
| 3 | Locked | QAM256 | 75 | 825000000 Hz | 8.9 dBmV | 40.3 dB | 17 | 56 |
| 4 | Locked | QAM256 | 76 | 831000000 Hz | 9.1 dBmV | 40.2 dB | 43 | 133 |
| 5 | Locked | QAM256 | 77 | 837000000 Hz | 9.4 dBmV | 40.3 dB | 15 | 84 |
| 6 | Locked | QAM256 | 78 | 843000000 Hz | 9.8 dBmV | 40.1 dB | 11 | 67 |
| 7 | Locked | QAM256 | 79 | 849000000 Hz | 9.7 dBmV | 40.5 dB | 13 | 60 |
| 8 | Locked | QAM256 | 80 | 855000000 Hz | 9.6 dBmV | 40.3 dB | 18 | 69 |
| 9 | Locked | QAM256 | 89 | 909000000 Hz | 8.8 dBmV | 40.3 dB | 15 | 55 |
| 10 | Locked | QAM256 | 90 | 915000000 Hz | 8.7 dBmV | 40.3 dB | 38 | 61 |
| 11 | Locked | QAM256 | 91 | 921000000 Hz | 8.7 dBmV | 40.3 dB | 24 | 98 |
| 12 | Locked | QAM256 | 92 | 927000000 Hz | 9.2 dBmV | 40.5 dB | 38 | 31 |
| 13 | Locked | QAM256 | 93 | 933000000 Hz | 8.8 dBmV | 40.3 dB | 22 | 81 |
| 14 | Locked | QAM256 | 94 | 939000000 Hz | 8.2 dBmV | 40.1 dB | 49 | 107 |
| 15 | Locked | QAM256 | 95 | 945000000 Hz | 7.7 dBmV | 39.9 dB | 18 | 57 |
| 16 | Locked | QAM256 | 96 | 951000000 Hz | 8.2 dBmV | 40.0 dB | 12 | 69 |
| Upstream Bonded Channels | ||||||
|---|---|---|---|---|---|---|
| Channel | Lock Status | US Channel Type | Channel ID | Symbol Rate | Frequency | Power |
| 1 | Locked | ATDMA | 4 | 5120 Ksym/sec | 37300000 Hz | 36.9 dBmV |
| 2 | Locked | ATDMA | 1 | 2560 Ksym/sec | 19400000 Hz | 34.8 dBmV |
| 3 | Locked | ATDMA | 2 | 5120 Ksym/sec | 24300000 Hz | 35.3 dBmV |
| 4 | Locked | ATDMA | 3 | 5120 Ksym/sec | 30800000 Hz | 36.0 dBmV |
Current System Time: Mon Jan 02 20:18:17 2017
| Time | Priority | Description |
|---|---|---|
| Mon Jan 02 20:02:24 2017 | Warning (5) | Dynamic Range Window violation |
| Mon Jan 02 19:45:13 2017 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Mon Jan 02 19:44:45 2017 | Warning (5) | Dynamic Range Window violation |
| Mon Jan 02 19:44:44 2017 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Mon Jan 02 19:43:15 2017 | Warning (5) | Dynamic Range Window violation |
| Mon Jan 02 19:40:31 2017 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Mon Jan 02 19:39:48 2017 | Notice (6) | TLV-11 - unrecognized OID;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Time Not Established | Warning (5) | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.0;CM-VER=3.0; |
| Time Not Established | Notice (6) | Honoring MDD; IP provisioning mode = IPv4 |
| Time Not Established | Critical (3) | No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.0;CM-VER=3.0; |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
| Mon Jan 02 19:38:47 2017 | Critical (3) | Resetting the cable modem due to docsDevResetNow |
| Mon Jan 02 19:14:32 2017 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Mon Jan 02 14:49:12 2017 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
| Sun Jan 01 12:18:24 2017 | Critical (3) | Resetting the cable modem due to docsDevResetNow |
| Sun Jan 01 12:06:25 2017 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Sun Jan 01 10:18:08 2017 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Sun Jan 01 10:18:04 2017 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Sun Jan 01 07:45:18 2017 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Sun Jan 01 04:12:00 2017 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Sun Jan 01 02:49:36 2017 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Sun Jan 01 02:49:26 2017 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Sun Jan 01 01:04:25 2017 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Sun Jan 01 00:34:59 2017 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Sat Dec 31 22:08:29 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Sat Dec 31 21:16:38 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Sat Dec 31 21:16:10 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Sat Dec 31 19:37:00 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Sat Dec 31 19:36:57 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Sat Dec 31 19:36:44 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Sat Dec 31 19:29:30 2016 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Sat Dec 31 19:21:46 2016 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Sat Dec 31 19:04:05 2016 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Sat Dec 31 18:26:28 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Sat Dec 31 17:06:43 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Sat Dec 31 14:38:58 2016 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Sat Dec 31 10:22:19 2016 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Sat Dec 31 10:20:20 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Sat Dec 31 09:14:17 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Fri Dec 30 20:11:54 2016 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Fri Dec 30 19:32:03 2016 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Fri Dec 30 19:31:47 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Fri Dec 30 14:19:22 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Fri Dec 30 12:53:38 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Fri Dec 30 12:32:27 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Fri Dec 30 12:06:47 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Fri Dec 30 11:44:52 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Fri Dec 30 11:16:42 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Fri Dec 30 09:43:45 2016 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Fri Dec 30 08:47:55 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Thu Dec 29 23:01:39 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Thu Dec 29 17:40:27 2016 | Critical (3) | 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Thu Dec 29 17:40:27 2016 | Critical (3) | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Thu Dec 29 17:40:27 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Thu Dec 29 17:37:28 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Thu Dec 29 15:10:05 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Thu Dec 29 15:09:58 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Thu Dec 29 13:05:10 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Thu Dec 29 13:04:38 2016 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Thu Dec 29 12:16:33 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Thu Dec 29 10:44:07 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Thu Dec 29 04:02:33 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Thu Dec 29 02:35:07 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Thu Dec 29 02:34:58 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Thu Dec 29 02:34:46 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Thu Dec 29 01:28:56 2016 | Critical (3) | 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Thu Dec 29 01:28:56 2016 | Critical (3) | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Thu Dec 29 01:28:56 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Wed Dec 28 20:58:38 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Wed Dec 28 14:04:29 2016 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Wed Dec 28 12:26:04 2016 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Wed Dec 28 12:25:50 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Wed Dec 28 10:26:12 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Wed Dec 28 10:24:58 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Wed Dec 28 10:23:40 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Wed Dec 28 10:23:38 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Wed Dec 28 10:23:36 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Wed Dec 28 10:18:33 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Tue Dec 27 18:29:10 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Tue Dec 27 18:27:38 2016 | Critical (3) | Resetting the cable modem due to docsDevResetNow |
| Tue Dec 27 14:13:19 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Tue Dec 27 14:06:05 2016 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Tue Dec 27 13:57:24 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Tue Dec 27 12:15:27 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Tue Dec 27 11:34:07 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Tue Dec 27 09:26:31 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Mon Dec 26 17:42:40 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Mon Dec 26 04:52:59 2016 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Mon Dec 26 04:52:45 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Sun Dec 25 14:20:37 2016 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Sun Dec 25 13:40:15 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Sun Dec 25 09:58:00 2016 | Critical (3) | 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Sun Dec 25 09:58:00 2016 | Critical (3) | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Sun Dec 25 09:58:00 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Sun Dec 25 09:39:19 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Sun Dec 25 04:37:19 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Sun Dec 25 00:05:00 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Sat Dec 24 14:36:22 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
| Sat Dec 24 09:44:20 2016 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; |
Related Content
Closed
4
0
Closed
2
0
Closed
10
0
Closed
2
0
Closed
1
0
WayneMadeley
New Contributor
•
4 Messages
0
0
Becky
Moderator
•
4.3K Messages
0
0
mkb914
New Contributor
•
2 Messages
Hi Becky,
Service tech came today and checked everything out with no reported problems. They replaced the modem and recommended replacing the wireless router (originally provided by Cox a year ago).
After they left, I was still having issues so I tried direct linking my computer to the modem. I have run for about an hour now with zero latency spikes...
New router is ordered and on the way!
0
0
Becky
Moderator
•
4.3K Messages
I'm glad you were able to pinpoint the source of the problem. Thanks for posting an update! I'm sure the new router will make a big difference.
0
0
AZMIT
New Contributor
•
3 Messages
I had a similar issue.
Started Unicast Maintenance Ranging - No Response received - T3 time-out: I was getting this same message on my cable modem. After hours of complaints and a few phone calls and chat sessions, Cox finally put out a outage notification. It was a problem on their end...not the modem or the router. I almost went out and bought a modem when they finally admitted to the problem. That was yesterday. Now today...about 30 minutes ago...I lost connectivity again.
No worries...getting a secondary ISP to see if they are better. This is not the first time I have had problems, but certainly I have decided not to wait for them to fix the problems because it seems like they don't even know what to do.
0
0
Tecknowhelp
Valued Contributor II
•
2.8K Messages
T3 errors are usually caused by a problem with the upstream signal(US) to noise ratio (SNR). This can be caused by local wiring issues, issues on the lines on the poles, or a issue at the plant where the signal starts. So it can be a sign of a outage, but not everyone getting T3's are in a outage. You may be having the same symptoms as OP, but unless they are also in AZ, it is probably not directly related.
0
0
thehollowaytape
New Contributor
•
12 Messages
@Becky @ChrisL
The issues have not been rectified. I thought it might be my Arris SB6183, so I bought a TP-Link TC-7620 and I'm having the same issues: more T3 time-outs. The "technician" that came out on Sunday (subcontractor, not in a Cox truck) had no idea what a time-out even was. He said "my modem shows critical so it's probably a problem with the modem." Well, this is the third modem that I've had these issues with since last September when I bought the Arris, one being a Cox-issued Cisco.
What do I need to do to get this resolved? Everything I read about T3 time-outs is pointing to an issue with signal noise on one or more of the upstream channels. It seems the modems are having issues talking back to the CMTS, and ramp up the upstream power levels trying to compensate (akin to talking louder into a phone) until the power level gets so high that the modem drops packets due to power levels being out of range (too high). The cause seems to be an issue with wiring somewhere outside of my house. It could even be one of my neighbors that has old wiring or a bad splitter or something causing issues for everyone in the neighborhood. Some of the houses in my neighborhood are from the 60s. Once again, the worst part about these issues is that they are intermittent and sometimes happen for hours on end and sometimes can go 6 or 8 hours with no issue. Either way, the time-outs are not normal and something is causing noise in the return path to the CMTS that my modems have not been able to overcome.
0
0
DerrickW
Valued Contributor
•
1.2K Messages
0
0