Lingering issues after line tech visits - Time Warner Internet

#1
This question is about "Lingering issues after line tech visits", with Time Warner Cable internet and apps. Greetings,



I've had the line techs come out twice now to my home in Dallas to try and salvage the hot mess that is my connection... Originally I had 20/24 channels below -15dBmV, but they adjusted things and it's a little better now. A few lingering issues though:



1) Even after line maintenance, I have one channel that has a ton of uncorrectables, and I'm not sure why. This channel is also repeatedly losing lock. It's at 753MHz which is LTE spectrum if I remember correctly.

2) Tons of correctables, probably because the signal out here is bonkers.

3) TDMA channel is running at 38dBmV, not sure if it should be doing that? Seems a little low.

4) Lots of messages about T3 timeouts ever since I rebooted the modem this morning. I figure this may be related to item 3.



Can anyone provide some insight as to what I should do? If the line techs have been out here twice and signed off on the job, I'm kind of at a loss for how to make things better... If I need to keep complaining, I'd also rather complain effectively.



Thanks for taking a look.



[TABLE]

Downstream Bonded Channels


[TABLE]

Channel

Lock Status

Modulation

Channel ID

Frequency

Power

SNR

Correctables

Uncorrectables


1

Locked

QAM256

24

813000000 Hz

0.4 dBmV

36.1 dB

1636224

0


2

Locked

QAM256

9

723000000 Hz

4.9 dBmV

38.7 dB

282878

0


3

Locked

QAM256

10

729000000 Hz

2.8 dBmV

32.5 dB

1390095

0


4

Locked

QAM256

11

735000000 Hz

6.3 dBmV

36.4 dB

167247

0


5

Locked

QAM256

12

741000000 Hz

1.8 dBmV

36.8 dB

1561229

0


6

Locked

QAM256

13

747000000 Hz

6.1 dBmV

36.3 dB

387721

0


7

Locked

QAM256

14

753000000 Hz

1.5 dBmV

31.1 dB

9095162

6360633


8

Locked

QAM256

15

759000000 Hz

4.4 dBmV

38.1 dB

349529

0


9

Locked

QAM256

16

765000000 Hz

3.2 dBmV

37.2 dB

848401

0


10

Locked

QAM256

17

771000000 Hz

0.9 dBmV

36.3 dB

1726300

0


11

Locked

QAM256

18

777000000 Hz

3.3 dBmV

37.9 dB

485379

0


12

Locked

QAM256

19

783000000 Hz

0.0 dBmV

35.8 dB

3134607

0


13

Locked

QAM256

20

789000000 Hz

2.5 dBmV

37.6 dB

525336

0


14

Locked

QAM256

21

795000000 Hz

-1.6 dBmV

34.8 dB

6624465

0


15

Locked

QAM256

22

801000000 Hz

2.2 dBmV

37.5 dB

504120

0


16

Locked

QAM256

23

807000000 Hz

-2.9 dBmV

33.9 dB

11223840

0


17

Locked

QAM256

25

819000000 Hz

-3.8 dBmV

33.9 dB

1551

0


18

Locked

QAM256

26

825000000 Hz

-4.4 dBmV

33.0 dB

2376

0


19

Locked

QAM256

27

831000000 Hz

-2.5 dBmV

34.5 dB

1068

0


20

Locked

QAM256

28

837000000 Hz

-5.3 dBmV

33.0 dB

3334

0


21

Locked

QAM256

29

843000000 Hz

-1.9 dBmV

35.6 dB

397

0


22

Locked

QAM256

30

849000000 Hz

-6.8 dBmV

31.6 dB

6889

0


23

Locked

QAM256

31

855000000 Hz

-3.2 dBmV

34.8 dB

369

0


24

Locked

QAM256

32

861000000 Hz

-7.3 dBmV

30.5 dB

8934

0

[/TABLE]


Upstream Bonded Channels


[TABLE]

Channel

Lock Status

US Channel Type

Channel ID

Symbol Rate

Frequency

Power


1

Locked

ATDMA

2

