Welcome to Comcast Help & Support Forums
Find solutions, share knowledge, and get answers from customers and experts

New to the Community? Start here.

5,760,594

members

43

online now

1,916,609

discussions

Back to Top

Critical errors on new Arris SB8200

New Poster

Critical errors on new Arris SB8200

Experiencing the following issues with a brand new Arris SB8200.  Any ideas?  Only one, high quality splitter upstream of modem (one half to TV, other to modem).  Good quality cables, tight connections.  A relatively new pole to house cable...

 

 

 

Time Priority Description
12-7-2017, 7:58:18 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-7-2017, 7:28:56 Critical(3) "SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-7-2017, 7:22:0 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-6-2017, 20:9:41 Critical(3) "SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-6-2017, 20:7:23 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-6-2017, 19:21:34 Critical(3) "SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-6-2017, 19:21:33 Critical(3) "SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-6-2017, 19:21:31 Critical(3) "SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-6-2017, 19:21:31 Critical(3) "SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-6-2017, 19:10:49 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-6-2017, 19:9:12 Critical(3) "SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-6-2017, 18:53:29 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-6-2017, 17:14:37 Critical(3) "SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-6-2017, 17:14:31 Critical(3) "SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-6-2017, 17:14:30 Critical(3) "SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-6-2017, 17:10:18 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-6-2017, 16:23:11 Critical(3) "SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-6-2017, 16:13:36 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-6-2017, 11:50:20 Critical(3) "SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-6-2017, 11:49:48 Critical(3) "SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-6-2017, 11:49:48 Critical(3) "SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-6-2017, 11:37:16 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-6-2017, 11:13:41 Critical(3) "SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-6-2017, 11:13:41 Critical(3) "SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-6-2017, 11:12:18 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-6-2017, 10:57:54 Critical(3) "SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-6-2017, 10:57:53 Critical(3) "SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-6-2017, 10:36:10 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-6-2017, 8:20:18 Critical(3) "SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-6-2017, 8:13:44 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-6-2017, 6:45:54 Critical(3) "SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-6-2017, 6:45:53 Critical(3) "SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-6-2017, 6:40:50 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-6-2017, 5:42:29 Critical(3) "SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-6-2017, 5:42:29 Critical(3) "SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-6-2017, 5:33:41 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-6-2017, 3:21:43 Critical(3) "SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-6-2017, 3:21:43 Critical(3) "SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"
12-6-2017, 3:20:3 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:2a:62:09;CMTS-MAC=00:01:5c:79:b8:5f;CM-QOS=1.1;CM-VER=3.1;"

 

 

Here's the status

 

