Virgin Media
My Virgin Media
Mobile Your Account
Paul,
Thanks for checking in.
The original post linked to my BQM setup, but I messed up the link, so here's from a few days ago (12th)
Yesterday morning I called in an got the expected "We can't talk to you unless you're running in router mode, so switch from modem mode to router mode for 48 hours and call again", and there's not been a massive change in stability, although packet loss has been gently mitigated (there were also "good days" in Modem Mode so I'm not convinced it made a difference.
The below is today's one (14th, i.e. >24hrs since switching to Router mode)
Is there any sensible way to attach this post to my customer profile so it's available to whomever picks up the phone tomorrow or will I get to tell a long story to someone just trying their best on a Thursday morning? 😄
Cheers.
Thanks for feeding back.
So, you can't see anything on the other side, and noone can send anyone out anyway, so there's functionally nothing I can do, right?
This one is from today, followed by a few highlights over the past week of BQM
Yesterday
Sunday, with some significant packet loss
And throughout the rest of last week, there seems to be a 'brown out' around 10pm every evening. While I wish my evening schedule was that fixed, there wasn't any "consistent behaviour" on our part that would indicate it's traffic related.
Is there any visibility of when engineering visits can be booked? Until then there's no point in me clogging up the phone lines.
Happy "Revenge of the 6th"!
In the continuing adventures of using this thread as a log while everyone gets their 5G administered, for the past 2 weeks I've had intermittent Hub dropouts. I can access my internal network fine.
When I catch them (or get caught by them) it takes an age to try and log in to the head router (192.168.0.1), so they seem to be full Hub resets, including resetting my now disabled Wifi connection settings.
That one was just before 6am on Wednesday and "only" lasted 3-5 minutes, and I've just had another one this morning, which prompted the bump
Network Log from today; Note, nothing that talks about the reset this morning
| 05/05/2021 21:16:23 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 05/05/2021 03:21:43 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 05/05/2021 03:08:23 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 05/05/2021 03:08:23 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 30/04/2021 07:11:4 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 29/04/2021 23:12:31 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 29/04/2021 23:12:31 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 27/04/2021 13:01:1 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 27/04/2021 02:50:11 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 27/04/2021 02:50:11 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 22/04/2021 11:56:6 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 22/04/2021 06:34:54 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 22/04/2021 06:34:54 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 21/04/2021 17:15:7 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 21/04/2021 17:15:7 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 21/04/2021 17:15:7 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 21/04/2021 17:15:7 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 21/04/2021 11:35:24 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 21/04/2021 09:52:52 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 20/04/2021 04:02:24 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
No expectation currently that anything can be fixed until engineers can come out of non-essential work, but this is very disappointing for a contract that was only signed a month or two ago...
