Menu
Reply
Highlighted
  • 7
  • 0
  • 0
Tuning in
153 Views
Message 1 of 11
Flag for a moderator

Repeated drop outs on wired broadband, T3 and T4 times outs

Recently upgraded to broadband 350, and the newer 4.0 hub. Since doing so Hub keeps dropping out connection with reported T3 and T4 timeouts. Have rebooted the router quite a few times, checked through all settings and completed a factory reset. Also tried different ethernet cables, all Cat5 rated, even run a signal test through all cat5's. Simple set up, laptop to cat5 to hub. Nothing else that would interfere. It does the same when connected via wifi except its a little more forgiving.

Any suggestions? Most of these issues that I've seen had to be fixed at the junction box by virgin themselves, but I'm open to ideas while I wait for virgin admin/engineer to notice this post.

0 Kudos
Reply
Highlighted
  • 7
  • 0
  • 0
Tuning in
150 Views
Message 2 of 11
Flag for a moderator

Re: Repeated drop outs on wired broadband, T3 and T4 times outs

TimePriorityDescription
12/11/2020 17:37ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/11/2020 04:10criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/11/2020 13:49ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/11/2020 12:06criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/11/2020 01:49ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/11/2020 01:15noticeSW download Successful - Via NMS
05/11/2020 01:14noticeSW Download INIT - Via NMS
01/11/2020 14:46ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/10/2020 10:14criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/10/2020 02:46ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/10/2020 02:46ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/10/2020 02:11criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/10/2020 02:11criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/10/2020 02:11criticalReceived 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;
29/10/2020 02:11criticalReceived 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;
29/10/2020 02:05Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/10/2020 02:05Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/10/2020 02:05criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/10/2020 02:05criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/10/2020 02:05Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/10/2020 02:05criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/10/2020 02:05Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/10/2020 02:05criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/10/2020 03:45criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/10/2020 03:45criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/10/2020 02:59ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/10/2020 02:59ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/10/2020 00:09ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/10/2020 00:09ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/10/2020 22:14criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/10/2020 15:38ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/10/2020 13:07criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/10/2020 04:17ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/10/2020 15:05criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/10/2020 17:06ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/10/2020 13:36ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/10/2020 10:48criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/10/2020 13:02ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/10/2020 16:43noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/10/2020 06:06ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/10/2020 03:22ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/10/2020 02:59criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/10/2020 19:09ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/10/2020 19:09ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/10/2020 14:42criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/10/2020 14:42criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/10/2020 08:11ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/10/2020 08:11ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/10/2020 23:49ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/10/2020 23:49ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/10/2020 18:52ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/10/2020 18:52ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/10/2020 10:14criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/10/2020 08:08noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/10/2020 08:08noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
Tags (1)
0 Kudos
Reply
Highlighted
  • 24.66K
  • 1.42K
  • 3.14K
Alessandro Volta
122 Views
Message 3 of 11
Flag for a moderator
Helpful Answer

Re: Repeated drop outs on wired broadband, T3 and T4 times outs

Post the upstream and downstream logs too


*****
If you think my answer has helped - please provide me with a Kudos rating and mark as Helpful Answer!!
I do not work for Virgin Media - all opinions expressed are of my own and all answers are provided from my own and past experiences.
Office 365, Dynamics CRM and Cloud Computing Jedi
Highlighted
  • 7
  • 0
  • 0
Tuning in
114 Views
Message 4 of 11
Flag for a moderator

Re: Repeated drop outs on wired broadband, T3 and T4 times outs

Upstream bonded channels

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

14620000045512064 qam3
26030001045.5512064 qam1
35370000045.3512064 qam2
43940001045512064 qam4



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0020
2ATDMA0030
3ATDMA0000
4ATDMA0010
Tags (1)
0 Kudos
Reply
Highlighted
  • 7
  • 0
  • 0
Tuning in
113 Views
Message 5 of 11
Flag for a moderator

Re: Repeated drop outs on wired broadband, T3 and T4 times outs

Downstream bonded channels

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

