|
Time |
|
Priority |
|
Description |
|
Time Not Established |
|
Critical (3) |
|
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:4:c1;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
|
Time Not Established |
|
Critical (3) |
|
No Ranging Response received - T3 time-out;CM-MAC=00:4:c1;CMTS-MAC=CM-QOS=1.1;CM-VER=3.1; |
|
Time Not Established |
|
Critical (3) |
|
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00::c1;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
|
Time Not Established |
|
Critical (3) |
|
No Ranging Response received - T3 time-out;CM-MAC=00::c1;CMTS-MAC=QOS=1.1;CM-VER=3.1; |
|
Time Not Established |
|
Critical (3) |
|
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:c1;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
|
Time Not Established |
|
Critical (3) |
|
No Ranging Response received - T3 time-out;CM-MAC=00::c1;CMTS-MAC=0-QOS=1.1;CM-VER=3.1; |
|
Time Not Established |
|
Critical (3) |
|
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:4:c1;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
|
Time Not Established |
|
Critical (3) |
|
No Ranging Response received - T3 time-out;CM-MAC=00::c1;CMTS-MAC;CM-QOS=1.1;CM-VER=3.1; |
|
Time Not Established |
|
Critical (3) |
|
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=:c1;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
|
Time Not Established |
|
Critical (3) |
|
No Ranging Response received - T3 time-out;CM-MAC=00:c1;CMTS-MAC=-QOS=1.1;CM-VER=3.1; |
|
Time Not Established |
|
Critical (3) |
|
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00c1;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
|
Time Not Established |
|
Critical (3) |
|
No Ranging Response received - T3 time-out;CM-MAC=0:c1;CMTS-MAC=CM-QOS=1.1;CM-VER=3.1; |
|
Time Not Established |
|
Critical (3) |
|
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00c1;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
|
Time Not Established |
|
Critical (3) |
|
No Ranging Response received - T3 time-out;CM-MAC=00::c1;CMTS-MAC=CM-QOS=1.1;CM-VER=3.1; |
|
Time Not Established |
|
Critical (3) |
|
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:c1;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
|
Time Not Established |
|
Critical (3) |
|
No Ranging Response received - T3 time-out;CM-MAC=00:c1;CMTS-MAC;CM-QOS=1.1;CM-VER=3.1; |
|
Time Not Established |
|
Critical (3) |
|
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00c1;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
|
Time Not Established |
|
Critical (3) |
|
No Ranging Response received - T3 time-out;CM-MAC=0c1;CMTS-MAC=CM-QOS=1.1;CM-VER=3.1; |
|
Time Not Established |
|
Critical (3) |
|
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:c1;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
|
Time Not Established |
|
Critical (3) |
|
No Ranging Response received - T3 time-out;CM-MAC=00c1;CMTS-MAC=M-QOS=1.1;CM-VER=3.1; |
|
Time Not Established |
|
Critical (3) |
|
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=0c1;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
|
Time Not Established |
|
Critical (3) |
|
No Ranging Response received - T3 time-out;CM-MAC=00::c1;CMTS-MAC=0CM-QOS=1.1;CM-VER=3.1; |
|
Time Not Established |
|
Critical (3) |
|
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=c1;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
|
Time Not Established |
|
Critical (3) |
|
No Ranging Response received - T3 time-out;CM-MAC=00c1;CMTS-MAC=CM-QOS=1.1;CM-VER=3.1; |
|
Time Not Established |
|
Critical (3) |
|
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:c1;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
|
Time Not Established |
|
Critical (3) |
|
No Ranging Response received - T3 time-out;CM-MAC=c1;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
|
Time Not Established |
|
Critical (3) |
|
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:c1;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
|
Time Not Established |
|
Critical (3) |
|
No Ranging Response received - T3 time-out;CM-MAC=00::c1;CMTS-MAC=M-QOS=1.1;CM-VER=3.1; |
|
Time Not Established |
|
Notice (6) |
|
Honoring MDD; IP provisioning mode = IPv6 |
|
19:29:29 Fri Jan 14 2022 |
|
Notice (6) |
|
DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=0:c1;CMTS-MACQOS=1.1;CM-VER=3.1; |
|
19:29:45 Fri Jan 14 2022 |
|
Notice (6) |
|
CM-STATUS message sent. Event Type Code: 24; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;CM-MACCMTS-MAC=CM-QOS=1.1;CM-VER=3.1; |
terp67
Visitor
•
16 Messages
3 years ago
0
0
EG
Expert
•
110.2K Messages
3 years ago
Please redact all of the CM MAC and the CMTS MAC addresses in your error log entries for your privacy. They are considered to be personal information. Personally identifying 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".
2
0
EG
Expert
•
110.2K Messages
3 years ago
Yep. In the second example, the SNR's are indeed too low / out of spec. It appears that there is intermittent noise ingress into the line(s) somewhere. 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 connection quality, 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 Radio Shack, Home Depot, Target, 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, 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.
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.
Good luck !
(edited)
9
0
terp67
Visitor
•
16 Messages
3 years ago
SNR improved. Upstream power still below 30
2
0
terp67
Visitor
•
16 Messages
3 years ago
Well, new - new motorola mb8611 seems to be doing better, or some changes were made on Comcast's end. The biggest difference I see is the increase in downstream power. I still see some t-3 time outs, and synch failures.....but the modem has not reset yet, going on 14 hours.
4
0
terp67
Visitor
•
16 Messages
3 years ago
So to recap. I had a month old mb8611 and was having issues. Tech visited and replaced connections from tap to modem. Still had modem refreshes. Contacted Amazon, they sent out replacement mb8611. In the meantime, we connected the Comcast gateway that I had not returned yet.......still had drops. I connected the brand new mb8611 yesterday and the connection numbers posted today are from that. Here is the event log. Comcast is sending a tech again today.
Fri Jan 21 2022
Fri Jan 21 2022
Fri Jan 21 2022
Fri Jan 21 2022
Sat Jan 22 2022
Sat Jan 22 2022
Sat Jan 22 2022
Sat Jan 22 2022
Sat Jan 22 2022
Sat Jan 22 2022
0
0
terp67
Visitor
•
16 Messages
3 years ago
Glad I didn't cancel the tech visit for today. Bad tap. Service ticket is in and they will come out in the next few weeks to work on the tap. Hopefully that does it.
0
0
EG
Expert
•
110.2K Messages
3 years ago
Good luck ! Please post back With how things turn out.
0
0
terp67
Visitor
•
16 Messages
3 years ago
I hadn't heard anything from Comcast about the ticket to replace the tap, so I reached out the other day. They suggested a third tech visit to hopefully get things moving along. Well, third times the charm. An actual Xfinity technician, not a contractor, came out this morning and tested everything out again. I have a long driveway....over 1000feet, so a line comes in underground from the road and goes to a pedestal about 100feet from the house. The line from the pole to the tap was fine, tap was bad at the pedestal, and the line underground from the tap to the house was bad. The service technician called in to maintenance to have the tap repaired. So, a maintenance tech came and made that repair and also swapped out an amp on one of the poles down the road. The service tech ran a new line (will need to get buried at some point) from the tap to the house, replace the connection box on the outside of the house, and ran a new line from that box all the way to the modem. A supervisor also came out and checked everything over. Looking at the numbers now, the downstream power is above 0, and the upstream power is now above 40. It seems that all is well and my service should no longer be interrupted.
On a side note, Xfinity needs to address the call center (1-855-433-2886) technicians calling to try and cancel appointments. Ahead of the second tech visit, and again ahead of the third visit, someone called from Xfinity to suggest that the problem had been fixed and I shouldn't need an appointment. These same people suggested previously that my modem was the problem, which prompted me to exchange a month old modem. I knew that xfinity had not been out to fix the tap and that my numbers were out of spec, so why would they call and suggest otherwise?
1
0