5120 Ksym/sec

24200000 Hz

40.3 dBmV


2

Locked

TDMA

1

2560 Ksym/sec

19400000 Hz

38.0 dBmV


3

Locked

ATDMA

3

5120 Ksym/sec

30600000 Hz

40.5 dBmV


4

Locked

ATDMA

4

5120 Ksym/sec

37000000 Hz

42.0 dBmV


5

Not Locked

Unknown

0

0 Ksym/sec

0 Hz

0.0 dBmV


6

Not Locked

Unknown

0

0 Ksym/sec

0 Hz

0.0 dBmV


7

Not Locked

Unknown

0

0 Ksym/sec

0 Hz

0.0 dBmV


8

Not Locked

Unknown

0

0 Ksym/sec

0 Hz

0.0 dBmV

[/TABLE]

[/TABLE]
[TABLE]

Time

Priority

Description


2018-06-13, 21:08:58

Warning (5)

MDD message timeout;CM-MAC=10:da:43:50:84:39;CMTS-MAC=00:01:5c:a1:e4:61;CM-QOS=1.1;CM-VER=3.0;


2018-06-13, 20:29:37

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:50:84:39;CMTS-MAC=00:01:5c:a1:e4:61;CM-QOS=1.1;CM-VER=3.0;


2018-06-13, 20:28:50

Warning (5)

MDD message timeout;CM-MAC=10:da:43:50:84:39;CMTS-MAC=00:01:5c:a1:e4:61;CM-QOS=1.1;CM-VER=3.0;


2018-06-13, 18:48:47

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:50:84:39;CMTS-MAC=00:01:5c:a1:e4:61;CM-QOS=1.1;CM-VER=3.0;


2018-06-13, 18:48:45

Warning (5)

MDD message timeout;CM-MAC=10:da:43:50:84:39;CMTS-MAC=00:01:5c:a1:e4:61;CM-QOS=1.1;CM-VER=3.0;


2018-06-13, 17:02:37

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:50:84:39;CMTS-MAC=00:01:5c:a1:e4:61;CM-QOS=1.1;CM-VER=3.0;


2018-06-13, 16:59:01

Warning (5)

MDD message timeout;CM-MAC=10:da:43:50:84:39;CMTS-MAC=00:01:5c:a1:e4:61;CM-QOS=1.1;CM-VER=3.0;


2018-06-13, 15:14:00

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:50:84:39;CMTS-MAC=00:01:5c:a1:e4:61;CM-QOS=1.1;CM-VER=3.0;


2018-06-13, 15:07:44

Warning (5)

MDD message timeout;CM-MAC=10:da:43:50:84:39;CMTS-MAC=00:01:5c:a1:e4:61;CM-QOS=1.1;CM-VER=3.0;


2018-06-13, 10:48:53

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:50:84:39;CMTS-MAC=00:01:5c:a1:e4:61;CM-QOS=1.1;CM-VER=3.0;


2018-06-13, 10:48:21

Warning (5)

MDD message timeout;CM-MAC=10:da:43:50:84:39;CMTS-MAC=00:01:5c:a1:e4:61;CM-QOS=1.1;CM-VER=3.0;


2018-06-13, 09:57:16

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:50:84:39;CMTS-MAC=00:01:5c:a1:e4:61;CM-QOS=1.1;CM-VER=3.0;


2018-06-13, 09:57:11

Warning (5)

MDD message timeout;CM-MAC=10:da:43:50:84:39;CMTS-MAC=00:01:5c:a1:e4:61;CM-QOS=1.1;CM-VER=3.0;


2018-06-13, 06:46:43

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:50:84:39;CMTS-MAC=00:01:5c:a1:e4:61;CM-QOS=1.1;CM-VER=3.0;


2018-06-13, 06:45:08

Warning (5)

MDD message timeout;CM-MAC=10:da:43:50:84:39;CMTS-MAC=00:01:5c:a1:e4:61;CM-QOS=1.1;CM-VER=3.0;

[/TABLE]

Lingering issues after line tech visits?
 
Top