Tyler_S
New Contributor II
Joined 5 years ago
User Profile
User Widgets
Contributions
Re: Constant Outages T3 & T4 Errors and Command Power Exceeding 6db.
I thought I would update for anyone having a similar problem... Technician was at our house today, and the underground cable to our house was the old "white" variety instead of the new black kind. Apparently, the white ones get water logged. Also, there was a 9 year old 3-way splitter hooked up to the main line. So, yeah, good times.4Views2likes0CommentsRe: Constant Outages T3 & T4 Errors and Command Power Exceeding 6db.
Not at the moment. The modem used to be connected to a different line, but when we first started having problems I moved it to the main line as part of the troubleshooting process and have left it ther,e since that's also an easier spot for a Technician to access. If there is something going on inside the wall from the original installation or something, I wouldn't know though.4Views0likes0CommentsConstant Outages T3 & T4 Errors and Command Power Exceeding 6db.
Hello, We've been experiencing terrible internet connectivity over the past month or so... Lately the internet is just plain out (or only on for 5 minutes at a time before resetting itself) from around 12pm-5pm and then experiencing a lot of random disconnects throughout the night and morning. We've been dealing with customer support quite a bit and the experience has been maddening at best. After dealing with them every day for a week (and getting nothing more than suggesting that we Power Cycle), I started using the chat help feature instead of the telephone, so that I could quote modem logs to them. This got them to transfer me to a tier 2 technician... Who told me power cycle. -.- After I told him that has been done, he said a technician would need to come to our house, I said that's fine and waited for my appointment. On the day of our appointment, we received an email saying that the Appointment has been canceled, and when I checked my modem logs, I sawthat they sent an online modem reset--something I had already done myself multiple times, and since the internet was working at that moment, proceeded to cancel our tech visit thinking job well done. It's been five days since then, and the problems consist... T3 errors all day long, our downstream channel power is constantly way out of normal range (sometimes varying by up to 7 dBmV!), and the uncorrectables continue to outweigh the corrected on most of the channels. Here's a chunk of the recent modem log for reference: 6-18-2019, 19:35:38 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:da:f9:16:89:81;CMTS-MAC=00:42:5a:9f:00:ed;CM-QOS=1.1;CM-VER=3.1;" 6-18-2019, 19:35:31 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=b0:da:f9:16:89:81;CMTS-MAC=00:42:5a:9f:00:ed;CM-QOS=1.1;CM-VER=3.1;" 6-18-2019, 19:35:26 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:da:f9:16:89:81;CMTS-MAC=00:42:5a:9f:00:ed;CM-QOS=1.1;CM-VER=3.1;" 6-18-2019, 19:33:38 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:16:89:81;CMTS-MAC=00:42:5a:9f:00:ed;CM-QOS=1.1;CM-VER=3.1;" 6-18-2019, 19:33:18 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:16:89:81;CMTS-MAC=00:42:5a:9f:00:ed;CM-QOS=1.1;CM-VER=3.1;" 6-18-2019, 19:33:16 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:16:89:81;CMTS-MAC=00:42:5a:9f:00:ed;CM-QOS=1.1;CM-VER=3.1;" 6-18-2019, 19:33:15 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:16:89:81;CMTS-MAC=00:42:5a:9f:00:ed;CM-QOS=1.1;CM-VER=3.1;" 6-18-2019, 19:33:14 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:16:89:81;CMTS-MAC=00:42:5a:9f:00:ed;CM-QOS=1.1;CM-VER=3.1;" 1-1-1970, 0:0:32 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=b0:da:f9:16:89:81;CMTS-MAC=00:42:5a:9f:00:ed;CM-QOS=1.1;CM-VER=3.1;" 1-1-1970, 0:0:18 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:da:f9:16:89:81;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" 6-18-2019, 19:23:7 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:da:f9:16:89:81;CMTS-MAC=00:42:5a:9f:00:ed;CM-QOS=1.1;CM-VER=3.1;" 6-18-2019, 19:22:37 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:16:89:81;CMTS-MAC=00:42:5a:9f:00:ed;CM-QOS=1.1;CM-VER=3.1;" 6-18-2019, 19:22:26 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:16:89:81;CMTS-MAC=00:42:5a:9f:00:ed;CM-QOS=1.1;CM-VER=3.1;" 6-18-2019, 19:22:25 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:16:89:81;CMTS-MAC=00:42:5a:9f:00:ed;CM-QOS=1.1;CM-VER=3.1;" 6-18-2019, 16:3:36 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:16:89:81;CMTS-MAC=00:42:5a:9f:00:ed;CM-QOS=1.1;CM-VER=3.1;" 6-18-2019, 16:3:29 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=b0:da:f9:16:89:81;CMTS-MAC=00:42:5a:9f:00:ed;CM-QOS=1.1;CM-VER=3.1;" 1-1-1970, 1:26:44 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=b0:da:f9:16:89:81;CMTS-MAC=00:42:5a:9f:00:ed;CM-QOS=1.1;CM-VER=3.1;" 1-1-1970, 1:26:36 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:da:f9:16:89:81;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" 1-1-1970, 1:25:31 Critical(3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:da:f9:16:89:81;CMTS-MAC=00:42:5a:9f:00:ed;CM-QOS=1.1;CM-VER=3.1;" 1-1-1970, 1:25:13 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=b0:da:f9:16:89:81;CMTS-MAC=00:42:5a:9f:00:ed;CM-QOS=1.1;CM-VER=3.1;" 1-1-1970, 1:24:46 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:da:f9:16:89:81;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" 1-1-1970, 1:24:42 Critical(3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:da:f9:16:89:81;CMTS-MAC=00:42:5a:9f:00:ed;CM-QOS=1.1;CM-VER=3.1;" 1-1-1970, 1:24:21 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=b0:da:f9:16:89:81;CMTS-MAC=0Solved2.4KViews0likes3Comments