8 days of intermittent outages and no reply to previous post days ago
Hi, there is a fault at the cmts. Keep getting intermittent outages, can you help please.
Broadband monitor link https://www.thinkbroadband.com/broadband/monitoring/quality/share/30f1c46b670d89cd8e65fb6a9a567ff0212a1050
Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID1 | 36600009 | 57 | 5120 | 64 qam | 8 |
Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts1 | ATDMA | 0 | 0 | 42 | 0 |
Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 34 | 425673 | 66118 |
2 | Locked | 34.4 | 373294 | 61175 |
3 | Locked | 34.6 | 336435 | 54305 |
4 | Locked | 35 | 303278 | 49361 |
5 | Locked | 34.9 | 280155 | 47182 |
6 | Locked | 35 | 257340 | 43602 |
7 | Locked | 35 | 239109 | 43632 |
8 | Locked | 35.2 | 215409 | 39123 |
9 | Locked | 35.5 | 196110 | 35306 |
10 | Locked | 35.5 | 182176 | 32848 |
11 | Locked | 35.7 | 171868 | 30828 |
12 | Locked | 35.7 | 159136 | 28359 |
13 | Locked | 35.7 | 143429 | 24206 |
14 | Locked | 35.7 | 134034 | 21498 |
15 | Locked | 35.7 | 125348 | 19146 |
16 | Locked | 35.5 | 121226 | 17788 |
17 | Locked | 35.2 | 113991 | 15999 |
18 | Locked | 35.5 | 103610 | 12534 |
19 | Locked | 35.9 | 93242 | 9825 |
20 | Locked | 36.3 | 87265 | 9127 |
21 | Locked | 35.7 | 82142 | 8433 |
22 | Locked | 35.5 | 75346 | 7526 |
23 | Locked | 35.7 | 69671 | 7106 |
24 | Locked | 35.5 | 64813 | 6559 |
Time Priority Description
17/10/2024 13:11:36 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/10/2024 13:11:21 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/10/2024 13:10:0 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/10/2024 12:12:49 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/10/2024 11:39:32 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/10/2024 11:39:31 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/10/2024 11:39:26 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/10/2024 11:39:2 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/10/2024 11:38:58 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/10/2024 11:38:35 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/10/2024 11:38:35 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/10/2024 11:38:12 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/10/2024 11:38:11 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/10/2024 11:37:48 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/10/2024 11:37:45 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/10/2024 11:37:43 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/10/2024 04:43:46 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/10/2024 04:43:44 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/10/2024 04:43:42 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/10/2024 04:43:15 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
Is there really only one upstream channel - maxed out on power too ?
Start from a clean sheet by doing this...
+++++++++++++++++++++++++++++
Switch the Hub off and unplug it from the mains supply for five minutes. Whilst it's off, Do a quick check that all of your coax and ethernet cable connections are in nice and "finger" tight - at the Hub and wall box and also at any connectors etc. Disconnect all the connections and reconnect to be sure. Ensure there are no “unterminated cable loose ends. Also check that the internal wiring is ok with no kinking, chaffing or dog chews etc.
Also, check that all looks good with the outside cabling and wall box (no “staples, etc.,) piercing the cables. Then, switch the Hub back on and leave ~5 minutes When all done, check back in the settings and ensure that the PostRS error counts and T3 errors have all reset to 0. Then check every hour or so to see if they start reappearing - they shouldn't. If they do (particularly the PostRS and T3 ones) you have a problem (noise) that only a Tech visit will sort.
Also check the Upstream QAM’s are all at 64Then, Post up all of your Hub/network connection details - just copy/paste the normal “Formatted Text” (not images) 3 FULL sets of data onto here – 2 tables from the Downstream, 2 from the Upstream, & the Network Logs pages. Don't worry too much about the formatting it can be easily read & DON’T include personal data or MAC addresses - blank them out - if you copy/paste the data, the board software will do this for you (you may need to click the "submit" button again). If character limits are “exceeded” - just do two posts