Forum Discussion

ranch1's avatar
ranch1
New Contributor
2 years ago

ARRIS S33 cable modem event log shows 31/12/1969 date when internet connection is dropped

ARRIS S33 cable modem event log shows 31/12/1969 date when internet connection is dropped. Internet connection is re-established after a couple of minutes with the correct date and time. I have contacted COX and reported this problem with no luck. The modem gets the wrong date and time from a COX device that gives out the DHCP address and other information. COX has a piece of UNIX equipment that needs to be setup because it is sending the default 12/31/1969 date.

  • WiderMouthOpen's avatar
    WiderMouthOpen
    Esteemed Contributor
    2 years ago

    The UNIX equipment that is defaulting the date to 1969 is the modem itself. When it is not online it can't get the Time of Day(ToD) signal from Cox to set it's virtual clock. Since the modem has no internal clock, it defaults to the UNIX birthday. The problem isn't the lost of date but the loss of connection that causes the loss of date. If you want to troubleshoot that, look at what the event logs are saying before the connection loss. T3/T4 errors?

      • WiderMouthOpen's avatar
        WiderMouthOpen
        Esteemed Contributor
        2 years ago

        It's not a race. The more the merrier I always say.

        I was wondering how exactly the ToD system works. Does it use some kind of local NTP server at the headend? 

    • ranch1's avatar
      ranch1
      New Contributor
      2 years ago

      EXAMPLE

      26/7/2023
      10:39:26 3 SYNC Timing Synchronization failure - 

      31/12/1969
      17:00:15 3 CMSTATUS:US_Diplexer_Mode_Change:Init, 5-42MHz.
      31/12/1969
      17:00:19 3 SYNC Timing Synchronization failure - 
      31/12/1969
      17:00:21 3 CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.2, 108MHz.
      31/12/1969
      17:00:21 3 CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.3, 1002MHz.
      31/12/1969
      17:00:21 3 CMSTATUS:US_Diplexer_Mode_Change_Ignored:TLV-21.1, 85MHz.
      31/12/1969
      17:00:21 3 UCD invalid or channel unusable;
      31/12/1969
      17:00:25 3 No Ranging Response received - T3 time-out;
      31/12/1969
      17:00:33 6 Honoring MDD; IP provisioning mode = IPv4
      31/12/1969
      17:00:35 5 DHCP WARNING - Non-critical field invalid in response ;
      26/7/2023
      12:52:26 3 CMSTATUS:US_Diplexer_Mode_Change:TLV-84.1, 5-85MHz.
      26/7/2023
      12:52:26 3 CMSTATUS:US_Diplexer_Mode_Change_Ignored:Other, 85MHz.

      Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables
      21 Locked QAM256 855000000 Hz 0 dBmV 38 dB 0 0
      1 Locked QAM256 735000000 Hz 5 dBmV 42 dB 0 0
      2 Locked QAM256 741000000 Hz 5 dBmV 42 dB 0 0
      3 Locked QAM256 747000000 Hz 5 dBmV 42 dB 0 0
      4 Locked QAM256 753000000 Hz 5 dBmV 42 dB 0 0
      5 Locked QAM256 759000000 Hz 5 dBmV 42 dB 0 0
      6 Locked QAM256 765000000 Hz 4 dBmV 42 dB 0 0
      7 Locked QAM256 771000000 Hz 4 dBmV 42 dB 0 0
      8 Locked QAM256 777000000 Hz 3 dBmV 41 dB 0 0
      9 Locked QAM256 783000000 Hz 3 dBmV 41 dB 0 0
      10 Locked QAM256 789000000 Hz 3 dBmV 41 dB 0 0
      11 Locked QAM256 795000000 Hz 2 dBmV 41 dB 0 0
      12 Locked QAM256 801000000 Hz 3 dBmV 41 dB 0 0
      13 Locked QAM256 807000000 Hz 2 dBmV 40 dB 0 0
      14 Locked QAM256 813000000 Hz 2 dBmV 40 dB 0 0
      15 Locked QAM256 819000000 Hz 2 dBmV 40 dB 0 0
      16 Locked QAM256 825000000 Hz 1 dBmV 40 dB 0 0
      17 Locked QAM256 831000000 Hz 0 dBmV 39 dB 0 0
      18 Locked QAM256 837000000 Hz 0 dBmV 39 dB 0 0
      19 Locked QAM256 843000000 Hz 0 dBmV 39 dB 0 0
      20 Locked QAM256 849000000 Hz 0 dBmV 39 dB 0 0
      22 Locked QAM256 861000000 Hz -1 dBmV 38 dB 0 0
      23 Locked QAM256 867000000 Hz -1 dBmV 38 dB 0 0
      24 Locked QAM256 873000000 Hz -1 dBmV 38 dB 1 0
      41 Locked QAM256 213000000 Hz 8 dBmV 43 dB 0 0
      42 Locked QAM256 219000000 Hz 8 dBmV 43 dB 0 0
      43 Locked QAM256 225000000 Hz 8 dBmV 43 dB 0 0
      44 Locked QAM256 231000000 Hz 8 dBmV 43 dB 0 0
      45 Locked QAM256 237000000 Hz 8 dBmV 43 dB 0 0
      46 Locked QAM256 243000000 Hz 8 dBmV 43 dB 0 0
      47 Locked QAM256 249000000 Hz 8 dBmV 43 dB 0 0
      48 Locked QAM256 255000000 Hz 8 dBmV 43 dB 0 0
      159 Locked OFDM PLC 300000000 Hz 7 dBmV 42 dB 206384206 0
      160 Locked OFDM PLC 918000000 Hz -1 dBmV 36 dB 256849320 113



      Upstream Bonded Channels
      Channel ID Lock Status US Channel Type Frequency Width Power
      1 Locked SC-QAM 16900000 Hz 6400000 31.8 dBmV
      2 Locked SC-QAM 23500000 Hz 6400000 32.3 dBmV
      3 Locked SC-QAM 29900000 Hz 6400000 32.3 dBmV
      4 Locked SC-QAM 36300000 Hz 6400000 32.3 dBmV
      6 Locked OFDMA 36800000 Hz 44000000 27.0 dBmV



      Current System Time:Sat Jul 29 15:55:04 2023

      • WiderMouthOpen's avatar
        WiderMouthOpen
        Esteemed Contributor
        2 years ago
        17:00:25 3 No Ranging Response received - T3 time-out;

        That is the main error that made you lose connection. Can you post your signal levels?

  • JGriffi1's avatar
    JGriffi1
    New Contributor
    2 years ago

    I am having the same issue and have had to call Cox three times today and they keep just having me run a speed test and telling me the modem is fine...I tried explaining the errors and event log and requested a technician, but keep getting the run around. 

    • ranch1's avatar
      ranch1
      New Contributor
      2 years ago

      COX will never get back to you regarding this issue. I finally got a hold of a tech savy person that aggred to place a note to my complaint so that the I.T. people would address the problem of the wrong date and time in their equipment. Now that issue has been taken care of it is now the process of them every day setting the levels for download speed then upload speed. Its a balancing act to do this properly and the contractors do not have the big picture in mind when they just throw attenuators in line and connect your house to the wrong port. I pay for the 1 gig and 100 meg package and it is not being delivered as of yet, just have to be patient.

      • Darkatt's avatar
        Darkatt
        Honored Contributor
        2 years ago

        try replacing cable wires/splitters/barrel connectors, and see if that helps. Sometimes we get a bent cable wire, and that can cause all kinds of issues, causing the RF signal to get reflected backwards, and causing problems for all devices in the home.