Downstream Bonded Channels
Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables
1 Locked QAM256 489000000 Hz 4.4 dBmV 38.8 dB 12 0
2 Locked QAM256 495000000 Hz 4.3 dBmV 38.8 dB 7 0
3 Locked QAM256 507000000 Hz 4.1 dBmV 38.7 dB 10 0
4 Locked QAM256 513000000 Hz 4.3 dBmV 38.9 dB 24 0
5 Locked QAM256 519000000 Hz 4.5 dBmV 38.8 dB 0 0
6 Locked QAM256 525000000 Hz 4.4 dBmV 38.8 dB 6 0
7 Locked QAM256 531000000 Hz 4.5 dBmV 38.7 dB 16 0
8 Locked QAM256 537000000 Hz 4.6 dBmV 38.7 dB 26 0
9 Locked QAM256 543000000 Hz 4.8 dBmV 38.8 dB 29 0
10 Locked QAM256 549000000 Hz 4.8 dBmV 38.7 dB 5 0
11 Locked QAM256 555000000 Hz 4.9 dBmV 38.7 dB 6 0
12 Locked QAM256 561000000 Hz 5.0 dBmV 38.7 dB 0 0
13 Locked QAM256 567000000 Hz 4.9 dBmV 38.6 dB 25 0
14 Locked QAM256 573000000 Hz 5.1 dBmV 38.6 dB 4 0
15 Locked QAM256 579000000 Hz 5.2 dBmV 38.6 dB 16 0
16 Locked QAM256 585000000 Hz 5.3 dBmV 38.7 dB 4 0
17 Locked QAM256 591000000 Hz 5.2 dBmV 38.6 dB 5 0
18 Locked QAM256 597000000 Hz 5.2 dBmV 38.5 dB 0 0
19 Locked QAM256 603000000 Hz 5.1 dBmV 38.7 dB 4 0
20 Locked QAM256 609000000 Hz 5.0 dBmV 38.5 dB 0 0
21 Locked QAM256 615000000 Hz 4.8 dBmV 38.5 dB 0 0
22 Locked QAM256 621000000 Hz 4.7 dBmV 38.5 dB 0 0
23 Locked QAM256 627000000 Hz 4.6 dBmV 38.6 dB 0 0
24 Locked QAM256 633000000 Hz 4.7 dBmV 38.7 dB 0 0
26 Locked QAM256 639000000 Hz 4.7 dBmV 38.6 dB 0 0
27 Locked QAM256 645000000 Hz 4.9 dBmV 38.8 dB 22 0
28 Locked QAM256 651000000 Hz 4.9 dBmV 38.7 dB 0 0
29 Locked QAM256 657000000 Hz 5.0 dBmV 38.7 dB 0 0
30 Locked QAM256 663000000 Hz 5.2 dBmV 38.9 dB 0 0
31 Locked QAM256 669000000 Hz 5.4 dBmV 38.7 dB 0 0
25 Locked Other 720000000 Hz 8.1 dBmV 37.5 dB 1609771 41

 

 
Upstream Bonded Channels
Channel Channel ID Lock Status US Channel Type Frequency Width Power
1 14 Locked SC-QAM 29400000 Hz 6400000 Hz 38.3 dBmV
2 16 Locked SC-QAM 16600000 Hz 6400000 Hz 36.5 dBmV
3 13 Locked SC-QAM 35800000 Hz 6400000 Hz 39.0 dBmV
4 15 Locked SC-QAM 23000000 Hz 6400000 Hz 37.3 dBmV
Highlighted
Connection Expert

Re: Critical errors on new Arris SB8200

The stats as read at the modem level at that moment in time were o/k but there are three additional signal stats that can cause those errors which can't be read by the modem. They can only be read from their end by them polling the CMTS (Cable Modem Termination System) at the local headend facility.

They are the "Upstream Rx Power" (Upstream Receive Power Level), the "Upstream SNR Ch." (Upstream Signal To Noise Ratio), and the "Upstream ICFR" (In Channel Frequency Response). These are as equally important in diagnosing connectivity issues as are the modem's stats.

You can call in and ask what these figures are. The Upstream Receive Power Level should fall within the range of -2dB to +2dB with 0dB being in the middle and perfect.

The Upstream SNR should be least 31dB, and the higher it is the better.

The ICFR should be no higher than 2 dB.

You could have an intermittent noise ingress issue in only the upstream channel(s) / return path only somewhere.

They will be able to see whether or not everything is in the green zone and also see a history plot for the modem.





Community Icon
I am not a Comcast employee, I am a paying customer just like you!
I am an XFINITY Forum Expert and I am here to help. For information on the program click here.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark it as an accepted solution!solution Icon
Community Icon
I am not a Comcast employee. I am a paying customer just like you!
I am an XFINITY Forum Expert and I am here to help.
We ask that you post publicly so people with similar questions may benefit.
Was your question answered? Mark it as an accepted solution!solution Icon
Community Icon
I am not a Comcast employee.

Was your question answered?
Mark it as a solution!solution Icon

New Poster

Re: Critical errors on new Arris SB8200

Thanks EG.... trying to get someone at COmcast to talk to on this that doesn't want to just reboot the modem is a challenge.  I'm trying though Smiley Happy

Connection Expert

Re: Critical errors on new Arris SB8200

Ask for a tier 2 rep.




Community Icon
I am not a Comcast employee, I am a paying customer just like you!
I am an XFINITY Forum Expert and I am here to help. For information on the program click here.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark it as an accepted solution!solution Icon
Community Icon
I am not a Comcast employee. I am a paying customer just like you!
I am an XFINITY Forum Expert and I am here to help.
We ask that you post publicly so people with similar questions may benefit.
Was your question answered? Mark it as an accepted solution!solution Icon
Community Icon
I am not a Comcast employee.

Was your question answered?
Mark it as a solution!solution Icon

Connection Expert
Moved:

Re: Critical errors on new Arris SB8200

Connection Expert
Moved:

Re: Critical errors on new Arris SB8200