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?
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
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?
A little over 53 hrs and the date and time have not been set on my modem to 12/31/1969 with the drop in internet coverage to follow. I have not made any changes to my residential setup but did notify COX about the date problem a little over 2 days ago.
Shortly after the post above stating I have had no internet problems for over 53 hrs, the internet goes down and my levels have all changed.
After COX outage to fix problems…
|
Downstream Bonded Channels |
|||||||
|
Channel ID |
Lock Status |
Modulation |
Frequency |
Power |
SNR/MER |
Corrected |
Uncorrectables |
|
21 |
Locked |
QAM256 |
855000000 Hz |
0 dBmV |
38 dB |
177 |
0 |
|
1 |
Locked |
QAM256 |
735000000 Hz |
6 dBmV |
42 dB |
98 |
456 |
|
2 |
Locked |
QAM256 |
741000000 Hz |
5 dBmV |
42 dB |
120 |
446 |
|
3 |
Locked |
QAM256 |
747000000 Hz |
5 dBmV |
42 dB |
114 |
450 |
|
4 |
Locked |
QAM256 |
753000000 Hz |
6 dBmV |
42 dB |
118 |
445 |
|
5 |
Locked |
QAM256 |
759000000 Hz |
5 dBmV |
42 dB |
135 |
431 |
|
6 |
Locked |
QAM256 |
765000000 Hz |
5 dBmV |
42 dB |
117 |
445 |
|
7 |
Locked |
QAM256 |
771000000 Hz |
5 dBmV |
42 dB |
107 |
457 |
|
8 |
Locked |
QAM256 |
777000000 Hz |
4 dBmV |
41 dB |
26 |
0 |
|
9 |
Locked |
QAM256 |
783000000 Hz |
4 dBmV |
41 dB |
17 |
0 |
|
10 |
Locked |
QAM256 |
789000000 Hz |
4 dBmV |
41 dB |
18 |
0 |
|
11 |
Locked |
QAM256 |
795000000 Hz |
3 dBmV |
41 dB |
21 |
0 |
|
12 |
Locked |
QAM256 |
801000000 Hz |
3 dBmV |
41 dB |
23 |
0 |
|
13 |
Locked |
QAM256 |
807000000 Hz |
3 dBmV |
41 dB |
15 |
0 |
|
14 |
Locked |
QAM256 |
813000000 Hz |
2 dBmV |
40 dB |
110 |
479 |
|
15 |
Locked |
QAM256 |
819000000 Hz |
2 dBmV |
40 dB |
112 |
478 |
|
16 |
Locked |
QAM256 |
825000000 Hz |
2 dBmV |
40 dB |
101 |
489 |
|
17 |
Locked |
QAM256 |
831000000 Hz |
1 dBmV |
40 dB |
115 |
469 |
|
18 |
Locked |
QAM256 |
837000000 Hz |
1 dBmV |
39 dB |
129 |
455 |
|
19 |
Locked |
QAM256 |
843000000 Hz |
0 dBmV |
39 dB |
103 |
481 |
|
20 |
Locked |
QAM256 |
849000000 Hz |
0 dBmV |
39 dB |
110 |
474 |
|
22 |
Locked |
QAM256 |
861000000 Hz |
0 dBmV |
38 dB |
103 |
470 |
|
23 |
Locked |
QAM256 |
867000000 Hz |
0 dBmV |
38 dB |
103 |
467 |
|
24 |
Locked |
QAM256 |
873000000 Hz |
0 dBmV |
38 dB |
124 |
475 |
|
41 |
Locked |
QAM256 |
213000000 Hz |
8 dBmV |
43 dB |
137 |
469 |
|
42 |
Locked |
QAM256 |
219000000 Hz |
8 dBmV |
43 dB |
157 |
467 |
|
43 |
Locked |
QAM256 |
225000000 Hz |
8 dBmV |
43 dB |
121 |
480 |
|
44 |
Locked |
QAM256 |
231000000 Hz |
8 dBmV |
43 dB |
116 |
472 |
|
45 |
Locked |
QAM256 |
237000000 Hz |
8 dBmV |
43 dB |
126 |
450 |
|
46 |
Locked |
QAM256 |
243000000 Hz |
8 dBmV |
43 dB |
130 |
456 |
|
47 |
Locked |
QAM256 |
249000000 Hz |
8 dBmV |
43 dB |
116 |
447 |
|
48 |
Locked |
QAM256 |
255000000 Hz |
8 dBmV |
43 dB |
98 |
448 |
|
159 |
Locked |
OFDM PLC |
300000000 Hz |
8 dBmV |
43 dB |
1949529824 |
0 |
|
160 |
Locked |
OFDM PLC |
918000000 Hz |
0 dBmV |
37 dB |
2390641426 |
558 |
|
Upstream Bonded Channels |
||||||
|
Channel ID |
Lock Status |
US Channel Type |
Frequency |
Width |
Power |
|
|
1 |
Locked |
SC-QAM |
16900000 Hz |
6400000 |
31.0 dBmV |
|
|
2 |
Locked |
SC-QAM |
23500000 Hz |
6400000 |
31.3 dBmV |
|
|
3 |
Locked |
SC-QAM |
29900000 Hz |
6400000 |
30.8 dBmV |
|
|
4 |
Locked |
SC-QAM |
36300000 Hz |
6400000 |
31.3 dBmV |
|
|
6 |
Locked |
OFDMA |
36800000 Hz |
44000000 |
26.2 dBmV |
|
Current System Time:Mon Jul 31 20:42:50 2023
It COULD be the modem.
Have they scheduled a tc to ensure the signals are in spec?
Your upstream looks low. Usually the lower the better, but if there is intermittent noise floor problem low upstream can be a issue. Its basically like if you are at a party and trying to whisper to be heard. If there is high background noise, you can't be heard very well and there is T3 errors. However, when the party stops, it is very quiet so you don't have to talk loud so your upstream doesn't have to be high.
I would suggest having a technician investigate the T3 errors. Maybe a attenuator might help. Don't mention the date error. That will only confuse the technician IMO.
::edit:: I assume you have bypassed all the splitters in the house BTW. Please confirm that.
Those downstream's are a bit hot, honestly, I prefer seeing something closer to 50 db.
Just the one feed from COX going directly to the cable modem. This has already been checked out by a COX technician a couple days ago at the house and point of service
Just for testing, add a splitter inline to the modem and test it for a few hours, see what happens?
Abnormally low upstream power levels combined with normal/above normal downstreams makes me wonder if there's an amplifier somewhere in the connection. That may be the case if the home has ever had lots of simultaneously active cable outlets to counteract the signal loss that comes with all the splits. If that's what's happening the ideal solution would be to put a 2-way splitter at the demarc with the modem coming off one leg then the amp on the other for the remaining outlets. If your home is a newer construction the developer may have installed a smart panel distribution system for the entire house. Without specialized knowledge as to how to best configure those they generally tend to cause more harm than good.
