on 16-04-2022 15:07
Hi All,
I've been reading about using my own router and whether to use modem or router mode regarding the UDP/Puma chipset issue. I get the odd period of lag, noticed while working from home on some teams calls.
I've just looked at the network log and see the following since install.
I'm not sure if this is normal and there is an accepted error 'tolerance' or does this need addressing?
Any info would be appreciated.
Network Log
Time Priority Description
16/04/2022 13:37:48 critical No Ranging Response received - T3 time-out;CM-MAC=**.**.**.**.**.**;CMTS-MAC=**.**.**.**.**.**;CM-QOS=1.1;CM-VER=3.0;
16/04/2022 13:23:15 notice LAN login Success;CM-MAC=**.**.**.**.**.**;CMTS-MAC=**.**.**.**.**.**;CM-QOS=1.1;CM-VER=3.0;
15/04/2022 16:28:5 critical No Ranging Response received - T3 time-out;CM-MAC=**.**.**.**.**.**;CMTS-MAC=**.**.**.**.**.**;CM-QOS=1.1;CM-VER=3.0;
15/04/2022 14:58:50 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**.**.**.**.**.**;CMTS-MAC=**.**.**.**.**.**;CM-QOS=1.1;CM-VER=3.0;
12/04/2022 06:40:40 critical No Ranging Response received - T3 time-out;CM-MAC=**.**.**.**.**.**;CMTS-MAC=**.**.**.**.**.**;CM-QOS=1.1;CM-VER=3.0;
12/04/2022 02:58:50 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**.**.**.**.**.**;CMTS-MAC=**.**.**.**.**.**;CM-QOS=1.1;CM-VER=3.0;
08/04/2022 18:20:0 critical No Ranging Response received - T3 time-out;CM-MAC=**.**.**.**.**.**;CMTS-MAC=**.**.**.**.**.**;CM-QOS=1.1;CM-VER=3.0;
08/04/2022 14:58:50 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**.**.**.**.**.**;CMTS-MAC=**.**.**.**.**.**;CM-QOS=1.1;CM-VER=3.0;
06/04/2022 20:54:20 critical No Ranging Response received - T3 time-out;CM-MAC=**.**.**.**.**.**;CMTS-MAC=**.**.**.**.**.**;CM-QOS=1.1;CM-VER=3.0;
06/04/2022 13:33:45 notice LAN login Success;CM-MAC=**.**.**.**.**.**;CMTS-MAC=**.**.**.**.**.**;CM-QOS=1.1;CM-VER=3.0;
05/04/2022 05:54:51 critical No Ranging Response received - T3 time-out;CM-MAC=**.**.**.**.**.**;CMTS-MAC=**.**.**.**.**.**;CM-QOS=1.1;CM-VER=3.0;
05/04/2022 02:58:50 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**.**.**.**.**.**;CMTS-MAC=**.**.**.**.**.**;CM-QOS=1.1;CM-VER=3.0;
04/04/2022 01:39:48 critical No Ranging Response received - T3 time-out;CM-MAC=**.**.**.**.**.**;CMTS-MAC=**.**.**.**.**.**;CM-QOS=1.1;CM-VER=3.0;
03/04/2022 18:18:33 notice LAN login Success;CM-MAC=**.**.**.**.**.**;CMTS-MAC=**.**.**.**.**.**;CM-QOS=1.1;CM-VER=3.0;
03/04/2022 01:10:47 critical No Ranging Response received - T3 time-out;CM-MAC=**.**.**.**.**.**;CMTS-MAC=**.**.**.**.**.**;CM-QOS=1.1;CM-VER=3.0;
02/04/2022 23:19:34 notice LAN login Success;CM-MAC=**.**.**.**.**.**;CMTS-MAC=**.**.**.**.**.**;CM-QOS=1.1;CM-VER=3.0;
01/04/2022 21:13:18 critical No Ranging Response received - T3 time-out;CM-MAC=**.**.**.**.**.**;CMTS-MAC=**.**.**.**.**.**;CM-QOS=1.1;CM-VER=3.0;
01/04/2022 14:58:50 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**.**.**.**.**.**;CMTS-MAC=**.**.**.**.**.**;CM-QOS=1.1;CM-VER=3.0;
29/03/2022 06:47:27 critical No Ranging Response received - T3 time-out;CM-MAC=**.**.**.**.**.**;CMTS-MAC=**.**.**.**.**.**;CM-QOS=1.1;CM-VER=3.0;
29/03/2022 02:58:50 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**.**.**.**.**.**;CMTS-MAC=**.**.**.**.**.**;CM-QOS=1.1;CM-VER=3.0;
on 16-04-2022 20:28
Please post your full stats.
on 16-04-2022 22:36
Here you go.
on 17-04-2022 00:42
Pretty atrocious stats as they stand, but they are accumulative since the hub was last power cycled which could well be a long time ago. So please turn off the hub for a few minutes and the power it on. After a few hours post the current set of stats and we can then see if they are recent and the increase rate.
on 17-04-2022 15:45
Ugh, ok, this is after a reboot 🙂
on 17-04-2022 17:29
Those stats are acceptable for a short timescale, but let’s see some more after say another 4 or 5 hours.
on 22-04-2022 19:38
A bit later but here are the stats now. More T3 timeouts but no Post RS Errors since rebooting the router.
on 23-04-2022 13:20
I would suggest your US channel are two low power wise. They should be above 34, ideally around 40.
Setup a BQM to monitor and record the state of your connection www.thinkbroadband.com/ping
I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more
Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks
on 23-04-2022 17:52
I’m thinking that you probably need a technician’s visit to check out your circuit.
Check with Area faults on 0800 561 0061 If you have a VM landline 150 this goes down to post code level. You could also try the web page http://www.virginmedia.com/servicechecker
VM will not dispatch any technicians when an area fault exists.
If no faults found:
Call Customer Services on 0345 454 1111/150 if you have a VM landline or wait a day or two for a VM staff member to get to your post.
on 25-04-2022 18:02
Hello @mjh17474,
Welcome back, thanks for posting.
I am sorry for the issues with your broadband.
Can you tell me if you are still needing help with this?
Many thanks,
New around here? To find out more about the Community check out our Getting Started guide