Menu
Reply
  • 43
  • 0
  • 0
Tuning in
233 Views
Message 1 of 13
Flag for a moderator

Connection dropping intermittently - how to report?

Hi,

Could someone offer some advice on how best to report an intermittent problem to VM? My connection is dropping for less than a minute every so often, not usually long enough for the green lights to flash on the SH 3.0, but long enough to lose connections to services.

If I contact the support line, I suspect they are likely to state that there is no demonstrable fault.

The service interruptions are frustrating enough to impair home working.

The loss of connectivity can be correlated with CM "SYNC Timing Synchronization failure" messages in the CM logs.

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

11390000007.338256 qam1
21470000007.138256 qam2
31550000007.340256 qam3
41630000007.438256 qam4
51710000007.440256 qam5
61790000007.138256 qam6
71870000007.138256 qam7
81950000007.340256 qam8
92030000007.138256 qam9
102110000007.138256 qam10
112190000007.140256 qam11
122270000006.938256 qam12
132350000006.538256 qam13
14243000000638256 qam14
152510000005.838256 qam15
162590000005.538256 qam16
172670000006.138256 qam17
182750000006.638256 qam18
192830000007.338256 qam19
202910000007.640256 qam20
212990000007.938256 qam21
223070000007.838256 qam22
233150000008.140256 qam23
243230000008.540256 qam24



Downstream bonded channels

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

1Locked38.61974243024
2Locked38.91717155882
3Locked40.31687054861
4Locked38.91587356510
5Locked40.91575850445
6Locked38.91585844642
7Locked38.91597541056
8Locked40.31578535051
9Locked38.91575729124
10Locked38.91538924178
11Locked40.31522923511
12Locked38.91533723632
13Locked38.91539824302
14Locked38.91545822521
15Locked38.61562221111
16Locked38.91534419637
17Locked38.91514516275
18Locked38.91466815328
19Locked38.91459415649
20Locked40.31466615340
21Locked38.91468113156
22Locked38.91433712222
23Locked40.31409211465
24Locked40.31410411066

 

Upstream bonded channels

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

14620000043.8512064 qam3
23940000043.3512064 qam4
35370000044512064 qam2
46030000044.8512064 qam1

 

Logs:

Time Time Priority Description
20/11/2020 12:37:56 notice LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/11/2020 12:25:1 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/11/2020 12:25:1 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/11/2020 12:20:41 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/11/2020 12:20:41 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/11/2020 12:14:23 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/11/2020 11:47:44 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/11/2020 11:47:19 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/11/2020 11:47:19 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/11/2020 11:47:17 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/11/2020 11:47:17 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/11/2020 11:47:2 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/11/2020 11:47:2 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/11/2020 11:46:46 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/11/2020 11:46:46 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/11/2020 11:46:32 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/11/2020 11:45:58 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/11/2020 11:14:41 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/11/2020 11:14:41 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

0 Kudos
Reply
  • 12.3K
  • 952
  • 1.58K
Alessandro Volta
227 Views
Message 2 of 13
Flag for a moderator

Re: Connection dropping intermittently - how to report?

Your Pre & Post RS Error counts are very high.

In an ideal world they would be at zero and stay there. To zero them can you reboot the Hub using this method and then keep an eye on the counts.

Switch the Hub off using the small switch on the rear of the Hub next to the power cord and pull the PSU plug from the wall socket.

Give it a good 5 minutes put the plug back in and switch the Hub back on.

Allow the Hub a few minutes to fully restart then check the counts again in an hour or so.

***********************************************************************************************************************************

Mike Robinson
Semi-Retired Aircraft Engineer & Computer Based Training and Learning Designer for many of the world's Military Arms.

My Broadband Ping - Mike Robbo
0 Kudos
Reply
  • 12.3K
  • 952
  • 1.58K
Alessandro Volta
226 Views
Message 3 of 13
Flag for a moderator

Re: Connection dropping intermittently - how to report?

