QAM woes, again.

[Icantcrabhere]

Hi, this may be a somewhat lengthy post,
I'll have to split hub readings from the other day / after a restart today.

The basics out of the way first:

Superhub 3, modem mode. - wired
I have made sure all connections are finger tight.
I have checked both the online fault checker and the phone one

The following first set of logs I post will be from then (Before rebooting the hub).

The other night, 7th July - I noticed a huge latency spike, this turned out to be a Partial service error.

Obviously along with that comes a flood of post-RS errors, as expected.


The following first set of logs I post will be from then (Before rebooting the hub).
I am sorry for the formatting on this particular section:

Time Priority Description
07/07/2022 00:07:15 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/07/2022 00:07:14 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/07/2022 00:07:14 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/07/2022 00:06:16 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/07/2022 00:06:15 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/07/2022 00:05:14 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/07/2022 00:05:14 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/07/2022 00:03:28 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 40.3 3057 6731
2 Locked 40.9 1858 7104
3 Locked 40.9 1836 7435
4 Locked 40.9 1828 5666
5 Locked 40.3 1621 5757
6 Locked 40.3 1627 5633
7 Locked 40.3 1811 5775
8 Locked 40.3 1808 5749
9 Locked 40.3 1573 5101
10 Locked 40.3 1876 5284
11 Locked 40.3 1689 5669
12 Locked 40.3 1896 5574
13 Locked 40.3 2822 6718
14 Locked 40.3 1878 6648
15 Locked 40.9 1831 6211
16 Locked 40.3 1893 6552
17 Locked 40.3 2115 6110
18 Locked 38.9 2531 7290
19 Locked 40.3 2399 7146
20 Locked 38.6 3513 7108
21 Locked 38.9 3432 7220
22 Locked 38.9 3493 6851
23 Locked 38.9 3308 6668
24 Locked 38.6 3401 6886

Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 ATDMA 0 0 10 0
2 ATDMA 0 0 12 0
3 ATDMA 0 0 6 0
4 ATDMA 0 0 12 0


Even through this, all my upstream QAM were locked to 64,
Until today, that is.
The following posts will show todays logs AFTER a reboot.

[Icantcrabhere]

Thank you Matthew,
greatly appreciated 🙂

[Matthew_ML]

Hey Icantcrabhere, its no problem at all.

It was my pleasure. Thanks 

[Icantcrabhere]

A small update, a bit of a journal entry if you will.
Regardless of what I say here:
Matthew_ML has been wonderful to work with, i can't give him enough thanks.

Between the start of this thread and the last message in here, it has truly been a nightmare.



Multiple technicians,
many modulation drops and much disappointment(A great book title if you ask me)
We're still no closer in reality to what the route cause of the modulation drops is.

The last technican (Who I actually had to put a complaint in about) had no idea what was causing the issues, so instead has booked a repull for September 15th, however we know how these dates go.
A true shot in the dark, as it were.

Since the tech visited and fidlled with stuff in the cabinet and added attenuators to my line(I have no idea why honestly), the modulation drops have been worse and so has the rate of which PRE-RS errors are rising.

I should have guessed the "work" he'd do would be questionable after the "discussion" with him about a damaged drop cable going into next doors house.
I can elaborate on that further in a different post/PM if needed.



In regards to complaints i have put forward: I have a REF number, but I have no idea how to check up further on that, so maybe someone could help me with this too?

In follow up posts I'll post my current stats from the router log.

[Icantcrabhere]

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

