We recently had an engineer visit where the engineer concluded everything was fine, but the Hub 4 we had was replaced with a Hub 5. The reason for the visit was due to constant disconnections and loss of service.Since the Hub 5 was installed it has been much better until the last couple of days where we're losing our connection a lot again. The only way to sort it is turn the hub off, leave for a bit then restart. It then works for a while. I've discovered there is a log in the Hub 5 which provides the table below, the critical items coincide with when the internet is lost, I'm assuming this is the reason and is therefore related.I've found lots of questions about this, but no real answers, how does this get fixed? The current recorded message says there are no issues in our area, but when I check the service on line, it says there is an issue which is being worked on, check again tomorrow.imePriorityDescription14/12/2023 17:09warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;14/12/2023 17:09criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;14/12/2023 16:58noticeREGISTRATION COMPLETE - Waiting for Operational status14/12/2023 16:57warningRNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;14/12/2023 16:57warningREG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;14/12/2023 16:57warningDynamic Range Window violation14/12/2023 16:57noticeDS 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;14/12/2023 16:57noticeTLV-11 - unrecognized OID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;14/12/2023 16:57warningDHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;14/12/2023 16:57noticeHonoring MDD; IP provisioning mode = IPv414/12/2023 16:57criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;14/12/2023 16:57criticalCable Modem Reboot because of - HW or Power-On Reset14/12/2023 14:38criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;14/12/2023 14:38criticalCable Modem Reboot because of - HW or Power-On Reset14/12/2023 14:02criticalReceived 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.1;14/12/2023 09:51criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;14/12/2023 09:40criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;14/12/2023 09:39criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;14/12/2023 09:39criticalCable Modem Reboot because of - HW or Power-On Reset13/12/2023 23:16criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;13/12/2023 23:16criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;13/12/2023 23:16criticalCable Modem Reboot because of - HW or Power-On Reset13/12/2023 07:22criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;13/12/2023 07:22criticalCable Modem Reboot because of - HW or Power-On Reset12/12/2023 07:29criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;12/12/2023 07:28criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;12/12/2023 07:28criticalCable Modem Reboot because of - HW or Power-On Reset12/12/2023 07:26criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;12/12/2023 06:09criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;12/12/2023 05:58criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;12/12/2023 05:57criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;12/12/2023 05:57criticalCable Modem Reboot because of - HW or Power-On Reset

Share the stats from the Upstream and Downstream tabs, that will show the quality of the signal to the Hub.

3.0 Downstream channelsChannel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID 11700000001.539QAM 256521380000002.440QAM 256131460000002.540QAM 256241540000002.139QAM 256351620000001.739QAM 256461780000001.639QAM 256671860000001.640QAM 25678194000000240QAM 256892020000002.140QAM 2569102100000002.440QAM 25610112180000002.539QAM 25611122260000002.339QAM 25612132340000002.439QAM 25613142420000002.239QAM 25614152500000001.739QAM 25615162580000001.339QAM 25616172660000000.839QAM 25617182740000000.639QAM 25618192820000000.639QAM 25619202900000000.839QAM 25620212980000000.839QAM 25621223060000000.939QAM 25622233140000001.139QAM 25623243220000001.239QAM 25624253300000001.239QAM 25625263380000001.639QAM 25626273460000001.739QAM 25627283540000001.839QAM 25628293620000001.939QAM 25629303700000001.939QAM 25630313780000001.939QAM 25631

hannel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID06030000040.85120QAM 64115370000040.85120QAM 64224620000040.35120QAM 64333940000040.35120QAM 64443260000040.35120QAM 64552360000040.35120QAM 646

Is there anyone who can help with this? I check the service update and at the moment it says:Looks like there’s still an issue with your connectionbut there are no known issues in my post code. It said this the other day, then when the 24 hours were up it said it was fixed, but it's not, I can't seem to get a technician to come out until it says this issue isn't fixed after 24 hours!

Forum Discussion

iain123456

Joining in

2 years ago

