Time |
Priority |
Description |
Sun Aug 06 10:03:52 2023 |
Warning (5) |
Dynamic Range Window violation |
Sun Aug 06 10:03:52 2023 |
Warning (5) |
RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Sun Aug 06 08:57:18 2023 |
Warning (5) |
Dynamic Range Window violation |
Sun Aug 06 08:57:18 2023 |
Warning (5) |
RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTD;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Sun Aug 06 08:53:38 2023 |
Warning (5) |
Dynamic Range Window violation |
Sun Aug 06 08:53:38 2023 |
Warning (5) |
RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Sun Aug 06 08:52:48 2023 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Sun Aug 06 05:22:39 2023 |
Warning (5) |
Dynamic Range Window violation |
Sun Aug 06 05:22:39 2023 |
Warning (5) |
RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Sun Aug 06 05:22:39 2023 |
Warning (5) |
Dynamic Range Window violation |
Sun Aug 06 05:22:39 2023 |
Warning (5) |
RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Sun Aug 06 01:36:42 2023 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Sun Aug 06 01:36:09 2023 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Sun Aug 06 01:34:36 2023 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Sun Aug 06 01:34:07 2023 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Sat Aug 05 19:21:22 2023 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Sat Aug 05 19:20:55 2023 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Sat Aug 05 19:12:44 2023 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Sat Aug 05 19:12:11 2023 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Sat Aug 05 19:10:17 2023 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=REDACTEDCMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Sat Aug 05 19:09:05 2023 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Sat Aug 05 18:35:40 2023 |
Warning (5) |
Dynamic Range Window violation |
Sat Aug 05 18:35:40 2023 |
Warning (5) |
RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Sat Aug 05 18:35:40 2023 |
Warning (5) |
Dynamic Range Window violation |
Sat Aug 05 18:35:40 2023 |
Warning (5) |
RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Sat Aug 05 17:07:49 2023 |
Warning (5) |
Dynamic Range Window violation |
Sat Aug 05 17:07:49 2023 |
Warning (5) |
RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Sat Aug 05 17:07:49 2023 |
Warning (5) |
Dynamic Range Window violation |
Sat Aug 05 17:07:49 2023 |
Warning (5) |
RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Sat Aug 05 16:57:30 2023 |
Warning (5) |
Dynamic Range Window violation |
Sat Aug 05 16:57:30 2023 |
Warning (5) |
RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Sat Aug 05 15:46:37 2023 |
Warning (5) |
Dynamic Range Window violation |
Sat Aug 05 15:46:37 2023 |
Warning (5) |
RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Sat Aug 05 15:16:00 2023 |
Warning (5) |
Dynamic Range Window violation |
Sat Aug 05 15:16:00 2023 |
Warning (5) |
RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Sat Aug 05 13:36:29 2023 |
Warning (5) |
Dynamic Range Window violation |
Sat Aug 05 13:36:29 2023 |
Warning (5) |
RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Sat Aug 05 13:36:29 2023 |
Warning (5) |
Dynamic Range Window violation |
Sat Aug 05 13:36:29 2023 |
Warning (5) |
RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTEDCMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1; |
Sat Aug 05 13:23:10 2023 |
Warning (5) |
Dynamic Range Window violation |
EG
Expert
•
111.3K Messages
2 years ago
@user_79617b
Please redact all of the CM MAC and the CMTS MAC addresses from 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".
That said. 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.
In an effort to try to obtain better connectivity / more wiggle room, check to see if there are there any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1000 MHz, bi-directional, and no gold colored garbage from Home Depot, Target, Wal-Mart, etc. Splitters should be swapped with known to be good / new ones to test.
Also check the coax cable for any damage such as cuts, nicks, abrasions, kinks, sharp bends, etc.
If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two-way splitter connected directly off of the drop from the street / pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.
2
EG
Expert
•
111.3K Messages
2 years ago
@user_79617b
You're quite welcome ! Yes. More needs to be done. There's no wiggle room to allow for those inevitable intermittent signal power fluctuations.
So if there is nothing more that can be done by you to improve the connection quality, then you'll need to get the techs re-involved until things get fixed properly.
Bear in mind that if the premises facing techs can not find or fix a problem at your home, it is they who are responsible for escalating it to their line / network / maintenance dept. techs. The problem may lie beyond your home in the local neighborhood infrastructure somewhere but it is their S.O.P. to start at the home. And if the problem is found to be on their side of the demarcation point, there will not be any charge.
Good luck !
1
0
EG
Expert
•
111.3K Messages
2 years ago
My pleasure ! Good luck with this ! Please post back here with how things turn out.
0
0
XfinityJustinC
Official Employee
•
1.4K Messages
2 years ago
Hello, @user_79617b. Thank you for reaching out over Xfinity Forums, you have reached out to the right place for assistance. I appreciate all the detailed information you have provided, and completely understand where you're coming from in regard to needing a solid internet connection as I work from home as well.
I would like to ensure that you're able to get this corrected, and see you were working with someone over the phone. If you're still needing help, please send a DM with the requested information as we don't want that in a public conversation:
To send a direct message:
Click "Sign In" if necessary
• Click the "Direct Message" icon in the upper right - it looks like a chat bubble
• Click the "New message" (pencil and paper) icon just to the right of Conversations
• Type "Xfinity Support" in the "To:" line - do not use the Employee's name!
• Type your message in the text area near the bottom of the window
• Press Enter to send it
To expedite your request, we ask that you please include your name, the account holder name (if different), and the service address.
0
0