Frequent Visitor
•
5 Messages
T3 timeouts, Aborted responses, and intermittent internet
Hello,
We have been having constant interruptions to our internet service that last anywhere from a few minutes to several hours, approximately 10-12 times per day. This is causing us problems working from home. Called Xfinity several times but they all keep saying "just monitor the situation."
Greatly appreciate any help.
Output from modem (Motorola MB7621):
Time | Priority | Description |
Time Not Established | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:69:db:78;CMTS-MAC=58:97:bd:98:5c:e9;CM-QOS=1.0;CM-VER=3.0; |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=00:40:36:69:db:78;CMTS-MAC=58:97:bd:98:5c:e9;CM-QOS=1.0;CM-VER=3.0; |
Time Not Established | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:69:db:78;CMTS-MAC=58:97:bd:98:5c:e9;CM-QOS=1.0;CM-VER=3.0; |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=00:40:36:69:db:78;CMTS-MAC=58:97:bd:98:5c:e9;CM-QOS=1.0;CM-VER=3.0; |
Time Not Established | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:69:db:78;CMTS-MAC=58:97:bd:98:5c:e9;CM-QOS=1.0;CM-VER=3.0; |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=00:40:36:69:db:78;CMTS-MAC=58:97:bd:98:5c:e9;CM-QOS=1.0;CM-VER=3.0; |
Time Not Established | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:69:db:78;CMTS-MAC=58:97:bd:98:5c:e9;CM-QOS=1.0;CM-VER=3.0; |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=00:40:36:69:db:78;CMTS-MAC=58:97:bd:98:5c:e9;CM-QOS=1.0;CM-VER=3.0; |
Time Not Established | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:69:db:78;CMTS-MAC=58:97:bd:98:5c:e9;CM-QOS=1.0;CM-VER=3.0; |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=00:40:36:69:db:78;CMTS-MAC=58:97:bd:98:5c:e9;CM-QOS=1.0;CM-VER=3.0; |
Time Not Established | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:69:db:78;CMTS-MAC=58:97:bd:98:5c:e9;CM-QOS=1.0;CM-VER=3.0; |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=00:40:36:69:db:78;CMTS-MAC=58:97:bd:98:5c:e9;CM-QOS=1.0;CM-VER=3.0; |
Time Not Established | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:69:db:78;CMTS-MAC=58:97:bd:98:5c:e9;CM-QOS=1.0;CM-VER=3.0; |
Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:69:db:78;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Time Not Established | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:69:db:78;CMTS-MAC=58:97:bd:98:5c:e9;CM-QOS=1.0;CM-VER=3.0; |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=00:40:36:69:db:78;CMTS-MAC=58:97:bd:98:5c:e9;CM-QOS=1.0;CM-VER=3.0; |
Time Not Established | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:69:db:78;CMTS-MAC=58:97:bd:98:5c:e9;CM-QOS=1.0;CM-VER=3.0; |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=00:40:36:69:db:78;CMTS-MAC=58:97:bd:98:5c:e9;CM-QOS=1.0;CM-VER=3.0; |
Time Not Established | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:69:db:78;CMTS-MAC=58:97:bd:98:5c:e9;CM-QOS=1.0;CM-VER=3.0; |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=00:40:36:69:db:78;CMTS-MAC=58:97:bd:98:5c:e9;CM-QOS=1.0;CM-VER=3.0; |
Time Not Established | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
Mon Jul 20 08:50:06 2020 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:69:db:78;CMTS-MAC=58:97:bd:98:5c:e9;CM-QOS=1.1;CM-VER=3.0; |
Mon Jul 20 08:50:28 2020 | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
Mon Jul 20 09:24:55 2020 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:69:db:78;CMTS-MAC=58:97:bd:98:5c:e9;CM-QOS=1.1;CM-VER=3.0; |
Mon Jul 20 09:25:29 2020 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:69:db:78;CMTS-MAC=58:97:bd:98:5c:e9;CM-QOS=1.0;CM-VER=3.0; |
Mon Jul 20 09:25:50 2020 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=00:40:36:69:db:78;CMTS-MAC=58:97:bd:98:5c:e9;CM-QOS=1.0;CM-VER=3.0; |
Mon Jul 20 09:26:14 2020 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:69:db:78;CMTS-MAC=58:97:bd:98:5c:e9;CM-QOS=1.0;CM-VER=3.0; |
Mon Jul 20 09:26:25 2020 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=00:40:36:69:db:78;CMTS-MAC=58:97:bd:98:5c:e9;CM-QOS=1.0;CM-VER=3.0; |
Mon Jul 20 09:26:48 2020 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:69:db:78;CMTS-MAC=58:97:bd:98:5c:e9;CM-QOS=1.0;CM-VER=3.0; |
Mon Jul 20 09:27:48 2020 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=00:40:36:69:db:78;CMTS-MAC=58:97:bd:98:5c:e9;CM-QOS=1.0;CM-VER=3.0; |
Mon Jul 20 09:28:06 2020 | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
Mon Jul 20 09:29:27 2020 | Warning (5) | Unicast DSID PSN startup error |
titan730
Frequent Visitor
•
5 Messages
5 years ago
Here is the upstream channels:
0
0
EG
Expert
•
111.7K Messages
5 years ago
The upstream power is on is too high / out of spec. The downstream power is almost out of spec as well. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.
In a self troubleshooting effort to try to obtain better connectivity / more wiggle room, 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-1002 MHz, bi-directional, and no gold colored garbage types like GE, RadioShack, RCA, Philips, Leviton, Magnavox, and Rocketfish from big box stores like Home Depot, Lowes, Target, Wal-Mart etc. Splitters should be swapped with known to be good / new ones to test
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.
0
0
pritch55
Regular Visitor
•
4 Messages
5 years ago
Delete
0
0
titan730
Frequent Visitor
•
5 Messages
5 years ago
Thanks, @EG . I've ordered another splitter to see if that's the problem. Will update asap with results. Thanks again.
0
0
EG
Expert
•
111.7K Messages
5 years ago
Quite welcome ! Good luck with it !
0
0
titan730
Frequent Visitor
•
5 Messages
5 years ago
@EG -- Just wanted to close the loop. We removed 1 splitter from the network, replaced the splitter from the main coax cable into the house, and so far things are working without any problems. Glad it was a simple fix. Thanks for the help.
0
0
EG
Expert
•
111.7K Messages
5 years ago
For curiosity, what do the signal stats look like now ?
0
0
titan730
Frequent Visitor
•
5 Messages
5 years ago
@EG Here they are after 24 hours of being connected without any interruptions in service...
0
0
EG
Expert
•
111.7K Messages
5 years ago
The upstream power is still a bit on the high side. The preferred area is 40 to 45 dB. It may be ok if it holds stable. Bottom line. Live with it for a while and see if the problem returns. Good luck with it !
0
0