on 28-12-2023 15:07
My cable modem will suddenly no longer go online. I’ve tried reconnecting the coax cable on the modem and at the wall with no success. Any ideas? Does this need an engineer? Here are the logs.
Thanks
Time Priority Description
Thu 01/01/1970 00:01:42 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:01:42 | 3 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 28/12/2023 15:00:23 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 28/12/2023 15:00:21 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 28/12/2023 15:00:20 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 25; 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; |
Thu 28/12/2023 15:00:20 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 28/12/2023 15:00:19 | 6 | CM-STATUS message sent. Event Type Code: 21; 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; |
Thu 28/12/2023 15:00:19 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 28/12/2023 15:00:16 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 28/12/2023 15:00:10 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 28/12/2023 15:00:01 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 28/12/2023 15:00:00 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 28/12/2023 14:59:58 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 28/12/2023 14:59:49 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 28/12/2023 14:59:47 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 28/12/2023 14:59:45 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 28/12/2023 14:59:42 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 28/12/2023 14:59:35 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 28/12/2023 14:59:35 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 28/12/2023 14:59:31 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 28/12/2023 14:59:11 | 6 | CM-STATUS message sent. Event Type Code: 3; Chan ID: N/A; DSID: 959006; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 28/12/2023 14:59:03 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 28/12/2023 14:59:03 | 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; |
Thu 28/12/2023 14:58:45 | 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 28/12/2023 14:53:36 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 28/12/2023 14:53:34 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 28/12/2023 14:53:31 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 28/12/2023 14:53:31 | 6 | CM-STATUS message sent. Event Type Code: 21; 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; |
Thu 28/12/2023 14:53:28 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 28/12/2023 14:41: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; |
Thu 28/12/2023 14:41:18 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 28/12/2023 14:41:18 | 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; |
Thu 28/12/2023 14:41:08 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 28/12/2023 14:41:08 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 28/12/2023 14:40:56 | 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 01/01/1970 00:03:59 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:01:43 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:01:43 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:01:37 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:01:34 | 3 | No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:01:24 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 28/12/2023 14:35:27 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 28/12/2023 14:35:24 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 28/12/2023 14:35:24 | 6 | CM-STATUS message sent. Event Type Code: 21; 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; |
Thu 28/12/2023 14:35:22 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 28/12/2023 14:35:21 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER |
Answered! Go to Answer
on 28-12-2023 15:46
Check with Area faults on 0800 561 0061 If you have a VM landline 150 this goes down to post code level. You could also try the web page status, but this is not recommended as it only covers issues that affect a very large number of customers.
VM will not dispatch any technicians while an area fault exists.
If no area faults found:
The primary place to report faults or for service requests is Customer Services on 0345 454 1111/150 if you have a VM landline or wait two or three days for a VM staff member to get to your post.
on 28-12-2023 15:10
ItemStatusCommentsCable Modem Status
Primary downstream channel
Channel OverviewDownstreamUpstreamDOCSIS 3.0 channels
DOCSIS 3.1 channels
25 | 331000000 | -18.2 | 30.4 | QAM256 | 25 |
25 | Locked | 30.366289 | 0 | 0 |
1 | 0 |
1 | 0 | 0 |
6 | 10.0 | 58.2 | 2K | QAM8 |
6 | OFDMA | 200 | 53.9 | 0 | 0 |
on 28-12-2023 15:46
Check with Area faults on 0800 561 0061 If you have a VM landline 150 this goes down to post code level. You could also try the web page status, but this is not recommended as it only covers issues that affect a very large number of customers.
VM will not dispatch any technicians while an area fault exists.
If no area faults found:
The primary place to report faults or for service requests is Customer Services on 0345 454 1111/150 if you have a VM landline or wait two or three days for a VM staff member to get to your post.
on 31-12-2023 08:42
It eventually came back online after several hours and has been fine since apart from going offline again last night (back on this morning). Posting signal levels just to check if they’re ok. Is only 1 upstream channel normal?
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
4 | 163000000 | -6.5 | 38.6 | QAM256 | 4 |
1 | 139000000 | -5.3 | 39 | QAM256 | 1 |
2 | 147000000 | -5.3 | 38.6 | QAM256 | 2 |
3 | 155000000 | -5.7 | 38.6 | QAM256 | 3 |
5 | 171000000 | -7.2 | 37.6 | QAM256 | 5 |
6 | 179000000 | -7.5 | 37.6 | QAM256 | 6 |
7 | 187000000 | -7.7 | 37.6 | QAM256 | 7 |
8 | 195000000 | -7.8 | 38.6 | QAM256 | 8 |
9 | 203000000 | -7.7 | 37.6 | QAM256 | 9 |
10 | 211000000 | -7.7 | 36.4 | QAM256 | 10 |
11 | 219000000 | -7.7 | 37.6 | QAM256 | 11 |
12 | 227000000 | -7.8 | 37.4 | QAM256 | 12 |
13 | 235000000 | -8 | 38.6 | QAM256 | 13 |
14 | 243000000 | -8.3 | 37.6 | QAM256 | 14 |
15 | 251000000 | -8.6 | 37.6 | QAM256 | 15 |
16 | 259000000 | -8.4 | 37.6 | QAM256 | 16 |
17 | 267000000 | -8.6 | 37.4 | QAM256 | 17 |
18 | 275000000 | -8.7 | 37.4 | QAM256 | 18 |
19 | 283000000 | -9 | 37.6 | QAM256 | 19 |
20 | 291000000 | -9 | 37.6 | QAM256 | 20 |
21 | 299000000 | -8.9 | 37.6 | QAM256 | 21 |
22 | 307000000 | -8.8 | 37.6 | QAM256 | 22 |
23 | 315000000 | -9 | 37.6 | QAM256 | 23 |
24 | 323000000 | -9.3 | 37.6 | QAM256 | 24 |
25 | 331000000 | -9.8 | 37.4 | QAM256 | 25 |
26 | 339000000 | -9.8 | 37.4 | QAM256 | 26 |
27 | 347000000 | -9.9 | 37.4 | QAM256 | 27 |
28 | 355000000 | -10.5 | 36.6 | QAM256 | 28 |
29 | 363000000 | -10.3 | 37.4 | QAM256 | 29 |
30 | 371000000 | -10.1 | 37.4 | QAM256 | 30 |
31 | 379000000 | -10.2 | 37.6 | QAM256 | 31 |
159 | 96 | 4K | 1840 | QAM256 | 759 |
159 | Locked | 35 | -14.3 | 2811577 | 5896 |
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 0 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | 0 | 0 |
6 | 10.0 | 49.0 | 2K | QAM128 |
6 | OFDMA | 200 | 53.9 | 0 | 0 |
on 31-12-2023 09:08
Less than a minute after posting that it’s gone offline again with sync/timing errors
on 01-01-2024 11:51
Hey @DannyF Thanks for reaching out to us on the Virgin Media forums. 👋🏼
I'm sorry to hear about the issues with the connection you've had recently.
Have you used the advice given by Tudor on this thread and checked to see if there's any outages in the area?
Let us know and we can progress from there.
Kind regards,
Ilyas.
on 01-01-2024 12:21
Yes, I called and a tech visit is scheduled. Thanks