Downstream Post RS errors in the thousands. Virgin haven't responded to complaint raised 6 days ago

Likely a utilisation problem setup a BQM

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

The "filter" is an attenuator and it modifies the power levels for the Hub. 

Try checking with Area faults on 0800 561 0061 or if you have a VM landline 150 as small local faults are not listed on the VM status page.

Can you please post all the power level stats and the network log, copy and paste as you have done above.  You are also correct that PostRS errors are a bad sign, as these need packets need to be retransmitted. 

Also setup a BQM to check for over utilisation in the evenings   www.thinkbroadband.com/ping

Once done we can comment on your circuit.

Thanks folks - been trying to find that site for ages as used it before put obviously wasn't using the correct web search terms.  Set a BQM going so hopefully will gather some data over next few days.

I know my work vpn connection drops packets all day long, intermittently. My VDP (and the wife's) drop out at least a few times a day when the packet drops get too many or for too long, sometimes session reconnects and others times have to disconnect from wifi and go back in (VDP sessions are using Microsoft OAVPN).

Here's router info just now:
I see the T3 errors are marked as 'critical' in the network log - don't know what that tends to indicate though?

Downstream bonded channels

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

Downstream bonded channels

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

Upstream bonded channels

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

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

Network Log
Time Priority Description
14/12/2023 22:24:7 notice LAN login Success;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;

13/12/2023 02:35:59 critical No Ranging Response received - T3 time-out;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;

12/12/2023 22:46:8 notice LAN login Success;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;

11/12/2023 21:06:28 critical No Ranging Response received - T3 time-out;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;

11/12/2023 11:17:37 notice DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060+voc-b.cm modified;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;

11/12/2023 11:17:37 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;

11/12/2023 02:11:26 critical No Ranging Response received - T3 time-out;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;

11/12/2023 02:11:19 Warning! Lost MDD Timeout;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;

11/12/2023 02:11:13 Warning! RCS Partial Service;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;

11/12/2023 02:11:13 Warning! Lost MDD Timeout;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;

11/12/2023 02:11:13 Warning! RCS Partial Service;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;

11/12/2023 02:11:13 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;

11/12/2023 02:11:12 Warning! RCS Partial Service;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;

11/12/2023 02:11:12 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;

11/12/2023 02:11:12 Warning! RCS Partial Service;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;

10/12/2023 10:29:6 critical No Ranging Response received - T3 time-out;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;

09/12/2023 22:02:12 notice LAN login Success;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;

09/12/2023 01:14:17 critical No Ranging Response received - T3 time-out;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;

08/12/2023 19:57:20 notice LAN login Success;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;

07/12/2023 23:17:37 notice DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060+voc-b.cm modified;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;

Was really bad today during the day, especially around 3pm-5pm - which is relatively unusual, as normally worst 7pm-10pm.

Todays BQM

[url=https://www.thinkbroadband.com/broadband/monitoring/quality/share/0f5670b8f2e6425e05ddbe8aa9d05fd8dbf02d10-16-12-2023]My Broadband Ping[/url]

https://www.thinkbroadband.com/broadband/monitoring/quality/share/0f5670b8f2e6425e05ddbe8aa9d05fd8dbf02d10-16-12-2023

Hi BobinEd,

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

I'm so sorry to hear you're having some trouble with your connection recently. I've just checked over things on our systems and I'm unable to detect any faults currently that would explain this.

Is this issue ongoing for you today? If so, can you clarify if it's only happening at certain times each day? Are you also able to share a live BQM as opposed to a snapshot so we can look at your connection quality in real-time instead of the past?

Thanks,
 

Are you still getting PostRS and T3 errors?  If so a technician should be in attendance to resolve this first before looking at over utilisation in the evenings. 

Looks to me that you have accumulated  0  PostRS errors since this thread started - the numbers in the tables look the same to me?.  So these might just be a historical record of a VM connection issue from some time ago.

So can you start from a blank sheet and do this.

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.   Disconnect all the connections and reconnect to be sure. Ensure there are no “unterminated cable loose ends.

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 of course. If they do (particularly the postRS and T3 ones) you do have a problem (noise) that only a Tech visit will sort.    Also check the Upstream QAM’s are all at 64.