Can you set up a Broadband Quality Monitor (BQM) at thinkbroadband.com - this will give you an insight into what is happening with the signal at the other side of the Hub, it will take a few hours to get any kind of trend showing although you should post the link straight away.

Post a 'Live Link' to your BQM on here.

Instructions for posting BQM Link

Under your BQM graph are two links in red.

Click the lower link (Share Live Graph) then click generate.

Copy the text in the Direct Link box, beware, there may be more text than you can see.

On here click the Link icon (2 links chain to the left of the camera icon)

In the URL box paste the link you copied and in the ‘text to display’ box write My BQM then click OK - you can post the link straight away.

***********************************************************************************************************************************

Mike Robinson
Semi-Retired Aircraft Engineer & Computer Based Training and Learning Designer for many of the world's Military Arms.

My Broadband Ping - Mike Robbo
0 Kudos
Reply
  • 43
  • 0
  • 0
Tuning in
196 Views
Message 4 of 13
Flag for a moderator

Re: Connection dropping intermittently - how to report?

Hi,

Thanks for the tips.

Attached are two outputs of the pre/post-RS errors, about 4 hours apart after a modem reboot. The errors don't appear to increment significantly when the system is stable, more when the connection is interrupted.

As far as I can see from the other parameters, power levels and SNR values are within acceptable limits.

I have created and include a BQM 

20/11 17:22

Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 38.6 1453 4260
2 Locked 38.9 1256 5692
3 Locked 40.3 1281 5294
4 Locked 38.9 1212 5705
5 Locked 40.3 1183 4954
6 Locked 38.9 1203 4620
7 Locked 38.9 1242 4057
8 Locked 40.9 1242 3655
9 Locked 38.9 1272 3472
10 Locked 38.9 1233 2598
11 Locked 40.3 1260 2469
12 Locked 38.6 1188 2697
13 Locked 38.9 1253 2655
14 Locked 38.9 1221 2376
15 Locked 38.9 1204 2617
16 Locked 38.9 1231 2272
17 Locked 38.6 1193 1835
18 Locked 38.9 1207 1705
19 Locked 38.9 1160 1843
20 Locked 40.3 1173 1899
21 Locked 38.9 1160 1614
22 Locked 38.9 1311 1379
23 Locked 39.3 1252 1432
24 Locked 40.3 1139 1437

20/11 21:32

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 38.9 3655 11886
2 Locked 38.9 3135 14390
3 Locked 40.3 3046 13971
4 Locked 38.9 2825 15024
5 Locked 40.3 2892 12693
6 Locked 38.9 2742 12313
7 Locked 38.9 2888 10914
8 Locked 40.9 2979 9381
9 Locked 38.9 3018 8351
10 Locked 38.9 3013 6743
11 Locked 40.9 3043 6679
12 Locked 38.9 2974 6870
13 Locked 38.9 3153 6705
14 Locked 38.9 3117 6264
15 Locked 38.9 3171 6269
16 Locked 38.9 3224 5760
17 Locked 38.9 3115 4708
18 Locked 38.9 3221 4409
19 Locked 38.9 3128 4693
20 Locked 40.3 3115 4545
21 Locked 38.6 3123 3961
22 Locked 38.9 3349 3473
23 Locked 39.3 3116 3681
24 Locked 40.3 3037 3502

0 Kudos
Reply
  • 43
  • 0
  • 0
Tuning in
167 Views
Message 5 of 13
Flag for a moderator

Re: Connection dropping intermittently - how to report?

I have removed an internal amplifier which was installed by VM just in case it was failing in a way which was affecting the line, but it has made no difference (the downstream power levels numbers are still within specification, though reduced).

There has been around 24 hours' worth of data gathered by BQM - link is here 

Given the diagnostics here, does this point to an external issue, rather than a local issue with the SH3?

