Unicast Maintenance Ranging attempted - No response

[stelyth]

Hello, I have been experiencing intermitent internet for a couple of weeks now both on the WIFI and hard wired side of things. Here is a copy of my current network log. As you can see there are many unicast errors but also dynamic range window violations and commanded power exceeds values. Most of the time the light on the router stays solid white even when experiencing issues but sometimes changes to red. Do I need an engineer?

Network Log

Time Priority Description

16-05-2023 21:50:15	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2023 21:50:15	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2023 21:50:15	critical	16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2023 21:50:15	critical	16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2023 21:50:15	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2023 21:50:15	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2023 21:50:15	critical	16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2023 21:50:15	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2023 21:50:01	notice	US profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2023 21:50:01	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2023 21:50:01	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;
16-05-2023 21:50:01	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2023 21:50:01	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2023 21:50:01	critical	16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2023 21:49:44	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2023 21:49:43	critical	16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2023 21:49:43	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2023 21:49:17	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2023 21:48:55	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;
16-05-2023 21:48:55	notice	US profile assignment change. US Chan ID: 14; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-05-2023 21:48:52	notice	REGISTRATION COMPLETE - Waiting for Operational status
16-05-2023 21:48:46	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;
16-05-2023 21:48:46	warning	Dynamic Range Window violation
16-05-2023 21:48:46	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;
16-05-2023 21:48:46	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;
16-05-2023 21:48:46	warning	Dynamic Range Window violation
16-05-2023 21:48:46	warning	Dynamic Range Window violation
16-05-2023 21:48:46	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;
16-05-2023 21:48:46	warning	Dynamic Range Window violation
16-05-2023 21:48:46	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;
16-05-2023 21:48:46	warning	Dynamic Range Window violation
16-05-2023 21:48:46	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;

[Tudor]

Please post a full set of stats. 

[stelyth]

What stats do I need to post?

[jbrennand]

See this....

____________

In your browser’s URL box type in http://192.168.0.1 (or http://192.168.100.1 - if in modem mode) (DONT click these links) - and hit return. No need to log in - just click on the “Router Status” icon/text at bottom-middle (Hub3/4/5) or top/right (SH’s) - of the Login page.

Then… Navigate to these “data pages” and just copy/paste the normal “Formatted Text” (not images) 3 FULL sets of data onto here – 2 tables from the Downstream, 2 from the Upstream, & the Network Logs pages. Don't worry too much about the formatting it can be easily read & DON’T include personal data or MAC addresses - blank them out - if you copy/paste the data, the board software will do this for you (you may need to click the "submit" button again). If character limits are “exceeded” - just do two posts

Also, If you haven’t already, set up a free, secure and “offlsite” - “Broadband Quality Monitor” to continually monitor the state of your connection and record any true network dropouts , latency issues, packet drops, etc - it will thus allow you to differentiate between those and simple wifi dropouts. It does it 24/7/365 and it keeps a visual record of any/all of your network disconnections, useful data to have to match to the Network logs (in your Hub settings) and also in discussions with VM - note it will take a few hours to start seeing a sensible picture - post up the “link” to the “share live graph”. Click the lower link (Share Live Graph) then, click generate. Copy the text in the Direct Link box, beware, there may be more text than you can see. On here click the Link icon (2 links chain to the left of the camera icon) In the URL box paste the link you copied and then click OK

https://www.thinkbroadband.com/broadband/monitoring/quality

[stelyth]

Thanks for the update, here is the info.

Network Log

Time Priority Description

17-05-2023 18:28:44	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-05-2023 18:28:44	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-05-2023 18:28:44	critical	16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-05-2023 18:28:24	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-05-2023 18:28:24	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-05-2023 18:28:24	critical	16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-05-2023 18:27:24	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-05-2023 18:27:24	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-05-2023 18:27:24	critical	16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-05-2023 18:27:04	critical	16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-05-2023 18:27:04	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-05-2023 18:26:24	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-05-2023 18:26:04	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-05-2023 18:26:04	critical	16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-05-2023 18:23:45	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-05-2023 17:24:02	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;
17-05-2023 17:24:02	notice	US profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-05-2023 17:16:31	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-05-2023 17:16:31	critical	16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-05-2023 17:12:32	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-05-2023 17:12:29	critical	16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-05-2023 17:12:29	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-05-2023 17:12:19	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-05-2023 17:12:19	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;
17-05-2023 17:11:52	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-05-2023 17:06:52	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-05-2023 17:06:52	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;
17-05-2023 17:04:12	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-05-2023 16:42:20	notice	CM-STATUS message sent. Event Type Code: 3; Chan ID: N/A; DSID: 680596; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-05-2023 16:42:19	warning	Unicast DSID PSN startup error
17-05-2023 16:42:05	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;
17-05-2023 16:42:05	notice	US profile assignment change. US Chan ID: 14; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

