1 Message
Dropping connection- Critical 3 T3 time-out
Hello. I have a Netgear CM2000. I keep receiving critical 3 T3 time outs in my error log. I had a tech come out, he found a kink in the line at the pole and replaced. Checked signals at the line coming into the home and at my modem- all good. However I'm still getting T3 time-outs. One of my downstream channels is getting some uncorrectables
Here's my log and Diagnostic
| Time | Priority | Description |
| Thu Apr 03 01:42:34 2025 | (Critical (3)) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=NA;CMTS-MAC=NA;CM-QOS=1.1;CM-VER=3.1; |
| Wed Apr 02 17:32:29 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=NA;CMTS-MAC=NA;CM-QOS=1.1;CM-VER=3.1; |
| Wed Apr 02 17:31:10 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 23; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=NA;CMTS-MAC=NA;CM-QOS=1.1;CM-VER=3.1; |
| Wed Apr 02 17:30:18 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=NA;CMTS-MAC=NA;CM-QOS=1.1;CM-VER=3.1; |
| Wed Apr 02 17:25:49 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=NA;CMTS-MAC=NA;CM-QOS=1.1;CM-VER=3.1; |
| Wed Apr 02 17:24:30 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 23; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=NA;CMTS-MAC=NA;CM-QOS=1.1;CM-VER=3.1; |
| Wed Apr 02 17:23:38 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=NA;CMTS-MAC=NA;CM-QOS=1.1;CM-VER=3.1; |
| Wed Apr 02 17:19:09 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=NA;CMTS-MAC=NA;CM-QOS=1.1;CM-VER=3.1; |
| Wed Apr 02 17:17:50 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 23; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=NA;CMTS-MAC=NA;CM-QOS=1.1;CM-VER=3.1; |
| Wed Apr 02 17:16:58 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=NA;CMTS-MAC=NA;CM-QOS=1.1;CM-VER=3.1; |
| Wed Apr 02 17:13:47 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=NA;CMTS-MAC=NA;CM-QOS=1.1;CM-VER=3.1; |
| Wed Apr 02 17:12:32 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=NA;CMTS-MAC=NA;CM-QOS=1.1;CM-VER=3.1; |
| Wed Apr 02 17:12:29 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 3.;CM-MAC=NA;CMTS-MAC=NA;CM-QOS=1.1;CM-VER=3.1; |
| Wed Apr 02 17:12:27 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=NA;CMTS-MAC=NA;CM-QOS=1.1;CM-VER=3.1; |
| Wed Apr 02 17:11:56 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=NA;CMTS-MAC=NA;CM-QOS=1.1;CM-VER=3.1; |
| Wed Apr 02 17:11:23 2025 | (Warning (5)) | MDD message timeout;CM-MAC=NA;CMTS-MAC=NA;CM-QOS=1.1;CM-VER=3.1; |
| Wed Apr 02 15:10:52 2025 | (Critical (3)) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=NA;CMTS-MAC=NA;CM-QOS=1.1;CM-VER=3.1; |
| Mon Mar 31 17:26:13 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=NA;CMTS-MAC=NA;CM-QOS=1.1;CM-VER=3.1; |
| Mon Mar 31 17:24:10 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=NA;CMTS-MAC=NA;CM-QOS=1.1;CM-VER=3.1; |
| Mon Mar 31 17:22:51 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 23; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=NA;CMTS-MAC=NA;CM-QOS=1.1;CM-VER=3.1; |
| Mon Mar 31 17:19:33 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=NA;CMTS-MAC=NA;CM-QOS=1.1;CM-VER=3.1; |
| Mon Mar 31 17:17:30 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=NA;CMTS-MAC=NA;CM-QOS=1.1;CM-VER=3.1; |
| Mon Mar 31 17:16:11 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 23; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=NA;CMTS-MAC=NA;CM-QOS=1.1;CM-VER=3.1; |
| Mon Mar 31 17:12:53 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=NA;CMTS-MAC=NA;CM-QOS=1.1;CM-VER=3.1; |
| Mon Mar 31 17:10:50 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=NA;CMTS-MAC=NA;CM-QOS=1.1;CM-VER=3.1; |
| Mon Mar 31 17:10:06 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=NA;CMTS-MAC=NA;CM-QOS=1.1;CM-VER=3.1; |
| Mon Mar 31 17:09:31 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 23; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=NA;CMTS-MAC=NA;CM-QOS=1.1;CM-VER=3.1; |
| Mon Mar 31 17:09:06 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=NA;CMTS-MAC=NA;CM-QOS=1.1;CM-VER=3.1; |
| Mon Mar 31 17:08:35 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=NA;CMTS-MAC=NA;CM-QOS=1.1;CM-VER=3.1; |
| Mon Mar 31 17:07:58 2025 | (Warning (5)) | MDD message timeout;CM-MAC=NA;CMTS-MAC=NA;CM-QOS=1.1;CM-VER=3.1; |
| Mon Mar 31 16:16:53 2025 | (Critical (3)) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=54:07:7d:02:c7:60;CMTS-MAC=NA;CM-QOS=1.1;CM-VER=3.1; |
| Sun Mar 30 12:44:47 2025 | (Critical (3)) | UCD invalid or channel unusable;CM-MAC=NA;CMTS-MAC=NA;CM-QOS=1.1;CM-VER=3.1; |
| Sun Mar 30 12:36:43 2025 | (Critical (3)) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=NA;CMTS-MAC=NA;CM-QOS=1.1;CM-VER=3.1; |
| Sun Mar 30 12:34:43 2025 | (Critical (3)) | UCD invalid or channel unusable;CM-MAC=NA;CMTS-MAC=NA;CM-QOS=1.1;CM-VER=3.1; |
| Sun Mar 30 12:34:11 2025 | (Critical (3)) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=NA;CMTS-MAC=NA;CM-QOS=1.1;CM-VER=3.1; |
| Thu Mar 27 17:42:33 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=NA;CMTS-MAC=NA;CM-QOS=1.1;CM-VER=3.1; |
| Downstream OFDM Channels | |||||||||||||||||||||||||||||||||
|
No Responses!