Skip to main content
Question

SB8200 my connection is dropping intermittently over past 3 days

D
The Many
Forum|alt.badge.img
  • dscThe Many
  • The Many
  • 2 replies

Rebooted laptop, modem, and router -- drops still happening and garbling webex audio.

Xfinity mobile app is not showing any indication of outages.

Fast.com and speedtest.net always eventually revert to normal speed at round 85 Mbps, but still drops happening.

On the SB8200 status screen, comparing expected values on

https://arris.my.salesforce-sites.com/consumers/articles/General_FAQs/SB8200-Cable-Signal-Levels

to what I see, the one that stands out is upstream bonded channel power is at 37 or 38 for me:

whereas the doc says acceptable is 45 - 51.

 

So, what do you think?  Is this a real problem?  could be THE problem?  No idea what this power level was 4 days ago when webex was fine.

This topic has been closed for comments

5 replies

plemans
Juggernaut
Forum|alt.badge.img+41
  • plemansJuggernaut
  • Juggernaut
  • 2274 replies
  • March 4, 2023

do you also have the downstream values and event logs?

the values have a range because if you’re right next to a hub, the modem doesn’t need as much power to connect with it. And that’ll be reflected because your downstream values will be high. 

Current setup: Netgear CM3000-->Netgear RBE973S-->2.5gig tp-link switch, Xfinity 2.4gig/350mbps
D
The Many
Forum|alt.badge.img
  • dscThe Many
  • Author
  • The Many
  • 2 replies
  • March 5, 2023

Here is the downstream info - looks to be 7.5 - 12.1.  And yes, the TP-Link Mesh router is connected to the modem with 6” of cable.

 

Here is the event log:

Date Time

Event ID

Event Level

Description

03/05/2023 05:24

82000500

3

"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

03/03/2023 11:07

82000200

3

"No Ranging Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

03/03/2023 11:07

84000500

3

"SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

03/03/2023 11:07

67061600

6

"DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

01/01/1970 00:00

2436694066

6

"Honoring MDD; IP provisioning mode = IPv6"

01/01/1970 00:00

84000100

3

"SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[removed];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"

03/03/2023 10:22

82000500

3

"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

03/03/2023 08:12

82000200

3

"No Ranging Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

01/01/1970 00:00

84000100

3

"SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[removed];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"

03/03/2023 08:18

2436694044

3

"Resetting the cable modem due to docsDevResetNow"

03/03/2023 08:15

82000500

3

"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

03/02/2023 17:07

82000500

3

"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

03/02/2023 16:23

82000500

3

"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

03/02/2023 14:48

82000500

3

"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

03/02/2023 14:26

82000500

3

"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

02/27/2023 20:37

82000500

3

"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

02/27/2023 20:18

82000500

3

"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

02/27/2023 20:11

82000500

3

"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

02/27/2023 17:30

82000500

3

"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

02/27/2023 17:15

82000500

3

"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

02/27/2023 17:01

82000500

3

"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

02/25/2023 21:21

82000500

3

"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

02/22/2023 09:36

82000200

3

"No Ranging Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

 

 

 

  

 

 

 

 

 

 

  

Date Time

Event ID

Event Level

Description

03/05/2023 05:24

82000500

3

"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

03/03/2023 11:07

82000200

3

"No Ranging Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

03/03/2023 11:07

84000500

3

"SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

03/03/2023 11:07

67061600

6

"DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

01/01/1970 00:00

2436694066

6

"Honoring MDD; IP provisioning mode = IPv6"

01/01/1970 00:00

84000100

3

"SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[removed];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"

03/03/2023 10:22

82000500

3

"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

03/03/2023 08:12

82000200

3

"No Ranging Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

01/01/1970 00:00

84000100

3

"SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[removed];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"

03/03/2023 08:18

2436694044

3

"Resetting the cable modem due to docsDevResetNow"

03/03/2023 08:15

82000500

3

"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

03/02/2023 17:07

82000500

3

"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

03/02/2023 16:23

82000500

3

"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

03/02/2023 14:48

82000500

3

"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

03/02/2023 14:26

82000500

3

"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

02/27/2023 20:37

82000500

3

"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

02/27/2023 20:18

82000500

3

"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

02/27/2023 20:11

82000500

3

"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

02/27/2023 17:30

82000500

3

"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

02/27/2023 17:15

82000500

3

"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

02/27/2023 17:01

82000500

3

"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

02/25/2023 21:21

82000500

3

"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"

02/22/2023 09:36

82000200

3

"No Ranging Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;"
       
plemans
Juggernaut
Forum|alt.badge.img+41
  • plemansJuggernaut
  • Juggernaut
  • 2274 replies
  • March 6, 2023

Only showed about a 1/3 of your downstream values but what I can see, you’re running a bit high on your power. And your logs show line issues. 

You can try putting an attenuator in the line to see if it drops your signal into spec ans see if it helps. If it doesn’t, the isp needs to check the line

Current setup: Netgear CM3000-->Netgear RBE973S-->2.5gig tp-link switch, Xfinity 2.4gig/350mbps
D
The Many
Forum|alt.badge.img
  • dscThe Many
  • Author
  • The Many
  • 2 replies
  • March 13, 2023

I appreciate your help and info.  After this issue happening for ~3 days, it seems to have “healed itself” the following week with not having to take any additional actions.  Not sure if it is going to return.  For now, it seems all good again.  Thanks again.

plemans
Juggernaut
Forum|alt.badge.img+41
  • plemansJuggernaut
  • Juggernaut
  • 2274 replies
  • March 14, 2023

Hope it stays stable for you!

Current setup: Netgear CM3000-->Netgear RBE973S-->2.5gig tp-link switch, Xfinity 2.4gig/350mbps

Most helpful members this week

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings