New Contributor
•
1 Message
Arris SB8200 Firmware Update / Download Speed Issue
Hello - I activated a new SB8200 today with Cox.
In reviewing the firmware, it appears that the modem does not have the latest firmware update applied. That said, I also understand that Cox controls which firmware is actually applied to the device once it is on their network. So, I'm looking for the answer to a couple of quesitons:
- What the the latest approved firmware version for the Arris SB8200 modem on Cox's network? Mine is running AB01.01.009.27_081619_183.0A.NSH
- If a more recent firmware has been approved, how long does my modem have to be online before it will pick up the latest firmware and apply it?
I bought this new modem (along with a brand new TP-Link AX6000 router) in an attempt to improve my download speed. However, I'm finding that the speed is not improved any from the previous setup (which was the Cox-provided Panoramic WiFi modem). I am a Gigablast customer and this modem is listed as "Gigablast compatible". I'm getting around 200-300Mbps down on average.
In reviewing the modem's event log, I also notice several "SYNC Timing Synchronization failure - Loss of Sync" messages. Not sure if that's relevant or not to this issue.
Date Time | Event ID | Event Level | Description |
---|---|---|---|
09/08/2020 12:29 | 84000500 | 3 | "SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=<REDACTED>;CMTS-MAC=<REDACTED>;CM-QOS=1.1;CM-VER=3.1;" |
09/08/2020 12:17 | 67061600 | 6 | "DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=<REDACTED>;CMTS-MAC=<REDACTED>;CM-QOS=1.1;CM-VER=3.1;" |
09/08/2020 12:17 | 73040100 | 6 | "TLV-11 - unrecognized OID;CM-MAC=<REDACTED>;CMTS-MAC=<REDACTED>;CM-QOS=1.1;CM-VER=3.1;" |
09/08/2020 12:17 | 68000300 | 5 | "DHCP WARNING - Non-critical field invalid in response ;CM-MAC=<REDACTED>;CMTS-MAC=<REDACTED>;CM-QOS=1.1;CM-VER=3.1;" |
01/01/1970 00:01 | 2436694066 | 6 | "Honoring MDD; IP provisioning mode = IPv4" |
01/01/1970 00:01 | 82000200 | 3 | "No Ranging Response received - T3 time-out;CM-MAC=<REDACTED>;CMTS-MAC=<REDACTED>;CM-QOS=1.1;CM-VER=3.1;" |
01/01/1970 00:01 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=<REDACTED>;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" |
01/01/1970 00:00 | 84020200 | 5 | "Lost MDD Timeout;CM-MAC=<REDACTED>;CMTS-MAC=00:00:00:00:00:00;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=<REDACTED>;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" |
I'm also not sure what normal signal levels are for the service/modem, so hard to know if these are within range or not:
Startup Procedure | ||
---|---|---|
Procedure | Status | Comment |
Acquire Downstream Channel | 789000000 Hz | Locked |
Connectivity State | OK | Operational |
Boot State | OK | Operational |
Configuration File | OK | |
Security | Enabled | BPI+ |
DOCSIS Network Access Enabled | Allowed |
Downstream Bonded Channels | |||||||
---|---|---|---|---|---|---|---|
Channel ID | Lock Status | Modulation | Frequency | Power | SNR/MER | Corrected | Uncorrectables |
2 | Locked | QAM256 | 789000000 Hz | 1.0 dBmV | 41.0 dB | 0 | 0 |
1 | Locked | QAM256 | 783000000 Hz | 1.2 dBmV | 41.3 dB | 0 | 0 |
3 | Locked | QAM256 | 795000000 Hz | 1.3 dBmV | 41.2 dB | 0 | 0 |
4 | Locked | QAM256 | 801000000 Hz | 1.5 dBmV | 41.3 dB | 0 | 0 |
9 | Locked | QAM256 | 831000000 Hz | -1.2 dBmV | 40.1 dB | 0 | 0 |
10 | Locked | QAM256 | 837000000 Hz | -1.1 dBmV | 40.0 dB | 0 | 0 |
11 | Locked | QAM256 | 843000000 Hz | -1.0 dBmV | 40.1 dB | 0 | 0 |
12 | Locked | QAM256 | 849000000 Hz | -0.8 dBmV | 40.3 dB | 0 | 0 |
17 | Locked | QAM256 | 879000000 Hz | -1.4 dBmV | 40.0 dB | 0 | 0 |
18 | Locked | QAM256 | 885000000 Hz | -1.9 dBmV | 39.8 dB | 0 | 0 |
19 | Locked | QAM256 | 891000000 Hz | -1.6 dBmV | 40.0 dB | 0 | 0 |
20 | Locked | QAM256 | 897000000 Hz | -0.9 dBmV | 40.4 dB | 0 | 0 |
21 | Locked | QAM256 | 903000000 Hz | -0.6 dBmV | 40.5 dB | 0 | 0 |
22 | Locked | QAM256 | 909000000 Hz | -1.1 dBmV | 40.4 dB | 0 | 0 |
25 | Locked | QAM256 | 927000000 Hz | -0.5 dBmV | 40.8 dB | 0 | 0 |
26 | Locked | QAM256 | 933000000 Hz | -0.8 dBmV | 40.8 dB | 0 | 0 |
27 | Locked | QAM256 | 939000000 Hz | -0.6 dBmV | 41.0 dB | 0 | 0 |
28 | Locked | QAM256 | 945000000 Hz | -0.8 dBmV | 40.9 dB | 0 | 0 |
29 | Locked | QAM256 | 951000000 Hz | -1.6 dBmV | 40.6 dB | 0 | 0 |
30 | Locked | QAM256 | 957000000 Hz | -2.0 dBmV | 40.5 dB | 0 | 0 |
33 | Locked | QAM256 | 357000000 Hz | 3.0 dBmV | 41.4 dB | 0 | 0 |
34 | Locked | QAM256 | 363000000 Hz | 2.4 dBmV | 41.5 dB | 0 | 0 |
35 | Locked | QAM256 | 369000000 Hz | 2.4 dBmV | 41.6 dB | 0 | 0 |
36 | Locked | QAM256 | 375000000 Hz | 3.1 dBmV | 41.7 dB | 0 | 0 |
37 | Locked | QAM256 | 381000000 Hz | 3.2 dBmV | 41.9 dB | 0 | 0 |
38 | Locked | QAM256 | 387000000 Hz | 2.7 dBmV | 41.7 dB | 0 | 0 |
41 | Locked | QAM256 | 405000000 Hz | 2.8 dBmV | 41.7 dB | 0 | 0 |
42 | Locked | QAM256 | 411000000 Hz | 2.6 dBmV | 41.7 dB | 0 | 0 |
43 | Locked | QAM256 | 417000000 Hz | 2.8 dBmV | 41.9 dB | 0 | 0 |
44 | Locked | QAM256 | 423000000 Hz | 3.3 dBmV | 42.0 dB | 0 | 0 |
45 | Locked | QAM256 | 429000000 Hz | 3.6 dBmV | 42.1 dB | 0 | 0 |
46 | Locked | QAM256 | 435000000 Hz | 3.6 dBmV | 42.1 dB | 0 | 0 |
159 | Locked | Other | 300000000 Hz | 2.8 dBmV | 41.5 dB | 302893000 | 0 |
Upstream Bonded Channels | ||||||
---|---|---|---|---|---|---|
Channel | Channel ID | Lock Status | US Channel Type | Frequency | Width | Power |
1 | 4 | Locked | SC-QAM Upstream | 38600000 Hz | 6400000 Hz | 44.0 dBmV |
2 | 1 | Locked | SC-QAM Upstream | 19300000 Hz | 6400000 Hz | 43.0 dBmV |
3 | 2 | Locked | SC-QAM Upstream | 25800000 Hz | 6400000 Hz | 43.0 dBmV |
4 | 3 | Locked | SC-QAM Upstream | 32200000 Hz | 6400000 Hz | 44.0 dBmV |
I realize that there's no guarantee as to speeds, but I've literally never gotten anywhere close to "Gigablast" speeds. That said, I'd be happy to consistently get between 500-700 down. Am I crazy to have those types of expectations considering what I pay for this service?
Thanks in advance for all the help!
V/R
Paul S
Edmond, OK
Dave9
Contributor III
•
251 Messages
5 years ago
I have the same firmware as you and get 940/35 easily. It's not a firmware problem. Cox will push out a new firmware when they're ready, Signals look very good. Post at least 24 hours worth of logs without resetting your modem during that time. The excerpt you posted is too short to see if there are any intermittent problems.
0
0