Constant disconnections

We recently had an engineer visit where the engineer concluded everything was fine, but the Hub 4 we had was replaced with a Hub 5. The reason for the visit was due to constant disconnections and loss of service.

Since the Hub 5 was installed it has been much better until the last couple of days where we're losing our connection a lot again. The only way to sort it is turn the hub off, leave for a bit then restart. It then works for a while. I've discovered there is a log in the Hub 5 which provides the table below, the critical items coincide with when the internet is lost, I'm assuming this is the reason and is therefore related.

I've found lots of questions about this, but no real answers, how does this get fixed? The current recorded message says there are no issues in our area, but when I check the service on line, it says there is an issue which is being worked on, check again tomorrow.

ime	Priority	Description
14/12/2023 17:09	warning	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
14/12/2023 17:09	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
14/12/2023 16:58	notice	REGISTRATION COMPLETE - Waiting for Operational status
14/12/2023 16:57	warning	RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
14/12/2023 16:57	warning	REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
14/12/2023 16:57	warning	Dynamic Range Window violation
14/12/2023 16:57	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;
14/12/2023 16:57	notice	TLV-11 - unrecognized OID;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
14/12/2023 16:57	warning	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
14/12/2023 16:57	notice	Honoring MDD; IP provisioning mode = IPv4
14/12/2023 16:57	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
14/12/2023 16:57	critical	Cable Modem Reboot because of - HW or Power-On Reset
14/12/2023 14:38	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
14/12/2023 14:38	critical	Cable Modem Reboot because of - HW or Power-On Reset
14/12/2023 14:02	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.1;
14/12/2023 09:51	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
14/12/2023 09:40	critical	No Ranging Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
14/12/2023 09:39	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
14/12/2023 09:39	critical	Cable Modem Reboot because of - HW or Power-On Reset
13/12/2023 23:16	critical	No Ranging Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
13/12/2023 23:16	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
13/12/2023 23:16	critical	Cable Modem Reboot because of - HW or Power-On Reset
13/12/2023 07:22	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
13/12/2023 07:22	critical	Cable Modem Reboot because of - HW or Power-On Reset
12/12/2023 07:29	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
12/12/2023 07:28	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
12/12/2023 07:28	critical	Cable Modem Reboot because of - HW or Power-On Reset
12/12/2023 07:26	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
12/12/2023 06:09	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
12/12/2023 05:58	critical	No Ranging Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
12/12/2023 05:57	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
12/12/2023 05:57	critical	Cable Modem Reboot because of - HW or Power-On Reset

21 Replies

iain123456
Joining in
2 years ago
Can anyone help?
Client62
Alessandro Volta
2 years ago
Share the stats from the Upstream and Downstream tabs, that will show the quality of the signal to the Hub.

iain123456

Joining in

2 years ago

3.0 Downstream channels

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

1	170000000	1.5	39	QAM 256	5
2	138000000	2.4	40	QAM 256	1
3	146000000	2.5	40	QAM 256	2
4	154000000	2.1	39	QAM 256	3
5	162000000	1.7	39	QAM 256	4
6	178000000	1.6	39	QAM 256	6
7	186000000	1.6	40	QAM 256	7
8	194000000	2	40	QAM 256	8
9	202000000	2.1	40	QAM 256	9
10	210000000	2.4	40	QAM 256	10
11	218000000	2.5	39	QAM 256	11
12	226000000	2.3	39	QAM 256	12
13	234000000	2.4	39	QAM 256	13
14	242000000	2.2	39	QAM 256	14
15	250000000	1.7	39	QAM 256	15
16	258000000	1.3	39	QAM 256	16
17	266000000	0.8	39	QAM 256	17
18	274000000	0.6	39	QAM 256	18
19	282000000	0.6	39	QAM 256	19
20	290000000	0.8	39	QAM 256	20
21	298000000	0.8	39	QAM 256	21
22	306000000	0.9	39	QAM 256	22
23	314000000	1.1	39	QAM 256	23
24	322000000	1.2	39	QAM 256	24
25	330000000	1.2	39	QAM 256	25
26	338000000	1.6	39	QAM 256	26
27	346000000	1.7	39	QAM 256	27
28	354000000	1.8	39	QAM 256	28
29	362000000	1.9	39	QAM 256	29
30	370000000	1.9	39	QAM 256	30
31	378000000	1.9	39	QAM 256	31

