QAM 16, packet loss

[Biscuit_Monster]

I’ve noticed a couple of upstream channels flapping between 16 32 and 64 QAM along with an uptick in packet loss on my BQM graph.

I think my power levels are in spec, and nothing has changed inside the property, all connections look good.  Could this be an area issue (31) or noise in the cabinet (from a neighbour?).

There was a major outage a couple of months ago caused by a nearby lightning strike and upstream power was over 50 dBmV for a while after it was fixed, seems to be back to around 42 which is typical for my line. 

Tried powering everything off for 5 minutes but levels are the same. 

BQM (red lines after midnight are the shutdown period).

will post stats below. 

[Biscuit_Monster]

Downstream bonded channels

Channel	Frequency (Hz)	Power (dBmV)	SNR (dB)	Modulation	Channel ID
1	482250000	0.2	38	256 qam	16
2	474250000	0.2	38	256 qam	15
3	490250000	0.2	38	256 qam	17
4	498250000	0	38	256 qam	18
5	506250000	-0.2	38	256 qam	19
6	514250000	-0.5	38	256 qam	20
7	522250000	-0.5	38	256 qam	21
8	530250000	-0.7	38	256 qam	22
9	538250000	-0.5	38	256 qam	23
10	546250000	-0.4	38	256 qam	24
11	554250000	-0.7	38	256 qam	25
12	562250000	-0.7	38	256 qam	26
13	570250000	-0.9	38	256 qam	27
14	578250000	-0.9	38	256 qam	28
15	586250000	-0.5	38	256 qam	29
16	594250000	-0.4	38	256 qam	30
17	602250000	-0.2	38	256 qam	31
18	610250000	-0.4	38	256 qam	32
19	618250000	-0.9	38	256 qam	33
20	626250000	-0.9	38	256 qam	34
21	634250000	-0.5	38	256 qam	35
22	658250000	-0.7	38	256 qam	36
23	666250000	-0.7	38	256 qam	37
24	674250000	-1	38	256 qam	38

[Biscuit_Monster]

Downstream bonded channels

Channel	Locked Status	RxMER (dB)	Pre RS Errors	Post RS Errors
1	Locked	38.6	7	0
2	Locked	38.9	5	0
3	Locked	38.6	5	0
4	Locked	38.6	6	0
5	Locked	38.9	7	0
6	Locked	38.9	8	0
7	Locked	38.6	6	0
8	Locked	38.6	8	0
9	Locked	38.6	7	0
10	Locked	38.6	17	0
11	Locked	38.6	7	0
12	Locked	38.9	6	0
13	Locked	38.6	9	0
14	Locked	38.9	8	0
15	Locked	38.9	10	0
16	Locked	38.9	5	0
17	Locked	38.6	10	0
18	Locked	38.6	8	0
19	Locked	38.9	11	0
20	Locked	38.9	5	0
21	Locked	38.9	10	0
22	Locked	38.9	17	0
23	Locked	38.9	14	0
24	Locked	38.6	21	0

[Biscuit_Monster]

Upstream bonded channels

Channel	Frequency (Hz)	Power (dBmV)	Symbol Rate (ksps)	Modulation	Channel ID
1	43100000	43	5120	64 qam	6
2	36600000	42.5	5120	64 qam	7
3	30100000	43.5	5120	16 qam	8
4	23600274	42.5	5120	16 qam	11
5	49600258	43.5	5120	64 qam	5

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
5	ATDMA	0	0	0	0

[Adduxi]

All your US channels should be 64QAM, so I suspect noise igress somewhere.  Check all the connections are tight.  Also post your Network Log please for comment.

[Biscuit_Monster]

Agree. Connections all tight, cables haven’t been touched and don’t run near anything that could pick up noise (power etc). Pretty sure it’s an issue in the cabinet. 

Network Log

Time Priority Description

01/01/1970 00:01:46	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/11/2023 11:18:18	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/11/2023 09:21:11	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/11/2023 00:04:44	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/11/2023 00:04:13	Warning!	LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/11/2023 00:03:55	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/11/2023 21:07:47	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/11/2023 12:32:1	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/11/2023 09:07:47	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2023 15:48:50	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/11/2023 21:07:47	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/11/2023 12:19:24	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/11/2023 09:07:47	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/11/2023 18:23:18	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/11/2023 10:49:19	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/11/2023 03:09:59	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/11/2023 03:01:18	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;
09/11/2023 02:58:47	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/11/2023 02:58:41	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/11/2023 02:58:41	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

[Adduxi]

Nothing jumping out in the logs AFAICS.  Looks like you need a VM engineer to check the circuit out.  If you have one of the older metal box isolators/splitters, it could also be failing/corroding?

[Biscuit_Monster]

Thanks for looking, could be some corrosion on whatever is in the box on the outside wall I suppose, I’ve never actually looked inside!

Inside the house is a white HDU-200 amplifier/splitter, only about 3 years old. PSU died on the last one after 10 years or so. 

[Joseph_B]

Hey @Biscuit_Monster,

Thanks for reaching out to us, looking into the diagnostics I can run via our system, I do not see any issues presently affecting you, has the issue since improved over the weekend?

Joe

[legacy1]

---

@Joseph_B wrote:

Hey @Biscuit_Monster,

Thanks for reaching out to us, looking into the diagnostics I can run via our system, I do not see any issues presently affecting you, has the issue since improved over the weekend?

---

Your diagnostics do not include hub auto downgrading Modulation