on 14-12-2022 01:22
Been having dropouts for the past couple of days after midnight.
Checked the modem noticed upstream issues.
Which I believe is indictive of a mainline issue.
Not sure where the fault lies.
Unfortunately support via customer services hasn't yielded much help.
They just said they would monitor it and let techs know.
13/12/2022 08:00:30 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/12/2022 02:22:38 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/12/2022 02:22:34 | Warning! | TCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/12/2022 02:22:34 | Warning! | Initializing Channel Timeout Expires - Time the CM can perform initial ranging on all upstream channels in the TCS has expired;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/12/2022 19:14:42 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/12/2022 00:15:17 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/12/2022 00:10:12 | Warning! | TCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/12/2022 00:10:12 | Warning! | Initializing Channel Timeout Expires - Time the CM can perform initial ranging on all upstream channels in the TCS has expired;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/12/2022 19:40:8 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/12/2022 10:55:27 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/12/2022 10:55:24 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/12/2022 10:55:24 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/12/2022 10:55:23 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/12/2022 10:55:22 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/12/2022 10:55:13 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/12/2022 10:55:13 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/12/2022 10:55:12 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
Answered! Go to Answer
15-12-2022 14:20 - edited 15-12-2022 15:06
on 14-12-2022 01:23
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 39400000 | 51 | 5120 | 64 qam | 2 |
2 | 25800000 | 51 | 5120 | 64 qam | 4 |
3 | 46200000 | 51 | 5120 | 64 qam | 1 |
4 | 32600000 | 51 | 5120 | 64 qam | 3 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
on 14-12-2022 01:24
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 234750000 | 2.4 | 38 | 256 qam | 13 |
2 | 242750000 | 2.2 | 38 | 256 qam | 14 |
3 | 250750000 | 2.5 | 38 | 256 qam | 15 |
4 | 258750000 | 2.5 | 38 | 256 qam | 16 |
5 | 266750000 | 2.7 | 38 | 256 qam | 17 |
6 | 274750000 | 2.7 | 38 | 256 qam | 18 |
7 | 282750000 | 3 | 38 | 256 qam | 19 |
8 | 290750000 | 3 | 38 | 256 qam | 20 |
9 | 298750000 | 3.4 | 38 | 256 qam | 21 |
10 | 306750000 | 3.2 | 38 | 256 qam | 22 |
11 | 314750000 | 3.5 | 38 | 256 qam | 23 |
12 | 322750000 | 3.4 | 38 | 256 qam | 24 |
13 | 330750000 | 3.5 | 38 | 256 qam | 25 |
14 | 338750000 | 3.5 | 38 | 256 qam | 26 |
15 | 346750000 | 3.5 | 38 | 256 qam | 27 |
16 | 354750000 | 3.2 | 38 | 256 qam | 28 |
17 | 362750000 | 3.5 | 38 | 256 qam | 29 |
18 | 370750000 | 3.5 | 38 | 256 qam | 30 |
19 | 378750000 | 3.7 | 38 | 256 qam | 31 |
20 | 386750000 | 3.4 | 38 | 256 qam | 32 |
21 | 394750000 | 3.5 | 38 | 256 qam | 34 |
22 | 402750000 | 3.4 | 38 | 256 qam | 35 |
23 | 410750000 | 3.7 | 38 | 256 qam | 36 |
24 | 418750000 | 3.5 | 38 | 256 qam | 37 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 38.9 | 6 | 0 |
2 | Locked | 38.6 | 2 | 0 |
3 | Locked | 38.9 | 7 | 0 |
4 | Locked | 38.6 | 4 | 0 |
5 | Locked | 38.9 | 6 | 0 |
6 | Locked | 38.6 | 6 | 0 |
7 | Locked | 38.6 | 5 | 0 |
8 | Locked | 38.6 | 7 | 0 |
9 | Locked | 38.6 | 8 | 0 |
10 | Locked | 38.9 | 6 | 0 |
11 | Locked | 38.9 | 5 | 0 |
12 | Locked | 38.6 | 8 | 0 |
13 | Locked | 38.6 | 4 | 0 |
14 | Locked | 38.9 | 7 | 0 |
15 | Locked | 38.9 | 8 | 0 |
16 | Locked | 38.9 | 2 | 0 |
17 | Locked | 38.9 | 6 | 0 |
18 | Locked | 38.9 | 7 | 0 |
19 | Locked | 38.6 | 6 | 0 |
20 | Locked | 38.6 | 7 | 0 |
21 | Locked | 38.9 | 6 | 0 |
22 | Locked | 38.9 | 8 | 0 |
23 | Locked | 38.6 | 9 | 0 |
24 | Locked | 38.9 | 9 | 0 |
on 14-12-2022 13:55
Interesting situation
I saw someone mention a bad attenuator in another thread.
What do you know, when I removed the cable, it was completely bent.
I'm not sure how this occurred, but I've since changed the attenuator.
From a previous cable that was installed on the same line before.
Strangely, the previous occupant had no problems.
Second hint: Our attenuator is too high.
Latency and jitter are much more stable when using one rated at 3db as opposed to 6db.
As far as I can tell, the problem may have been the downstream rather than upstream.
No matter what we do, upstream remains at 51.
on 14-12-2022 13:55
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 234750000 | 5.4 | 38 | 256 qam | 13 |
2 | 242750000 | 5.3 | 38 | 256 qam | 14 |
3 | 250750000 | 5.5 | 38 | 256 qam | 15 |
4 | 258750000 | 5.5 | 38 | 256 qam | 16 |
5 | 266750000 | 5.9 | 38 | 256 qam | 17 |
6 | 274750000 | 5.8 | 38 | 256 qam | 18 |
7 | 282750000 | 6 | 38 | 256 qam | 19 |
8 | 290750000 | 6 | 38 | 256 qam | 20 |
9 | 298750000 | 6.5 | 38 | 256 qam | 21 |
10 | 306750000 | 6.3 | 38 | 256 qam | 22 |
11 | 314750000 | 6.4 | 38 | 256 qam | 23 |
12 | 322750000 | 6.4 | 38 | 256 qam | 24 |
13 | 330750000 | 6.5 | 38 | 256 qam | 25 |
14 | 338750000 | 6.6 | 38 | 256 qam | 26 |
15 | 346750000 | 6.5 | 38 | 256 qam | 27 |
16 | 354750000 | 6.5 | 38 | 256 qam | 28 |
17 | 362750000 | 6.5 | 38 | 256 qam | 29 |
18 | 370750000 | 6.5 | 38 | 256 qam | 30 |
19 | 378750000 | 6.6 | 38 | 256 qam | 31 |
20 | 386750000 | 6.5 | 38 | 256 qam | 32 |
21 | 394750000 | 6.6 | 38 | 256 qam | 34 |
22 | 402750000 | 6.5 | 38 | 256 qam | 35 |
23 | 410750000 | 6.8 | 38 | 256 qam | 36 |
24 | 418750000 | 6.5 | 38 | 256 qam | 37 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 38.6 | 5 | 0 |
2 | Locked | 38.6 | 0 | 0 |
3 | Locked | 38.9 | 0 | 0 |
4 | Locked | 38.9 | 0 | 0 |
5 | Locked | 38.6 | 5 | 0 |
6 | Locked | 38.6 | 0 | 0 |
7 | Locked | 38.9 | 5 | 0 |
8 | Locked | 38.6 | 4 | 0 |
9 | Locked | 38.9 | 6 | 0 |
10 | Locked | 38.9 | 6 | 0 |
11 | Locked | 38.9 | 0 | 0 |
12 | Locked | 38.6 | 0 | 0 |
13 | Locked | 38.9 | 0 | 0 |
14 | Locked | 38.9 | 5 | 0 |
15 | Locked | 38.6 | 2 | 0 |
16 | Locked | 38.9 | 0 | 0 |
17 | Locked | 38.9 | 5 | 0 |
18 | Locked | 38.9 | 5 | 0 |
19 | Locked | 38.9 | 5 | 0 |
20 | Locked | 38.6 | 0 | 0 |
21 | Locked | 38.6 | 5 | 0 |
22 | Locked | 38.6 | 0 | 0 |
23 | Locked | 38.6 | 6 | 0 |
24 | Locked | 38.6 | 6 | 0 |
14-12-2022 13:56 - edited 14-12-2022 13:57
Time will tell if the issue is fixed.
Will pop back tomorrow.
15-12-2022 00:12 - edited 15-12-2022 00:13
Well this is rather strange it just dropped.
Yet reconnected straight away.
At 00:08 almost one minute later it reconnected.
Incidentally the modem isn't showing anything in the log.
When I logged into the modem, it came back.
So bad firmware perhaps or main line issue?
Who knows, have a stronger attenuator on the way.
I figure once we get it stable during cold months.
Should be fine all year round.
Fingers crossed.
on 15-12-2022 00:32
Gone back to the 6db attenuator.
I don't trust the thing.
Middle isn't straight at all.
These are the new downstream values.
on 15-12-2022 00:33
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 234750000 | 2.5 | 38 | 256 qam | 13 |
2 | 242750000 | 2.5 | 38 | 256 qam | 14 |
3 | 250750000 | 2.7 | 38 | 256 qam | 15 |
4 | 258750000 | 2.7 | 38 | 256 qam | 16 |
5 | 266750000 | 3 | 38 | 256 qam | 17 |
6 | 274750000 | 3 | 38 | 256 qam | 18 |
7 | 282750000 | 3.2 | 38 | 256 qam | 19 |
8 | 290750000 | 3.4 | 38 | 256 qam | 20 |
9 | 298750000 | 3.7 | 38 | 256 qam | 21 |
10 | 306750000 | 3.5 | 38 | 256 qam | 22 |
11 | 314750000 | 3.7 | 38 | 256 qam | 23 |
12 | 322750000 | 3.5 | 38 | 256 qam | 24 |
13 | 330750000 | 3.7 | 38 | 256 qam | 25 |
14 | 338750000 | 3.9 | 38 | 256 qam | 26 |
15 | 346750000 | 3.7 | 38 | 256 qam | 27 |
16 | 354750000 | 3.5 | 38 | 256 qam | 28 |
17 | 362750000 | 3.7 | 38 | 256 qam | 29 |
18 | 370750000 | 3.7 | 38 | 256 qam | 30 |
19 | 378750000 | 3.9 | 38 | 256 qam | 31 |
20 | 386750000 | 3.7 | 38 | 256 qam | 32 |
21 | 394750000 | 3.9 | 38 | 256 qam | 34 |
22 | 402750000 | 3.7 | 38 | 256 qam | 35 |
23 | 410750000 | 4 | 38 | 256 qam | 36 |
24 | 418750000 | 3.7 | 38 | 256 qam | 37 |
on 15-12-2022 00:50
Just for the hell of it.
Removed the attenuator to see how the levels would behave.
Surprisingly without any attenuator the upstream looks more stable.