iain123456
Joining in
2 years ago
hannel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
0 60300000 40.8 5120 QAM 64 1
1 53700000 40.8 5120 QAM 64 2
2 46200000 40.3 5120 QAM 64 3
3 39400000 40.3 5120 QAM 64 4
4 32600000 40.3 5120 QAM 64 5
5 23600000 40.3 5120 QAM 64 6
iain123456
Joining in
2 years ago
Is there anyone who can help with this? I check the service update and at the moment it says:
Looks like there’s still an issue with your connection
but there are no known issues in my post code. It said this the other day, then when the 24 hours were up it said it was fixed, but it's not, I can't seem to get a technician to come out until it says this issue isn't fixed after 24 hours!
- Sabrina_B
  Forum Team
  2 years ago
  Hi iain123456 👋.
  
  Thanks for reaching out to us. Apologies that you are having issues with the service in your area. If the service checker 👉 Service Status is saying that the outage is now clear, please run the same test again with the Hub in router mode, and all third party Hubs removed and operating off the VM network name and post the results for us to see.
  
  Sabrina
iain123456
Joining in
2 years ago
error
Roger_Gooner
Alessandro Volta
2 years ago
Before you repost your stats ensure that all connections between hub and wall socket are tight and you reboot your hub.

iain123456

Joining in

2 years ago

forgive my ignorance, but is this graph bad?

Beth_G

Forum Team

2 years ago

Hi iain123456

Thanks for posting a screenshot of your graph.

When the graph appears all red like this, it'll either mean that your Hub has been offline for the entire 24 hour log, or your Hub is blocking CMTS ping request which is what's required in order to allow the site to speak with your Hub and present the data on the graph.

We've checked the SamKnows data on our side for the past week and we aren't able to see any issues at all with your connection.

How've things been since Friday?

iain123456

Joining in

2 years ago

Hi,

We had and engineer come on Friday who replaced the blue box externally on the house and the connection into the house (the install was an old way of doing it, so now it is the new way?). The engineer had detected some issues when he connected his bit of kit, which were then almost gone when he tested it after the replacement box.

It was all good and we managed 3 days without it going off, then yesterday lunch time it went off and this morning it has just gone off again.

Time Priority Description

02-01-2024 09:49:48	warning	TCS Partial Service;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
02-01-2024 09:49:48	critical	No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
02-01-2024 09:49:48	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
02-01-2024 09:49:48	notice	REGISTRATION COMPLETE - Waiting for Operational status
02-01-2024 09:49:38	warning	REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
02-01-2024 09:49:38	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
02-01-2024 09:49:33	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;
02-01-2024 09:49:30	notice	TLV-11 - unrecognized OID;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
02-01-2024 09:49:27	warning	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
02-01-2024 09:49:25	notice	Honoring MDD; IP provisioning mode = IPv4
02-01-2024 09:49:15	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
02-01-2024 09:49:14	critical	Cable Modem Reboot because of - HW or Power-On Reset

.0 Downstream channels

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

