NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Experiencing packet loss and loss connection
Wed Sep 22 17:45:55 2021 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 22 16...
So last night I responded to my thread with the cable connections page, however the Netgear website was sturggling quite a bit and it said that it posted, apparently it did not.
I will post when I get home tonight, from what I do know, 31/32 downstream channels are locked and one is considered unknown. For my upstream channels, 4/8 are active. I am not too versed in understanding what any of that means and searching last night didn't really give me an idea as well.
Before my ISP showed up I went ahead and got their modem and was going to fiddle with mine a little more before plugging theirs in to see if my modem is causing the problem. The interesting thing for me is that I was running this hardware for around ~45days in this house before we started to see internet problems. Since then, the last month, it's every day.
I think I may have been lucky last night when I ran a speedtest on my LAN while I was experiencing some issues, and came back with 4mpbs downstream signal. I immediately got on ISP website and was working through the support line and ran the speedtest they needed me to run and we were magically back up to 420-450mbps downstream.
I appreciate the reply and will post the cable logs. I did check the FW and that is current. If it means anything, my modem then connects to an Asus GT-AX11000 which at this point, I feel like the problem is before my router.
Thank you
Line issues can be challenging. Even the connections page doesn't always help that much as it takes a brief snip when the page is opened. the logs help because they show longer term (which indicate line issues by the t3 errors). but if there's something obvious on there it helps.
If the isp's checked the line, try moving the modem to right where the coax enters the home. they rarely look at anything in the home and just ensure the signal is good up to where it goes into the home. After that its on the home owner to ensure the cables/splitters/etc are all in good condition.
The tech checked the lines from the box outside, junction box attached to house, my tele box in garage, and then the line all the way through the house to the modem. He stated, which in previous experience could have been just to get done, that the lines were clean. He even said that testing past the modem was clean, however, same story same dance scenario.
Apply Cancel Frequency start Value This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect. Starting Frequency 0 Startup Procedure Procedure Status Comment Acquire Downstream Channel 759000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Security Enabled BPI+ IP Provisioning Mode IPv6 Only ipv6Only(1) Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables 1 Locked QAM256 20 759000000 Hz 5.6 dBmV 37.5 dB 105 0 2 Locked QAM256 2 651000000 Hz 5.7 dBmV 38.4 dB 140 0 3 Locked QAM256 3 657000000 Hz 5.5 dBmV 38.2 dB 160 0 4 Locked QAM256 4 663000000 Hz 5.5 dBmV 38.1 dB 151 0 5 Locked QAM256 5 669000000 Hz 5.8 dBmV 38.1 dB 155 0 6 Locked QAM256 6 675000000 Hz 5.6 dBmV 37.7 dB 139 0 7 Locked QAM256 7 681000000 Hz 5.5 dBmV 38 dB 177 0 8 Locked QAM256 8 687000000 Hz 5.7 dBmV 38 dB 162 0 9 Locked QAM256 9 693000000 Hz 5.5 dBmV 38 dB 145 0 10 Locked QAM256 10 699000000 Hz 5.6 dBmV 37.9 dB 138 0 11 Locked QAM256 11 705000000 Hz 5.6 dBmV 37.9 dB 132 0 12 Locked QAM256 12 711000000 Hz 5.6 dBmV 37.9 dB 147 0 13 Locked QAM256 13 717000000 Hz 5.7 dBmV 37.8 dB 135 0 14 Locked QAM256 14 723000000 Hz 5.6 dBmV 37.7 dB 124 0 15 Locked QAM256 15 729000000 Hz 5.7 dBmV 37.7 dB 121 0 16 Locked QAM256 16 735000000 Hz 5.8 dBmV 37.7 dB 129 0 17 Locked QAM256 17 741000000 Hz 5.8 dBmV 37.8 dB 109 0 18 Locked QAM256 18 747000000 Hz 5.8 dBmV 37.7 dB 145 0 19 Locked QAM256 19 753000000 Hz 5.8 dBmV 37.6 dB 128 0 20 Locked QAM256 21 765000000 Hz 5.4 dBmV 37.5 dB 99 0 21 Locked QAM256 22 771000000 Hz 5.4 dBmV 37.5 dB 121 0 22 Locked QAM256 23 777000000 Hz 5.3 dBmV 37.6 dB 165 19 23 Locked QAM256 24 783000000 Hz 5.2 dBmV 37.4 dB 209 8 24 Locked QAM256 25 789000000 Hz 5.2 dBmV 37.4 dB 122 0 25 Locked QAM256 26 795000000 Hz 5.1 dBmV 37.2 dB 97 0 26 Locked QAM256 27 801000000 Hz 5.1 dBmV 37.2 dB 107 0 27 Locked QAM256 28 807000000 Hz 4.9 dBmV 37.1 dB 105 0 28 Locked QAM256 29 813000000 Hz 4.9 dBmV 37 dB 97 0 29 Locked QAM256 30 819000000 Hz 4.9 dBmV 36.9 dB 95 0 30 Locked QAM256 32 831000000 Hz 4.8 dBmV 36.7 dB 120 0 31 Locked QAM256 33 645000000 Hz 6 dBmV 38.6 dB 134 0 32 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 5 5120 Ksym/sec 17800000 Hz 45 dBmV 2 Locked ATDMA 6 5120 Ksym/sec 24200000 Hz 45.3 dBmV 3 Locked ATDMA 7 5120 Ksym/sec 30600000 Hz 46.3 dBmV 4 Locked ATDMA 8 5120 Ksym/sec 37000000 Hz 47 dBmV 5 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 6 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 7 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 8 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV Downstream OFDM Channels Channel Lock Status Modulation / Profile ID Channel ID Frequency Power SNR / MER Active Subcarrier Number Range Unerrored Codewords Correctable Codewords Uncorrectable Codewords 1 Locked 0 ,1 ,2 1 338000000 Hz 4.9 dBmV 40.7 dB 148 ~ 3947 2942451253 2838745666 137732 2 Not Locked 0 0 0 Hz 0 dBmV 0.0 dB 0 ~ 4095 0 0 0 Upstream OFDMA Channels Channel Lock Status Modulation / Profile ID Channel ID Frequency Power 1 Not Locked 0 0 0 Hz 0 dBmV 2 Not Locked 0 0 0 Hz 0 dBmV Extended Upstream Transmit Power Enable Extended Upstream Transmit Power Current System Time:Thu Sep 23 18:34:25 2021 System Up Time:2 days 02:08:54
Here is the current event log that corresponds with the cable connection page.
Also apparently my post from yesterday did come up and I can see it now in the thread showing yesterday.
Thank you again.
Time Priority Description Thu Sep 23 18:42:12 2021 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 17:32:52 2021 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 17:32:14 2021 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 16:46:13 2021 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 16:45:34 2021 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 16:18:10 2021 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 16:17:36 2021 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 15:06:12 2021 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 15:01:59 2021 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 14:15:58 2021 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 14:15:51 2021 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 12:20:21 2021 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 12:20:01 2021 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 11:59:18 2021 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 11:58:46 2021 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 10:13:53 2021 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 10:12:43 2021 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 09:34:51 2021 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 09:33:37 2021 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 08:05:26 2021 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 08:04:55 2021 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 07:13:09 2021 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 04:22:56 2021 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 04:15:38 2021 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 04:15:38 2021 Notice (6) TLV-11 - unrecognized OID;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 04:15:37 2021 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 04:15:37 2021 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 04:15:28 2021 Notice (6) Overriding MDD IP initialization parameters; IP provisioning mode = IPv6 Thu Sep 23 04:15:16 2021 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 04:15:15 2021 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 04:15:11 2021 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 04:15:10 2021 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 04:14:56 2021 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 04:14:56 2021 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 04:14:54 2021 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 04:12:15 2021 Notice (6) CM-STATUS message sent. Event Type Code: 8; Chan ID: 6 7 8; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 04:11:16 2021 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 04:09:32 2021 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 04:09:18 2021 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1; Thu Sep 23 04:09:18 2021 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Your powerlevels look pretty spot on.
But your event logs are showing issues connecting back to the cmts.
You're caught in a problem.
The power levels do look good. but the logs dont. And the ISP has checked the line.
so is it still the line or is it the modem?
Unless you have a backup modem, its tough to prove either way.
I've actually rented a modem from an ISP for the $10 a month (only rented for a month) to check which is was.
right now I've got enough backup modems that I don't have to do that anymore.