Menu
Reply
  • 11
  • 1
  • 0
adampryor92
On our wavelength
130 Views
Message 1 of 3
Flag for a moderator

Unstable connection with 60% packet loss and lots of T3 timeouts - area 30

Hi all,

As the subject states, I'm experiencing a really unstable connection at the moment, with a BQM showing regularly around 60% packet loss and my network log showing a lot of T3 timeout errors, which is not only making online activities like gaming and voip calling very jittery, but also making general browsing a tedious and slow process. I had this problem before for around 2 months (from the moment I got my connection) and most of that time was spent getting engineers out and trying to escalate it to networks. I rang technical support last night and I've got an engineer coming out on Thursday afternoon, but I wanted to post here to see if it was possible to bring this to the attention of the community in case lots of people in my area (30) were experiencing this, or if it would be more relevant with this type of error to pass to networks. Last time I had this problem I ended up with about 4 or 5 engineer visits, but none of them were able to do anything (which wasn't their fault!) apart from pass the problem up as it was a network problem, so I just wanted to post this here to save time and potentially lots of engineer visits.

Here's a snapshot BQM graph:

My Broadband Ping - VM Unstable Connection

And here are my network logs (not formatted - sorry if it looks like a confusing mess!):

Network Log Date And Time Error Number Event Description

2016-12-02 12:18:29.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-02 12:24:35.0068010100DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-02 12:24:38.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-02 12:27:44.0068010100DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-02 12:28:07.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-02 12:29:18.0068010100DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-02 12:29:24.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-02 12:30:53.0068010100DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-02 12:31:07.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 00:02:01.0068000401ToD request sent - No Response received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-02 19:22:58.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 00:02:14.0068000401ToD request sent - No Response received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-02 20:13:57.0082000500Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-02 20:14:23.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 00:02:40.0068000100DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 00:02:45.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-02 20:27:05.0082000500Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-02 20:27:06.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-02 20:39:02.0082000500Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-02 20:39:03.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

If you need any other details just let me know.

Thanks,

Adam

0 Kudos
Reply
  • 11
  • 1
  • 0
adampryor92
On our wavelength
82 Views
Message 2 of 3
Flag for a moderator

Re: Unstable connection with 60% packet loss and lots of T3 timeouts - area 30

Just replying in case anyone comes across this thread in the future - the issue is resolved now and didn't need any action on my part. Haven't had an engineer visit yet either so I'm guessing it was something network related that just got fixed. Hope this helps anyone browsing in the future with a similar problem!

Here's a trace of what it looked like on the day the issue was resolved, in case anyone was wondering!

My Broadband Ping - VM Unstable Connection

0 Kudos
Reply
  • 3.88K
  • 120
  • 203
Forum Team (Retired) Adam_L
Forum Team (Retired)
63 Views
Message 3 of 3
Flag for a moderator

Re: Unstable connection with 60% packet loss and lots of T3 timeouts - area 30

Hi adampryor92, 

Thanks for the post! I am sorry to hear about your issues with your unstable connection. I apologise for any inconvenience caused.

I have run some checks from here and I noticed a very high number of T3 time outs inside the Hubs logs. An engineer will be required to attend and investigate this further for you.

I will send you a PM (purple envelope at the top) detailing what's required in order to proceed with making the booking. Please respond to me there and I'll get this all sorted for you.

Take care, 

Thanks, 

Adam.


Tech fan? Have you read our Digital life blog yet? Check it out


0 Kudos
Reply