on 22-02-2024 16:45
Is someone able to check the below stats for me? Are the numerous T3 timeouts concerning?
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 139000000 | -1.7 | 38 | 256 qam | 1 |
2 | 147000000 | -1.5 | 40 | 256 qam | 2 |
3 | 155000000 | -1.7 | 40 | 256 qam | 3 |
4 | 163000000 | -1.7 | 40 | 256 qam | 4 |
5 | 171000000 | -1.5 | 40 | 256 qam | 5 |
6 | 179000000 | -1.5 | 40 | 256 qam | 6 |
7 | 187000000 | -1.4 | 40 | 256 qam | 7 |
8 | 195000000 | -1.2 | 40 | 256 qam | 8 |
9 | 203000000 | -1.4 | 40 | 256 qam | 9 |
10 | 211000000 | -1.7 | 40 | 256 qam | 10 |
11 | 219000000 | -1.5 | 40 | 256 qam | 11 |
12 | 227000000 | -1.7 | 40 | 256 qam | 12 |
13 | 235000000 | -1.7 | 40 | 256 qam | 13 |
14 | 243000000 | -1.9 | 40 | 256 qam | 14 |
15 | 251000000 | -1.9 | 40 | 256 qam | 15 |
16 | 259000000 | -1.9 | 40 | 256 qam | 16 |
17 | 267000000 | -1.5 | 40 | 256 qam | 17 |
18 | 275000000 | -1.5 | 40 | 256 qam | 18 |
19 | 283000000 | -1.4 | 40 | 256 qam | 19 |
20 | 291000000 | -1.2 | 40 | 256 qam | 20 |
21 | 299000000 | -1 | 40 | 256 qam | 21 |
22 | 307000000 | -1 | 40 | 256 qam | 22 |
23 | 315000000 | -0.9 | 40 | 256 qam | 23 |
24 | 323000000 | -0.7 | 40 | 256 qam | 24 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 38.9 | 350 | 0 |
2 | Locked | 40.3 | 185 | 0 |
3 | Locked | 40.3 | 101 | 0 |
4 | Locked | 40.3 | 176 | 3 |
5 | Locked | 40.3 | 100 | 0 |
6 | Locked | 40.3 | 111 | 0 |
7 | Locked | 40.3 | 116 | 0 |
8 | Locked | 40.3 | 84 | 0 |
9 | Locked | 40.3 | 131 | 0 |
10 | Locked | 40.3 | 119 | 0 |
11 | Locked | 40.3 | 111 | 0 |
12 | Locked | 40.3 | 117 | 0 |
13 | Locked | 40.3 | 169 | 0 |
14 | Locked | 40.3 | 236 | 0 |
15 | Locked | 40.3 | 333 | 0 |
16 | Locked | 40.3 | 307 | 0 |
17 | Locked | 40.3 | 224 | 0 |
18 | Locked | 40.3 | 245 | 0 |
19 | Locked | 40.3 | 209 | 0 |
20 | Locked | 40.3 | 163 | 0 |
21 | Locked | 40.3 | 177 | 0 |
22 | Locked | 40.3 | 165 | 0 |
23 | Locked | 40.3 | 272 | 0 |
24 | Locked | 40.3 | 258 | 0 |
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 36600000 | 43.5 | 5120 | 64 qam | 11 |
2 | 23600000 | 44.3 | 5120 | 64 qam | 13 |
3 | 30100000 | 43.8 | 5120 | 64 qam | 12 |
4 | 43100000 | 44.3 | 5120 | 64 qam | 10 |
5 | 49600000 | 44.3 | 5120 | 64 qam | 9 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 26 | 0 |
2 | ATDMA | 0 | 0 | 4 | 0 |
3 | ATDMA | 0 | 0 | 8 | 0 |
4 | ATDMA | 0 | 0 | 7 | 0 |
5 | ATDMA | 0 | 0 | 6 | 0 |
Network access | Allowed |
Maximum Number of CPEs | 1 |
Baseline Privacy | Enabled |
DOCSIS Mode | Docsis30 |
Config file | 834ncxv9873254k;fg87dsfd; |
SFID | 23500 |
Max Traffic Rate | 402500089 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
SFID | 23499 |
Max Traffic Rate | 38500089 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Max Concatenated Burst | 42600 |
Scheduling Type | BestEffort |
on 22-02-2024 17:22
Do the T# happen at night like 2am?
on 22-02-2024 17:25
Post your network log please.
I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more
Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks
on 22-02-2024 19:03
See below:
Time Priority Description
22/02/2024 00:24:22 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/02/2024 00:24:22 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/02/2024 00:35:41 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/02/2024 12:24:22 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/02/2024 12:24:22 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/02/2024 00:24:21 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/02/2024 00:24:21 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/02/2024 12:55:7 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/02/2024 12:24:21 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/02/2024 12:24:21 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/02/2024 14:47:51 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
08/02/2024 00:24:21 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
08/02/2024 00:24:21 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/02/2024 00:32:43 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
04/02/2024 12:24:21 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
04/02/2024 12:24:21 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
02/02/2024 01:55:41 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
02/02/2024 01:55:39 | Warning! | B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
02/02/2024 01:54:1 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
02/02/2024 01:53:32 | critical |
on 23-02-2024 14:46
I would suggest a factory reset as below. There is something amiss with that number of T3 errors, it's as if the Hub is not completing a download from VM?
60 second factory pinhole reset as below;
Remove any ethernet cables from the Hub and hold the pinhole reset switch for 60 seconds. Do NOT reboot the Hub, just let it do it's thing. Note you will need the passwords from the bottom of the Hub afterwards, so make sure they are legible. NOTE this will remove any custom settings you may have set in the Hub, and they will all have to be setup again.
I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more
Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks
on 23-02-2024 17:05
Hi, I have tried this multiple times before and it doesn't make a difference, plus - the hub is running in Modem mode with my own router connected.
on 25-02-2024 10:31
VM will need to check this for you then. However you will need the Hub back in router mode for VM to do any checks. Call it in as a fault.
I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more
Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks
on 27-02-2024 12:11
Hey ellisb51, thank you for reaching out and I am so sorry to hear about this.
Thank you for confirming all this stuff you've done, let me send you a PM and we can take a look into this.
Matt - Forum Team
New around here?