Forum Discussion

yorkieboy123's avatar
yorkieboy123
Tuning in
3 hours ago

No Ranging Response received - T3 time-out

Hi there,

We are having persistent issues with high latency and high jitter which are affecting our home network

The network logs show T3 time-out. I restarted the Hub 3.0 since the last once at 9am.

We've had this issue previously and it was fixed when an engineer visited the box in the street. We have on-curb parking in our street and unfortunately for us the network box is INSIDE a parking space and it has been hit and knocked over several times. 

Please advise if the Network Status stats and logs look good and if we can get an engineer to look at the box in the street.

 

Network Log

TimePriorityDescription
26/08/2025 11:58:28noticeLAN login Success; [REMOVED]
26/08/2025 09:09:14Warning!TCS Partial Service;[REMOVED]
26/08/2025 09:09:14Warning!Initializing Channel Timeout Expires - Time the CM can perform initial ranging on all upstream channels in the TCS has expired;[REMOVED]
25/08/2025 15:01:40criticalNo Ranging Response received - T3 time-out;[REMOVED]
25/08/2025 06:30:8noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;[REMOVED]
25/08/2025 06:30:8ErrorDHCP RENEW WARNING - Field invalid in response v4 option;[REMOVED]
22/08/2025 03:57:17criticalNo Ranging Response received - T3 time-out;[REMOVED]
21/08/2025 18:30:8noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;[REMOVED]
21/08/2025 18:30:8ErrorDHCP RENEW WARNING - Field invalid in response v4 option;[REMOVED]
18/08/2025 12:08:22criticalNo Ranging Response received - T3 time-out;[REMOVED]
18/08/2025 06:30:7noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;[REMOVED]
18/08/2025 06:30:7ErrorDHCP RENEW WARNING - Field invalid in response v4 option;[REMOVED]
15/08/2025 03:43:43criticalNo Ranging Response received - T3 time-out;[REMOVED]
14/08/2025 18:30:7noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;[REMOVED]
14/08/2025 18:30:7ErrorDHCP RENEW WARNING - Field invalid in response v4 option;[REMOVED]
11/08/2025 11:14:20criticalNo Ranging Response received - T3 time-out;[REMOVED]
11/08/2025 06:30:2noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;[REMOVED]
11/08/2025 06:30:2ErrorDHCP RENEW WARNING - Field invalid in response v4 option;[REMOVED]
10/08/2025 01:59:11criticalNo Ranging Response received - T3 time-out;[REMOVED]
07/08/2025 18:30:2noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;[REMOVED]
[MOD EDIT: MAC addresses removed]

