I have purchased a brand new SURFBoard SB8200. But lately i have been having several interruptions on my connectivity, where it seems the modem reboots itself. This is causing me a lot of issues I am running my own business, and multiple occasions this reboot, interrupted my zoom session (this is not professionals), it does not reflect well on my Company.
Please advise why this is becoming an issue.
Best answer by LoveMyLab
Thanks for sharing! From what I see, your signals levels all look good as do the Signal to Noise ratios. Arris would probably specify that your upstream power levels are low, but those numbers are consistent with many ISPs. You are not showing any uncorrected errors, which is encouraging.
The fact that you have two locked OFDM PLC channels down and an OFDMA up suggests you are on an upgraded service. By chance, are you with Cox and in the Phoenix or Los Vegas area? Some of the folks over on the Cox forums have noted challenges as Cox rolled out those upgrades. The upgrades have not occurred where I am.
At this point, I don’t have any helpful suggestions. Just for convenience, you might want to do a hard reset on your SB8200 now that your ISP has taken care of some signal issues. That’s the only way to clear the event log on an SB8200, and it will make it a little easier to see exactly what is happening currently. You’ll just want to go in and change the password after you do it since it will go back to the factory default of the Serial Number. I did that when I was doing some troubleshooting that all turned out to be temporary CMTS errors.
+19What do you see in the Event Log when this happens? It can be caused by the ISP. If so, it typically requires reaching out and having them reprovision the modem.
How are your signal and signal to noise levels on the Status page?
With a little more information, some helpful suggestions may be possible.
+41I’d agree with
Thank you
Current Setup:
SurFBoard8200 → PFSense FW → Cisco Switch 2950
As a side Note: Recently about a week or so, because of losing connection's persistent i called my ISP and after testing they found out that there are some noises and errors and they fixed. However, it seems i continue to get these issues.
Here is the logs from Event Log
I see some sync and discover failures during the time when the device was rebooted, I really appreciate any pointer.
30/9/2023
13:15:29 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
30/9/2023
13:15:34 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
30/9/2023
13:15:39 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
30/9/2023
13:16:26 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
30/9/2023
13:17:01 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
30/9/2023
13:17:04 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
30/9/2023
14:22:45 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
30/9/2023
14:22:50 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
30/9/2023
14:22:52 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
30/9/2023
14:52:39 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
30/9/2023
14:52:44 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
30/9/2023
15:15:40 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
30/9/2023
15:15:49 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
30/9/2023
15:23:47 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
30/9/2023
15:23:53 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
30/9/2023
15:23:58 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
30/9/2023
16:58:53 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
30/9/2023
16:58:58 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
1/10/2023
15:44:57 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
1/10/2023
15:45:00 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
1/10/2023
15:45:31 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
1/10/2023
15:45:36 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
1/10/2023
15:45:51 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
1/10/2023
15:46:04 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
1/10/2023
17:04:07 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
1/10/2023
17:04:13 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
1/10/2023
17:05:12 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
1/10/2023
17:05:12 3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
1/10/2023
17:05:25 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
1/10/2023
17:05:25 3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
1/10/2023
17:05:45 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
1/10/2023
17:05:45 3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
1/10/2023
17:06:05 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
1/10/2023
17:06:05 3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
1/10/2023
17:06:25 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
1/10/2023
17:06:25 3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
31/12/1969
19:01:37 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
31/12/1969
19:01:51 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
31/12/1969
19:01:56 3 UCD invalid or channel unusable;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
1/10/2023
17:09:40 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
1/10/2023
17:09:44 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
1/10/2023
17:09:46 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
4/10/2023
01:23:08 3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
4/10/2023
01:23:18 3 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
4/10/2023
01:23:28 3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
4/10/2023
01:23:38 3 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
4/10/2023
01:23:48 3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
4/10/2023
01:23:59 3 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
4/10/2023
01:24:08 3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
4/10/2023
01:24:34 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
4/10/2023
01:24:47 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
4/10/2023
01:25:00 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
4/10/2023
01:25:49 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
4/10/2023
01:26:02 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
4/10/2023
01:26:56 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
4/10/2023
01:28:30 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
4/10/2023
01:28:43 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
4/10/2023
01:54:53 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
4/10/2023
01:54:53 3 SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
4/10/2023
02:05:02 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
4/10/2023
02:06:44 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
4/10/2023
02:08:38 3 DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
4/10/2023
02:16:24 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
4/10/2023
02:16:31 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
4/10/2023
02:16:49 3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
4/10/2023
02:17:19 3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
4/10/2023
02:20:04 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
4/10/2023
02:23:29 3 DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
4/10/2023
02:24:18 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
4/10/2023
02:24:35 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
4/10/2023
02:25:05 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
4/10/2023
02:26:05 3 DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
31/12/1969
19:00:24 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
31/12/1969
19:00:25 3 UCD invalid or channel unusable;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
31/12/1969
19:00:42 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
5/10/2023
11:32:58 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
5/10/2023
11:33:03 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
31/12/1969
19:00:23 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
31/12/1969
19:00:26 3 UCD invalid or channel unusable;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
31/12/1969
19:00:30 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
31/12/1969
19:00:39 6 Honoring MDD; IP provisioning mode = IPv4
31/12/1969
19:00:41 5 DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
5/10/2023
21:55:17 6 TLV-11 - unrecognized OID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
5/10/2023
21:55:34 3 REG RSP not received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
5/10/2023
21:55:35 6 DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
5/10/2023
21:55:36 6 DS profile assignment change. DS Chan ID: 33; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
5/10/2023
21:55:42 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
5/10/2023
21:55:42 5 RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
5/10/2023
21:55:42 5 Dynamic Range Window violation
5/10/2023
21:55:42 5 RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
5/10/2023
21:55:42 5 Dynamic Range Window violation
5/10/2023
21:55:42 5 RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
5/10/2023
21:55:42 5 Dynamic Range Window violation
5/10/2023
21:55:45 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
5/10/2023
21:55:45 5 RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
5/10/2023
21:55:45 5 Dynamic Range Window violation
5/10/2023
21:56:45 6 US profile assignment change. US Chan ID: 8; Previous Profile: 13; New Profile: 9 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
6/10/2023
10:12:24 6 US profile assignment change. US Chan ID: 8; Previous Profile: 9 13; New Profile: 10 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
6/10/2023
10:13:56 6 US profile assignment change. US Chan ID: 8; Previous Profile: 10 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
6/10/2023
10:57:47 6 US profile assignment change. US Chan ID: 8; Previous Profile: 11 13; New Profile: 9 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
+19Thanks for sharing!
Can you show us what your current upstream and downstream levels are from the Status screen? The event log shows a wide range of communication errors, and we can see the modem restarting after a series of T3 timeouts. I suspect you still have some signal issues. The Status screen will help us ensure the appropriate channels are locked, as well as provide insight into the uncorrected error rates.
Downstream Bonded Channels
Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables
21 Locked QAM256 855000000 Hz 6 dBmV 41 dB 0 0
1 Locked QAM256 735000000 Hz 5 dBmV 40 dB 0 0
2 Locked QAM256 741000000 Hz 6 dBmV 41 dB 0 0
3 Locked QAM256 747000000 Hz 5 dBmV 40 dB 0 0
4 Locked QAM256 753000000 Hz 6 dBmV 40 dB 0 0
5 Locked QAM256 759000000 Hz 6 dBmV 41 dB 0 0
6 Locked QAM256 765000000 Hz 6 dBmV 40 dB 0 0
7 Locked QAM256 771000000 Hz 5 dBmV 40 dB 0 0
8 Locked QAM256 777000000 Hz 6 dBmV 41 dB 0 0
9 Locked QAM256 783000000 Hz 6 dBmV 41 dB 0 0
10 Locked QAM256 789000000 Hz 5 dBmV 40 dB 0 0
11 Locked QAM256 795000000 Hz 6 dBmV 41 dB 0 0
12 Locked QAM256 801000000 Hz 6 dBmV 41 dB 0 0
13 Locked QAM256 807000000 Hz 5 dBmV 40 dB 0 0
14 Locked QAM256 813000000 Hz 6 dBmV 40 dB 0 0
15 Locked QAM256 819000000 Hz 6 dBmV 41 dB 0 0
16 Locked QAM256 825000000 Hz 5 dBmV 40 dB 0 0
17 Locked QAM256 831000000 Hz 5 dBmV 40 dB 0 0
18 Locked QAM256 837000000 Hz 6 dBmV 41 dB 0 0
19 Locked QAM256 843000000 Hz 6 dBmV 41 dB 0 0
20 Locked QAM256 849000000 Hz 5 dBmV 40 dB 0 0
22 Locked QAM256 861000000 Hz 6 dBmV 41 dB 0 0
23 Locked QAM256 867000000 Hz 5 dBmV 41 dB 0 0
24 Locked QAM256 873000000 Hz 6 dBmV 41 dB 0 0
41 Locked QAM256 213000000 Hz 7 dBmV 43 dB 0 0
42 Locked QAM256 219000000 Hz 9 dBmV 44 dB 0 0
43 Locked QAM256 225000000 Hz 7 dBmV 43 dB 0 0
44 Locked QAM256 231000000 Hz 7 dBmV 43 dB 0 0
45 Locked QAM256 237000000 Hz 9 dBmV 44 dB 0 0
46 Locked QAM256 243000000 Hz 7 dBmV 43 dB 0 0
47 Locked QAM256 249000000 Hz 7 dBmV 42 dB 0 0
48 Locked QAM256 255000000 Hz 8 dBmV 43 dB 0 0
159 Locked OFDM PLC 300000000 Hz 8 dBmV 43 dB 458258729 0
160 Locked OFDM PLC 918000000 Hz 7 dBmV 41 dB 530340571 0Here is the Upstream
Upstream Bonded Channels
Channel ID Lock Status US Channel Type Frequency Width Power
1 Locked SC-QAM 17400000 Hz 6400000 39.0 dBmV
2 Locked SC-QAM 23900000 Hz 6400000 38.5 dBmV
3 Locked SC-QAM 30300000 Hz 6400000 38.8 dBmV
4 Locked SC-QAM 36700000 Hz 6400000 39.3 dBmV
6 Locked OFDMA 36800000 Hz 44000000 34.2 dBmV
+19Thanks for sharing! From what I see, your signals levels all look good as do the Signal to Noise ratios. Arris would probably specify that your upstream power levels are low, but those numbers are consistent with many ISPs. You are not showing any uncorrected errors, which is encouraging.
The fact that you have two locked OFDM PLC channels down and an OFDMA up suggests you are on an upgraded service. By chance, are you with Cox and in the Phoenix or Los Vegas area? Some of the folks over on the Cox forums have noted challenges as Cox rolled out those upgrades. The upgrades have not occurred where I am.
At this point, I don’t have any helpful suggestions. Just for convenience, you might want to do a hard reset on your SB8200 now that your ISP has taken care of some signal issues. That’s the only way to clear the event log on an SB8200, and it will make it a little easier to see exactly what is happening currently. You’ll just want to go in and change the password after you do it since it will go back to the factory default of the Serial Number. I did that when I was doing some troubleshooting that all turned out to be temporary CMTS errors.
I will take care of your recommendations, I do appreciate for all your help.
Thanks,
I have had countless issues for quite some time with cox in the Scottsdale area where the SB8200 would reset 8-10 times a day and it would take 1-3 hours to get back online. (I should mention I have unlimited gigablast service using upwards of 2TB of data a month.).
I replaced all the hard line connectors and tested the hard wire connection from the D-mark (outside box where cox comes in) to the connection to the modem. I still had issues after this so I logged into the modem and activated link Aggregation, the system will reboot after this.
It's only been a week and I've only had to reset the modem one time but it was Back up in minutes.
Ethernet Installation for Link Aggregation
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.