1	370000000	8	37	QAM 256	30
2	138000000	9.2	38	QAM 256	1
3	146000000	8.9	38	QAM 256	2
4	154000000	8.8	38	QAM 256	3
5	162000000	8.5	38	QAM 256	4
6	170000000	8.7	38	QAM 256	5
7	178000000	8.7	38	QAM 256	6
8	186000000	9	38	QAM 256	7
9	194000000	9.2	39	QAM 256	8
10	202000000	9.1	38	QAM 256	9
11	210000000	9	38	QAM 256	10
12	218000000	8.8	38	QAM 256	11
13	226000000	8.7	38	QAM 256	12
14	234000000	8.7	38	QAM 256	13
15	242000000	8.8	38	QAM 256	14
16	250000000	8.6	38	QAM 256	15
17	258000000	8.6	38	QAM 256	16
18	266000000	8.4	38	QAM 256	17
19	274000000	8.4	38	QAM 256	18
20	282000000	8.4	38	QAM 256	19
21	290000000	8.6	38	QAM 256	20
22	298000000	8.4	38	QAM 256	21
23	306000000	8.4	38	QAM 256	22
24	314000000	8.2	38	QAM 256	23
25	322000000	8.1	38	QAM 256	24
26	330000000	8	37	QAM 256	25
27	338000000	8	37	QAM 256	26
28	346000000	7.9	37	QAM 256	27
29	354000000	7.9	37	QAM 256	28
30	362000000	8	37	QAM 256	29
31	378000000	8.2	37	QAM 256	31

3.0 Downstream channels

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

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

3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)

159

1840

QAM 4096

1108

3.1 Downstream channels

Channel ID Locked Status RxMER Data (dB) PLC Power (dBmV) Corrected errors (Active Profile) Uncorrectable errors (Active Profile)

159

Locked

8.8

4959952

3.0 Upstream channels

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

0	60300000	28.3	5120	QAM 64	1
1	53700000	28.3	5120	QAM 64	2
2	46200000	28.3	5120	QAM 64	3
3	39400000	28	5120	QAM 64	4
4	32600000	28.3	5120	QAM 64	5
5	23600000	27.8	5120	QAM 64	6

3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

0	ATDMA	1
1	ATDMA	1
2	ATDMA	1
3	ATDMA	1
4	ATDMA	1
5	ATDMA	1

General Configuration

Network accessMaximum Number of CPEsBaseline PrivacyDOCSIS ModeConfig file

Allowed

Enabled

3.1

A,.iyewrkldJKDHSUBsgvca69834n

Primary Downstream Service Flow

SFIDMax Traffic RateMax Traffic BurstMin Traffic RateSFIDMax Traffic RateMax Traffic BurstMin Traffic Rate

8582

575000085 bps

42600bytes

0 bps

22062

128000 bps

4000bytes

0 bps

Primary Upstream Service Flow

SFIDMax Traffic RateMax Traffic BurstMin Traffic RateMax Concatenated BurstScheduling TypeSFIDMax Traffic RateMax Traffic BurstMin Traffic RateMax Concatenated BurstScheduling Type

8581

55000085 bps

42600bytes

0 bps

42600bytes

Best Effort

22061

128000 bps

4000bytes

0 bps

1522bytes

Best Effort

iain123456
Joining in
2 years ago
And it's gone again, needless to say this is becoming increasingly frustrating and making working from home virtually impossible.
- iain123456
  Joining in
  2 years ago
  Hi,
  We had and engineer come on Friday who replaced the blue box externally on the house and the connection into the house (the install was an old way of doing it, so now it is the new way?). The engineer had detected some issues when he connected his bit of kit, which were then almost gone when he tested it after the replacement box.
  It was all good and we managed 3 days without it going off, then yesterday lunch time it went off and this morning it has just gone off again.

iain123456

Joining in

2 years ago

Time Priority Description

02-01-2024 09:49:48	warning	TCS Partial Service;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
02-01-2024 09:49:48	critical	No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
02-01-2024 09:49:48	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
02-01-2024 09:49:48	notice	REGISTRATION COMPLETE - Waiting for Operational status
02-01-2024 09:49:38	warning	REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
02-01-2024 09:49:38	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
02-01-2024 09:49:33	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;
02-01-2024 09:49:30	notice	TLV-11 - unrecognized OID;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
02-01-2024 09:49:27	warning	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
02-01-2024 09:49:25	notice	Honoring MDD; IP provisioning mode = IPv4
02-01-2024 09:49:15	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
02-01-2024 09:49:14	critical	Cable Modem Reboot because of - HW or Power-On Reset

.0 Downstream channels

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

