Visitor
•
7 Messages
Connection Drops on DOCSIS 3.1 SB8200
Back in December I upgraded our internet to 900Mbps. With it needed a router that can provide the full bandwidth with room for future upgrades to Gig+ tiers. Coming from a SB6190 which honestly didn't have much problems with. Initially started with the MB8611 modem. At first the connection was great even though setup had to be done over the phone instead of the app. That same night connection dropped a couple times, but it reconnected. As days went on more drops with some happening several times an hour. Read forums after forums and took this back for an SB8200. Same story initial connection was fine. Next day drops continued. Had a tech come out. He replaced the line from the pole to the house, replaced the end connections on some of the cables even to the tv box (was not having issue with that) and switched the powered splitter the previous home owners had installed to a two-way splitter. Initial connection was fine. Next day took back the 8200 for the MB8611. Activated and the following day drops drops drops. Went back to the 8200. Would be fine for first couple hours than random drops. Replaced back to 6190 did not have issues but was not getting full bandwidth I was paying for. Watching the modem whenever it switched to DOCSIS 3.1 that's when issues seemed to come up. Weeks ago I installed a powered splitter that seemed to help and reduce the connection drops but they are still occurring. This week it has gotten so much worse. Reading posts on here and on arris and motorola forums it seems for of a provisioning problem on xfinity that is to blame. Reading 2+ year old posts and this is still an issue. Attached are more recent power levels and event logs. Not sure if it is even worth trying the CM2000 if it's going to be the same outcome.
Date Time Event ID Event Level Description
02/27/2022 15:57 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; OFDM/OFDMA Profile ID: 0 1 2 3.;;CM-QOS=1.1;CM-VER=3.1;"
02/27/2022 15:56 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; ; OFDM/OFDMA Profile ID: 0.;;CM-QOS=1.1;CM-VER=3.1;"
02/27/2022 15:56 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; ; OFDM/OFDMA Profile ID: 0 1 2 3.;;CM-QOS=1.1;CM-VER=3.1;"
02/27/2022 15:56 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; OFDM/OFDMA Profile ID: 1.CM-QOS=1.1;CM-VER=3.1;"
02/27/2022 15:56 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; ; OFDM/OFDMA Profile ID: 0 1 2 3.;;CM-QOS=1.1;CM-VER=3.1;"
02/27/2022 15:56 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; ; OFDM/OFDMA Profile ID: 0.;;CM-QOS=1.1;CM-VER=3.1;"
02/27/2022 15:55 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; ; OFDM/OFDMA Profile ID: 0 1 2 3.;;CM-QOS=1.1;CM-VER=3.1;"
02/27/2022 15:54 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; OFDM/OFDMA Profile ID: 1 2 3.;;CM-QOS=1.1;CM-VER=3.1;"
02/27/2022 15:54 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; ; OFDM/OFDMA Profile ID: 0 1.;;CM-QOS=1.1;CM-VER=3.1;"
02/27/2022 15:52 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; ; OFDM/OFDMA Profile ID: 1 2 3.;;CM-QOS=1.1;CM-VER=3.1;"
02/27/2022 15:51 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; ; OFDM/OFDMA Profile ID: 0 1.;;CM-QOS=1.1;CM-VER=3.1;"
02/27/2022 15:51 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; ; OFDM/OFDMA Profile ID: 0.;;CM-QOS=1.1;CM-VER=3.1;"
02/27/2022 15:51 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; ; OFDM/OFDMA Profile ID: 0 1 2 3.;;CM-QOS=1.1;CM-VER=3.1;"
02/27/2022 15:50 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; ; OFDM/OFDMA Profile ID: 1 2 3.;;CM-QOS=1.1;CM-VER=3.1;"
02/27/2022 15:48 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; ; OFDM/OFDMA Profile ID: 1.;;CM-QOS=1.1;CM-VER=3.1;"
02/27/2022 15:47 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; OFDM/OFDMA Profile ID: 1 2 3.;;CM-QOS=1.1;CM-VER=3.1;"
02/27/2022 15:44 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; ; OFDM/OFDMA Profile ID: 2 3.;;CM-QOS=1.1;CM-VER=3.1;"
02/27/2022 15:44 67061600 6 "DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;;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 82000200 3 "No Ranging Response received - T3 time-out;C;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-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:00 82000200 3 "No Ranging Response received - T3 time-out;;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-QOS=1.1;CM-VER=3.1;"
02/26/2022 15:20 82000200 3 "No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 15:14 82000200 3 "No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 15:11 82000200 3 "No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 14:57 82000200 3 "No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 14:39 82000200 3 "No Ranging Response received - T3 time-out;C;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 14:34 82000200 3 "No Ranging Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 14:32 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 14:27 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 14:26 82000200 3 "No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 13:32 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 13:30 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 13:19 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 13:10 82000200 3 "No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 13:06 82000200 3 "No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 11:47 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 11:35 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;C;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 11:34 82000200 3 "No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 08:57 82000400 3 "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 08:53 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;d;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 00:47 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/25/2022 14:04 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;"
02/25/2022 14:04 82000200 3 "No Ranging Response received - T3 time-out;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-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:00 82000200 3 "No Ranging Response received - T3 time-out;;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-QOS=1.1;CM-VER=3.1;"
02/23/2022 02:56 2436694044 3 "Resetting the cable modem due to docsDevResetNow"
01/01/1970 00:00 82000200 3 "No Ranging Response received - T3 time-out;;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-QOS=1.1;CM-VER=3.1;"
02/22/2022 18:25 82000200 3 "No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/22/2022 17:51 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/22/2022 17:50 82000200 3 "No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/22/2022 17:49 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/22/2022 17:48 82000200 3 "No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/22/2022 17:39 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/22/2022 17:30 82000200 3 "No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/22/2022 17:27 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/22/2022 17:26 82000200 3 "No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/22/2022 17:17 82000200 3 "No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/22/2022 16:31 82000200 3 "No Ranging Response received - T3 time-out;d;CM-QOS=1.1;CM-VER=3.1;"
02/22/2022 15:35 82000200 3 "No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/22/2022 15:33 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;"
02/22/2022 14:56 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;"
02/27/2022 15:57 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; OFDM/OFDMA Profile ID: 0 1 2 3.;;CM-QOS=1.1;CM-VER=3.1;"
02/27/2022 15:56 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; ; OFDM/OFDMA Profile ID: 0.;;CM-QOS=1.1;CM-VER=3.1;"
02/27/2022 15:56 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; ; OFDM/OFDMA Profile ID: 0 1 2 3.;;CM-QOS=1.1;CM-VER=3.1;"
02/27/2022 15:56 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; OFDM/OFDMA Profile ID: 1.CM-QOS=1.1;CM-VER=3.1;"
02/27/2022 15:56 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; ; OFDM/OFDMA Profile ID: 0 1 2 3.;;CM-QOS=1.1;CM-VER=3.1;"
02/27/2022 15:56 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; ; OFDM/OFDMA Profile ID: 0.;;CM-QOS=1.1;CM-VER=3.1;"
02/27/2022 15:55 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; ; OFDM/OFDMA Profile ID: 0 1 2 3.;;CM-QOS=1.1;CM-VER=3.1;"
02/27/2022 15:54 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; OFDM/OFDMA Profile ID: 1 2 3.;;CM-QOS=1.1;CM-VER=3.1;"
02/27/2022 15:54 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; ; OFDM/OFDMA Profile ID: 0 1.;;CM-QOS=1.1;CM-VER=3.1;"
02/27/2022 15:52 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; ; OFDM/OFDMA Profile ID: 1 2 3.;;CM-QOS=1.1;CM-VER=3.1;"
02/27/2022 15:51 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; ; OFDM/OFDMA Profile ID: 0 1.;;CM-QOS=1.1;CM-VER=3.1;"
02/27/2022 15:51 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; ; OFDM/OFDMA Profile ID: 0.;;CM-QOS=1.1;CM-VER=3.1;"
02/27/2022 15:51 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; ; OFDM/OFDMA Profile ID: 0 1 2 3.;;CM-QOS=1.1;CM-VER=3.1;"
02/27/2022 15:50 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; ; OFDM/OFDMA Profile ID: 1 2 3.;;CM-QOS=1.1;CM-VER=3.1;"
02/27/2022 15:48 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; ; OFDM/OFDMA Profile ID: 1.;;CM-QOS=1.1;CM-VER=3.1;"
02/27/2022 15:47 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; OFDM/OFDMA Profile ID: 1 2 3.;;CM-QOS=1.1;CM-VER=3.1;"
02/27/2022 15:44 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; ; OFDM/OFDMA Profile ID: 2 3.;;CM-QOS=1.1;CM-VER=3.1;"
02/27/2022 15:44 67061600 6 "DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;;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 82000200 3 "No Ranging Response received - T3 time-out;C;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-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:00 82000200 3 "No Ranging Response received - T3 time-out;;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-QOS=1.1;CM-VER=3.1;"
02/26/2022 15:20 82000200 3 "No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 15:14 82000200 3 "No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 15:11 82000200 3 "No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 14:57 82000200 3 "No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 14:39 82000200 3 "No Ranging Response received - T3 time-out;C;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 14:34 82000200 3 "No Ranging Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 14:32 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 14:27 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 14:26 82000200 3 "No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 13:32 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 13:30 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 13:19 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 13:10 82000200 3 "No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 13:06 82000200 3 "No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 11:47 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 11:35 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;C;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 11:34 82000200 3 "No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 08:57 82000400 3 "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 08:53 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;d;CM-QOS=1.1;CM-VER=3.1;"
02/26/2022 00:47 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/25/2022 14:04 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;"
02/25/2022 14:04 82000200 3 "No Ranging Response received - T3 time-out;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-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:00 82000200 3 "No Ranging Response received - T3 time-out;;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-QOS=1.1;CM-VER=3.1;"
02/23/2022 02:56 2436694044 3 "Resetting the cable modem due to docsDevResetNow"
01/01/1970 00:00 82000200 3 "No Ranging Response received - T3 time-out;;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-QOS=1.1;CM-VER=3.1;"
02/22/2022 18:25 82000200 3 "No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/22/2022 17:51 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/22/2022 17:50 82000200 3 "No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/22/2022 17:49 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/22/2022 17:48 82000200 3 "No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/22/2022 17:39 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/22/2022 17:30 82000200 3 "No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/22/2022 17:27 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/22/2022 17:26 82000200 3 "No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/22/2022 17:17 82000200 3 "No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/22/2022 16:31 82000200 3 "No Ranging Response received - T3 time-out;d;CM-QOS=1.1;CM-VER=3.1;"
02/22/2022 15:35 82000200 3 "No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;"
02/22/2022 15:33 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;"
02/22/2022 14:56 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;"
No Responses!