29-05-2023 01:55 - edited 29-05-2023 02:51
For the second time in the last 3 days, I have been experiencing dropouts in the early hours.
The time stamps for the network log are not showing the correct time and there was a dropout due to improvement work last week which was supposed to be a six hour period but mine was only down for 10 or 15 minutes. No area problems are now showing on status check on app or on the phone version.
Power levels look okay to me but network log certainly isn't.
My original hub 3 was replaced with a hub 5 a week ago as that showed up as faulty to the offshore techs.
My gut feeling is that this is an external network problem as I have a new cable to the cabinet and my indoor cable goes straight into the hub 5. F connector is tight. The two technicians who installed the hub 5 last week checked everything and said it was fine, which it was until these intermittent dropouts after midnight started. Yesterday's dropouts were accompanied by 28 post RS errors on one channel, but no post RS errors today.
https://www.thinkbroadband.com/broadband/monitoring/quality/share/32e0c93de66d840572d736b376ac2f931c075a8d-29-05-2023
The 2AM and 7AM outages on the left were hub reboots by me to see if it helped. It was fine all day but started dropping out again after midnight.
Downstream bonded channels
1 | 330000000 | 8.3 | 41 | QAM 256 | 25 |
2 | 138000000 | 8.8 | 41 | QAM 256 | 1 |
3 | 146000000 | 8.8 | 41 | QAM 256 | 2 |
4 | 154000000 | 8.7 | 41 | QAM 256 | 3 |
5 | 162000000 | 8.7 | 41 | QAM 256 | 4 |
6 | 170000000 | 8.7 | 41 | QAM 256 | 5 |
7 | 178000000 | 8.8 | 41 | QAM 256 | 6 |
8 | 186000000 | 8.7 | 41 | QAM 256 | 7 |
9 | 194000000 | 8.7 | 41 | QAM 256 | 8 |
10 | 202000000 | 8.4 | 41 | QAM 256 | 9 |
11 | 210000000 | 8.2 | 41 | QAM 256 | 10 |
12 | 218000000 | 8.1 | 41 | QAM 256 | 11 |
13 | 226000000 | 8.1 | 41 | QAM 256 | 12 |
14 | 234000000 | 8.2 | 41 | QAM 256 | 13 |
15 | 242000000 | 8.3 | 41 | QAM 256 | 14 |
16 | 250000000 | 8.1 | 41 | QAM 256 | 15 |
17 | 258000000 | 8.2 | 41 | QAM 256 | 16 |
18 | 266000000 | 8.3 | 29 | QAM 256 | 17 |
19 | 274000000 | 8.5 | 41 | QAM 256 | 18 |
20 | 282000000 | 8.5 | 41 | QAM 256 | 19 |
21 | 290000000 | 8.6 | 41 | QAM 256 | 20 |
22 | 298000000 | 8.6 | 41 | QAM 256 | 21 |
23 | 306000000 | 8.5 | 41 | QAM 256 | 22 |
24 | 314000000 | 8.3 | 41 | QAM 256 | 23 |
25 | 322000000 | 8.4 | 41 | QAM 256 | 24 |
26 | 338000000 | 8.4 | 41 | QAM 256 | 26 |
27 | 346000000 | 8.4 | 41 | QAM 256 | 27 |
28 | 354000000 | 8.4 | 41 | QAM 256 | 28 |
29 | 362000000 | 8.4 | 41 | QAM 256 | 29 |
30 | 370000000 | 8.4 | 41 | QAM 256 | 30 |
31 | 378000000 | 8.7 | 41 | QAM 256 | 31 |
Downstream bonded channels
1 | Locked | 41 | 323 | 0 |
2 | Locked | 41 | 29 | 0 |
3 | Locked | 41 | 23 | 0 |
4 | Locked | 41 | 17 | 0 |
5 | Locked | 41 | 14 | 0 |
6 | Locked | 41 | 22 | 0 |
7 | Locked | 41 | 11 | 0 |
8 | Locked | 41 | 18 | 0 |
9 | Locked | 41 | 19 | 0 |
10 | Locked | 41 | 14 | 0 |
11 | Locked | 41 | 31 | 0 |
12 | Locked | 41 | 28 | 0 |
13 | Locked | 41 | 47 | 0 |
14 | Locked | 41 | 35 | 0 |
15 | Locked | 41 | 29 | 0 |
16 | Locked | 41 | 135 | 0 |
17 | Locked | 41 | 88 | 0 |
18 | Locked | 29 | 158 | 0 |
19 | Locked | 41 | 133 | 0 |
20 | Locked | 41 | 208 | 0 |
21 | Locked | 41 | 221 | 0 |
22 | Locked | 41 | 195 | 0 |
23 | Locked | 41 | 413 | 0 |
24 | Locked | 41 | 203 | 0 |
25 | Locked | 41 | 480 | 0 |
26 | Locked | 41 | 265 | 0 |
27 | Locked | 41 | 184 | 0 |
28 | Locked | 41 | 163 | 0 |
29 | Locked | 41 | 76 | 0 |
30 | Locked | 41 | 89 | 0 |
31 | Locked | 41 | 110 | 0 |
Upstream bonded channels
0 | 49600000 | 43.3 | 5120 | QAM 64 | 1 |
1 | 43100000 | 43.3 | 5120 | QAM 64 | 2 |
2 | 36600000 | 43.3 | 5120 | QAM 64 | 3 |
3 | 30100000 | 43 | 5120 | QAM 64 | 4 |
4 | 23600000 | 43 | 5120 | QAM 64 | 5 |
Upstream bonded channels
0 | ATDMA | 0 | 0 | 0 | 0 |
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
Network Log
29-05-2023 03:14:00 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-05-2023 03:13:54 | warning | TCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-05-2023 03:12:57 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-05-2023 03:12:54 | warning | 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; |
29-05-2023 02:59:05 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-05-2023 02:58:53 | warning | TCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-05-2023 02:57:55 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-05-2023 02:57:53 | warning | 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; |
29-05-2023 02:44:00 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-05-2023 02:43:38 | warning | TCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-05-2023 02:43:02 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-05-2023 02:42:38 | warning | 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; |
29-05-2023 02:28:46 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
28-05-2023 23:03:48 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
28-05-2023 23:03:48 | warning | 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; |
29-05-2023 03:09 - edited 29-05-2023 03:18
It looks like the first dropout today was bang on midnight, which is interesting.
Network log isn't showing any new errors, it looks like it was unstable for less than an hour.
Network Log
29-05-2023 03:14:00 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-05-2023 03:13:54 | warning | TCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-05-2023 03:12:57 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-05-2023 03:12:54 | warning | 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; |
29-05-2023 02:59:05 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-05-2023 02:58:53 | warning | TCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-05-2023 02:57:55 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-05-2023 02:57:53 | warning | 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; |
29-05-2023 02:44:00 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-05-2023 02:43:38 | warning | TCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-05-2023 02:43:02 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-05-2023 02:42:38 | warning | 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; |
29-05-2023 02:28:46 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
28-05-2023 23:03:48 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
28-05-2023 23:03:48 | warning | 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; |
28-05-2023 21:59:18 | warning | 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; |
28-05-2023 21:59:18 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
28-05-2023 21:32:48 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
28-05-2023 21:32:48 | warning | 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; |
28-05-2023 20:28:04 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
28-05-2023 20:28:04 | warning | 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; |
28-05-2023 20:12:07 | warning | 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; |
28-05-2023 20:12:07 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
28-05-2023 19:02:26 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
28-05-2023 19:02:26 | warning | 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; |
28-05-2023 18:41:28 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
28-05-2023 18:41:28 | warning | 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; |
28-05-2023 17:36:34 | warning | 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; |
28-05-2023 17:36:34 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
28-05-2023 17:10:50 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
28-05-2023 17:10:50 | warning | 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; |
28-05-2023 16:09:01 | warning | 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; |
on 31-05-2023 09:12
Tech support have booked an engineer to check out the cabinet as they suspect there may be an intermittent local area network problem.
I think it might have something to do with the six hour local area maintenance/upgrade event last week, because these early morning dropouts started after that.
on 31-05-2023 09:15
Hi @tonyw2,
Welcome back to our Community Forums! Thank you for your post and I'm sorry to hear that you're having some broadband connection issues!
I've taken a look at our systems and there are no local issues listed that could be causing this issue. This means that there could be an issue with the Hub connection itself.
Looking at your power levels, I can see that there's some issues with your connection. To look into this further for you, I'll send you a Private Message to confirm some details.
Please keep an eye out for an envelope at the top right corner of your Forum page. If you're having issues locating this, please let me know and I can help. I'll be in touch soon.
Thank you.
on 31-05-2023 09:32
Hi @tonyw2,
Thank you for coming back to me via Private Message. I'm glad to hear that our team was able to look into this for your further already!
Please keep us updated on how you're getting on and if there's anything else we can do to help.
We're here if you need us.
Thank you! 😊
on 31-05-2023 09:37
Thanks, but I won't know anything until the 8th June as that was the first available date for a network engineer to check the cabinet.
Fingers crossed they find something, I hate intermittent faults.
on 01-06-2023 07:37
Hi Paulina-Z,
After a period of no errors, during the 24 hour VM monitoring, errors are reoccurring. I have sent you a PM.
on 01-06-2023 10:24
Hi @tonyw2,
Thank you for coming back to me via private message and confirming your details. I have now booked you a technician visit for ongoing connection issue – you can check and amend the date and time of your appointment via your online account.
There will be no charge for this visit unless:
• The technician diagnoses the faults as not being caused by our network/equipment
• The technician discovers that the fault or problem relates to your equipment
• The technician discovers that the fault or problem relates to any system that we are not responsible for
The technician will confirm during their visit if any of these instances apply, and if so, a £25 charge will be applied to your account.
Please ensure there is someone over the age of 18 present at the time of the visit. If you need to change or cancel your appointment you can do this online or via the MyVM app by 4pm the day before the appointment.
If you do miss an agreed appointment for any reason, a £25 missed appointment charge will be applied to your account on the day of the appointment.
Please keep us updated on how your appointment goes and if you need any further assistance.
Thank you.
on 01-06-2023 11:40
Hi @tonyw2,
Thanks for coming back to me via Private Message! Glad to hear that you're happy with the date and time of the appointment!
Please let us know how you get on and if you need any further help going forward!
Thank you! 😊
on 02-06-2023 10:34
Hi Paulina,
The engineer has just left. He was very thorough and checked everything at my house and found no problems, but for good measure re-made all of the "F" connectors and fitted an attenuator because, although within specification, the power levels were on the high side.
He agreed that there have been intermittent dropouts and hopes that the problem will be resolved by the network engineer when he attends the cabinet next week.
Most importantly for me is that everything is okay in my house and if a problem does occur, whilst I am away, it will almost certainly be external to my house and therefore will not need access to rectify.
Thanks for your help.