Forum Index | Search | Register (New User) | Login (Existing User) | Who's Online | FAQ | Main Site

General Discussion
  >> Broadband Quality Monitor Previous thread View all threads Next thread


Register (or login) on our website and you will not see this ad.


  Print Thread
Standard User MeInWales
(newbie) Sun 29-Aug-21 15:45:45
Print Post

Total packet loss but broadband still works most of the time


[link to this post] 		 
Hi all

I’m seeing big red areas on my BQM, sometimes during these episodes I can remain connected to the internet, at other times the green lights flash on my VM hub 3 and I have no connection.

Please could someone explain to me what is happening. Thanks in advance

https://www.thinkbroadband.com/broadband/monitoring/...
Standard User jchamier
(eat-sleep-adslguide) Sun 29-Aug-21 19:07:48
Print Post

Re: Total packet loss but broadband still works most of the


[re: MeInWales] [link to this post] 		 
In reply to a post by MeInWales:
I’m seeing big red areas on my BQM, sometimes during these episodes I can remain connected to the internet, at other times the green lights flash on my VM hub 3 and I have no connection.

It sounds as if your Hub3 is restarting with the green flashing light. This is not normal.

If you connect to the hub http://192.168.0.1 you should get a page asking for a password, and below that is a link for "check router status" click on this and then go to the "network log" tab and copy/paste into a new post.

21 years of broadband connectivity since 1999 trial - Live BQM
Standard User MeInWales
(newbie) Sun 29-Aug-21 19:47:11
Print Post

Re: Total packet loss but broadband still works most of the


[re: jchamier] [link to this post] 		 
Thanks for your reply.


29/08/2021 18:08:1 notice LAN login Success;CM-MAC=40:0d:10:68:25:03;CMTS-MAC=28:52:61:f0:a9:5d;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:03:58 critical No Ranging Response received - T3 time-out;CM-MAC=40:0d:10:68:25:03;CMTS-MAC=28:52:61:f0:a9:5d;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:03:58 critical Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=40:0d:10:68:25:03;CMTS-MAC=28:52:61:f0:a9:5d;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:02:42 critical No Ranging Response received - T3 time-out;CM-MAC=40:0d:10:68:25:03;CMTS-MAC=28:52:61:f0:a9:5d;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:02:42 critical Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=40:0d:10:68:25:03;CMTS-MAC=28:52:61:f0:a9:5d;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:55 critical No Ranging Response received - T3 time-out;CM-MAC=40:0d:10:68:25:03;CMTS-MAC=28:52:61:f0:a9:5d;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:55 critical Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=40:0d:10:68:25:03;CMTS-MAC=28:52:61:f0:a9:5d;CM-QOS=1.1;CM-VER=3.0;
29/08/2021 17:11:34 critical No Ranging Response received - T3 time-out;CM-MAC=40:0d:10:68:25:03;CMTS-MAC=28:52:61:f0:a9:5d;CM-QOS=1.1;CM-VER=3.0;
29/08/2021 17:11:34 critical Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=40:0d:10:68:25:03;CMTS-MAC=28:52:61:f0:a9:5d;CM-QOS=1.1;CM-VER=3.0;
29/08/2021 17:10:39 critical No Ranging Response received - T3 time-out;CM-MAC=40:0d:10:68:25:03;CMTS-MAC=28:52:61:f0:a9:5d;CM-QOS=1.1;CM-VER=3.0;
29/08/2021 17:10:39 critical Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=40:0d:10:68:25:03;CMTS-MAC=28:52:61:f0:a9:5d;CM-QOS=1.1;CM-VER=3.0;
29/08/2021 17:09:50 critical No Ranging Response received - T3 time-out;CM-MAC=40:0d:10:68:25:03;CMTS-MAC=28:52:61:f0:a9:5d;CM-QOS=1.1;CM-VER=3.0;
29/08/2021 17:09:50 critical Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=40:0d:10:68:25:03;CMTS-MAC=28:52:61:f0:a9:5d;CM-QOS=1.1;CM-VER=3.0;
29/08/2021 17:09:2 critical No Ranging Response received - T3 time-out;CM-MAC=40:0d:10:68:25:03;CMTS-MAC=28:52:61:f0:a9:5d;CM-QOS=1.1;CM-VER=3.0;
29/08/2021 17:09:2 critical Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=40:0d:10:68:25:03;CMTS-MAC=28:52:61:f0:a9:5d;CM-QOS=1.1;CM-VER=3.0;
29/08/2021 17:08:15 critical No Ranging Response received - T3 time-out;CM-MAC=40:0d:10:68:25:03;CMTS-MAC=28:52:61:f0:a9:5d;CM-QOS=1.1;CM-VER=3.0;
29/08/2021 17:08:15 critical Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=40:0d:10:68:25:03;CMTS-MAC=28:52:61:f0:a9:5d;CM-QOS=1.1;CM-VER=3.0;
29/08/2021 17:07:15 critical No Ranging Response received - T3 time-out;CM-MAC=40:0d:10:68:25:03;CMTS-MAC=28:52:61:f0:a9:5d;CM-QOS=1.1;CM-VER=3.0;
29/08/2021 17:07:15 critical Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=40:0d:10:68:25:03;CMTS-MAC=28:52:61:f0:a9:5d;CM-QOS=1.1;CM-VER=3.0;
29/08/2021 17:06:11 critical No Ranging Response received - T3 time-out;CM-MAC=40:0d:10:68:25:03;CMTS-MAC=28:52:61:f0:a9:5d;CM-QOS=1.1;CM-VER=3.0;


Register (or login) on our website and you will not see this ad.

Standard User jchamier
(eat-sleep-adslguide) Sun 29-Aug-21 19:53:06
Print Post

Re: Total packet loss but broadband still works most of the


[re: MeInWales] [link to this post] 		 
Looks as if you have a lot of T3 time outs.

I would contact Virgin Media support, you can do this on the community forums, and they will want this log.

https://community.virginmedia.com/

21 years of broadband connectivity since 1999 trial - Live BQM
Standard User MeInWales
(newbie) Sun 29-Aug-21 20:18:31
Print Post

Re: Total packet loss but broadband still works most of the


[re: jchamier] [link to this post] 		 
Thanks a lot, I appreciate your help
Standard User jchamier
(eat-sleep-adslguide) Sun 29-Aug-21 20:38:35
Print Post

Re: Total packet loss but broadband still works most of the


[re: MeInWales] [link to this post] 		 
The T3 time out is when your Hub is losing connection to the rest of the virgin network and this is likely causing your outages (red bars) on the BQM.

You probably need your power levels checked by a technician.

21 years of broadband connectivity since 1999 trial - Live BQM
  Print Thread

Previous thread View all threads Next thread
Jump to