12030000001.940256 qam9
22110000001.940256 qam10
32190000001.740256 qam11
42270000001.740256 qam12
52350000001.540256 qam13
62430000001.440256 qam14
72510000001.240256 qam15
82590000000.940256 qam16
92670000001.540256 qam17
102750000001.540256 qam18
11283000000240256 qam19
122910000002.240256 qam20
132990000002.540256 qam21
143070000002.740256 qam22
153150000002.940256 qam23
16323000000340256 qam24
17331000000340256 qam25
183390000003.240256 qam26
193470000003.240256 qam27
203550000003.440256 qam28
213630000003.240256 qam29
223710000003.540256 qam30
233790000002.940256 qam31
243870000002.540256 qam32



Downstream bonded channels

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

1Locked40.3560
2Locked40.3300
3Locked40.3310
4Locked40.9330
5Locked40.9980
6Locked40.3510
7Locked40.3540
8Locked40.3310
9Locked40.33715
10Locked40.3810
11Locked40.31010
12Locked40.3720
13Locked40.3500
14Locked40.9200
15Locked40.32630
16Locked40.9610
17Locked40.9530
18Locked40.3740
19Locked40.3330
20Locked40.9440
21Locked40.3610
22Locked40.3700
23Locked40.3610
24Locked40.36355
Tags (1)
0 Kudos
Reply
Highlighted
  • 24.66K
  • 1.42K
  • 3.14K
Alessandro Volta
85 Views
Message 6 of 11
Flag for a moderator

Re: Repeated drop outs on wired broadband, T3 and T4 times outs

When was the hub last rebooted?


*****
If you think my answer has helped - please provide me with a Kudos rating and mark as Helpful Answer!!
I do not work for Virgin Media - all opinions expressed are of my own and all answers are provided from my own and past experiences.
Office 365, Dynamics CRM and Cloud Computing Jedi
0 Kudos
Reply
Highlighted
  • 7
  • 0
  • 0
Tuning in
45 Views
Message 7 of 11
Flag for a moderator

Re: Repeated drop outs on wired broadband, T3 and T4 times outs

Last weekend, and a couple of times during the week leading up to this weekend. I've switched out the ethernet cables twice to see if I had any faulty cables as well, tested all cables with a signal meter as well. I'll reboot it again now, but I'm sure it won't help.

Any suggestions welcome though! 🙂

0 Kudos
Reply
Highlighted
  • 17.35K
  • 1.82K
  • 3.02K
Very Insightful Person
Very Insightful Person
43 Views
Message 8 of 11
Flag for a moderator

Re: Repeated drop outs on wired broadband, T3 and T4 times outs

if you haven’t already, set up a free “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” (as per instructions on the TB website) when you have the first 24h period.

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

--------------------
John
--------------------

My services: HD TV on VIP (+ Sky Sports & Movies & BT sport), x3 V6 boxes (1 wired 2 WiFi,) SH2 in modem mode with Airport Extreme Router. On VIVID200, Talk Anytime Phone, x2 Mobile SIM only iPhones.
0 Kudos
Reply
Highlighted
  • 7
  • 0
  • 0
Tuning in
38 Views
Message 9 of 11
Flag for a moderator

Re: Repeated drop outs on wired broadband, T3 and T4 times outs

You have to setup an account and register to use it, I'm not overly keen on doing so. As it is I had to create an account just to access VM Community which baffkes considering I'm already a customer and have two logins! Would packet capture from something like wireshark over a reasonable period not be better?

PS. Rebooted the router 3 times now, 2 software reboots and one hardware with no improvement, still doing the same dropout. Note this still happens both on wifi and on wired connections. I've also run the hub's diagnostics which didn't show anything useful apart from complaining that my home phone can't be accessed, but thats not connected as it's not with Virgin.

0 Kudos
Reply
Highlighted
  • 7
  • 0
  • 0
Tuning in
37 Views
Message 10 of 11
Flag for a moderator

Re: Repeated drop outs on wired broadband, T3 and T4 times outs

You have to setup an account and register to use it, I'm not overly keen on doing so. As it is I had to create an account just to access VM Community which baffles considering I'm already a customer and have two logins! Would packet capture from something like wireshark over a reasonable period not be better?

PS. Rebooted the router 3 times now, 2 software reboots and one hardware with no improvement, still doing the same dropout. Note this still happens both on wifi and on wired connections. I've also run the hub's diagnostics which didn't show anything useful apart from complaining that my home phone can't be accessed, but thats not connected as it's not with Virgin.

0 Kudos
Reply