a week ago
I've been having intermittent Internet over ethernet and WiFi. I have been getting this issue intermittently everyday for around three weeks. I have checked all Coax connections and reseated them which helped a little with the RS errors, rebooted the Hub3, but the underlying problem still persists. anyone have any ideas? All help greatly appreciated.
IGNORE the 23 minute outtage at 01.03am - That was me checking coax connections.
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 323000000 | 1.2 | 40 | 256 qam | 24 |
2 | 139000000 | 2.9 | 40 | 256 qam | 1 |
3 | 147000000 | 2.7 | 38 | 256 qam | 2 |
4 | 155000000 | 2.5 | 40 | 256 qam | 3 |
5 | 163000000 | 2.5 | 40 | 256 qam | 4 |
6 | 171000000 | 2.7 | 40 | 256 qam | 5 |
7 | 179000000 | 2.5 | 40 | 256 qam | 6 |
8 | 187000000 | 2.7 | 38 | 256 qam | 7 |
9 | 195000000 | 2.7 | 40 | 256 qam | 8 |
10 | 203000000 | 2.7 | 40 | 256 qam | 9 |
11 | 211000000 | 2.5 | 40 | 256 qam | 10 |
12 | 219000000 | 2.5 | 36 | 256 qam | 11 |
13 | 227000000 | 2.4 | 38 | 256 qam | 12 |
14 | 235000000 | 2.2 | 40 | 256 qam | 13 |
15 | 243000000 | 2 | 40 | 256 qam | 14 |
16 | 251000000 | 1.9 | 40 | 256 qam | 15 |
17 | 259000000 | 1.5 | 40 | 256 qam | 16 |
18 | 267000000 | 1.5 | 40 | 256 qam | 17 |
19 | 275000000 | 1.4 | 40 | 256 qam | 18 |
20 | 283000000 | 1 | 40 | 256 qam | 19 |
21 | 291000000 | 1 | 40 | 256 qam | 20 |
22 | 299000000 | 1 | 40 | 256 qam | 21 |
23 | 307000000 | 0.7 | 40 | 256 qam | 22 |
24 | 315000000 | 1 | 40 | 256 qam | 23 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 40.9 | 5 | 0 |
2 | Locked | 40.3 | 56 | 0 |
3 | Locked | 40.9 | 5 | 0 |
4 | Locked | 40.3 | 27 | 0 |
5 | Locked | 40.9 | 13 | 0 |
6 | Locked | 40.3 | 10 | 0 |
7 | Locked | 40.3 | 6 | 0 |
8 | Locked | 40.3 | 6 | 0 |
9 | Locked | 40.9 | 7 | 0 |
10 | Locked | 40.3 | 5 | 0 |
11 | Locked | 40.3 | 10 | 0 |
12 | Locked | 36.6 | 6 | 0 |
13 | Locked | 38.6 | 12 | 0 |
14 | Locked | 40.3 | 186 | 9 |
15 | Locked | 40.9 | 97 | 0 |
16 | Locked | 40.3 | 7 | 0 |
17 | Locked | 40.3 | 11 | 0 |
18 | Locked | 40.3 | 7 | 0 |
19 | Locked | 40.3 | 5 | 0 |
20 | Locked | 40.3 | 5 | 0 |
21 | Locked | 40.3 | 27 | 0 |
22 | Locked | 40.3 | 7 | 0 |
23 | Locked | 40.3 | 6 | 0 |
24 | Locked | 40.3 | 7 | 0 |
a week ago
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 32599991 | 32 | 5120 | 64 qam | 13 |
2 | 23600000 | 32 | 5120 | 64 qam | 14 |
3 | 39400000 | 32 | 5120 | 64 qam | 12 |
4 | 46199988 | 32 | 5120 | 64 qam | 11 |
5 | 53699998 | 32 | 5120 | 64 qam | 10 |
6 | 60299976 | 32 | 5120 | 64 qam | 9 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 1 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
5 | ATDMA | 0 | 0 | 0 | 0 |
6 | ATDMA | 0 | 0 | 0 | 0 |
a week ago
Network access | Allowed |
Maximum Number of CPEs | 1 |
Baseline Privacy | Enabled |
DOCSIS Mode | Docsis30 |
Config file | a69834ncxv9873254k;fg87ds |
SFID | 22212 |
Max Traffic Rate | 402500089 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
SFID | 22211 |
Max Traffic Rate | 38500089 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Max Concatenated Burst | 42600 |
Scheduling Type | BestEffort |
a week ago
Time Priority Description
22/10/2024 15:57:42 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/10/2024 01:31:13 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/10/2024 01:23:26 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/10/2024 01:04:51 | critical | 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; |
22/10/2024 01:01:56 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/10/2024 01:01:52 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/10/2024 01:01:52 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/10/2024 01:01:52 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/10/2024 01:01:52 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/10/2024 01:01:52 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/10/2024 01:01:52 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/10/2024 01:01:50 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/10/2024 01:01:50 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/10/2024 01:01:49 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/10/2024 01:01:48 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/10/2024 01:01:47 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/10/2024 01:01:47 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/10/2024 01:01:47 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/10/2024 01:01:47 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/10/2024 01:01:46 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
a week ago
a week ago
a week ago
a week ago
a week ago
Welcome to the community forums.
Sorry to hear you're having service issues. I've checked the systems on our side and cannot see anything at this time that might be causing this. I can see that you've already a visit arranged to investigate this further. Please do keep us posted and let us know if you are having any further issues or have any questions at all. We'll be here to help on the community forums if needed
a week ago
Hi Carley,
Thanks for coming back to me.
I am still experiencing some slow down and a very significant number of pre RS Errors and a number of post RS Errors.
I'm running analysis software on a computer connected directly by cable to the HUB 3 and it is showing considerably high latencies (averaging around 35ms but running as high as 180ms with around 4 - 5 % packet drop.
FYI the Hub3 doesn't handle our WiFi connections - that's handled via an enterprise grade WAP.
I've a few more things to check out to be sure but I'm veering towards it being an issue with the fibre as the problems have only occurred since Street lighting engineers carried out work on the street and excavated a cable trench directly intersecting the fiber ducts! This of course may be a coincidence.
As you may have guessed from my moniker I've a reasonable knowledge of networks, and fibre installation as its something I do frequently in my day job 😀
Thanks again,
Jim