04-03-2023 17:05 - edited 04-03-2023 17:06
Hi community,
I've been having issues recently with my internet dropping multiple times every single day for the past couple weeks. The only way to fix it is to reboot the Hub4 modem, otherwise the internet is never restored.
Apparently no faults in the post code checker.
Please let me know if i can provide anything more from my side.
It's not letting me directly paste the logs so i have pasted them as plain text below
Thanks
Nick
Network Log
Time Priority Description
Sat Mar
3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Mar
5 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Mar
6 US profile assignment change. US Chan ID: 14; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Mar
5 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Mar
3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Mar
6 US profile assignment change. US Chan ID: 14; Previous Profile: ; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Mar
5 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;
Fri Mar
5 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Mar
6 US profile assignment change. US Chan ID: 14; Previous Profile: ; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Mar
5 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;
Fri Mar
5 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Mar
6 US profile assignment change. US Chan ID: 14; Previous Profile: ; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Mar
5 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;
Fri Mar
5 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Mar
6 US profile assignment change. US Chan ID: 14; Previous Profile: ; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Mar
3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Mar
3 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Mar
3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Mar
3 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Mar
3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Mar
3 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Mar
3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Mar
3 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Mar
3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Mar
3 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Mar
3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Mar
3 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Feb
28 6 US profile assignment change. US Chan ID: 14; Previous Profile: ; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Feb
28 5 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Feb
28 6 CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Feb
28 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Feb
28 5 Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Feb
28 6 CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Feb
28 5 Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Feb
28 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Feb
28 6 US profile assignment change. US Chan ID: 14; Previous Profile: ; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Feb
28 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Feb
28 6 US profile assignment change. US Chan ID: 14; Previous Profile: ; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Feb
28 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Feb
28 6 US profile assignment change. US Chan ID: 14; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Feb
28 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Feb
28 6 US profile assignment change. US Chan ID: 14; Previous Profile: ; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Feb
28 5 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;
Tue Feb
28 5 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Feb
28 4 DBC-ACK not received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Feb
27 6 US profile assignment change. US Chan ID: 14; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Feb
27 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Feb
26 6 US profile assignment change. US Chan ID: 14; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Feb
26 5 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Feb
26 4 DBC-ACK not received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Answered! Go to Answer
on 07-03-2023 14:43
Hi @nickdems
Thanks for posting and welcome to the community.
I am sorry to hear of the broadband issues. You are affected by an SNR issue (signal to noise ratio).
F010527723 - fault reference number.
The estimated fix date is tomorrow at 10.15AM. Please do monitor the connection after this time and report back if any issues.
Kind regards.
Need a helpful hand to show you how to make a payment? Check out our guide - How to pay my Virgin Media bill
on 04-03-2023 17:05
3.0 Upstream channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 23600000 45.020599 5120 KSym/sec 32QAM 13
2 30100000 45.520599 5120 KSym/sec 64QAM 12
3 36600000 46.520599 5120 KSym/sec 32QAM 11
4 43100000 46.520599 5120 KSym/sec 64QAM 10
5 49600000 47.020599 5120 KSym/sec 64QAM 9
3.0 Upstream channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 US_TYPE_ATDMA 0 0 0 0
2 US_TYPE_ATDMA 0 0 0 0
3 US_TYPE_ATDMA 0 0 0 0
4 US_TYPE_ATDMA 0 0 0 0
5 US_TYPE_ATDMA 0 0 0 0
3.1 Upstream channels
Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation
14 10.0 41.2 2K QAM8
3.1 Upstream channels
Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts
14 OFDMA 200 53.9 1 0
on 04-03-2023 17:06
3.0 Downstream channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
8 195000000 1.599998 40.946209 QAM256 8
4 163000000 2.299999 40.366287 QAM256 4
5 171000000 2.000000 40.946209 QAM256 5
6 179000000 1.799999 40.946209 QAM256 6
7 187000000 1.799999 40.946209 QAM256 7
9 203000000 1.299999 40.946209 QAM256 9
10 211000000 1.099998 40.946209 QAM256 10
11 219000000 1.099998 40.946209 QAM256 11
12 227000000 1.200001 40.946209 QAM256 12
13 235000000 1.099998 40.946209 QAM256 13
14 243000000 0.900002 40.946209 QAM256 14
15 251000000 0.400002 40.366287 QAM256 15
16 259000000 -0.299999 40.946209 QAM256 16
17 267000000 -0.799999 40.366287 QAM256 17
18 275000000 -0.099998 40.946209 QAM256 18
19 283000000 0.299999 40.946209 QAM256 19
20 291000000 0.599998 40.946209 QAM256 20
21 299000000 0.700001 40.946209 QAM256 21
22 307000000 0.799999 40.366287 QAM256 22
23 315000000 0.900002 40.946209 QAM256 23
24 323000000 1.200001 40.946209 QAM256 24
25 331000000 1.400002 40.366287 QAM256 25
26 339000000 1.500000 40.946209 QAM256 26
27 347000000 1.500000 40.946209 QAM256 27
28 355000000 1.500000 40.366287 QAM256 28
29 363000000 1.500000 40.946209 QAM256 29
30 371000000 1.799999 40.366287 QAM256 30
31 379000000 1.799999 40.946209 QAM256 31
32 387000000 2.000000 40.946209 QAM256 32
33 395000000 1.400002 40.946209 QAM256 33
34 403000000 0.900002 40.366287 QAM256 34
3.0 Downstream channels
Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
8 Locked 40.946209 0 0
4 Locked 40.366287 0 0
5 Locked 40.946209 0 0
6 Locked 40.946209 0 0
7 Locked 40.946209 0 0
9 Locked 40.946209 0 0
10 Locked 40.946209 0 0
11 Locked 40.946209 0 0
12 Locked 40.946209 0 0
13 Locked 40.946209 0 0
14 Locked 40.946209 0 0
15 Locked 40.366287 0 0
16 Locked 40.946209 0 0
17 Locked 40.366287 0 0
18 Locked 40.946209 0 0
19 Locked 40.946209 0 0
20 Locked 40.946209 0 0
21 Locked 40.946209 0 0
22 Locked 40.366287 0 0
23 Locked 40.946209 0 0
24 Locked 40.946209 0 0
25 Locked 40.366287 0 0
26 Locked 40.946209 0 0
27 Locked 40.946209 0 0
28 Locked 40.366287 0 0
29 Locked 40.946209 0 0
30 Locked 40.366287 0 0
31 Locked 40.946209 0 0
32 Locked 40.946209 0 0
33 Locked 40.946209 0 0
34 Locked 40.366287 0 0
3.1 Downstream channels
Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
159 96 4K 1840 QAM4096 759
3.1 Downstream channels
Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
159 Locked 42 -1.3 215064 0
on 07-03-2023 14:43
Hi @nickdems
Thanks for posting and welcome to the community.
I am sorry to hear of the broadband issues. You are affected by an SNR issue (signal to noise ratio).
F010527723 - fault reference number.
The estimated fix date is tomorrow at 10.15AM. Please do monitor the connection after this time and report back if any issues.
Kind regards.
Need a helpful hand to show you how to make a payment? Check out our guide - How to pay my Virgin Media bill
08-03-2023 00:02 - edited 08-03-2023 00:02
Hi John,
The connection has been stable the last 24h, will keep an eye on it and let you know if it starts to drop again.
Cheers,
Nick