Earlier today we had another full area outage (tv & internet). Service was supposedly restored a few hours later, but as always happens when an outage occurs over the weekend, internet service was not fully restored. We are bonded to all 16 down and 3 up channels, all signals in range on power and snr, however there is a constant flow of errors in the log and literally millions of uncorrectable errors across all the channels. The below is just in the last few hours:
2018-6-17, 17:44:15 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:79:36:40;CMTS-MAC=00:17:10:92:9a:a4;CM-QOS=1.1;CM-VER=3.0;
2018-6-17, 17:44:20 Warning (5) Dynamic Range Window violation
2018-6-17, 17:45:00 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:79:36:40;CMTS-MAC=00:17:10:92:9a:a4;CM-QOS=1.1;CM-VER=3.0;
2018-6-17, 17:45:02 Warning (5) Dynamic Range Window violation
2018-6-17, 17:45:06 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:79:36:40;CMTS-MAC=00:17:10:92:9a:a4;CM-QOS=1.1;CM-VER=3.0;
2018-6-17, 17:53:12 Warning (5) MDD message timeout;CM-MAC=2c:30:33:79:36:40;CMTS-MAC=00:17:10:92:9a:a4;CM-QOS=1.1;CM-VER=3.0;
2018-6-17, 17:55:18 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:79:36:40;CMTS-MAC=00:17:10:92:9a:a4;CM-QOS=1.1;CM-VER=3.0;
2018-6-17, 17:55:22 Warning (5) Dynamic Range Window violation
2018-6-17, 18:03:08 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:79:36:40;CMTS-MAC=00:17:10:92:9a:a4;CM-QOS=1.1;CM-VER=3.0;
2018-6-17, 18:04:21 Warning (5) MDD message timeout;CM-MAC=2c:30:33:79:36:40;CMTS-MAC=00:17:10:92:9a:a4;CM-QOS=1.1;CM-VER=3.0;
2018-6-17, 18:04:28 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:79:36:40;CMTS-MAC=00:17:10:92:9a:a4;CM-QOS=1.1;CM-VER=3.0;
2018-6-17, 18:04:36 Warning (5) MDD message timeout;CM-MAC=2c:30:33:79:36:40;CMTS-MAC=00:17:10:92:9a:a4;CM-QOS=1.1;CM-VER=3.0;
2018-6-17, 18:08:53 Warning (5) Dynamic Range Window violation
2018-6-17, 18:09:27 Warning (5) MDD message timeout;CM-MAC=2c:30:33:79:36:40;CMTS-MAC=00:17:10:92:9a:a4;CM-QOS=1.1;CM-VER=3.0;
2018-6-17, 18:15:33 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:79:36:40;CMTS-MAC=00:17:10:92:9a:a4;CM-QOS=1.1;CM-VER=3.0;
2018-6-17, 18:15:33 Warning (5) Dynamic Range Window violation
2018-6-17, 18:16:25 Warning (5) MDD message timeout;CM-MAC=2c:30:33:79:36:40;CMTS-MAC=00:17:10:92:9a:a4;CM-QOS=1.1;CM-VER=3.0;
2018-6-17, 18:16:26 Warning (5) Dynamic Range Window violation
2018-6-17, 18:16:46 Warning (5) MDD message timeout;CM-MAC=2c:30:33:79:36:40;CMTS-MAC=00:17:10:92:9a:a4;CM-QOS=1.1;CM-VER=3.0;
2018-6-17, 18:17:22 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:79:36:40;CMTS-MAC=00:17:10:92:9a:a4;CM-QOS=1.1;CM-VER=3.0;
2018-6-17, 18:18:35 Warning (5) Dynamic Range Window violation
2018-6-17, 18:19:27 Warning (5) MDD message timeout;CM-MAC=2c:30:33:79:36:40;CMTS-MAC=00:17:10:92:9a:a4;CM-QOS=1.1;CM-VER=3.0;
2018-6-17, 18:21:46 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:79:36:40;CMTS-MAC=00:17:10:92:9a:a4;CM-QOS=1.1;CM-VER=3.0;
2018-6-17, 18:34:37 Warning (5) MDD message timeout;CM-MAC=2c:30:33:79:36:40;CMTS-MAC=00:17:10:92:9a:a4;CM-QOS=1.1;CM-VER=3.0;
2018-6-17, 18:34:37 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:79:36:40;CMTS-MAC=00:17:10:92:9a:a4;CM-QOS=1.1;CM-VER=3.0;
2018-6-17, 18:40:18 Warning (5) MDD message timeout;CM-MAC=2c:30:33:79:36:40;CMTS-MAC=00:17:10:92:9a:a4;CM-QOS=1.1;CM-VER=3.0;
2018-6-17, 18:42:02 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:79:36:40;CMTS-MAC=00:17:10:92:9a:a4;CM-QOS=1.1;CM-VER=3.0;
2018-6-17, 18:42:32 Warning (5) Dynamic Range Window violation
2018-6-17, 18:43:56 Warning (5) MDD message timeout;CM-MAC=2c:30:33:79:36:40;CMTS-MAC=00:17:10:92:9a:a4;CM-QOS=1.1;CM-VER=3.0;
2018-6-17, 18:46:28 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:79:36:40;CMTS-MAC=00:17:10:92:9a:a4;CM-QOS=1.1;CM-VER=3.0;
2018-6-17, 19:22:04 Warning (5) MDD message timeout;CM-MAC=2c:30:33:79:36:40;CMTS-MAC=00:17:10:92:9a:a4;CM-QOS=1.1;CM-VER=3.0;
2018-6-17, 19:24:11 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:79:36:40;CMTS-MAC=00:17:10:92:9a:a4;CM-QOS=1.1;CM-VER=3.0;
2018-6-17, 19:26:12 Warning (5) Dynamic Range Window violation
2018-6-17, 19:27:12 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:79:36:40;CMTS-MAC=00:17:10:92:9a:a4;CM-QOS=1.1;CM-VER=3.0;
2018-6-17, 19:28:03 Warning (5) MDD message timeout;CM-MAC=2c:30:33:79:36:40;CMTS-MAC=00:17:10:92:9a:a4;CM-QOS=1.1;CM-VER=3.0;
2018-6-17, 19:31:13 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:79:36:40;CMTS-MAC=00:17:10:92:9a:a4;CM-QOS=1.1;CM-VER=3.0;
2018-6-17, 19:45:44 Warning (5) Dynamic Range Window violation
2018-6-17, 19:48:15 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:79:36:40;CMTS-MAC=00:17:10:92:9a:a4;CM-QOS=1.1;CM-VER=3.0;
2018-6-17, 19:59:07 Warning (5) MDD message timeout;CM-MAC=2c:30:33:79:36:40;CMTS-MAC=00:17:10:92:9a:a4;CM-QOS=1.1;CM-VER=3.0;
2018-6-17, 20:01:21 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:79:36:40;CMTS-MAC=00:17:10:92:9a:a4;CM-QOS=1.1;CM-VER=3.0;
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 6 153000000 Hz 4.8 dBmV 39.3 dB 45259896 5528929
2 Locked QAM256 2 117000000 Hz 6.1 dBmV 39.4 dB 48384347 15844689
3 Locked QAM256 3 123000000 Hz 6 dBmV 39.3 dB 48239423 13537398
4 Locked QAM256 4 129000000 Hz 5.8 dBmV 39.2 dB 47946243 11545935
5 Locked QAM256 5 147000000 Hz 5.1 dBmV 39.3 dB 46304629 7035985
6 Locked QAM256 1 111000000 Hz 6.2 dBmV 38.9 dB 48445443 18108164
7 Locked QAM256 7 159000000 Hz 4.4 dBmV 39.4 dB 44234007 4526385
8 Locked QAM256 8 165000000 Hz 4 dBmV 39.4 dB 42818236 3455251
9 Locked QAM256 9 171000000 Hz 3.7 dBmV 39.5 dB 41102493 2495852
10 Locked QAM256 10 177000000 Hz 3.5 dBmV 39.3 dB 40345278 2116187
11 Locked QAM256 11 183000000 Hz 3.6 dBmV 39.3 dB 39290602 1671531
12 Locked QAM256 12 189000000 Hz 3.4 dBmV 39.5 dB 37709248 1259135
13 Locked QAM256 13 195000000 Hz 3.1 dBmV 39.3 dB 37070252 1116240
14 Locked QAM256 14 201000000 Hz 2.9 dBmV 39.8 dB 35297033 791403
15 Locked QAM256 15 207000000 Hz 2.6 dBmV 39.5 dB 33264346 584934
16 Locked QAM256 16 213000000 Hz 2.1 dBmV 38.2 dB 32347834 546616
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 1 5120 Ksym/sec 35750000 Hz 43.3 dBmV
2 Locked ATDMA 2 5120 Ksym/sec 28250000 Hz 43.3 dBmV
3 Locked ATDMA 3 5120 Ksym/sec 20750000 Hz 40.8 dBmV
Needless to say, service was obviously not restored despite supports claims that it is. You cannot stream anything with the above, let alone even try to use voip or any service that cant handle dropped packets.
My frustration is that this occurs EVERY weekend outage we have, the tech on call claims service was restored when it was not and we then have to fight with support with them saying we have to wait two weeks before we can get a tech out. Our local facebook group has confirmed this is is happening all over the area, why is it so difficult for support to see this and escalate above the on call who lied yet again saying service was restored?
↧