errors in hub5 log
having problems with low speed/disconnects today and have the following in hub5 log. Do I need an engineer?
Nick
Forum Discussion
4 Replies
having problems today with network being slow / dropping out. The log file contains the following.
Do i have a problem? Do I need an engineer call out?
Nick
05-11-2025 20:53:44 notice GUI Login Status - Login Success from LAN interface 05-11-2025 20:15:57 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=[REMOVED] 05-11-2025 20:15:57 notice US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=[REMOVED] 05-11-2025 20:15:53 notice REGISTRATION COMPLETE - Waiting for Operational status 05-11-2025 20:15:46 warning RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=[REMOVED] 05-11-2025 20:15:46 warning Dynamic Range Window violation 05-11-2025 20:15:46 warning REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=[REMOVED] 05-11-2025 20:15:41 notice DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=[REMOVED] 05-11-2025 20:15:37 notice TLV-11 - unrecognized OID;CM-MAC=[REMOVED] 05-11-2025 20:15:35 warning DHCP WARNING - Non-critical field invalid in response ;CM-MAC=[REMOVED] 05-11-2025 20:15:33 notice Honoring MDD; IP provisioning mode = IPv4 05-11-2025 20:15:22 critical No Ranging Response received - T3 time-out;CM-MAC=[REMOVED] 05-11-2025 20:15:16 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[REMOVED] 05-11-2025 20:15:14 critical Cable Modem Reboot because of - HW or Power-On Reset 05-11-2025 17:50:59 critical No Ranging Response received - T3 time-out;CM-MAC=[REMOVED] 05-11-2025 17:50:53 critical Cable Modem Reboot because of - Reboot Timezone Change 05-11-2025 17:50:53 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[REMOVED] 05-11-2025 17:48:15 critical No Ranging Response received - T3 time-out;CM-MAC=[REMOVED] 05-11-2025 17:48:11 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[REMOVED] 05-11-2025 17:48:09 critical Cable Modem Reboot because of - HW or Power-On Reset 14-10-2025 10:42:29 critical No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=[REMOVED] 14-10-2025 10:42:04 critical No Ranging Response received - T3 time-out;CM-MAC=[REMOVED] 14-10-2025 10:41:59 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[REMOVED] 14-10-2025 10:41:16 critical No Ranging Response received - T3 time-out;CM-MAC=[REMOVED] 13-10-2025 09:53:09 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[REMOVED] 12-10-2025 01:17:37 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[REMOVED] 10-10-2025 03:11:25 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:[REMOVED] 08-10-2025 04:44:34 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[REMOVED] 07-10-2025 14:52:35 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[REMOVED] 05-10-2025 16:46:03 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[REMOVED] 04-10-2025 13:44:00 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[REMOVED] 02-10-2025 08:41:28 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:[REMOVED] 27-09-2025 16:43:18 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[REMOVED] More informative data is found in the Downstream and Upstream tabs of the Hub.
- Kath_P
Forum Team
Hi nmcculloch,
Thanks for coming back here.
I can see my colleague has already replied to your other thread here: errors in hub5 log
Please make sure you are only posting once about your issue. If you need to update the thread then just reply to your original thread rather than creating a new one. We understand it's frustrating when something's not right however posting more than once about the same fault makes the boards look busier than what they actually are. It also means we could take longer to reply due to needing to sift through duplicate posts.
Have a look at the reply on the other thread and stick with that one so we keep all the information in one place.
Thanks,
- Carley_S
Hi nmcculloch
Welcome back to the Community Forums.
Sorry to hear of your service concerns. Checking the systems on our side, we cannot see any issues today that could be affecting your services.
Are you finding that the issue has still been recurring since Wednesday? If so, are you able to provide further details? It doesn't look like the Hub log information has been posted.
Let us know, and we'll help in any way we can on our side.
