Contributor

 • 

43 Messages

Monday, March 4th, 2024

Closed

Logged errors, upstream desync

Upstream light on Motorola MB8611 started blinking, around Feb 6th. Restarted the modem, cleared it up. Started again, randomly, over the next week. MB8611 event log caught it at 11:52:37 Tue Feb 13 2024 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=XX:XX:XX:XX:XX; CMTS-MAC=XX:XX:XX:XX:XX:XX; CM-QOS=1.1; CM-VER=3.1. Multiple errors logged rest of the day, on Feb 13 and on Feb 14, such as SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XX:XX:XX:XX:XX:XX:XX; CMTS-MAC=XX:XX:XX:XX:XX:XX; CM-QOS=1.1; CM-VER=3.1. No Ranging Response received - T3 timeout; CM-MAC=XX:XX:XX:XX:XX:XX:XX; CMTS-MAC=XX:XX:XX:XX:XX:XX; CM-QOS=1.1; CM-VER=3.1. Started Unicast Maintenance Ranging - No Response received - T3 timeout; CM-MAC=XX:XX:XX:XX:XX:XX:XX; CMTS-MAC=XX:XX:XX:XX:XX:XX; CM-QOS=1.1; CM-VER=3.1.

These errors continued, intermittently, until Feb 21, when a tech arrived, that I'd finally managed to get scheduled. He checked the signals on the coax, inside my apartment, found a splitter that he removed as it wasn't needed, discovered that the line that was in use was bad and swapped to the second pre-installed line to the wall plate. Checked the signals again and showed his handheld oscilloscope to me, to let me know that he'd gotten that problem dealt with. He went outside, checked the equipment boxes, replaced the underground cable, from those boxes out to the pedestal, as that cable was very old. At that point, everything looked good and I didn't have any more trouble until the next afternoon.

Timing Sync failure - Failed to acquire QAM-QSPK symbol timing; CM-MAC=XX:XX:XX:XX:XX:XX:XX; CMTS-MAC=XX:XX:XX:XX:XX:XX; CM-QOS=1.1; CM-VER=3.1 (Logged 3 consecutive times).

Next entry No Ranging Response received - T3 timeout; CM-MAC=XX:XX:XX:XX:XX:XX:XX; CMTS-MAC=XX:XX:XX:XX:XX:XX; CM-QOS=1.1; CM-VER=3.1 followed by SYNC Timing Synchronization failure - Loss of Sync; CM-MAC=XX:XX:XX:XX:XX:XX:XX; CMTS-MAC=XX:XX:XX:XX:XX:XX; CM-QOS=1.1; CM-VER=3.1. Happened at 13:26:49 Thu Feb 22.

At 13:32:43 entry reads Notice (6) DS profile assignement change. DS Chan ID:32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=XX:XX:XX:XX:XX:XX:XX; CMTS-MAC=XX:XX:XX:XX:XX:XX; CM-QOS=1.1; CM-VER=3.1.

Also at 13:32:43 entry reads SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=XX:XX:XX:XX:XX:XX:XX; CMTS-MAC=XX:XX:XX:XX:XX:XX; CM-QOS=1.1; CM-VER=3.1.

13:32:51 Thu Feb 22 2024 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW: CM-MAC=XX:XX:XX:XX:XX:XX:XX; CMTS-MAC=XX:XX:XX:XX:XX:XX; CM-QOS=1.1; CM-VER=3.1

13:32:51 Thu Feb 22 2024 Warning (5) Dynamic Range Window violation

Those two repeated numerous times. Tried explaining things to a few people via Live chat, via phone conversation, which resulted in several hours of wasted time and a large amount of frustration. I was promised, by 3 agents that I'd get a call back, another disconnected me, after having me on hold for nearly an hour. Late Friday afternoon, I called again, in hopes of getting someone that would actually listen. Didn't work out as I hoped. I agreed to pick up a Xfinity gateway and give it a try, which I did. Wound up with another headache, trying to get it (xb8) setup and running. Called support wanting to know the IP address, how to split the Wifi channels and why the 6GHz signal wasn't showing up. Got the IP address, tried to split the channels following directions given, to no avail and I gave up until Saturday. I did note that the event logs for the xb8 showed the same errors I had gotten on my Motorola MB8611. At least, until I wasn't able to access any log file but the system logs. No help there. Logged in on my Xfinity account, clicked on billing. It tried loading 5 times and I got a message that I'd been logged out. Tried the phone app, same result. Turned off wifi on my phone and was able to get into billing. At the same time all this is going on, I was getting errors logging into my Verizon account, as well. In the meantime, after being told by one person I spoke with to check with the manufacturer of my Motorola, I tried to find any current support info on it, only to find that Zoom Telephonics, the company that built had been merged into Minim and they had laid off 41 of 50 employees. When the Netgear CM2000 got here, this past Saturday (I'd ordered it, prior to picking up the xb8), I got it set up, activated and operating. Took a phone call to get thing straight on my account, so it would work at full speed. Imagine my dismay, when I check the event log of the CM2000 and find this:

