Signal Issue SB6190 - Time Warner Internet

#1
This question is about "Signal Issue SB6190", with Time Warner Cable internet and apps. I was inquring about why I am unable to lock a signal on CH's 2-5 on my SB6190 in Dayton Ohio? I recently upgraded to 300/20 service and am an Internet Only customer with a direct line and no splitters. Please advise.

Status
Home > Status > Connection
The statuses listed show the connection state of the cable modem. They are used by your service provider to evaluate the operation of the cable modem.

Startup Procedure [TABLE]

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


[/TABLE]


Downstream Bonded Channels [TABLE]

Channel

Lock Status

Modulation

Channel ID

Frequency

Power

SNR

Corrected

Uncorrectables


1

Locked

256QAM

31

759.00 MHz

2.40 dBmV

40.37 dB

57

0


2

Not Locked

----

9

627.00 MHz

----

----

----

----


3

Not Locked

----

10

633.00 MHz

----

----

----

----


4

Not Locked

----

11

639.00 MHz

----

----

----

----


5

Not Locked

----

13

651.00 MHz

----

----

----

----


6

Locked

256QAM

14

657.00 MHz

-7.70 dBmV

34.35 dB

2765186

23334


7

Locked

256QAM

15

663.00 MHz

-1.00 dBmV

38.61 dB

26487

6002


8

Locked

256QAM

16

669.00 MHz

1.80 dBmV

40.37 dB

58

0


9

Locked

256QAM

17

675.00 MHz

3.10 dBmV

40.95 dB

59

0


10

Locked

256QAM

18

681.00 MHz

3.70 dBmV

40.37 dB

47

0


11

Locked

256QAM

19

687.00 MHz

4.10 dBmV

40.37 dB

37

0


12

Locked

256QAM

20

693.00 MHz

4.60 dBmV

40.37 dB

38

0


13

Locked

256QAM

21

699.00 MHz

4.70 dBmV

40.37 dB

33

0


14

Locked

256QAM

22

705.00 MHz

4.70 dBmV

40.37 dB

57

0


15

Locked

256QAM

23

711.00 MHz

4.50 dBmV

40.95 dB

69

0


16

Locked

256QAM

24

717.00 MHz

4.40 dBmV

40.95 dB

54

0


17

Locked

256QAM

25

723.00 MHz

3.90 dBmV

40.95 dB

51

0


18

Locked

256QAM

26

729.00 MHz

3.60 dBmV

40.95 dB

62

0


19

Locked

256QAM

27

735.00 MHz

3.50 dBmV

40.37 dB

74

0


20

Locked

256QAM

28

741.00 MHz

3.40 dBmV

40.37 dB

72

4


21

Locked

256QAM

29

747.00 MHz

3.00 dBmV

40.37 dB

63

0


22

Locked

256QAM

30

753.00 MHz

2.80 dBmV

40.95 dB

55

0


23

Locked

256QAM

32

765.00 MHz

2.30 dBmV

40.37 dB

93

0


[/TABLE]


Upstream Bonded Channels [TABLE]

Channel

Lock Status

US Channel Type

Channel ID

Symbol Rate

Frequency

Power


1

Locked

ATDMA

11

5120 kSym/s

30.60 MHz

38.50 dBmV


2

Locked

ATDMA

12

2560 kSym/s

37.00 MHz

39.50 dBmV


3

Locked

ATDMA

10

5120 kSym/s

24.20 MHz

37.50 dBmV


4

Locked

TDMA

9

2560 kSym/s

19.40 MHz

37.00 dBmV


[/TABLE]



Current System Time: Mon Jan 30 13:43:51 2017​

Event Log
Home > Status > Event Log
The table below contains the log of events that the SB6190 has detected. This log can be important to the service provider to help diagnose and correct problems, if any should occur.

Time Priority Description [TABLE]

Tue Jan 24 12:50:16 2017

5

Lost MDD Timeout;CM-MAC=d4:0a:a9:55:54:8f;CMTS-MAC=00:01:5c:68:e2:5f;CM-QOS=1.1;CM-VER=3.0;


Tue Jan 24 12:50:24 2017

3

No Ranging Response received - T3 time-out;CM-MAC=d4:0a:a9:55:54:8f;CMTS-MAC=00:01:5c:68:e2:5f;CM-QOS=1.1;CM-VER=3.0;


Tue Jan 24 12:50:43 2017

