gig 1 hub 5 post rs errors

[johnnyboy98]

hi 

i'm getting a lot of post rs errors and a couple of things on the logs, I've tightened the coaxial cable going into the hub 5 and checked all the other connections. in a nutshell i would like to get some advice to see if its a noise problem and to see if i need to get an engineer to come out. 

Network Log

Time Priority Description

03-05-2023 17:46:19	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;
03-05-2023 16:42:31	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;
03-05-2023 14:20:22	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;
03-05-2023 11:23:27	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;
03-05-2023 10:19:38	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;
02-05-2023 21:33:54	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;
02-05-2023 20:30:05	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;
02-05-2023 04:49:56	error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-04-2023 18:39:30	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;
28-04-2023 17:43:45	notice	REGISTRATION COMPLETE - Waiting for Operational status
28-04-2023 17:43:42	notice	US profile assignment change. US Chan ID: 12; Previous Profile: 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-04-2023 17:43:37	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;
28-04-2023 17:43:24	warning	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-04-2023 17:43:22	notice	Honoring MDD; IP provisioning mode = IPv4
28-04-2023 17:43:16	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;
28-04-2023 17:42:28	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-04-2023 17:42: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;
28-04-2023 17:42:15	warning	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-04-2023 17:41: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;
28-04-2023 17:41:54	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-04-2023 17:41:52	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;
28-04-2023 17:37:51	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-04-2023 17:37:06	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-04-2023 17:36: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;
28-04-2023 17:36:47	critical	Cable Modem reset to Factory Default via reset button

Downstream bonded channels

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

1	331000000	1.5	42	QAM 256	25
2	211000000	2.1	42	QAM 256	10
3	219000000	2	41	QAM 256	11
4	227000000	1.9	42	QAM 256	12
5	235000000	1.9	42	QAM 256	13
6	243000000	1.8	42	QAM 256	14
7	251000000	2.1	42	QAM 256	15
8	259000000	2	42	QAM 256	16
9	267000000	2	42	QAM 256	17
10	275000000	2	42	QAM 256	18
11	283000000	2.2	42	QAM 256	19
12	291000000	2.1	42	QAM 256	20
13	299000000	2.2	42	QAM 256	21
14	307000000	2.1	42	QAM 256	22
15	315000000	1.9	42	QAM 256	23
16	323000000	1.8	42	QAM 256	24
17	339000000	1.4	41	QAM 256	26
18	347000000	1.5	42	QAM 256	27
19	355000000	1.2	42	QAM 256	28
20	363000000	1	42	QAM 256	29
21	371000000	1	42	QAM 256	30
22	379000000	1.1	42	QAM 256	31
23	387000000	1	42	QAM 256	32
24	395000000	0.7	42	QAM 256	33
25	403000000	0.7	42	QAM 256	34
26	411000000	0.5	42	QAM 256	35
27	419000000	0.1	42	QAM 256	36
28	427000000	0.5	42	QAM 256	37
29	435000000	0.1	42	QAM 256	38
30	443000000	0.3	42	QAM 256	39
31	451000000	0.7	42	QAM 256	40

Downstream bonded channels

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

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

[VMUser1812]

As regard to the logs, don’t panic! Read them from the bottom up. You rebooted the hub at 17:36:57 on 28th April (and by the way, the timestamp will seem to be wrong, and that is because the hubs uses UTC time which equates to GMT, but we have changed to British Summer Time, so the time will seem to be one hour behind). Moving on though, the next important event is at 17:43:22, honouring MDD. MDD is Mac Domain Descriptor, which means that the hub has identified the channel that it needs to be listening on to find further configuration information. Now, that does seem to be a bit long time, but for now, shrug and see how it goes.

Anyhow,17:43:45, registration complete, the hub has successfully negotiated its connection with VM’s infrastructure, it’s not some clone and is a genuine VM hub and is now connected. Everything else above that is fine tuning the connection, and everything up to that point can be safely ignored, the initial DOCSIS ranging and registration process is a bit of a mess, and until it has settled down then you can safely ignore all the messages.

However, I’m not too happy about the post RS errors being clustered around the lower frequencies. It does hint of a bit of noise (interference) ingress. But having said that, if your connection is working just fine, then really don’t worry too much about it. The underlying technology is really quite robust and good at working around ‘issues’ such as what you seem to have reported - although said ‘issues’ may just be a transient, and will go away of their own accord!

Now to be perfectly honest, I suspect that if you were to call VM and ask for an tech visit, it is more than likely to be denied, on the grounds that your connection is working within VM’s parameters Or, if one were to turn up, it is more than likely that they will shrug their shoulders, go through the motions of checking connections, and then declare ‘all is well’ and clear off!

Bottom line, what you have posted above, doesn’t actually point to any real fault in your connection at all. 

[Tudor]

What you could do is power cycle the hub and post a new set of figures after about 2 hours. This will show the current state of your circuit.

[johnnyboy98]

That's what I've done twice and still get the rs errors, I'll keep an eye on it as atm my connection isn't having any issues. I just wanted to make sure that I don't need to get this sorted.

Thanks 

[Adduxi]

A good circuit should have 0 PostRS errors.  If there are, and they continue to rise, it needs fixed.

PostRS errors are "un-correctable errors" and they have to be re-transmitted from the sender.

If they continue, I would press VM to send a technician to sort it out.

In the meantime, setup a BQM to record and monitor the state of the incoming circuit  www.thinkbroadband.com/ping

[johnnyboy98]

hi and thanks for the reply .

I currently have a bqm up and running and will post it in this box, do you think i need to get virgin to get someone up to look at this. 

thanks john 

[Zach_R]

Hi @johnnyboy98,

Thank you for your posts and welcome back to our community forums. We're here to help.

I'm very sorry to hear that you seem to be having some issues with your broadband connection recently. I've checked over things on our systems and I'm unable to detect any faults currently that would explain this. How are things for you today? Any better?

Thanks,
 

[johnnyboy98]

Hi Zach and thanks for your reply.

i have posted just above this post that i have had some post rs errors on my hub 5 status page and wanted to know if i need to get them sorted, if i could get your opinion on this it would be greatly appreciated and then i can close this thread on the forum.

thanks again

John

[Paul_DN]

Hi johnnyboy98,

Thanks for coming back to us, sorry to see you are facing issues still, I was able to have another look our end and cannot see any issues.

Regards

Paul.

[johnnyboy98]

Hi Paul and thanks for getting back to me

While you may not be seeing issues the post rs levels have went up since I last posted and am being told that it's okay to ignore one moment and to get an engineer next. Surly it all should be at 0. Is it possible that someone can give me an honest opinion instead of telling me that there isn't an issue in my area when I can check of this. Also is there a possibility that my area is a classic case of high utilisation.

Thanks john