Welcome to the Spectrum Community

Get answers, share solutions, help your community.

Start here

Intermittent Internet + Numerous Modem Errors

NitebeatNitebeat Posts: 1
edited August 31 in Connectivity Aug 27, 2020

Hi all! I'm in Staten Island and for the longest time, I've had intermittent internet service despite visits from just about everyone that works "tech" in Spectrum. After the last visit, my connection was up solid for about 2 weeks, then back to where it is now - up and down all day, every day. I'm posting what I see on my modem "event log" if anyone can comment on what they think might be happening to cause the poor service I receive. Thanks in advance for any and all help! BTW, I am using an Arris SB8200 modem and Asus RT-N66U router.

8-24-2020, 16:2:10Warning(5)"RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 8-24-2020, 15:41:57Notice(6)"CM-STATUS message sent. Event Type Code: 24; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 .;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 8-24-2020, 15:27:34Critical(3)"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 8-24-2020, 15:27:23Notice(6)"DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 .;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 8-24-2020, 15:27:16Notice(6)"TLV-11 - unrecognized OID;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 8-24-2020, 15:27:16Error(4)"Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 8-24-2020, 15:27:16Error(4)"Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 1-1-1970, 0:0:35Warning(5)"DHCP WARNING - Non-critical field invalid in response ;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 1-1-1970, 0:0:33Notice(6)"Honoring MDD; IP provisioning mode = IPv4" 1-1-1970, 0:0:30Critical(3)"No Ranging Response received - T3 time-out;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 1-1-1970, 0:0:18Critical(3)"SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" 8-24-2020, 15:26:21Critical(3)"Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 8-24-2020, 15:26:21Critical(3)"No Ranging Response received - T3 time-out;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 8-24-2020, 15:26:19Critical(3)"Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 8-24-2020, 15:26:19Critical(3)"No Ranging Response received - T3 time-out;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 8-24-2020, 15:26:19Critical(3)"Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 8-24-2020, 15:25:51Critical(3)"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 8-24-2020, 15:7:22Critical(3)"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 1-1-1970, 0:0:29Critical(3)"No Ranging Response received - T3 time-out;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 1-1-1970, 0:0:18Critical(3)"SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" 8-24-2020, 15:1:56Critical(3)"Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 8-24-2020, 15:1:56Critical(3)"No Ranging Response received - T3 time-out;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 8-24-2020, 15:1:55Critical(3)"Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 8-24-2020, 15:1:55Critical(3)"No Ranging Response received - T3 time-out;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 8-24-2020, 15:1:54Critical(3)"Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 8-24-2020, 15:1:26Critical(3)"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 1-1-1970, 0:0:38Critical(3)"No Ranging Response received - T3 time-out;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 1-1-1970, 0:0:18Critical(3)"SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" 8-24-2020, 14:34:54Critical(3)"Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 8-24-2020, 14:34:54Critical(3)"No Ranging Response received - T3 time-out;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 8-24-2020, 14:34:52Critical(3)"Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 8-24-2020, 14:34:24Critical(3)"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 1-1-1970, 0:0:37Critical(3)"No Ranging Response received - T3 time-out;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 1-1-1970, 0:0:18Critical(3)"SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" 8-24-2020, 14:29:40Critical(3)"Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 8-24-2020, 14:29:40Critical(3)"No Ranging Response received - T3 time-out;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 8-24-2020, 14:29:38Critical(3)"Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 8-24-2020, 14:29:10Critical(3)"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 1-1-1970, 0:0:33Critical(3)"No Ranging Response received - T3 time-out;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 1-1-1970, 0:0:18Critical(3)"SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" 8-24-2020, 14:16:44Critical(3)"Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 8-24-2020, 14:16:44Critical(3)"No Ranging Response received - T3 time-out;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 8-24-2020, 14:16:43Critical(3)"Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 8-24-2020, 14:16:42Critical(3)"No Ranging Response received - T3 time-out;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 8-24-2020, 14:16:42Critical(3)"Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 8-24-2020, 14:16:41Critical(3)"No Ranging Response received - T3 time-out;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 8-24-2020, 14:16:38Critical(3)"Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;" 8-24-2020, 14:16:14Critical(3)"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=50:95:51:a4:57:21;CMTS-MAC=00:17:10:88:a4:d9;CM-QOS=1.1;CM-VER=3.1;"8-24-2020, 13:4:54Critical(3)"Started Unicast Maintenance Ranging - No Response received - T3

