on 24-08-2021 15:16
Hi,
Experiencing lots of glitchiness across my 100MB connection to a HUB3.
The logs are showing what feels like quite a lot of Pre and Post-RS errors:
Might this be the cause of the glitchiness? Worth escalating to the support team @ VM?
Thanks
Boyd
Answered! Go to Answer
on 26-08-2021 18:28
Thanks for getting back to me @bmo. I've scheduled a visit from an engineer, you will find confirmation via your online account (virg.in/myVM) and can reschedule from there if needed.
Please keep us posted with how that goes, or let us know if we can help with anything else.
Tom
on 24-08-2021 15:17
Oh - and I rebooted the hub last week....
on 24-08-2021 15:20
Logs are a little variable too. But then it's sometimes once per day, and other times pretty patchy/glitchy at times
Time Priority Description
24/08/2021 13:51:43 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/08/2021 13:46:54 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/08/2021 13:46:9 | Warning! | LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/08/2021 12:20:33 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/08/2021 01:31:2 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/08/2021 12:19:0 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/08/2021 17:24:43 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/08/2021 13:31:1 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/08/2021 17:05:53 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 24-08-2021 15:42
on 26-08-2021 15:57
Hi John,
Many thanks for the feedback.
I dumped the logs below.
I'll take a look at the broadband quality monitor - though pinging my router every second seems quite a bit.
Cheers
Boyd
Downstream bonded channels
Channel | Frequency (Hz) | Power (dBmV) | SNR (dB) | Modulation | Channel ID |
1 | 323000000 | -1.4 | 40 | 256 qam | 24 |
2 | 139000000 | -1.7 | 38 | 256 qam | 1 |
3 | 147000000 | -2 | 40 | 256 qam | 2 |
4 | 155000000 | -2.4 | 40 | 256 qam | 3 |
5 | 163000000 | -3 | 38 | 256 qam | 4 |
6 | 171000000 | -3 | 40 | 256 qam | 5 |
7 | 179000000 | -2 | 40 | 256 qam | 6 |
8 | 187000000 | -2 | 40 | 256 qam | 7 |
9 | 195000000 | -1.9 | 40 | 256 qam | 8 |
10 | 203000000 | -1.9 | 40 | 256 qam | 9 |
11 | 211000000 | -1.7 | 40 | 256 qam | 10 |
12 | 219000000 | -1.7 | 40 | 256 qam | 11 |
13 | 227000000 | -1.7 | 40 | 256 qam | 12 |
14 | 235000000 | -1.7 | 40 | 256 qam | 13 |
15 | 243000000 | -2 | 40 | 256 qam | 14 |
16 | 251000000 | -1.9 | 40 | 256 qam | 15 |
17 | 259000000 | -1.7 | 40 | 256 qam | 16 |
18 | 267000000 | -1.5 | 40 | 256 qam | 17 |
19 | 275000000 | -1.5 | 40 | 256 qam | 18 |
20 | 283000000 | -1.4 | 40 | 256 qam | 19 |
21 | 291000000 | -1.2 | 40 | 256 qam | 20 |
22 | 299000000 | -1.2 | 40 | 256 qam | 21 |
23 | 307000000 | -1.2 | 40 | 256 qam | 22 |
24 | 315000000 | -1.2 | 40 | 256 qam | 23 |
Downstream bonded channels
Channel | Locked Status | RxMER (dB) | Pre RS Errors | Post RS Errors |
1 | Locked | 40.9 | 1611 | 0 |
2 | Locked | 38.9 | 70030600 | 68538155 |
3 | Locked | 40.9 | 14600017 | 7116674 |
4 | Locked | 40.3 | 72099508 | 12255372 |
5 | Locked | 38.9 | 73570419 | 64205820 |
6 | Locked | 40.3 | 1159148 | 3847450 |
7 | Locked | 40.3 | 68531165 | 21116550 |
8 | Locked | 40.3 | 32426633 | 693228 |
9 | Locked | 40.3 | 66460 | 9714 |
10 | Locked | 40.9 | 45594 | 7604 |
11 | Locked | 40.3 | 28081 | 446 |
12 | Locked | 40.3 | 22323 | 278 |
13 | Locked | 40.3 | 35981 | 5129 |
14 | Locked | 40.9 | 33233 | 6394 |
15 | Locked | 40.3 | 19213 | 121 |
16 | Locked | 40.9 | 8698 | 103 |
17 | Locked | 40.3 | 11901 | 81 |
18 | Locked | 40.9 | 21517 | 3280 |
19 | Locked | 40.3 | 20324 | 551 |
20 | Locked | 40.3 | 4221 | 8 |
21 | Locked | 40.9 | 3205 | 32 |
22 | Locked | 40.9 | 13069 | 266 |
23 | Locked | 40.3 | 10486 | 25 |
24 | Locked | 40.3 | 1691 | 0 |
Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 53700000 | 51 | 5120 | 64 qam | 6 |
2 | 60300000 | 51 | 5120 | 64 qam | 5 |
3 | 39400000 | 51 | 5120 | 64 qam | 8 |
4 | 46199989 | 51 | 5120 | 64 qam | 7 |
Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 2 | 0 |
2 | ATDMA | 0 | 0 | 3 | 0 |
3 | ATDMA | 0 | 0 | 1 | 0 |
4 | ATDMA | 0 | 0 | 1 | 0 |
on 26-08-2021 15:58
And the Network Log
Network Log
Time | Priority | Description |
26/08/2021 14:34:21 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/08/2021 14:33:14 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/08/2021 14:00:57 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/08/2021 13:59:47 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/08/2021 13:59:14 | Warning! | LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/08/2021 12:12:20 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/08/2021 12:12:19 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/08/2021 10:57:59 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/08/2021 10:57:59 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/08/2021 10:22:2 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/08/2021 10:22:2 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
25/08/2021 22:48:0 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
25/08/2021 22:45:7 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
25/08/2021 20:57:19 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
25/08/2021 20:56:15 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
25/08/2021 20:44:57 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
25/08/2021 20:44:54 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
25/08/2021 18:13:42 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
25/08/2021 16:38:30 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/08/2021 22:06:58 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 26-08-2021 16:05
Hi bmo, thanks for posting.
Sorry to hear about the problems with your connection. I've taken a closer look into this today using your forum info and can see the upstream power levels are a bit on the high side and I feel this probably needs further attention.
If you get back to me via PM we'll be able to get that arranged for you.
Tom
on 26-08-2021 18:28
Thanks for getting back to me @bmo. I've scheduled a visit from an engineer, you will find confirmation via your online account (virg.in/myVM) and can reschedule from there if needed.
Please keep us posted with how that goes, or let us know if we can help with anything else.
Tom
on 27-08-2021 15:54
Hi Tom_F
Thanks for scheduling that.
The engineer has been (he was early) and has quickly identified and fixed a poor conection at street level so hopefully that is the root cause. Logs seem OK so far (but a little early to tell)
Kudos to both you and the engineer that turned up.
Thanks
Boyd
on 29-08-2021 15:59
Thanks for updating the thread bmo, glad we could help. Please don't hesitate to get back in touch if you have any more issues.
Tom