Forum Discussion

csqrd757's avatar
csqrd757
New Contributor II
2 years ago

intermittent internet - perhaps poor signal strength?

For the past two weeks my internet has gone offline several times throughout the day.  This is not unusual as I have had spurts of outages for the past year or so.   However, it seems to be a daily occurrence as of lately.   Almost seems related to the warmer weather?  I have replaced my cable modem and router and have a single run of  new coax attached to my modem.  I am not versed in modem signal strengths but i am assuming they are not sufficient?   Any guidance would be appreciated.  

Downstream

Channel Lock Status Modulation Channel ID Frequency Power SNR Corrected Uncorrectables
1 Locked 256QAM 21 855.00 MHz -4.50 dBmV 37.36 dB 24 0
2 Locked 256QAM 1 735.00 MHz -2.00 dBmV 38.61 dB 0 0
3 Locked 256QAM 2 741.00 MHz -1.30 dBmV 38.61 dB 0 0
4 Locked 256QAM 3 747.00 MHz -1.20 dBmV 38.61 dB 0 0
5 Locked 256QAM 4 753.00 MHz -1.20 dBmV 38.98 dB 36 0
6 Locked 256QAM 5 759.00 MHz -1.00 dBmV 38.98 dB 17 0
7 Locked 256QAM 6 765.00 MHz -1.10 dBmV 38.61 dB 14 0
8 Locked 256QAM 7 771.00 MHz -1.10 dBmV 38.61 dB 32 0
9 Locked 256QAM 8 777.00 MHz -0.40 dBmV 38.98 dB 0 0
10 Locked 256QAM 9 783.00 MHz 0.00 dBmV 38.98 dB 31 0
11 Locked 256QAM 10 789.00 MHz -0.20 dBmV 38.61 dB 24 0
12 Locked 256QAM 11 795.00 MHz -0.20 dBmV 38.61 dB 23 0
13 Locked 256QAM 12 801.00 MHz -1.10 dBmV 38.61 dB 35 0
14 Locked 256QAM 13 807.00 MHz -1.90 dBmV 38.61 dB 23 0
15 Locked 256QAM 14 813.00 MHz -1.50 dBmV 38.98 dB 37 0
16 Locked 256QAM 15 819.00 MHz -2.00 dBmV 38.98 dB 41 0
17 Locked 256QAM 16 825.00 MHz -3.30 dBmV 37.36 dB 9 29
18 Locked 256QAM 17 831.00 MHz -3.90 dBmV 37.36 dB 36 0
19 Locked 256QAM 18 837.00 MHz -3.70 dBmV 37.64 dB 34 0
20 Locked 256QAM 19 843.00 MHz -4.40 dBmV 37.64 dB 33 0
21 Locked 256QAM 20 849.00 MHz -5.60 dBmV 37.64 dB 38 0
22 Locked 256QAM 22 861.00 MHz -3.90 dBmV 37.36 dB 37 0
23 Locked 256QAM 23 867.00 MHz -4.40 dBmV 37.64 dB 48 0
24 Locked 256QAM 24 873.00 MHz -3.90 dBmV 37.36 dB 16 29
25 Locked 256QAM 41 357.00 MHz 0.00 dBmV 36.20 dB 0 0
26 Locked 256QAM 42 363.00 MHz 0.30 dBmV 38.20 dB 8 0
27 Locked 256QAM 43 369.00 MHz 0.50 dBmV 39.20 dB 5 0
28 Locked 256QAM 44 375.00 MHz -0.10 dBmV 37.30 dB 5 0
29 Locked 256QAM 45 381.00 MHz -0.50 dBmV 39.90 dB 0 0
30 Locked 256QAM 46 387.00 MHz 0.00 dBmV 38.60 dB 0 0
31 Locked 256QAM 47 393.00 MHz 0.00 dBmV 38.90 dB 10 0
32 Locked 256QAM 48 399.00 MHz -0.40 dBmV 39.20 dB 0 0

