critical No Ranging Response received
My super hub is failing with the message 09/05/2025 12:06:18 critical No Ranging Response received. How can I resolve this?
And why do my posts keep getting deleted????
Forum Discussion
8 Replies
That’s a general message that is normally ok. Please post full set of stats as per:
How to get stats from a VM hub (no need to logon to the hub)
Open a web browser and go to 192.168.0.1 router mode or 192.168.100.1 modem mode
- Click on the “> Check router status” button
- Click on the “Downstream” tab, copy the text and paste into your reply, do not take a screen shot
- Click on the “Upstream” tab, copy the text and paste into your reply
- Click on the “Networking” tab, copy the text and paste into your reply.
- Do NOT post photos or screen shots they will be rejected as they contain MAC addresses. The board software will automatically change MAC addresses to **:** if done as above.
These are the kind of errors I've been seeing along with intermittent internet access:
Time Priority Description 09/05/2025 12:06:18 critical No Ranging Response received - T3 time-out;CM-<REDACTED>;CM-QOS=1.1;CM-VER=3.0; 09/05/2025 12:06:18 Error TCS Fail on all Upstream Channels;CM-<REDACTED>;CM-QOS=1.1;CM-VER=3.0; 09/05/2025 12:06:18 critical Unicast Ranging Received Abort Response - initializing MAC;CM-<REDACTED>;CM-QOS=1.1;CM-VER=3.0; 09/05/2025 12:05:5 critical No Ranging Response received - T3 time-out;CM-<REDACTED>;CM-QOS=1.1;CM-VER=3.0; 09/05/2025 12:05:5 Error TCS Fail on all Upstream Channels;CM-<REDACTED>;CM-QOS=1.1;CM-VER=3.0; 09/05/2025 12:05:5 critical Unicast Ranging Received Abort Response - initializing MAC;CM-<REDACTED>;CM-QOS=1.1;CM-VER=3.0; 09/05/2025 12:03:48 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-<REDACTED>;CM-QOS=1.1;CM-VER=3.0; 09/05/2025 12:03:18 critical No Ranging Response received - T3 time-out;CM-<REDACTED>;CM-QOS=1.1;CM-VER=3.0; 09/05/2025 12:03:18 critical Unicast Ranging Received Abort Response - initializing MAC;CM-<REDACTED>;CM-QOS=1.1;CM-VER=3.0; 09/05/2025 08:06:0 Warning! RCS Partial Service;CM-<REDACTED>;CM-QOS=1.1;CM-VER=3.0; 09/05/2025 08:05:49 critical SYNC Timing Synchronization failure - Loss of Sync;CM-<REDACTED>;CM-QOS=1.1;CM-VER=3.0; 09/05/2025 08:05:49 Warning! RCS Partial Service;CM-<REDACTED>;CM-QOS=1.1;CM-VER=3.0; 09/05/2025 08:03:27 critical SYNC Timing Synchronization failure - Loss of Sync;CM-<REDACTED>;CM-QOS=1.1;CM-VER=3.0; 09/05/2025 08:03:24 Warning! RCS Partial Service;CM-<REDACTED>;CM-QOS=1.1;CM-VER=3.0; 09/05/2025 08:01:4 critical SYNC Timing Synchronization failure - Loss of Sync;CM-<REDACTED>;CM-QOS=1.1;CM-VER=3.0; 09/05/2025 07:52:56 Warning! RCS Partial Service;CM-<REDACTED>;CM-QOS=1.1;CM-VER=3.0; 09/05/2025 07:52:56 critical SYNC Timing Synchronization failure - Loss of Sync;CM-<REDACTED>;CM-QOS=1.1;CM-VER=3.0; 09/05/2025 07:38:43 Warning! RCS Partial Service;CM-<REDACTED>;CM-QOS=1.1;CM-VER=3.0; 09/05/2025 07:38:39 critical SYNC Timing Synchronization failure - Loss of Sync;CM-<REDACTED>;CM-QOS=1.1;CM-VER=3.0; 09/05/2025 07:18:26 Warning! RCS Partial Service;CM-<REDACTED>;CM-QOS=1.1;CM-VER=3.0;I can't get to 192.168.1.100 anymore to copy any more logs, despite being online!
Ok so its back online and I was hitting the wrong IP for the status page:
Upstream bonded channels Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID 1 49600024 57 5120 64 qam 1 Upstream bonded channels Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts 1 ATDMA 0 0 0 0Downstream bonded channels Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID 1 331000000 -1.2 40 256 qam 25 2 203000000 -1.2 38 256 qam 9 3 211000000 -1.5 40 256 qam 10 4 219000000 -1.4 38 256 qam 11 5 227000000 -1.7 38 256 qam 12 6 235000000 -1.5 40 256 qam 13 7 243000000 -1.5 40 256 qam 14 8 251000000 -2 40 256 qam 15 9 259000000 -1.9 40 256 qam 16 10 267000000 -1.5 40 256 qam 17 11 275000000 -1.7 40 256 qam 18 12 283000000 -1.7 40 256 qam 19 13 291000000 -2 40 256 qam 20 14 299000000 -1.5 40 256 qam 21 15 307000000 -1.2 40 256 qam 22 16 315000000 -1.2 40 256 qam 23 17 323000000 -1.2 40 256 qam 24 18 339000000 -0.7 40 256 qam 26 19 347000000 -1 40 256 qam 27 20 355000000 -1.2 40 256 qam 28 21 363000000 -1.2 40 256 qam 29 22 371000000 -1.2 40 256 qam 30 23 379000000 -1.4 40 256 qam 31 24 387000000 -1.5 40 256 qam 32 Downstream bonded channels Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors 1 Locked 40.3 0 0 2 Locked 38.9 18 0 3 Locked 40.3 14 0 4 Locked 38.9 11 0 5 Locked 38.9 11 0 6 Locked 40.9 13 0 7 Locked 40.9 17 0 8 Locked 40.3 9 0 9 Locked 40.9 10 0 10 Locked 40.3 14 0 11 Locked 40.9 6 0 12 Locked 40.9 6 0 13 Locked 40.3 0 0 14 Locked 40.3 0 0 15 Locked 40.3 10 0 16 Locked 40.3 7 0 17 Locked 40.9 5 0 18 Locked 40.3 11 0 19 Locked 40.9 5 0 20 Locked 40.3 5 0 21 Locked 40.3 5 0 22 Locked 40.9 6 0 23 Locked 40.3 8 0 24 Locked 40.3 0 0I suppose this was a temporary failure of virgin? I will post back here if it goes offline again.
- Robert_P
Forum Team
Monitor this going forward wwforever and if you experience the issues again, let us know here and we'll be happy to assist further.
Hi,
The modem is once again disconnected. Here are the details:
Cable Modem Status Item Status Comments Acquired Downstream Channel (Hz) 179000000 Ranging Ranged Upstream Channel (Hz) Update in progress undefined Provisioning State OfflineDownstream bonded channels Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID 1 179000000 -2.2 40 256 qam 6 Downstream bonded channels Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors 1 Locked 40.3 5 0Time Priority Description 12/05/2025 13:53:48 critical No Ranging Response received - T3 time-out;CM-MAC=4c:38:d8:31:b6:3b;CMTS-MAC=70:e4:22:f1:e7:22;CM-QOS=1.1;CM-VER=3.0; 12/05/2025 13:53:47 critical Unicast Ranging Received Abort Response - initializing REDACTED; 12/05/2025 13:53:47 Error TCS Fail on all Upstream Channels;CM-MAC=4c:38:d8:31:b6:3b;CMTS-MAC=70:e4:22:f1:e7:22;CM-QOS=1.1;CM-VER=3.0; 12/05/2025 13:52:39 critical No Ranging Response received - T3 time-out;CM-MAC=4c:38:d8:31:b6:3b;CMTS-MAC=70:e4:22:f1:e7:22;CM-QOS=1.1;CM-VER=3.0; 12/05/2025 13:52:39 Error TCS Fail on all Upstream Channels;CM-MAC=4c:38:d8:31:b6:3b;CMTS-MAC=70:e4:22:f1:e7:22;CM-QOS=1.1;CM-VER=3.0; 12/05/2025 13:52:39 critical Unicast Ranging Received Abort Response - initializing REDACTED; 12/05/2025 13:51:34 critical No Ranging Response received - T3 time-out;CM-MAC=4c:38:d8:31:b6:3b;CMTS-MAC=70:e4:22:f1:e7:22;CM-QOS=1.1;CM-VER=3.0; 12/05/2025 13:51:34 critical Unicast Ranging Received Abort Response - initializing REDACTED; 12/05/2025 13:50:25 critical No Ranging Response received - T3 time-out;CM-MAC=4c:38:d8:31:b6:3b;CMTS-MAC=70:e4:22:f1:e7:22;CM-QOS=1.1;CM-VER=3.0; 12/05/2025 13:50:25 critical Unicast Ranging Received Abort Response - initializing REDACTED; 12/05/2025 13:49:20 critical No Ranging Response received - T3 time-out;CM-MAC=4c:38:d8:31:b6:3b;CMTS-MAC=70:e4:22:f1:e7:22;CM-QOS=1.1;CM-VER=3.0; 12/05/2025 13:49:20 critical Unicast Ranging Received Abort Response - initializing REDACTED; 12/05/2025 13:48:24 critical No Ranging Response received - T3 time-out;CM-MAC=4c:38:d8:31:b6:3b;CMTS-MAC=70:e4:22:f1:e7:22;CM-QOS=1.1;CM-VER=3.0; 12/05/2025 13:48:24 critical Unicast Ranging Received Abort Response - initializing REDACTED; 12/05/2025 13:47:19 critical No Ranging Response received - T3 time-out;CM-MAC=4c:38:d8:31:b6:3b;CMTS-MAC=70:e4:22:f1:e7:22;CM-QOS=1.1;CM-VER=3.0; 12/05/2025 13:47:19 critical Unicast Ranging Received Abort Response - initializing REDACTED; 12/05/2025 13:46:24 critical No Ranging Response received - T3 time-out;CM-MAC=4c:38:d8:31:b6:3b;CMTS-MAC=70:e4:22:f1:e7:22;CM-QOS=1.1;CM-VER=3.0; 12/05/2025 13:46:24 critical Unicast Ranging Received Abort Response - initializing REDACTED; 12/05/2025 13:45:26 critical No Ranging Response received - T3 time-out;CM-MAC=4c:38:d8:31:b6:3b;CMTS-MAC=70:e4:22:f1:e7:22;CM-QOS=1.1;CM-VER=3.0; 12/05/2025 13:45:25 critical Unicast Ranging Received Abort Response - initializing REDACTED;
And its disconnected again now ... :(
- Matthew_ML
Hey wwforever, thank you for reaching out and we are sorry to hear you are having some connection issues.
We can see you've spoken to the team since this post.
Did they manage to help at all?