operation of the cable modem. Startup Procedure Procedure Status Comment Acquire Downstream Channel 471000000 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 32 Locked QAM256 471000000 Hz 0.6 dBmV 39.6 dB 9 28 1 Locked QAM256 279000000 Hz 1.2 dBmV 39.5 dB 0 0 2 Locked QAM256 285000000 Hz 1.3 dBmV 39.3 dB 0 0 3 Locked QAM256 291000000 Hz 1.3 dBmV 39.3 dB 0 0 4 Locked QAM256 297000000 Hz 1.3 dBmV 39.0 dB 0 0 5 Locked QAM256 303000000 Hz 1.2 dBmV 39.3 dB 0 0 6 Locked QAM256 309000000 Hz 1.2 dBmV 39.5 dB 0 0 7 Locked QAM256 315000000 Hz 1.4 dBmV 39.3 dB 0 0 8 Locked QAM256 321000000 Hz 1.2 dBmV 39.3 dB 0 0 9 Locked QAM256 327000000 Hz 1.7 dBmV 39.5 dB 0 0 10 Locked QAM256 333000000 Hz 1.1 dBmV 38.6 dB 0 0 11 Locked QAM256 339000000 Hz 1.1 dBmV 34.8 dB 8034 1452 12 Locked QAM256 345000000 Hz 1.6 dBmV 34.7 dB 0 0 13 Locked QAM256 351000000 Hz 1.4 dBmV 38.8 dB 0 0 14 Locked QAM256 357000000 Hz 1.1 dBmV 38.8 dB 0 0 15 Locked QAM256 363000000 Hz 1.1 dBmV 39.0 dB 0 0 16 Locked QAM256 369000000 Hz 1.4 dBmV 39.5 dB 0 0 17 Locked QAM256 375000000 Hz 1.0 dBmV 39.3 dB 0 0 18 Locked QAM256 381000000 Hz 1.3 dBmV 39.5 dB 0 0 19 Locked QAM256 387000000 Hz 0.9 dBmV 39.2 dB 0 0 20 Locked QAM256 393000000 Hz 1.3 dBmV 39.4 dB 0 0 21 Locked QAM256 399000000 Hz 1.1 dBmV 39.4 dB 0 0 22 Locked QAM256 405000000 Hz 1.4 dBmV 39.7 dB 0 0 23 Locked QAM256 411000000 Hz 0.9 dBmV 39.4 dB 0 0 24 Locked QAM256 417000000 Hz 0.9 dBmV 39.6 dB 0 0 25 Locked QAM256 423000000 Hz 1.2 dBmV 39.7 dB 0 0 26 Locked QAM256 429000000 Hz 1.2 dBmV 39.7 dB 0 0 27 Locked QAM256 435000000 Hz 1.3 dBmV 39.0 dB 0 0 28 Locked QAM256 447000000 Hz 1.3 dBmV 39.9 dB 0 0 29 Locked QAM256 453000000 Hz 0.9 dBmV 39.7 dB 0 0 30 Locked QAM256 459000000 Hz 1.2 dBmV 40.0 dB 0 0 31 Locked QAM256 465000000 Hz 1.0 dBmV 39.9 dB 0 0 33 Locked Other 777000000 Hz 2.2 dBmV 37.2 dB 421638 0


Upstream Bonded Channels Channel Channel ID Lock Status US Channel Type Frequency Width Power 1 1 Locked SC-QAM 17800000 Hz 6400000 Hz 49.0 dBmV 2 2 Locked SC-QAM 24200000 Hz 6400000 Hz 49.0 dBmV 3 3 Locked SC-QAM 30600000 Hz 6400000 Hz 49.0 dBmV 4 4 Locked SC-QAM 37000000 Hz 6400000 Hz 50.0 dBmV

