Welcome to the Cox Community
Our community is a collaborative place to learn about Cox products and services. Jump into the conversation today!
Messages
Selected Messages
New Contributor
•
T3 disconnects with SB6141, requires modem reboot frequently
Hello-
I have been having an issue in the last week where my modem needs to be unplugged and plugged back in due to internet failing approximately every 30 minutes (while using it).
I am in Orange County, and using the Arris SB6141 modem. The log shows "T3 time-out" right before failure.
Logs below - any ideas on this? Past posts here suggest its a cox problem with the signal.
Dec 04 2016 13:32:33
| 6-Notice | I401.0 | TLV-11 - unrecognized OID;CM-MAC=84:61:a0:7e:c2:ec;CMTS-MAC=00:24:14:64:09:61;CM-QOS=1.1;CM-VER=3.0; | |
| Dec 04 2016 13:32:33 | 5-Warning | Z00.0 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=84:61:a0:7e:c2:ec;CMTS-MAC=00:24:14:64:09:61;CM-QOS=1.1;CM-VER=3.0; |
| Jan 01 1970 00:00:30 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=84:61:a0:7e:c2:ec;CMTS-MAC=00:24:14:64:09:61;CM-QOS=1.1;CM-VER=3.0; |
| Jan 01 1970 00:00:15 | 6-Notice | N/A | Cable Modem Reboot due to power reset ;CM-MAC=84:61:a0:7e:c2:ec;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; |
| Dec 04 2016 13:31:02 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=84:61:a0:7e:c2:ec;CMTS-MAC=00:24:14:64:09:61;CM-QOS=1.1;CM-VER=3.0; |
| Dec 04 2016 13:30:18 | 3-Critical | R06.0 | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=84:61:a0:7e:c2:ec;CMTS-MAC=00:24:14:64:09:61;CM-QOS=1.1;CM-VER=3.0; |
| Dec 04 2016 13:30:18 | 3-Critical | R03.0 | Ranging Request Retries exhausted;CM-MAC=84:61:a0:7e:c2:ec;CMTS-MAC=00:24:14:64:09:61;CM-QOS=1.1;CM-VER=3.0; |
| Dec 04 2016 13:30:16 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=84:61:a0:7e:c2:ec;CMTS-MAC=00:24:14:64:09:61;CM-QOS=1.1;CM-VER=3.0; |
| Dec 04 2016 13:30:03 | 3-Critical | R06.0 | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=84:61:a0:7e:c2:ec;CMTS-MAC=00:24:14:64:09:61;CM-QOS=1.1;CM-VER=3.0; |
| Dec 04 2016 13:30:03 | 3-Critical | R03.0 | Ranging Request Retries exhausted;CM-MAC=84:61:a0:7e:c2:ec;CMTS-MAC=00:24:14:64:09:61;CM-QOS=1.1;CM-VER=3.0; |
| Dec 04 2016 13:30:02 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=84:61:a0:7e:c2:ec;CMTS-MAC=00:24:14:64:09:61;CM-QOS=1.1;CM-VER=3.0; |
| Dec 04 2016 12:50:00 | 6-Notice | I401.0 | TLV-11 - unrecognized OID;CM-MAC=84:61:a0:7e:c2:ec;CMTS-MAC=00:24:14:64:09:61;CM-QOS=1.1;CM-VER=3.0; |
| Dec 04 2016 12:50:00 | 5-Warning | Z00.0 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=84:61:a0:7e:c2:ec;CMTS-MAC=00:24:14:64:09:61;CM-QOS=1.1;CM-VER=3.0; |
| Jan 01 1970 00:00:34 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=84:61:a0:7e:c2:ec;CMTS-MAC=00:24:14:64:09:61;CM-QOS=1.1;CM-VER=3.0; |
| Jan 01 1970 00:00:15 | 6-Notice | N/A | Cable Modem Reboot due to power reset ;CM-MAC=84:61:a0:7e:c2:ec;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; |
| Dec 04 2016 12:48:40 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=84:61:a0:7e:c2:ec;CMTS-MAC=00:24:14:64:09:61;CM-QOS=1.1;CM-VER=3.0; |
| Dec 04 2016 12:48:40 | 3-Critical | R07.0 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=84:61:a0:7e:c2:ec;CMTS-MAC=00:24:14:64:09:61;CM-QOS=1.1;CM-VER=3.0; |
| Dec 04 2016 12:48:39 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=84:61:a0:7e:c2:ec;CMTS-MAC=00:24:14:64:09:61;CM-QOS=1.1;CM-VER=3.0; |
| Dec 04 2016 12:47:26 | 3-Critical | R07.0 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=84:61:a0:7e:c2:ec;CMTS-MAC=00:24:14:64:09:61;CM-QOS=1.1;CM-VER=3.0; |
| Dec 04 2016 12:47:20 | 3-Critical | R06.0 | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=84:61:a0:7e:c2:ec;CMTS-MAC=00:24:14:64:09:61;CM-QOS=1.1;CM-VER=3.0; |
Signal:
Downstream
| Bonding Channel Value | |||||||||
|---|---|---|---|---|---|---|---|---|---|
| Channel ID | 46 | 41 | 42 | 43 | 44 | 45 | 47 | 48 | |
| Frequency | 909000000 Hz | 879000000 Hz | 885000000 Hz | 891000000 Hz | 897000000 Hz | 903000000 Hz | 915000000 Hz | 921000000 Hz | |
| Signal to Noise Ratio | 37 dB | 38 dB | 38 dB | 38 dB | 38 dB | 38 dB | 38 dB | 38 dB | |
| Downstream Modulation | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | |
Power Level
|
-2 dBmV | -1 dBmV | -2 dBmV | -2 dBmV | -2 dBmV | -2 dBmV | -3 dBmV |
-3 dBmV |
|
Upstream
| Bonding Channel Value | ||||
|---|---|---|---|---|
| Channel ID | 1 | 2 | 3 | 4 |
| Frequency | 17600000 Hz | 24000000 Hz | 30400000 Hz | 36800000 Hz |
| Ranging Service ID | 132 | 132 | 132 | 132 |
| Symbol Rate | 2.560 Msym/sec | 5.120 Msym/sec | 5.120 Msym/sec | 5.120 Msym/sec |
| Power Level | 36 dBmV | 38 dBmV | 39 dBmV | 40 dBmV |
| Upstream Modulation | [3] QPSK [2] 16QAM [3] 64QAM |
[3] 16QAM [3] 64QAM |
[3] 16QAM [3] 64QAM |
[3] 16QAM [3] 64QAM |
| Ranging Status | Success | Success | Success | Success |
Thanks!
ChrisL
Former Moderator
•
The modem should recover from a T3 event on it's own either by the event passing or the modem rebooting itself due to lost sync. You may wan to test without the router just to make sure the manual reboot isn't correcting some other issue however if the issue continues this would suggest either a signal or modem issue.
0
0