1	370000000	8	37	QAM 256	30
2	138000000	9.2	38	QAM 256	1
3	146000000	8.9	38	QAM 256	2
4	154000000	8.8	38	QAM 256	3
5	162000000	8.5	38	QAM 256	4
6	170000000	8.7	38	QAM 256	5
7	178000000	8.7	38	QAM 256	6
8	186000000	9	38	QAM 256	7
9	194000000	9.2	39	QAM 256	8
10	202000000	9.1	38	QAM 256	9
11	210000000	9	38	QAM 256	10
12	218000000	8.8	38	QAM 256	11
13	226000000	8.7	38	QAM 256	12
14	234000000	8.7	38	QAM 256	13
15	242000000	8.8	38	QAM 256	14
16	250000000	8.6	38	QAM 256	15
17	258000000	8.6	38	QAM 256	16
18	266000000	8.4	38	QAM 256	17
19	274000000	8.4	38	QAM 256	18
20	282000000	8.4	38	QAM 256	19
21	290000000	8.6	38	QAM 256	20
22	298000000	8.4	38	QAM 256	21
23	306000000	8.4	38	QAM 256	22
24	314000000	8.2	38	QAM 256	23
25	322000000	8.1	38	QAM 256	24
26	330000000	8	37	QAM 256	25
27	338000000	8	37	QAM 256	26
28	346000000	7.9	37	QAM 256	27
29	354000000	7.9	37	QAM 256	28
30	362000000	8	37	QAM 256	29
31	378000000	8.2	37	QAM 256	31

3.0 Downstream channels

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

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

3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)

159

1840

QAM 4096

1108

3.1 Downstream channels

Channel ID Locked Status RxMER Data (dB) PLC Power (dBmV) Corrected errors (Active Profile) Uncorrectable errors (Active Profile)

159

Locked

8.8

4959952

3.0 Upstream channels

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

0	60300000	28.3	5120	QAM 64	1
1	53700000	28.3	5120	QAM 64	2
2	46200000	28.3	5120	QAM 64	3
3	39400000	28	5120	QAM 64	4
4	32600000	28.3	5120	QAM 64	5
5	23600000	27.8	5120	QAM 64	6

3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

0	ATDMA	1
1	ATDMA	1
2	ATDMA	1
3	ATDMA	1
4	ATDMA	1
5	ATDMA	1

General Configuration

Network accessMaximum Number of CPEsBaseline PrivacyDOCSIS ModeConfig file

Allowed

Enabled

3.1

A,.iyewrkldJKDHSUBsgvca69834n

Primary Downstream Service Flow

SFIDMax Traffic RateMax Traffic BurstMin Traffic RateSFIDMax Traffic RateMax Traffic BurstMin Traffic Rate

8582

575000085 bps

42600bytes

0 bps

22062

128000 bps

4000bytes

0 bps

Primary Upstream Service Flow

SFIDMax Traffic RateMax Traffic BurstMin Traffic RateMax Concatenated BurstScheduling TypeSFIDMax Traffic RateMax Traffic BurstMin Traffic RateMax Concatenated BurstScheduling Type

8581

55000085 bps

42600bytes

0 bps

42600bytes

Best Effort

22061

128000 bps

4000bytes

0 bps

1522bytes

Best Effort

John_GS
Forum Team
2 years ago
Hi iain123456

Thanks for coming back to the thread.

You do need a tech as the upstream channels are low plus the downstream ones are getting towards the high side.

I'll send you a PM now to book this in.

Forum Discussion

Constant disconnections

21 Replies

Looks like there’s still an issue with your connection

Related Content

Constant calls from 0800 052 8675

Constant swirling purple circle

Further bill after disconnection date

Been disconnected

Disconnection date?

0	60300000	40.8	5120	QAM 64	1
1	53700000	40.8	5120	QAM 64	2
2	46200000	40.3	5120	QAM 64	3
3	39400000	40.3	5120	QAM 64	4
4	32600000	40.3	5120	QAM 64	5
5	23600000	40.3	5120	QAM 64	6