I've seen some anecodal reports in similar threads here that resetting the Hub to factory defaults might be worth a try, but I am not completely convinced. It should also be mentioned that this has only just starting happening in the last few days (previously, it's been rock solid, apart from the known issues on the status page from time to time, which have been resolved quickly) - and since VM were outside working in pits (though this may be entirely coincidental).

Hopefully on of the VM Forum Team will pick this up and advise.

0 Kudos
Reply
  • 43
  • 0
  • 0
Tuning in
125 Views
Message 6 of 13
Flag for a moderator

Re: Connection dropping intermittently - how to report?

I did decide to reset the SH3 using the technique described in the forums (hold in reset pin for 60 seconds), and initially, this looked to have had an effect. The Post-RS errors were non-zero, but the connection (according to the BQM) wasn't interrupted for nearly 15 hours. However, this afternoon the disconnections have been observed again:

https://www.thinkbroadband.com/broadband/monitoring/quality/share/3724cb7b1e81e3d599c85c69d85cdda056... 

Network Log
Time Priority Description
22/11/2020 14:49:32 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/11/2020 14:42:50 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/11/2020 14:42:50 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/11/2020 14:41:7 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/11/2020 14:22:5 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/11/2020 14:05:18 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/11/2020 13:27:21 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/11/2020 13:26:32 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/11/2020 22:04:59 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/11/2020 22:02:56 Warning! Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/11/2020 22:02:51 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/11/2020 22:02:51 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/11/2020 22:02:51 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:40 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

0 Kudos
Reply
  • 43
  • 0
  • 0
Tuning in
118 Views
Message 7 of 13
Flag for a moderator

Re: Connection dropping intermittently - how to report?

Well, I did decide to reset the SH3 using the technique described in these forums (hold down reset pin for 60 seconds).

Initially, this looked to have had an effect and no connection interruptions were seen (from BQM or Router logs) for over 15 hours, although my Post-RS error counts were non-zero before the first drop-out occurred.

Router logs:

22/11/2020 14:49:32 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/11/2020 14:42:50 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/11/2020 14:42:50 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/11/2020 14:41:7 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/11/2020 14:22:5 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/11/2020 14:05:18 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/11/2020 13:27:21 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/11/2020 13:26:32 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/11/2020 22:04:59 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/11/2020 22:02:56 Warning! Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/11/2020 22:02:51 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/11/2020 22:02:51 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/11/2020 22:02:51 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:40 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/11/2020 21:52:47 notice LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:39 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/11/2020 20:09:28 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/11/2020 20:09:28 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/11/2020 20:04:12 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/11/2020 20:04:12 critical SYNC Timing Synchronization failure - Loss of Sync;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
1 139000000 2.5 38 256 qam 1
2 147000000 2.4 38 256 qam 2
3 155000000 2.4 40 256 qam 3
4 163000000 2.5 38 256 qam 4
5 171000000 2.5 40 256 qam 5
6 179000000 2.2 40 256 qam 6
7 187000000 2.2 38 256 qam 7
8 195000000 2.4 40 256 qam 8
9 203000000 2 38 256 qam 9
10 211000000 2 38 256 qam 10
11 219000000 2 38 256 qam 11
12 227000000 1.7 38 256 qam 12
13 235000000 1.5 38 256 qam 13
14 243000000 1.2 38 256 qam 14
15 251000000 0.7 38 256 qam 15
16 259000000 0.5 38 256 qam 16
17 267000000 1.2 38 256 qam 17
18 275000000 1.5 38 256 qam 18
19 283000000 2 38 256 qam 19
20 291000000 2.5 40 256 qam 20
21 299000000 2.7 38 256 qam 21
22 307000000 2.7 38 256 qam 22
23 315000000 3.2 40 256 qam 23
24 323000000 3.5 38 256 qam 24


Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 38.6 2105 4064
2 Locked 38.9 1932 5249
3 Locked 40.3 1882 5646
4 Locked 38.9 1795 5772
5 Locked 40.3 1725 5455
6 Locked 40.9 1747 5508
7 Locked 38.9 1766 5464
8 Locked 40.3 1783 4131
9 Locked 38.9 1793 3542
10 Locked 38.9 1693 3089
11 Locked 38.9 1662 3171
12 Locked 38.9 1720 2965
13 Locked 38.9 1809 3312
14 Locked 38.6 1756 2975
15 Locked 38.6 1782 2805
16 Locked 38.9 1776 2678
17 Locked 38.9 1681 2162
18 Locked 38.9 1632 2169
19 Locked 38.9 1670 2138
20 Locked 40.3 1644 2388
21 Locked 38.9 1628 2151
22 Locked 38.9 1654 1672
23 Locked 40.3 1574 1873

