Virgin Media Community

[peterUK1]

Hi,

My internet keeps dropping out and the hub has a green flashing light.  It's been doing this throughout the day.

Logs:

Network Log

Time Priority Description

18/02/2022 13:43:42	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/02/2022 20:25:28	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/02/2022 08:38:48	notice	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/02/2022 08:38:48	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/02/2022 22:37:28	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/02/2022 16:52:32	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/02/2022 16:25:4	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/02/2022 20:05:23	notice	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/02/2022 20:05:23	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/02/2022 19:04:23	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/02/2022 08:05:23	notice	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/02/2022 08:05:23	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/02/2022 21:27:0	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/02/2022 06:04:49	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/02/2022 20:05:23	notice	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/02/2022 20:05:23	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/02/2022 06:11:58	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/02/2022 08:05:23	notice	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/02/2022 08:05:23	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/02/2022 09:49:33	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

[peterUK1]

Cable Modem StatusItem Status Comments

Acquired Downstream Channel (Hz)	331000000	Locked
Ranged Upstream Channel (Hz)	46200000	Locked
Provisioning State	Online

[peterUK1]

Downstream bonded channels

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

1	331000000	1.2	38	256 qam	25
2	235000000	2	38	256 qam	13
3	243000000	2	38	256 qam	14
4	251000000	1.7	38	256 qam	15
5	259000000	1.7	37	256 qam	16
6	267000000	1.7	38	256 qam	17
7	275000000	1.9	38	256 qam	18
8	283000000	1.7	38	256 qam	19
9	291000000	1.7	38	256 qam	20
10	299000000	1.7	37	256 qam	21
11	307000000	1.7	38	256 qam	22
12	315000000	1.4	38	256 qam	23
13	323000000	1.2	38	256 qam	24
14	339000000	1	38	256 qam	26
15	347000000	1	38	256 qam	27
16	355000000	0.9	38	256 qam	28
17	363000000	0.9	38	256 qam	29
18	371000000	0.7	38	256 qam	30
19	379000000	0.9	38	256 qam	31
20	387000000	0.7	38	256 qam	32
21	395000000	1	38	256 qam	33
22	403000000	0.9	38	256 qam	34
23	411000000	1	38	256 qam	35
24	419000000	0.7	38	256 qam	36

Downstream bonded channels

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

1	Locked	38.6	30	0
2	Locked	38.6	33	0
3	Locked	38.9	49	0
4	Locked	38.6	54	0
5	Locked	37.3	49	0
6	Locked	38.6	36	0
7	Locked	38.6	43	0
8	Locked	38.9	39	0
9	Locked	38.6	41	0
10	Locked	37.6	44	0
11	Locked	38.6	39	0
12	Locked	38.6	37	0
13	Locked	38.6	48	1
14	Locked	38.6	58	0
15	Locked	38.9	33	13
16	Locked	38.6	26	0
17	Locked	38.6	28	0
18	Locked	38.9	28	0
19	Locked	38.6	38	0
20	Locked	38.6	58	0
21	Locked	38.9	33	0
22	Locked	38.9	35	0
23	Locked	38.9	24	0
24	Locked	38.9	28	0

[peterUK1]

Upstream bonded channels

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

1	46200000	36.5	5120	64 qam	3
2	32600000	36.5	5120	64 qam	5
3	39400007	37.5	5120	64 qam	4
4	53699986	38	5120	64 qam	2

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1	ATDMA	0	0	2	0
2	ATDMA	0	0	1	0
3	ATDMA	0	0	4	0
4	ATDMA	0	0	0	0

[peterUK1]

General Configuration

Network access	Allowed
Maximum Number of CPEs	1
Baseline Privacy	Enabled
DOCSIS Mode	Docsis30
Config file	A,.iyewrkldJKDHSUBsgvca69

Primary Downstream Service Flow

SFID	18172
Max Traffic Rate	575000000
Max Traffic Burst	42600
Min Traffic Rate	0

Primary Upstream Service Flow

SFID	24556
Max Traffic Rate	38520000
Max Traffic Burst	42600
Min Traffic Rate	0
Max Concatenated Burst	16320
Scheduling Type	BestEffort

[peterUK1]

Any idea on how to fix?

[peterUK1]

[peterUK1]

Here is the actual tracker.  Lots of latency

[Hayley_S]

Hello @peterUK1,

Welcome back, thanks for posting.

I am sorry for any issues with your broadband.

Can you please tell me if you are having a more stable connection at the moment?

Many thanks,

[peterUK1]

Hi - sorry for not responding yesterday @Hayley_S - it went off again yesterday briefly.  

It's strange but sometimes it goes off and we have nothing in the router logs.