1	539000000	-1.5	38	256 qam	17
2	547000000	-1.7	38	256 qam	18
3	555000000	-1.7	38	256 qam	19
4	563000000	-1.9	38	256 qam	20
5	571000000	-2.2	38	256 qam	21
6	579000000	-2.4	38	256 qam	22
7	587000000	-2.4	38	256 qam	23
8	595000000	-2.2	38	256 qam	24
9	603000000	-2.2	38	256 qam	25
10	611000000	-2.2	38	256 qam	26
11	619000000	-2.5	38	256 qam	27
12	627000000	-2.2	38	256 qam	28
13	635000000	-2.2	38	256 qam	29
14	643000000	-1.9	38	256 qam	30
15	651000000	-1.7	38	256 qam	31
16	659000000	-1.7	38	256 qam	32
17	667000000	-1.7	38	256 qam	33
18	675000000	-1.7	38	256 qam	34
19	683000000	-1.9	38	256 qam	35
20	691000000	-1.7	38	256 qam	36
21	699000000	-1.7	38	256 qam	37
22	707000000	-1.5	38	256 qam	38
23	715000000	-1.7	38	256 qam	39
24	723000000	-2	38	256 qam	40

Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1	Locked	38.6	569	0
2	Locked	38.6	892	0
3	Locked	38.6	743	0
4	Locked	38.9	793	0
5	Locked	38.9	1387	0
6	Locked	38.6	2007	0
7	Locked	38.9	1626	0
8	Locked	38.9	1142	0
9	Locked	38.9	1315	0
10	Locked	38.6	1942	0
11	Locked	38.9	2716	0
12	Locked	38.9	2576	0
13	Locked	38.6	2109	0
14	Locked	38.6	1750	0
15	Locked	38.9	1672	0
16	Locked	38.9	1552	0
17	Locked	38.9	1194	0
18	Locked	38.6	1136	0
19	Locked	38.9	1350	0
20	Locked	38.6	1306	0
21	Locked	38.9	1110	0
22	Locked	38.9	761	0
23	Locked	38.9	895	0
24	Locked	38.9	1175	0

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

1	46200000	42.5	5120	16 qam	1
2	32600000	40.8	5120	16 qam	3
3	25799907	40.3	5120	16 qam	4
4	39400000	41.2	5120	16 qam	2

[Icantcrabhere]

Sorry for the multiple posts,
Character limits need to be changed for this forum, I swear. aha

Network Log

Time Priority Description

27/08/2022 03:37:42	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/08/2022 22:01:25	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/08/2022 16:05:21	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/08/2022 15:33:9	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/08/2022 15:30:50	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/08/2022 15:30:45	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/08/2022 15:30:45	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/08/2022 15:30:45	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/08/2022 15:30:45	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2022 14:34:24	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2022 01:47:34	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2022 01:44:8	notice	NOTICE ATOM is restarted due to RPC timeout as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2022 01:39:34	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2022 01:36:38	notice	NOTICE ATOM is restarted due to RPC timeout as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2022 01:31:34	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2022 01:29:7	notice	NOTICE ATOM is restarted due to RPC timeout as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2022 01:23:34	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2022 01:21:36	notice	NOTICE ATOM is restarted due to RPC timeout as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2022 01:15:34	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2022 01:14:6	notice	NOTICE ATOM is restarted due to RPC timeout as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

I believe the "NOTICE ATOM" error was during overnight work (since the fault checker showed work due), but I can't be too sure.

Also I can't even use the online fault checker right now, as it seems to be down.
Guess I should rely on the phone one, really!

It's a shame about all these issues, since i've been with VM consistently since 2008~2009ish, and a while before that back in the day.
I've gone from recommending them to actually wanting people to avoid.

now it looks like Hey!Broadband are available in my area.
Hoping more people are going to post reviews + thinkbroadband graphs soon, so i can see how they are locally/generally - honestly looking tempting right now. 😞

[Icantcrabhere]

Once again adding to my own "Diary" as it were,
need to keep everything logged as best I can.

We were meant to be getting a re-pull,
this was meant to go ahead on the 15th of this month, however two Virgin engineers turned up for it today.

However they were UNABLE to do the job, as the original install, and I quote is "in the top 10 of the worst i've seen"

So they've had to take photos and are going to have to get back to us. - i'm unsure what this entails,

As of now:

My upstream modulation is once again in the gutter:

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

1	23600065	39	5120	32 qam	5
2	36600000	40	5120	32 qam	3
3	43099932	40.3	5120	32 qam	2
4	30100273	39.5	5120	16 qam	4
5	49599883	40.5	5120	64 qam	1

having a lovely small burst of packet loss occuring earlier today when the QAM decided to go bad, again:

https://www.thinkbroadband.com/broadband/monitoring/quality/share/2b531bfd99e9c7ef2d5b69ef22112a6703e1f1cc-12-09-2022

From SNR issues, to this,

Over 2 months since this thread started,
Other threads of mine spanning back even longer.

Truly not blessed.

