Community Forum

SB6190 and CM1000 troubles activating the xfinity can't see them?

Xfinity Forum Archive
About the archive project

Xfinity Forum Archive...

This is an archived section of the community.

Content in this area has been identified as outdated or irrelevant.

This change was done in an effort to make the forum easier to use and to keep only the most helpful and recent content active.

Post your questions in the Xfinity Community

Expert

Re: SB6190 and CM1000 troubles activating the xfinity can't see them?

The problem with the 6190 is that only one upstream is seen, have you noticed it ever go to 50+ for the upstream power? The CM1000-1AZNAS model is not compatible with Comcast. Have you tried reactivating using online activation. Just make sure that the old modem is powered off.

I am not a Comcast Employee.
I am just a customer, volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.

Was your question answered? Mark the post as best answer!
Frequent Visitor

Re: SB6190 and CM1000 troubles activating the xfinity can't see them?

I did call the activation line. I've spent about 2-3 hours on 4 different calls. That's why I'm here on the forums. Yesterday the guy wanted to send someone on my dime since they can't see any of the modems.

Frequent Visitor

Re: SB6190 and CM1000 troubles activating the xfinity can't see them?

As for the CM1000.  The two that I tried to activate I was told by the comcast tech that Netgear said to return them since they are defective and come back tomorrow. So, both are gone. However below is the info for the one I'm returning today.

 

 

Cable Connection

Apply             Cancel    

Frequency start Value

This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect.

Starting Frequency

Startup Procedure

Procedure

Status

Comment

Acquire Downstream Channel

657000000 Hz

Locked

Connectivity State

OK

Operational

Boot State

OK

Operational

Security

Enable

BPI+

IP Provisioning Mode

Honor MDD

IPv6 only

Downstream Bonded Channels

Channel

Lock Status

Modulation

Channel ID

Frequency

Power

SNR / MER

Unerrored Codewords

Correctable Codewords

Uncorrectable Codewords

1

Locked

QAM256

32

657000000 Hz

3.0 dBmV

39.0 dB

4724403

0

0

2

Locked

QAM256

1

471000000 Hz

5.2 dBmV

40.2 dB

3468644

0

0

3

Locked

QAM256

2

477000000 Hz

4.9 dBmV

40.1 dB

3478093

0

0

4

Locked

QAM256

3

483000000 Hz

2.4 dBmV

38.8 dB

3487317

0

0

5

Locked

QAM256

4

489000000 Hz

4.2 dBmV

39.8 dB

3496544

0

0

6

Locked

QAM256

5

495000000 Hz

4.3 dBmV

39.7 dB

3506492

0

0

7

Locked

QAM256

6

501000000 Hz

3.6 dBmV

39.6 dB

3515680

0

0

8

Locked

QAM256

7

507000000 Hz

3.7 dBmV

39.6 dB

3525169

0

0

9

Locked

QAM256

8

513000000 Hz

2.5 dBmV

39.2 dB

3534387

0

0

10

Locked

QAM256

9

519000000 Hz

4.2 dBmV

40.0 dB

3543729

0

0

11

Locked

QAM256

10

525000000 Hz

3.6 dBmV

39.7 dB

3553972

0

0

12

Locked

QAM256

11

531000000 Hz

2.2 dBmV

38.8 dB

3563193

0

0

13

Locked

QAM256

12

537000000 Hz

3.2 dBmV

39.5 dB

3572254

0

0

14

Locked

QAM256

13

543000000 Hz

3.1 dBmV

39.6 dB

3581466

0

0

15

Locked

QAM256

14

549000000 Hz

2.6 dBmV

39.1 dB

3590915

0

0

16

Locked

QAM256

15

555000000 Hz

2.2 dBmV

39.1 dB

3600475

0

0

17

Locked

QAM256

16

561000000 Hz

2.0 dBmV

38.9 dB

3609771

0

0

18

Locked

QAM256

17

567000000 Hz

1.8 dBmV

38.9 dB

3618962

0

0

19

Locked

QAM256

18

573000000 Hz

2.5 dBmV

39.2 dB

3628218

0

0

20

Locked

QAM256

20

585000000 Hz