0 Kudos
Reply
  • 43
  • 0
  • 0
Tuning in
82 Views
Message 8 of 13
Flag for a moderator

Re: Connection dropping intermittently - how to report?

Hi,

Is there anyone from the VM Forum Team who may be able to look at this please?

I have seen periods of ~12 and ~15 hours of a stable connection, and then the connection drops (see linked BQM), sometime just once, and other times, several brief outages are experienced.

Many thanks!

0 Kudos
Reply
  • 81
  • 0
  • 5
On our wavelength
79 Views
Message 9 of 13
Flag for a moderator

Re: Connection dropping intermittently - how to report?

I can remember exactly when this started as it coincided with the beginning of the very first lockdown. Mostly on an evening as my WFH has largely not been afflicted with this issue. I know a number of people from work who also live in the Bristol area (where I come from) who report EXACTLY the same thing.

Connection drops for 10 seconds then comes back up. Not the Wifi dropping (and my main desktop is using a cable), but the connection itself. No lights appearing on the router, you peer across at it and it all looks good. Then it comes back very quickly. As I say, it's down for all of 10 seconds. If you are watching a streaming service on a tablet or games console etc, you wouldn't even notice as the buffer would cover it up.

On a Win 10 desktop the network icon that looks like a monitor with a cable on the side of it turns into a globe so you can see that happen immediately.

There have been periods where it hasn't happened, or I haven't noticed it happen, for a couple of weeks. Then there are evenings where it's happening repeatedly. Can be every 30 seconds, every minute, or every 10 minutes or a couple of times an hour.  Given that inconsistency, with some times days or a week or two without an issue, and given that it is happening to so many others, I am calling utter rubbish on any suggestion that it is the router and won't waste my time faffing around with it. I did reboot it a few times back at the start but won't waste my time doing a merry dance now.

It's been fine for a few days but now tonight it's been back with a vengeance. Hence why I came here.

I don't believe there is anything we can do, and I also don't believe that VM are oblivious to it...so you are wasting your time posting all that stuff and jumping through those hoops.

 

0 Kudos
Reply
  • 43
  • 0
  • 0
Tuning in
63 Views
Message 10 of 13
Flag for a moderator

Re: Connection dropping intermittently - how to report?

Interesting to hear of similar issues elsewhere, and I am not too far away from you in Gloucester, although we're probably connecting to two different head-end CMTSes (Aztec West versus Staverton as a guess).

I spot the interruptions during workdays when I'm SSH'd into devices over a VPN (I'm a network engineer!), on a video call, or sometimes during streaming where the buffer just isn't quite large enough.

I too don't buy that it's a local router fault (but I felt that I had to go through the motions), and if it was an issue with the coaxial cabling (or an upstream amplifier/HFC device misbehaving), I'd half-expect it to affect the TiVo too, but it doesn't, which is more weight to the argument that it's not that, especially as the power-level and the SNR values on the Cable Modem are fine. If it was a cabling issue, it's usually more obvious from the downstream router stats.

Hopefully, VM are aware of it, but I am sceptical of a call to support actually acknowledging an issue, but at the moment I can't see how it's going to get resolved, and just hoping that VM fix it at some point is not going to be tenable if it continues for a prolonged period, due to work-from-home requirements.

0 Kudos
Reply