on 14-05-2018 22:13
Every day or two pretty much my internet goes down.
The logs on the router show this: How do I fix this?
2018-05-04 15:55:41.00 | 82000300 | Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
2018-05-04 15:55:41.00 | 82000600 | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
2018-05-04 15:55:42.00 | 82000200 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
2018-05-04 15:59:41.00 | 82000400 | Received 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; |
2018-05-04 16:00:18.00 | 82000200 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
2018-05-06 12:21:17.00 | 82000400 | Received 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; |
2018-05-06 12:22:11.00 | 82000200 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
2018-05-08 14:41:59.00 | 82000300 | Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
2018-05-08 14:41:59.00 | 82000600 | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
2018-05-08 14:45:58.00 | 82000400 | Received 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; |
2018-05-08 16:17:08.00 | 82000200 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
2018-05-10 18:35:52.00 | 82000400 | Received 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; |
2018-05-11 02:21:46.00 | 82000200 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
2018-05-12 23:10:48.00 | 82000400 | Received 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; |
2018-05-12 23:11:19.00 | 82000200 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
2018-05-14 20:48:46.00 | 82000300 | Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
2018-05-14 20:48:46.00 | 82000600 | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
2018-05-14 20:48:46.00 | 82000200 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
2018-05-14 20:52:46.00 | 82000400 | Received 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; |
2018-05-14 20:53:22.00 | 82000200 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 15-05-2018 17:04
Go into your hub again and post the up/down stream stats.
on 16-05-2018 07:50
Sure - here it is (thanks for getting back to me):
Downstream bonded channels | Channel Frequency(Hz) | Power(dBmV) | SNR(dB) | Modulation | Channel ID |
1 | 298750000 | 0 | 40.9 | 256 qam | 21 |
2 | 322750000 | 0 | 40.3 | 256 qam | 24 |
3 | 314750000 | 0 | 40.9 | 256 qam | 23 |
4 | 306750000 | 0 | 40.3 | 256 qam | 22 |
5 | 290750000 | 0.4 | 40.3 | 256 qam | 20 |
6 | 282750000 | 0.4 | 40.9 | 256 qam | 19 |
7 | 274750000 | 0 | 40.3 | 256 qam | 18 |
8 | 266750000 | 0.2 | 40.3 | 256 qam | 17 |
9 | 258750000 | 0.5 | 40.3 | 256 qam | 16 |
10 | 250750000 | 0.5 | 40.3 | 256 qam | 15 |
11 | 242750000 | 0.2 | 40.3 | 256 qam | 14 |
12 | 234750000 | 0.2 | 40.3 | 256 qam | 13 |
13 | 226750000 | 0.7 | 40.3 | 256 qam | 12 |
14 | 218750000 | 0.9 | 40.3 | 256 qam | 11 |
15 | 210750000 | 1.2 | 40.3 | 256 qam | 10 |
16 | 202750000 | 1.5 | 40.9 | 256 qam | 9 |
17 | 194750000 | 2 | 40.9 | 256 qam | 8 |
18 | 186750000 | 2.4 | 40.3 | 256 qam | 7 |
19 | 178750000 | 2.5 | 40.9 | 256 qam | 6 |
20 | 170750000 | 2.7 | 40.9 | 256 qam | 5 |
21 | 162750000 | 2.9 | 40.9 | 256 qam | 4 |
22 | 154750000 | 3 | 40.3 | 256 qam | 3 |
23 | 146750000 | 3.2 | 40.9 | 256 qam | 2 |
24 | 138750000 | 3 | 40.9 | 256 qam | 1 |
Upstream bonded channels | Frequency(Hz) | Mode | Power(dBmV) | Modulation | Channel Bandwidth(Hz) | Symbol Rate (ksps) |
54 | 60300000 | ATDMA | 47 | 16 qam | 6400000 | 5120 |
53 | 53700000 | ATDMA | 47 | 16 qam | 6400000 | 5120 |
on 18-05-2018 12:10
Hi Tudor - do you have any advice for what to do?
on 18-05-2018 12:42
Your logs in your first post are clearly showing the connection dropping between the Hub and VM's servers, it does look like an upstream problem, with the accompanying T3 errors.
You will need to contact VM for resolution, either by waiting here about a week until a VM Forum Team Member picks up the thread, or give them a call on 150 from a VM line or 0345 454 1111 for a quicker response.
Your power levels and downstream SNR are fine BTW.
on 18-05-2018 13:45
great - I will in the first case try and wait for them to look here (as I have all the logs already!).
Thanks for your help!
on 23-05-2018 15:53
Hey dylanuk1,
Thanks for getting in touch and Welcome to the Community! 😄
I'm sorry to hear you've been having trouble with your Broadband connection recently.
I've taken a look at your account and can see that we have an open SNR fault ticket in your area (Ref:F006230406) and the review date is currently set for 5pm today.
Let us know if you're still having trouble this evening and we can take another look.
Take care
Rebecca
New around here? Find out more about the Community by checking our "Getting started guide"
on 04-06-2018 07:28
on 13-06-2018 21:40
Hi dylanuk1,
Thanks for getting back in touch, things seem to be ok from this side.
Fault ref F006230406 has now been resolved.
How are things looking for you now? If you are still having trouble let us know and we will be happy to take a look for you.
All the best
Emma
on 17-06-2018 15:20
Hi,
It is still happening every couple of days 😞
Could you take a look?
latest logs:
2018-06-14 14:51:00.00 82000400 Received 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;
2018-06-14 14:51:52.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-06-16 12:42:35.00 82000400 Received 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;
2018-06-16 12:43:18.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-06-17 14:11:54.00 82000300 Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-06-17 14:11:54.00 82000600 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-06-17 14:11:54.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;