| Time |
Priority |
Description |
| 1970-1-1, 00:00:46 |
Notice (6) |
Honoring MDD; IP provisioning mode = IPv6 |
| 1970-1-1, 00:00:40 |
Notice (6) |
WiFi Interface [wl1] set to Channel 153 (Side-Band Channel:N/A) - Reason:INIT |
| 1970-1-1, 00:00:40 |
Notice (6) |
WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INIT |
| 1970-1-1, 00:00:37 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing; |
| 2023-7-19, 14:04:36 |
Critical (3) |
Resetting the cable modem due to docsDevResetNow |
| 2023-7-19, 13:22:55 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
| 2023-7-19, 13:21:49 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
| 2023-7-19, 11:15:07 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
| 2023-7-19, 11:14:02 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
| 2023-7-19, 09:18:15 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
| 2023-7-19, 09:17:09 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
| 2023-7-19, 05:20:22 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
| 2023-7-19, 03:22:20 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
| 2023-7-19, 03:21:15 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
| 2023-7-19, 01:21:15 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
| 2023-7-19, 01:20:10 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
| 2023-7-18, 23:15:22 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
| 2023-7-18, 23:14:17 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
| 2023-7-18, 21:22:20 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
| 2023-7-18, 21:21:16 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
| 2023-7-18, 19:16:10 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
| 2023-7-18, 19:15:05 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
| 2023-7-18, 17:24:01 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
| 2023-7-18, 17:22:56 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
| 2023-7-18, 15:23:48 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
| 2023-7-18, 15:22:43 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
| 2023-7-18, 11:11:19 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
| 2023-7-18, 09:21:51 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
| 2023-7-18, 09:20:46 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
| 2023-7-18, 07:15:19 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
| 2023-7-18, 05:24:23 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
| 2023-7-18, 05:23:18 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
| 2023-7-18, 03:21:32 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
| 2023-7-18, 03:20:27 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
| 2023-7-18, 01:16:35 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
| 2023-7-17, 23:23:29 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
| 2023-7-17, 23:22:24 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
| 2023-7-17, 21:24:02 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
| 2023-7-17, 21:22:57 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
| 2023-7-17, 19:24:44 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
EG
Expert
•
110.3K Messages
2 years ago
@jgagliardi2
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".
1
0
EG
Expert
•
110.3K Messages
2 years ago
No worries ! This may or may not be the root cause of the problem (YMMV) but it should be addressed regardless.
The downstream power is indeed on the high side. It may be over-driving the front-end receiver circuit of the modem. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.
Is there a drop amplifier on the coax cable line leading to the modem ? If so, try removing / bypassing it and see. If not, you can try installing a -6 dB forward path-only attenuator pad such as this one on the coax port on the rear of the modem to knock that power level down and see;
https://www.amazon.com/FPA6-54-Forward-Attenuator-DOCSIS-Internet/dp/B08KTRC3XZ
It won't affect the upstream power level which is within spec.
What is the exact make and model number of the modem / gateway device ?
Is this with a WiFi connection ? If so, as a test, does a computer / device that is hardwired directly to the router / gateway device with an ethernet cable have the same intermittent internet connection problem ?
With this test, we are trying to isolate this down to being either a WiFi-only problem or a problem with the general connection to the Comcast system which would of course affect both.
(edited)
1
0