Forum Discussion

Jamza25's avatar
Jamza25
New Contributor
5 months ago

Modem reboots daily, T3/T4 time-outs.

My modem is rebooting every day at around the same hour, causing all my wifi and ethernet connections to drop. Log is not showing time-outs everyday but it is happening as I see all my devices disconnect at the same time. It takes a couple of minutes for everything to reconnect, or seconds if I manually turn off/on the modem.

The coax cable is tight and not damaged from what I can see. I've already manually reset the modem multiple times and the problem didn't go away.

DOWNSTREAM/UPSTREAM BONDED CHANNELS:

Downstream Bonded Channels
ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectablesUnCorrectables
1LockedQAM 25629141000000 Hz4.0 dBmV43.3 dB1030
2LockedQAM 25633165000000 Hz4.4 dBmV40.9 dB590
3LockedQAM 25634171000000 Hz4.4 dBmV43.3 dB650
4LockedQAM 25635177000000 Hz4.5 dBmV43.3 dB420
5LockedQAM 25636183000000 Hz4.5 dBmV43.3 dB340
6LockedQAM 25638195000000 Hz4.6 dBmV43.3 dB270
7LockedQAM 25639201000000 Hz4.5 dBmV40.9 dB230
8LockedQAM 25640207000000 Hz4.6 dBmV43.3 dB150
9LockedQAM 25641213000000 Hz4.5 dBmV40.3 dB210
10LockedQAM 25642219000000 Hz4.6 dBmV43.3 dB240
11LockedQAM 25643225000000 Hz4.8 dBmV40.9 dB90
12LockedQAM 25644231000000 Hz4.6 dBmV43.3 dB180
13LockedQAM 25645237000000 Hz4.5 dBmV40.9 dB170
14LockedQAM 25646243000000 Hz4.6 dBmV40.9 dB130
15LockedQAM 25647249000000 Hz4.5 dBmV43.3 dB120
16LockedQAM 25613807000000 Hz2.7 dBmV40.9 dB20
 
Upstream Bonded Channels
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedATDMA15120 Ksym/sec17600000 Hz43.5 dBmV
2LockedATDMA25120 Ksym/sec24000000 Hz43.5 dBmV
3LockedATDMA35120 Ksym/sec30400000 Hz43.5 dBmV
4LockedATDMA45120 Ksym/sec36800000 Hz43.5 dBmV

 

EVENT LOG:

Sep 18 2023 08:57:46

Critical (3)No Ranging Response received - T3 time-out
Sep 18 2023 08:57:39Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Sep 18 2023 08:57:27Notice (6)TLV-11 - unrecognized OID
Sep 18 2023 08:57:27Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Sep 17 2023 22:30:22Critical (3)No Ranging Response received - T3 time-out
Sep 17 2023 22:30:09Notice (6)TLV-11 - unrecognized OID
Sep 17 2023 22:30:09Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Sep 16 2023 23:03:34Critical (3)No Ranging Response received - T3 time-out
Sep 16 2023 23:03:31Notice (6)TLV-11 - unrecognized OID
Sep 16 2023 23:03:31Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Sep 12 2023 12:50:02Critical (3)No Ranging Response received - T3 time-out
Sep 12 2023 09:58:13Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Sep 12 2023 09:57:58Notice (6)TLV-11 - unrecognized OID
Sep 12 2023 09:57:58Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1

5 Replies

  • Hello. By any chance, do you have any splitters or signal amps on the cable line going to the modem? 

    • Jamza25's avatar
      Jamza25
      New Contributor

      There's nothing on the cable. I talked with someone over email already and they couldn't see any issues on their end, but my connection just dropped an hour ago (exactly 12 hours since I last rebooted, at the lease time half-mark) and log shows the T3 and T4 time-out messages, uptime also reset.

      From searching around someone fixed (temporarily) the issue by assigning static IPs but since the uptime shows it dropped I don't think it will work for me, I'll still try.

      Also Cox doesn't support the lastest firmware for my modem and that could also be the issue, so I will be trying with a new modem and see if the problem continues before getting a technician.

  • Dgrewing2's avatar
    Dgrewing2
    New Contributor

    Our connection is going out every day as well. It's ridiculous!

    • Allan's avatar
      Allan
      Moderator

      Hello. I recommend sending us an email with your full name, address, and a brief description of this issue to cox.help@cox.com.