| |
Time |
|
Priority |
|
Description |
| |
08:33:15
Mon Dec 18 2023 |
|
Critical (3) |
|
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; |
| |
11:59:58
Mon Dec 18 2023 |
|
Critical (3) |
|
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; |
| |
12:00:32
Mon Dec 18 2023 |
|
Critical (3) |
|
No Ranging Response received - T3 time-out; |
| |
12:00:32
Mon Dec 18 2023 |
|
Critical (3) |
|
Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
| |
12:00:52
Mon Dec 18 2023 |
|
Critical (3) |
|
No Ranging Response received - T3 time-out; |
| |
16:21:18
Mon Dec 18 2023 |
|
Critical (3) |
|
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; |
| |
16:21:27
Mon Dec 18 2023 |
|
Critical (3) |
|
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; |
| |
16:22:25
Mon Dec 18 2023 |
|
Critical (3) |
|
No Ranging Response received - T3 time-out; |
| |
16:23:02
Mon Dec 18 2023 |
|
Critical (3) |
|
Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
| |
16:23:05
Mon Dec 18 2023 |
|
Critical (3) |
|
Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
| |
Time Not Established |
|
Critical (3) |
|
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; |
| |
Time Not Established |
|
Notice (6) |
|
Honoring MDD; IP provisioning mode = IPv6 |
| |
16:20:27
Thu Mar 7 2024 |
|
Notice (6) |
|
DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3. |
| |
16:20:32
Thu Mar 7 2024 |
|
Warning (5) |
|
REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value; |
| |
16:20:32
Thu Mar 7 2024 |
|
Warning (5) |
|
RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW; |
| |
16:20:32
Thu Mar 7 2024 |
|
Warning (5) |
|
Dynamic Range Window violation |
| |
16:55:07
Thu Mar 7 2024 |
|
Notice (6) |
|
CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.; |
| |
16:55:38
Thu Mar 7 2024 |
|
Notice (6) |
|
CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.; |
| |
16:55:47
Thu Mar 7 2024 |
|
Notice (6) |
|
CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.; |
| |
16:56:15
Thu Mar 7 2024 |
|
Notice (6) |
|
CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.; |
| |
16:56:29
Thu Mar 7 2024 |
|
Notice (6) |
|
CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.; |
| |
16:57:00
Thu Mar 7 2024 |
|
Notice (6) |
|
CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.; |
| |
17:27:45
Thu Mar 7 2024 |
|
Notice (6) |
|
CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.; |
| |
17:28:17
Thu Mar 7 2024 |
|
Notice (6) |
|
CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.; |
| |
17:35:53
Thu Mar 7 2024 |
|
Notice (6) |
|
CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.; |
| |
17:36:21
Thu Mar 7 2024 |
|
Notice (6) |
|
CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.; |
| |
18:03:48
Thu Mar 7 2024 |
|
Notice (6) |
|
CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.; |
| |
18:04:15
Thu Mar 7 2024 |
|
Notice (6) |
|
CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.; |
| |
20:42:25
Thu Mar 7 2024 |
|
Notice (6) |
|
CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.; |
| |
20:42:56
Thu Mar 7 2024 |
|
Notice (6) |
|
CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.; |
| |
22:59:04
Thu Mar 7 2024 |
|
Notice (6) |
|
CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.; |
| |
22:59:32
Thu Mar 7 2024 |
|
Notice (6) |
|
CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.; |
user_b0a114
Visitor
•
5 Messages
1 year ago
Here's the low down with a Motorola MB8611
0
0
BruceW
Gold Problem Solver
•
26.5K Messages
1 year ago
Whoosh! All the downstream power levels and SNR values are way out of spec (too low). This usually indicates a problem with the link between your modem and Comcast's network, and is likely responsible for most of the event log entries as well. The cause is often poor coax connections or damaged coax cable, usually in or near your home. Running the cable through a surge protector, a defective splitter, or too many splitters can cause signal problems as well. If there is an amplifier in the line make sure it's getting power.
If you want to troubleshoot this yourself, please see Internet Troubleshooting Tips.
If you can't find the problem or you'd rather have Comcast take care of it and an employee does not respond to your message here, call them at the phone number on your bill or 1-800-Comcast, or use one of the options on https://www.xfinity.com/support/contact-us/. It's not likely they can fix the problem remotely. If not, insist they send a tech out to identify the cause and correct it.
If the tech finds bad coax, splitters, amplifiers, or connections in your home (even if Comcast originally supplied them) you'll probably have to pay for the visit (approx $100) unless you have their Service Protection Plan ( https://www.xfinity.com/support/articles/service-protection-plan, closed to customers that don't already have it). If the trouble is due to a faulty Comcast rental device or anything outside your home you shouldn't be charged.
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.
2
BruceW
Gold Problem Solver
•
26.5K Messages
1 year ago
Unfortunately connection problems are often intermittent and hard to track down, but $100 billion dollar corporations have lots of resources they can bring to bear if properly motivated. If Internet Troubleshooting Tips doesn't help you are pretty much stuck with leaning on Comcast 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 which 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.
0
0
user_b0a114
Visitor
•
5 Messages
1 year ago
Thanks again @BruceW . Another technician came by and replaced some wiring on the outside of the house. Seems like things are working now...
1