New Poster
•
1 Message
Only 1 bonded upstream channel, constant T3/T4 time-outs
Hi, I have an Arris SB6121 that has been showing just one upstream bonded channel, with T3 and T4 time-outs every minute or so in the log. Perhaps because of this, the status shows "Offline" even though the internet is usable.
It may have been this way for a while, but I only noticed since the connection became unstable lately, dropping out for hours every few weeks or so. No amount of restarting or resetting the modem works. Download, upload speeds and latency are good.
The modem is directly connected to the cable line from outside, with nothing but a ground block between the utility pole and the modem. No splitters, extenders, or filters.
Is there anything I can do to diagnose this further? Thanks all.
| Channel ID | 33 | 34 | 35 | 36 | |
| Frequency | 651000000 Hz | 657000000 Hz | 663000000 Hz | 669000000 Hz | |
| Signal to Noise Ratio | 38 dB | 38 dB | 38 dB | 39 dB | |
| Downstream Modulation | QAM256 | QAM256 | QAM256 | QAM256 | |
Power Level
| 6 dBmV | 5 dBmV | 5 dBmV | 5 dBmV |
| Channel ID | 5 | 8 | 7 | 6 |
| Frequency | 36500000 Hz | 17300000 Hz | 23700000 Hz | 30100000 Hz |
| Ranging Service ID | 2308 | 2308 | 2308 | 2308 |
| Symbol Rate | 5.120 Msym/sec | 5.120 Msym/sec | 5.120 Msym/sec | 5.120 Msym/sec |
| Power Level | 39 dBmV | 39 dBmV | 39 dBmV | 39 dBmV |
| Upstream Modulation | [2] QPSK [1] 32QAM [3] 64QAM | [2] QPSK [1] 32QAM [3] 64QAM | [2] QPSK [1] 32QAM [3] 64QAM | [2] QPSK [1] 32QAM [3] 64QAM |
| Ranging Status | Success | T4 TimeOut | T4 TimeOut | T4 TimeOut |
| Channel ID | 33 | 34 | 35 | 36 |
| Total Unerrored Codewords | 12130014434 | 12129120465 | 12129121859 | 12129121352 |
| Total Correctable Codewords | 124 | 103 | 122 | 99 |
| Total Uncorrectable Codewords | 1202 | 2173 | 1168 | 1277 |
Time Priority Code Message
| Sep 03 2020 16:02:46 | 3-Critical | R04.0 | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=64:55:b1:b9:03:da;CMTS-MAC=70:6e:6d:2c:b0:ee;CM-QOS=1.1;CM-VER=3.0; |
| Sep 03 2020 16:02:16 | 3-Critical | R05.0 | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=64:55:b1:b9:03:da;CMTS-MAC=70:6e:6d:2c:b0:ee;CM-QOS=1.1;CM-VER=3.0; |
| Sep 03 2020 16:02:06 | 3-Critical | R04.0 | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=64:55:b1:b9:03:da;CMTS-MAC=70:6e:6d:2c:b0:ee;CM-QOS=1.1;CM-VER=3.0; |
| Sep 03 2020 16:01:56 | 3-Critical | R05.0 | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=64:55:b1:b9:03:da;CMTS-MAC=70:6e:6d:2c:b0:ee;CM-QOS=1.1;CM-VER=3.0; |
| Sep 03 2020 16:01:36 | 3-Critical | R04.0 | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=64:55:b1:b9:03:da;CMTS-MAC=70:6e:6d:2c:b0:ee;CM-QOS=1.1;CM-VER=3.0; |
| Sep 03 2020 16:01:36 | 3-Critical | R05.0 | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=64:55:b1:b9:03:da;CMTS-MAC=70:6e:6d:2c:b0:ee;CM-QOS=1.1;CM-VER=3.0; |
| Sep 03 2020 16:01:26 | 3-Critical | R04.0 | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=64:55:b1:b9:03:da;CMTS-MAC=70:6e:6d:2c:b0:ee;CM-QOS=1.1;CM-VER=3.0; |
No Responses!