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 John,

I appreciate the reply!

I look forward to the update 🙂

Thanks for the help so far,

Jo

[Natalie_L]

You're welcome. 

I just want to let you know we are still looking in to this and will update you as soon as possible. 

Thanks 

[Icantcrabhere]

Thanks Natalie 🙂

fingers crossed for a quick reply from them!

[Nathan_B]

Apologies for the delay in messaging you @Icantcrabhere, we have had no further update from the team so this has been chased for you again today.

Regards

Nathan

[Icantcrabhere]

Thank you, Nathan!

Very much appreciated 🙂

[Icantcrabhere]

Hi there, any update?
It has been over a week now since the original chase up,
I never seem to have much luck with our AFM. - it's like this every time, kind of unfortunate

[Ilyas_Y]

Hey there, thanks for reaching out to us.

I've had a look on our end and I cannot see any outages currently as of the moment in the area.
I've checked the service levels and everything is showing up as fine.
May I ask how the service has been recently?

Let us know 🙂

Kind regards.

[Icantcrabhere]

Well, it was "Ok"
as of this moment however we just had this happen:
(network logs are 1 hour behind, so it's from just moments ago, actually)

Network Log

Time Priority Description

01/08/2022 13:30:43	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/08/2022 13:30:42	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/08/2022 13:30:42	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/08/2022 13:30:41	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/08/2022 13:30:28	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/08/2022 13:30:24	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/08/2022 13:30:23	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/08/2022 13:30:23	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/08/2022 13:30:23	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	38.9	33667	3848
2	Locked	38.9	29543	5740
3	Locked	40.3	29036	6728
4	Locked	40.3	31775	4644
5	Locked	38.9	33371	4709
6	Locked	38.9	35875	4899
7	Locked	38.9	32342	4474
8	Locked	38.9	30863	6367
9	Locked	38.9	31299	6253
10	Locked	38.9	33506	7108
11	Locked	38.9	35384	6907
12	Locked	38.6	35227	5806
13	Locked	38.6	35653	6362
14	Locked	38.9	35443	6307
15	Locked	38.6	36639	7499
16	Locked	38.9	35750	6114
17	Locked	38.6	36768	6199
18	Locked	37.6	36939	7146
19	Locked	38.6	36674	7900
20	Locked	38.6	36105	9567
21	Locked	38.6	37052	7066
22	Locked	38.6	36580	6674
23	Locked	38.6	35688	5946
24	Locked	38.6	34873	6007

While this happened, x3 channels dropped from 64QAM > 32 again.
however the channels seem to have (For the moment) returned to 64QAM.
Also the "Pre-RS" count was super low before today, and the "Post-RS" were all at 0.
So there's definitely some sort of SNR/Noise related issue going on here.

There's definitely an issue here and it still isn't being chased up correctly with the AFM.
even after tech visits when everything in my premises is fine.

Please can we get this escalated, I'm losing faith here.

Thanks for the help so far,

Jo.

[Matthew_ML]

Hey Icantcrabhere, thank you for reaching back out with this information.

Okay I would like to take a look in more details and run some tests with you.

Please can you look out for the purple envelope, as I am going to send you a PM. Thanks 

[Matthew_ML]

Hey Icantcrabhere, thank you for reaching back out I am sorry in the delay in getting back to you, it were my days off.

However I have sent this over to the area field manager and I will reach out once again if I hear anything. Thanks