Sat Mar 02 23:12:27 2024 (Warning (5)) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=xx:xx:xx:xx:xx:xx;;CMTS-MAC=xx:xx:xx:xx:xx:xx;;CM-QOS=1.1;CM-VER=3.1;

Can anyone tell me what is going on? Of the three techs that have been here, only the first one actually did anything. The third one told me that he'd check the pedestal, called his boss and talked to him and said his boss told him that it was likely a microwave oven causing the problem or electrical wiring feedback. The former is likely to slow roast anyone near a microwave and the latter tells me there's a bad ground, belonging to Xfinity and possibly one belonging to Duke Energy. Neither of which I can fix. Apartment maintenance told me that they can't touch Duke's equipment, not even to reconnect a loose ground wire to a ground rod.

I need some help, please. Apologies for the font change, it wasn't intentional and I can't change it back, to what it was.

Oldest First
Selected Oldest First

Gold Problem Solver

 • 

26.7K Messages

2 years ago

... xb8 ... MB8611 ... CM2000 ...

Signal problems like the ones you are seeing are rarely due to a bad modem or gateway, they're almost always due to a problem with the connection between that device and Comcast's network, usually in or near your home, less often further upstream in Comcast's equipment. Unfortunately such problems are often intermittent and hard to track down.

You're welcome to review Internet Troubleshooting Tips to see if there is anything helpful, but I suspect you are stuck with leaning on Comcast as hard as you can until they figure out the problem and correct it. If an employee does not respond to your message here, keep at them until they provide competent technical help for the trouble you are having. The page at https://www.xfinity.com/hub/customer-experience/xfinity-customer-care-update links to the "contact me/Send Tom Feedback" form at https://support.xfinity.com/svp-contact-form and might be worth a try.

Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.

Contributor

 • 

43 Messages

Thanks for replying. I read through the troubleshooting tips, to see if I'd missed anything that I could to to mitigate things, given the restrictions of the apartment complex owners policy that residents can't run new coax cables or have their ISP do it. Didn't miss anything. I did upgrade my ethernet cables from cat 6 utp to cat 6a stp. Computer, modem and router are plugged into an APC 1500 Backup-UPS, so induced noise via electrical lines is nil. Before I click on those links, I'll wait to see if any official Xfinity people respond.

Official Employee

 • 

1.7K Messages

Hi there @user_u1aaq0 ! As @BruceW mentioned, these results usually point to a connection issue. Reading through your comments, it sounds like we should re-evaluate the signal levels and go from there. Please send a direct message to us by clicking the chat icon in the upper right corner of the page, click on the pen and paper icon, then enter “Xfinity Support” in the “To” section. Please include your full name and complete street address to get started. Thanks! 

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick

Contributor

 • 

43 Messages

Name and address given. Referenced this post, for background info.

Contributor

 • 

43 Messages

2 years ago

More errors: Tue Mar 05 00:14:57 2024 (Warning (5))  RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Mar 04 18:46:13 2024 (Notice (6))  CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 6 7 8 9 10 11 12 13 14 15 16 17 18 19 33 34 35 36 37 38 39 40 41 42 43 44 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Mar 04 18:45:13 2024 (Critical (3))  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Mon Mar 04 18:45:06 2024 (Warning (5))  MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;

Contributor

 • 

43 Messages

2 years ago

Appointment scheduled for tomorrow afternoon, 3-5pm. Weather may be a factor, though.

Official Employee

 • 

1.7K Messages

Thanks for the update @user_u1aaq0 ! If for some reason there is an issue with the visit we can reschedule. Don't forget the appointment management link I shared in private chat : https://www.xfinity.com/support/articles/xfinity-my-account-app-manage-appointments or reach out to us in that private conversation for assistance if needed. As I mentioned, we will be circling back with you after the visit as well to see how it went. 

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick

Contributor

 • 

43 Messages

@XfinityFrank, Sent DM. Technician at a loss to nail down reason for continued RNG-RSP CCAP errors, which were being followed by DRW violation, on the MB8611. That one isn't showing up on the CM2000. Contacted apartment manager. Will advise further.

Contributor

 • 

43 Messages

Got a call from Comcast Executive Care, last night. Discussed the problems with the gentleman, informed him that I'd been in contact with the manager. He's going to call her, today or tomorrow and I'm waiting to hear from one or the other of them, presently. Cleared the modems event log, a few hours ago and not long after, I got another RNG-RSP CCAP error.

Contributor

 • 

43 Messages

More and different errors.

Fri Mar 08 02:32:23 2024 (Notice (6))  CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 6 7 8 9 10 11 12 13 14 15 16 17 18 19 33 34 35 36 37 38 39 40 41 42 43 44 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 08 02:32:03 2024 (Notice (6))  CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 08 02:31:55 2024 (Notice (6))  CM-STATUS message sent. Event Type Code: 22; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 08 02:31:54 2024 (Notice (6))  CM-STATUS message sent. Event Type Code: 23; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 08 02:31:44 2024 (Critical (3))  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 08 02:31:11 2024 (Warning (5))  MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 08 00:33:49 2024 (Warning (5))  RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;

Contributor

 • 

43 Messages

I'm having a hard time believing these errors are being caused by a sketchy coax cable.

forum icon

New to the Community?

Start Here