| Time |
Priority |
Description |
| 2022-12-06, 02:05:31 |
Critical (3) |
No Ranging Response received - T3 time-out; |
| 2022-12-06, 01:55:29 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM- |
| 2022-12-06, 01:55:16 |
Critical (3) |
No Ranging Response received - T3 time-out; |
| 2022-12-06, 01:55:14 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out |
| 2022-12-06, 01:55:14 |
Critical (3) |
No Ranging Response received - T3 time-out; |
| 2022-12-06, 01:55:14 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
| 2022-12-06, 01:54:33 |
Warning (5) |
MDD message timeout |
| 2022-12-06, 01:49:22 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.; |
| 2022-12-06, 01:49:08 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out |
| 2022-12-06, 01:48:26 |
Warning (5) |
MDD message timeout |
| 2022-12-05, 21:18:51 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193; DSID: N/A; |
| 2022-12-05, 21:18:01 |
Warning (5) |
MDD message timeout |
| 2022-12-05, 16:57:15 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193; DSID: N/A; |
| 2022-12-05, 16:56:25 |
Warning (5) |
MDD message timeout |
| 2022-12-05, 15:12:19 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out |
| 2022-12-05, 14:45:25 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.; |
| 2022-12-05, 14:44:35 |
Warning (5) |
MDD message timeout |
| 2022-12-05, 14:35:27 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out |
| 2022-12-05, 13:12:26 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.; |
| 2022-12-05, 13:11:34 |
Warning (5) |
MDD message timeout |
| 2022-12-05, 08:22:44 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A. |
| 2022-12-05, 08:21:53 |
Warning (5) |
MDD message timeout |
| 2022-12-05, 06:16:00 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A. |
| 2022-12-05, 06:15:10 |
Warning (5) |
MDD message timeout |
| 2022-12-04, 21:47:16 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.; |
| 2022-12-04, 21:46:24 |
Warning (5) |
MDD message timeout |
| 2022-12-04, 21:24:26 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.; |
| 2022-12-04, 21:23:34 |
Warning (5) |
MDD message timeout |
| 2022-12-04, 20:04:37 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A. |
| 2022-12-04, 20:03:39 |
Warning (5) |
MDD message timeout |
| 2022-12-04, 19:31:24 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A. |
| 2022-12-04, 19:30:54 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out |
| 2022-12-04, 19:30:32 |
Warning (5) |
MDD message timeout |
| 2022-12-04, 17:12:48 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out |
| 2022-12-04, 16:46:39 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.; |
| 2022-12-04, 16:45:47 |
Warning (5) |
MDD message timeout |
| 2022-12-04, 11:37:36 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.; |
| 2022-12-04, 11:36:40 |
Warning (5) |
MDD message timeout |
| 2022-12-04, 01:30:32 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.; |
| 2022-12-04, 01:29:40 |
Warning (5) |
MDD message timeout |
Accepted Solution
gr-raider
Regular Visitor
•
7 Messages
3 years ago
Conclusion/Resolution:
Escalated the issue up to a line tech, who are separate from the techs that come inside the house and have the bucket trucks. The line tech reviewed multiple reports over a two day period and reviewed the node and amplifiers. I had compiled the list of neighbors, addresses, and their comments about it being a global issue only since the "next generation internet" upgrades. The tech reviewed internally with others and there was a bad batch of adapters sent out that was inside the node that serviced the neighborhood. After replacing this there has not been any TV freezing or any internet drops, including no MDD Message timeout or T3 or T4 timeouts.
2
0
CCRenee
New Problem Solver
•
169 Messages
4 years ago
Hi @gr-raider, and thanks for reaching out to us at Xfinity!
Thanks for letting us know how we can help. Sorry for the timeout issues you've been having; we'd be happy to help!
Could you please send our team a direct message with your full name and address? Our team can further investigate this issue. To send a "Direct Message" to Xfinity Support:
Click "Sign In" if necessary
Click the "Direct Messaging" icon
Click the "New message" (pencil and paper) icon
The "To:" line prompts you to "Type the name of a person". Instead, type "Xfinity Support" there
- As you are typing a drop-down list appears. Select "Xfinity Support" from that list
- An "Xfinity Support" graphic replaces the "To" line
Type your message in the text area near the bottom of the window
Press Enter to send it
0
0
EG
Expert
•
118.4K Messages
4 years ago
@gr-raider @XfinityRenee
Please circle back here and post any possible solutions for the issue here in the open forums so that all readers here may benefit from the exchange / info. This is in keeping with the spirit for which these public help forums were originally intended. Thank you.
0
0