Virgin Media Community

[PhilRJ]

Keep getting No ranging response errors and keeps affecting broadband speed.   Vriginmedia status shows no problems in area (but there was one earlier today).

Data below.

Many thanks in advance,

P

Network Log

Time Priority Description

02/02/2021 16:32:30	critical	No Ranging Response received - T3 time-out;CM-MAC=xxx;CMTS-MAC=xxx;CM-QOS=1.1;CM-VER=3.0;
02/02/2021 16:32:30	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=xxx;CMTS-MAC=xxx;CM-QOS=1.1;CM-VER=3.0;
02/02/2021 16:32:11	critical	No Ranging Response received - T3 time-out;CM-MAC=xxx;CMTS-MAC=xxx;CM-QOS=1.1;CM-VER=3.0;
02/02/2021 16:32:10	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=4xxx;CMTS-MAC=xxx;CM-QOS=1.1;CM-VER=3.0;

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

1	146750000	3.7	40	256 qam	2
2	138750000	4	40	256 qam	1
3	154750000	3.5	40	256 qam	3
4	162750000	3.4	40	256 qam	4
5	170750000	3.4	40	256 qam	5
6	178750000	3.2	40	256 qam	6
7	186750000	3.2	40	256 qam	7
8	194750000	3.2	40	256 qam	8
9	202750000	2.7	40	256 qam	9
10	210750000	2.5	38	256 qam	10
11	218750000	2	40	256 qam	11
12	226750000	2	38	256 qam	12
13	234750000	2	40	256 qam	13
14	242750000	1.7	38	256 qam	14
15	250750000	1.7	38	256 qam	15
16	258750000	1.5	40	256 qam	16
17	266750000	1.7	38	256 qam	17
18	274750000	1.7	38	256 qam	18
19	282750000	1.7	38	256 qam	19
20	290750000	1.7	38	256 qam	20
21	298750000	1.5	38	256 qam	21
22	306750000	1.7	40	256 qam	22
23	314750000	1.5	38	256 qam	23
24	322750000	1.2	38	256 qam	24

Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1	Locked	40.3	13	0
2	Locked	40.3	23	0
3	Locked	40.9	16	0
4	Locked	40.3	32	0
5	Locked	40.9	123	0
6	Locked	40.3	140	0
7	Locked	40.3	81	0
8	Locked	40.9	77	0
9	Locked	40.3	18	0
10	Locked	38.6	23	0
11	Locked	40.3	20	0
12	Locked	38.9	37	0
13	Locked	40.3	17	0
14	Locked	38.9	24	0
15	Locked	38.9	22	0
16	Locked	40.3	35	0
17	Locked	38.6	25	0
18	Locked	38.6	15	0
19	Locked	38.9	27	0
20	Locked	38.6	34	0
21	Locked	38.6	21	0
22	Locked	40.3	16	0
23	Locked	38.9	22	0
24	Locked	38.9	37	0

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

1	39400000	43.3	5120	64 qam	12
2	32600000	39.8	2560	64 qam	13
3	46200000	44.8	5120	64 qam	11
4	53700000	46	5120	64 qam	10

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1	ATDMA	0	0	56	0
2	ATDMA	0	0	77	0
3	ATDMA	0	0	56	0
4	ATDMA	0	0	44	0

[jbrennand · Accepted solution]

T3 timeouts are a worry. Can we see all of the Logs for the past week or so and in the meantime... if you haven’t already, set up a free and secure “Broadband Quality Monitor” to continually monitor the state of your connection and record any true network dropouts , latency issues, packet drops, etc - it will thus allow you to differentiate between those and simple wifi dropouts. It does it 24/7/365 and it keeps a visual record of any/all of your network disconnections, useful data to have to match to the Network logs (in your Hub settings) and also in discussions with VM - note it will take a few hours to start seeing a sensible picture - post up the “link” to the “share live graph” (as per instructions on the TB website) when it starts to develop.

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

[PhilRJ]

Thanks John,

Full log below.

Thanks for the tip re Broadband monitor - I will set it up. 

My hub is in router mode as I have an Asus router.  Wifi itself seems fine.  When I look into its log I can see the link drops out every few minutes (also posted a few lines below).  Both problems started at the same time as Virginmedia reporting a problem in the area so I'm assuming that they're related.  Virgin report that problem is cleared but issue still remains.

Phil

Network Log

Time Priority Description

02/02/2021 16:32:30	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/02/2021 16:32:30	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/02/2021 16:32:11	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/02/2021 16:32:10	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/02/2021 16:31:51	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/02/2021 16:31:50	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/02/2021 16:30:52	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/02/2021 16:30:51	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/02/2021 16:30:31	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/02/2021 16:30:30	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/02/2021 10:15:0	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/02/2021 10:14:40	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/02/2021 10:14:40	critical	Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/02/2021 10:14:20	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/02/2021 10:14:20	critical	Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/02/2021 10:14:0	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/02/2021 10:14:0	critical	Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:29:31	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:28:52	critical	DHCP FAILED - Request sent, No response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:26:59	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Example of Router Log as follows:

Feb 3 08:24:33 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link DOWN.
Feb 3 08:24:36 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link UP 100 mbps full duplex
Feb 3 08:25:09 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link DOWN.
Feb 3 08:25:12 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link UP 100 mbps full duplex
Feb 3 08:25:43 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link DOWN.
Feb 3 08:25:47 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link UP 100 mbps full duplex
Feb 3 08:26:23 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link DOWN.
Feb 3 08:26:26 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link UP 100 mbps full duplex

[PhilRJ]

Hi Again John,

So looking into router log further, I've now actually brought it down to the LAN connection to the TV (and not upstream to the Modem).  I suspect therefore that not much VirginMedia will want to look into now.

I just find it really weird that the problem occurred at precisely the same time that the T3 errors happened and Virgin declared the problem in my area.  Any thoughts?

My recent QM graph below in case interesting (I dont know how to interpret)

Best regards,   PJ

[PhilRJ]

Update:  Switched the TV off and then on again and the problem is gone.  I still think its an odd coincidence that it happened at the same time as the network problem but I don’t think I’ll ever get to the bottom of that.

Thanks again @John for looking into it.

PJ

[jbrennand · Accepted solution]

It may have just disconnected an in the time honoured CS way.... just needed a reboot/reconnection 🙂