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 Timeouts
I have had several service calls and each time the technician comes out they can't find an issue. I have extensive knowledge in Broadband internet as I was an installer, service tech, QC tech, and Technical Trainer with Comcast. I have been doing extensive research on my issues that have been occurring and no I am having return issues on my system. I am tired of technicians coming to my house and doing nothing to fix the problem.
Here is what I deal with on a daily basis and multiple times per day to say the least.
| Oct 25 2015 23:20:33 | 6-Notice | I401.0 | TLV-11 - unrecognized OID;CM-MAC=10:05:b1:93:2a:93;CMTS-MAC=c4:71:fe:76:cd:9f;CM-QOS=1.1;CM-VER=3.0; |
| Oct 25 2015 23:20:33 | 5-Warning | Z00.0 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=10:05:b1:93:2a:93;CMTS-MAC=c4:71:fe:76:cd:9f;CM-QOS=1.1;CM-VER=3.0; |
| Jan 01 1970 00:00:22 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=10:05:b1:93:2a:93;CMTS-MAC=c4:71:fe:76:cd:9f;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=10:05:b1:93:2a:93;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; |
| Oct 25 2015 23:19:14 | 3-Critical | T05.0 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=10:05:b1:93:2a:93;CMTS-MAC=c4:71:fe:76:cd:9f;CM-QOS=1.1;CM-VER=3.0; |
| Oct 25 2015 20:26:42 | 6-Notice | I401.0 | TLV-11 - unrecognized OID;CM-MAC=10:05:b1:93:2a:93;CMTS-MAC=c4:71:fe:76:cd:9f;CM-QOS=1.1;CM-VER=3.0; |
| Oct 25 2015 20:26:42 | 5-Warning | Z00.0 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=10:05:b1:93:2a:93;CMTS-MAC=c4:71:fe:76:cd:9f;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=10:05:b1:93:2a:93;CMTS-MAC=c4:71:fe:76:cd:9f;CM-QOS=1.1;CM-VER=3.0; |
| Oct 25 2015 19:53:54 | 6-Notice | I401.0 | TLV-11 - unrecognized OID;CM-MAC=10:05:b1:93:2a:93;CMTS-MAC=c4:71:fe:76:cd:9f;CM-QOS=1.1;CM-VER=3.0; |
| Oct 25 2015 19:53:54 | 5-Warning | Z00.0 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=10:05:b1:93:2a:93;CMTS-MAC=c4:71:fe:76:cd:9f;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=10:05:b1:93:2a:93;CMTS-MAC=c4:71:fe:76:cd:9f;CM-QOS=1.1;CM-VER=3.0; |
| Oct 24 2015 15:59:04 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=10:05:b1:93:2a:93;CMTS-MAC=c4:71:fe:76:cd:9f;CM-QOS=1.1;CM-VER=3.0; |
| Oct 24 2015 15:59:04 | 3-Critical | R07.0 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=10:05:b1:93:2a:93;CMTS-MAC=c4:71:fe:76:cd:9f;CM-QOS=1.1;CM-VER=3.0; |
| Oct 24 2015 15:59:03 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=10:05:b1:93:2a:93;CMTS-MAC=c4:71:fe:76:cd:9f;CM-QOS=1.1;CM-VER=3.0; |
| Oct 24 2015 15:59:03 | 3-Critical | R07.0 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=10:05:b1:93:2a:93;CMTS-MAC=c4:71:fe:76:cd:9f;CM-QOS=1.1;CM-VER=3.0; |
| Oct 24 2015 15:59:02 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=10:05:b1:93:2a:93;CMTS-MAC=c4:71:fe:76:cd:9f;CM-QOS=1.1;CM-VER=3.0; |
| Oct 24 2015 15:59:02 | 3-Critical | R07.0 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=10:05:b1:93:2a:93;CMTS-MAC=c4:71:fe:76:cd:9f;CM-QOS=1.1;CM-VER=3.0; |
| Oct 24 2015 15:59:01 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=10:05:b1:93:2a:93;CMTS-MAC=c4:71:fe:76:cd:9f;CM-QOS=1.1;CM-VER=3.0; |
| Oct 24 2015 15:59:01 | 3-Critical | R07.0 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=10:05:b1:93:2a:93;CMTS-MAC=c4:71:fe:76:cd:9f;CM-QOS=1.1;CM-VER=3.0; |
| Oct 24 2015 15:59:00 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=10:05:b1:93:2a:93;CMTS-MAC=c4:71:fe:76:cd:9f;CM-QOS=1.1;CM-VER=3.0; |
| Signal Stats (Codewords) | Bonding Channel Value | |||||||
|---|---|---|---|---|---|---|---|---|
| Channel ID | 73 | 74 | 75 | 76 | 81 | 82 | 83 | 84 |
| Total Unerrored Codewords | 87499435 | 86650451 | 86659086 | 86667310 | 86644389 | 86645640 | 86676018 | 86666889 |
| Total Correctable Codewords | 11 | 62 | 52 | 14 | 722 | 711 | 925 | 543 |
| Total Uncorrectable Codewords | 547 | 547 | 547 | 1455 | 1592 | 1491 | 677 | 1480 |
Not to mention one or two of the upstream channels aborts periodically throughout the day as well. The other evidence I have is that when I am having these issues and although the modem has bloc sync, your support technicians on the phone can't see my modem which means the return path (upstream) is not working properly. And you can't say it's my modem now because I returned it to BestBuy and got a brand spankin new one. I have only had this service since June and two modems later the problem still isn't fixed.
This is a new build area and we didn't start having issues until a few other homes moved in. Which may mean the node needs to swept for ingress/noise or just maybe the system is being overrun because the area wasn't cut over properly or segmented required. Regardless I have a student in this house and a teacher who require internet services. This is unacceptable and needs to be rectified. I also want credit for the terrible service.
Tecknowhelp
Valued Contributor II
•
Can you post your signal levels?
Also, I assume the resets from power are you unplugging it?
Whats your coaxial layout?
The inability for them to see your modem may be the tool they are using. Sometimes the server that passes the SNMP data from modem to system gets backed up. If it times out, they see that as modem offline. If they poll the street, they can usually still see the modem and it's IP(since thats logged). Pining that 10.x.x.x IP from Cox's end will show the modem is online. But your right, a issue with the upstream can also cause the problem.
PS. You probably want to edit out your MAC address from logs. Not a huge deal, but better to be safe.
0
0
DerrickW
Valued Contributor
•
I am sorry you've been having so many issues with the connection. We can look into this further for you, do you have any splitters or amplifiers connected to the cable outlet? Please send an email with the account information to cox.help@cox.com so we can investigate the signal problems you're having.
0
0
T3_Timeouts
New Contributor
•
0
0
DerrickW
Valued Contributor
•
0
0
T3_Timeouts
New Contributor
•
Here are the signal levels as of right now which is typical. These will change and typically show aborted on two of the upstream channels. I am actually thinking of putting a two or three way on the line to bump up the levels to 45-50 dBmV. Thoughts???
[3] 64QAM
[3] 64QAM
[3] 64QAM
[3] 64QAM
0
0
T3_Timeouts
New Contributor
•
Here are the errors as well.
0
0
Tecknowhelp
Valued Contributor II
•
" I am actually thinking of putting a two or three way on the line to bump up the levels to 45-50 dBmV. Thoughts???"
You never add a splitter to change signal levels, thats what pads are for IMO. But your signal levels look good. My guess is a bad tap. You should be getting atleast +4 to +5 off of it. Do you have a meter you could take a reading at the dmark?
0
0