Virgin Media Community

[tonycv51]

Well I did have a good quality connection, just plagued by SH3 Puma 6 latency for which i was impatiently waiting for the new firmware.  Just over a week ago there must have been some network changes as got a new IP and the BQM now has packet loss each and every day with much more variable latency, so don't think the firmware fix will now cure all my connection problems on my premium superfast broadband.....

Previous BQM Old IP Address

New IP Address BQM 

[tonycv51]

1	298750000	3.7	40.3	256 qam	21
2	434750000	4.3	40.9	256 qam	29
3	426750000	4.4	40.9	256 qam	28
4	418750000	4.1	40.9	256 qam	27
5	410750000	4.5	40.3	256 qam	26
6	402750000	4.5	40.3	256 qam	25
7	322750000	4	40.9	256 qam	24
8	314750000	4	40.9	256 qam	23
9	306750000	3.7	40.3	256 qam	22
10	290750000	3.5	40.3	256 qam	20
11	282750000	3.4	40.9	256 qam	19
12	274750000	3.2	40.9	256 qam	18
13	266750000	3.2	40.9	256 qam	17
14	258750000	3.4	40.9	256 qam	16
15	250750000	3.5	40.3	256 qam	15
16	242750000	3.7	40.9	256 qam	14
17	234750000	3.7	40.9	256 qam	13
18	226750000	3.7	40.3	256 qam	12
19	218750000	3.5	40.9	256 qam	11
20	210750000	3.5	40.9	256 qam	10
21	202750000	3.2	40.9	256 qam	9
22	194750000	3.2	40.3	256 qam	8
23	186750000	3.2	40.3	256 qam	7
24	178750000	3	40.3	256 qam	6

Upstream bonded channelsChannel ID Frequency(Hz) Mode Power(dBmV) Modulation Channel Bandwidth(Hz) Symbol Rate (ksps)

12	25800000	ATDMA	40.5	32 qam	6400000	5120
11	32600000	ATDMA	40.5	64 qam	6400000	5120
10	39400000	ATDMA	40.5	64 qam	6400000	5120
9	46200000	ATDMA	40.5	64 qam	6400000	5120

Network LogDate And TimeError NumberEvent Description2018-06-13 18:04:50.0082000500Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;2018-06-13 18:04:50.0082000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;2018-06-13 18:05:09.0082000500Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;2018-06-13 18:05:20.0082000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;2018-06-13 18:06:09.0082000500Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;2018-06-13 18:06:09.0082000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;2018-06-13 18:06:29.0082000500Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;2018-06-13 18:06:39.0082000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;2018-06-13 18:07:29.0082000500Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;2018-06-13 18:07:29.0082000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;2018-06-13 18:07:49.0082000500Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;2018-06-13 18:07:59.0082000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;2018-06-13 18:08:49.0082000500Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;2018-06-13 18:08:49.0082000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;2018-06-13 18:09:09.0082000500Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;2018-06-13 18:09:19.0082000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;2018-06-13 18:10:09.0082000500Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;2018-06-13 18:10:09.0082000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;2018-06-13 18:10:29.0082000500Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;2018-06-13 18:10:39.0082000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

One of the upstreams is a probem ?

[tonycv51]

T3/T4 timeouts continue at about 1 a minute  - upstream flapping between 64 and 32 QAM.....

Network LogDate And Time Error Number Event Description

2018-06-13 18:56:45.00	82000500	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-06-13 18:56:45.00	82000400	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-06-13 18:57:05.00	82000500	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-06-13 18:57:15.00	82000400	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-06-13 18:58:04.00	82000500	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-06-13 18:58:05.00	82000400	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-06-13 18:58:24.00	82000500	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-06-13 18:58:34.00	82000400	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-06-13 18:59:24.00	82000500	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-06-13 18:59:24.00	82000400	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-06-13 18:59:44.00	82000500	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-06-13 18:59:54.00	82000400	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-06-13 19:00:44.00	82000300	Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-06-13 19:00:44.00	82000600	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-06-13 19:00:44.00	82000400	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-06-13 19:01:04.00	82000300	Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-06-13 19:01:04.00	82000600	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-06-13 19:01:14.00	82000400	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-06-13 19:02:04.00	82000500	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-06-13 19:02:04.00	82000400	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

[Nat_J]

Sorry to hear about the connection trouble experienced tonycv51, 

I've located your account details and everything appears to be within range from this end. 

How have things been for you since posting?

Nat_J

[tonycv51]

Nat

The T3 and T4's have died down from 1 a minute to 1 or 2 a day more recently, but speeds very inconsistent and line quality variable shown in differeny sets of tests from Saturday and today Tuesday.  Just web browsing on Saturday was like wading through treacle.  Equivalent tests have always been in excess of 100 even when not hitting 200 I'm on.  I don't have time today do any tests connected directly to the modem but will hopefully be able to tomorrow

Tony

Saturday

Tuesday

 

[Jen_A]

Hi tonycv51,

Glad to see the Timeouts at least have abated. I'm seeing only a few for the past 6 days and there are no errors on the network segment so that's looking good.

However, fault ref: F005783851 will be impacting on peak time speeds and requires a network upgrade to resolve.

I have noted this on your account, for reference should you call in. If you would like us to check for updates please post on here and we'll take a look.

Kind regards,

[tonycv51]

---

@Jen_A wrote:However, fault ref: F005783851 will be impacting on peak time speeds and requires a network upgrade to resolve.

---

Has this fault ref been fixed yet ?

[Samantha_L]

Afternoon tonycv51,

Thanks for posting back here.

In regards to fault reference F005783851, this is now showing as closed.

Have you noticed an improvement with the connection at all?

Speak soon

Sam

[tonycv51]

Samantha

thanks for letting me know - modem logs show 1 or 2 T3 timeouts a day, and sometimes clear for a few days so seems pretty stable now thanks.  Speed is good i.e. 84Mbps single thread, 208Mbps multi thread just now on a Saturday lunchtime, but BQM still spikes at peak times and latency spikes to about 200ms in download tests (bufferbloat score of C), which isn't as clean as it was earlier in the year before the network change in my area and new IP address that triggered this post, when bufferbloat score was typically A grade