6 Replies

  • yorkieboy123's avatar
    yorkieboy123
    Tuning in
    3 hours ago

    Status ____________________________________________

    Item Status Comments

    Acquired Downstream Channel (Hz), 331000000, Locked

    Ranged Upstream Channel (Hz), 36599988, Locked

    Provisioning State, Online

    Downstream ____________________________________________

    Downstream bonded channels _____________________________

    Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

    1 331000000 3.7 40 256 qam 25

    2 139000000 4.9 40 256 qam 1

    3 147000000 4.8 40 256 qam 2

    4 155000000 4.9 40 256 qam 3

    5 163000000 4.8 40 256 qam 4

    6 171000000 4.6 40 256 qam 5

    7 179000000 4.3 40 256 qam 6

    8 187000000 4.4 40 256 qam 7

    9 195000000 4.3 40 256 qam 8

    10 203000000 4.1 40 256 qam 9

    11 227000000 4.3 40 256 qam 12

    12 235000000 4.1 40 256 qam 13

    13 259000000 3.9 40 256 qam 16

    14 267000000 4 40 256 qam 17

    15 291000000 3.7 40 256 qam 20

    16 299000000 4.4 40 256 qam 21

    17 323000000 3.5 40 256 qam 24

    18 355000000 3.4 40 256 qam 28

    19 363000000 3.2 40 256 qam 29

    20 379000000 3.7 40 256 qam 31

    21 387000000 3.4 40 256 qam 32

    22 395000000 2.9 40 256 qam 33

    23 403000000 2.5 40 256 qam 34

    24 411000000 2.7 40 256 qam 35

    Downstream bonded channels _____________________________

    Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

    1 Locked 40.9 8 0

    2 Locked 40.9 13 0

    3 Locked 40.3 83 0

    4 Locked 40.3 7 0

    5 Locked 40.9 18 0

    6 Locked 40.3 20 0

    7 Locked 40.3 30 0

    8 Locked 40.9 8 0

    9 Locked 40.9 19 0

    10 Locked 40.9 7 0

    11 Locked 40.3 8 0

    12 Locked 40.9 8 0

    13 Locked 40.3 9 0

    14 Locked 40.3 14 0

    15 Locked 40.3 5 0

    16 Locked 40.9 1 0

    17 Locked 40.9 9 0

    18 Locked 40.9 11 0

    19 Locked 40.3 1 0

    20 Locked 40.3 13 0

    21 Locked 40.9 6 0

    22 Locked 40.9 16 3

    23 Locked 40.9 6 0

    24 Locked 40.3 16 0

    Upstream ____________________________________________

    Upstream bonded channels ______________________________

    Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

    1 36599988 47 5120 64 qam 3

    2 23600019 47 5120 64 qam 5

    3 30099993 47 5120 64 qam 4

    4 43100024 47 5120 64 qam 2

    5 49600039 47 5120 64 qam 1

    Upstream bonded channels _____________________________

    Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

    1 ATDMA 0 0 0 0

    2 ATDMA 0 0 0 0

    3 ATDMA 0 0 0 0

    4 ATDMA 0 0 0 0

    5 ATDMA 0 0 0 0

     

    General Configuration _____________________________

    Network access, Allowed

    Maximum Number of CPEs, 1

    Baseline Privacy, Enabled

    DOCSIS Mode, Docsis30

    Config file, gvca69834ncxv9873254k;fg8

    Primary Downstream Service Flow, SFID 822

    Max Traffic Rate 287500061

    Max Traffic Burst 42600

    Min Traffic Rate 0

     

    Primary Upstream Service Flow

    SFID 821

    Max Traffic Rate 27500061

    Max Traffic Burst 42600

    Min Traffic Rate 0

    Max Concatenated Burst 42600

    Scheduling Type BestEffort

  • yorkieboy123's avatar
    yorkieboy123
    Tuning in
    3 hours ago

    Also, just to add we recently had the hub 3.0 replaced (within the past year) due to this same issue

  • yorkieboy123's avatar
    yorkieboy123
    Tuning in
    3 hours ago

    Here's my BQM

    26th August 25:


    (I turned it off at the wall at 9am but you can see packet loss all day)

    [MOD EDIT: Images removed due to containing private information]

    Then as another example on 15th August:



    Corresponding to this log below.

    15/08/2025 03:43:43criticalNo Ranging Response received - T3 time-out; [REMOVED]

     

  • Adduxi's avatar
    Adduxi
    Very Insightful Person
    2 hours ago

    I can't see anything wrong with your stats TBH.  Yes, the BQM shows minimal packet loss, but the stats don't match.  Hard one to pin down.

  • Nednats's avatar
    Nednats
    Hanging out
    2 hours ago

    You're seeing the error “No Ranging Response received – T3 time-out”, which is a DOCSIS error indicating your modem is struggling to communicate properly with your VM’s network equipment (specifically, the CMTS). This usually means that even though the modem sends a Ranging Request, it doesn’t get a response, causing it to reset the connection. 

    This error often points to issues in the physical connection—typically on the upstream path. Common culprits include:

    • Faulty, corroded, or loosely connected coax cables/connectors
    • Poor-quality or malfunctioning splitters/amplifiers
    • High upstream noise or interference
    • Issues outside your property, such as worn or overloaded infrastructure (taps, nodes, ports, etc.)