on 18-09-2022 15:16
No idea why this is happening and is really frustrating and looks like what other people experience.
Time | Priority | Description |
18/09/2022 13:58:6 | notice | LAN login Success;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.0; |
18/09/2022 13:54:7 | Warning! | Lost MDD Timeout;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.0; |
18/09/2022 13:52:6 | Error | Service Change Response rejected - Invalid transaction ID;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.0; |
18/09/2022 13:51:1 | Error | Service Add Ack rejected - Invalid transaction ID;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.0; |
18/09/2022 13:50:28 | Warning! | Lost MDD Timeout;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.0; |
18/09/2022 13:50:21 | Error | Service Add Ack rejected - Invalid transaction ID;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.0; |
18/09/2022 13:14:30 | Warning! | Lost MDD Timeout;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.0; |
18/09/2022 13:13:20 | Error | Service Delete Response rejected - Invalid Transaction;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.0; |
on 18-09-2022 15:30
on 18-09-2022 15:46
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 331000000 | -7.2 | 37 | 256 qam | 25 |
2 | 339000000 | -6.2 | 37 | 256 qam | 26 |
3 | 347000000 | -7.5 | 36 | 256 qam | 27 |
4 | 355000000 | -7 | 37 | 256 qam | 28 |
5 | 363000000 | -6.7 | 37 | 256 qam | 29 |
6 | 371000000 | -7 | 37 | 256 qam | 30 |
7 | 379000000 | -7.7 | 37 | 256 qam | 31 |
8 | 387000000 | -7.2 | 37 | 256 qam | 32 |
9 | 395000000 | -7.9 | 36 | 256 qam | 33 |
10 | 403000000 | -7.5 | 37 | 256 qam | 34 |
11 | 411000000 | -6.7 | 37 | 256 qam | 35 |
12 | 419000000 | -6.9 | 38 | 256 qam | 36 |
13 | 427000000 | -7.9 | 37 | 256 qam | 37 |
14 | 435000000 | -6.5 | 38 | 256 qam | 38 |
15 | 443000000 | -7.2 | 37 | 256 qam | 39 |
16 | 451000000 | -7 | 37 | 256 qam | 40 |
17 | 459000000 | -6.2 | 38 | 256 qam | 41 |
18 | 467000000 | -6.7 | 38 | 256 qam | 42 |
19 | 475000000 | -7.7 | 36 | 256 qam | 43 |
20 | 483000000 | -6.7 | 27 | 256 qam | 44 |
21 | 491000000 | -7.2 | 29 | 256 qam | 45 |
22 | 499000000 | -7 | 37 | 256 qam | 46 |
23 | 507000000 | -6.7 | 31 | 256 qam | 47 |
24 | 515000000 | -7.2 | 33 | 256 qam | 48 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 37.3 | 0 | 0 |
2 | Locked | 37.6 | 5 | 0 |
3 | Locked | 36.6 | 1 | 0 |
4 | Locked | 37.6 | 5 | 0 |
5 | Locked | 37.3 | 5 | 0 |
6 | Locked | 37.6 | 9 | 0 |
7 | Locked | 37.3 | 8 | 0 |
8 | Locked | 37.6 | 8 | 0 |
9 | Locked | 36.6 | 1 | 0 |
10 | Locked | 37.6 | 5 | 0 |
11 | Locked | 37.6 | 2 | 0 |
12 | Locked | 38.6 | 6 | 0 |
13 | Locked | 37.6 | 5 | 0 |
14 | Locked | 38.6 | 8 | 0 |
15 | Locked | 37.3 | 4 | 0 |
16 | Locked | 37.6 | 8 | 0 |
17 | Locked | 38.6 | 7 | 0 |
18 | Locked | 38.6 | 11 | 0 |
19 | Locked | 36.6 | 7 | 0 |
20 | Locked | 27.3 | 18200020 | 90943 |
21 | Locked | 29.1 | 10568123 | 5 |
22 | Locked | 37.6 | 8 | 0 |
23 | Locked | 31.6 | 332656 | 0 |
24 | Locked | 33.9 | 185 | 0 |
1 | 36599979 | 52.3 | 5120 | 64 qam | 11 |
2 | 30099930 | 52.3 | 5120 | 64 qam | 12 |
3 | 43099905 | 52.3 | 5120 | 64 qam | 10 |
4 | 49599908 | 52.3 | 5120 | 64 qam | 9 |
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
Network access | Allowed |
Maximum Number of CPEs | 1 |
Baseline Privacy | Enabled |
DOCSIS Mode | Docsis30 |
Config file | sgvca69834ncxv9873254k;fg |
SFID | 21619 |
Max Traffic Rate | 575000000 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
SFID | 21512 |
Max Traffic Rate | 38520000 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Max Concatenated Burst | 16320 |
Scheduling Type | BestEffort |
on 18-09-2022 16:15
on 18-09-2022 23:51
What leads you that ? I've checked now and the results don't appear too different and the internet has been fine for about 4-5 hours.
on 19-09-2022 08:09
During the time that the Internet connection has behaving, the stats you provided that are reproduced below would not have been in force. In particular, the upstream cannot function (by design) if the power level exceeds 51dBmv - it reboots. So, something got fixed. If you can be bothered, it would be interesting to see your stats now that it's working again.
20 | Locked | 27.3 | 18200020 | 90943 |
21 | Locked | 29.1 | 10568123 | 5 |
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 36599979 | 52.3 | 5120 | 64 qam | 11 |
2 | 30099930 | 52.3 | 5120 | 64 qam | 12 |
3 | 43099905 | 52.3 | 5120 | 64 qam | 10 |
4 | 49599908 | 52.3 | 5120 | 64 qam | 9 |
19-09-2022 10:36 - edited 19-09-2022 10:38
Definitely, here we go, thoughts? It has been stable according to my firewall for the last 12 hours.
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 331000000 | -7.2 | 37 | 256 qam | 25 |
2 | 339000000 | -6.5 | 37 | 256 qam | 26 |
3 | 347000000 | -7.5 | 36 | 256 qam | 27 |
4 | 355000000 | -7.7 | 37 | 256 qam | 28 |
5 | 363000000 | -7.2 | 37 | 256 qam | 29 |
6 | 371000000 | -8 | 37 | 256 qam | 30 |
7 | 379000000 | -8 | 37 | 256 qam | 31 |
8 | 387000000 | -7.7 | 37 | 256 qam | 32 |
9 | 395000000 | -8.2 | 37 | 256 qam | 33 |
10 | 403000000 | -8 | 37 | 256 qam | 34 |
11 | 411000000 | -7.2 | 37 | 256 qam | 35 |
12 | 419000000 | -7.2 | 37 | 256 qam | 36 |
13 | 427000000 | -8 | 37 | 256 qam | 37 |
14 | 435000000 | -6.9 | 37 | 256 qam | 38 |
15 | 443000000 | -7.5 | 37 | 256 qam | 39 |
16 | 451000000 | -7.7 | 37 | 256 qam | 40 |
17 | 459000000 | -6.7 | 38 | 256 qam | 41 |
18 | 467000000 | -7.4 | 38 | 256 qam | 42 |
19 | 475000000 | -7.7 | 37 | 256 qam | 43 |
20 | 483000000 | -6.9 | 29 | 256 qam | 44 |
21 | 491000000 | -7.2 | 34 | 256 qam | 45 |
22 | 499000000 | -7.5 | 37 | 256 qam | 46 |
23 | 507000000 | -7.2 | 35 | 256 qam | 47 |
24 | 515000000 | -7.9 | 36 | 256 qam | 48 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 37.3 | 16744 | 13161 |
2 | Locked | 37.3 | 17341 | 9390 |
3 | Locked | 36.6 | 18329 | 8092 |
4 | Locked | 37.3 | 17465 | 12856 |
5 | Locked | 37.6 | 17343 | 6509 |
6 | Locked | 37.3 | 18373 | 3276 |
7 | Locked | 37.6 | 21036 | 6431 |
8 | Locked | 37.6 | 19710 | 7590 |
9 | Locked | 37.6 | 17886 | 6922 |
10 | Locked | 37.6 | 17716 | 8666 |
11 | Locked | 37.6 | 15854 | 10734 |
12 | Locked | 37.3 | 16486 | 9107 |
13 | Locked | 37.6 | 18201 | 4740 |
14 | Locked | 37.6 | 17458 | 6061 |
15 | Locked | 37.6 | 17422 | 5660 |
16 | Locked | 37.6 | 17570 | 2287 |
17 | Locked | 38.6 | 17232 | 2559 |
18 | Locked | 38.6 | 16782 | 4960 |
19 | Locked | 37.3 | 16254 | 12446 |
20 | Locked | 29.9 | 535040774 | 272381 |
21 | Locked | 34.9 | 64413370 | 4018 |
22 | Locked | 37.6 | 16454 | 9535 |
23 | Locked | 35.7 | 11801430 | 207900 |
24 | Locked | 36.6 | 139079 | 53359 |
1 | 36599969 | 52.3 | 5120 | 64 qam | 11 |
2 | 23600000 | 50.8 | 5120 | 64 qam | 13 |
3 | 30099979 | 50.8 | 5120 | 64 qam | 12 |
4 | 43099974 | 52.3 | 5120 | 64 qam | 10 |
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 19-09-2022 11:06
on 19-09-2022 11:25
I say "according to my firewall" - it is sensitive to WAN disconnects as it has a backup WAN and records them in its event log.
How has it not dropped/reset in that case? I'm getting a good latency and a consistent upload according to speedtest.net and speed tests on the firewall.
I'll see how it goes, thanks for the help.
Here's the latest upstream config dump
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 36599969 | 52.3 | 5120 | 64 qam | 11 |
2 | 23600000 | 50.8 | 5120 | 64 qam | 13 |
3 | 30099979 | 50.8 | 5120 | 64 qam | 12 |
4 | 43099974 | 52.3 | 5120 | 64 qam | 10 |
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 19-09-2022 11:31