8 Messages
Internet connectivity issues
Hello,
I have been having issues with connecting to the internet for the past week or so and it is solved by rebooting my Arris SB8000 modem but the issue presents itself again throughout the day. I'm hoping to get some help from this community to fix the issue.
*CM MAC and the CMTS MAC details were removed for privacy.
Thank you in advance for you assistance!
Here are the details from my connection status:
The status listed show the connection state of the cable modem. They are used by your service provider to evaluate the operation of the cable modem.
Startup Procedure | ||
---|---|---|
Procedure | Status | Comment |
Acquire Downstream Channel | 555000000 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 |
25 | Locked | QAM256 | 555000000 Hz | 3.2 dBmV | 33.9 dB | 542193 | 0 |
1 | Locked | QAM256 | 393000000 Hz | 3.3 dBmV | 35.5 dB | 27120 | 0 |
2 | Locked | QAM256 | 399000000 Hz | 1.5 dBmV | 34.8 dB | 50638 | 0 |
3 | Locked | QAM256 | 405000000 Hz | 3.1 dBmV | 34.8 dB | 43425 | 0 |
4 | Locked | QAM256 | 411000000 Hz | 3.1 dBmV | 35.0 dB | 46965 | 0 |
5 | Locked | QAM256 | 417000000 Hz | 2.0 dBmV | 33.9 dB | 147040 | 0 |
6 | Locked | QAM256 | 423000000 Hz | 3.3 dBmV | 34.4 dB | 101849 | 0 |
7 | Locked | QAM256 | 429000000 Hz | 2.0 dBmV | 34.1 dB | 132855 | 0 |
8 | Locked | QAM256 | 435000000 Hz | 2.4 dBmV | 33.9 dB | 203272 | 0 |
9 | Locked | QAM256 | 453000000 Hz | 2.2 dBmV | 33.9 dB | 266282 | 0 |
10 | Locked | QAM256 | 459000000 Hz | 1.9 dBmV | 34.7 dB | 141865 | 0 |
11 | Locked | QAM256 | 465000000 Hz | 2.7 dBmV | 34.4 dB | 177525 | 0 |
12 | Locked | QAM256 | 471000000 Hz | 2.2 dBmV | 34.6 dB | 122312 | 0 |
13 | Locked | QAM256 | 477000000 Hz | 3.3 dBmV | 34.5 dB | 134573 | 0 |
14 | Locked | QAM256 | 483000000 Hz | 3.5 dBmV | 34.3 dB | 164117 | 0 |
15 | Locked | QAM256 | 489000000 Hz | 3.8 dBmV | 34.2 dB | 144693 | 0 |
16 | Locked | QAM256 | 495000000 Hz | 4.8 dBmV | 34.0 dB | 250233 | 0 |
17 | Locked | QAM256 | 507000000 Hz | 4.2 dBmV | 32.9 dB | 870708 | 0 |
18 | Locked | QAM256 | 513000000 Hz | 4.6 dBmV | 33.6 dB | 405626 | 0 |
19 | Locked | QAM256 | 519000000 Hz | 3.4 dBmV | 33.0 dB | 863589 | 0 |
20 | Locked | QAM256 | 525000000 Hz | 3.5 dBmV | 33.3 dB | 661573 | 0 |
21 | Locked | QAM256 | 531000000 Hz | 2.2 dBmV | 33.5 dB | 635910 | 0 |
22 | Locked | QAM256 | 537000000 Hz | 2.5 dBmV | 33.8 dB | 613861 | 0 |
23 | Locked | QAM256 | 543000000 Hz | 2.3 dBmV | 34.2 dB | 367061 | 0 |
24 | Locked | QAM256 | 549000000 Hz | 2.2 dBmV | 33.8 dB | 531212 | 0 |
26 | Locked | QAM256 | 561000000 Hz | 3.0 dBmV | 34.1 dB | 425555 | 0 |
27 | Locked | QAM256 | 567000000 Hz | 4.2 dBmV | 34.2 dB | 467899 | 0 |
28 | Locked | QAM256 | 573000000 Hz | 2.5 dBmV | 33.4 dB | 1003518 | 1 |
29 | Locked | QAM256 | 579000000 Hz | 3.7 dBmV | 33.8 dB | 580339 | 0 |
30 | Locked | QAM256 | 585000000 Hz | 2.8 dBmV | 32.8 dB | 1533846 | 3 |
31 | Locked | QAM256 | 591000000 Hz | 2.7 dBmV | 33.0 dB | 1601522 | 5 |
45 | Locked | Other | 690000000 Hz | 1.8 dBmV | 29.8 dB | 126503548 | 13606569 |
Upstream Bonded Channels | ||||||
---|---|---|---|---|---|---|
Channel | Channel ID | Lock Status | US Channel Type | Frequency | Width | Power |
1 | 6 | Locked | SC-QAM Upstream | 10400000 Hz | 3200000 Hz | 46.0 dBmV |
2 | 7 | Locked | SC-QAM Upstream | 16400000 Hz | 6400000 Hz | 45.0 dBmV |
3 | 8 | Locked | SC-QAM Upstream | 22800000 Hz | 6400000 Hz | 46.0 dBmV |
4 | 9 | Locked | SC-QAM Upstream | 29200000 Hz | 6400000 Hz | 47.0 dBmV |
5 | 10 | Locked | SC-QAM Upstream | 35600000 Hz | 6400000 Hz | 46.0 dBmV |
6 | 11 | Locked | SC-QAM Upstream | 39600000 Hz | 1600000 Hz | 45.0 dBmV |
Current System Time:Tue Aug 13 07:54:47 2024
Here are the details from my event log:
The table below contains the log of events that the SB8200 has detected. This log can be important to the service provider to help diagnose and correct problems, if any should occur.
Date Time | Event ID | Event Level | Description |
---|---|---|---|
08/13/2024 07:50 | 74010100 | 6 | "CM-STATUS message sent. Event Type Code: 16; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.; |
08/13/2024 07:50 | 74010100 | 6 | "CM-STATUS message sent. Event Type Code: 24; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.; |
08/13/2024 07:33 | 74010100 | 6 | "CM-STATUS message sent. Event Type Code: 16; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.; |
08/13/2024 07:33 | 67061600 | 6 | "DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.; |
01/01/1970 00:00 | 2436694066 | 6 | "Honoring MDD; IP provisioning mode = IPv6" |
01/01/1970 00:00 | 82000200 | 3 | "No Ranging Response received - T3 time-out; |
01/01/1970 00:00 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; |
01/01/1970 00:00 | 82000200 | 3 | "No Ranging Response received - T3 time-out; |
01/01/1970 00:00 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; |
08/10/2024 21:25 | 82000500 | 3 | "Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
08/10/2024 21:25 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; |
08/10/2024 21:25 | 82000600 | 3 | "Unicast Maintenance Ranging attempted - No response - Retries exhausted; |
08/10/2024 21:25 | 82000500 | 3 | "Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
08/10/2024 21:25 | 82000600 | 3 | "Unicast Maintenance Ranging attempted - No response - Retries exhausted; |
08/10/2024 21:25 | 82000500 | 3 | "Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
08/10/2024 21:25 | 82000600 | 3 | "Unicast Maintenance Ranging attempted - No response - Retries exhausted; |
08/10/2024 21:25 | 82000500 | 3 | "Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
08/10/2024 21:25 | 82000600 | 3 | "Unicast Maintenance Ranging attempted - No response - Retries exhausted; |
08/10/2024 21:25 | 82000500 | 3 | "Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
08/10/2024 21:25 | 82000600 | 3 | "Unicast Maintenance Ranging attempted - No response - Retries exhausted; |
08/10/2024 21:25 | 82000500 | 3 | "Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
08/10/2024 21:24 | 82000400 | 3 | "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
08/10/2024 21:24 | 82000500 | 3 | "Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
08/10/2024 21:24 | 73000200 | 3 | "REG RSP not received; |
08/10/2024 21:24 | 82000200 | 3 | "No Ranging Response received - T3 time-out; |
08/10/2024 21:24 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; |
08/10/2024 21:23 | 82000400 | 3 | "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
08/10/2024 21:23 | 73000200 | 3 | "REG RSP not received; |
08/10/2024 21:23 | 82000500 | 3 | "Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
08/10/2024 21:22 | 82000200 | 3 | "No Ranging Response received - T3 time-out; |
08/10/2024 21:22 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; |
08/10/2024 21:22 | 82000400 | 3 | "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
08/10/2024 21:22 | 68000600 | 3 | "TFTP failed - configuration file NOT FOUND; |
01/01/1970 00:02 | 82000500 | 3 | "Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
01/01/1970 00:02 | 82000200 | 3 | "No Ranging Response received - T3 time-out; |
01/01/1970 00:01 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; |
01/01/1970 00:00 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; |
08/10/2024 13:27 | 82000500 | 3 | "Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
08/10/2024 13:26 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; |
08/10/2024 13:26 | 82000400 | 3 | "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
08/10/2024 13:26 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; |
08/10/2024 13:26 | 82000400 | 3 | "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
08/10/2024 13:26 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; |
08/10/2024 13:26 | 82000400 | 3 | "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
08/10/2024 13:26 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; |
08/10/2024 13:24 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; |
08/10/2024 13:21 | 82000200 | 3 | "No Ranging Response received - T3 time-out; |
08/10/2024 13:21 | 84000500 | 3 | "SYNC Timing Synchronization failure - Loss of Sync; |
08/10/2024 13:21 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; |
08/10/2024 13:17 | 84000500 | 3 | "SYNC Timing Synchronization failure - Loss of Sync; |
EG
Expert
•
107.1K Messages
3 months ago
All of the downstream channels SNR values are too low / out of spec. It appears that there is spurious noise ingress leaking into the line(s) somwhere. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.
Here are some things that you can try to see if they apply but you may need a tech out to investigate and correct this one;
In an effort to try to obtain better connectivity, check to see if there are any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1002 MHz, bi-directional, and no gold colored garbage from Home Depot, Target, Wal-Mart, etc. Splitters should be swapped with known to be good / new ones to test.
Also check the coax cable for any damage such as cuts, nicks, abrasions, kinks, sharp bends, etc.
If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two-way splitter connected directly off of the drop from the street / pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.
Good luck with it !
(edited)
2
0
EG
Expert
•
107.1K Messages
3 months ago
You're welcome ! Everything is already in black and white.... Good luck !
(edited)
0
0
EG
Expert
•
107.1K Messages
3 months ago
@user_v93vc5 @XfinityBenjaminM
Please circle back here and post any possible solutions for the issue here in these open public forums so that all readers here may benefit from the exchange / info. This is in keeping with the spirit for which these public help forums were originally intended. Thank you.
1
0
user_v93vc5
8 Messages
3 months ago
A Comcast technician came out to the house this weekend and confirmed our signal was strong at the street side but was weak at the modem. After doing some investigative work, he determined the source of the issue where our home was connected to the street (source). Adjustments were made and all is well.
There was also a monster splitter that was likely put into place when we had triple play, which we no longer have, and this also strengthened our internet connection.
Case closed.
0
0
EG
Expert
•
107.1K Messages
3 months ago
Thanks for the update ! For curiosity, would you please post what the signal values look like now ? Thanks.
1
0
user_v93vc5
8 Messages
3 months ago
Here is an updated Connection log:
The status listed show the connection state of the cable modem. They are used by your service provider to evaluate the operation of the cable modem.
Current System Time: Mon Aug 19 14:07:29 2024
0
0
user_v93vc5
8 Messages
3 months ago
The table below contains the log of events that the SB8200 has detected. This log can be important to the service provider to help diagnose and correct problems, if any should occur.
0
0
EG
Expert
•
107.1K Messages
3 months ago
So the SNR's are a bit better but they are still on the low side. We'd like to see them even higher. Mine are at 43-44 dB. And there are a fair number of uncorrectable bit errors. Seems more work needs to be done. Good luck with it !
2
0
EG
Expert
•
107.1K Messages
3 months ago
It can't be fixed remotely. It requires boots on the ground. And bear in mind that if the premises facing techs can not find or fix a problem at your home, it is they who are responsible for escalating it up to their line / network / maintenance dept. techs. The problem may lie beyond your home in the local neighborhood infrastructure somewhere but it is their S.O.P. to start at the home. And if the problem is found to be on their side of the demarcation point, there will not be any charge.
1
0