Virgin Media Community

[Ron-ski]

Several evenings recently web pages have been very slow to respond, on checking my TBB ping monitor I see clear signs of peak time congestions.

Sorry about only posting links, but I don't have the time to workout how to post images as this forum doesn't seem to accept standard forum image code.

https://www.thinkbroadband.com/broadband/monitoring/quality/share/10d6a3a06e704a66ab3d62223085799299... 

https://www.thinkbroadband.com/broadband/monitoring/quality/share/67a853b3aa4dfaf42e590af9fcb0543559... 

https://www.thinkbroadband.com/broadband/monitoring/quality/share/dda9bc8bbcd4c35ef41e99bb63efe006c7... 

https://www.thinkbroadband.com/broadband/monitoring/quality/share/b1ae136c92680a697f92e9137484106e4d... 

https://www.thinkbroadband.com/broadband/monitoring/quality/share/5e2322b2e4e196f524ff393146286f7205... 

https://www.thinkbroadband.com/broadband/monitoring/quality/share/c146f8bb5ec3f0caa2cad497600b739e54... 

https://www.thinkbroadband.com/broadband/monitoring/quality/share/cb75908baf89a86d4835d937d97df760c4... 

https://www.thinkbroadband.com/broadband/monitoring/quality/share/1cc6da0b1415fbcd0a4e6ef0411cd1ea58... 

Any chance this is going to be fixed please?

[jbrennand]

Can you follow the instructions on the TB website to post a link to "share live graph". BQM's dont look great !

Have you checked first for “known network faults” As well as trying the “check service,” Area status webpage" (link at top right of this forum), also try the “free & automated” Service Status number - 0800 561 0061 - which usually gives the most up to date info. and tells you of more local issues down to postcode level.

However, congestion issues are often not reported on there - but worth a look Also post up yopu connection data - as per below - and lets see what VM staff say about the connection when they pick this up in a day or two.
________________________

In your browser’s URL box type in http://192.168.0.1  (or http://192.168.100.1 - if in modem mode) and hit return. On the first page up [there should be no need to login if you have done so before unless you have the New Hub4 when you do] click on the “router status” icon/text at bottom-middle of first page up and then copy/paste as “Formatted Text” (not images) 3 FULL sets of data onto here – 2 pages from the Downstream, 2 from the Upstream, & the Network Logs page. Don't worry too much about the formatting it can be easily read & DON’T include personal data or MAC addresses - blank them out - if you copy/paste the data, the board software will do this for you (you may need to click the "submit" button again.

[Andrew-G]

I don't think that's congestion, because the main problem is continuous packet loss at all times.  It will inherently be worse when there's more system use, but typically congestion problems are evidenced by steadily worsening latency that is much more intensive than shown in your BQM, with packet loss only a "side order".

If you follow @jbrennand 's advice to post the hub's status data somebody will take a look and advise - even if the problem isn't evident from the hub stats, I would expect that it can be fixed.

[Ron-ski]

Thanks for the replies, not sure why, but I've only just received an email notification that someone's replied - a week late!

No issues really since I posted, all been running smooth, link to live graph.

https://www.thinkbroadband.com/broadband/monitoring/quality/share/1d6fcf2a6171c36e1ae1f255513a45d3ad... 

I would have posted the nicely formatted copy and pasted tables, but the forum complains that the post exceeds 20,000 chrs even with just half a table pasted in!

Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 378750000 1.7 40 256 qam 27
2 202750000 2.2 40 256 qam 9
3 210750000 2.2 40 256 qam 10
4 218750000 2.2 40 256 qam 11
5 226750000 2 40 256 qam 12
6 234750000 2 40 256 qam 13
7 242750000 2 40 256 qam 14
8 250750000 1.7 40 256 qam 15
9 258750000 1.4 40 256 qam 16
10 266750000 1 40 256 qam 17
11 274750000 0.7 40 256 qam 18
12 282750000 0.5 40 256 qam 19
13 290750000 0.5 40 256 qam 20
14 298750000 0.5 40 256 qam 21
15 306750000 0.5 40 256 qam 22
16 314750000 1 40 256 qam 23
17 322750000 1.4 40 256 qam 24
18 330750000 1.5 40 256 qam 25
19 370750000 1.7 40 256 qam 26
20 386750000 1.5 40 256 qam 28
21 394750000 1.5 40 256 qam 29
22 402750000 1.7 40 256 qam 30
23 410750000 1.7 40 256 qam 31
24 418750000 1.7 40 256 qam 32

Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 40.3 70 0
2 Locked 40.3 149 0
3 Locked 40.3 156 0
4 Locked 40.9 125 0
5 Locked 40.3 106 0
6 Locked 40.3 103 0
7 Locked 40.3 128 0
8 Locked 40.3 129 0
9 Locked 40.3 126 0
10 Locked 40.3 129 0
11 Locked 40.9 137 0
12 Locked 40.3 163 0
13 Locked 40.3 152 0
14 Locked 40.3 172 0
15 Locked 40.3 165 0
16 Locked 40.9 119 0
17 Locked 40.3 115 0
18 Locked 40.3 84 0
19 Locked 40.3 75 0
20 Locked 40.3 101 0
21 Locked 40.9 120 0
22 Locked 40.3 176 0
23 Locked 40.3 185 0
24 Locked 40.3 122 0

Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 39400000 32.8 5120 64 qam 12
2 32600000 32.8 5120 64 qam 13
3 46200000 33.3 5120 64 qam 11
4 53700000 33.3 5120 64 qam 10

Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 ATDMA 0 0 18 0
2 ATDMA 0 0 1536 0
3 ATDMA 0 0 6 0
4 ATDMA 0 0 13 0

Network Log
Time Priority Description
08/06/2021 14:37:24 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/06/2021 06:21:37 notice DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/06/2021 06:21:37 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/06/2021 23:56:41 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/06/2021 18:21:36 notice DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/06/2021 18:21:36 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/06/2021 07:02:50 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/06/2021 06:21:36 notice DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/06/2021 06:21:36 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/05/2021 12:17:12 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/05/2021 09:36:36 notice DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/05/2021 09:36:36 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/05/2021 09:36:34 Error DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/05/2021 14:28:54 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/05/2021 14:06:34 notice DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/05/2021 14:06:34 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/05/2021 02:36:49 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/05/2021 02:06:34 notice DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/05/2021 02:06:34 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/05/2021 22:12:46 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

[lotharmat]

Upstream power looks too low - (34-51 I believe is the accepted range)

This looks like it could have led to the T3 timeouts which prevent the downstream channels working properly as they can't sync!

[John_GS]

Hi Ron-ski

Thanks for coming back to us.

The upstream levels are all out of spec which would require an engineer visit to the property to solve.

I'll PM you now to arrange.

Best,