on 24-02-2023 16:17
Hello, I keep disconneting, can you please look into that?
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 49600000 | 39.8 | 5120 KSym/sec | QAM64 | 1 |
2 | 23600000 | 38.8 | 5120 KSym/sec | QAM32 | 5 |
3 | 30100000 | 38.8 | 5120 KSym/sec | QAM64 | 4 |
4 | 36600000 | 39.3 | 5120 KSym/sec | QAM32 | 3 |
5 | 43100000 | 39.8 | 5120 KSym/sec | QAM64 | 2 |
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 |
6 | 10.0 | 34.5 | 2K | QAM8 |
6 | OFDMA | 200 | 53.9 | 1 | 0 |
Answered! Go to Answer
on 02-03-2023 14:23
Thanks for speaking with us today @MasterJpe on the forums.
I'm glad we have been able to investigate what the issue is.
We have all the details mentioned in our conversation for the appointment that is required, you can also view them here on MyVM.
As advised - let us know how it goes with the appointment and always reach out to us if you ever need anything.
Kind regards,
Ilyas.
on 24-02-2023 16:17
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
25 | 330750000 | 7.6 | 37.6 | QAM256 | 25 |
18 | 274750000 | 6.7 | 37.6 | QAM256 | 18 |
19 | 282750000 | 7.4 | 37.6 | QAM256 | 19 |
20 | 290750000 | 6.7 | 37.6 | QAM256 | 20 |
21 | 298750000 | 6 | 37.4 | QAM256 | 21 |
22 | 306750000 | 6.9 | 37.6 | QAM256 | 22 |
23 | 314750000 | 6.4 | 37.6 | QAM256 | 23 |
24 | 322750000 | 6.6 | 37.6 | QAM256 | 24 |
26 | 338750000 | 6 | 37.6 | QAM256 | 26 |
27 | 346750000 | 6.1 | 37.4 | QAM256 | 27 |
28 | 354750000 | 6.9 | 37.6 | QAM256 | 28 |
29 | 362750000 | 5.1 | 37.4 | QAM256 | 29 |
30 | 370750000 | 5.5 | 37.6 | QAM256 | 30 |
31 | 378750000 | 6 | 37.6 | QAM256 | 31 |
32 | 386750000 | 4.5 | 37.6 | QAM256 | 32 |
33 | 394750000 | 5.1 | 37.4 | QAM256 | 33 |
34 | 402750000 | 5.5 | 37.6 | QAM256 | 34 |
35 | 410750000 | 4.1 | 37.4 | QAM256 | 35 |
36 | 418750000 | 5.1 | 37.6 | QAM256 | 36 |
37 | 426750000 | 5.5 | 37.6 | QAM256 | 37 |
38 | 434750000 | 4.4 | 37.6 | QAM256 | 38 |
39 | 442750000 | 5.7 | 37.6 | QAM256 | 39 |
40 | 450750000 | 5.7 | 37.4 | QAM256 | 40 |
41 | 458750000 | 4.1 | 37.4 | QAM256 | 41 |
42 | 466750000 | 5.1 | 37.6 | QAM256 | 42 |
43 | 474750000 | 4.4 | 37.4 | QAM256 | 43 |
44 | 482750000 | 3.8 | 37.4 | QAM256 | 44 |
45 | 490750000 | 4.3 | 37.4 | QAM256 | 45 |
46 | 498750000 | 4.4 | 37.4 | QAM256 | 46 |
47 | 506750000 | 3.3 | 37.6 | QAM256 | 47 |
48 | 514750000 | 3.8 | 37.6 | QAM256 | 48 |
Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
25 | Locked | 37.636276 | 0 | 0 |
18 | Locked | 37.636276 | 0 | 0 |
19 | Locked | 37.636276 | 0 | 0 |
20 | Locked | 37.636276 | 0 | 0 |
21 | Locked | 37.355988 | 0 | 0 |
22 | Locked | 37.636276 | 0 | 0 |
23 | Locked | 37.636276 | 0 | 0 |
24 | Locked | 37.636276 | 0 | 0 |
26 | Locked | 37.636276 | 0 | 0 |
27 | Locked | 37.355988 | 0 | 0 |
28 | Locked | 37.636276 | 0 | 0 |
29 | Locked | 37.355988 | 0 | 0 |
30 | Locked | 37.636276 | 0 | 0 |
31 | Locked | 37.636276 | 0 | 0 |
32 | Locked | 37.636276 | 0 | 0 |
33 | Locked | 37.355988 | 0 | 0 |
34 | Locked | 37.636276 | 0 | 0 |
35 | Locked | 37.355988 | 0 | 0 |
36 | Locked | 37.636276 | 0 | 0 |
37 | Locked | 37.636276 | 0 | 0 |
38 | Locked | 37.636276 | 0 | 0 |
39 | Locked | 37.636276 | 0 | 0 |
40 | Locked | 37.355988 | 0 | 0 |
41 | Locked | 37.355988 | 0 | 0 |
42 | Locked | 37.636276 | 0 | 0 |
43 | Locked | 37.355988 | 0 | 0 |
44 | Locked | 37.355988 | 0 | 0 |
45 | Locked | 37.355988 | 0 | 0 |
46 | Locked | 37.355988 | 0 | 0 |
47 | Locked | 37.636276 | 0 | 0 |
48 | Locked | 37.636276 | 0 | 0 |
on 24-02-2023 16:18
Time Priority Description
Fri 24/02/2023 15:29:12 | 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; |
Fri 24/02/2023 15:06:36 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 24/02/2023 14:58:31 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 24/02/2023 14:04:16 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 24/02/2023 13:40:41 | 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; |
Fri 24/02/2023 13:33:42 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 24/02/2023 12:58:23 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 24/02/2023 12:49:10 | 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; |
Fri 24/02/2023 12:32:01 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 24/02/2023 11:58:31 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 24/02/2023 09:26:15 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 24/02/2023 08:57:09 | 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; |
Fri 24/02/2023 08:23:30 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 24/02/2023 08:01:37 | 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; |
Fri 24/02/2023 07:52:08 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 24/02/2023 07:44:18 | 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; |
Fri 24/02/2023 03:09:49 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 24/02/2023 03:05:19 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 24/02/2023 01:35:44 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 24/02/2023 01:04:45 | 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 24/02/2023 01:02:41 | 4 | DBC-ACK not received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 24/02/2023 00:00:19 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 23/02/2023 23:49:26 | 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 23/02/2023 22:57:10 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 23/02/2023 21:18:50 | 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 23/02/2023 20:56:44 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 23/02/2023 20:45:28 | 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 23/02/2023 20:26:49 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 23/02/2023 19:52:26 | 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 23/02/2023 18:56:50 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 23/02/2023 18:45:58 | 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 23/02/2023 18:26:46 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 23/02/2023 17:12:57 | 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 23/02/2023 17:10:04 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 23/02/2023 17:08:21 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 23/02/2023 16:56:50 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 23/02/2023 16:37:01 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 23/02/2023 16:36:54 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 23/02/2023 15:42:51 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 23/02/2023 14:56:38 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 23/02/2023 14:01:27 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 23/02/2023 13:37:00 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 23/02/2023 11:39:55 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 23/02/2023 09:56:33 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 23/02/2023 09:46:24 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt057-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 23/02/2023 09:46:24 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 23/02/2023 07:36:40 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 23/02/2023 07:25:35 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 23/02/2023 06:50:56 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 23/02/2023 00:26:24 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
on 27-02-2023 10:34
Hey there @MasterJpe, thanks for reaching out to us on the Virgin Media forums. 👋🏼
I'm sorry to see this issue occur with the connection. 😞
I've checked on our end and this will need further investigating.
I will send a private message - watch out for the purple envelope inviting you in.
Kind regards,
Ilyas.
on 02-03-2023 14:23
Thanks for speaking with us today @MasterJpe on the forums.
I'm glad we have been able to investigate what the issue is.
We have all the details mentioned in our conversation for the appointment that is required, you can also view them here on MyVM.
As advised - let us know how it goes with the appointment and always reach out to us if you ever need anything.
Kind regards,
Ilyas.
on 04-03-2023 13:02
Hello,
Engineer find out lot of noise, so he changed the cabel and added some 4db atachment. Everything start geting balanced on graph after that. Let see how is going but I belive he has sorted out.
Thank you for your help and time!
on 07-03-2023 19:04
Hello, well isnt sorted, it was ok all saturday, but T3 timeouts are back.
on 10-03-2023 11:50
Hi MasterJpe 👋 thank you for returning to the thread and keeping us updated.
Really sorry to hear the issues have not been resolved, and you are still having problems! I've had a quick look on our systems for you today and it does look as though there were a significant number of disconnections on the hub between Monday and Wednesday this week, although this has now stabilised in the past 24 or so hours. How are things at your end?
Please let us know if you are still having major issues and we can get another tech booked back out to you ASAP.
Wishing you all the best. 🌞