Hello there, Sorry I have to type English as my Dutch is quite bad.
Since last night, my modem (connectbox) started to restart itself almost each hour, it doesn’t have a regular timely schedule, but it looks like it usually happens when I’m streaming videos/games or in a video conference.
I’ve been in the live chat for the last 2 hours but still no one responded yet, so I thought a community post might be better.
My modem is in bridge mode, but the problem appears to be on the connectbox modem itself, not on my router. I’ve seen similar issues on this forum, where it’s recommended for people to share upstream and downstream channels from the modem interface, below I’ll paste those information as well as my network logs. I also see one critical error on network logs; “No Ranging Response received - T3 time-out” just like in this post here; https://community.ziggo.nl/internetverbinding-102/veel-no-ranging-response-received-t3-time-out-meldingen-58942
Below you can see the downstream and upstream values from the modem interface. I don’t know how to read these values tho, I’m not sure if they’re normal or not.
Downstream Bonded Channels
| Channel | Frequency (Hz) | Power (dBmV) | SNR (dB) | Modulation | Channel ID |
| 1 | 618000000 | 1.5 | 40 | 256 qam | 3 |
| 2 | 610000000 | 1.5 | 38 | 256 qam | 2 |
| 3 | 602000000 | 1.5 | 38 | 256 qam | 1 |
| 4 | 626000000 | 1.2 | 38 | 256 qam | 4 |
| 5 | 634000000 | 1 | 38 | 256 qam | 5 |
| 6 | 642000000 | 1 | 38 | 256 qam | 6 |
| 7 | 650000000 | 1.4 | 38 | 256 qam | 7 |
| 8 | 658000000 | 1.7 | 40 | 256 qam | 8 |
| 9 | 666000000 | 2 | 40 | 256 qam | 9 |
| 10 | 674000000 | 2.7 | 38 | 256 qam | 10 |
| 11 | 682000000 | 2.7 | 38 | 256 qam | 11 |
| 12 | 690000000 | 2.5 | 40 | 256 qam | 12 |
| 13 | 698000000 | 2 | 38 | 256 qam | 13 |
| 14 | 706000000 | 1.5 | 38 | 256 qam | 14 |
| 15 | 714000000 | 0.9 | 38 | 256 qam | 15 |
| 16 | 722000000 | 0.2 | 38 | 256 qam | 16 |
| 17 | 730000000 | 0.2 | 38 | 256 qam | 17 |
| 18 | 738000000 | 0 | 38 | 256 qam | 18 |
| 19 | 746000000 | 0 | 38 | 256 qam | 19 |
| 20 | 754000000 | -0.5 | 38 | 256 qam | 20 |
| 21 | 762000000 | 0 | 38 | 256 qam | 21 |
| 22 | 770000000 | 0 | 38 | 256 qam | 22 |
| 23 | 778000000 | -0.5 | 38 | 256 qam | 23 |
| 24 | 786000000 | -0.5 | 38 | 256 qam | 24 |
Downstream Bonded Channels
| Channel | Locked Status | RxMER (dB) | Pre RS Errors | Post RS Errors |
| 1 | Locked | 40.3 | 5 | 0 |
| 2 | Locked | 38.9 | 0 | 0 |
| 3 | Locked | 38.9 | 3 | 0 |
| 4 | Locked | 38.9 | 0 | 0 |
| 5 | Locked | 38.9 | 6 | 0 |
| 6 | Locked | 38.9 | 5 | 0 |
| 7 | Locked | 38.9 | 0 | 0 |
| 8 | Locked | 40.3 | 6 | 0 |
| 9 | Locked | 40.3 | 0 | 0 |
| 10 | Locked | 38.6 | 5 | 0 |
| 11 | Locked | 38.9 | 4 | 0 |
| 12 | Locked | 40.3 | 5 | 0 |
| 13 | Locked | 38.9 | 0 | 0 |
| 14 | Locked | 38.9 | 5 | 0 |
| 15 | Locked | 38.9 | 7 | 0 |
| 16 | Locked | 38.6 | 0 | 0 |
| 17 | Locked | 38.6 | 5 | 0 |
| 18 | Locked | 38.9 | 0 | 0 |
| 19 | Locked | 38.9 | 4 | 0 |
| 20 | Locked | 38.6 | 0 | 0 |
| 21 | Locked | 38.9 | 5 | 0 |
| 22 | Locked | 38.9 | 4 | 0 |
| 23 | Locked | 38.6 | 0 | 0 |
| 24 | Locked | 38.9 | 5 | 0 |
Upstream Bonded Channels
| Channel | Frequency (Hz) | Power (dBmV) | Symbol Rate (ksps) | Modulation | Channel ID |
| 1 | 44000000 | 4.65 | 5120 | 64 qam | 3 |
| 2 | 28600000 | 4.65 | 2560 | 64 qam | 6 |
| 3 | 50900000 | 4.65 | 5120 | 64 qam | 2 |
| 4 | 37100000 | 4.65 | 5120 | 64 qam | 4 |
| 5 | 57800000 | 4.65 | 5120 | 64 qam | 1 |
| 6 | 31800000 | 4.65 | 2560 | 64 qam | 5 |
Upstream Bonded Channels
| 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 |
| 5 | ATDMA | 0 | 0 | 0 | 0 |
| 6 | ATDMA | 0 | 0 | 0 | 0 |
and finally,
Network Logs
| Time | Priority | Description |
| 03/09/2020 22:24:50 | notice | LAN login Success;CM-MAC=18:35:d1:a8:b4:13;CMTS-MAC=00:17:10:91:e4:96;CM-QOS=1.1;CM-VER=3.0; |
| 03/09/2020 22:23:20 | notice | TLV-11 - unrecognized OID;CM-MAC=18:35:d1:a8:b4:13;CMTS-MAC=00:17:10:91:e4:96;CM-QOS=1.1;CM-VER=3.0; |
| 03/09/2020 20:38:59 | critical | No Ranging Response received - T3 time-out;CM-MAC=18:35:d1:a8:b4:13;CMTS-MAC=00:17:10:91:e4:96;CM-QOS=1.1;CM-VER=3.0; |
| 03/09/2020 20:16:27 | notice | TLV-11 - unrecognized OID;CM-MAC=18:35:d1:a8:b4:13;CMTS-MAC=00:17:10:91:e4:96;CM-QOS=1.1;CM-VER=3.0; |
| 03/09/2020 20:12:05 | critical | No Ranging Response received - T3 time-out;CM-MAC=18:35:d1:a8:b4:13;CMTS-MAC=00:17:10:91:e4:96;CM-QOS=1.1;CM-VER=3.0; |
| 03/09/2020 18:53:08 | notice | TLV-11 - unrecognized OID;CM-MAC=18:35:d1:a8:b4:13;CMTS-MAC=00:17:10:91:e4:96;CM-QOS=1.1;CM-VER=3.0; |
| 03/09/2020 18:44:24 | critical | No Ranging Response received - T3 time-out;CM-MAC=18:35:d1:a8:b4:13;CMTS-MAC=00:17:10:91:e4:96;CM-QOS=1.1;CM-VER=3.0; |
| 03/09/2020 17:48:27 | notice | TLV-11 - unrecognized OID;CM-MAC=18:35:d1:a8:b4:13;CMTS-MAC=00:17:10:91:e4:96;CM-QOS=1.1;CM-VER=3.0; |
| 03/09/2020 15:21:23 | critical | No Ranging Response received - T3 time-out;CM-MAC=18:35:d1:a8:b4:13;CMTS-MAC=00:17:10:91:e4:96;CM-QOS=1.1;CM-VER=3.0; |
| 03/09/2020 13:07:38 | notice | TLV-11 - unrecognized OID;CM-MAC=18:35:d1:a8:b4:13;CMTS-MAC=00:17:10:91:e4:96;CM-QOS=1.1;CM-VER=3.0; |
| 03/09/2020 12:58:25 | critical | No Ranging Response received - T3 time-out;CM-MAC=18:35:d1:a8:b4:13;CMTS-MAC=00:17:10:91:e4:96;CM-QOS=1.1;CM-VER=3.0; |
| 03/09/2020 12:32:02 | notice | TLV-11 - unrecognized OID;CM-MAC=18:35:d1:a8:b4:13;CMTS-MAC=00:17:10:91:e4:96;CM-QOS=1.1;CM-VER=3.0; |
| 03/09/2020 11:38:32 | critical | No Ranging Response received - T3 time-out;CM-MAC=18:35:d1:a8:b4:13;CMTS-MAC=00:17:10:91:e4:96;CM-QOS=1.1;CM-VER=3.0; |
| 03/09/2020 8:09:17 | notice | TLV-11 - unrecognized OID;CM-MAC=18:35:d1:a8:b4:13;CMTS-MAC=00:17:10:91:e4:96;CM-QOS=1.1;CM-VER=3.0; |
| 03/09/2020 4:08:26 | critical | No Ranging Response received - T3 time-out;CM-MAC=18:35:d1:a8:b4:13;CMTS-MAC=00:17:10:91:e4:96;CM-QOS=1.1;CM-VER=3.0; |
| 03/09/2020 1:58:10 | notice | TLV-11 - unrecognized OID;CM-MAC=18:35:d1:a8:b4:13;CMTS-MAC=00:17:10:91:e4:96;CM-QOS=1.1;CM-VER=3.0; |
| 03/09/2020 1:45:14 | critical | No Ranging Response received - T3 time-out;CM-MAC=18:35:d1:a8:b4:13;CMTS-MAC=00:17:10:91:e4:96;CM-QOS=1.1;CM-VER=3.0; |
| 03/09/2020 0:43:54 | notice | TLV-11 - unrecognized OID;CM-MAC=18:35:d1:a8:b4:13;CMTS-MAC=00:17:10:91:e4:96;CM-QOS=1.1;CM-VER=3.0; |
| 05/08/2020 13:39:53 | critical | No Ranging Response received - T3 time-out;CM-MAC=18:35:d1:a8:b4:13;CMTS-MAC=00:17:10:91:e4:96;CM-QOS=1.1;CM-VER=3.0; |
| 05/08/2020 10:17:48 | notice | TLV-11 - unrecognized OID;CM-MAC=18:35:d1:a8:b4:13;CMTS-MAC=00:17:10:91:e4:96;CM-QOS=1.1;CM-VER=3.0; |
I wouldn’t mind connection drops too much, but since we are working remotely for a while now, losing connection during calls can be a serious issue for me. I haven’t seen this problem before at all and it started suddenly yesterday night. Let me know if there is anything I could do.
Thanks!
M.


