Read the forum guidelines
Cox Core Technology Tech has been out to verify no issue with my modem or wiring. He said there is issue with noise in the signal. He sent a Field Service Technician out. Unfortunately before he could research, he was called away to an outage in another part of Phoenix. Before he departed, he left a note that said "There is a neighborhood issue related to noise/ingress. It is usually from homes" He said he'd be back that day or the next to research and fix. That was nearly a week ago and I haven't heard anything.
I called Cox yesterday to inquire. They sent a representative out this morning. He wasn't a field service person, and only told me that he was aware of tickets open in the neighborhood but couldn't give me any information on when the issue may be fixed. He left after a five minute conversation.
Hoping a Cox representative may be able to research and provide more information on what's going on and the expected resolution time. I've pasted some information from my cable modem for review by those who may be knowledgable in that regard. Any help is appreciated in advance. (Note: I last rebooted about 14:30)
Mar 21 2023 07:50:09 Notice (6) US profile assignment change. US Chan ID: 6Mar 21 2023 07:50:09 Notice (6) US profile assignment change. US Chan ID: 6Mar 21 2023 07:50:09 Notice (6) US profile assignment change. US Chan ID: 6Mar 21 2023 07:50:09 Notice (6) US profile assignment change. US Chan ID: 6Mar 21 2023 07:50:09 Notice (6) US profile assignment change. US Chan ID: 6Mar 21 2023 07:50:09 Notice (6) US profile assignment change. US Chan ID: 6Mar 21 2023 07:50:09 Notice (6) US profile assignment change. US Chan ID: 6Mar 21 2023 07:50:09 Notice (6) US profile assignment change. US Chan ID: 6Mar 21 2023 07:50:09 Notice (6) US profile assignment change. US Chan ID: 6Mar 21 2023 07:57:45 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRWMar 21 2023 08:01:33 Notice (6) US profile assignment change. US Chan ID: 6Mar 21 2023 08:20:50 Notice (6) CM-STATUS message sent. Event Type Code: 24Mar 21 2023 08:27:47 Notice (6) US profile assignment change. US Chan ID: 6Mar 21 2023 08:52:41 Critical (3) No Ranging Response received - T3 time-outMar 21 2023 08:57:50 Notice (6) US profile assignment change. US Chan ID: 6Mar 21 2023 09:04:18 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRWMar 21 2023 09:12:00 Notice (6) US profile assignment change. US Chan ID: 6Mar 21 2023 09:55:54 Critical (3) No Ranging Response received - T3 time-outMar 21 2023 09:58:24 Notice (6) US profile assignment change. US Chan ID: 6Mar 21 2023 10:06:12 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRWMar 21 2023 10:10:33 Notice (6) US profile assignment change. US Chan ID: 6Mar 21 2023 10:52:48 Critical (3) No Ranging Response received - T3 time-outMar 21 2023 10:53:44 Notice (6) US profile assignment change. US Chan ID: 6Mar 21 2023 11:03:07 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRWMar 21 2023 11:05:34 Notice (6) US profile assignment change. US Chan ID: 6Mar 21 2023 12:05:41 Critical (3) Unicast Ranging Received Abort Response - initializing MACMar 21 2023 12:05:41 Critical (3) No Ranging Response received - T3 time-outMar 21 2023 12:07:57 Critical (3) Unicast Ranging Received Abort Response - initializing MACMar 21 2023 12:07:57 Critical (3) No Ranging Response received - T3 time-outMar 21 2023 12:09:58 Notice (6) US profile assignment change. US Chan ID: 6Mar 21 2023 12:21:19 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRWMar 21 2023 12:23:11 Notice (6) US profile assignment change. US Chan ID: 6Mar 21 2023 13:23:38 Critical (3) Unicast Ranging Received Abort Response - initializing MACMar 21 2023 13:23:38 Critical (3) No Ranging Response received - T3 time-outMar 21 2023 13:32:39 Notice (6) US profile assignment change. US Chan ID: 6Mar 21 2023 13:38:12 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRWMar 21 2023 13:53:31 Critical (3) No Ranging Response received - T3 time-outMar 21 2023 13:54:59 Notice (6) US profile assignment change. US Chan ID: 6Mar 21 2023 14:03:50 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRWMar 21 2023 14:04:11 Notice (6) US profile assignment change. US Chan ID: 6Mar 21 2023 14:31:20 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1Mar 21 2023 14:31:20 Notice (6) TLV-11 - unrecognized OIDMar 21 2023 14:31:20 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11Mar 21 2023 14:31:24 Warning (5) REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided ValueMar 21 2023 14:31:24 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRWMar 21 2023 14:31:24 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRWMar 21 2023 14:31:34 Alert (2) CM Certificate ErrorMar 21 2023 14:36:44 Notice (6) US profile assignment change. US Chan ID: 6
Looks like T3 time-out errors, probably from the noise on the upstream the tech hasn't isolated yet. My guess is you got the upstream OFDM channel around the time you had these problems. I would suggest emailing Cox at cox.help@cox.com with your account info and a link to this thread and ask for a update. Hopefully someone will be able to track down a ticket number for the work. If not, they may have to start all over again.
Great, thanks for the input, I will email them.