Upstream Channel at 16 QAM - Packet loss

[lotharmat]

Hiya,

I have noticed a fair bit of packet loss on my BQM (See sig for live) Link Here

One of my upstream channels is sat at 16 QAM 

Also my downstream power levels seem to have crept up to borderline high - they have been bobbing around up to 9.5dBmV

I have rebooted the Hub (in Modem mode) and the packet-loss is still persisting and the QAM is still 16.

Is this something that I need a Tech to rectify - I imagine I'd need a 6dB FPA to cure the downstream issues:

Stats and logs to follow.

[lotharmat]

D/S:

Downstream bonded channels

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

1	331000000	8.5	40	256 qam	25
2	203000000	8.6	40	256 qam	9
3	211000000	8	40	256 qam	10
4	219000000	7.3	40	256 qam	11
5	227000000	7.5	40	256 qam	12
6	235000000	7.3	40	256 qam	13
7	243000000	6.4	40	256 qam	14
8	251000000	7.1	40	256 qam	15
9	259000000	8.1	40	256 qam	16
10	267000000	7.5	40	256 qam	17
11	275000000	7.5	40	256 qam	18
12	283000000	8.1	40	256 qam	19
13	291000000	8.3	40	256 qam	20
14	299000000	8.4	40	256 qam	21
15	307000000	8.5	40	256 qam	22
16	315000000	8.5	40	256 qam	23
17	323000000	8.5	40	256 qam	24
18	371000000	6.6	40	256 qam	26
19	379000000	7.4	40	256 qam	27
20	387000000	8.3	40	256 qam	28
21	395000000	7.4	40	256 qam	29
22	403000000	6.5	40	256 qam	30
23	411000000	7.6	40	256 qam	31
24	419000000	7.5	40	256 qam	32

Downstream bonded channels

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

1	Locked	40.3	0	0
2	Locked	40.3	7	0
3	Locked	40.3	5	0
4	Locked	40.3	0	0
5	Locked	40.3	5	0
6	Locked	40.3	5	0
7	Locked	40.3	0	0
8	Locked	40.3	0	0
9	Locked	40.9	1	0
10	Locked	40.9	0	0
11	Locked	40.3	0	0
12	Locked	40.9	5	0
13	Locked	40.9	6	0
14	Locked	40.3	6	0
15	Locked	40.3	5	0
16	Locked	40.3	6	0
17	Locked	40.9	5	0
18	Locked	40.3	5	0
19	Locked	40.3	6	0
20	Locked	40.9	0	0
21	Locked	40.3	6	0
22	Locked	40.3	0	0
23	Locked	40.9	0	0
24	Locked	40.9	1	0

[lotharmat]

U/S

Upstream bonded channels

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

1	46200000	40.5	5120	64 qam	1
2	39400000	40.3	5120	64 qam	2
3	25800302	40	5120	16 qam	4
4	32600000	40.3	5120	64 qam	3

Upstream bonded channels

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

[lotharmat]

Log:

Network Log

Time Priority Description

13/07/2021 15:27:7	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2021 21:13:9	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/07/2021 18:01:5	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/07/2021 09:13:8	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/07/2021 04:10:43	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/07/2021 09:13:7	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/06/2021 01:29:11	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/06/2021 21:13:7	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/06/2021 12:35:43	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/06/2021 09:13:7	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/06/2021 18:30:17	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/06/2021 21:47:43	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/06/2021 15:02:49	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/06/2021 07:58:5	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:39	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/06/2021 07:26:26	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/06/2021 18:42:31	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/06/2021 18:27:59	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/06/2021 17:48:37	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/06/2021 06:37:59	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

[lotharmat]

I'm starting to think there is some planned work occurring as here is yesterday's BQM

And today's:

Both the packet-loss begin at 1400 hrs.

[John_GS · Accepted solution]

Hi lotharmat,

Thanks for posting and apologies about the packet loss. 

I've ran a system diagnostic today and it's come up with this;

We've identified a connectivity issue that would cause performance related issues with the customer's connection. This issue is impacting at least 25% of the customers in the area.

We've automatically raised the issue to our network teams who will investigate and fix the fault in the area.

Best,

[lotharmat]

Legend! 

At least I know there's a reason for it! - There was nothing on the Service status pages or the 0800 561 0061 number!

I appreciate the update!

[John_GS]

Haha thanks for coming back to me 🙂

I've raised it as a work order on the account so the network team know you're impacted by it, so hopefully resolved soon. 

Give me a shout if you need further help

Best,

[lotharmat]

Brilliant! - Cheers John!

[lotharmat]

Just wanted to add to this:

Got a text this morning saying that the fault had been fixed which is evidenced by the BQM looking healthy and the QAM being 64 across the board for upstream!

Many thanks John for your help with this!