1.1 dBmV

38.4 dB

3637608

0

0

21

Locked

QAM256

21

591000000 Hz

2.0 dBmV

38.9 dB

3647140

0

0

22

Locked

QAM256

22

597000000 Hz

2.0 dBmV

38.9 dB

3656204

0

0

23

Locked

QAM256

23

603000000 Hz

0.8 dBmV

38.2 dB

3665593

0

0

24

Locked

QAM256

24

609000000 Hz

1.1 dBmV

38.3 dB

3674840

0

0

25

Locked

QAM256

25

615000000 Hz

0.9 dBmV

38.4 dB

3684639

0

0

26

Locked

QAM256

26

621000000 Hz

2.1 dBmV

39.0 dB

3693838

0

0

27

Locked

QAM256

27

627000000 Hz

1.9 dBmV

38.6 dB

3702938

0

0

28

Locked

QAM256

28

633000000 Hz

1.7 dBmV

38.6 dB

3712697

0

0

29

Locked

QAM256

29

639000000 Hz

2.7 dBmV

38.7 dB

3721801

0

0

30

Locked

QAM256

30

645000000 Hz

3.2 dBmV

39.2 dB

3728192

0

0

31

Locked

QAM256

31

651000000 Hz

1.1 dBmV

38.2 dB

3734776

0

0

32

Not Locked

Unknown

0

0 Hz

0.0 dBmV

0.0 dB

0

0

0

Upstream Bonded Channels

Channel

Lock Status

Modulation

Channel ID

Frequency

Power

1

Locked

ATDMA

13

35800000 Hz

48.3 dBmV

2

Locked

ATDMA

14

29400000 Hz

48.0 dBmV

3

Locked

ATDMA

15

23000000 Hz

47.8 dBmV

4

Locked

ATDMA

16

16600000 Hz

46.8 dBmV

5

Not Locked

Unknown

0

0 Hz

0.0 dBmV

6

Not Locked

Unknown

0

0 Hz

0.0 dBmV

7

Not Locked

Unknown

0

0 Hz

0.0 dBmV

8

Not Locked

Unknown

0

0 Hz

0.0 dBmV

Downstream OFDM Channels

Channel

Lock Status

Modulation / Profile ID

Channel ID

Frequency

Power

SNR / MER

Active Subcarrier Number Range

Unerrored Codewords

Correctable Codewords

Uncorrectable Codewords

1

Locked

0, 1

33

708000000 Hz

7.0 dBmV

38.5 dB

1108 ~ 2987

91367

25916

0

2

Not Locked

0

0

0 Hz

7.3 dBmV

0.0 dB

0 ~ 4095

0

0

0

Upstream OFDMA Channels

Channel

Lock Status

Modulation / Profile ID

Channel ID

Frequency

Power

1

Not Locked

Unknown

0

0 Hz

0 dBmV

2

Not Locked

Unknown

0

0 Hz

0 dBmV

Current System Time: Wed Aug 01 04:51:10 2018 

 

 

Event Log

      Clear Log              Refresh       

Time

Priority

Description

2018-08-01, 04:49:44

Notice (6)

DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 .;CM-MAC=78:d2:94:5b:8c:b8;CMTS-MAC=00:01:5c:82:fc:61;CM-QOS=1.1;CM-VER=3.1;

2018-08-01, 04:49:35

Notice (6)

TLV-11 - unrecognized OID;CM-MAC=78:d2:94:5b:8c:b8;CMTS-MAC=00:01:5c:82:fc:61;CM-QOS=1.1;CM-VER=3.1;

Time Not Established

Notice (6)

Honoring MDD; IP provisioning mode = IPv6

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=78:d2:94:5b:8c:b8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

Time Not Established

Critical (3)

No Ranging Response received - T3 time-out;CM-MAC=78:d2:94:5b:8c:b8;CMTS-MAC=00:01:5c:82:fc:61;CM-QOS=1.1;CM-VER=3.1;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=78:d2:94:5b:8c:b8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

2018-07-31, 20:38:54

Critical (3)

Resetting the cable modem due to docsDevResetNow

Time Not Established

Critical (3)

