Constant disconnections
We recently had an engineer visit where the engineer concluded everything was fine, but the Hub 4 we had was replaced with a Hub 5. The reason for the visit was due to constant disconnections and loss of service.
Since the Hub 5 was installed it has been much better until the last couple of days where we're losing our connection a lot again. The only way to sort it is turn the hub off, leave for a bit then restart. It then works for a while. I've discovered there is a log in the Hub 5 which provides the table below, the critical items coincide with when the internet is lost, I'm assuming this is the reason and is therefore related.
I've found lots of questions about this, but no real answers, how does this get fixed? The current recorded message says there are no issues in our area, but when I check the service on line, it says there is an issue which is being worked on, check again tomorrow.
| ime | Priority | Description |
| 14/12/2023 17:09 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 14/12/2023 17:09 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 14/12/2023 16:58 | notice | REGISTRATION COMPLETE - Waiting for Operational status |
| 14/12/2023 16:57 | warning | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 14/12/2023 16:57 | warning | REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 14/12/2023 16:57 | warning | Dynamic Range Window violation |
| 14/12/2023 16:57 | notice | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 14/12/2023 16:57 | notice | TLV-11 - unrecognized OID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 14/12/2023 16:57 | warning | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 14/12/2023 16:57 | notice | Honoring MDD; IP provisioning mode = IPv4 |
| 14/12/2023 16:57 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 14/12/2023 16:57 | critical | Cable Modem Reboot because of - HW or Power-On Reset |
| 14/12/2023 14:38 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 14/12/2023 14:38 | critical | Cable Modem Reboot because of - HW or Power-On Reset |
| 14/12/2023 14:02 | critical | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 14/12/2023 09:51 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 14/12/2023 09:40 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 14/12/2023 09:39 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 14/12/2023 09:39 | critical | Cable Modem Reboot because of - HW or Power-On Reset |
| 13/12/2023 23:16 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 13/12/2023 23:16 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 13/12/2023 23:16 | critical | Cable Modem Reboot because of - HW or Power-On Reset |
| 13/12/2023 07:22 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 13/12/2023 07:22 | critical | Cable Modem Reboot because of - HW or Power-On Reset |
| 12/12/2023 07:29 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 12/12/2023 07:28 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 12/12/2023 07:28 | critical | Cable Modem Reboot because of - HW or Power-On Reset |
| 12/12/2023 07:26 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 12/12/2023 06:09 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 12/12/2023 05:58 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 12/12/2023 05:57 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 12/12/2023 05:57 | critical | Cable Modem Reboot because of - HW or Power-On Reset |
