Started Unicast Maintenance Ranging - No Response received

Question

Hi,I've recently joined Virginmedia on the Gig1 package and received a Hub5, which is in Modem mode. Every day I seem to get the error . . .Started Unicast Maintenance Ranging - No Response received - T3 time-outThis seems to cause my internet connection to hang for a few minutes.Here are my Hub 5 stats . . .Downstream bonded channelsChannel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID 1467000000341QAM 256824110000004.941QAM 256134190000004.841QAM 256244270000004.541QAM 256354350000004.341QAM 25646443000000440QAM 256574510000003.740QAM 256684590000003.141QAM 256794750000003.341QAM 2569104830000003.540QAM 25610114910000003.741QAM 25611124990000003.941QAM 25612135070000003.841QAM 25613145150000003.741QAM 25614155230000003.741QAM 25615165310000003.641QAM 25616175390000003.741QAM 25617185470000003.741QAM 25618195550000003.741QAM 25619205630000003.741QAM 25620215710000003.741QAM 25621225790000003.741QAM 25622235870000003.541QAM 25623245950000003.541QAM 25624256030000003.441QAM 25625266110000003.141QAM 25626276190000002.941QAM 2562728627000000341QAM 25628296350000003.141QAM 25629306430000003.241QAM 25630316510000003.241QAM 25631Downstream bonded channelsChannel Locked Status RxMER (dB) Pre RS Errors Post RS Errors 1Locked414202Locked412603Locked412104Locked412005Locked413306Locked403807Locked406308Locked414409Locked4143010Locked4029011Locked4134012Locked4132013Locked4125014Locked4127015Locked4139016Locked4139017Locked4137018Locked4132019Locked4132020Locked4137021Locked4145022Locked4133023Locked4151024Locked4141025Locked4143026Locked4148027Locked4162028Locked4174029Locked4157030Locked4152031Locked41490Upstream bonded channelsChannel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID 049600000455120QAM 64114310000044.55120QAM 642236600000445120QAM 64333010000043.55120QAM 644423600000435120QAM 645Upstream bonded channelsChannel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts 0ATDMA00401ATDMA00102ATDMA00003ATDMA00104ATDMA0020&nbsp;&nbsp;I wondered if the mods could take a look at my connection?&nbsp;Thanks

Adduxi · Answer

Power levels on the stats look okay.&nbsp; Post the full Network log as well.Also setup a BQM to monitor and record the incoming circuit, as it may show something to help.www.thinkbroadband.com/ping&nbsp;

Anonymous · Answer

Hi,Thanks for your reply - here is the Network log . . .&nbsp;Network LogTime Priority Description 09-06-2023 23:32:12criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;09-06-2023 23:22:25noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;09-06-2023 07:44:34errorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;09-06-2023 07:20:31criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;08-06-2023 12:16:38noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;08-06-2023 11:12:49noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;08-06-2023 08:42:01noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;08-06-2023 08:36:58noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;07-06-2023 16:40:01criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;07-06-2023 10:36:35noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;07-06-2023 10:31:32noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;07-06-2023 03:26:43noticeREGISTRATION COMPLETE - Waiting for Operational status07-06-2023 03:26:28criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;07-06-2023 03:26:27noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;07-06-2023 03:26:22noticeDS 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;07-06-2023 03:26:21noticeTLV-11 - unrecognized OID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;07-06-2023 03:26:19warningDHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;07-06-2023 03:26:17noticeHonoring MDD; IP provisioning mode = IPv407-06-2023 03:23:26criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;07-06-2023 03:23:07criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;07-06-2023 03:23:03criticalReceived 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;07-06-2023 03:22:40criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;07-06-2023 03:22:39criticalReceived 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;07-06-2023 03:21:56criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;07-06-2023 03:21:55criticalReceived 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;07-06-2023 03:21:12criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;07-06-2023 03:21:11criticalReceived 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;07-06-2023 03:20:30criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;07-06-2023 03:20:29criticalReceived 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;07-06-2023 03:19:28criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;07-06-2023 03:19:26warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;07-06-2023 03:19:17criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

Anonymous · Answer

Yet more errors in the Network log . . .

Network Log

Time Priority Description

11-06-2023 23:23:45	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
11-06-2023 23:23:45	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;
11-06-2023 23:22:37	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;

Paul_DN · Answer

Hi JCARRING,
Thank you for reaching out to us in our community and welcome sorry to hear you are getting errors since you have had your Hub 5.0, I was able to locate you on our system with the details we have for you and was unable to see any issues, I can see you have a 3rd party Router which means I can only check so much, so we can run further checks please put our Router in Router mode and remove yours.
Regards
Paul.

Anonymous · Answer

Hi,Thanks for your reply.I replaced the coax cable that was originally supplied by Virgin Media, with the cable that was supplied with the Hub 5. Not sure it would have made any difference, however so far I haven't seen any errors. The new cable has push on connectors rather than screw on, which I think is a better design.&nbsp;

