Hub 5 Time sync

[Osram]

Hi

Any body now how important Time sync is on a Hub5, mine has always failed to sync on reboot and today I have noticed that the Log times are about 2 hours in the future, the last reboot was yesterday morning time now is 16:22 so been wrong well over 24 hours. This may have always been the case since getting Hub5 and 1gig last Oct, but I always assumed that it corrected itself without producing a log event. 

[John_GS]

Hi @Osram 

Thanks for posting and welcome back to the community. 

Are you having any broadband issues? 

We've sent your post to the relevant team and if we need further assistance we'll reply back here but please do let us know if you are having service issues and we'll be glad to help.

[Osram]

Hi John

At present service is working okay, but the logs are filling up with crap as follows below. Ever since installation in Oct 22 it has always done this, 3 engineer visits and a replacement hub5 (second engineer condemed first one but I feel it worked better than this older one) all un neccesary spliters removed and required ones replaced, differing views from engineers as to value of the attenuater required etc etc etc. I now anticipate by regularly checking logs when it is likely to reboot it's self and manualy reboot it at a least critical time (my son works from home and has lost commission on several ocasions by the antics of your service. Yes is it working now but the logs are telling me it is likely to reboot soon unless I intervene, the last reboot was 28th May at 1pm. The BQM currently looks ok but start showing lost packets prior to self booting. Quite frankly I wish I had stayed with the 3 mobile 5g modem I had on trial for nearly a month, it's only downside was that the wifi signal was not very strong, this may have improved with their latest newer modem. 

Sorry for the rant, but why should I have to reboot every few days because of poor equipment and dated cableing.

Kevin.

Note the time of top entry in Network log actual time is now 21:58

Network Log

Time Priority Description

30-05-2023 23:45:11	error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
30-05-2023 05:21:59	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;
30-05-2023 04:02:08	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
30-05-2023 04:02:08	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;
30-05-2023 03:58:16	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
30-05-2023 03:57:36	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;
30-05-2023 02:44:23	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;
30-05-2023 02:44:23	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;
30-05-2023 02:44:23	warning	Dynamic Range Window violation
30-05-2023 02:44:23	warning	Dynamic Range Window violation
29-05-2023 23:46:41	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
29-05-2023 23:46:41	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;
29-05-2023 23:36:48	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
29-05-2023 19:38:11	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;
29-05-2023 19:38:11	warning	Dynamic Range Window violation
29-05-2023 17:46:46	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;
29-05-2023 17:46:46	notice	US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
29-05-2023 16:53:07	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;
29-05-2023 16:46:39	notice	US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
29-05-2023 16:46:39	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;
29-05-2023 16:15:31	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;
29-05-2023 16:05:23	notice	US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
29-05-2023 16:05:23	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;
29-05-2023 08:46:54	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;
29-05-2023 08:43:56	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
29-05-2023 08:41:24	notice	US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
29-05-2023 08:41:24	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;
29-05-2023 08:37:15	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;
29-05-2023 07:42:08	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
29-05-2023 07:42:08	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;
29-05-2023 07:41:47	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
29-05-2023 07:40:31	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;

[Osram]

MORE

Upstream bonded channels

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

0	49600000	49	5120	QAM 64	1
1	43100000	48.5	5120	QAM 64	2
2	36600000	48	5120	QAM 64	3
3	30100000	48	5120	QAM 64	4
4	23600000	48	5120	QAM 64	5

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

0	ATDMA	0	37	0	0
1	ATDMA	0	37	0	0
2	ATDMA	0	37	1	0
3	ATDMA	0	37	0	0
4	ATDMA	0	37	55	0

Downstream bonded channels

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

1	363000000	7.3	40	QAM 256	29
2	211000000	5.3	38	QAM 256	10
3	219000000	5.2	38	QAM 256	11
4	227000000	5	38	QAM 256	12
5	235000000	4.5	37	QAM 256	13
6	243000000	4.4	37	QAM 256	14
7	251000000	4.7	38	QAM 256	15
8	259000000	5.5	38	QAM 256	16
9	267000000	5.7	39	QAM 256	17
10	275000000	6.2	39	QAM 256	18
11	283000000	6.5	39	QAM 256	19
12	291000000	6.5	39	QAM 256	20
13	299000000	6.5	39	QAM 256	21
14	307000000	6.7	39	QAM 256	22
15	315000000	6.7	39	QAM 256	23
16	323000000	6.8	39	QAM 256	24
17	331000000	6.8	39	QAM 256	25
18	339000000	6.7	39	QAM 256	26
19	347000000	7	39	QAM 256	27
20	355000000	7.2	39	QAM 256	28
21	371000000	6.9	39	QAM 256	30
22	379000000	7.1	40	QAM 256	31
23	387000000	6.7	40	QAM 256	32
24	395000000	6.9	40	QAM 256	33
25	403000000	7.1	40	QAM 256	34
26	411000000	7	40	QAM 256	35
27	419000000	6.7	40	QAM 256	36
28	427000000	6.8	40	QAM 256	37
29	435000000	6.8	40	QAM 256	38
30	443000000	7.1	40	QAM 256	39
31	451000000	7.5	40	QAM 256	40