Upstream bonded channels

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

0	49600000	56.5	5120	QAM 64	9
1	43100000	56	5120	QAM 64	10
2	36600000	55.5	5120	QAM 64	11
3	30100000	55.8	5120	QAM 64	12
4	23600000	55	5120	QAM 64	13

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

0	ATDMA	0	903	17	0
1	ATDMA	0	903	18	0
2	ATDMA	0	903	35	0
3	ATDMA	0	903	18	0
4	ATDMA	0	903	36	0

Downstream bonded channels

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

1	138000000	-1.9	39	QAM 256	1
2	146000000	-2.2	39	QAM 256	2
3	154000000	-2.5	40	QAM 256	3
4	162000000	-2.5	41	QAM 256	4
5	170000000	-2.4	41	QAM 256	5
6	178000000	-2.4	41	QAM 256	6
7	186000000	-3	41	QAM 256	7
8	194000000	-3.3	41	QAM 256	8
9	202000000	-3.6	41	QAM 256	9
10	210000000	-3.2	41	QAM 256	10
11	218000000	-3	39	QAM 256	11
12	226000000	-3.2	39	QAM 256	12
13	234000000	-3.7	41	QAM 256	13
14	242000000	-3.9	41	QAM 256	14
15	250000000	-3.9	41	QAM 256	15
16	258000000	-3.8	41	QAM 256	16
17	266000000	-3.8	41	QAM 256	17
18	274000000	-3.9	41	QAM 256	18
19	282000000	-4.2	41	QAM 256	19
20	290000000	-4.2	41	QAM 256	20
21	298000000	-3.9	41	QAM 256	21
22	306000000	-3.8	41	QAM 256	22
23	314000000	-3.9	41	QAM 256	23
24	322000000	-4.6	40	QAM 256	24
25	330000000	-5	40	QAM 256	25
26	338000000	-5.2	40	QAM 256	26
27	346000000	-5	40	QAM 256	27
28	354000000	-4.8	40	QAM 256	28
29	362000000	-4.5	40	QAM 256	29
30	370000000	-4.8	40	QAM 256	30
31	378000000	-5.3	40	QAM 256	31

Downstream bonded channels

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

1	Locked	39	43105260	5390
2	Locked	39	10038725	61567
3	Locked	40	423325	62982
4	Locked	41	1175334	81995
5	Locked	41	269952	349183
6	Locked	41	84383	165953
7	Locked	41	275688	504879
8	Locked	41	29221	4654
9	Locked	41	24572	4055
10	Locked	41	19206	2958
11	Locked	39	19577	3630
12	Locked	39	18929	2714
13	Locked	41	16395	1484
14	Locked	41	19467	2137
15	Locked	41	17928	1697
16	Locked	41	11985	979
17	Locked	41	15276	1307
18	Locked	41	13693	1109
19	Locked	41	17456	471
20	Locked	41	73077	464
21	Locked	41	72714	348
22	Locked	41	10985	82
23	Locked	41	5753	204
24	Locked	40	5912	247
25	Locked	40	3077	58
26	Locked	40	3284	87
27	Locked	40	4530	129
28	Locked	40	6130	17
29	Locked	40	1846195	17
30	Locked	40	3076277	23
31	Locked	40	20975457	124

[jbrennand]

Not great... but can you start from a clean sheet and do this and then post up the stats again after 20-30 minutes

Switch the Hub off and unplug it from the mains supply for five minutes. Whilst it's off, do a quick check that all of your coax and ethernet cable connections are in nice and "finger" tight - at the Hub and wall box and also at any connectors etc. Ensure there are no “unterminated cable loose ends. Disconnect all the connections and reconnect to be sure. Also check that the internal wiring is ok with no kinking or chaffing. When its light, check that all looks good with the outside cabling and wall box (no “staples, etc.,) piercing the cables. Then switch the Hub back on and leave ~5 minutes When all done, check back in the settings and ensure that the RS error counts and T3 errors have all reset to 0. Then check every hour or so to see if they start reappearing - they shouldn't. If they do (particularly the postRS and T3 ones) you have a problem (noise) that only a Tech visit will sort.

[stelyth]

Cheers for the info, have done the reset and checked all cables. I'll just keep an eye on it now and get back with anything further.

[Kain_W]

Thanks for the response stelyth,

Welcome back to the community.

Keep us updated on how things go.

Regards,

[VMUser1812]

I do have to say, I’m not too sure why you were asked to post up all sorts of additional data, when it was screamingly obvious from your first post that you have an upstream connectivity issue, could be a loose cable joint, but I doubt it, almost certainly you’ll need a tech visit to sort it out.