1 Message
Intermittent T3 and T4 Time-Outs
I have a Motorola MB8600 modem and have been experiencing intermittent connectivity for the past two weeks. The power and signal-to-noise ratio are within expected parameters, but there are critical errors in the logs. Before this, the setup was working flawlessly, aside from the occasional outage.
| Time | Priority | Description |
| 3/29/25 8:42 AM | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out |
| 3/29/25 8:42 AM | Critical (3) | No Ranging Response received - T3 time-out |
| 3/29/25 8:42 AM | Notice (6) | CM-STATUS message sent. Event Type Code: 20 |
| 3/29/25 8:42 AM | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out |
| 3/29/25 8:42 AM | Critical (3) | No Ranging Response received - T3 time-out |
| 3/29/25 8:42 AM | Critical (3) | No Ranging Response received - T3 time-out |
| 3/29/25 8:42 AM | Critical (3) | No Ranging Response received - T3 time-out |
| 3/29/25 8:42 AM | Notice (6) | CM-STATUS message sent. Event Type Code: 20 |
| 3/29/25 8:42 AM | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out |
| 3/29/25 8:42 AM | Notice (6) | CM-STATUS message sent. Event Type Code: 20 |
| 3/29/25 8:41 AM | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out |
| 3/29/25 8:39 AM | Notice (6) | CM-STATUS message sent. Event Type Code: 16 |
| 3/29/25 8:34 AM | Notice (6) | CM-STATUS message sent. Event Type Code: 20 |
| 3/29/25 8:32 AM | Critical (3) | UCD invalid or channel unusable |
| 3/29/25 8:22 AM | Warning (5) | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW |
| 3/29/25 8:22 AM | Warning (5) | Dynamic Range Window violation |
| 3/29/25 8:22 AM | Warning (5) | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW |
| 3/29/25 8:22 AM | Warning (5) | Dynamic Range Window violation |
| 3/29/25 8:22 AM | Warning (5) | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW |
| 3/29/25 8:22 AM | Warning (5) | Dynamic Range Window violation |
| 3/29/25 8:22 AM | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out |
| 3/29/25 8:19 AM | Critical (3) | UCD invalid or channel unusable |
| 3/29/25 8:19 AM | Notice (6) | DS profile assignment change. DS Chan ID: 33 |
| 3/29/25 8:19 AM | Notice (6) | DS profile assignment change. DS Chan ID: 32 |
| 3/29/25 8:19 AM | Critical (3) | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.2, 108MHz. |
| 3/29/25 8:19 AM | Critical (3) | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.3, 1002MHz. |
| 3/29/25 8:19 AM | Critical (3) | CMSTATUS:US_Diplexer_Mode_Change:TLV-84.1, 5-42MHz. |
| 3/29/25 8:18 AM | Notice (6) | Honoring MDD |
| 3/29/25 8:18 AM | Critical (3) | UCD invalid or channel unusable |
| 3/29/25 8:18 AM | Critical (3) | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.2, 258MHz. |
| 3/29/25 8:18 AM | Critical (3) | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.3, 1002MHz. |
| 3/29/25 8:18 AM | Critical (3) | CMSTATUS:US_Diplexer_Mode_Change_Ignored:TLV-21.1, 85MHz. |
| 3/29/25 8:18 AM | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing |
| 3/29/25 8:18 AM | Critical (3) | CMSTATUS:US_Diplexer_Mode_Change:TLV-84.1, 5-42MHz. |
| 3/29/25 8:18 AM | Critical (3) | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.2, 108MHz. |
| 3/29/25 8:18 AM | Critical (3) | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.3, 1002MHz. |
| 3/29/25 8:18 AM | Notice (6) | Honoring MDD |
| 3/29/25 8:18 AM | Critical (3) | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.2, 258MHz. |
| 3/29/25 8:18 AM | Critical (3) | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.3, 1002MHz. |
| 3/29/25 8:18 AM | Critical (3) | CMSTATUS:US_Diplexer_Mode_Change:TLV-21.1, 5-85MHz. |
| 3/29/25 8:18 AM | Warning (5) | Lost MDD Timeout |
| 3/29/25 8:18 AM | Critical (3) | CMSTATUS:US_Diplexer_Mode_Change:TLV-84.1, 5-42MHz. |
| 3/29/25 8:18 AM | Critical (3) | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.2, 108MHz. |
| 3/29/25 8:18 AM | Critical (3) | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.3, 1002MHz. |
| 3/29/25 8:18 AM | Notice (6) | Honoring MDD |
| 3/29/25 8:18 AM | Critical (3) | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.2, 258MHz. |
| 3/29/25 8:18 AM | Critical (3) | CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-21.3, 1002MHz. |
| 3/29/25 8:18 AM | Critical (3) | CMSTATUS:US_Diplexer_Mode_Change:TLV-21.1, 5-85MHz. |
| 3/29/25 8:18 AM | Critical (3) | CMSTATUS:US_Diplexer_Mode_Change:Fixed Initial, 5-42MHz. |
| 3/29/25 8:17 AM | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out |
| 3/29/25 8:17 AM | Critical (3) | No Ranging Response received - T3 time-out |
| 3/29/25 8:17 AM | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out |
| 3/29/25 8:16 AM | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out |
| 3/29/25 8:14 AM | Warning (5) | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW |
| 3/29/25 8:14 AM | Warning (5) | Dynamic Range Window violation |
| 3/29/25 8:14 AM | Warning (5) | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW |
| 3/29/25 8:14 AM | Warning (5) | Dynamic Range Window violation |
| 3/29/25 8:14 AM | Warning (5) | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW |
| 3/29/25 8:14 AM | Warning (5) | Dynamic Range Window violation |
| 3/29/25 8:14 AM | Warning (5) | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW |
| 3/29/25 8:14 AM | Warning (5) | Dynamic Range Window violation |
| 3/29/25 8:14 AM | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out |
| 3/29/25 8:07 AM | Critical (3) | UCD invalid or channel unusable |
XfinityThomasB
Official Employee
•
1.8K Messages
2 days ago
user_x072sq
It would be our pleasure to review the diagnostics on this. 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
0