5

RCS Partial Service;CM-MAC=d4:0a:a9:55:54:8f;CMTS-MAC=00:01:5c:68:e2:5f;CM-QOS=1.1;CM-VER=3.0;


Thu Jan 01 00:01:51 1970

5

ToD request sent - No Response received;CM-MAC=d4:0a:a9:55:54:8f;CMTS-MAC=00:01:5c:68:e2:5f;CM-QOS=1.1;CM-VER=3.0;


Thu Jan 01 00:00:31 1970

3

TFTP failed - Request sent - No Response;CM-MAC=d4:0a:a9:55:54:8f;CMTS-MAC=00:01:5c:68:e2:5f;CM-QOS=1.1;CM-VER=3.0;


Thu Jan 01 00:00:33 1970

3

TFTP Request Retries exceeded, CM unable to register


Thu Jan 01 00:01:15 1970

3

No Ranging Response received - T3 time-out;CM-MAC=d4:0a:a9:55:54:8f;CMTS-MAC=00:01:5c:68:e2:5f;CM-QOS=1.1;CM-VER=3.0;


Tue Jan 24 12:55:55 2017

5

RCS Partial Service;CM-MAC=d4:0a:a9:55:54:8f;CMTS-MAC=00:01:5c:68:e2:5f;CM-QOS=1.1;CM-VER=3.0;


Tue Jan 24 18:02:02 2017

3

No Ranging Response received - T3 time-out;CM-MAC=d4:0a:a9:55:54:8f;CMTS-MAC=00:01:5c:68:e2:5f;CM-QOS=1.1;CM-VER=3.0;


Wed Jan 25 09:01:36 2017

5

RCS Partial Service;CM-MAC=d4:0a:a9:55:54:8f;CMTS-MAC=00:01:5c:68:e2:5f;CM-QOS=1.1;CM-VER=3.0;


Sat Jan 28 15:59:13 2017

3

No Ranging Response received - T3 time-out;CM-MAC=d4:0a:a9:55:54:8f;CMTS-MAC=00:01:5c:68:e2:5f;CM-QOS=1.1;CM-VER=3.0;


Sun Jan 29 09:07:51 2017

5

RCS Partial Service;CM-MAC=d4:0a:a9:55:54:8f;CMTS-MAC=00:01:5c:68:e2:5f;CM-QOS=1.1;CM-VER=3.0;


Thu Jan 01 00:01:54 1970

5

ToD request sent - No Response received;CM-MAC=d4:0a:a9:55:54:8f;CMTS-MAC=00:01:5c:68:e2:5f;CM-QOS=1.1;CM-VER=3.0;


Thu Jan 01 00:00:31 1970

3

TFTP failed - Request sent - No Response;CM-MAC=d4:0a:a9:55:54:8f;CMTS-MAC=00:01:5c:68:e2:5f;CM-QOS=1.1;CM-VER=3.0;


Thu Jan 01 00:00:33 1970

3

TFTP Request Retries exceeded, CM unable to register


Thu Jan 01 00:00:35 1970

5

ToD request sent - No Response received;CM-MAC=d4:0a:a9:55:54:8f;CMTS-MAC=00:01:5c:68:e2:5f;CM-QOS=1.1;CM-VER=3.0;


Thu Jan 01 00:01:06 1970

3

No Ranging Response received - T3 time-out;CM-MAC=d4:0a:a9:55:54:8f;CMTS-MAC=00:01:5c:68:e2:5f;CM-QOS=1.1;CM-VER=3.0;


Thu Jan 01 00:01:19 1970

5

ToD request sent - No Response received;CM-MAC=d4:0a:a9:55:54:8f;CMTS-MAC=00:01:5c:68:e2:5f;CM-QOS=1.1;CM-VER=3.0;


Thu Jan 01 00:00:02 1970

5

RCS Partial Service;CM-MAC=d4:0a:a9:55:54:8f;CMTS-MAC=00:01:5c:68:e2:5f;CM-QOS=1.1;CM-VER=3.0;


Thu Jan 01 00:00:05 1970

4

ToD request sent- No Response received;CM-MAC=d4:0a:a9:55:54:8f;CMTS-MAC=00:01:5c:68:e2:5f;CM-QOS=1.1;CM-VER=3.0;


[/TABLE]




This topic covered Signal Issue SB6190, and TWC cable internet service.
 
Top