[Adri_G]

Hey Icantcrabhere, thanks for the posts on our help forum.

We're sorry to see you've had ongoing issues with your services caused by a network fault, have you had a new date confirmed for this re-pull / cabling work yet to complete since you last posted here on Monday?

Please, let us know if you had any updates, glad to assist further if you still need us to.

[Icantcrabhere]

They've been and done the repull, i guess.

My power levels are all now out of spec.

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

1	49600000	49.5	5120	64 qam	1
2	36600000	48.8	5120	64 qam	3
3	30100000	48.3	5120	64 qam	4
4	43100040	49	5120	64 qam	2
5	23600044	47.8	5120	64 qam	5

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

1	411000000	-6.5	38	256 qam	1
2	419000000	-6.7	38	256 qam	2
3	427000000	-7	38	256 qam	3
4	435000000	-7.5	38	256 qam	4
5	443000000	-7.5	38	256 qam	5
6	451000000	-7.7	38	256 qam	6
7	459000000	-7.5	38	256 qam	7
8	467000000	-7.5	38	256 qam	8
9	475000000	-7.7	38	256 qam	9
10	483000000	-7.9	38	256 qam	10
11	491000000	-8	38	256 qam	11
12	499000000	-8.2	38	256 qam	12
13	507000000	-8.4	38	256 qam	13
14	515000000	-8.5	38	256 qam	14
15	523000000	-8.7	37	256 qam	15
16	531000000	-8.9	37	256 qam	16
17	539000000	-9	37	256 qam	17
18	547000000	-9.5	37	256 qam	18
19	555000000	-9.5	37	256 qam	19
20	563000000	-9.7	37	256 qam	20
21	571000000	-10	37	256 qam	21
22	579000000	-10.2	37	256 qam	22
23	587000000	-10.2	37	256 qam	23
24	595000000	-10	37	256 qam	24

They've driven off already, guessing no consideration to levels after the repull - so i'd assume they're just contractors?

Beyond a joke.
I need this fixed in a timely manner, i am really sick of being messed around.
A same day technician would be wonderful right about now...

[Icantcrabhere]

Update:

It wasn't even a full repull, just some sort of prep work.

The "2 man repull" isn't due now till October 26th (As I expected)
No real work seemed to have actually been carried out.

and I'm basically being ran in circles trying to get my power levels fixed, after they changed today!
In fact I feel like I'm actively being refused an engineer visit!

I need this escalated - if a VIP or mod can actually help.
This is unacceptable.
I need these levels fixed ASAP.

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

1	411000000	-6.5	38	256 qam	1
2	419000000	-6.7	38	256 qam	2
3	427000000	-7	38	256 qam	3
4	435000000	-7.4	38	256 qam	4
5	443000000	-7.7	38	256 qam	5
6	451000000	-7.7	38	256 qam	6
7	459000000	-7.5	38	256 qam	7
8	467000000	-7.5	38	256 qam	8
9	475000000	-7.7	38	256 qam	9
10	483000000	-7.7	38	256 qam	10
11	491000000	-8	38	256 qam	11
12	499000000	-8.2	38	256 qam	12
13	507000000	-8.4	38	256 qam	13
14	515000000	-8.5	38	256 qam	14
15	523000000	-8.7	37	256 qam	15
16	531000000	-8.9	37	256 qam	16
17	539000000	-9	37	256 qam	17
18	547000000	-9.4	37	256 qam	18
19	555000000	-9.5	37	256 qam	19
20	563000000	-9.5	37	256 qam	20
21	571000000	-10	37	256 qam	21
22	579000000	-10.2	37	256 qam	22
23	587000000	-10.2	37	256 qam	23
24	595000000	-10	37	256 qam	24

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

1	49600000	49.3	5120	64 qam	1
2	36600000	48.8	5120	64 qam	3
3	30100015	48.3	5120	64 qam	4
4	43099883	49	5120	64 qam	2
5	23600136	47.8	5120	64 qam	5

[pete_at_home]

Looks like they have moved your cable onto a different tap in the cabinet - hence your DS & US levels are wrong.

The US flipping from 64 to 32 or 16 QAM is most likely ingress getting into the cabling, or one or more modems in your area are badly aligned causing upstream issues.