Hub5 remotely rebooted by VM now has upstream noise issue.

[chrcoluk]

Can a staff member please check if a noise problem exists in my area.

I will post information here.

Downstream bonded channels

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

1	331000000	6.5	42	QAM 256	25
2	139000000	5.7	41	QAM 256	1
3	147000000	5.7	41	QAM 256	2
4	155000000	5.6	41	QAM 256	3
5	163000000	5.6	41	QAM 256	4
6	171000000	5.4	41	QAM 256	5
7	179000000	5.4	41	QAM 256	6
8	187000000	5.7	41	QAM 256	7
9	195000000	6.3	41	QAM 256	8
10	203000000	6.6	42	QAM 256	9
11	211000000	6.6	42	QAM 256	10
12	219000000	6	42	QAM 256	11
13	227000000	5.6	42	QAM 256	12
14	235000000	5.6	42	QAM 256	13
15	243000000	6	42	QAM 256	14
16	251000000	6.2	42	QAM 256	15
17	259000000	6.4	42	QAM 256	16
18	267000000	6.4	42	QAM 256	17
19	275000000	6.4	42	QAM 256	18
20	283000000	6.2	42	QAM 256	19
21	291000000	5.9	42	QAM 256	20
22	299000000	5.8	42	QAM 256	21
23	307000000	6.2	42	QAM 256	22
24	315000000	6.8	42	QAM 256	23
25	323000000	7	42	QAM 256	24
26	339000000	6.1	42	QAM 256	26
27	347000000	5.5	42	QAM 256	27
28	355000000	5.4	42	QAM 256	28
29	363000000	5.7	42	QAM 256	29
30	371000000	6	42	QAM 256	30
31	379000000	6.3	42	QAM 256	31

Downstream bonded channels

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

1	Locked	42	0	0
2	Locked	41	0	0
3	Locked	41	0	0
4	Locked	41	0	0
5	Locked	41	0	0
6	Locked	41	0	0
7	Locked	41	0	0
8	Locked	41	0	0
9	Locked	41	0	0
10	Locked	42	0	0
11	Locked	42	0	0
12	Locked	42	0	0
13	Locked	42	0	0
14	Locked	42	0	0
15	Locked	42	0	0
16	Locked	42	0	0
17	Locked	42	0	0
18	Locked	42	0	0
19	Locked	42	0	0
20	Locked	42	0	0
21	Locked	42	0	0
22	Locked	42	0	0
23	Locked	42	0	0
24	Locked	42	0	0
25	Locked	42	0	0
26	Locked	42	0	0
27	Locked	42	0	0
28	Locked	42	0	0
29	Locked	42	0	0
30	Locked	42	0	0
31	Locked	42	0	0

[chrcoluk]

Upstream bonded channels

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

0	49600000	42.8	5120	QAM 32	1
1	43100000	42.8	5120	QAM 32	2
2	36600000	42	5120	QAM 32	3
3	30100000	41.5	5120	QAM 32	4
4	23600000	41.3	5120	QAM 32	9

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

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

[chrcoluk]

Network Log

Time Priority Description

17-04-2023 23:01:35	notice	REGISTRATION COMPLETE - Waiting for Operational status
17-04-2023 23:01:31	notice	US profile assignment change. US Chan ID: 10; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-04-2023 23:01:26	notice	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-04-2023 23:01:22	notice	TLV-11 - unrecognized OID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-04-2023 23:01:20	warning	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-04-2023 23:01:18	notice	Honoring MDD; IP provisioning mode = IPv4
17-04-2023 23:00:59	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-04-2023 23:00:41	critical	Cable Modem Reboot via RG reboot command

[chrcoluk]

Prior to this upstream's were always QAM64, then 11pm had the "Cable Modem Reboot via RG reboot command"

Now they are rotating between QAM16 and QAM32. (QAM32 at time of this post).

[Alex_RM]

Hi chrcoluk,

Thanks for posting, I've had a look at things from our side and everything looks to be within the specifications we would expect.

Are you experiencing any connect issues currently?

Let us know if you are.

Alex_Rm

[chrcoluk]

---

@Alex_RM wrote:

Hi chrcoluk,

Thanks for posting, I've had a look at things from our side and everything looks to be within the specifications we would expect.

Are you experiencing any connect issues currently?

Let us know if you are.

Alex_Rm

---

Hi, luckily the connection still performs fine.  I didnt know QAM32 is within spec.

Because its still performing ok I wont push it now.

[chrcoluk]

---

@Alex_RM wrote:

Hi chrcoluk,

Thanks for posting, I've had a look at things from our side and everything looks to be within the specifications we would expect.

Are you experiencing any connect issues currently?

Let us know if you are.

Alex_Rm

---

Had an outage earlier whilst watching a stream, had to go out, but checked logs when I came back, and seen the following lines, they do coincide with the outage, which is also visible on my tbb ping graph, which I will add as well.  These indicate an issue with the 3.1 channel though.  The 3.0 channels are now back on QAM64..

22-04-2023 14:37:35	critical	16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
22-04-2023 14:37:35	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
22-04-2023 14:33:34	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

[chrcoluk]

.

Upstream bonded channels

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

0	49600000	43	5120	QAM 64	1
1	43100000	42.8	5120	QAM 64	2
2	36600000	42.3	5120	QAM 64	3
3	30100000	41.8	5120	QAM 64	4
4	23600000	41.5	5120	QAM 64	9

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

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

[chrcoluk]

graph

[Travis_M]

Hi @chrcoluk

Thanks for your response

The BQM doesn't actually show any alarming signs asides from the one short dropout - noise doesn't seem to be a problem as per the BQM graph. How has your connection been since Saturday?

Regards