Forum Discussion

Started Unicast Maintenance Ranging - No Response received

8 Replies

Related Content

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received

Errors - ‘No Ranging Response received - T3 time-out‘ and separate T4 time out

Tivo box cannot receive Netflix

No Ranging Response received - T3 time-out

Forbidden 403 - usual response doesn't work

1	467000000	3	41	QAM 256	8
2	411000000	4.9	41	QAM 256	1
3	419000000	4.8	41	QAM 256	2
4	427000000	4.5	41	QAM 256	3
5	435000000	4.3	41	QAM 256	4
6	443000000	4	40	QAM 256	5
7	451000000	3.7	40	QAM 256	6
8	459000000	3.1	41	QAM 256	7
9	475000000	3.3	41	QAM 256	9
10	483000000	3.5	40	QAM 256	10
11	491000000	3.7	41	QAM 256	11
12	499000000	3.9	41	QAM 256	12
13	507000000	3.8	41	QAM 256	13
14	515000000	3.7	41	QAM 256	14
15	523000000	3.7	41	QAM 256	15
16	531000000	3.6	41	QAM 256	16
17	539000000	3.7	41	QAM 256	17
18	547000000	3.7	41	QAM 256	18
19	555000000	3.7	41	QAM 256	19
20	563000000	3.7	41	QAM 256	20
21	571000000	3.7	41	QAM 256	21
22	579000000	3.7	41	QAM 256	22
23	587000000	3.5	41	QAM 256	23
24	595000000	3.5	41	QAM 256	24
25	603000000	3.4	41	QAM 256	25
26	611000000	3.1	41	QAM 256	26
27	619000000	2.9	41	QAM 256	27
28	627000000	3	41	QAM 256	28
29	635000000	3.1	41	QAM 256	29
30	643000000	3.2	41	QAM 256	30
31	651000000	3.2	41	QAM 256	31

1	Locked	41	42
2	Locked	41	26
3	Locked	41	21
4	Locked	41	20
5	Locked	41	33
6	Locked	40	38
7	Locked	40	63
8	Locked	41	44
9	Locked	41	43
10	Locked	40	29
11	Locked	41	34
12	Locked	41	32
13	Locked	41	25
14	Locked	41	27
15	Locked	41	39
16	Locked	41	39
17	Locked	41	37
18	Locked	41	32
19	Locked	41	32
20	Locked	41	37
21	Locked	41	45
22	Locked	41	33
23	Locked	41	51
24	Locked	41	41
25	Locked	41	43
26	Locked	41	48
27	Locked	41	62
28	Locked	41	74
29	Locked	41	57
30	Locked	41	52
31	Locked	41	49

0	49600000	45	5120	QAM 64	1
1	43100000	44.5	5120	QAM 64	2
2	36600000	44	5120	QAM 64	3
3	30100000	43.5	5120	QAM 64	4
4	23600000	43	5120	QAM 64	5

09-06-2023 23:32:12	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
09-06-2023 23:22:25	notice	US profile assignment change. US Chan ID: 12; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
09-06-2023 07:44:34	error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
09-06-2023 07:20:31	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
08-06-2023 12:16:38	notice	US profile assignment change. US Chan ID: 12; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
08-06-2023 11:12:49	notice	US profile assignment change. US Chan ID: 12; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
08-06-2023 08:42:01	notice	US profile assignment change. US Chan ID: 12; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
08-06-2023 08:36:58	notice	US profile assignment change. US Chan ID: 12; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
07-06-2023 16:40:01	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
07-06-2023 10:36:35	notice	US profile assignment change. US Chan ID: 12; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
07-06-2023 10:31:32	notice	US profile assignment change. US Chan ID: 12; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
07-06-2023 03:26:43	notice	REGISTRATION COMPLETE - Waiting for Operational status
07-06-2023 03:26:28	critical	No Ranging Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
07-06-2023 03:26:27	notice	US profile assignment change. US Chan ID: 12; Previous Profile: 13; New Profile: 11 13.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
07-06-2023 03:26:22	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;
07-06-2023 03:26:21	notice	TLV-11 - unrecognized OID;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
07-06-2023 03:26:19	warning	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
07-06-2023 03:26:17	notice	Honoring MDD; IP provisioning mode = IPv4
07-06-2023 03:23:26	critical	No Ranging Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
07-06-2023 03:23:07	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
07-06-2023 03:23:03	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;
07-06-2023 03:22:40	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
07-06-2023 03:22:39	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;
07-06-2023 03:21:56	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
07-06-2023 03:21:55	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;
07-06-2023 03:21:12	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
07-06-2023 03:21:11	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;
07-06-2023 03:20:30	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
07-06-2023 03:20:29	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;
07-06-2023 03:19: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;
07-06-2023 03:19:26	warning	MDD message timeout;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
07-06-2023 03:19:17	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;

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