Comments

  • misterjmisterj Posts: 80 ✭✭✭✭
    Aug 27, 2020

    Thanks for the levels and SNRs, Nitebeat but please re-post them as a Screenshot. It is really hard to decipher them like that. Please post just the SNRs and levels and if there are any OFDM information, please post that. Please tell me what color the LEDs are. Thanks and enjoy, John.

  • RAIST5150RAIST5150 Posts: 794 ✭✭✭✭
    edited August 27 Aug 27, 2020

    @Nitebeat

    Looks like you have a bit too much noise creeping in. A couple downstream channels are dipping close to the noise floor, and the upstream channels are screaming to be heard at the head end--the one at 37MHz is getting close to triggering an automatic reboot of the modem.

    Some of the dips are occurring in ranges that may indicate a legacy TV choke may still be in play from when they were blocking specific analogue channels that are no longer needed since they went all digital (the lower frequencies), as well as maybe some LTE creep that tends to seep in from things like cable boxes (the higher frequencies). If a TV choke is still in play, it could also be impacting upstream levels a bit as well.

    There could be issues with the inhouse wiring/devices, or somewhere upstream from your home. If there is reasonable access to where the line comes into the home, could try hooking the modem up there to compare levels against where it is installed now. If that shows substantial improvement, then that inhouse wiring will need to be investigated thoroughly to see what improvements may be made. Otherwise, will need to conduct a close inspection for the usual suspects... compromised cables, loose/corroded/wet connectors, splitters with open ports or unterminated cables, failing/maladjusted amps, etc.

  • misterjmisterj Posts: 80 ✭✭✭✭
    Aug 28, 2020

    Nitebeat, I have formatted your data and see nothing wrong. Your signal and SNRs are a little low but do appear to be a problem because of the low error counts. Are you sure you do not have any OFDM data in you statistics? Other users have OFDM data showing up.

    Still not real pretty but readable:

    Downstream Bonded Channels Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables

    32 Locked QAM256 471000000 Hz 0.6 dBmV 39.6 dB 9 28

     1 Locked QAM256 279000000 Hz 1.2 dBmV 39.5 dB 0 0

     2 Locked QAM256 285000000 Hz 1.3 dBmV 39.3 dB 0 0

     3 Locked QAM256 291000000 Hz 1.3 dBmV 39.3 dB 0 0

     4 Locked QAM256 297000000 Hz 1.3 dBmV 39.0 dB 0 0

     5 Locked QAM256 303000000 Hz 1.2 dBmV 39.3 dB 0 0

     6 Locked QAM256 309000000 Hz 1.2 dBmV 39.5 dB 0 0

     7 Locked QAM256 315000000 Hz 1.4 dBmV 39.3 dB 0 0

     8 Locked QAM256 321000000 Hz 1.2 dBmV 39.3 dB 0 0

     9 Locked QAM256 327000000 Hz 1.7 dBmV 39.5 dB 0 0

    10 Locked QAM256 333000000 Hz 1.1 dBmV 38.6 dB 0 0

    11 Locked QAM256 339000000 Hz 1.1 dBmV 34.8 dB 8034 1452

    12 Locked QAM256 345000000 Hz 1.6 dBmV 34.7 dB 0 0

    13 Locked QAM256 351000000 Hz 1.4 dBmV 38.8 dB 0 0

    14 Locked QAM256 357000000 Hz 1.1 dBmV 38.8 dB 0 0

    15 Locked QAM256 363000000 Hz 1.1 dBmV 39.0 dB 0 0

    16 Locked QAM256 369000000 Hz 1.4 dBmV 39.5 dB 0 0

    17 Locked QAM256 375000000 Hz 1.0 dBmV 39.3 dB 0 0

    18 Locked QAM256 381000000 Hz 1.3 dBmV 39.5 dB 0 0

    19 Locked QAM256 387000000 Hz 0.9 dBmV 39.2 dB 0 0

    20 Locked QAM256 393000000 Hz 1.3 dBmV 39.4 dB 0 0

    21 Locked QAM256 399000000 Hz 1.1 dBmV 39.4 dB 0 0

    22 Locked QAM256 405000000 Hz 1.4 dBmV 39.7 dB 0 0

    23 Locked QAM256 411000000 Hz 0.9 dBmV 39.4 dB 0 0

    24 Locked QAM256 417000000 Hz 0.9 dBmV 39.6 dB 0 0

    25 Locked QAM256 423000000 Hz 1.2 dBmV 39.7 dB 0 0

    26 Locked QAM256 429000000 Hz 1.2 dBmV 39.7 dB 0 0

    27 Locked QAM256 435000000 Hz 1.3 dBmV 39.0 dB 0 0

    28 Locked QAM256 447000000 Hz 1.3 dBmV 39.9 dB 0 0

    29 Locked QAM256 453000000 Hz 0.9 dBmV 39.7 dB 0 0

    30 Locked QAM256 459000000 Hz 1.2 dBmV 40.0 dB 0 0

    31 Locked QAM256 465000000 Hz 1.0 dBmV 39.9 dB 0 0

    33 Locked Other 777000000 Hz 2.2 dBmV 37.2 dB 421638 0


    Upstream Bonded Channels Channel Channel ID Lock Status US Channel Type Frequency Width Power

     1 1 Locked SC-QAM 17800000 Hz 6400000 Hz 49.0 dBmV

     2 2 Locked SC-QAM 24200000 Hz 6400000 Hz 49.0 dBmV

     3 3 Locked SC-QAM 30600000 Hz 6400000 Hz 49.0 dBmV

     4 4 Locked SC-QAM 37000000 Hz 6400000 Hz 50.0 dBmV


    Enjoy, John.

  • RAIST5150RAIST5150 Posts: 794 ✭✭✭✭
    edited August 28 Aug 28, 2020

    One channel in the AT&T/Verizon LTE sphere is getting flooded with corrupt packets.

    Below 37 SNR on downstream channels and hitting 49+ upstream on DOCSIS 3.0 channels is outside the norm they have targeted here for a long time... one of those channels is working it's way towards a no-no level of 51. History has shown that on THIS system straying from such norms tends to present stability/throughput issues in the 3.0 sphere.

    So yes, there is evidence of unwanted noise on the line that they will likely want to isolate.

Sign In or Register to comment.