Downstream bonded channels

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

1	Locked	40	28389	9011
2	Locked	38	24792	18000
3	Locked	38	17748	7374
4	Locked	38	16283	6575
5	Locked	37	16257	6343
6	Locked	37	15728	6551
7	Locked	38	12972	6477
8	Locked	38	10630	5670
9	Locked	39	6056	3667
10	Locked	39	15476	7085
11	Locked	39	7708	5141
12	Locked	39	51432	20857
13	Locked	39	7232	4966
14	Locked	39	6925	5298
15	Locked	39	40218	13644
16	Locked	39	9767	3682
17	Locked	39	5238	3753
18	Locked	39	3985	3133
19	Locked	39	5070	2873
20	Locked	39	3485	2638
21	Locked	39	2879	2134
22	Locked	40	5041	3543
23	Locked	40	3054	2845
24	Locked	40	8503	4628
25	Locked	40	2784	2354
26	Locked	40	3357	3015
27	Locked	40	7034	4997
28	Locked	40	5128	3605
29	Locked	40	4087	3918
30	Locked	40	3832	3548
31	Locked	40	1934	2043

[Adduxi]

Far too many Upstream T3 errors and PostRS errors. Indicative of noise in the circuit or a SNR fault at a guess. A VM Mod should be able to diagnose and get a technician in to help. 

[Adri_G]

Hi Osram, thanks for coming back to us and for updating the thread.

Sorry to see you're getting these log issues still and that you've also experienced a few problems with your service performance, glad to assist with that.

As you've attempted many hub reboots and things have not improved so far, could you see if a pin hole reset would improve things?

Please, be advised this will cause all your hub settings to go back to default - however it's worth a try if not tested yet.

We'd like to also ask as you've explained there have been a few visits from our engineers regarding the cabling and in-home network where have we left things and has the team advised of any more work to be done?

Are you using any 3rd party equipment currently?

Share a bit more and we'll be eager to assist you, cheers.

[Osram]

Hello again Adduxi,

Hi Adri

Yes Pin hole resets have been tried on several occasions to no real avail just clears logs and starts the whole saga again. None of the visiting engineers have advised of any further work required, to be fair they have all been rather rushed and seem to have a trial and error approach. Not sure what you mean by 3rd party equipement? I have a 4 way tp Link network switch which is cabled via a cat 7 cable to upstairs, which in turn connects  3 desk tops, On wifi there are 4 cameras, 6 Kasa switches, 1 smart TV, 3 Fire tv sticks, 3 heat and hot water switches, 3 mobile phones, 1 Ipad and my Laptop. Thats about it.

[John_GS]

Hi @Osram 

Thanks for coming back to the thread. The incorrect timing on the logs has been raised but shouldn't be causing any issues. I've ran a check on the system today, your levels are slightly high on the downstream but in spec. There was an issue with the SNR on the upstream but now that has gone back in spec.

Please do keep us posted if you are having service issues.

Best wishes.

[Osram]

Hi John

Thanks for your reply, unfortunately the upstream levels have gone up above the level of 51 that I believe is max, although the T1 2 3 4s seem to be the same, Pre and post errors on the Down stream are increasing, time sync is still 2 hours in the future as far as I can tell :-

Kevin

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
0 49600000 55 5120 QAM 64 1
1 43100000 55 5120 QAM 64 2
2 36600000 55 5120 QAM 64 3
3 30100000 55 5120 QAM 64 4
4 23600000 55 5120 QAM 64 5

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
0 ATDMA 0 37 0 0
1 ATDMA 0 37 0 0
2 ATDMA 0 37 1 0
3 ATDMA 0 37 0 0
4 ATDMA 0 37 74 0

[Adduxi]

Terrible stats on the Upstream channel 4 for T3 Timeouts, and the power level is still too high, range should really be between 34 to 51.  If the PostRS errors continue to rise, there is a problem with the circuit somewhere, and VM should really find and fix it.....

Set a BQM now and keep it running as it records the stats of the circuit and is a great troubleshooting tool   www.thinkbroadband.com/ping