No Ranging Response received - T3 time-out;CM-MAC=78:d2:94:5b:8c:b8;CMTS-MAC=00:01:5c:82:fc:61;CM-QOS=1.1;CM-VER=3.1;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=78:d2:94:5b:8c:b8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

2018-07-31, 20:33:49

Critical (3)

Resetting the cable modem due to docsDevResetNow

Time Not Established

Critical (3)

No Ranging Response received - T3 time-out;CM-MAC=78:d2:94:5b:8c:b8;CMTS-MAC=00:01:5c:82:fc:61;CM-QOS=1.1;CM-VER=3.1;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=78:d2:94:5b:8c:b8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

2018-07-31, 20:21:27

Critical (3)

Resetting the cable modem due to docsDevResetNow

Time Not Established

Critical (3)

No Ranging Response received - T3 time-out;CM-MAC=78:d2:94:5b:8c:b8;CMTS-MAC=00:01:5c:82:fc:61;CM-QOS=1.1;CM-VER=3.1;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=78:d2:94:5b:8c:b8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=78:d2:94:5b:8c:b8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

 

 

Help Center

 

Show/Hide Help Center

 

From <http://192.168.100.1/EventLog.asp>

 

 

 

Capturea1.PNG
Capturea2.PNG
Frequent Visitor

Re: SB6190 and CM1000 troubles activating the xfinity can't see them?

Images for the SB6190

 

Capture1.PNG
Capture2.PNG
Capture3.PNG
Capture4.PNG
Diamond Problem Solver

Re: SB6190 and CM1000 troubles activating the xfinity can't see them?

The CSR's at 1-800-comcast can see your signal stats if the modem is online. Have you tried calling ?

Expert

Re: SB6190 and CM1000 troubles activating the xfinity can't see them?

The pictures for your signal stats appear to be broken. What about the CM1000 you mentioned in the title?
I am not a Comcast Employee.
I am just a customer, volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.

Was your question answered? Mark the post as best answer!
Frequent Visitor

Re: SB6190 and CM1000 troubles activating the xfinity can't see them?

Looks like the Event log didn't want to attach, so here it is:

 
 
 
 
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
Mon Jul 23 18:02:03 2018 6 Received REG-RSP while in REG-HOLD1 state;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
Mon Jul 23 18:14:19 2018 5 RCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
Mon Jul 23 18:14:19 2018 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
Mon Jul 23 18:14:19 2018 5 RCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
Mon Jul 23 18:14:19 2018 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
Mon Jul 23 18:14:19 2018 5 RCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 01 00:01:52 1970 3 No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
Thu Jul 26 18:55:57 2018 6 TLV-11 - unrecognized OID;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
Thu Jul 26 18:56:00 2018 6 Received REG-RSP while in REG-HOLD1 state;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 01 00:01:51 1970 3 No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
Thu Jul 26 19:03:10 2018 6 TLV-11 - unrecognized OID;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
Thu Jul 26 19:03:13 2018 6 Received REG-RSP while in REG-HOLD1 state;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 01 00:01:52 1970 3 No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
Tue Jul 31 18:56:29 2018 6 TLV-11 - unrecognized OID;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
Tue Jul 31 18:56:32 2018 6 Received REG-RSP while in REG-HOLD1 state;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
Tue Jul 31 19:11:52 2018 3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 01 00:01:51 1970 3 No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
Tue Jul 31 19:14:31 2018 6 TLV-11 - unrecognized OID;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
Tue Jul 31 19:14:34 2018 6 Received REG-RSP while in REG-HOLD1 state;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
Tue Jul 31 19:29:56 2018 3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;

 
 
 
 
Frequent Visitor

SB6190 and CM1000 troubles activating the xfinity can't see them?

My SB6190 lost it's connection to xfinity a couple of weeks and after trying to re-activate it I settled with using my old SB6121 until this was resolved.  I've recently connected the SB6190 back and get the following signal levels:

ch1.PNGch 2.PNGproduct info.PNGstatus.PNG

Hopefully someone can help me get the SB6190 activated and provisioned to the speeds I'm subscribed to. In the mean time want to keep using the SB6121.

I've attached the event log

Thanks, Edgardo