DeXLV702
7 years agoNew Contributor
Getting T3 Timeouts...AGAIN.
Time | Priority | Description |
Wed Apr 12 17:37:24 2017 | Warning (5) | Dynamic Range Window violation |
Wed Apr 12 17:36:09 2017 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:5d:0a:28;CMTS-MAC=50:57:a8:89:27:c9;CM-QOS=1.1;CM-VER=3.0; |
Wed Apr 12 17:30:10 2017 | Notice (6) | WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE |
Wed Apr 12 17:29:41 2017 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:5d:0a:28;CMTS-MAC=50:57:a8:89:27:c9;CM-QOS=1.1;CM-VER=3.0; |
Wed Apr 12 17:24:42 2017 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:5d:0a:28;CMTS-MAC=50:57:a8:89:27:c9;CM-QOS=1.1;CM-VER=3.0; |
Wed Apr 12 17:24:42 2017 | Critical (3) | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=6c:b0:ce:5d:0a:28;CMTS-MAC=50:57:a8:89:27:c9;CM-QOS=1.1;CM-VER=3.0; |
Wed Apr 12 17:24:42 2017 | Critical (3) | 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=6c:b0:ce:5d:0a:28;CMTS-MAC=50:57:a8:89:27:c9;CM-QOS=1.1;CM-VER=3.0; |
Wed Apr 12 17:24:12 2017 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:5d:0a:28;CMTS-MAC=50:57:a8:89:27:c9;CM-QOS=1.1;CM-VER=3.0; |
Wed Apr 12 17:24:12 2017 | Critical (3) | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=6c:b0:ce:5d:0a:28;CMTS-MAC=50:57:a8:89:27:c9;CM-QOS=1.1;CM-VER=3.0; |
Wed Apr 12 17:24:12 2017 | Critical (3) | 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=6c:b0:ce:5d:0a:28;CMTS-MAC=50:57:a8:89:27:c9;CM-QOS=1.1;CM-VER=3.0; |
Wed Apr 12 16:45:37 2017 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:b0:ce:5d:0a:28;CMTS-MAC=50:57:a8:89:27:c9;CM-QOS=1.1;CM-VER=3.0; |
Wed Apr 12 16:44:54 2017 | Notice (6) | TLV-11 - unrecognized OID;CM-MAC=6c:b0:ce:5d:0a:28;CMTS-MAC=50:57:a8:89:27:c9;CM-QOS=1.1;CM-VER=3.0; |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
This has been happening on and off for the past few days. A few months ago it was happening a lot more frequently and a technician came and removed a filter from the power line that he said someone had left there previously and was messing with the upstream signals. Mind you we only have internet, no phone or TV. It seemed to fix the issue but it is now starting to happen again.
I have triple checked all my connections everything is secured tightly. I do not have any splitters. Power cord is going straight into a wall outlet. I have restarted my computer. I have reset and hard reset my modem. Still happening. Please, this is a huge inconvenience as we use streaming services a lot and work from home.