on 18-03-2022 12:36
Not sure if I have issues with my connection but upgraded to 1Gig a week or so back but it's just not as consistent/stable as the 600mb plan I had before.
Had the SH3 in modem mode to a Negear Orbi system before and now have the SH4 connected in the same way.
I seem to get regular loss of connection for a split second or so every day around 5pm as I lose connection to some work based systems which need a constant connection. Occasionally, family members have issues with basic tasks (web browsing etc) and my BQM seems to have significant latency spikes - my 600 connection had been pretty stable in recent months.
Wondered if someone can take a look please - thinking I might just cancel and move back to a slower but more consistent connection else.
1 | 411000000 | 3.799999 | 38.983261 | QAM256 | 1 |
2 | 419000000 | 3.400002 | 38.605377 | QAM256 | 2 |
3 | 427000000 | 3.500000 | 38.983261 | QAM256 | 3 |
4 | 435000000 | 3.400002 | 40.366287 | QAM256 | 4 |
5 | 443000000 | 3.500000 | 40.366287 | QAM256 | 5 |
6 | 451000000 | 3.299999 | 38.605377 | QAM256 | 6 |
7 | 459000000 | 3.099998 | 38.983261 | QAM256 | 7 |
8 | 467000000 | 3.200001 | 40.366287 | QAM256 | 8 |
9 | 475000000 | 3.400002 | 38.983261 | QAM256 | 9 |
10 | 483000000 | 3.700001 | 38.983261 | QAM256 | 10 |
11 | 491000000 | 3.799999 | 40.366287 | QAM256 | 11 |
12 | 499000000 | 3.900002 | 40.366287 | QAM256 | 12 |
13 | 507000000 | 3.799999 | 40.366287 | QAM256 | 13 |
14 | 515000000 | 3.900002 | 38.605377 | QAM256 | 14 |
15 | 523000000 | 4.099998 | 38.983261 | QAM256 | 15 |
16 | 531000000 | 4.199997 | 40.366287 | QAM256 | 16 |
17 | 539000000 | 4.199997 | 40.366287 | QAM256 | 17 |
18 | 547000000 | 4.300003 | 38.983261 | QAM256 | 18 |
19 | 555000000 | 4.300003 | 38.983261 | QAM256 | 19 |
20 | 563000000 | 4.300003 | 40.366287 | QAM256 | 20 |
21 | 571000000 | 4.300003 | 40.366287 | QAM256 | 21 |
22 | 579000000 | 4.199997 | 38.983261 | QAM256 | 22 |
23 | 587000000 | 4.199997 | 38.983261 | QAM256 | 23 |
24 | 595000000 | 4.099998 | 40.366287 | QAM256 | 24 |
25 | 603000000 | 4.099998 | 38.605377 | QAM256 | 25 |
26 | 611000000 | 4.400002 | 38.983261 | QAM256 | 26 |
27 | 619000000 | 4.300003 | 40.366287 | QAM256 | 27 |
28 | 627000000 | 4.300003 | 38.983261 | QAM256 | 28 |
29 | 635000000 | 4.099998 | 40.366287 | QAM256 | 29 |
30 | 643000000 | 4.199997 | 40.366287 | QAM256 | 30 |
31 | 651000000 | 4.199997 | 40.366287 | QAM256 | 31 |
1 | Locked | 38.983261 | 0 | 0 |
2 | Locked | 38.605377 | 0 | 0 |
3 | Locked | 38.983261 | 0 | 0 |
4 | Locked | 40.366287 | 0 | 0 |
5 | Locked | 40.366287 | 0 | 0 |
6 | Locked | 38.605377 | 0 | 0 |
7 | Locked | 38.983261 | 0 | 0 |
8 | Locked | 40.366287 | 0 | 0 |
9 | Locked | 38.983261 | 1 | 0 |
10 | Locked | 38.983261 | 7 | 0 |
11 | Locked | 40.366287 | 1 | 0 |
12 | Locked | 40.366287 | 1 | 0 |
13 | Locked | 40.366287 | 1 | 0 |
14 | Locked | 38.605377 | 0 | 0 |
15 | Locked | 38.983261 | 0 | 0 |
16 | Locked | 40.366287 | 0 | 0 |
17 | Locked | 40.366287 | 0 | 0 |
18 | Locked | 38.983261 | 0 | 0 |
19 | Locked | 38.983261 | 0 | 0 |
20 | Locked | 40.366287 | 0 | 0 |
21 | Locked | 40.366287 | 0 | 0 |
22 | Locked | 38.983261 | 0 | 0 |
23 | Locked | 38.983261 | 0 | 0 |
24 | Locked | 40.366287 | 0 | 0 |
25 | Locked | 38.605377 | 0 | 0 |
26 | Locked | 38.983261 | 0 | 0 |
27 | Locked | 40.366287 | 0 | 0 |
28 | Locked | 38.983261 | 1 | 0 |
29 | Locked | 40.366287 | 0 | 0 |
30 | Locked | 40.366287 | 0 | 0 |
31 | Locked | 40.366287 | 0 | 0 |
on 18-03-2022 12:37
33 | 96 | 4K | 1880 | QAM4096 | 759 |
33 | Locked | 42 | 3.5 | 537489566 | 5 |
1 | 53700000 | 48.270599 | 5120 KSym/sec | 64QAM | 2 |
2 | 60300000 | 48.270599 | 5120 KSym/sec | 64QAM | 1 |
3 | 46200000 | 47.770599 | 5120 KSym/sec | 64QAM | 3 |
4 | 39400000 | 47.520599 | 5120 KSym/sec | 64QAM | 4 |
1 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
2 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
3 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
4 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
Thu Jan 1 00:01:21 1970 | 4 | Missing Mandatory MDD TLV on primary DS Channel;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Jan 1 00:01:59 1970 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 11 13:38:48 2022 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 11 13:41:47 2022 | 6 | SW Download INIT - Via Config file cmreg-vmdg640-bbt076+voc-b.cm |
Fri Mar 11 13:43:06 2022 | 6 | SW download Successful - Via Config file |
Fri Mar 11 13:45:38 2022 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 11 14:15:53 2022 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 11 16:11:48 2022 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Mar 14 11:02:15 2022 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed Mar 16 13:07:07 2022 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
on 18-03-2022 13:33
Nothing I can see that's a problem - power, SNR, modulation and errors are all good - a handful of uncorrectables on the single D3.1 channel, but unless they're increasing that shouldn't be a problem. As you're using an Orbi mesh, you'll struggle to have any useful conversations with VM staff, so I'd give serious thought to cancel the upgrade if you're in the cooling off period, unless you're prepared to run the hub in router mode for a while, and jump through hoops for agents who report there's nothing wrong from their side?
on 20-03-2022 09:37
Thanks - I can't run in router mode sadly as the wifi range is so poor, I can't get a usable signal in my office when I work from home.
My BQM looks pretty good most of the time its just showing some large, short term latency spikes every few hours which I'm guessing is what causes the momentary drop outs on my server connections? It's just strange I never had this at all using the Orbi with the SH3 on the 600mb connection?
Think I will just cancel the 1Gig upgrade - stability is more useful to me than that extra speed.
on 20-03-2022 10:39
on 20-03-2022 11:12
I get one every hour.
on 20-03-2022 11:29
What I meant was set the Orbi to access point (sometimes called bridge) mode, and then have the hub as the router. Everything connects as you normally have it, and the Orbi provides the wifi, all the hub is doing is running the DHCP router. Not a preferred long term configuration, but stops VM blaming your equipment and means you can at least try and get them to fix a fault. My mesh system and hub are currently running in that configuration due to reliability problems, but even then there's no interest or ownership by VM in response to problems - the sole purpose of the customer service staff is to terminate a call as soon as they can and chalk it up as resolved (and the same for the equally disappointing complaints teams).
Your BQM shows spiking, but previous experience suggests that probably classifies as within tolerance for VM's low standards - trying to get it fixed may or may not solve the problem, but probably would carry you past the cooling off period, so if it doesn't work you'll be locked in. If you do revert, fingers crossed things improve.
on 21-03-2022 10:26
Ah right - thanks very much for explaining.
I ran the SH4 in Modem Mode a bit more yesterday with a Asus Gaming Router I have just to see if that showed any better results than the Orbi. The BQM latency was worse in this configuration - more frequent latency spikes so have binned that idea.
Today I've set up as you've suggested - with the Orbi in AP mode so will see how it performs on the BQM and in real world use as the day goes on.
on 21-03-2022 13:27
Early signs aren't promising - probably worse if anything - it's just annoying as these latency spikes didn't occur anything like as much on the 600 service.
on 23-03-2022 13:36
Hello @WhiteHartMart,
Welcome back, thanks for posting.
I am sorry for the issues with your broadband.
I checked our systems, I am unable to see any fault with your equipment. I can see that you are unhappy with your current speeds, what speeds are you getting on your wired connection?
Many thanks,
New around here? To find out more about the Community check out our Getting Started guide