26-05-2022 13:26 - edited 26-05-2022 13:27
Hello there. For the last month we are experiencing broadband outages and drops everyday.
Usually while checking Hub logs quickly I can notice a clear connection between Downstream Channels power drops and RCS errors appearing, however signal then gets back to normal until next outage. We've already had 3 engineer visits (last one yesterday, 4-7pm, said it was fine).
And after the last guy left we've experienced outage again around 10pm.
Outages are not so long, but extremely annoying because they are enough to disconnect everything.
BQM link:
Last outages happened just an hour and 30 minutes ago.
Answered! Go to Answer
on 09-06-2022 20:03
Today was totally unbearable to work overall.
Connection gets worse and worse
on 09-06-2022 21:12
That is just ridiculous, jumping up and down like crazy. Also for some reason service check still reminds me of maintenance which should've been done more than 12 hours ago.
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 46199986 | 38.5 | 5120 | 64 qam | 3 |
2 | 39400021 | 35.3 | 5120 | 64 qam | 4 |
3 | 53699974 | 45.3 | 5120 | 64 qam | 2 |
4 | 60300000 | 38 | 5120 | 64 qam | 1 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 3 | 0 |
3 | ATDMA | 0 | 0 | 1 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
on 10-06-2022 10:06
@Carley_S
So as you can see, nothing has changed unless worsened
on 10-06-2022 11:31
So for now I've again booked a tech visit on closest date possible (got redirected there after service check). This is my 4th tech visit, hope he won't just ignore my attempts to show logs/data that could indicate the possible problems like the last tech guy.
on 12-06-2022 12:00
And whilst waiting for tech, 12th of June and this again
on 12-06-2022 12:18
Also my today's error lags is very different to what I see usually, does this mean that Hub is dying?
Time Priority Description
12/06/2022 10:37:50 | notice | NOTICE ATOM is restarted due to Kernel/oops panic as part of Self Healing Mechanism ;X;CM-QOS=1.1;CM-VER=3.0; |
12/06/2022 10:37:36 | critical | No Ranging Response received - T3 time-out;X;CM-QOS=1.1;CM-VER=3.0; |
12/06/2022 10:37:35 | critical | Unicast Ranging Received Abort Response - initializing MAC;X;CM-QOS=1.1;CM-VER=3.0; |
12/06/2022 10:37:31 | notice | NOTICE ATOM is restarted due to RPC timeout as part of Self Healing Mechanism;X;CM-QOS=1.1;CM-VER=3.0; |
12/06/2022 10:35:56 | critical | No Ranging Response received - T3 time-out;X;CM-QOS=1.1;CM-VER=3.0; |
12/06/2022 10:35:56 | critical | Unicast Ranging Received Abort Response - initializing MAC;X;CM-QOS=1.1;CM-VER=3.0; |
12/06/2022 10:34:36 | critical | No Ranging Response received - T3 time-out;X;CM-QOS=1.1;CM-VER=3.0; |
12/06/2022 10:34:36 | critical | Unicast Ranging Received Abort Response - initializing MAC;X;CM-QOS=1.1;CM-VER=3.0; |
12/06/2022 10:33:16 | critical | No Ranging Response received - T3 time-out;x;CM-QOS=1.1;CM-VER=3.0; |
12/06/2022 10:33:16 | critical | Unicast Ranging Received Abort Response - initializing MAC;x;CM-QOS=1.1;CM-VER=3.0; |
12/06/2022 10:31:56 | critical | No Ranging Response received - T3 time-out;x;CM-QOS=1.1;CM-VER=3.0; |
12/06/2022 10:31:56 | critical | Unicast Ranging Received Abort Response - initializing MAC;X;CM-QOS=1.1;CM-VER=3.0; |
12/06/2022 10:30:36 | critical | No Ranging Response received - T3 time-out;X;CM-QOS=1.1;CM-VER=3.0; |
12/06/2022 10:30:36 | critical | Unicast Ranging Received Abort Response - initializing MAC;X;CM-QOS=1.1;CM-VER=3.0; |
12/06/2022 10:29:16 | critical | No Ranging Response received - T3 time-out;x;CM-QOS=1.1;CM-VER=3.0; |
12/06/2022 10:29:16 | critical | Unicast Ranging Received Abort Response - initializing MAC;x;CM-QOS=1.1;CM-VER=3.0; |
12/06/2022 10:27:57 | critical | No Ranging Response received - T3 time-out;x;CM-QOS=1.1;CM-VER=3.0; |
12/06/2022 10:27:56 | critical | Unicast Ranging Received Abort Response - initializing MAC;x;CM-QOS=1.1;CM-VER=3.0; |
12/06/2022 10:27:20 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;x;CM-QOS=1.1;CM-VER=3.0; |
12/06/2022 10:27:20 | critical | Ranging Request Retries exhausted;xCM-QOS=1.1;CM-VER=3.0; |
on 12-06-2022 12:31
Hi CIMcGee,
Thank you for getting back in touch with us here on the Community.
I am sorry to hear the problem is ongoing but I am happy you have been able to schedule the visit with the team.
Please do let us know how it all goes and if you require any further assistance.
Thank you,
on 12-06-2022 12:39
Thanks for response. Will again post here after the tech visit and/or if anyhting like these log changes occurs
on 12-06-2022 23:48
So just wanted to share that graph, totally not the worst, but I've never been experiencing such a heavy and frequent packet loss in my life.
this huge red line was when hub probably rebooted itself due to "kernel panic"
on 13-06-2022 11:22
So the tech guy was superb this time, amazing service. However that "ghost" of intermittent signal was not present at that time, thus he decided to book me a cable change (the one that goes from street cab to our property). Will have to wait for it again.