2 Messages
Motorola MB8611 keeps loosing connection.
I have a Motorola MB8611, and have been at this address for 2 years (I bought the modem new when we moved in). This last year I noticed a few times when the internet would drop out, but not enough to investigate. In the last month, it started dropping out more and more. After some investigation with my router and finding no issues, I did some searching online and realized that the modem could be the problem. The next time the internet went out, I checked and my modem appeared to have rebooted and was going through the setup procedure (connecting upstream, downstream, etc). I took a look at the status page, and saw some logged errors. Based on previous forum and reddit posts I did some re-wiring and removed a splitter outside. Now the cable goes directly into the room with the modem. That seemed to help. it went from ~2 disconnects per hour to going several hours without a restart. That was yesterday. But today I've had quite a few restarts in the morning. The Connection Info page seems to indicate everything is in range (although the uncorrected numbers are higher today than usual. Most of the time the QAM256 channels are all at 0). But I also can't connect to the page as the modem is re-connecting, so I can't see if the levels spike or drop around the time of the outage. I figured I'd post here to see if someone more knowledgeable has any tips before getting a service call. One other note: outside of the restarts, the internet works great and I'm getting the speeds I pay for.
Connection Page:
|
||||||||||||||||||||||||
|
|
||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
|
Event Log
(around the time of the most recent outage):
09:38:05 Tue Jan 14 2025 |
Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=<redact>;CMTS-MAC=<redact>;CM-QOS=1.1;CM-VER=3.1; | |||
09:38:07 Tue Jan 14 2025 |
Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=<redact>;CMTS-MAC=<redact>;CM-QOS=1.1;CM-VER=3.1; | |||
09:40:27 Tue Jan 14 2025 |
Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=<redact>;CMTS-MAC=<redact>;CM-QOS=1.1;CM-VER=3.1; | |||
09:40:40 Tue Jan 14 2025 |
Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<redact>;CMTS-MAC=<redact>;CM-QOS=1.1;CM-VER=3.1; | |||
09:40:41 Tue Jan 14 2025 |
Warning (5) | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=<redact>;CMTS-MAC=<redact>;CM-QOS=1.1;CM-VER=3.1; | |||
09:40:41 Tue Jan 14 2025 |
Warning (5) | Dynamic Range Window violation | |||
09:40:42 Tue Jan 14 2025 |
Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<redact>;CMTS-MAC=<redact>;CM-QOS=1.1;CM-VER=3.1; | |||
09:40:56 Tue Jan 14 2025 |
Warning (5) | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=<redact>;CMTS-MAC=<redact>;CM-QOS=1.1;CM-VER=3.1; | |||
09:40:56 Tue Jan 14 2025 |
Warning (5) | Dynamic Range Window violation | |||
09:40:58 Tue Jan 14 2025 |
Warning (5) | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=<redact>;CMTS-MAC=<redact>;CM-QOS=1.1;CM-VER=3.1; | |||
09:40:58 Tue Jan 14 2025 |
Warning (5) | Dynamic Range Window violation | |||
09:41:38 Tue Jan 14 2025 |
Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=<redact>;CMTS-MAC=<redact>;CM-QOS=1.1;CM-VER=3.1; | |||
09:41:41 Tue Jan 14 2025 |
Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<redact>;CMTS-MAC=<redact>;CM-QOS=1.1;CM-VER=3.1; | |||
09:42:08 Tue Jan 14 2025 |
Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 2 3.;CM-MAC=<redact>;CMTS-MAC=<redact>;CM-QOS=1.1;CM-VER=3.1; |
XfinityThomasB
Official Employee
•
2K Messages
5 months ago
Inspector_E
Could you please send our team a direct message with your full name and full address? Our team can most definitely take a further look at this issue.
To send a Direct message:
Click "Sign In" if necessary
• Click the "Direct Message" icon
• Click the "New message" (pencil and paper) icon
• Type "Xfinity Support" in the "To:" line and select "Xfinity Support" from the drop-down list which appears.
0
EG
Expert
•
110.8K Messages
5 months ago
@Inspector_E @XfinityThomasB
Please circle back here and post any possible solutions for the issue here in these open public forums so that all readers here may benefit from the exchange / info. This is in keeping with the spirit for which these public help forums were originally intended. Thank you.
0
Inspector_E
2 Messages
4 months ago
Update:
Support said that they would create an escalated repair ticket to the advanced repair team. They said the advanced repair team may reach out by text if they have any questions. I haven't heard from them yet. The dropouts seem to be much less common, but definitely still come up about once per day. They also resolve much faster (usually within a minute). Usually they happen very early in the morning or late at night. But a couple of times it has happened in the middle of a work meeting which is quite frustrating. If this happens regularly I will reach out to support again.
0
0