Visitor
•
15 Messages
T3 Timeouts Everyday
Hi, I am hoping someone can help me with my issue of having T3 timeouts which happens a few times a day. It is causing my internet to go down for about 1-2 minutes when it happens. I just moved into this house 3 weeks ago and I have been having this problem every since I got here. There was already a line ran to the house from the other owners that lived here before me, so I do not know the history of how this was installed.
I have already tried calling customer support twice on this issue. The first tech told me I needed to buy a UPS/Batter Backup because there is power flucuation causing the modem to reset. I have never heard of needing one of these for a modem before. I of course did not go and buy one to test this theory. The other tech didn't know anything on how modems worked. He told me, and I quote, "I just sit here and push buttons all day".
The power coming in from the tap is pretty high so there are 2 attenuators hooked up at the modem, I am pretty sure they are both -6dbm, to get the power in the acceptable ranges. I have done all I can on my end that I can think of to try and fix this issue.
Today I also got a T4 timeout as well. I have only seen this a few times before. Not sure if this is related to the current issue I am facing or not.
Below are the stats of my modem. I have a Netgear CM2000.
Cable Diagnostic
Status: Good
Action:
Your setup looks fine. If you can't access the internet, make sure you properly activated the modem. If modem has been activated and you still can't access the internet, contact your service provider for troubleshooting help.
If you can access the internet but has other internet issue, the Netgear Cable Knowledge Base can provide additional troubleshooting info.
CM Status: Good
Downstream Status: Good
Downstream Power Level: Good
Downstream SNR Level: Good
Upstream Status: Good
Upstream Power Level: Good
Current Time: Mon Apr 10 15:23:55 2023
Startup Procedure
Acquire Downstream Channel: 417000000 Hz Locked
Connectivity State: OK Operational
Boot State: OK Operational
Security: Enabled BPI+
IP Provisioning Mode: Honor MDD IPv6 only
Downstream Bonded Channels
Channel LockedStatus Modulation ChannelID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 4 417000000 Hz 1.4 39.3 490357 1485404
2 Locked QAM256 1 399000000 Hz 1.3 39.6 568448 1742801
3 Locked QAM256 2 405000000 Hz 1.4 39.8 393383 1184826
4 Locked QAM256 3 411000000 Hz 1.3 39.8 607123 1879398
5 Locked QAM256 5 423000000 Hz 1.6 40.2 505599 1549441
6 Locked QAM256 6 429000000 Hz 1.7 40.5 704178 2170015
7 Locked QAM256 7 435000000 Hz 2.3 40.4 799888 2497828
8 Locked QAM256 8 441000000 Hz 1.5 40.4 670895 2061712
9 Locked QAM256 9 447000000 Hz 1.3 40.4 919439 2897431
10 Locked QAM256 10 453000000 Hz 1.3 40.2 744755 2278876
11 Locked QAM256 11 459000000 Hz 1.3 40.2 827319 2547817
12 Locked QAM256 12 465000000 Hz 2.1 39.6 789432 2456561
13 Locked QAM256 13 471000000 Hz 2.2 40 739821 2266617
14 Locked QAM256 14 477000000 Hz 1.9 40 966249 3053012
15 Locked QAM256 15 483000000 Hz 1.8 39.9 1161554 3672462
16 Locked QAM256 16 489000000 Hz 1.5 39.5 1291008 4141950
17 Locked QAM256 17 495000000 Hz 1.2 38.9 1017851 3186658
18 Locked QAM256 18 507000000 Hz 1.7 39.1 1086470 3398121
19 Locked QAM256 19 513000000 Hz 1.5 39.4 1230062 3927490
20 Locked QAM256 20 519000000 Hz 1.7 38.6 1215263 3859046
21 Locked QAM256 21 525000000 Hz 1.1 38.9 1335078 4283887
22 Locked QAM256 22 531000000 Hz 0.9 39.4 1523476 4881765
23 Locked QAM256 23 537000000 Hz 0.5 38.5 1417264 4478860
24 Locked QAM256 24 543000000 Hz 1 39.1 1412599 4471985
25 Locked QAM256 25 549000000 Hz 1.4 39.8 1847949 6006364
26 Locked QAM256 26 555000000 Hz 1.5 39.8 1812841 5870645
27 Locked QAM256 27 561000000 Hz 1.3 39.8 1280804 3988808
28 Locked QAM256 28 567000000 Hz 1.3 39.9 1864747 6043975
29 Locked QAM256 29 573000000 Hz 0.8 40.1 1482066 4686403
30 Locked QAM256 30 579000000 Hz 0.6 40 1685022 5397578
31 Locked QAM256 31 585000000 Hz 0.6 40 1964030 6353341
32 Locked QAM256 32 591000000 Hz 0.8 40.1 1738433 5591987
Upstream Bonded Channels
Channel LockedStatus ChannelType ChannelID SymbolRate Frequency Power
1 Locked ATDMA 1 5120 Ksym/sec 35600000 Hz 48.0 dBmV
2 Locked ATDMA 2 5120 Ksym/sec 29200000 Hz 48.5 dBmV
3 Locked ATDMA 3 5120 Ksym/sec 22800000 Hz 48.0 dBmV
4 Locked ATDMA 4 5120 Ksym/sec 16400000 Hz 48.0 dBmV
5 Locked ATDMA 5 2560 Ksym/sec 40400000 Hz 46.0 dBmV
6 Locked ATDMA 6 2560 Ksym/sec 10400000 Hz 47.0 dBmV
7 Not Locked Unknown 0 0 0 0.0
8 Not Locked Unknown 0 0 0 0.0
Downstream OFDM Channels
Channel LockedStatus ProfileID ChannelID Frequency Power SNR/MER ActiveSubcarrier Unerror Correctable Uncorrectable
1 Locked 0 ,1 ,2 ,3 193 690000000 Hz -1.92 dBmV 39.2 dB 1108 ~ 2987 1531051310 1187822673 0
2 Not Locked 0 0 0 Hz 0 dBmV 0 dB 0 ~ 4095 0 0 0
Upstream OFDMA Channels
Channel LockedStatus ProfileID ChannelID Frequency Power
1 Not Locked 0 0 0 Hz 0 dBmV
2 Not Locked 0 0 0 Hz 0 dBmV
Event Log
Time Priority Description
Mon Apr 10 15:21:26 2023 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 10 14:21:07 2023 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 10 12:09:02 2023 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 10 12:08:56 2023 Warning (5) MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 10 12:08:53 2023 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 10 11:43:01 2023 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 10 11:42:52 2023 Warning (5) MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 10 11:42:52 2023 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 10 16 17 24 27; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 10 11:42:50 2023 Warning (5) MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 10 11:42:37 2023 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 10 11:41:57 2023 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 10 16 17 24; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 10 11:41:43 2023 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 10 11:41:27 2023 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 10 16 17 24; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 10 11:41:13 2023 Warning (5) MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 10 11:41:02 2023 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 10 11:34:16 2023 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 12 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 10 11:34:01 2023 Warning (5) MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 10 11:25:48 2023 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 12 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 10 11:25:47 2023 Warning (5) MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 10 11:22:39 2023 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 10 16 17; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 10 11:22:33 2023 Notice (6) CM-STATUS message sent. Event Type Code: 2; Chan ID: 10; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 10 10:01:25 2023 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 12 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 10 10:01:00 2023 Warning (5) MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 10 10:00:29 2023 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 10 09:57:40 2023 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 16 17; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 10 09:57:40 2023 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 15 16 17 18 19 21 22 23 27 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 10 09:57:34 2023 Warning (5) MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 10 09:57:17 2023 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 19 21 23 27 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 10 09:57:13 2023 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 10 09:56:49 2023 Warning (5) MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 10 09:56:18 2023 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 10 09:45:44 2023 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 21 23 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 10 09:45:24 2023 Warning (5) MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 10 09:43:02 2023 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 10 09:39:02 2023 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 10 09:39:00 2023 Warning (5) MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 10 09:37:04 2023 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sun Apr 09 15:11:44 2023 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sun Apr 09 15:11:36 2023 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sun Apr 09 15:11:30 2023 Notice (6) TLV-11 - unrecognized OID;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Accepted Solution
user_edu1411
Visitor
•
15 Messages
2 years ago
Problem appears to be fixed now. Appreantly there was a bunch more damaged lines in the neighborhood that have finally been fixed. Everything seems stable now without issue.
1
0
EG
Expert
•
110K Messages
2 years ago
Please redact the CM MAC address from the first line of your error log entries for your privacy. They are considered to be personal information. The posting of personally identifiable information is a violation of their forum guidelines. The forum bot will not allow your post to be seen publically. It flagged your post as "Private".
1
0
EG
Expert
•
110K Messages
2 years ago
OK. Are those two attenuators the overall type or are the FPA's (Forward Path Attenuators) ? What are the make and model numbers ?
1
0
EG
Expert
•
110K Messages
2 years ago
So this may or may not be the root cause of the problem (YMMV) but the upstream power is on the high side and it may be intermittently fluctuating even higher to out of spec levels. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.
So you can first try removing the Holland FAM-6 pad and see. It will lower the upstream power down 6 dB to a more desirable range with more wiggle room. And it will raise the downstream power by 6 dB but it will still be OK / in spec. Please post back with what the new power levels are after doing so.
3
0
EG
Expert
•
110K Messages
2 years ago
For the Halibut, you can try taking out the 12 SVCS. It's a cable simulator / tilt compensator, not an actual overall attenuator pad. If it doesn't help, you can always put it back inline. I'm curious to see the signal values with it removed so please post them.
Again. Please bear in mind that we may be barking up the wrong tree, so you may need a tech out to investigate this one.
1
0
EG
Expert
•
110K Messages
2 years ago
Put it back in. The downstream power is way too high without it. They may need to adjust / balance the power levels at the line amp on the pole / aerial strand. Please post back again after they are done. Good luck !
8
0