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...
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.
Lol, this is where I figured that I am. I do have the spectrum provided modem, picked up a few days ago. I have been too prideful to accept that my modem could be the problem and wanted to check on here first before fully accepting defeat. I do plan to commission the spectrum modem to see if things become more stable which in turn will tell me I just need to get another modem.
Last question, would factory reseting the modem do anything? Or is this more hardware malfunction kind of thing and its a lost cause? Of course this is assuming the modem is the actual culprit and nothing upstream.
At this rate, I am just trying to find some piece of mind.
Thank you again
yahdoneson1247 wrote:
Last question, would factory reseting the modem do anything? ---doesn't hurt to try. It doesn't need to be reinstalled/reprovisioned when you do it. Or is this more hardware malfunction kind of thing and its a lost cause?---I'm not sure its a hardware failure. I'd still be betting on an issue connecting to the cmts. Of course this is assuming the modem is the actual culprit and nothing upstream.
At this rate, I am just trying to find some piece of mind. ---agreed. Its frustrating when you're stuck between the ISP and your own hardware. is the modem still in warranty? If the spectrum device does work fine, you could get it replaced. click on "Mynetgear" at the top. register an account and the device. from there you can check warranty status.
Thank you again