|
Time |
|
Priority |
|
Description |
|
21:29:13 Sun Jul 24 2022 |
|
Critical (3) |
|
TFTP failed - Request sent - No Response;CM-MAC=Personal Info;CMTS-MAC=Personal Info;CM-QOS=1.1;CM-VER=3.1; |
|
21:29:13 Sun Jul 24 2022 |
|
Critical (3) |
|
TFTP Request Retries exceeded, CM unable to register |
|
21:29:20 Sun Jul 24 2022 |
|
Critical (3) |
|
No Ranging Response received - T3 time-out;CM-MAC=Personal Info;CMTS-MAC=Personal Info;CM-QOS=1.1;CM-VER=3.1; |
|
21:30:06 Sun Jul 24 2022 |
|
Critical (3) |
|
TFTP failed - Request sent - No Response;CM-MAC=Personal Info;CMTS-MAC=Personal Info;CM-QOS=1.1;CM-VER=3.1; |
|
21:30:06 Sun Jul 24 2022 |
|
Critical (3) |
|
TFTP Request Retries exceeded, CM unable to register |
|
21:30:13 Sun Jul 24 2022 |
|
Critical (3) |
|
No Ranging Response received - T3 time-out;CM-MAC=Personal Info;CMTS-MAC=Personal Info;CM-QOS=1.1;CM-VER=3.1; |
|
21:30:59 Sun Jul 24 2022 |
|
Critical (3) |
|
TFTP failed - Request sent - No Response;CM-MAC=Personal Info;CMTS-MAC=Personal Info;CM-QOS=1.1;CM-VER=3.1; |
|
21:30:59 Sun Jul 24 2022 |
|
Critical (3) |
|
TFTP Request Retries exceeded, CM unable to register |
|
21:31:07 Sun Jul 24 2022 |
|
Critical (3) |
|
No Ranging Response received - T3 time-out;CM-MAC=Personal Info;CMTS-MAC=Personal Info;CM-QOS=1.1;CM-VER=3.1; |
|
21:31:52 Sun Jul 24 2022 |
|
Critical (3) |
|
TFTP failed - Request sent - No Response;CM-MAC=Personal Info;CMTS-MAC=Personal Info;CM-QOS=1.1;CM-VER=3.1; |
|
21:31:52 Sun Jul 24 2022 |
|
Critical (3) |
|
TFTP Request Retries exceeded, CM unable to register |
|
21:31:59 Sun Jul 24 2022 |
|
Critical (3) |
|
No Ranging Response received - T3 time-out;CM-MAC=Personal Info;CMTS-MAC=Personal Info;CM-QOS=1.1;CM-VER=3.1; |
|
21:32:47 Sun Jul 24 2022 |
|
Critical (3) |
|
TFTP failed - Request sent - No Response;CM-MAC=Personal Info;CMTS-MAC=Personal Info;CM-QOS=1.1;CM-VER=3.1; |
|
21:32:47 Sun Jul 24 2022 |
|
Critical (3) |
|
TFTP Request Retries exceeded, CM unable to register |
|
21:32:55 Sun Jul 24 2022 |
|
Critical (3) |
|
No Ranging Response received - T3 time-out;CM-MAC=Personal Info;CMTS-MAC=Personal Info;CM-QOS=1.1;CM-VER=3.1; |
|
21:33:43 Sun Jul 24 2022 |
|
Critical (3) |
|
TFTP failed - Request sent - No Response;CM-MAC=Personal Info;CMTS-MAC=Personal Info;CM-QOS=1.1;CM-VER=3.1; |
|
21:33:43 Sun Jul 24 2022 |
|
Critical (3) |
|
TFTP Request Retries exceeded, CM unable to register |
|
21:33:52 Sun Jul 24 2022 |
|
Critical (3) |
|
No Ranging Response received - T3 time-out;CM-MAC=Personal Info;CMTS-MAC=Personal Info;CM-QOS=1.1;CM-VER=3.1; |
|
21:34:38 Sun Jul 24 2022 |
|
Critical (3) |
|
TFTP failed - Request sent - No Response;CM-MAC=Personal Info;CMTS-MAC=Personal Info;CM-QOS=1.1;CM-VER=3.1; |
|
21:34:38 Sun Jul 24 2022 |
|
Critical (3) |
|
TFTP Request Retries exceeded, CM unable to register |
|
21:34:54 Sun Jul 24 2022 |
|
Critical (3) |
|
No Ranging Response received - T3 time-out;CM-MAC=Personal Info;CMTS-MAC=Personal Info;CM-QOS=1.1;CM-VER=3.1; |
|
21:35:40 Sun Jul 24 2022 |
|
Critical (3) |
|
TFTP failed - Request sent - No Response;CM-MAC=Personal Info;CMTS-MAC=Personal Info;CM-QOS=1.1;CM-VER=3.1; |
|
21:35:40 Sun Jul 24 2022 |
|
Critical (3) |
|
TFTP Request Retries exceeded, CM unable to register |
|
21:35:48 Sun Jul 24 2022 |
|
Critical (3) |
|
No Ranging Response received - T3 time-out;CM-MAC=Personal Info;CMTS-MAC=Personal Info;CM-QOS=1.1;CM-VER=3.1; |
|
21:36:30 Sun Jul 24 2022 |
|
Critical (3) |
|
TFTP failed - Request sent - No Response;CM-MAC=Personal Info;CMTS-MAC=Personal Info;CM-QOS=1.1;CM-VER=3.1; |
|
21:36:31 Sun Jul 24 2022 |
|
Critical (3) |
|
TFTP Request Retries exceeded, CM unable to register |
|
Time Not Established |
|
Critical (3) |
|
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=Personal Info;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
|
Time Not Established |
|
Critical (3) |
|
No Ranging Response received - T3 time-out;CM-MAC=Personal Info;CMTS-MAC=Personal Info;CM-QOS=1.1;CM-VER=3.1; |
|
Time Not Established |
|
Critical (3) |
|
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=Personal Info;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
|
Time Not Established |
|
Critical (3) |
|
No Ranging Response received - T3 time-out;CM-MAC=Personal Info;CMTS-MAC=Personal Info;CM-QOS=1.1;CM-VER=3.1; |
|
Time Not Established |
|
Notice (6) |
|
Honoring MDD; IP provisioning mode = IPv6 |
|
22:09:39 Sun Jul 24 2022 |
|
Notice (6) |
|
DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=Personal Info;CMTS-MAC=Personal Info;CM-QOS=1.1;CM-VER=3.1; |
EG
Expert
•
117.7K Messages
4 years ago
The upstream power is too high / out of spec. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.
In an 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-1000 MHz, bi-directional, and no gold colored garbage from Radio Shack, Home Depot, Target, etc. Splitters should be swapped with known to be good / new ones to test.
Also check the coax cable for any damage such as cuts, nicks, kinks, sharp bends, etc.
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.
Good luck with it !
1
0
EG
Expert
•
117.7K Messages
4 years ago
@hjsohn
If there is nothing more that can be done to improve the connection quality, then you'll need a tech visit as stated.
Bear in mind that if the premises facing techs can not find or fix a problem at your home, it is they who are responsible for escalating it to their line / network / maintenance dept. techs. The problem may lie beyond your home in the local neighborhood infrastructure somewhere but it is their S.O.P. to start at the home. And if the problem is found to be on their side of the demarcation point, there will not be any charge.
Good luck !
0
0