Upstream:

Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 2 5120 kSym/s 23.90 MHz 38.75 dBmV
2 Locked ATDMA 4 5120 kSym/s 36.70 MHz 41.75 dBmV
3 Locked ATDMA 3 5120 kSym/s 30.30 MHz 40.25 dBmV
4 Locked ATDMA 1 5120 kSym/s 17.40 MHz 38.75 dBmV
  • WiderMouthOpen's avatar
    WiderMouthOpen
    Esteemed Contributor

    What model modem do you have? Do you seen anything critical in the logs from around the time of the disconnects? Signal levels look good to me. A few uncorrectables but that wouldn't cause a disconnect. 

    • csqrd757's avatar
      csqrd757
      New Contributor II

      Arris SB6190.  The modem was recently reset.  Here is the event log:

      Time Priority Description
      Thu Jan 01 00:07:44 1970 3 No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Tue Feb 28 13:27:20 2023 6 TLV-11 - unrecognized OID;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Tue Feb 28 13:28:32 2023 5 RCS Partial Service;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Tue Feb 28 13:30:46 2023 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Tue Feb 28 13:31:08 2023 3 No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Tue Feb 28 13:33:24 2023 3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Thu Jan 01 00:02:06 1970 3 No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Thu Jan 01 00:04:09 1970 5 B-INIT-RNG Failure - Retries exceeded;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Thu Jan 01 00:04:11 1970 3 No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Thu Jan 01 00:06:14 1970 5 B-INIT-RNG Failure - Retries exceeded;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Tue Feb 28 13:40:34 2023 6 TLV-11 - unrecognized OID;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Tue Feb 28 13:42:42 2023 3 No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Tue Feb 28 13:42:55 2023 5 RCS Partial Service;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Tue Feb 28 13:42:55 2023 3 No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Tue Feb 28 15:22:21 2023 3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Tue Feb 28 15:25:22 2023 6 TLV-11 - unrecognized OID;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Tue Feb 28 15:31:17 2023 3 No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Tue Feb 28 15:33:33 2023 3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Thu Jan 01 00:02:05 1970 3 No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Tue Feb 28 15:36:53 2023 6 TLV-11 - unrecognized OID;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      • WiderMouthOpen's avatar
        WiderMouthOpen
        Esteemed Contributor

        The 3 things I see in the log are T3 and T4 time-outs and the partial service error. Pretty sure that happens when the modem drops a downstream channel. The T3's happen from noise on the upstream. I think you require a technician. Hopefully you get a Cox technician and not a contractor, as they usually aren't paid/trained/etc to handle a ingress issue.

    • csqrd757's avatar
      csqrd757
      New Contributor II

      ARRIS SB6190.  The modem was recently reset.

      Event Log:

      Time Priority Description
      Thu Jan 01 00:07:44 1970 3 No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Tue Feb 28 13:27:20 2023 6 TLV-11 - unrecognized OID;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Tue Feb 28 13:28:32 2023 5 RCS Partial Service;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Tue Feb 28 13:30:46 2023 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Tue Feb 28 13:31:08 2023 3 No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Tue Feb 28 13:33:24 2023 3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Thu Jan 01 00:02:06 1970 3 No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Thu Jan 01 00:04:09 1970 5 B-INIT-RNG Failure - Retries exceeded;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Thu Jan 01 00:04:11 1970 3 No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Thu Jan 01 00:06:14 1970 5 B-INIT-RNG Failure - Retries exceeded;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Tue Feb 28 13:40:34 2023 6 TLV-11 - unrecognized OID;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Tue Feb 28 13:42:42 2023 3 No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Tue Feb 28 13:42:55 2023 5 RCS Partial Service;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Tue Feb 28 13:42:55 2023 3 No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Tue Feb 28 15:22:21 2023 3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Tue Feb 28 15:25:22 2023 6 TLV-11 - unrecognized OID;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Tue Feb 28 15:31:17 2023 3 No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Tue Feb 28 15:33:33 2023 3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Thu Jan 01 00:02:05 1970 3 No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;
      Tue Feb 28 15:36:53 2023 6 TLV-11 - unrecognized OID;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0;