cancel
Showing results for 
Search instead for 
Did you mean: 

Intermittent dropouts lasting 2-3 minutes

jasonprf
On our wavelength

Hello,

I am suffering intermittent dropouts at (I believe) random times of the day. I noticed this in router mode and assumed the Virgin Hub was the issue so now use the router in modem mode with an Asus ZenWifi AX (AT8) router.

It has made no difference so I don't believe the issue is inside my property. It is affecting wired connections as well as the Wi-Fi, and there do not appear to be any wider issues in my area when I do a check. All wires are new and I have checked connections.

Does anyone know what I can check in the Hub 3.0 settings to see if it is a problem on the outside of my network?

24 REPLIES 24

Icantcrabhere
Superfast

Hi!

type in http://192.168.0.1 or http://192.168.100.1 (If in modem mode) in your browser,
Don't log in, click the text that says ">Check router status"

Copy and paste everything from the Upstream, Downstream and Network log.
The forum will filter out MAC-address.

Also set up one of these: https://www.thinkbroadband.com/broadband/monitoring/quality
You'll need to allow ICMP in the hub settings, however.

Network Log

Time Priority Description

23/08/2022 20:47:16noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2022 19:41:35criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2022 19:40:21criticalReceived 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.0;
23/08/2022 19:38:6criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2022 19:38:5Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2022 19:38:5criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2022 19:36:45Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2022 19:36:45criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2022 19:18:56Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2022 18:32:44criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2022 18:31:50criticalReceived 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.0;
23/08/2022 18:29:35criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2022 18:29:26Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2022 05:08:32noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2022 05:08:32ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2022 02:43:5Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2022 02:20:36criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2022 02:17:9Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2022 02:16:55criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2022 02:16:55Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Downstream bonded channels

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

13307500005.340256 qam25
22027500005.540256 qam9
32107500005.440256 qam10
42187500005.440256 qam11
52267500005.540256 qam12
62347500005.640256 qam13
72427500005.640256 qam14
82507500005.843256 qam15
92587500005.840256 qam16
102667500005.840256 qam17
112747500005.840256 qam18
122827500005.940256 qam19
132907500005.640256 qam20
142987500005.640256 qam21
153067500005.540256 qam22
163147500005.540256 qam23
173227500005.540256 qam24
18338750000540256 qam26
193467500005.340256 qam27
203547500005.340256 qam28
213627500005.140256 qam29
22370750000540256 qam30
233787500004.840256 qam31
243867500004.440256 qam32



Downstream bonded channels

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

1Locked40.32080
2Locked40.3170
3Locked40.3190
4Locked40.9170
5Locked40.9130
6Locked40.9150
7Locked40.9170
8Locked43.3180
9Locked40.9170
10Locked40.9180
11Locked40.9160
12Locked40.9120
13Locked40.9140
14Locked40.9120
15Locked40.9150
16Locked40.9140
17Locked40.3120
18Locked40.380
19Locked40.9130
20Locked40.3140
21Locked40.9120
22Locked40.9100
23Locked40.9180
24Locked40.960

Upstream bonded channels

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

13260002443512064 qam5
23940004843.5512064 qam4
34620000443.5512064 qam3
45370001745512064 qam2



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000

This error right here, quite a few of them in the logs.

23/08/2022 19:36:45Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;


and of course a few T4 timeouts to go along with it

23/08/2022 19:40:21criticalReceived 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.0;


I'm guessing the Post and Pre-RS errors are clearing after the T4 timeouts, or i'd be expecting to see a lot more of them from the partial service, etc.
Can you keep an eye on them and see how fast they climb?

You'll definitely need staff to take a look,
At least the issues are sticking out right away, so fingers crossed for a fast fix!

until then I'd suggest checking the service faults page: https://www.virginmedia.com/help/service-status
See if there's anything showing there for your post code.

If you're interested in what those error messages are, there's a lovely little write-up here: https://community.virginmedia.com/t5/Speed/Hub-status-data-understanding-network-log-messages/td-p/4...

Thanks so much for your help with this. That link explaining the errors is magic as well.

What's the best way to get someone on staff to read this post? Do they do it as a matter of course or do I need to somehow instigate this process?

Hey, no worries!
Just paying forward the same help i've received!
The link is definitely a good one 🙂

In regards to staff:

You'll have to wait a few days, usually. - you wont have to do anything 🙂
Much easier than dealing with and being fobbed off by the offshore CS.

Hey jasonprf, thank you for reaching out and I am sorry to hear you are having some connection issues.

Would it be possible to take it out of modem mode and just use the router to see if this makes any difference at all?

How did you get on checking the settings, has anything improved over the last few days? 

Please do let me know. Thanks 

Matt - Forum Team


New around here?

Hi Matthew,

I was using the hub in router mode and initially thought the issue was because of this. I then invested quite o lot of cash on the ASUS router system to boost my wifi coverage and also to take some of the 'load' off the virgin hub but the dropouts are still occurring. Nothing has changed over the past few days although I've not changed any settings. The help I received above was purely to obtain and share logs which I was advised point to an issue on the WAN rather than my LAN.